I get pretty much 100% on my MAC without any module apart from the "Audio Interface". It seems the system is not yet optimized at all. Need to investigate the code a bit...autodafe wrote:I get nearly 90% CPU on the "Audio Interface" module simply connecting a VCO directly to the Audio Out
is that possible???
VCV Rack
-
- KVRian
- Topic Starter
- 960 posts since 27 Jun, 2009 from Germany
-
- KVRAF
- 8071 posts since 9 Jan, 2003 from Saint Louis MO
Andrew mentioned to me that the "Audio Interface" module shows idle time, not actual CPU usage.
On the ~2012 Macbook he was running the demo on, Elements instances took about 8% CPU.
On the ~2012 Macbook he was running the demo on, Elements instances took about 8% CPU.
-
- KVRist
- 234 posts since 24 Apr, 2004 from Patagonia
Thats what I was thinking, that would be idle but then the lapton started to sound like an helicopter because the fan, and checked that CPU was almost 100% even with no modules loaded (just audio device). W7x64 here.
-
- KVRian
- Topic Starter
- 960 posts since 27 Jun, 2009 from Germany
I was also referring to the system monitor, rather than the CPU meter of rack. But now it seems to have calmed down. Maybe it was related to an issue which is discussed on the github, namely hight CPU when no actual audio interface is selected.
Now, with a couple of modules playing, it moves between 60% and 130%. But then, my Macbook is not the newest. Will try my PC later.
Now, with a couple of modules playing, it moves between 60% and 130%. But then, my Macbook is not the newest. Will try my PC later.
-
- KVRian
- 1311 posts since 31 Dec, 2008
Generally speaking, I like what I'm seeing and hearing. After like a 10 minutes test. I do have many of those mutables and it's nice to be able to just hear them in the box without going to hardware. The main oscillators sound good, and I like that befaco reverb. There is a wealth of modules here.
I like what they've done with the interface. Though there are a couple of things that I would point regarding, stacking cables, puling cables and modules (scrolling) to reach hidden raws and stuff like that. But I think it is still too early to judge. This is the easy stuff, it shouldn't be a problem to sort out.
I'm not getting the 100% CPU that your getting guys. Using ASIO4ALL I get 32% (on task manager) on an empty rack (with one core almost maxed). The CPU usage increases slowly as you add modules but no drops. I think they are using multi threading because other cores start to work when you add more modules. I wouldn't say it's bad, for a beta, considering that lots of code has been ported from a completely different platform that was probably optimized for dedicated hardware.
One thing of interest to me is the block size. The minimum here says 64. Is that external (only for the audio module), or even internal? For highest fidelity, internal block size should be 1
I like what they've done with the interface. Though there are a couple of things that I would point regarding, stacking cables, puling cables and modules (scrolling) to reach hidden raws and stuff like that. But I think it is still too early to judge. This is the easy stuff, it shouldn't be a problem to sort out.
I'm not getting the 100% CPU that your getting guys. Using ASIO4ALL I get 32% (on task manager) on an empty rack (with one core almost maxed). The CPU usage increases slowly as you add modules but no drops. I think they are using multi threading because other cores start to work when you add more modules. I wouldn't say it's bad, for a beta, considering that lots of code has been ported from a completely different platform that was probably optimized for dedicated hardware.
One thing of interest to me is the block size. The minimum here says 64. Is that external (only for the audio module), or even internal? For highest fidelity, internal block size should be 1
www.solostuff.net
The 3rd law of thermo-dynamics states that: the 2nd law has two meanings, one of them is strictly wrong, the other is massively misunderstood.
The 3rd law of thermo-dynamics states that: the 2nd law has two meanings, one of them is strictly wrong, the other is massively misunderstood.
-
- KVRist
- 323 posts since 19 Jul, 2008
There are two issues of confusion surrounding the CPU usage.
1) Foosnark is right. The Audio Interface reports idle time, not actual spent CPU cycles. In other words, the Audio Interface does not contribute significantly to your fans blowing up.
2) When no audio device is selected in the Audio Interface, there is no idle blocking because Rack has no timing information coming from any device. So it simply "skips" the Audio Interface and blazes through a loop, iterating through 0 active modules at 100% CPU. This is a bug and will be fixed once I find a reasonable solution, but it is currently likely the reason for your fans taking off.
S0lo, that is the device's block size. Internally, there is a 1-sample latency between patch cables as you've guessed.
I should also mention that multiple Audio Interfaces with different audio devices is possible but experimental. I know of very few DAWs that can achieve this, and if they do it's a complicated process of setting up multiplexed / aggregate drivers. In VCV Rack, just add another interface, select another device, and patch between them.
1) Foosnark is right. The Audio Interface reports idle time, not actual spent CPU cycles. In other words, the Audio Interface does not contribute significantly to your fans blowing up.
2) When no audio device is selected in the Audio Interface, there is no idle blocking because Rack has no timing information coming from any device. So it simply "skips" the Audio Interface and blazes through a loop, iterating through 0 active modules at 100% CPU. This is a bug and will be fixed once I find a reasonable solution, but it is currently likely the reason for your fans taking off.
S0lo, that is the device's block size. Internally, there is a 1-sample latency between patch cables as you've guessed.
I should also mention that multiple Audio Interfaces with different audio devices is possible but experimental. I know of very few DAWs that can achieve this, and if they do it's a complicated process of setting up multiplexed / aggregate drivers. In VCV Rack, just add another interface, select another device, and patch between them.
VCV Rack, the Eurorack simulator
-
- KVRian
- 1311 posts since 31 Dec, 2008
Thats good to knowvortico wrote:S0lo, that is the device's block size. Internally, there is a 1-sample latency between patch cables as you've guessed.
.www.solostuff.net
The 3rd law of thermo-dynamics states that: the 2nd law has two meanings, one of them is strictly wrong, the other is massively misunderstood.
The 3rd law of thermo-dynamics states that: the 2nd law has two meanings, one of them is strictly wrong, the other is massively misunderstood.
-
- KVRist
- 234 posts since 24 Apr, 2004 from Patagonia
Thanks Vortico!
And congrats for your excellent work!! what a piece of beauty you made!!!
And congrats for your excellent work!! what a piece of beauty you made!!!
-
- KVRAF
- 1721 posts since 17 Jul, 2001 from Milan, Italy
Ok, 100% issue solved. it's just a but misleading since thebutton says "CPU usage"...I was suspecting it just because the synth worked very well...
I made a quick patch if you want to test it:
http://www.autodafe.net/tmp/QuasiMini.json.zip
It's been made on my MAC, tell me if you get issues (blank modules) when loading it on PC (I get blank modules when loadin it on my Win10 machine)
I made a quick patch if you want to test it:
http://www.autodafe.net/tmp/QuasiMini.json.zip
It's been made on my MAC, tell me if you get issues (blank modules) when loading it on PC (I get blank modules when loadin it on my Win10 machine)
-
- KVRAF
- 1721 posts since 17 Jul, 2001 from Milan, Italy
I tested it also on an old MacBook ruinning el Captain 10.11.6
Rack opens but the module grid is completely blank...no racks, no right click or ctrl-click.
Opening a patch created on my other mac, the modules have no knobs, no outs and so on, more or less the same problem I have when switching between mac/pc
Rack opens but the module grid is completely blank...no racks, no right click or ctrl-click.
Opening a patch created on my other mac, the modules have no knobs, no outs and so on, more or less the same problem I have when switching between mac/pc
-
- KVRian
- 931 posts since 23 May, 2010
Works and sounds great to me.
I don't see a way to route one output to multiple inputs (like in Softube Modular). Is that on purpose or not implemented yet?
Plugin support will be cool. Cheers.
I don't see a way to route one output to multiple inputs (like in Softube Modular). Is that on purpose or not implemented yet?
Plugin support will be cool. Cheers.
https://spektralisk.com/products | Sound libraries for: Massive X, Pigments, Vital, Razor, Kontour and more | Free sounds → Sound Flux
-
- KVRian
- Topic Starter
- 960 posts since 27 Jun, 2009 from Germany
You will need to use the multiple module. But having the option to stack cables would be a great addition...spektralisk wrote:Works and sounds great to me.
I don't see a way to route one output to multiple inputs (like in Softube Modular). Is that on purpose or not implemented yet?
Plugin support will be cool. Cheers.
-
- KVRian
- 964 posts since 21 Sep, 2013
Use the multiples module.spektralisk wrote:Works and sounds great to me.
I don't see a way to route one output to multiple inputs (like in Softube Modular). Is that on purpose or not implemented yet?
Plugin support will be cool. Cheers.
In fact, learn about each module (youtube will get you pretty far here).
On a side note, I'll buy upgrades to all of my older plugins if they start putting out "module" versions when they upgrade!!!
Very nice app!
Oh, and rumor has it that they're working on a plug-in version of it.
-
- KVRian
- 931 posts since 23 May, 2010
Thanks guys.
https://spektralisk.com/products | Sound libraries for: Massive X, Pigments, Vital, Razor, Kontour and more | Free sounds → Sound Flux
-
- KVRian
- 1498 posts since 21 Nov, 2005 from The Netherlands
Looks nice, but that's all for now on my computer. 
The application doesn't see an audio device, it does see all my MIDI devices.
Windows 10, 64bit, creators update.
PS: when logging in I can't paste my password.. It's randomly generated with quite some characters. Please add paste to the pw field.
The application doesn't see an audio device, it does see all my MIDI devices.
Windows 10, 64bit, creators update.
PS: when logging in I can't paste my password.. It's randomly generated with quite some characters. Please add paste to the pw field.
You do not have the required permissions to view the files attached to this post.