ZynewaveZynewaveZynewaveZynewave@swindus wrote:
When I create a new arrangement with a new midi track with a VST instrument and a new sequence with midi notes and then select the half length of the sequence for the punch range Alt+B renders the complete sequence/track.
After undoing the bounce and enabling the record mode Alt+B renders the punch range.
From this point on Alt+B renders the punch range without enabling record mode. So it seems that the punch range rendering does not work correct on e new track/sequence without enabling the record mode at least once(?).
Thanks, I’m fixing this currently. It was a problem when using the Alt+B key shortcut, when the track was not already bounce enabled.
ZynewaveI’ve updated some of the guide chapters with the 2.36 changes. I’ll do some testing tomorrow, and if no new bugs appears, I’ll probably release 2.36 in a day or two.
Zynewave@thcilnnahoj wrote:
@Zynewave wrote:
– Enabling bouncing on a track doesn’t show the B button on the mixer strip, so you can’t see its state there.
The new Bounce button in the effect chain should show the bounce state. Unless the effect chain is hidden, the redundant B button is hidden to save vertical space. Isn’t it enough with the bounce indicator in the effect chain?
Hmm, I guess, though it’s not as clear that a track is configured for bouncing when the only indication is an effects slot, compared to the aligned B buttons. You also can’t use key shortcuts the bounce selectors, it seems. Edit: Missed the post about the bypass buttons. I usually don’t use them, though…
I’ve changed it so that the ‘B’ buttons only disappear if the “show bypass buttons” option is enabled.
Zynewave@LiquidProj3ct wrote:
Maybe it’s in your plan already, but the same shorctus you use for effects slots (Shift-Click to bypass, Alt-Click to delete) should work in the bounce slots.
Alt+Click will unassign the device mapping on a track. It does not delete the track. The bounce track does not have a device assigned, so I’m not sure if Alt+click would make sense there. Likewise, there is no device to bypass.
Note that if you select the “show bypass buttons” mixer option, a “B” button will appear instead of an “X” button on bounce tracks.
Zynewave@thcilnnahoj wrote:
– If a track doesn’t have any effects, the bounce track is created on the parent track instead of the selected track, and nothing is rendered.
Fixed in the new beta8. It was a last minute code change that I forgot to test.
– Enabling bouncing on a track doesn’t show the B button on the mixer strip, so you can’t see its state there.
The new Bounce button in the effect chain should show the bounce state. Unless the effect chain is hidden, the redundant B button is hidden to save vertical space. Isn’t it enough with the bounce indicator in the effect chain?
– Another one, not related to 2.36: Using Ctrl+C&V on a track in the mixer doesn’t copy the track (even though it’s set as active selection in the mixer) whenever a sequence or tempo/marker event is selected as well. It copies the sequence (which only has inactive selection) instead.
I’ll fix that.
ZynewaveBeta7:
Bounce enabling a track will now create a dedicated bounce track in the effect chain, instead of enabling bounce mode on an existing effect track. The bounce track will show up with a “Bounce” button in the chain, which can be clicked to open the bounce menu. The bounce extraction point can be set by dragging the bounce track up or down in the chain.
MIDI channel reset messages are now only sent to MIDI interface channels that have previously been used. This greatly reduces the total number of reset messages sent on playback start.
ZynewaveTry the new 2.36 beta7. The reset messages are now only sent to MIDI channels that previously have received MIDI messages.
ZynewaveZynewavePodium sends the “all notes off”, “reset all controllers” and “all sound off” control change messages to each MIDI channel. That’s 8 ports * 16 channels * 9 bytes = 1152 bytes. Quite a lot when the MIDI transmission speed is about 3K bytes per second. The MIDI server operates at a high priority, so that can explain why it is stealing time from the audio driver. I could optimize this, so that only the channels that are actually used on the tracks will be reset.
Can you get rid of the crackles by increasing the ASIO buffer size?
ZynewaveI searched, and I assume you mean this discussion:
http://www.kvraudio.com/forum/viewtopic.php?t=276414&start=0
It appears the crash also occurs with Reaper, and that the developer is looking into the issue.
ZynewaveI’ve noted that down for a future update to the curve editor.
ZynewaveWhich Podium version number, and which VAZ Plus version number?
I’ve previously experienced stability issues with VAZ Modular, so perhaps VAZ Plus has the same issues.
If you can reproduce the crash with other plugins than VAZ Plus, then it is likely a Podium problem. Otherwise it is likely to be a problem with the plugin. Try to replace your VAZ Plus with another instrument on the track, and repeat the automation procedure you used to make VAZ Plus crash.