FL Studio 21.1 released! - A disappointment in the making

[donkey tugger]

Seems to be different if you have 'quantize song jumps' enabled here, but can't remember how it worked before with it enabled.

That is the purpose of the option. To wait until the setting snap unit before jumping or relocating. Off to Beats or Bars e.t.c.

Yeah, I know that, but what you can't do with it enabled is move the starting position. That's mebbe the issue here.

[_al_]

Made a post in tech support and some guy called Hevy is trying to tell me that it has always worked like that.

Can you post his exact advice? Because relocating while playing works here and had always worked like that. Nothing has changed.

Yes, relocating works, but the moment you push space, the song immediately jumps back to the position it was in when you last pushed play.

Before this update, I could be working in a looped area (lets say bar 80), and when finished editing, I could simple double click at 73 while song was playing.
This would begin playback at 73, remove the loop at 80 and ALSO change the playback start position to 73 (as it was previously at 80 when working in the loop)

But now, I click at 73, and the moment I push stop, it jumps back up to 80!

I promise you bro, it has never done that

[Carbonboy]

Made a post in tech support and some guy called Hevy is trying to tell me that it has always worked like that.

Can you post his exact advice? Because relocating while playing works here and had always worked like that. Nothing has changed.

Yes, relocating works, but the moment you push space, the song immediately jumps back to the position it was in when you last pushed play.

Before this update, I could be working in a looped area (lets say bar 80), and when finished editing, I could simple double click at 73 while song was playing.
This would begin playback at 73, remove the loop at 80 and ALSO change the playback start position to 73 (as it was previously at 80 when working in the loop)

But now, I click at 73, and the moment I push stop, it jumps back up to 80!

I promise you bro, it has never done that

Are you aware of the setting on the stop button right-click - Remember seek time?

Sounds like its switched on and it was off before.

Now I really want to see your technical support conversation can you post a link. I can't believe the ts guys there would miss that.

[xbitz]

share it here too, maybe

Képernyőfotó 2023-09-07 - 21.42.24.png

https://syntheticorchestra.com/tools/articulate/

I've totally missed the mac release

[osiris]

I notice the update I downloaded included a copy of ASIO4All v2. So it actually works. Problem is when I use it audio won't output through the headphones, just the speakers. I'm sure it's a Windows setting. The latency you can set it to is insanely low.

[_al_]

Are you aware of the setting on the stop button right-click - Remember seek time?

Sounds like its switched on and it was off before.

Now I really want to see your technical support conversation can you post a link. I can't believe the ts guys there would miss that.

Yeah, switching off remember seek time is actually worse, because the start time always returns to song start, so it wasn't that.
I still have FL20 and FL21 installed, and they both exhibit different behaviour. FL20 still works as I remember it.

As for posting a link to TS, I've posted 2 vids in there, which contain my personal information, so I asked them to keep the post in Private Mode (apparently that's a thing).

However, with all that said, today Hevy posted a vid of FL behaving as it is supposed to!
The first video he posted, he cheated by quickly pushing stop/start before moving start position (I noticed the play button flicking quickly), but today he posted a vid of him changing start time without FL stopping.
So either they already have a hotfix for it, or it is simply a problem on my comp, which seems unlikely, as I've been using FL since V9, and this doesn't look like a problem that can be caused by hardware (imo)

So atm, I'm not sure if I should be happy they have found the problem, or worried that it's specific to my comp lol

Either way, I'm happy for the prompt response from them

[kingozrecords]

What's kept me on edge is having to rely on fl studio 11 for a sample accurate edison that belies pops and churks taking place in the mix. The older edison was sample accurate and did not need editing after the fact, no matter your cpu usage and how bogged down you are.

I also point out that midi / synth automation and de-selected synths still remain in memory; so what is the point of even bouncing a track. That function had worked before I tried one of the latest versions. Really disappointing, and I don't often have time to point out these bugs.

[Carbonboy]

so what is the point of even bouncing a track.

Because there will much less CPU load playing a sample vs generating one live.

If you use smart disable, the plugins will also stop using even more CPU.

[Carbonboy]

To be fair to Image Line you seem to be changing your problem and not making a lot of sense

Before this recent update, it was always possible to change playback start position while the song is playing. But now... I literally have to push space, click the timeline, and push space again.

This is fixed by deselecting "Quantize song jumps"

Yes, relocating works, but the moment you push space, the song immediately jumps back to the position it was in when you last pushed play.

This is fixed by deselecting "Remember seek time"

You should do a clean install. What I don't understand how this is Image-Lines fault and is "ridiculous".

You can paste the support response here. I don't see how they are cheating" you.

[kingozrecords]

so what is the point of even bouncing a track.

Because there will much less CPU load playing a sample vs generating one live.

If you use smart disable, the plugins will also stop using even more CPU.

Doesn't work sadly; and I've been using the image-line's products for twenty years.

[osiris]

It's true. I've bounced and loaded a bunch of tracks and it makes FL huff and puff. Same thing barely affects Reaper. Smart Disable is good. Setting Max Polyphony to 1 on every VST even better.

[Carbonboy]

Doesn't work sadly; and I've been using the image-line's products for twenty years.

Of course it works. Sounds like you still left the plugin receiving note input and playing while muted.

[_al_]

To be fair to Image Line you seem to be changing your problem and not making a lot of sense

Before this recent update, it was always possible to change playback start position while the song is playing. But now... I literally have to push space, click the timeline, and push space again.

This is fixed by deselecting "Quantize song jumps"

Yes, relocating works, but the moment you push space, the song immediately jumps back to the position it was in when you last pushed play.

This is fixed by deselecting "Remember seek time"


You should do a clean install. What I don't understand how this is Image-Lines fault and is "ridiculous".

You can paste the support response here. I don't see how they are cheating" you.

Wow, you fixed the problem that Image Line couldn't.
Quantize song jumps was the problem, and I can't believe Support didn't know that one!
So although you seem pretty rude and arrogant, I will indeed thank you for fixing that one.

I even remember trying that out a little while ago, so I'm not sure how I didn't connect those two things.

Remember seek time... nope. Never touched that, never will.

Not sure how you think I changed my story though. It's been the same single problem from the start?
And Image Line cheating? um, not quite. Hevy just failed to follow the steps properly when trying to replicate the problem, but I later agreed that the problem might be specific to my comp.
So I'm not sure why you still decided to get your panties in a twist.
You solved the problem. If that's not enough to satisfy you, then um... good luck

Thanks again though

To be honest though... why the hell would quantize song jumps have any effect on whether or not we can change start position during playback??
If there's anything that doesn't make sense, it's that. I'm not surprised I didn't connect that

[osiris]

This is the thing, I think it's a waste of CPU and GPU to just have 99 tracks (or whatever it is) up all at once. I think this is why Reaper handles things differently. I wish FL would open with a Master Track and one insert. Then there should be an option to add a track. No add a Midi Track or the other insane BS other DAWS make you jump through. Just add a track. Maybe add an Insert Track option as well. I've done hellacious CPU intensive stuff in FL and watched my laptop struggle as FL goes through saving all 99 tracks even though I may be only using 12 of them.

[Dionysos]

This is the thing, I think it's a waste of CPU and GPU to just have 99 tracks (or whatever it is) up all at once. I think this is why Reaper handles things differently.

Surely FL optimises this away internally and doesn't actually process tracks that are not in use.

That said, IL are working on changing the mixer architecture to enable the model you describe.