Upgrade FL or Buy energyXT?

[arke]

I'm not a discovery user but I'm certainly glad to see discoDSP and IL work together on this to get this fixed as quick as possible. I'm sure it'll get fixed as quickly as possible.

[JMC]

I already reported clearly the situation about FLS samples (saving) handling :

- put a sample on your desktop (eg one you just downloaded from the web)
- load it in fls sampler channel or slicer
- delete it from your desktop
- save the fls project as FL zipped loopfile
- surprise : the sample isnt in the zipfile, while fls still plays it (its in "fls ram")
- you get no message, nothing telling you the sample hasnt been saved

Last time i told you this, you said "you arent serious, right ?" or something like that.

Although I aggree the slicer should at least turn red like a sampler channel (and I'll ask our developers to check this out and change it) I can only repeat that you have to be at least a little cautious when you start deleting samples & loops you need/want (or save a zipped package *before* you start doing this).

I just checked and there there are plenty of places in FL (audioclips, granuliser, wavetraveller, scratcher, ...) and other apps that don't lock or care about the source material that you're using. A website generator won't notice if you delete the images that you link in your projects either.

See ya,

jmc (FL Studio)

[geoslake]

I already reported clearly the situation about FLS samples (saving) handling :

- put a sample on your desktop (eg one you just downloaded from the web)
- load it in fls sampler channel or slicer
- delete it from your desktop
- save the fls project as FL zipped loopfile
- surprise : the sample isnt in the zipfile, while fls still plays it (its in "fls ram")
- you get no message, nothing telling you the sample hasnt been saved

Last time i told you this, you said "you arent serious, right ?" or something like that.

Although I aggree the slicer should at least turn red like a sampler channel (and I'll ask our developers to check this out and change it) I can only repeat that you have to be at least a little cautious when you start deleting samples & loops you need/want (or save a zipped package *before* you start doing this).

I just checked and there there are plenty of places in FL (audioclips, granuliser, wavetraveller, scratcher, ...) and other apps that don't lock or care about the source material that you're using. A website generator won't notice if you delete the images that you link in your projects either.

See ya,

jmc (FL Studio)

But i AM very cautious
I was just suggesting/asking if FLS shouldnt save properly loaded samples (?)
I mean, once the sample IS inside FLS, why does FLS need to access the HD to save it ?

Thanks for taking care of the Slicer missing warning

[YellowJacket]

As Discovery is my "go-to" VA synth (I highly recommend it if you haven't tried it yet), FL6 isn't working for me at present. Hope the problem is fixed soon -- otherwise, the choice will be energyXT or something else. Does anyone have any alternate suggestions?

Thanks,
YellowJacket

[geoslake]

As Discovery is my "go-to" VA synth (I highly recommend it if you haven't tried it yet), FL6 isn't working for me at present. Hope the problem is fixed soon -- otherwise, the choice will be energyXT or something else. Does anyone have any alternate suggestions?

Thanks,
YellowJacket

Yep : FLS 5.02

[lunik]

absolutely crock

I was directed to the appopriate threads and have now happily exported my midi

The new 'replace channel' command is worth the update alone for me... saved me much tedious work I had been putting off for weeks.

Unfortunately FL won't let you export midi into another host.

*CROCK ALERT*

[ceenda]

The new 'replace channel' command is worth the update alone for me... saved me much tedious work I had been putting off for weeks.

Yes!

In particular, when importing a MIDI, it created lots of MIDI Out generators that had to be replaced by Cut & Pasting the pattern content from each one.