ZynewaveThe maximum group level limit is a UI restriction only. I’ll increase it just slightly. I would like to keep a max limit, to avoid abuse. It e.g. affects how the mouse behaves when you drag a track to set the group level.
When I get around to implementing device wrapper mappings, there will be less need for creating deep multiple nested plugin tracks.
ZynewaveI’ve noticed that when I change some curves in the embeded editor (volume for example) while playing, the values are not send to the audio until a restart of the play ?
The engine prepares playback approximately one second ahead of time, so if you change events just slightly ahead of the play cursor, the changes will not be heard in the playback.
It seemed to be solved in the floating editor ?
There should be no difference on this behaviour no matter if you’re using embedded or floating editors.
Also, the audio is “muted” when changing the length or splicing an audio sequence until a restart of the play too.
It will be nice if it don’t affect playing…
Yes, this is a problem I will fix at some point.
Zynewaveif I’m quantizing to 1/8ths, but click in the 2nd 16th note division, I’d expect the note to be quantized to the 1st 8th note position. However, the note created is actually quantized to the 2nd 8th note.
I was not aware that other hosts commonly always truncate. It just feels natural to me, that painting a new note with quantize snap on will snap it to the same position that you would get if you painted with quantize snap off, and then selected the quantize edit command. I originally implemented the truncation method, but it frustrated me that clicking just one pixel to the left of the gridline would paste the note at the previous gridline. I always try to hit gridline that I want to place a new note at, even when I have quantize snap on. Also the cursor display in the top toolbar will show the note position that will be snapped to, with a -/+ percentage deviation.
it’s streamlined my workflow like you wouldn’t believe! Great job!
Thanks 🙂
ZynewaveYour post is added to the bottom of my evergrowing acousmod-requests.txt file 😉
It will be a day to celebrate when this list is empty. And when it is, I’ll raise the price of Podium to 1000$ 😛
ZynewaveGood points. I’ll think about an alternative splice functionality.
Another thing : I have not seen any possibility to add an embeded editor in the Profile Properties, like for the Mixer.
My purpose will be to have TWO editors : one for the MIDI sequence and one for the MIDI curve controllers (like in the old Cubase’s Key Edit, at the place of the velocity zone).
You can only have one embedded editor, and it is linked to the tracks region. If you want to show multiple sequences simultaneously, you can open separate editor windows.
ZynewaveI am splitting a clip and getting a click in between when playing back, any fix for this?
Yes, in the upcoming 1.34 release 🙂 I’ve had this on my notepad since lalo brought it up.
This bug could also be the cause for your recording click. Please notify me if this problem remains in the 1.34 release.
ZynewaveI often run into this when demoing various synths. It is normally caused by a few badly designed presets, and changing the preset should make it return to normal. If not, then try reloading the plugin (switch the monitor button in Podium off/on).
Frits
ZynewaveThe problem was that you had mapped your three mixer send/return pairs to the same mixer bus instance, only offsetting the channels. That is why it is feeding back into itself. You just have to use separate mixer bus instances, and you won’t have this problem. In fact you only need two send/return pairs to do what you want. I have modified your project file and sent it back.
ZynewaveHi Joachim,
This sounds like an interesting experiment. I’ve read and reread your post, but still don’t have a clear picture of how you have routed the signal. Could you email me the project file, or a screenshot?
ZynewaveIs it only when auditioning files that you get the stutter? Is normal Podium sequence playback of a VSampler instrument working? If not, does it help if you close the plugin editor window?
I googled for ‘VSampler crackles’ and found an old user-review of VSampler on kvr that mentioned he got crackles, if the editor window was open.
ZynewaveThe four screenshots on the zynewave.com home page have been updated to show the new layout.
ZynewaveI got the spikes and crackle, and I got rid of them by increasing the ASIO buffer size. What ASIO latency are you using?
The CPU spike is occurring because the plugin audio processing is doing something heavy when starting a sample playback. The crackles appear during the sample playback, but they are not accompanied by CPU spikes. That means it is the internal sample loading within the plugin that cannot keep up with the audio streaming. You can hear that by the stuttering and apparent slow down in sample playback speed. I tried adjusting the idle calls that Podium sends to the plugin, but this had no effect. Try increasing your ASIO buffer size.
Frits
ZynewaveZynewaveI’ve installed VSampler, and tried it briefly. I did not manage to quickly find the window you described. I found an ‘import wav’ command, that allowed me to select a folder with wavs. Somehow I managed to make the plugin pop up a crash dialog. I would rather not spend time on learning this plugin, as it seems to have a lot of features. Could you describe step by step what I need to do after loading the plugin on a track?
ZynewavePerhaps do you know how to invert the order ?
I don’t know. You could try emailing RME support. They should be able to give a quick answer to this.
But will it be also complicated to only remove the outputs that are not selected from the bus ?
Yes, and I don’t think it is a good solution. Some users may have e.g. connected an effects device to SPDIF, and created mappings to those channel numbers. If the user then later on enables/disables some of the previous analog channels, he would want the SPDIF mappings to remain on the same physical channels.
What is the use of this selection if it doesn’t remove them ?
Unselecting audio interface channels will make Podium skip those channels in the engine, and thus saving CPU resources.