Ableton Forum

Hey folks

I'm getting a slight problem using FL Studio 5 as a VSTi with Live 6. It all works fine apart from the fact that when I press play in Ableton, the first note/beat of anything I've got going on in FL (using its own pattern sequencers/piano roll) is missed the first time through the loop - it just doesn't sound. As the loop repeats, the first note/beat WILL be present - just not that very first one when I press play.

Does anyone have any info on this or know if it can be avoided?

Thanks

Ash

I saw your thread, and thought I'd help beacuse I hate being unreplied when I haev issues also ..

maybe this is the problem, first of all make sure your plug-in the FL vst isnt synced internally, and only synced on the host (ABleton) secondly , make sure that your global groove is set to 0 ... because sometimes it isnt and it delays the beat because thats what it does...

if not sorry I cant think of anything else good luck

Thanks for the reply man - no, there is no Global Groove set. However I'm not sure what you mean by "make sure your plug-in the FL vst isnt synced internally, and only synced on the host" - how do I do this? I just opened FL as a VSTi...

Does no one else have FL Studio missing the first beat in Ableton?

bumperoonie

I think there is a general bug with Live regarding the first note sometimes

but I'd also like to point out that FLStudio is up to v7 now so they may have changed alot in that time - and if you actually bought it (for the measily $99 US they ask! ) then it's free upgrades for life - always try the latest versions of software, especially if you are having probs

Ashmil wrote:Hey folks

I'm getting a slight problem using FL Studio 5 as a VSTi with Live 6. It all works fine apart from the fact that when I press play in Ableton, the first note/beat of anything I've got going on in FL (using its own pattern sequencers/piano roll) is missed the first time through the loop - it just doesn't sound. As the loop repeats, the first note/beat WILL be present - just not that very first one when I press play.

Does anyone have any info on this or know if it can be avoided?

Thanks

Ash

hmmmmmm... I don't know if i was having the same problem as you but... It turned out that the loop just won't play the note if is before the loop start point.If you recorded the note just a little bit ahead of the first beat, note doesn't play. I fixed the problem just by moving the first note, and then moving it back therefore snapping it exactly to 1 and then Live would play it just fine. Of course this only applies to loops you have notes that start on the 1. if it has trouble playing the first note if it doesn't start on the 1 then i have no idea what's going on with that.

I have this same exact problem all of a sudden. I have uninstalled and reinstalled countless times to no avail. Anything from 1.1.1 to 1.1.4 is not picked up at all, even the metronome incoming from FL Studio. Very annoying and inconvenient. I am using Live 6.0.10 and FL Studio 7 both with the most recent patches etc. And I am using the ReWire that comes with Live. I can not seem to find any information on how to fix this at all, or even if it can be (i hope so). The only thing I can seem to find is that I'm not the only one having this problem. Anyone have any suggestions besides the usual "uninstall completely" because I have done this with both Live and FL. Thank you in advance.

I have a Creative X-Fi Platinum sound card with the latest drivers including the latest ASIO drivers. Although this problem still occurs even with Direct X as the driver.

It's a Live issue, A lot of plugins use a small internal buffer to cut down CPU usage, and Live doesn't compensate for it. Some others affected include some NI plugins, XT2 and Zebra, to name a few.

There's a couple threads about the issue in the u-he forum at KVR, such as this one;

http://www.kvraudio.com/forum/viewtopic.php?t=187867

ew

So basically, it has been a well known, reproducible bug for a while now, they know it has to do with Live not compensating for a buffer and it affects a multitude of software, not just FL Studio, that Ableton advertises it works just fine in tandem with...yet it has no known fix or work around? That's not encouraging...