Fl 5 and some vsts not bouncing down right?

[Mighty_Hero]

Everytime I bounce down a track using trilogy and/or atmosphere, when I play my track back, the notes aren't sync'ed up. I have changed my buffers to test (which the newest version lets me use 64 buffers with no problems ) from the lowest, to 1012....still same problem.

I can't figure out why it's doing this. I tried the new wrapper settings such as 'use fixed size buffers' and the 'rendering mode notify' (what's this do btw) Linear, sync 256 etc.

Anyone using fl5 and trilogy/atmosphere want to test this on your end as well? So far all other plug-ins seem to bounce down properly. I tried this on 4.5.2 same thing. Now since this is a brand new and clean install of xp, I guess I could always install 4.12 to test this as well.

[Mighty_Hero]

Ok here is one really quick test I did with 4 random vst's:
I bounced down with only fl compressor, no eq, etc.
Tried all different types of buffers, since trilogy and atmosphere are sample based. 64, 256, 512, 1024.

The mp3's are named by vst. Brand new XP install, and newest drivers for all OS, hardware, and vst related dlls. Now I can't figure out why during the bounce down process (wav and in mp3 format) is reading trilogy/atmosphere like this, when it plays right in the host. Also stylus RMX bounces down fine, so I can't say all their products do this, because they all don't. Weird for sure.

http://mighty-hero.panicnow.net/Albino2.mp3

http://mighty-hero.panicnow.net/Atmosphere.mp3

http://mighty-hero.panicnow.net/Sampletank2.mp3

http://mighty-hero.panicnow.net/Trilogy.mp3

[Ian B]

Hi Brice,
The Atmosphere/FL 5 out of sync problem confirmed here. I haven't changed any settings to try and fix this....they work for all my other vsti's, including sample based, so the problem must lie with Atmosphere Doesn't help you much, but at least your not alone.

[zircon]

I get a problem like this, but much worse, with Kompakt-based VSTs - but that's it. Stylus RMX works fine.

A buffer of ~1000 samples is really pretty tiny, I think. Try increasing to about.. 5000, and see if that helps. In order to solve my rendering drop out problem w/ Kompakt, that's what I had to do, and I also had to increase reserved voices in each Kompakt instance from 64 to 244, and preload/voice memory exponentially. Increased my RAM usage from 600MB to 1.1GB, but it worked.

[moody]

unfortunatly this problem has been previously dicussed on the fl forums and is a known fault.
spectrasonics have been notified of the problem..
steve...

[Mighty_Hero]

unfortunatly this problem has been previously dicussed on the fl forums and is a known fault.
spectrasonics have been notified of the problem..
steve...

Ok that's good to know others are aware of it. This also happens with Trilogy. I will try Bosendorfer here in a minute, since it's also sample based.
Thanks guys.

[nutsadamus]

I can also confirm the issue with Atmosphere and FL5.
...pronounced lag in the Atmosphere track after rendering. I thought I'd try loading Atmosphere within an instance of EnergyXT vsti but got the same problem.

Hope it gets sorted out soon. This bug's been around a long time.

[jmh]

Isn't that UVI engine marvellous... You'll encounter the same behavior with all UVI engine based instruments.

I ran into an even weirder issue. With an earlier FL demo - afair it was 4.10 (?), I had zero latency on Plugsound instruments! Yes, that's right. Samples played on FL's own sampler channels appeared late compared to Plugsound drums (from the Drums and percussive elements thing, vol. 3), and the amount of delay between them equalled the latency setting in FL.

From what I've heard, this happens with every single UVI engine based instrument, including Mach5. Except that the timing error seems to vary greatly - I've heard one person having UVI engine playing exactly a 16th note late and so on... and my experience with it seems to be unique.

Regards,

JMH

[nutsadamus]

Well,

UVI sure sounds good, though:) And afaik, it only seems to be an issue with FL.

[Carbonboy]

Isn't that UVI engine marvellous... You'll encounter the same behavior with all UVI engine based instruments.

deleted...

From what I've heard, this happens with every single UVI engine based instrument, including Mach5. Except that the timing error seems to vary greatly - I've heard one person having UVI engine playing exactly a 16th note late and so on... and my experience with it seems to be unique.

Regards,JMH

Plugsound plugins render 400 ms (with 10 ms latency setting)late on my system. It varies with the latency on FL.

It is indeed the engine, as far as I can see. They are not conforming to the VST standard.

Carb.

[reflex]

Well,

UVI sure sounds good, though:) And afaik, it only seems to be an issue with FL.

I've made it happen with other hosts as well. It's a plugin issue and the people from PlugSound are aware of it.

[kode_poet]

Same thing here. I've had that problem with Atmosphere and with all of the Plugsound modules, specially the hip hop one, which drove me nuts. Usually what I end up doing is exporting the loop to wav, choping it up, and loading it back in to the FL sampler or granulizer to use it and have it sync properly. Hope this helps.

[Mighty_Hero]

Well that is weird.
I loaded hip hop volume, put it at the same tempo as the loop and bounced down. Works fine, but I am following what you guys are saying. So was Eric notified personally on the spectrasonic plugs? I don't know the contact name for the plugsound side.

[Jaeson Merrill]

try wrapping them as DXi, works here

[Mighty_Hero]

It does?
Let me try that then.