Levendis's Forum Page

@The Telenator wrote:

…I need to grab that beat in my ear while grabbing my guitar and pick to head into recording a track.

Undoubtedly, a performer surely needs a beat or two to guide them into sync. Orchestra conductors, tapping drumsticks, and click-tracks provide such cues in concert halls, stage and recording studio.

Try the following. While it’s a little more effort to establish than a pre-count function, these tactics will give you those cues:

1. Playhead launches ahead of Punch In.
2. Loop range starts before Punch In – for multi-take recordings.
3. Record the lead-in.
   This is probably most advisable. You can trim and fade the take afterwards.
   This method ensures the inclusion of sound played, fractionally, ahead of the first beat.
   • e.g. You might want to capture the sound of a saxophone’s mechanism when keys are pressed, which occurs before a note is blown (on beat).

Hello MelodyMan,

The behaviour you’re after is still there. The following applies to, sound and midi sequence events on the tracks timeline, as well as midi notes in editors:

Shift + click + drag
Disables quantize snap.

Click + drag + Alt
Constrains an event to its timed position (the function you want).
Alt + click + drag
Adjusts the length of events.

… holding Ctrl after you begin these drag operations
Creates an alias copy of selected events.
… double tap + hold Ctrl once you start these drag operations
Creates an unique copy of selected events

@alex wrote:

Plugin scan – adding new and removing deleted plugins (from the list) at every launch.

Preferably, this would be optional behaviour, as the Telenator suggests. I like that Podium loads fast. A plugin scan at each launch would be stifling. With the current device list, it would also mean a scan would occur each time a project was open (within the same session of Podium).

@The Telenator wrote:

… time maintaining my plugin database and then having to load the most recently updated list into every current project and template.

I do the same. The template I maintain is updated each time I install a plugin to my system. It also has a customised hierarchy, grouping plugins by type, for easier selection in the arrangement.

The pull down menu for prescribing the desired device list, on the project start page, used to include project templates.

Hello MelodyMan,

If I understand you correctly, you would like to mute only what is in the puch range as you loop through and record your sequence. Akin to not having an ‘overdub’ mode.

I would have suggested making a child midi track and selecting ‘Use as composite track‘ in its Track Properties dialog. This would mute prior takes within the punch range while always playing back the midi parts on its group track.

Surprisingly, composite tracks don’t operate on midi as it does on audio. Subsequent takes don’t spawn as child tracks, each pass of a loop is written to one sequence event.

Hopefully Frits will shed some light here.