LiquidProj3ct.
LiquidProj3ctNo, it wasn’t fixed yet. But that’s not the big problem, the big problem is that if you use plugins that generate latency you won’t be able to export to wav your project without errors.
Zynewave@LiquidProj3ct wrote:
Frits, I have a new musical order for 1th January 2011. Please, could you fix before January the latency bug? I say this because I cannot render to wav any song!
Please don’t feel pressured about this, if you feel that you cannot fix this soon just let me know and I’ll make the songs in another host. 😉
Best regards
2.40 will be a minor bug fix release. I’ll see if I can reproduce this bug and include a fix for it in 2.40. I can’t make any promises though.
LiquidProj3ctThanks Frits 🙂 Try to reproduce it using zPitch as thcilnnahoj show in his video
thcilnnahojIn the meantime, can’t you do a real-time bounce of the master track, or just the problematic tracks before rendering the master? At least that’s how I work around it (though I prefer to use real-time bouncing in most cases anyway).
That being said, I kinda already do this: 😳
@LiquidProj3ct wrote:
…and I’ll make the songs in another host. 😉
LiquidProj3ctThe problem is the master itself, which uses my only limiter (Stillwell EventHorizon+) and it has a big latency.
And this is a thought inherited from old FL Studio days, which I don’t know if it’s true in Podium: only non-realtime bouncing uses the high quality features from most plugins, like oversampling. Is that true in Podium?
Anyway it’s a good idea 😉
outsiderinventionouch… this is a bad problem. i can’t mixdown my tracks with imageline’s maximus. 😥
what to do now?
thcilnnahojWell, the only way to make sure everything gets written to a sound file the same way you hear it in this case is using real-time bounce recording, meaning you need to real-time bounce record individual tracks that have plug-ins causing dropouts because of latency before rendering a master bounce.
If it’s impossible to record the whole mix in real-time because of CPU use, you could still put all your tracks in a “dummy” group (just before the master), which you then offline bounce. This way you can run the mix through those problematic effects on the master track in real-time… in a sort of 2-pass bounce. 😕
In my findings I’ve had dropouts only at the start of individual sequences, never anywhere else. Since the “pre-master” bounce would be one long sound sequence, this should work until the bug finally gets fixed…
I’m curious if you’ve experienced it in other places, like right in the middle of a bounce of a single sound sequence… :-k
thcilnnahoj@LiquidProj3ct wrote:
And this is a thought inherited from old FL Studio days, which I don’t know if it’s true in Podium: only non-realtime bouncing uses the high quality features from most plugins, like oversampling. Is that true in Podium?
Of course I don’t know about the actual bounce rendering code, but I don’t think offline bouncing produces higher quality by itself…
Whether it tells plug-ins to switch to high-quality mode (if available) – that’s a good question. Are you sure this works also with 3rd party plug-ins in FL Studio, and not just Image-Line’s own plug-ins?
outsiderinventioni’m actually getting very weird behavior all throught my songs when using maximus. not dropouts, but “smearing” and strange volume bursts. everything sounds fine when i render without maximus. and no, it’s not the limiter settings. song plays through fine within podium.
i’ll try rendering each track and then the master.
outsiderinvention@thcilnnahoj wrote:
In the meantime, can’t you do a real-time bounce of the master track,
this is a work around, but i can’t imagine sitting around for 40 minutes everyday real-time rendering test mixes. no problem with rendering a final like this, but i like to take my mixes around for a while and tweak them as i listen in different environments and this is going to be a PITA.
Trancit@thcilnnahoj wrote:
@LiquidProj3ct wrote:
And this is a thought inherited from old FL Studio days, which I don’t know if it’s true in Podium: only non-realtime bouncing uses the high quality features from most plugins, like oversampling. Is that true in Podium?
Of course I don’t know about the actual bounce rendering code, but I don’t think offline bouncing produces higher quality by itself…
Whether it tells plug-ins to switch to high-quality mode (if available) – that’s a good question. Are you sure this works also with 3rd party plug-ins in FL Studio, and not just Image-Line’s own plug-ins?
In FL Studio FLS internal render additions like Resampling, HQ Envelopes etc. are Fruity only…
For every non native plugin you can choose in it´s options (for each plugin seperate and state is saved) if you want to inform the plugin about offline rendering or not…
Trancit
thcilnnahoj@outsiderinvention wrote:
this is a work around, but i can’t imagine sitting around for 40 minutes everyday real-time rendering test mixes.
Yep, no argument there. To be honest, I don’t know why it hasn’t been looked at for this long, as it actually is a quite serious bug if you think about it for a minute… I just didn’t bring it up a lot since I first reported it because I always use real-time bouncing ever since that was restored to working order.
As for turning on higher quality for plug-ins during rendering… This is just my opinion, but I would disable such an option, as I don’t want the final render to sound different than what I’ve been mixing and listening to for the last n hours. 😉
Let’s just wait for Frits to tell if Podium does anything differently during offline and real-time bouncing.
LiquidProj3ct@Trancit wrote:
In FL Studio FLS internal render additions like Resampling, HQ Envelopes etc. are Fruity only…
For every non native plugin you can choose in it´s options (for each plugin seperate and state is saved) if you want to inform the plugin about offline rendering or not…
Thanks Trancit. However I’m confused because Sytrus (VST version) has settings for real time and for rendering time.
@thcilnnahoj wrote:
As for turning on higher quality for plug-ins during rendering… This is just my opinion, but I would disable such an option, as I don’t want the final render to sound different than what I’ve been mixing and listening to for the last n hours.
Believe me, in my olders host that didn’t have an advanced bounce feature like Podium, it was pretty useful. 😉
ZynewaveI’ve identified the problem when bounce rendering with plugins that introduce latency. I’m working on a fix for that. Whether this fix solves all reported bouncing issues remains to be seen. I expect to have a 2.40 beta ready for the weekend.
LiquidProj3ctActually those are good news! 😀