FLStudio 6.0.8 is up

[diverdee]

Cool - shows that IL are hard at work fixing things up.
Dunno what their beta program is like - but at least when there are problems they set to to sort them out (although the different versions do seem to be coming out thick & fast, 6.09 prolly came out whilst I was typing this).

[ouroboros]

at looptalk, the updates listed are:
6.05
then
6.08 : you didn't miss any, they just skipepd some numbers.

[ulozilla]

JMC, Gol, etc:
Has the UVI bug been fixed?

oh yes....and the superwave BUG?

[james0tucson]

looks like they had a lot of iterations fixing the ridiculous chrome-crash problem. And it appears IL has a LOT riding on DirectWave. Everything about this whole FL6 release from the beginning has had something about DW. I haven't even loaded the demo. I'm not even sure I know what DW *is*. Yet another sampler to further cloud the confusion about sample formats, that's all I see. Maybe it will load ST2 samples and be a better player than STLE. Or maybe it means I can buy one of the popular pianos or orchestral sets and not have to buy Kontakt or whatever. But I don't know.

[Shane Sanders]

looks like they had a lot of iterations fixing the ridiculous chrome-crash problem. And it appears IL has a LOT riding on DirectWave. Everything about this whole FL6 release from the beginning has had something about DW. I haven't even loaded the demo. I'm not even sure I know what DW *is*. Yet another sampler to further cloud the confusion about sample formats, that's all I see. Maybe it will load ST2 samples and be a better player than STLE. Or maybe it means I can buy one of the popular pianos or orchestral sets and not have to buy Kontakt or whatever. But I don't know.

I was able to make a fairly cool/musical sound out of a single vacuum cleaner sample with DirectWave. It's fairly straightforward as far as samplers go. Give it a shot.

[serge]

looks like they had a lot of iterations fixing the ridiculous chrome-crash problem. And it appears IL has a LOT riding on DirectWave. Everything about this whole FL6 release from the beginning has had something about DW. I haven't even loaded the demo. I'm not even sure I know what DW *is*. Yet another sampler to further cloud the confusion about sample formats, that's all I see. Maybe it will load ST2 samples and be a better player than STLE. Or maybe it means I can buy one of the popular pianos or orchestral sets and not have to buy Kontakt or whatever. But I don't know.

I was able to make a fairly cool/musical sound out of a single vacuum cleaner sample with DirectWave. It's fairly straightforward as far as samplers go. Give it a shot.

Shane, lets hear it

[Penis Arcade]

JMC, Gol, etc:
Has the UVI bug been fixed?

You in particular have been informed a countless number of times that UVI engine does not support full VST spec - namely, variable size buffers. For this to be resolved you will need to contact makers of UVI engine. It will not be fixed by Image Line who feel pretty strongly about compromizing their code to support every poorely written plugin out there.

So unless you have some new information about what specifically FL does wrong, you can expect that UVI bug can only be fixed by those who made it.

[diverdee]

But UVI engine plugs work ok in all the other hosts?
Or am I incorrect in assuming that, it's just I've only ever seen FL users reporting these problems.
But it's not FL's problem though...... obviously.

[Shane Sanders]

looks like they had a lot of iterations fixing the ridiculous chrome-crash problem. And it appears IL has a LOT riding on DirectWave. Everything about this whole FL6 release from the beginning has had something about DW. I haven't even loaded the demo. I'm not even sure I know what DW *is*. Yet another sampler to further cloud the confusion about sample formats, that's all I see. Maybe it will load ST2 samples and be a better player than STLE. Or maybe it means I can buy one of the popular pianos or orchestral sets and not have to buy Kontakt or whatever. But I don't know.

I was able to make a fairly cool/musical sound out of a single vacuum cleaner sample with DirectWave. It's fairly straightforward as far as samplers go. Give it a shot.

Shane, lets hear it

I had posted it a night or two after the FL6 debut, but since then I've changed servers for all my sites. I don't know where the file or sound is at the moment. I was just goofing off. Maybe I'll think to look for it again later on. My memory is bad, though.

[ouroboros]

I was able to make a fairly cool/musical sound out of a single vacuum cleaner sample with DirectWave. It's fairly straightforward as far as samplers go. Give it a shot.

Shane, lets hear it

I heard it; it sucked.

[birrbits]

I was able to make a fairly cool/musical sound out of a single vacuum cleaner sample with DirectWave. It's fairly straightforward as far as samplers go. Give it a shot.

Shane, lets hear it

I heard it; it sucked.

I heard he bagged it

[arguru]

But UVI engine plugs work ok in all the other hosts?
Or am I incorrect in assuming that, it's just I've only ever seen FL users reporting these problems.
But it's not FL's problem though...... obviously.

Majority of hosts uses a fixed size for their mixing main process function and VST rendering, this is, they render a fixed amount of samples all the time, wich should also be equal to the asio preferred buffer size, so it's not a surprise such UVI thing work in most other hosts.

But the VST process function have a parameter wich specifies the desired number of sampleframes to render, wich results in a inconsistency in the SDK, because in one side, you have a reported fixed buffer (block size) and in the other a parametric 'size' for process function.

The right common sense for a plugin developer SHOULD BE support whatever "sampleframes" number is specified in the process parameter and AVOID RELYING CRITICAL PARTS of the plugin in trusting that "reported block size" wont change.

In fact, VST reported block size is plain stupid and useless if your rendering process function have a lenght parameter. This is Steinberg's fault.

I guess FL Studio takes advantage of a variable-sized process calls to align sequencer events within sample accurate precission, wich in theory, is a perfectly safe method.

If such UVI thing crash due to this reason, is because not taking care of the above.

Conclusion: ImageLine is doing fine in not bloating their host to support poorly written engines.

[Teksonik]

Arguru, can you explain why DiscoDSP's Discovery has suddenly stopped working in FL6? Worked fine in FL5.

Just to be clear I'm not trying to be a smart ass. Just hoped you might be able to shed some light on the FL-Discovery issue. If I remember correctly you are/were involved with DiscoDSP.

[diverdee]

Thanks for the explanation Arguru, I know virtually nothing about DSP - but it kind of made sense.
So the UVI engine problem is due to the fact that the UVI plugins have IYO badly written code, but this isn't a problem with any other host - as they also have badly written code, or at least don't follow the VST SDK spec. (or whatever) correctly - but IL & FL do.... but only they do.... only they do it correctly.... that's why those particular plugins don't work in FL.... it's their fault.... & the reason they work in other hosts is because they're all 'wrong' also.... but wrong in the same way, a way that allows the UVI engine plugins to work correctly..... & that's why the UVI engine plugins don't work in FL, because FL is 'right'... so it doesn't work.
m'kay.

[serge]

I was able to make a fairly cool/musical sound out of a single vacuum cleaner sample with DirectWave. It's fairly straightforward as far as samplers go. Give it a shot.

Shane, lets hear it

I heard it; it sucked.

I heard he bagged it

makes sense