Zynewave.
jpleongHi, I am trying out Podium to see if it will be a good fit for my work.
I am wondering if it is possible to do a “Mixdown to file” sort of operation without having to do a realtime bounce. I work with tracks that end up being longer than an hour and to do a realtime bounce would be, how should I say… tedious.
JP
ZynewaveI am wondering if it is possible to do a “Mixdown to file” sort of operation without having to do a realtime bounce.
You can do an offline bounce render instead of a realtime recording. Right click the bounce track and select the “render bounce track” command (or press Ctrl+B).
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
ZynewaveI 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.
Yeah, I’m considering adding a new “auto-size bounce event” track option which will keep the bounce events automatically sized to the length of the arrangement.
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
http://www.zynewave.com/wiki/doku.php?id=guide:sound#sound_editor
There is a few destructive editing commands. Normalizing is there.
2) Is cross fading in Editor mode coming soon?
You mean destructive fade in/out in the sound editor? If so, then I have no estimate on when I start on this. As a workaround (and a very flexible workaround I think), you can set up an arrangement with the sound events you want to fade, set up crossfade or level curve automation, and then do a bounce render. The resulting bounce sound will then be your “destructive” version.
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
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
ZynewaveImport 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?
I don’t understand why you need to normalize so early in the process. Normalizing is an operation that will result in a small quality degradation, so it should be done as late as possible. Best would be to adjust the track levels in the mixing, so that normalization is not necessary.
Also, how is your relationship with your former employer, TCE?
I still do consultant work for TC. I’ve been involved in some parts of the control panel for the Konnekt.
Is 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…
It’s on the todo list.
BTW- the Ctrl+A shortcut didn’t work for me in the editor view. Has this been /will this be implemented in future versions?
Ctrl+A will select all events. In the sound editor this would be any marker events. To select a segment, press J.
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
Zynewaveis there an easy way to switch between I/O within a project?
A command for adding mappings for multiple audio interfaces is on my todo list. Currently you need to manually modify the mappings. Note that the audio mappings only refer to a channel number on the audio interface, so you can still use the audio mappings for your second interface, even though the channel names may be wrong.
I’ve also tried adding WDM through the device properties but it doesn’t show up in the project. Am I missing something?
Only ASIO and Wave drivers are supported. Using Wave drivers is not recommended, as it results in terrible performance. If you don’t have an ASIO driver for your interface, check out the http://www.asio4all.com driver.
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
Zynewavethe Bounce took around 15-20 minutes. With Audition, I’m used to a three to five minute mixdown to file
Such a difference must be due to something other than the actual performance of the bounce rendering. Rendering is performed as fast as possible, and using multiprocessing if available. Note that if punch-in/out is enabled the punch-in/out markers define the range that is bounced.
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.
Podium performs all edit actions in memory/cache files, and does not write to the sound file until you choose the save command. Maybe Audition operates directly on the file. When Podium cannot allocate more free RAM, it starts writing the edits to cache files, which may explain the slowdown. You can check if the RAM is used up with the Windows Task Manager. How much RAM do you have, and how big are your audio files?