Levendis's Forum Page

I reconfigured “10 tracks” slightly:

This routing means;

• Send bus 2 receives zPEQ’s output.
• Send bus 1 receives zPEQ and zReverb’s output.
• “10 tracks” has maximum attenuation at its output.

Hi sam c,
Frits’ suggestion to move the track’s fader is a good one. It allows maximum attenuation of a track’s output while not effecting levels on sends.

Nesting a send track within a return track will not work. It’s not a feedback loop but Podium marks the object in red.

Alternate to the right-click menu, on tracks, you can control fader & meter positions in the mixer.

I hope this helps 🙂

Hello joemans,

Yes, quantize operations do work on audio events. But there are some things to consider.

Here is a drum loop that I wish to manually beat slice…

I engage loop and tune to the region I wish to isolate.

Hit A on the keyboard, to toggle snap to off, or Shift+click+drag the loop range handles (start/end), to temporarily disengage snap (this also works on events).
This allows sample accurate placement of handles – the highest resolution of the sound file. Useful for finding zero-crossings. Although, it is not necessary given fades can be applied to sound events.

Ctrl+Q will reposition the edit cursor to the previous event.
Ctrl+W will reposition the edit cursor to the next event.
The edit cursor will jump to the ends of, selected events, loop ends, segment ends – whichever comes first.
I reposition the edit cursor to the ends of the loop range and hit Ctrl+T to split the drum loop sample at those points.

I now have a hit isolated.

Now, this is where some issues arise.

If I use the Adjust Timing tool there is the possibility of ruining my efforts so far. At full influence, the audio event is moved to snap to the grid and its length is adjusted. Below, the start of my split has moved to align with the grid and the event length has increased to equal the quantize unit length (grid). As the audio event references the whole drum loop, its increased length leads to the inclusion of the start of the next drum hit.

Resize the event, or apply a hard fade shape to remove it. Better still…

To prevent this, right-click the isolated event (split drum hit) and select Convert to Unique Cropped Copy before using the Adjust Timing tool. The sound event can be snapped and its length adjusted, but it will only hold the audio isolated in the split (drum hit). The unique cropped copy will create a new sound file in:
[current project folder] > [current arrangement folder] when you next save the project.

Alternatively, you could use the Beat Slice tool to perform these edits. Quantize operations have the same implications, as described above.

Here I have a note sequence. The notes are of various lengths and positioned loosely around the grid.

With the right settings, the notes can be rigidly quantized (snapped to grid).

Oddly, the min.Sensitivity has more influence at 0% ?!…

Uploaded with [URL=http://imageshack.us]ImageShack.us[/URL]” alt=”null” />

This is the Adjust Timing dialogue. It can be invoked via the Edit menu or right-click menu on events. It is available for audio and midi events on tracks, as well as note and automation events in editors.

Basically, the quantize functions allow you to tighten-up performance timing. Strength, sensitivity, randomize and swing allow some of the original timing to be preseved. At full influence, the selected events will align exactly to the prescribed tempo division (Grid).

This tool does not behave like a groove machine. Rhythmic patterns can be imported into both the note and automation editor as MIDI files. But not be applied to existing events.

If you’d like to match alignments of notes, which are off the grid, use the keyboard commands Ctrl+Q and Ctrl+W. This places the edit cursor at the start (Ctrl+Q) and ends (Ctrl+W) of selected events. Subsequently, moving events will snap to the grid and edit cursor.

I hope you found this helpful joemans.

• This reply was modified 11 years ago by Levendis.

Ishkabbible wrote:
… what is the point of “rebuild plugin database” if it keeps pointers to deleted folders / plugins? And how do I tell it to actually start clean?

Zynewave wrote:
Podium will try to reconfigure mappings of plugins that have moved location… The plugin combobox selectors in the arrangement editor should be highlighted in red if the referenced plugins are missing.

I truly appreciate that Podium handles plugins this way. Most other DAWs jettison note and automation arrangement objects when they can’t find the relevant plugin. In preserving that information, Podium allows a project to be salvaged. If I choose to abandon the referenced plugin, then I simply assign a replacement. All automation can be set to control new parameters while maintaining performance information.

I agree with the Telenator, if you’re doing D.I.Y.s on your plugins, then maintain more than one
[local disk]: > Users > … > AppData > Roaming > Zynewave > Podium > PluginDatabase.pod
It’s also worth maintaining project templates:
[local disk]: > Users > … > Documents > Zynewave Podium > Library > Project Templates > (templateA-Z).pod
These can store custom device lists. Which in turn can be loaded via the device list menu:
Devices – I/O, Busses, Plugins > Load Plugin Setup from Template > (templateA-Z)
The benefit of a template’s device list is adaptability and neatness.
One example is if you’re moving between hardware setups. Another is if you’ve renamed parameter objects – sometimes the plugin reports a name inconsistent with the plugin’s GUI. Here’s one I configured and includes submenus for parameters, consistent with the GUI:
<br/>

This is done within Project Folder Page Mode. Speaking of which, Frits, when in a folder with lots of objects, the page doesn’t scroll when dragging.

Since moving onto Win7, then Win8, I have yet to see the bluescreen. If Podium crashes, it is a rare occurrence, and the system is intact. On previous OS, the bluescreen would emerge in Podium and other DAWs.

Unfortunately, ASIO drivers are subsequently not accessible. I am able to use DirectSound or wmd. These are always reliably there to use. Or unplug then plug in my audio interface; the manufacturer’s ASIO driver for that device is then available for use.

I have also dispensed of VSTs I suspected were involved in catastrophic crashes. But essentially, I believe the more recent OS’ are way more stable. If you want to recover work, deselect Preferences > Editors > Activate power when opening arrangement editor to edit track assignments within the arrangement, or delete the objects in the Device List.

Best wishes in your troubleshooting. I recommend sending Frits the *.pod file via pm for debugging 🙂