ZynewaveI’ll take a look next week, after I have completed the current release.
ZynewaveZynewaveIt appears to still happen with the latest 0.88 Karma beta. It does not happen when I run Podium in debug mode, so it is hard for me to examine what is going on. I have not seen this behaviour with any other plugins, so I’m guessing the Karma synth is doing something that causes this.
Since it’s still called a beta version, I’m assuming there are some issues with this plugin that KarmaFX is working on.
ZynewaveAre you using the latest KarmaFX release? I haven’t tried the latest version myself, but I had this problem with an earlier beta version:
ZynewaveOops, forgot:
In the sustain parameter properties you also need to set the value range from 0 to 127.
ZynewaveAre there really vst-plugins with parameters which have 7bit resolution?
If you have a VST parameter that is used to select e.g. 5 different filter types, then the values stored in the plugin and sent to the host would typically be 0.00, 0.25, 0.50, 0.75, 1.00. The plugin would of course accept values from the host in the entire 0.0 .. 1.0 range and just round to the nearest valid value. In this case, defining the parameter in Podium as having a value range of 0 .. 4 would make it easier to read and set the quantized value, thus avoiding an infinite resolution value dial.
ZynewaveYou need to set up a sustain MIDI parameter in the device you’re controlling. I assume it is a plugin. Here’s how to do it:
Using the project browser, go into the Devices folder, locate the device definition for the plugin, and enter the MIDI Parameters folder within. There should be three parameters. Select the ‘New Parameter’ menu. Name it ‘Sustain’, change the CC number to 64 (64 is the standard CC number for sustain).
When you record enable your track with the plugin, and start recording, then using the Sustain pedal should automatically create a Sustain parameter automation track.
ZynewaveI’ve been looking for an explanation of this bug. This may be a bit far-fetched, but do you by any chance keep your PC turned on for days, without using shut-down? And I mean shut-down and not stand by.
ZynewaveZynewaveI’m currently revising the CPU detection mechanism.
ZynewaveIt was glassverb that caused the spike when I added it, it did’nt do it sraight away, it was after the plugin appeard to stop producing sound
Are your PC running a Pentium 4 processor? This could be the dreaded denormalization issue. This can occur when sound dies out and the plugin thus need to process increasingly smaller numbers. Most plugins have been coded to reduce this problem, but often there will be a slight variance in CPU usage when the sound goes silent.
Zynewavejust put 0-127 instead of 0.00 1.27, will this work O.K.
Yes. You can only enter integer numbers for the value range, so 1.27 is a no go.
ZynewaveI was just wondering if you would prefer sugestions concentrating on how to develop things that already exesist in podium or whole new ideas
I have plenty of feature suggestions to work with for at least a year. What I would appreciate to know about is bugs and minor things that people find confusing or annoying.
ZynewaveThat sounds like a lot of trouble just to email me a project file. Perhaps we can manage without going that far. So you’re not using any backup of your harddrive files? How about getting a usb memory key? A 128MB key can be bought for maybe 15 dollars these days.
ZynewaveI don’t no if this can tell you anything or not just thought it may be usefull to know.
Thanks. This kind of information is very useful. I’m currently looking at improving the CPU usage detection and indication.