OK, so the audio module is finally installed, and connected as shown in the image. Still no sound, so I’m also uploading some logging info from qjackctl. Thanks for spending all this time with a noob like me.
Show the qjacktcl connections window.
Also what is plugged in to the mixer? Doesn’t look like anything is passing through it.
Your jack log is ok but it looks like you’re not running a lowlatency kernel or haven’t set something up somewhere, run the quickscan I linked above and it will tell you. Post the output here in fact.
The MIXER IN1 signal is coming from the VCF LPF out, in a conventional VCO->VCF path governed by an ADSR gated from LFO-2. (At least I hope that’s what’s happening… 8^) seriously, it would be hard to believe I’d committed any patching errors as basic as that.)
I’ve attached the output of a real…scan.pl. Looks like a neat tool I’ll come back to more than once.
We have ignition. As of yesterday afternoon. I followed David’s link to the “Linux Audio Survival Kit”. With a little more fiddling, started to hear things from VCV-Rack.
Naturally there are a bunch of lessons for me in reflecting on the path I took through the past 4-5 days. I should have begun with a couple of hours of youtube video clips on the subject. Instead, I wasted a good deal of time – mine and yours – thrashing around in my own ignorance.
Anyway, I guess I’m ready for the next phase. Thanks to everybody who contributed here.
“Next phase” = detailed examination of each module, with notes on its behavior, and how that behavior differs from that of an equivalent analog function.
Oops: my audio connections are still behaving erratically.
I’m seeing a red vertical bar on the left side of AUDIO-8, and a sky-high cpu usage.
This persists even when I ctl-E disable all the other eight modules.
There’s something I’m still not getting about JACK connections. I’m uploading a couple of screenshots.
The audio was fine. No problem. But I figure that if the 90% load remains with all the audio processors disabled, it must originate in something funny in the Jack patching.
I’ll experiment with specifying 4 or 6 or 8 threads, instead of just one. Reading about “CPU timer” suggests that I was overreacting to the red bar and the 90% usage value.
The red bar on the Audio module is the percentage you have left to work with measured in ms. The red bar on each module is how much it’s using. A lot of people misunderstood this to begin with.
Why does the survival kit currently suggest to build Rack from sources rather than downloading the binary? Are there any practical advantages? (or is it just not up-to-date?)
it is a kind of random tutorial for new linux users, I started installing repositories, then, software from the repo, for a downloaded .deb, a .sh from the command line, and finally compiling, but it could have beed how to compile a Zynaddsubfx, or a vcv rack plugging.
but there are some reason to compile a software by yourself,for instance, you can have and try the last version of the software (at this point it is not necessary since the v1 have no new release ), or to make the software perfectly fit to your hardware or to enable an special feature, like jack in the v0.5 and so on.
I will rewrite these, I should do for the v2, for now the leonardo’s guide is the best