Cytomic "The Drop" Resonant Filter

[zerocrossing]

Ugh I liked this thread better when it was about filters and sound.

But to have it on record: the current system works fine, please don't switch to a dongle, that would suck.

And here's a thought experiment for you...

Someone uses Drop/Glue on their tracks. What happens next? THEY KEEP USING them. And they drool over your next plugin.

The only people selling these plugins are the ones not actually making music, so please do not punish your super happy customers by acquiescing to a vocal contingent of people who evidently don't appreciate your hard work.

Actually, no. This isn't the case. I bought The Drop. Most of the time I've owned it it was in beta. Between then and now I just didn't really find myself using it. I just don't use filter plug ins very much. So, I thought about selling it as other than checking out out, I really have yet to use it. (I also now have a DSP based system which I do much of my effect processing in). So... Anyway. I probably will keep it now because I just found out how much the transfer fee is, but I doubt I'll ever use it. I know. My bad.

[Lazylefteye]

Looking forward to the update too
The Drop and The Glue get lots of use here.
Keep up the good work.

[nrosko]

Thought i would check back here was not expecting an update as im sure you said more filter models were unlikely. Very excited now.

[btw]

Wow, that Wasp filter model sounds great. Very much looking forward to this update, and grateful for the continued improvements all around!

[andy-cytomic]

I would love to have already delivered the latest build, but I've not had enough clear work days to make much progress over the past couple of months for various reasons. It's also not looking so good over the coming weeks. Every spare moment I get I'm working on this build.

[Jax Pok]

Long as it takes I never paid for the extra filters it's great you add stuff for free Andy.

[Funkybot's Evil Twin]

Hi Andy, just got a 4k monitor on my laptop (running Windows 10) and the text on the "Windows style" pop up menus is very small. For example, the Presets/Load/Save menu, and the filter type menu. I've got good vision, so I can navigate them as-is without issue, but it would definitely be preferred if that text could be made a bit larger on 4k displays. The same is true for The Glue (where DC Block looked to me like Dr Block - maybe my eyesight is starting to go after all).

And don't stress about getting the next update out. I only hope whatever is keeping you busy is worthwhile.

[andy-cytomic]

Hi Andy, just got a 4k monitor on my laptop (running Windows 10) and the text on the "Windows style" pop up menus is very small. For example, the Presets/Load/Save menu, and the filter type menu. I've got good vision, so I can navigate them as-is without issue, but it would definitely be preferred if that text could be made a bit larger on 4k displays. The same is true for The Glue (where DC Block looked to me like Dr Block - maybe my eyesight is starting to go after all).

And don't stress about getting the next update out. I only hope whatever is keeping you busy is worthwhile.

Thanks for pointing out the issue. I'll check with the guys at Juce about scaling the menu properly on HiDPI displays, or at least checking some system metrics for how big to make it.

[pheeleep]

I finally got The Drop today. Yeah!!!

Seem to have found one bug in Fl Studio 12.2 64 bit. I have both realtime and render and set to x2.

If I change the render setting to a higher rate, the CPU increases drastically. This should not be the case, correct, since it's the render setting? I would expect the CPU to increase when I up the realtime setting (which of course it does).

Hmm I notice the same things happens with the Glue. If I set Render x1, I get the lowest CPU. If i switch render to x2, x4, et.. the CPU usage keeps going up. I had it set to x8 (recommended) but now I changed it to x1 and the CPU decreased. Are you just supposed to set it to x8 when you are ready to render? I thought that this was a "set it and forget" setting that did not affect realtime CPU use and that it would only turn on (and use CPU) when rendering (?) Thanks!

[andy-cytomic]

I finally got The Drop today. Yeah!!!

Seem to have found one bug in Fl Studio 12.2 64 bit. I have both realtime and render and set to x2.

If I change the render setting to a higher rate, the CPU increases drastically. This should not be the case, correct, since it's the render setting? I would expect the CPU to increase when I up the realtime setting (which of course it does).

Correct, the cpu should not change if you are on x2 realtime then setting any value of render should not make any difference from there.

Hmm I notice the same things happens with the Glue. If I set Render x1, I get the lowest CPU. If i switch render to x2, x4, et.. the CPU usage keeps going up. I had it set to x8 (recommended) but now I changed it to x1 and the CPU decreased. Are you just supposed to set it to x8 when you are ready to render? I thought that this was a "set it and forget" setting that did not affect realtime CPU use and that it would only turn on (and use CPU) when rendering (?) Thanks!

The only time render settings should change the realtime cpu is if realtime is set to x1 (off) since a small a delay needs to be added to the realtime signal to match it up with what the offline render will add in latency. What you report sounds like a bug, it sounds like Cytomic plugins aren't correctly detecting if FL Studio is offline or not, which is really odd since this is a very basic flag to check and it works in all other DAWs. I'll have a look and let you know.

[pheeleep]

Thanks Andy. The folks at image line are usually pretty responsive if you get in touch with them, but let me know if it would help you if I log this as a potential bug in the FL forum as well.

On another note, it seems I can set the render setting higher than the realtime setting but not vice versa. If I want to set realtime to x2 and render to X1 I can't (to circumvent this bug that is making the plugin use more CPU than it needs to when using the higher render settings)

[andy-cytomic]

Thanks Andy. The folks at image line are usually pretty responsive if you get in touch with them, but let me know if it would help you if I log this as a potential bug in the FL forum as well.

On another note, it seems I can set the render setting higher than the realtime setting but not vice versa. If I want to set realtime to x2 and render to X1 I can't (to circumvent this bug that is making the plugin use more CPU than it needs to when using the higher render settings)

Don't bother logging a bug on the FL forum until I debug things at my end, I have an extensive logging system that I can switch on to see what is going on easily, and this isn't a complicated issue to resolve.

It doesn't make sense to have a lower render setting than realtime so for convenience when you set the realtime to particular value the render will also switch to at least that value. This way you only have to change one setting if you don't want a higher quality render setting than realtime.

[pheeleep]

Thanks. I am 100% with you on why you normally wouldn't want a lower setting for render than for real time use. The only reason it would have been good for me in this case is because of this bug I am just setting both to x2 for now knowing that a little extra CPU is being used but not a big deal.

[pheeleep]

This info might help. I found a fix it seems.

In the Fl Studio wrapper, there is an option "Use fixed size buffers", when I checkmark it and click ok, then I can switch between all the render rates and the CPU does not change (same in the Glue).

The weird thing is, if I uncheck "Use fixed size buffers" afterwards, the issue remains fixed.

So, as soon as I insert the Drop, the problem occurs. However if I check and immediately uncheck "Use fixed size buffers", the problem is fixed, or, I can leave "Use fixed size buffers" on and the issue is also fixed.

I just found this fix and haven't had much time to mess around but I am not hearing any difference in the audio if "Use fixed size buffers" is selected so maybe I should just leave this on for your plugins (?)

[andy-cytomic]

This info might help. I found a fix it seems.

In the Fl Studio wrapper, there is an option "Use fixed size buffers", when I checkmark it and click ok, then I can switch between all the render rates and the CPU does not change (same in the Glue).

The weird thing is, if I uncheck "Use fixed size buffers" afterwards, the issue remains fixed.

So, as soon as I insert the Drop, the problem occurs. However if I check and immediately uncheck "Use fixed size buffers", the problem is fixed, or, I can leave "Use fixed size buffers" on and the issue is also fixed.

I just found this fix and haven't had much time to mess around but I am not hearing any difference in the audio if "Use fixed size buffers" is selected so maybe I should just leave this on for your plugins (?)

Cytomic plugins don't require fixed buffer sizes so please leave this option off. You get more accurate automation if the host can split buffer sizes wherever it wants to, only poorly written plugins require a fixed buffer size to work around bugs in the plugin. Overall this sounds like a bug in FL Studio to me since if the plugin works properly when you change a setting in Fl Studio then it sounds like FL Studio is not correctly reporting the offline status when the fixed buffer size is set.