Does FLStudio have PDC?

[Hink]

I put 8 in () and get (8)

izzat some crazy ass CIA code or something?

I don't know...I can't even spell CIA...

[Igor 4000]

Plugin delay compensation is actually vital when you use high end limiters/compressors, DSP plugins/synths and convolution reverb, to avoid the entire project shifting tracks back and forth in time for a couple ms.

As a FLStudio user, how would I know if my entire mix is being effected by these small ms delays? Is there something I should listen for in the final render? I'm just wondering if my tracks have been effected by this all along and I have not been able to recoginze this


I'm not trying to extend this exhaustive thread...just trying to learn something

[jmh]

If you're using any delay introducing plugins, the tracks they're being applied to are playing late compared to other tracks.

Depending on the delay of the plugin and to some degree the instruments going through it, it can be noticeable. For example, layering two or three different bassdrums and processing one of the layers through a compressor that has delay on it, they wouldn't be playing at the exact same time and you might notice it from the transients.

Also, when rendering loops and using plugins that have delay, you'll end up with a small bit of silence in the beginning of the loop and you'll lose a small part of the loop, both the silence and the lost portion equal to the amount of delay the plugin has (with 'cut remainder' option).

Time permitting, someone I know who's using a host capable of reporting plugin delays will hopefully provide a list of plugins and delays they have, this information will be interesting and handy.

And I guess that as long as no-one notices it in their own work, it's not an issue

As for some people being vocal about it, read what they're saying. It's not the end of the world or an issue making music production totally impossible for them, just a concern that comes into play in their workflow...

Regards,

JMH

[Semitone]

PDC is a must for every serious producer, and now that fruity are starting to get serious with there sequencer then it should be vital for the proggramers to write a simple PDC proggram..

As you all know TC powercore is becoming a major player with there crack down on stopping pirated software by using a dsp card which runs state of the art plugins and synths with high limiters, reverbs, compressors ect and synths.. If you use fruity and run TC powercore's access virus and SH01 and Sony Oxford Efx's you will get a delay.. Because there is no PDC! And rewireing fruity into cubase and using the TC in cubase is just a bitch!

So all in all when it comes down to it in the end the serious ones are going to have to convert to a more stable enviroment. But please don't get me wrong fruity is realy good I have had loads of success with it though DPC is must in the end!
If they finaly make dpc for fruity then all will be sweet!!!

cheers!

[Peller]

My brain melted at around page 14 so forgive me if someone else has already explained this... but a delay of 61 samples on the master output when rendering shouldn't be a big problem. Your loop is 61 samples too short? Well, you know the tempo. So when you import it into Cubase, or whatever, set the tempo manually and use the snap to grid option when you're duplicating the loop.

And as Gol pointed out, if it's going to click, it's going to click. That's nothing to do with cutting off the last 61 samples. If the loop ends with silence or a zero crossing, no click. Otherwise, the waveform is cut off and it clicks. Deal with it.

[jmh]

Oh, great... "interesting" for first postings... lemme guess, Looptalk had a mention about this and you came over to check it out?

Bother to read before you bother to comment, it's a basic rule or practice on forums... maybe then you'd realise why clinging on to the number 61 is silly (ok, I'll clarify that so you don't have to stress yourself: it was an example of how much latency one certain plugin introduces - now imagine you were using a number of new amazing quality plugins that are available, processing your loops you intend to use in another application... see? Get it?).

A little effort might go a long way, just friendly advice

Btw, do you always accept workarounds as a solution to something (I'm avoiding the word problem here since someone might still cling on to the number 61... "not seeing the forest from the trees" or however that old saying goes)? Will you change your song's tempo to accomodate possible issues that popped up from using several tools in the process, one or more of them affecting the outcome in an unwelcome way? (Think about this without it being an exclusive issue to any single application as that's the way it's meant) Or will you accept flawed results from one or more applications with their flaws into your production, such as gaps in the audio, bad overall quality, wrong samplerate, younameit? (I'm really talking generally, so I hope no-one does the obvious and turn these around as any kind of commentary or FL as they're not - they're generalisations and should remain as such)

(Oh, and I should write short, clear sentences and not use these brackets as doing either seem to cause serious issues regarding getting understood )

Food for thought for the weekend.

Regards,

JMH

[forma]

This has got to be the worst 20 page thread i've ever read. It was good at first and very constructive, then Spaceman got involved and it became a fruity fanboy load of crap. Sorry, but bmanic is correct in what he said and I think PDC on the master channel shouldn't even be questioned and shame on you gol for arguing this fact.

One last thing; spaceman, do you know gol? is he a good friend of yours or something because you behave as if he is. Maybe he is though but Infact you behave as if you are a fruity dev too and perhaps married to gol and love him. Just my thoughts after reading 15 pages of crap.

thanks.

[jmh]

Regards,

JMH

[_pix_]

I´m interested in this as well. I saw a good workaround that was to use a template that had 2 or 3 or whatever number of delay compensation plug ins on each track. Then when you wanted to use a plug in (the guy used a UAD-1) you replace your plug-in with one of the "dummy" delay plug-ins (these dummies are bundled with the UAD card).

Now this would work great if the delay plug-ins were very low on cpu and all the plug ins that you´d use had the same latency.

I guess this would be the case with DSP cards. (?)

As anyone tryed this?

And are there plug-ins of the "dummy" type available?

[Jaeson Merrill]

strange... LOGIC doesnt even have PDC..

[stubar]

have read a lot of the pages in this thread.....

am still got a problem tho... I am using FL studio and Spectrasonics stylus, and the latency is more than noticeable.... A lovely "stutter" every now and again!!!

Music, for me, is about inspiration and some knowledge..... Ive just got to grips with FL Studio and dont wanna learn to use Cubase from scratch..

I dont wanna debate over who uses the most expensive/best host either...

just if anyone has managed to overcome this PDC problem with FL!!!???

Please help... i wanna get making more musics!!

thanks!

[gruberman]

strange... LOGIC doesnt even have PDC..

Watch out! You might be considered a FLS fanboy

[tony tony chopper]

A lovely "stutter" every now and again!!!

this is not latency

[stubar]

this is not latency

didnt think this was latency as for a main reason the "stutter" is being created not when played within FL studio, but when audio has been rendered and played thru ANY player, or wave editor...

but it is being created when stylus is being triggered and plays stylus out by a fraction of a second to every other sample or vst - so similar in that way....

maybe i need to reinstall Stylus?!

maybe i need to learn cubase??????

maybe there is a simple solution....?

[tony tony chopper]

maybe i need to reinstall Stylus?!

could be FL or the plugin, personally I'd vote for the plugin