rinxai's Forum Page

Yup, this would be useful. I’m thinking this could probably be configured once generic midi mapping for all key elements such faders has been implemented. 😉

@Conquistador wrote:

Can you please consider some sort of automapping process for Podium that will allow a user to delete an existing VST folder structure and simply import the new one but…also not lose all their FX and instrument settings if a project already has mappings in use?

+1

This is also an issue for me, as updating and testing new plugs and then consolidating into a tidy list of devices does eat up a fair bit of time.

1. Generic MIDI controller mapping (eg: MIDI CC to mixer pan/fader/send..)
2. Zgrid
3. Time stretching

@AngelicLight wrote:

Can I ask why you found Podium so attractive and what you like about it so much?

…

Does the “heirarchial” way of doing it involve extra steps to get something going as opposed to another host like Cubase? Is the advantage that it’s more creative?

It being an affordable option put it at the top of my list. That it is a stable and robust audio/midi engine many years in development, zero bloat, zero bugs. Intelligent contemporary design. Imho, Podium’s GUI implements some ‘best practices’ in regard to general software and GUI design, stuff that has nothing to do with digital audio, but more to do with how Frits approaches a solution to a challenge. Rather than imitating the hardware paradigm, Podium provides a uniquely flexible ‘modular’ approach to defining signal flow from inputs, audio/midi tracks, groups, sends/returns to master output according to the changing needs of a project.

It seems a more intuitive approach to directing signal flow, with an excellent implementation of track bouncing/’freezing’. It is IMO not yet perfect, but with Frits’ proactive development cycle I’ve noticed steady improvement with each regular update.

The ‘hierarchical’ approach is IMO another example of ‘best practice’ in terms of using programming conventions that have evolved over the years of software design, the main purpose being Usability. Now that I’ve mostly figured out how deploy Podium, I can say that the ‘steps’ are actually mental, since once the usable methods are understood, getting something going is no problemo.

For an analogy I consider a tree trunk and root system, where the signal is like sap flowing up from various root tips into groups of roots flowing into a stereo master trunk. Signal/sap flows up from the bottom/VSTi/audio feeding into groups feeding the master track at the top. So initially in Podium, gardening for sound involves first sprouting a seed/arrangement, and growing it piece by piece, root by route into a system defined by you. By using templates, any part of a arrangement/group/track/root can be cloned and grafted onto other……erm plants. Also, any kind of tree/track routing structure can be created, simple or complex, and is easily first defined in ‘New Arrangement Properties’. Useful for when the structural requirements for an arrangement are known or established.

I don’t see this as giving some extra ‘creative’ advantage, since its just a tool, but a very capable one. It is sharp and is being further honed to virtual perfection. I feel that ‘creative advantage’ is something that grows with relative mastery over one’s tools and instruments, regardless of what they are. Its like learning to play a guitar, or ski, ride or surf, the creative bit kicks in once the basics are mastered.

😉

Great, Thanks 😀

Thanks for the informative reply, will give it another go.