@LiquidProj3ct wrote:
@Zynewave wrote:
Added “bypass processing when detecting CPU overload” option to preferences. Disabling this option can result in smoother playback, but with a more sluggish UI when CPU overload occurs.
I was thinking that there is a third method. FL Studio, my old host, could reserve a minimal CPU time for interface handling in case that overload occurs. That was very useful, because sometimes you cannot press the stop button even. Anyway I will test this later when I come back.
Tested. I’ve posted the answer here 🙂
http://www.zynewave.com/forum/viewtopic.php?t=1882&start=45
Edit: And I’ve see that GUI doesn’t freeze when CPU is overloaded. Maybe you should turn off that option by default, so those people as me with problems in their PCs could see that Podium is CPU friendly also.
@Zynewave wrote:
The tempo event properties dialog now has controls for setting up a scale. There is a combobox for selecting among common scale types and a comboxbox for selecting the tonic. Custom scales can be configured using the 12 note buttons. Tempo events configured with a scale will show the scale name on the tempo event lane. The piano roll editor will highlight note rows that are in the scale.
Added “highlight scale” option to the piano roll properties dialog.
Impressive 😯 . Really Impressive. I’m testing this feature now and I really like it. Very few host can do the same. But none of them can setup the scale as easily as Podium. This could be the best piano roll in the market, I’m really in love with Podium Piano roll. I knew you was doing a big work and I really surprised. Congrats man :D. This feature would deserve its own KVR thread 😉
@Zynewave wrote:
Added “editor mouse snap mode” setting to the Preferences dialog. Options are “grid line closest to cursor” and “start of grid unit under cursor”.
Now that I can test both methods, I like more the grid unit under cursor, it’s more comfortable for me.
@Zynewave wrote:
Added “drum map region properties” shortcut to the drum map right-click menu.
Good idea, more consistent GUI
@Zynewave wrote:
Added “bypass processing when detecting CPU overload” option to preferences. Disabling this option can result in smoother playback, but with a more sluggish UI when CPU overload occurs.
I was thinking that there is a third method. FL Studio, my old host, could reserve a minimal CPU time for interface handling in case that overload occurs. That was very useful, because sometimes you cannot press the stop button even. Anyway I will test this later when I come back.
@Zynewave wrote:
Any other uses for scales?
Maybe an action or scale option that forces a group of selected notes to a scale, by example when you drag them.
Best regards 🙂
@Zynewave wrote:
I’ve added a “bypass processing when detecting CPU overload” option to the preferences dialog. When you disable this option, it will not mute the plugins when CPU surges occur. The UI may become sluggish if the CPU overload is sustained over a long period. The CPU indicator will still flash red to indicate that you most likely had a glitch in the audio output.
Ok, thanks, I will try that option when you release the next beta and I will give you some feedback about this subject again. 😉
Yes, I’m using the same drivers in the three systems (I only have one ASIO device).
Frits, is posible disable the auto-mute when CPU is overloaded? It would be pretty useful in systems as mine, as I’ve seen with DPC Latency Checker, thx DFusion.
Best regards
I have the buffer to the maximum. I’ve disabled anticipative also, and yes, I can run 6 gladiator instances with few glitches (and not 7). But I can run six, where in Podium I can run three only. Same in Orion, I can run six instances.
Anyway you can see as Podium doesn’t use the full potential of my CPU (see the perfomance graph above).
Anyone can confirm this? maybe is a hardware problem?
Best regards
@Zynewave wrote:
Popular topic 😉 . Let’s get to the bottom of this.
@LiquidProj3ct: Can you please email me your Podium and Reaper project files, so I can test it on my system.My guess is that the improved performance you see on Reaper, is related to the “anticipative FX processing” option in Preferences/Buffering. You get better CPU utilization at the expense of larger latency response to realtime changes in plugin editors etc.
Sent!
However I don’t think that anticipative fx processing be so powerful. Orion can load 6 instances of Gladiator2 and its CPU usage in both cores are about 87% here. Reaper can load 7, due to anticipative.
Best regards
@DFusion wrote:
Could you please post screenshots with the taskmanager set at Rendimiento instead of Procesos so we can see the load graph instead of numbers.
It’s funny see you writting spanish 😆
Of course, here you’re:
Podium, 3 Gladiators, take one, just before audio will be interrupted:
Podium, 3 Gladiators, take two (different take), just after audio was interrupted because CPU meter reach its maxium
Reaper 3 alpha 2b, 7 Gladiators, you only hear a few minor artifact (very few), CPU it’s working at 90-100%
@DFusion wrote:
Hmm. that is weird.
To me it looks like you have Multithreading enabled in Reaper but not in Podium.
I have it enabled in Podium also:
Btw. where have you got that cool dragon background?
Click here for download it:
Thx Conquistador I’m gonna read it.
However I can play 7 Gladiator tracks (4 voices chords each) until CPU overload (and I get audio glitches) in Reaper, 6 Gladiator tracks in Orion, and 3 in Podium.
Similar results with Sylenth1.
Yes, same here. Podium is using about 2x CPU or more that Reaper/Orion with same settings, but task manager doesn’t reach 50% of CPU usage (when it reach 50%, Podium CPU Meter is at 100% and it mutes it output).
I’m on a intel dual core.
I forgot say that when the meter reach 100% the output is muted (but windows task manager hardly reaches 50% 😯 ) and, although you press STOP the meter doesn’t descend
Best regards
EDIT: This has been tested with Gladiator2 and Sylenth1. It seems that Podium doubles the normal CPU usage.
I got Firebird+, Warmverb and Gladiator2. All of them are legit, and all of them phone home… I’ve complained several times to Markus, because this crash all the host I’ve tried… it’s a pain
I think the problems should be fixed before future improvements, I had problems with this too
Best regards 😉