Bug found. It turned out to be related to the preset system changes introduced in the latest release. I’ll make a bug-fix version tomorrow.
Thanks for pointing out this bug to me.
I tried with Cygnus, and I was able to get pops with low latency setting. I’ll examine what causes this. The pops are only present during playback, and not while auditioning the synth live with MIDI in. Do you get pops when auditioning synths?
Do the pops occur with all your plugins or just the three you mentioned? If you bounce render offline, are there any pops in the bounced audio file?
oh if i record manually it seems to fix it
When you say manually, do you mean real-time bounce recording as opposed to offline bounce rendering?
I downloaded and tried the Rapture demo. It does indeed seem to handle VST program naming in a strange way. Fair enough that it only exposes one VST program in the bank, but to me it seems like a bug that whenever you choose a ‘prog’ preset in Rapture, the VST program is overwritten with “C:Program FilesCakewa”. Once I had selected a ‘prog’ in the Rapture browser, I did manage to use the Podium ‘name…’ button to give the VST program a sensible name. This would stick until you selected another ‘prog’ in Rapture. Using ‘name…’ however caused the Rapture UI to show ’empty’ in the preset name field. Weird behaviour.
@darcyb62 wrote:
If we had previously done a full import of plugins in a project do we have to redo this for that project to use this new structure?
Using ‘scan and import’ will not upgrade your existing projects. I recommend you try out the new preset system in new projects only. Otherwise you would need to do a lot of copy/pasting to move your old program and library presets to the new folder structure.
This bug seems to have been introduced in a recent version of Podium. when editing note attack velocities, the “hotspots” for each note are offset by half. If you click on the righthand side of a bar, it edits the attack velocity for the note next to it instead of the note you clicked on.
This happens because quantize snap is enabled, and the quantize value is longer than the notes you try to edit. Are you sure it hasn’t always been this way? But I think you have a point there. There is no need for the mouse tools to snap in the velocity editor. I’ll fix it.
Next time it happens, try the following before exiting Podium:
Try switching monitoring off and on. If this does not help, try opening the MIDI/audio interfaces dialog and press OK. This will restart the audio driver and reset the internal sample position counter. Let me know if any of this cures the problem, as this will be a clue to where the bug is.
I have to say it would be great to know exactly what the time frames are for certain features as it would be very useful to know…but I think from Frits point of view, giving a timeframe and not sticking to that timeframe may rightly lead to needless problems.
I know that a precise road-map would be ideal, but this is difficult to achieve. Requests for a certain feature may suddenly surge, and problems may arise that needs to be fixed. There have been many examples in the past where discussions on this forum has led to several weeks of work on usability features that was not previously on the road-map.
I also read a lot of posts on e.g. kvraudio.com where people complain that promised features for various products did not arrive within the time originally announced. I don’t want to put myself in that position. I try to remove as many stress-factors as possible from my daily work, and that includes not having to wrap up features for a certain date. The promise of quality and stability in the development requires that I can put on the extra time if I discover that a certain feature is more complex than anticipated.
@francois wrote:
There are at least 2-3 major features that are higher on the list
can i know them , or its a surprise 😳
Coming up in next release is automatic plugin preset storage. The other major features are those that have been talked about for a long time on the forum. This is things like fade-in/out of audio events, optimized disk streaming, completion of the Podium guide and creating new example projects with a couple more z plugins.
Do you have already a planning for midi remote control , because i am planning to build a magic box to pilot podium in the recording functions…
It’s on the plan, but I have no time estimate. There are at least 2-3 major features that are higher on the list.
Could you please describe in greater detail how you want to this work? Should the index be added to the object name?
