Thanks!
Looks like a FXpansion problem. For me it’s not Geist but Cypher from the DCAM Synth Squad wich causes the problem.
Yes, I noticed this too. I’m on Vista 32bit.
Open the sound event in the editor, select all and choose normalize from the edit menu. Or drag the top of the event in the arrangement view up to increase the volume.
Bug fixing and code cleaning is always a good thing.
When saving a effect chain to a template and then loading the chain again on another track a gain and pan slider of the top effect track of the chain is visible on the track where the chain is inserted. The meter and fader grid is also ‘disordered’ after inserting the chain.
@H-man wrote:
Also, it would be pretty handy if the bounced punch range would auto-crop.
Indeed, would be pretty handy.
There is a problem with sending MIDI clock/start/stop. Podium sends MIDI messages to the MIDI clock enabled output but the external device does not start playback (in my case a MIDI hardware sequencer). With Reaper or Studio One the external device slaves perfect to the sequencer playback.
Great release. Thanks!
😀
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(?).
The strange thing is sometimes it works and sometimes not.