super_crunchy@Zynewave wrote:
Say what!? That’s the whole point of the bounce track. Once the B button is activated (and R button is deselected), the bounced audio track should play. This is indicated by muted subtracks and the audio event on the bounce track is drawn in unmuted color.
Another nice thing about the new bounce rendering, is that you don’t have to record arm the bounce tracks if you just want to render one bounce track at the time. The B button then behaves more like the freeze feature of other hosts.
Frits
guess what? i’ve been using this feature incorrectly the whole time. a long time ago when i first used the bounce feature, i used to disarm both R and B buttons and still do that to do this day. simply didn’t realise you had to leave B enabled after bouncing, for playback. i deserve one of these > 🙄 😉
disregard everything i’ve said above… it’s irrelevant now i know how to use Podium properly 😆
super_crunchymaybe there should be an tick box in the setup section somewhere, or maybe on a track by track basis – “Allow track to play back after bouncing”
? or something like that
thanks
super_crunchy@Zynewave wrote:
@super_crunchy wrote:
Something you may want to consider changing eventually, and this goes for realtime bounce as well… once a bounce track has finished recording (ie stop is pressed after recording) make the bounce track automatically turn off “Enable audio bouncing”
I’m not sure I understand. Do you mean that once you have bounce-recorded a track, either realtime or rendered, that you want the track to be converted to a regular audio track without the bounce button in the track header?
yes Frits, that would be good – because at the moment the bounced audio does not play back until “Enable audio bouncing” is turned off
super_crunchyhave tried it, and its a nice, simple and efficient implementation… thanks Frits!
Something you may want to consider changing eventually, and this goes for realtime bounce as well… once a bounce track has finished recording (ie stop is pressed after recording) make the bounce track automatically turn off “Enable audio bouncing” and make the tracks beneath in the group “Unload plugins” by default. Seems to be a few extra steps every time you bounce when realistically after you bounce, you’d only want to play the bounced audio. Well, this is the case for me, to save CPU cycles
super_crunchybrilliant! just downloading it now to try it out. thanks Frits. this is certainly going to be one of the most applauded features you’ve added recently i think
super_crunchyWant a free plugin to make your mixes sound warmer, and like they’ve been run through a nice analog mixing desk?
http://www.tritonedigital.com/products.htm#colortone
This one’s been out for a little while, those of you who frequent KVR have probably already seen it.
Note: It’s very subtle, so you may have to put on your best pair of Golden Ears to hear it working! Try it on a whole mix to see how it can warm your sound in a subtle way
super_crunchyExtra RAM should also help plugins to perform better. Is this correct, or does it depend on the plugin? Sorry, this area is unknown to me
Edit: I already know it will help plugins like samplers that load samples into RAM, but what about VST instruments and effects?
super_crunchyI’ve got 1GB more RAM coming my way soon… will let you know what kind of improvements I get from this. It might even reduce audio dropouts altogether 8)
super_crunchyI’m very excited about the offline bounce. It’s a feature that most other hosts have, and although I’ve gotten by ok without it, I’ll definitely be using it when it arrives. Great way to bounce even when CPU use is maxxing out. Good luck Frits!
super_crunchy@darcyb62 wrote:
Nice program once you get used to it. Now I just gotta see if like it better than Tracktion enough to pay you to fix that occasional “but not random” silence bug. 😉
I think you should buy yourself a christmas present 😉 🙂
super_crunchyI use an onboard graphics card on my laptop (shared 64mb). I turned “hardware acceleration” to about 50% to help run some plugins smoother, and it also helped Podium a little I found
A “run of the mill” 64mb card should be find I think, you could probably pick one up for $50
super_crunchy@acousmod wrote:
And why not also add a new file option with something like “bounce entire project to”, with the possibility to save the file where we want ?
Excellent idea, this will be the equivalent of “Export project to WAV” that others hosts have. I think for new users, the lack of this option can be confusing
I like solution A as well, except my suggestion for the bounce online option would be this
On first click of the B button on a track, the bounce OFFLINE option is enabled
On second click of the same B button, bounce ONLINE is enabled (and the B button would change, maybe it would become 50% transparent red instead of 100% transparent red). On third click, bounce recording is turned off. So basically it’s a three way toggle
super_crunchyI’ve removed DR-008 from the curent project after bouncing
As I’m still getting minor audio dropouts with 512MB ram, I’m going to upgrade. Going to upgrade to 1.5GB RAM (an extra 1gb) so I don’t run into any more problems… this should be considerably more than I should need, shouldn’t it? (Translation: will my arse be covered?)
I suppose it depends on how many tracks I have running in project…
For anyone who uses many tracks of audio, bounced at 32bit with higher than 44100Hz sample rate, what amount of RAM are you finding sufficient?
Cheers
super_crunchyOn the same track headers as the E button,
the X button is used to bypass an instrument or effect
and
S = solo
M = mute
R = record (on that track)
B = bounce (if the track is bounce enabled… right click on a VST track and choose “Wrap in new bounce track” if you want to record the output of a VSTi, or if you want to record the audio at any point within a plugin chain)
Regarding the tracktion racks – Podium can do the same thing, except without all the visible rack cables. it’s easy to set up vocoders, side chain compressors, by making sure you use the right mappings available for that plugin. For example, a standard vocoder will have 2 inputs (one for carrier, one for modulator) and one output. So you’d make sure you have three different tracks, and on one track have “input 1” mapping, on another track have “input 2” mapping, and on another track have “output” mapping. Then you’d feed each input track a different sound source to start the vocoding. If you’re familiar with vocoder plugins, this will help you understand how the other things I mentioned (ie side chaining) can be achieved in Podium. Multiple outputs is also very simple to set up (I do it all the time with FXpansion Guru)
Have fun
super_crunchyFrits beat me to it 😆