Yep, makes sense :). I always found the inability to quickly adjust the gain on the bounced track a bit frustrating.
I also strongly agree with the others above that the PAN, if not functional on the bounced tracks, should be either locked or not visable.
2.06 is looking like another excellent update!
Ben
Beta9 is uploaded, with the post-bounce gain controls. Let me know if you experience any problems.
@H-man wrote:
I also strongly agree with the others above that the PAN, if not functional on the bounced tracks, should be either locked or not visable.
Currently the text written on the pan slider/dial is dimmed, to indicate that it is inactive. I don’t think the pan control should be hidden, as you may want some indication of what the pan is set at, even when the track is bounced.
@Zynewave wrote:
Beta9 is uploaded, with the post-bounce gain controls. Let me know if you experience any problems.
@H-man wrote:
I also strongly agree with the others above that the PAN, if not functional on the bounced tracks, should be either locked or not visable.
Currently the text written on the pan slider/dial is dimmed, to indicate that it is inactive. I don’t think the pan control should be hidden, as you may want some indication of what the pan is set at, even when the track is bounced.
Okay, sounds great. I wasn’t aware that the bounced track could/would reflect the Pan position of the track(s) being bounced. Perhaps that is because Pan & Gain were inactive on the bounce track previously.
I look forward to testing 😀
@Zynewave wrote:
Currently the text written on the pan slider/dial is dimmed, to indicate that it is inactive. I don’t think the pan control should be hidden, as you may want some indication of what the pan is set at, even when the track is bounced.
Cool, thxs. I think that at least the pan should be untweakable althought, visible but untweakable. It would seem more natural.
Beta10 is up. This hopefully is the final beta. If I don’t find any bugs tomorrow, I’ll release 2.06 this weekend.
I’ve optimized and made minor changes to the way that solo and mute works. It is now possible to solo a bounced track, and still have the bounce playing. Previously the solo would disable the bounce.
If you have some spare time, please try this beta10 and check if your old arrangements still behave as expected.
@LiquidProj3ct wrote:
Cool, thxs. I think that at least the pan should be untweakable althought, visible but untweakable. It would seem more natural.
Perhaps in a later update. The way I see it, if the pan control should be disabled, then there are a lot of other inactive controls (bypass, sends, automation sliders, plugin editors, etc.) that also should be disabled because they have no effect when the track is bounced. And I think that would be a bit too much.
You’re right Frits, I understand. I like the new behavior of mute and solo buttons 😉 well done!
No problems with older projects here.
But – it’d be nice to have an easier method for bouncing to mono – maybe an entry in the bounce menu. (Until now I’d create an empty audio event, change its properties and bounce away. Added to that I now have to un-hide and hide the track, too. That’s unnecessarily complicated, I think.)
@thcilnnahoj wrote:
But – it’d be nice to have an easier method for bouncing to mono – maybe an entry in the bounce menu.
Are there any DAWs out there that let you check your mix in mono?
Just asking cause even though you might be asking this for a totally different reason I think a mono-switch on the individual tracks or on the master track buss would be awesome.
@UncleAge wrote:
Are there any DAWs out there that let you check your mix in mono?
reaper has a stereo/mono button on the master buss. would be cool if podium had this function