FL Studio 6 Mixer...

[xander]

still, FL renders loop more easily than any other app, it's not that hard to do a little post-trimming..
..or export uncompressed/unlimited 32bit wavs

All I do, and it's so simple and fast, when I render my track(s) in FLS, I just add a two-bar silent track at the beginning. When I pull all the split tracks (or single track) into Audition (or back into FLS) I nudge the track that has any delay a couple of notches forward until it's in sync. Works great for me!

I think, from what I've heard so far, I'll stick with this metod. Sounds like any sort of PDC plug would buggar up the works, so to speak. The last thing I want is a lot of needless bulk in FLS -- I'm happy dealing with any plugin delay the way I do it now, and I don't experience that much of it anyway in what I do.

[Jaeson Merrill]

switchable PDC would be nice.. like in samplitude..

[Jaeson Merrill]

...then again theres never a reason to shut samplitudes pdc off..

[Mush]

I was just checking out the Fl studio demo. Is there any quick way to record vocals straight into Fl studio instead of using an external wave editor/recorder?

Cheers

[ouroboros]

yes, it is easy, you arm it at the bottom of the mixer

[Jaeson Merrill]

death to the pdc debate from looptalk forum:



Sean Ercanbrack wrote :


I found the following message in the tech support forum... Well, at least we know whether PDC will be in FL6 or not. I understand, and I'm not too disappointed. I just thought others might like to know as well, so that they don't have their hopes dropped. FL6 is still going to be a GREAT update. Remember that everyone!

--Sean



Jor van Gelder wrote :


Hello UAD-1/FL users and FL developers..!

My name is Jor van Gelder, PC QA Manager from Universal Audio. We have many users of our product UAD-1 Powered Plug-Ins who are interested in greater compatibility with FL. Currently, the plug-ins work well within FL except for two compatibility issues:

1. All UAD-1 Powered Plug-Ins always introduce latency. (as do all other plug-ins powered by standalone PCI DSP processors. Other professional plug-ins also introduce latency, esp. those which feature look-ahead processing).

The introduced latency is 2 x ASIO buffer size (when VST plug-ins are running at the ASIO buffer size).

Will FL soon feature "Plug-In Delay Compensation", similar to the Logic Audio, Cubase, Nuendo, Samplitude and SONAR host applications?

This is particularly becoming important with the new mixing features of FL Studio.

2. We are encountering a problem with .wav export in FL 3.56. Our plug-ins currently will be automatically bypassed during export because of the following restriction:

Because our Plug-In DSP code is executed on a PCI card, we have a
restriction that all UAD plugins must operate with the same buffer size.
The UAD plugins will detect and set the operating buffer size when
audio starts in the application.

A smaller buffer than expected is OK, but must only be encountered once the
maximum buffer size is set by the intial buffers. For example, the end of a loop
may use a small buffer. The UAD plugins play audio correctly in this situation.

If a buffer comes in that is larger than the operating buffer size of the UAD card,
the buffer size mismatch error will occur, and the UAD plugins run in bypass.
The plugins remain in bypass until the audio is stopped.

When the audio is stopped, the operating buffer size of the card is cleared.
When audio starts again, the initial buffer is measured and that value is
used to set the operating buffer size for the card. This allows the user
to change buffer sizes within the application or on thier Audio device
without having to reload the plugins.

It appears the FL .wav export is beginning with an intial buffer size that is smaller than the subsequent buffer(s).

FL Developers, please feel free to contact me directly for further details regarding compatibility.

________________________________________
- Jor van Gelder -
Universal Audio
Quality Assurance Manager - PC Platform
jvg@uaudio.com
voice: (831) 466-3737 x11
fax: (831) 466-3775
http://www.uaudio.com/



[Reply] [ vr, 07-mrt-03 19:45 ]







verstaerker wrote :

thats unbelievable - this message is over 2 years old and nothing has changed with the situation.

Are u from IL not intrested in finding a solution for this problem? i'm sorry to say
that - but it really looks like that u don't give a shit about it, cause there are not enoough FL-users with an UAD card. (i know the number is not that small and it's growing)

I can handle the situation to delay compensate everything manually (even when it's sometimes really a mess. But not beeing able to render a song is really annoying.

I can only say please do lot's of FL/UAD users a favour and solve this problem together with Universal Audio.

[Reply] [Profile] [ vr, 08-jul-05 17:12 ]








cocopuffz wrote :

So has this problem been fixed yet? I'm getting the UAD1-ULTRA-PAK soon. It would be nice to know if these issues have been addressed.

[Reply] [ ma, 29-aug-05 13:53 ]








reflex wrote :

Well, there's no plugin delay compensation yet. For the second problem, there's the "Use fixed size buffers" option, but that won't necessarily work well when rendering a wave.

[Reply] [Profile] [ ma, 29-aug-05 14:00 ]








verstaerker wrote :

it seems IL doesn't care at all

[Reply] [Profile] [ ma, 29-aug-05 15:02 ]








reflex wrote :

There's caring and then there's being able to actually do anything about it without rewriting the entire application. The second is not possible at the moment.

[Reply] [Profile] [ ma, 29-aug-05 15:11 ]








verstaerker wrote :

but if nobody ever answers (and i wrote several times about this problem) it looks like
that u don't care

this has been the first time someone answers - so i don't have to wait for any changes with this issue

[Reply] [Profile] [ ma, 29-aug-05 15:23 ]








reflex wrote :

so i don`t have to wait for any changes with this issue

Indeed, it won't change for version 6. There will be plugin delay compensation at some point, but I don't know when or what it will look like exactly.










[Reply] [Profile] [ Today 12:45 ]

[tony tony chopper]

Because our Plug-In DSP code is executed on a PCI card, we have a
restriction that all UAD plugins must operate with the same buffer size.

I don't understand why you're expecting PDC, since it clearly won't make your plugin work better, since it has 2 problems.

FL support proper VST plugins, that is, those that follow the rules (defined by Steinberg). A proper VST plugin should be able to process any length (that's lower than the max length they're being told) at any time. FL works in random-sized buffers, so will work with any proper VST plugin. We never claimed to support plugins tailored for just Cubase.

So nothing is broken here, we only claim to support 100% genuine VST plugins, and this one isn't. I'm not saying it's a bad coding on their side, it's probably their hardware limitation, but the result is that it's not a genuine VST plugin.

[pitchdrifter]

When you use gear like the UAD, do yourself a favor and use a host that does work properly with it (read: about every host on the planet). No point wasting your own time like that on a futile attempt to help imrpoving a product when the author clearly doesn't want to go that path.

Markus

[tony tony chopper]

yes, do that and don't forget to make another drama out of it. And of course, don't think of blaming the plugins themselves, ever.

[pitchdrifter]

Tony, I don't use FL. I was merely giving advice, stating its not worth to 'wait' for a feature to be implemented and get angry when it's evident that the developer doesn't want or isn't able to (even if he wanted to) implement it.

As for the plugin, they work with the set max buffer size and any size smaller than that. And that is according to your own elaboration above, following the VST specifications (which anyway? 1? 2.2?).

Take it easy

Markus

[tony tony chopper]

they work with the set max buffer size and any size smaller than that

I wouldn't know - I never tried it. I'm just reading what he wrote, and it seems to tell it's not the case:

Because our Plug-In DSP code is executed on a PCI card, we have a
restriction that all UAD plugins must operate with the same buffer size.

This is a strong restriction, which makes it a non-genuine VST plugin, and that restriction makes it so that it can't work in FL, because it's critical for FL to ask plugins to render a random amount of samples.

If you can understand their restriction, surely you can understand FL's? Our restriction is that plugins that can't follow the VST specifications accurately won't work in FL.

[tony tony chopper]

and as I said I never tried it (no we didn't buy every existing plugin, and certainly don't own every piece of hardware).

If the problem is that it crackles when it renders, PDC won't help, and it will never work in FL - no need to whine about PDC. If the problem is that it's simply delayed, PDC will.

[verstaerker]

i have nothing to add - i just demo'd Sonar - it's great
and PDC is lovely but i think can't work only with Sonar - so i'll have to find a good way to work with Sonar AND FL

[Jaeson Merrill]

guess ill be working around things for a long time...

[pitchdrifter]

Tony, the problem with FL's rendering is that the max buffer size sent to the UAD card by FL isn't actually the max buffer size, FL sends bigger buffers after that, so the UAD plugins get bypassed on renders.
The other issue is the normal absence of PDC, which means all plugins with a latency (including poco/uad plugins) introduce that latency to the audio stream they're used with, and all other streams don't get delayed. That borks the timing of your instruments within any single project.

Verstaerker: does Sonar support rewire? If it does you can pipe seperate FL channels into Sonar. I.e. use FL as a sound source, do all the fx and mixing in Sonar.

Markus