Slackware 14.2 fresh install sanity check before sepkg -q audio command.

[globetrotterdk globetrotterdk]

After my problems with cross installing the Calf plugins from SlackBuilds.org, due to the installation of a different jack-connection-kit version by the quefile, I decided to do a fresh install, as I also wanted to install 

sonic-visualiser, which depends on the SlackBuilds.org version of the jack-connection-kit. Having run the quefile for sonic-visualiser, I am aware of at least one other program (it runs white noise as it is installed) that is installed by both sbopkg and sepkg. To avoid conflicts, I can remove the jack-connection-kit package, however I don't know if there are other packages that conflict with packages from the Studioware audio group. What can I do to run a sanity check before I run the sepkg -q audio command? Fortunately, this time around I installed any audio software that I am currently aware of that I need, that is not available in the Studioware audio group, before running sepkg -q audio, but that of course doesn't guarantee that something else isn't out there (such as the program that makes the white noise check as it is being installed) that was installed along with the sonic-visualiser quefile and conflicts with a Studioware package. Particularly, as I noted that more was installed via the quefile, than is listed as dependencies for sonic-visualiser on the SlackBuild.org site..

[globetrotterdk globetrotterdk]

On Thursday, May 3, 2018 at 8:22:28 AM UTC+2, globetrotterdk globetrotterdk wrote:

After my problems with cross installing the Calf plugins from SlackBuilds.org, due to the installation of a different jack-connection-kit version by the quefile, I decided to do a fresh install, as I also wanted to install 

sonic-visualiser, which depends on the SlackBuilds.org version of the jack-connection-kit. Having run the quefile for sonic-visualiser, I am aware of at least one other program (it runs white noise as it is installed) that is installed by both sbopkg and sepkg. To avoid conflicts, I can remove the jack-connection-kit package, however I don't know if there are other packages that conflict with packages from the Studioware audio group. What can I do to run a sanity check before I run the sepkg -q audio command? Fortunately, this time around I installed any audio software that I am currently aware of that I need, that is not available in the Studioware audio group, before running sepkg -q audio, but that of course doesn't guarantee that something else isn't out there (such as the program that makes the white noise check as it is being installed) that was installed along with the sonic-visualiser quefile and conflicts with a Studioware package. Particularly, as I noted that more was installed via the quefile, than is listed as dependencies for sonic-visualiser on the SlackBuild.org site.

 

BTW, here is an excellent video explaining what I want to use sonic-visualizer for:

https://www.youtube.com/watch?v=bQrleXXQmWY

If you notice, he just extracts the necessary vamp plugins, which is far superior to the alternative as the SlackBuild script qm-vamp-plugins requires atlas, which can cause all sorts of issues for the installer, as it requires the processor not being throttled. Whether this is only during the build, or always, I am unsure, but I suspect it is always, which would potentially interfere with other programs function normally (wouldn't it?).

[B Watson]

On 5/3/18, globetrotterdk globetrotterdk <globetr...@gmail.com> wrote:

> requires atlas, which can cause all sorts of issues for the installer, as
> it requires the processor not being throttled. Whether this is only during
> the build, or always, I am unsure, but I suspect it is always, which would
> potentially interfere with other programs function normally (wouldn't it?).

It's only required to un-throttle the CPU during the build.

However. If you're serious about audio production, you don't want the
CPU to be throttled while you're using the software. jackd can and will
have x-runs caused by throttling.

Unthrottling the CPU won't interfere with software functioning
normally. It might cause your fan to run all the time... if you're
using a laptop on batteries, it'll shorten the battery life. But, when
are you ever going to be doing audio production in a place that doesn't
have outlets to plug your laptop into?