camsr wrote:Does the new version save and remember what plugin windows were open and which were closed?
If you aren't aware, it does this in version 10.
err....what?camsr wrote:Don't lie, it does not! (in version 10)
camsr wrote:Does the new version save and remember what plugin windows were open and which were closed?
If you aren't aware, it does this in version 10.
err....what?camsr wrote:Don't lie, it does not! (in version 10)
Is it faster to record the audio in real-time rather than freezing after the fact.Image-Line wrote:Why use the real-time method? Use the offline method (second video above), it's much quicker and higher quality. I wouldn't be using real-time Edison recording for making stems. Here is a tutorial for you:camsr wrote:Is this realtime rendering capable of recording without buffer underrun glitches?
Edison has a problem that when recording and a cpu dropout occurs, it records the dropout also. What has been illuding me is, how can Edison record buffer underruns, which only happen at the end of the signal chain?
Is it like a track freeze feature?
Regards Scott
It's faster to render normally. Since it's usually only one or two tracks, they represent a low CPU load and render quickly.Kalamata Kid wrote:Is it faster to record the audio in real-time rather than freezing after the fact.
OK, but if a randomization function is not repeatable, then how does real-time recording make any difference here? If you can't predict the result, then a live or offline render will both be the next random version of the event...and unknown.Kalamata Kid wrote:Some randomization functions are not repeatable. In this respect Cubase does this right! No I am not saying Cubase is better. I actually dropped Cubase and looks like I may be switching to FLS.
The quality of the realtime recording is limited by your live interpolation settings (this depends on your CPU) and plugins that automatically switch to HQ mode when they receive a render flag from the host. This is true for all hosts AFAIK. Generally, realtime will be lower quality than offline renders because of these two factors.Kalamata Kid wrote:And finally if the real-time audio recording on the playlist is of low quality I will not be using this method so I will have to find a convenient way to record in real-time and in high quality. Please make a suggestion.
Did you report it? First I have heard of it FL Studio always opens as saved here.camsr wrote:So has this been fixed yet?
When saving a project with only wanted plugin editors open, reopening the project includes almost all plugin editors open... some (edison) are saved open but when loaded are loaded closed...
Same here.saintjohnbaxter wrote:My projects always re-open in exactly the same state as they were last saved - plug-in windows left open are still open and still in the exact same place on the screen they last were. That's the same for FL native, Image Line & 3rd party VST/VSTi.
Thanks man. I'll check that out.camsr wrote:Make sure your plugin wrapper settings are correct, you may need to mess with them.
Disclaimer, I am not beta testing it.
That sounds like the Piano roll menu > Helpers > Detect scale feature. Turn it off. BTW if this is on you did it yourself, nothing to do with us.Orbit-50 wrote:What the hell did you guys do to it? It's all effed up now. The piano roll grid highlights keep moving all over the place when I transpose notes...
It's a BETA. Didn't you agree to these?Orbit-50 wrote:It literally crashed within 10 minutes of use, which has never happened to me before... This blows!
Why are you using the 64 Bit Nexus in FL Studio 32 Bit?Orbit-50 wrote:It bridged 64 bit Nexus2? Sylenth1 was acting like a retard! Just all kinds of wacky stuff is going on which is really shocking considering the excellent rock solid performance of the previous betas.
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026