FL Studio 2024.1 available... hehehe

[Teksonik]

I don´t know if you really read them...
about 60% of them are whining why their license name was now replaced by the license plate if they even have understood what that means, tons of errors about FL Cloud/cloud plugins misbehaviour which doesn´t interest me at all and a few problems with some plugins like Soundtoys which seems to be not IL´s fault...

On page 4 alone there are five or more reports.

Whether it's stable for you or me is not the point. It's how the larger user base is affected and the reputation of FL as having been relatively bug free in past release versions.

Look, I know you're just in "defense of DAW" mode and that's fine. But your defense actually works against the reputation of the company you're defending. I'm saying that in the past their release versions have had much better quality control irregardless of what was added or changed and I go back over 20 years to make that comparison. So I'm actually complimenting them while expressing some disappointment in the QC of this release.

I'm not an FL hater although it does fall short for my needs but all I'm saying is there should have been more RCs before calling it a release. It would have saved me time beta testing a release version and making an error report that was until yesterday ignored.

EDIT: Here's another one:

Load an empty project then load an FPC with a kit.
Put some notes in the PR on the Hi Hat Closed for example then apply Note Repeat
Load another generator and add a note in its PR.
The last Note Repeat value is applied to that note as well.
Expected result is that note repeat value should not be remembered. It should default back to zero.

Also trying to apply Note Repeat when notes are stacked, for example Snare and Hat on the same beat is very fiddly. Clicking on the adjustment node sets the same value for both notes.

[osiris]

I don't know if it's a bug and maybe need to report, maybe it's the way it is, but when I use the Chord Progression tool I can't edit the notes it puts in the Piano Roll individually. I tried everything yesterday but they are all grouped as a chord. Delete one, the all go. Try to move one, they all move.

[carrieres]

I don't know if it's a bug and maybe need to report, maybe it's the way it is, but when I use the Chord Progression tool I can't edit the notes it puts in the Piano Roll individually. I tried everything yesterday but they are all grouped as a chord. Delete one, the all go. Try to move one, they all move.

The notes are just automatically grouped so all you have to do is going into the PR menu to ungroup or hit ALT+G

[Dionysos]

You can also disable note & clip grouping globally in the toolbar by clicking this chain icon:


Then you don't need to manually ungroup anything.

[Trancit]

...
EDIT: Here's another one:

Load an empty project then load an FPC with a kit.
Put some notes in the PR on the Hi Hat Closed for example then apply Note Repeat
Load another generator and add a note in its PR.
The last Note Repeat value is applied to that note as well.
Expected result is that note repeat value should not be remembered. It should default back to zero.

Also trying to apply Note Repeat when notes are stacked, for example Snare and Hat on the same beat is very fiddly. Clicking on the adjustment node sets the same value for both notes.

The first one isn´t a bug... it´s part of FLS´system that the properties of the last touched note are the default properties for new notes...
I.e. if you edit anything from the control pane in the PR editor (velocity, panning, ModX /Y and now as well note repeat) and you insert a new note it gets automatically these edited values for it...
You have to open the note properties window and ALT click every parameter to get back the "normal" defaults
An absolute shitty behaviour but not a bug... was always like this... sadly!

The second one I don´t really understand... luckily I have no use for this note repeat thingie... so I am safe...

[Teksonik]

it´s part of FLS´system that the properties of the last touched note are the default properties for new notes...

Yes this is just another example of the stupid way FL handles things. How many times are you going to want to add note repeat at the same value on consecutive notes and more importantly on different generators?

You add note repeat on a hi hat then load a bass synth and it adds the same note repeat value to the next note entered. The only solution there is to go back and manually select no repeat value. Stupid.

Yes I understand that note lengths are remembered even between sessions but since you're far more likely to use notes in a composition than note repeat (by your own admission) then note repeat should not follow the "remember last value" paradigm.

If you had actually used note repeat you would have realized the fault in no time. Why it wasn't caught in Alpha or even Beta just reinforces my opinion....sloppy.


As for the second part. The image shows two stacked notes with different repeat values. Clicking anywhere to adjust one value automatically causes both values to jump to that point. Same with velocity. Sloppy.

FL 070324-1.png

[osiris]

I hate those pin bars. HATE.

[MrJubbly]

As for the second part. The image shows two stacked notes with different repeat values. Clicking anywhere to adjust one value automatically causes both values to jump to that point. Same with velocity. Sloppy.

FL 070324-1.png

You have a couple of options. Either place your mouse pointer over the specific note you want to change the parameter value of and hold down ALT + Scroll-wheel up or down to change JUST that note's parameter value (or CTRL + ALT for fine adjustments).

Alternatively, just select the note(s) you want to alter first and then use the standard Left-click and mouse to drag JUST that note's parameter value, without altering the other notes.

[Trancit]

Yes this is just another example of the stupid way FL handles things. How many times are you going to want to add note repeat at the same value on consecutive notes and more importantly on different generators?

You add note repeat on a hi hat then load a bass synth and it adds the same note repeat value to the next note entered. The only solution there is to go back and manually select no repeat value. Stupid.

Yes I understand that note lengths are remembered even between sessions but since you're far more likely to use notes in a composition than note repeat (by your own admission) then note repeat should not follow the "remember last value" paradigm.

100% agree... Note length are ok and there is a modifier (Shift + left click with pencil or brush) to insert a new note with the length of the current quantize setting but to clone the note controls is perhaps the most dumb idea ever and doesn´t make any sense at all...

As for the second part. The image shows two stacked notes with different repeat values. Clicking anywhere to adjust one value automatically causes both values to jump to that point. Same with velocity. Sloppy.

You need to select the note(s) you want to edit first... then clicking in the control pane just affects the selected note...
But this behaviour I find quite normal... how would you define which one to edit other way??

[Caine123]

i didnt test FL24 yet, seems very buggy atm.

[osiris]

Maintenance update already.

[Teksonik]

As for the second part. The image shows two stacked notes with different repeat values. Clicking anywhere to adjust one value automatically causes both values to jump to that point. Same with velocity. Sloppy.

You have a couple of options. Either place your mouse pointer over the specific note you want to change the parameter value of and hold down ALT + Scroll-wheel up or down to change JUST that note's parameter value (or CTRL + ALT for fine adjustments).
Alternatively, just select the note(s) you want to alter first and then use the standard Left-click and mouse to drag JUST that note's parameter value, without altering the other notes.

Thanks but I'm aware of the options, it's the specific behavior in the lane I'm pointing out. I don't use key modifiers because my qwerty boards sits behind my midi keyboard as it should so is not convenient to use.

Clicking on the node of one note in the lane should not change the value of other notes.

[Teksonik]

You need to select the note(s) you want to edit first... then clicking in the control pane just affects the selected note...
But this behaviour I find quite normal... how would you define which one to edit other way??

No that doesn't work (for stacked notes on the same beat). Selecting a note still does not change the behavior in the note properties lane. Clicking the node of the selected note still causes values of all other notes to jump to the same point and resets all their values to the same amount.

The expected behavior would be that selecting the node of one note value in the lane should not set the values of all other notes.

It's been that way for a long time so I don't expect it to change for velocity but for note repeat it should default to zero regardless of the last value used because again it's not something that will be used on every note or in every generator.

[osiris]

Thanks for the unglue tip. I did have that on.

[Trancit]

No that doesn't work (for stacked notes on the same beat). Selecting a note still does not change the behavior in the note properties lane. Clicking the node of the selected note still causes values of all other notes to jump to the same point and resets all their values to the same amount.

...

Perhaps we are talking about different things... this is how I understand it and it works fine here: