VCV Rack

[ThomasHelzle]

I still get the one-core-fully maxed out on my system with 0.4 and only a midi in/audio out loaded.
(Windows 8.1 x64, 6 core i7 3930K Cpu @ 4.1 Ghz, 64 GB RAM, Geforce GTX 980 TI, Focusrite Scarlett 18i20 first gen, all with up to date drivers etc.).
So it's not really usable here, I get crackles even from the most simple setups.
All my other audio software works great.

I also have to say that finding/downloading all the 3rd party plugins again after each update is a bit of a pain. Would be great if plugins would be usable at least for a couple of versions.

The integrated Plugin-Updater was unable to overwrite the old existing plugins here. It downloaded them each time I clicked the button in the interface but didn't manage to overwrite them. I had to delete the old ones manually, then it worked.

Cheers,

Tom

[prohozhii]

What makes you think that? Did an error message suggest something like that?

I think this is because images are not only displayed in vector format. SVG. The format .PNG is displayed normally. The problem is exclusively with the display of .SVG. There were no errors.

[vortico]

Here's a list of all the plugins, their versions, and a link to compiled binaries.
https://github.com/VCVRack/Rack/wiki/List-of-plugins

@prohozhii: That's because your computer doesn't support framebuffers, or maybe it does but Rack doesn't know how to enable them.

[prohozhii]

@prohozhii: That's because your computer doesn't support framebuffers, or maybe it does but Rack doesn't know how to enable them.

How can this be remedied?

[RPH]

I still get the one-core-fully maxed out on my system with 0.4 and only a midi in/audio out loaded.
(Windows 8.1 x64, 6 core i7 3930K Cpu @ 4.1 Ghz, 64 GB RAM, Geforce GTX 980 TI, Focusrite Scarlett 18i20 first gen, all with up to date drivers etc.).

Which audio device driver are you using, and have you tried others?

When I just insert an audio device ( no device ) and MIDI device module, my CPU barely shows CPU usage, but when I change from no device to ASIO from my Behringer usb interface 1 core shoots up to about 75%.
M-audio delta ASIO is even worse, 90% CPU usage on one core.
Windows Directsound and others like MME or WASAPI show a more even distribution to about 40% per core.

Think best for my system is the MME driver.

CPU: Core i5 6600k

[ThomasHelzle]

I still get the one-core-fully maxed out on my system with 0.4 and only a midi in/audio out loaded.
(Windows 8.1 x64, 6 core i7 3930K Cpu @ 4.1 Ghz, 64 GB RAM, Geforce GTX 980 TI, Focusrite Scarlett 18i20 first gen, all with up to date drivers etc.).

Which audio device driver are you using, and have you tried others?

When I just insert an audio device ( no device ) and MIDI device module, my CPU barely shows CPU usage, but when I change from no device to ASIO from my Behringer usb interface 1 core shoots up to about 75%. M-audio delta is even worse, 90% CPU usage on one core.
Windows Directsound and others like MME or WASAPI show a more even distribution to about 40% per core.

CPU: Core i5 6600k

I was using ASIO, but the other options don't seem to make any difference for me.

[sramsay]

Forgive me, but I seem to be the dumbest person here. How do I get non-Fundamental plugins to load? I select them on the website, I log into Rack, I press "refresh plugins," it looks like it's downloading . . . and lo! I have various directories for these new plugins.

But I can't load them. When I right click, I just see the fundamental plugs.

Mac 10.13, Rack 0.4.0, but honestly, I feel like I'm missing something blazingly obvious here . . .

[GaryG]

@sramsey - I think there could be a problem with the plugin update in 0.4, it went through the motions as you described but all I had in my plugins folder was three 25 byte zips that couldn't be opened. I manually DLed the plugs and they worked fine. Auto-dafes modules too. This is on Windows 10.

Besides that, all working fine, love the stackable outs and submenus. Thanks!

[vortico]

Sounds like you're doing everything correctly. Could you run the command

Code: Select all

/Applications/Rack.app/Contents/MacOS/Rack

in the Terminal and email me the debug information that it spits out? contact@vcvrack.com

[sramsay]

@vortico - Actually, I just ran the program, hit refresh plugins (again), and they all showed up. Really don't know what happened, but it now appears to be working fine.

[vortico]

Ah, you were probably experiencing the issue I fixed 2-3 hours ago. The server was giving these corrupt zip files to a few select users, but it should be fixed for everybody now.

[sramsay]

Ah, thanks. This thing is awesome, btw.

[vortico]

@prohozhii: That's because your computer doesn't support framebuffers, or maybe it does but Rack doesn't know how to enable them.

How can this be remedied?

If I had access to your computer, or another that was having the same issue, I could probably fix it. Otherwise, there's not much that can be done.

[lnikj]

Hi Andrew. You participated in the discussion the other day about the difficulty in distributing a modular synth over muliple cores but I wondered (as a clueless non-programmer) if there was any mileage in distributing the graphical load of VCVrack across multiple cores.

There's an easier fix: Cache all graphical elements in framebuffers. It requires about twice as much video RAM (~200-300MB instead of 100-200MB) but avoids redrawing a lot of the elements on every frame. It'll take a few months for that to be worked on though.]

OK. Understood. No worries.

I'm managing fine in the meantime as I have an iMac too - which I've been in front of half the night madly patching

[blakecasimir]

I bet no-one else noticed this. I renamed RACK.EXE to VCVRACK.EXE because I wanted to make it less generic sounding in my list of audio programs... and that causes none of the modules to appear in the right-click menu. Upon renaming the executable back to RACK.EXE, all modules appear. Odd.