Levendis.
alexHi!
I’m Alex and I am a vst plugin junkie š
I downloaded Podium free ………
……There’s one thing that really bothers me. I know that Podium uses 32 bit floating point for all internal audio operations just like the most of the software that I have. So, normally, if I work with 24 bit files, the extra bits are added only for the internal audio operations, but the actual conversion never really takes place, and I’ll have 24 bit mixdown as soon as I export the file. For some reason, Podium will only export 32 bit floating file or ask to dither to 24 bit?! Another strange thing happened. I have a 24 bit interface and I had a 24 bit driver that came with it years ago. The files that I recorded and saved were 24 bit. That driver started crashing my system and I had to update it. It’s now 32 bit driver and so are the recordings in Podium. I’m pretty confused about this.
And my second question would be: what can I expect from the licensed version?
Thanks in advance
kim_otcjPodium does everything at 32 bit resolution. It doesn’t just up-sample to 32 bits for the plugins, it uses 32 bits for bouncing and on the mix bus as well. That’s a good thing. You wouldn’t want it automatically down-sampling stuff in the signal path.
The only time Podium isn’t working at 32 bit is when you set it to save audio clips at a different bit-rate (e.g. when saving a clip from the audio editor).
If you’re recording a large number of tracks and you’re concerned about running out of processing power, then you should arrange all your tracks into groups. That way you can bounce groups of tracks to create sub-mixes, which will free up all the space that the individual tracks and plugins were using.
The TelenatorWelcome to the world of Zynewave, Alex.
To be honest, it’s been long enough since Podium Free that I can’t recall what else is involved besides ReWire and multi-core usage, BUT let me add that the free version is always several upgrades behind whatever we licensed users are able to record with right now. There was recently a big Mackie control surfaces upgrade in a recent release — which I am making huge use of suddenly, having bought a very full-featured MIDI controller keyboard. Basically, the license is so cheap that it’s rather hard not to end up buying it before too long. You are not missing a tonne of features with the Free, though, so the choice is strictly personal needs.
kim was correct about most of what he posted, except that one can set Podium to process everything in 64 float internally, if one wishes. I do — and it does add to quality some, though at a CPU price hit. If there was no value in using internal 64, then I would ask, Why then do so many plugin makers have their VSTs do everything internally at 64 bit? Hmm?
I can’t answer all, but interfacing at 24 is what I and most DAW users employ — worlds better than 16 and plenty good enough. These ones on some forums who insist on using very high rates such as 196 to record rock and pop make me laugh and roll on the floor. It’s not a symphony by Ravel! Oh, also — Podium does not have any dithering of its own onboard, regarding your mention of it. Podium can only reduce your bits without that, SO . . . you can import RDR or the mda dither (both free) as plugins for this task, or you can do what I and some others use — drag your files into the free AUDACITY 2.02 open-source audio editor and do it there with Audacity’s even better onboard dither. I suggest you install Audacity in any case, because it handles various other file conversion tasks (many formats!) Besides, having and having used Audacity used to be a sort of ‘rite of passage’ in the realm of digital recording. It sets up in a flash and is also particularly good for capturing streaming audio from the Net and converting your old tapes and vinyl to PC files. I digress.
Perhaps check into the freeware ASIO driver called ASIO4ALL. It has a new beta version lately that I’ve tested and found even more stable than the last one. Even if you stay with purchased driver, it is good to have a spare ASIO lying around. Anyhow, it will do 24 bits, if you need this. BTW, when you make 24-bit into 32 float it should not truly be considered a ‘conversion.’ Think of it more like adding more breathing room or a higher ceiling to a too-tiny apartment dwelling by throwing 8 bits in the basement, etc. I have had big problems with Podium freezing up on certain other commercial drivers, so this is another reason I mention ASIO4ALL.
Cheers and Best Wishes with getting going here. I’ve put Podium through some rather intense extremes to say the least. I’m usually pushing the envelope these days both sonically and digitally with these DAWs when I’m doing my own projects and not recording other artists, and I haven’t quite killed Podium yet. At the very least, let me say that Podium is a truly unique DAW and quite unlike any other you will possibly use.
P.S. [Edited to add] Alex, I, too, am a plugin junkie, but I’ve found a really nice 12-step group to help with that!
adimatis@The Telenator wrote:
kim was correct about most of what he posted, except that one can set Podium to process everything in 64 float internally, if one wishes.
Not Podium Free, it cannot.
Levendis@The Telenator wrote:
P.S. [Edited to add] Alex, I, too, am a plugin junkie, but I’ve found a really nice 12-step group to help with that!
lol š
@alex wrote:
And my second question would be: what can I expect from the licensed version? I have a single core processor and I don’t use rewire.
Welcome Alex š
The licensed version also enables working on Surround Sound projects.
While you’re at YouTube, may I recommend taking a look at Liquid Proj3ct’s videos.
@The Telenator wrote:
Why then do so many plugin makers have their VSTs do everything internally at 64 bit?
To match hardware capability!? Satisfy maximalists!?
@ alex: Here’s some explanation by Zynewave about 64-Bit Mixing.
alexHi, evb!
Thank you so much guys!
Wasn’t such a great idea not to open the Podium guide, after all. I’d have done it instead of asking stupid questions.
@ kim_otcj: you answered the second part of my first question. Now I know that Podium can’t really “see” if one uses 24 bit interface with the 32 bit driver (it only cares about the driver :)). But as you said, it can be set ( setup>preferences>engine š ). However, the master bounce will still be 32 bit.
And, yes, Podium is really CPU hungry. So, with a 2 GHz single core processor, and 1.5 gigs of RAM, believe me I know everything about bouncing, although I prefer freezing, because you can unfreeze the track in a second and tweak, well, whatever you need to. But I still don’t know how or if it all works in Podium, and I won’t ask any more questions before I’m thru with the Podium guide.
@ The Telenator: No dithering onboard. Tnx man. I don’t know how I missed it. So, everything below 24 is just zeros and it’s totally safe to click on “convert to 24 bit…” and get rid of those bits, or simple leave it as it is and take care of it after dithering.
Using 192 for rock and pop?! š š š š š š š š š š
My M-audio usb ASIO works good for now, but u r right about commercial drivers (m-audio asio drivers are famous for being unstable).
Tnx and cheers
kim_otcjSo, with a 2 GHz single core processor, and 1.5 gigs of RAM, believe me I know everything about bouncing, although I prefer freezing, because you can unfreeze the track in a second and tweak, well, whatever you need to.
Go ahead and use bouncing exactly as you would freezing. When you bounce you get a “B” button in the track header. Press that and it will unmute all the tracks so you can edit them. Press it again, and it will bounce the tracks with all your changes. So, from your point of view, it can be functionally the same thing as freezing.
You can also use it like a regular bounce, and move the bounced sound-clip to a track of its own. But I don’t bother. I use group tracks, bounce groups, and just leave the bounced sound-clip on the group track.
And if you’re particularly ambitious with your track counts, you can even nest them. So you can have a group of groups, and bounce it separately.
Levendis@kim_otcj wrote:
Go ahead and use bouncing exactly as you would freezing. When you bounce you get a “B” button in the track header. Press that and it will unmute all the tracks so you can edit them. Press it again, and it will bounce the tracks with all your changes. So, from your point of view, it can be functionally the same thing as freezing.
You can also bounce within a Punch In/Out range. This is useful when you want to overdub a portion of track events. It saves time rendering the whole duration of a track’s output š
