Zynewavethe other day the cpu meter went down to -1000
Are you running Podium on a Cray supercomputer? 😮
Did it write -1000% in the CPU indicator? Were you doing anything when it happened?
ZynewaveHi Peter,
it seems like it’s not possible till now.
Correct. You can however use the ctrl+arrow left/right keyboard shortcuts to move the events along the timeline without loosing the relative snap offset.
‘Relative-snap option’ is now added to the future developments list.
ZynewaveIf the parameter was a plugin parameter, then the value should go from 0.00 to 1.00. Is that what you mean? If the parameter was a MIDI parameter then the value by default goes from 0 to 127. You can change this in the properties of the parameter, by adjusting the value range settings.
ZynewaveNoted.
ZynewaveWhen will the offline bouncing function be released?
I have not set a deadline for this. It will not appear for at least a couple of months.
ZynewaveHowever, I find it drops notes quite often
This is because the randomized note end of the previous note overlaps the randomized start of the next note, and so the note off will cut the next note event short. There need to be a certain amount of space between repeating notes. There is a small note about this in the guide.
some links appear to be wrong in the installed version of the Podium guide
Thanks, I’ll get those sorted. I’m doing some writing on the guide currently.
ZynewaveZynewaveBug-fix version 1.36 is released. I’m locking this topic to keep the release topics in chronologic order. Please post your comments about 1.35 in the 1.36 topic.
ZynewaveThree reproductible crashes for me, with the project I have sent you last time :
– when switching from the second screen view (full arrange) to the first one (arrange on top and edition window below)
– when dragging the track separator to the right to make it wide
– when show / hide the Inspector. The crash occurs only in the big arrangement (“Peintures Noires”).
DOH! 😳
All three crash-situations you describe are caused by the same bug. Part of the optimization involved using a cache of the painted waveform, instead of extracting the waveform from the sound on every paint. Unfortunately this cache is not reset when you change the horizontal width of the tracks area, causing invalid memory access. Bug-fix version will go up later today.
ZynewaveZynewaveThe bounce recording is captured at the output of the track, to free all audio processing occurring at the track, including any gain and pan settings and automation of these. This is indicated by the dimmed gain and pan texts when the bounce file is activated.
If you want to gain control a bounced track, then you have to wrap it in another audio track, as you have done.
ZynewaveThere is a marker named ‘Chapelets’ at the end of the blank part of your arrangement. If you delete this, the maximum zoom will shrink to your sequence events. You have to zoom out a little to see the marker event. Alternatively you can switch to the event list profile, and find the marker at the bottom of the list.
ZynewaveZynewaveHi,
The zoom bar in the right pane of the window is a display scale zoom. It does not change the relative track heights, which you set by dragging each individual track. This makes it possible to quickly zoom out so that all tracks are at their minimum height, and zoom back in again without disrupting the relative heights of the tracks. In the first arrangement in your project file, it seems that you had set the zoom out to maximum, and then dragged the height of the tracks. Thus when restarting Podium (or by setting the track zoom to default by control clicking the zoom bar), all the tracks will be huge.
I’m going to revise this behaviour the coming days. The next release 1.35 will save the zoom settings of each arrangement in the project file.
ZynewaveFor the end of 2006 perhaps ?
Sounds about right, if I’m going to process your other requests first 😉