jpleongThanks Frits!
Regarding the Group Copy… Genius. If I can’t find it in the Wiki and can’t figure it out by myself, I often assume it’s just not possible.
Regarding the AFL/SIP issue, the (fabulous) engine only works with “regular tracks” which is fine if that’s all you need. I, however, need to hear AFL for my effects returns and the only way I know how to do this in Podium is to reassign the output so that only the track in question is setup. Simply hitting the solo button doesn’t work, since that mutes all the other channels. Re-routing outputs takes a lot more time than simply clicking a button (or modifier+button). And as much as I’d like to charge my client an extra $50 while I spend that time re-routing, it’d be just a lot nicer if I didn’t have to do that. Is that a persuasive argument?
Regarding mute/bypass automation, I hope it hops onto your current schedule. I first learned multi-track automation with only Mute and Mute Groups and still use them on digital console based mixes -especially to switch between takes of tracks. It’s a lot cleaner and easier to accomplish than splitting/aligning, drawing fader curves, etc… Is that a persuasive argument?
I think (hope) my above suggestions will make using Podium much more friendly to newcomers and those used to different kinds of workflow. I regard such functionality as near-essential for quick, spontaneous, and creative multi-track recording and mixing. I can still put together a mix more quickly on a console than I can in Podium (or any other DAW for that matter) and I hope that Podium can narrow that gap for me.
JP
PS- it might be helpful to have a chart in the WIKI that lists “normal” functions/features people are used to and their Podium equivalents.
jpleongAre there any plans to implement a mute/bypass automation function within Podium?
Also, an AFL/SIP capability would be well received (by me!). And copying of whole groups would be awesome.
JP
jpleongThanks Frits!
I, for some reason, tried this before and it didn’t work. And now it does. The only thing that changed was the reassurance of your posting that it should change! Very comforting…
JP
jpleongI kind of do that already, albeit on paper.
I think some sort of History Manager like those found in Adobe Photoshop or inDesign would be a great addition, though.
JP
jpleongHeh. I should be more specific…
I have my root drive with Windows and all applications on my laptop. I then have an external Lacie hard drive with Podium Project data and temp folder.
I’ve now acquired another external to replace the current one and partitioned 144 GB for Project data and 4.8 GB for Temp Folder. The theory being that it would keep temp folder fragmentation to a minimum.
What do you think?
JP
jpleongIt’s likely your master bounce track has not been sized to fit your song. If you notice, you’re tracks with data have their lanes filled with a box of a slightly different color. The Master Bounce doesn’t. Either extend the existing area in the track lane or double-click with your cursor (at least in cursor edit mode, though this may work in other modes as well) in the track lane and a new instance will be created for you (which you have to stretch out, of course).
I believe the process is illustrated in one of the demo videos.
I couldn’t figure that out either, I had to ask…
JP
jpleongGot to actually use Podium as described in this thread! So, for the most part, things have been positive. The change in my workflow was smooth (though it took me at least twice as long, more on that in a moment) and I think helped the project as a whole.
It did take some getting used to figuring out the automation and choosing how best to process the audio -so that added an extra hour or two. The other aspect, which does not thrill me, is that it seems that it takes an incredible amount of time to do certain functions I am used to accomplishing very quickly. For instance, the Bounce took around 15-20 minutes. With Audition, I’m used to a three to five minute mixdown to file. Another example is happening while I type this thread. In Edit mode, I’ve tried chopping off the first two minutes of the recital (which was bounced as silence). It took maybe three minutes to do that. In Audition, that happens instantaneously. I’m not sure if it’s a rendering thing or what, but it’s made Podium unusable in that manner (it would take me an hour to just split the master file into smaller files in what has only taken me five or so minutes in Audition). Is there something I’m doing wrong here or that I could try to speed things up? Or, is there improvement coming along in this area?
Like I’ve said in other posts, I like Podium on the whole -it’s just the editing functionality (and now performance) that bugs me. Of course, with the money saved from buying Podium, I could just update my copy of Wavelab and take care of all my complaints (hmmm… 😉 what an appealing idea).
Thanks for the great looking and working environment in Podium, though. Boy, was I ever so pleased for those few hours…
JP
jpleongMy heart says, “Yes! VST Instruments, please!”
My head and pocketbook say, “Enhanced editing (fade in/out) and CANCEL feature!”
Since my livelihood is based on the latter, I have to agree with Frits for the moment…
JP
jpleongTrack level adjustments are usually insufficient to bring the audio to a decent level. When I work with more conventional material (when I have the luxury of using limiters, compressors, and overdubs!) I don’t normalize nearly as much. The problem with a live classical recording is that I need to leave as much headroom for preamps and converters as possible for the >90dB dynamic range. Hence, the need to boost.
The advantage of a change of workflow is the removal of one stage of normalisation, which is nice.
Please do hurry with the cancel button! I crashed Podium trying to normalize a 70 minute file and type my previous post on this forum at the same time.
Also, is there an easy way to switch between I/O within a project? I sometimes need to work on audio away from an interface and I can’t seem to be able to switch between the built-in soundcard and the interface from the Map Assign. I’ve also tried adding WDM through the device properties but it doesn’t show up in the project. Am I missing something?
Thanks!
JP
jpleongIs there a way to cancel a process in progress? I tried the normalize and realized there’s no cancel button. It’s rendering right now… as I type…
Waiting for an hour’s worth of music to normalize when you realize you didn’t select the whole region… ouch. BTW- the Ctrl+A shortcut didn’t work for me in the editor view. Has this been /will this be implemented in future versions?
(I’ve got 1.77 CM)
JP
jpleongThank you! This is very helpful. I will see if I can actually accomplish this on my own!
I do classical recording and, obviously, need to break apart long pieces into their respective movements. This has been my previous work flow:
Import tracks (usually one big 60-90 minute performance) -> mix to two stereo (if necessary) -> normalize -> hard limit (usually to compensate for clapping) -> normalize again -> cut movements into individual .wav files -> add fade in/out to each movement.
It would seem that Podium would necessitate a change in work flow as follows:
Import tracks -> Bounce to two -> (in editor) normalize -> use markers to ID movement changes -> fade curves -> bounce to two -> cut movements into individual .wav files
Does this seem right? Or is there a quicker way Podium can make things happen?
Also, how is your relationship with your former employer, TCE? I’ve been using their Konnekt 24D and have been having, er, issues with the audio staying consistently clean. I’m sure it’s not a problem with Podium but if there’s someway you can get them up and going with your program, I’d love it 🙂
I’m really digging Podium. Cheers!
JP
jpleongThanks! I actually tried Ctrl+B as the first thing but didn’t realize I had to extend the master track’s area to match the rest of the children tracks. Worked like a charm…
I realize I’m going to have a few more questions so I figured I keep it all in the same thread.
1) I couldn’t seem to find anywhere in the user’s guide that talks about destructive editing. I need to do the following: Normalize and Hard limit
2) Is cross fading in Editor mode coming soon?
JP