ZynewaveI held ctrl+alt leftmousebutton and then I moved the mouse in order to zoom out.. The zoom-out was very fast and then the program crashed
I couldn’t reproduce the crash here, so it could be something related to the contents of your arrangement. If you are able to reproduce the crash frequently, then email me the project file.
ZynewaveI can’t tell what you’re doing wrong from your description. Email me the project file and I’ll have a look.
ZynewaveMy project just crashed a few minutes ago
You mean Podium crashed? When this occurs, please try to remember what you were doing before the crash, and try to recreate the crash scenario. Otherwise I have no chance of fixing these bugs.
ZynewaveEnter the properties dialog for the parameter. If it is a plugin parameter, the value range should be set to 0..0. This means that the internal floating point resolution of the VST parameter is used. If you change the range settings to an integer range such as 0..127, then Podium will convert the internal floating point range of the VST paramter to this integer value range when writing parameter values in the curve editor and on the mixer sliders etc.
This will only work if you are certain that the VST parameter in the plugin editor is actually using the range 0..127. The normal floating point resolution of VST parameters has a much higher resolution. The 0.00 to 1.00 range that Podium displays is a rounded value.
Also note that when the value is written as 0.00 to 1.00, this represents the full value range for the parameter. Changing this to a range of 0..127 will not increase the range.
ZynewaveWas the ‘-1000%’ accompanied by a red flash in the indicator and a drop-out in the sound? For how long does the -1000 remain in the indicator?
ZynewaveI’ll bypass the VSTi and wait a few minutes to see if the spike is gone.
You could also try to increase the ASIO buffer size. A low CPU usage and occasional CPU spikes is a typical problem with very low ASIO buffer settings. When the buffer size is small, there is a greater risk that timer critical events in the OS or application can disturb the ASIO buffer processing. What soundcard and what latency are you running currently?
ZynewaveI moved my Podium directory to another hard drive, perhaps that has something to do with streaming from my second hard drive..
Moving the Podium program or the project folder should have no effect on this. If you moved the plugin files, then there can be problems if they are using disk-streaming to play the samples. Does the spikes occur only when you play notes on your keyboard, or can they occur when you do nothing and the plugins are silent?
Try bypassing either the Grand or the Sampletank plugin and see if that removes the spikes.
Zynewave@Podianer wrote:
Today I found Podium acting the same way.. Irregular cpu spikes.. My samplerate and resolution are 44KHz and 16 bit.. Average CPU use: 15%.
Not sure, but I think this behaviour is new since I use 1.36…
I need more details. Are you using plugins? Does it happen only during playback? When the cpu spikes occur, does the Podium CPU indicator go red and jump to 100% and then fall back down to 15%?
If you’re using plugins, try bypassing in turn each plugin, until the CPU spikes stop. If you find a plugin that is causing the spikes, then try changing to another preset.
There is nothing new in the 1.35/1.36 releases that should cause these problems. On the contrary, the optimized graphics should reduce the chances of spikes.
Zynewave@Zynewave wrote:
I’m sure this has worked before, so it could be a bug introduced with the latest release.
I stand corrected. This bug has been there since the auto-extension feature was introduced in version 1.26.
ZynewaveHi Alan,
Thanks, and welcome to the forum 🙂
ZynewaveOk, I’ve managed to recreate the bug on my system now. I’ll fix this for the next release. I’m sure this has worked before, so it could be a bug introduced with the latest release. Thanks for reporting it.
ZynewaveIt appears to be happening when the audio event is extended by the recording. If you start by dragging the size of the audio event to the desired length of the recording, and then start recording, does the gaps appear then?
ZynewaveHi Eli,
Are the gaps approximately 1024 samples wide? If you change the latency setting on your soundcard, does the gaps change?
– ASIO sample position gaps: 1 (1024)
This entry concerns me. It means the ASIO driver jumped forward in time, which could explain the gaps in your recording. The report you listed was only measured for 14 seconds. If you measure over a longer period, such as the time taken to record the sound in your screenshot, does the gaps count increase then?
Zynewaveanyone knows how soon this will be ?
No deadline set yet. For the next few releases I intend to work on some of the minor things that have been requested.
ZynewaveI’ve added ‘New ‘bypass mapping’ mixer parameter.’ to the future developments list.