Cableguys ShaperBox 2 Released | VST 3 + Winter Sale Now On

VST, AU, AAX, CLAP, etc. Plugin Virtual Effects Discussion
Post Reply New Topic

Post

The demos/presentation included in the dev site is superb.
That’s great, because the CG stuff need more than average focus from user to get best out.
More stuff like that.

Post

zvenx wrote: Wed Nov 18, 2020 12:36 pm That doesn't happen to me on mac or pc in cubendo.
Sorry.
rsp
Maybe it's related to the gpu / opengl ??? I'm using an ATI card. I'll soon test Spaperbox on my other computer that has an Nvidia card.

Post

How old is your video card?
Amd bought ATI in 2010 and I think the brand was retired since then.

I myself have an AMD card (Radeon HD7700)..

rsp
sound sculptist

Post

zvenx wrote: Wed Nov 18, 2020 1:06 pm How old is your video card?
Amd bought ATI in 2010 and I think the brand was retired since then.

I myself have an AMD card (Radeon HD7700)..

rsp
I found the problem! It's related to the scaling options. I can remember that i already mentioned that one year ago.

If you set the UI scale to 100% the editor behaves very direct and smooth. If you scale the UI up to 175% it gets laggy. I have a certain distance to my screens (because of some hardware controllers) That's why i always scale up plugins that offer such options. Unfortunatly that keeps me away from loading up Shaperbox into a project. Most of the time i'm satisfied with Xfers LFO Tool. A shame, as the new crusher module and the latest improvements in Shaperbox are extremly interesting :(

Post

I use it at 150% on mac and PC (on my system, anything higher is greyed out)
rsp
sound sculptist

Post

zvenx wrote: Wed Nov 18, 2020 2:03 pm I use it at 150% on mac and PC (on my system, anything higher is greyed out)
rsp
On my sytem 200% is greyed out. Seems that the plugin only offers scales that fit into your screen size/resolution, so that it doesnt get larger than your window.

Anyway ... i hope they adress this issue. Even at 100% the editor could behave a bit more direct or snappy. If you find the time you should demo LFOtool to see what i mean. But to be fair: Xfer's graphical editors in Serum and LFO tool are the best. Seems i'm a bit to spoiled in that way :oops:

Post

I have LFOTool (and Serum).... I honestly don't see a difference in their behaviour in terms of snappiness on either my pc or mac.
rsp
sound sculptist

Post

zvenx wrote: Wed Nov 18, 2020 2:33 pm I have LFOTool (and Serum).... I honestly don't see a difference in their behaviour in terms of snappiness on either my pc or mac.
rsp
The difference is very marginally, but somehow i prefer Xfers editors. I would be completly satisfied if the Cableguys sort out that laggy behavior in the scaled modes, because Shaperbox per se is an awesome toolbox and can do things that LFOtool cant :pray: :pray: :pray:

Post

I assume you have written support? Since it might turn out to be an issue for a very few users that they may not be aware of.
rsp
sound sculptist

Post

Thank you for bringing this up! Indeed, it's something we're aware of on certain Windows systems for scalings of more than 100%.

The issue depends a lot on which DAW you’re using, and it can be worse when 2 or more ShaperBox windows are open.

To work around the issue in the meantime, open only 1 ShaperBox UI at a time. If that doesn’t solve it, please scale to 100% and/or disable the oscilloscope (via the right-click menu in the Wave Editor, or the “three dots” in the tool bar).

Post

Lee / Cableguys wrote: Wed Nov 18, 2020 3:24 pm Thank you for bringing this up! Indeed, it's something we're aware of on certain Windows systems for scalings of more than 100%.

The issue depends a lot on which DAW you’re using, and it can be worse when 2 or more ShaperBox windows are open.

To work around the issue in the meantime, open only 1 ShaperBox UI at a time. If that doesn’t solve it, please scale to 100% and/or disable the oscilloscope (via the right-click menu in the Wave Editor, or the “three dots” in the tool bar).
My DAW is Cubase 10.5.20. Disabeling the Osciloscope doesnt help and the issue also appears even when using just one instance.

BTW: I sent you a message via contact form on your website, regarding that issue. You can ignore it :) We can discuss this here, if you want to ... might be interesting to other useres as well.

Post

Seems they are aware of it :)
rsp
sound sculptist

Post

Lee / Cableguys wrote: Wed Nov 18, 2020 3:24 pm To work around the issue in the meantime, open only 1 ShaperBox UI at a time. If that doesn’t solve it, please scale to 100% and/or disable the oscilloscope (via the right-click menu in the Wave Editor, or the “three dots” in the tool bar).
Disabling the oscilloscope actually helped on my system so many thanks for the hint :tu:
Sound C loud
Band C amp
Clicks and pops is all I get

Post

Some more info on that: Our ShaperBox UI is slowest in Cubase, definitely (on some computers.. it can work perfectly on others). We're not using OpenGL on Windows (we do on macOS). That's because we had quite some issues with OpenGL with some DAWs.

We had been in the middle of working on it, but then decided to first work on Big Sur compatibility for Curve, FilterShaper, MidiShaper and Kickstart - they kinda work, but not perfectly (ShaperBox and HalfTime are all fine, and the others will be too in a bit..), as well as work on native Mac Silicon / ARM / M1 support. Well, Apple can really keep you busy..
Last edited by Jakob / Cableguys on Wed Nov 18, 2020 5:20 pm, edited 1 time in total.

Post

Jakob / Cableguys wrote: Wed Nov 18, 2020 5:03 pm We had been in the middle of working on it, but then decided to first work on Big Sur compatibility for Curve, FilterShaper, MidiShaper and Kickstart - they kinda work, but not perfectly (ShaperBox and HalfTime are all fine, and the others will be too in a bit..), as well as work on native Mac Silicon / ARM / M1 support. Well, Apple can really keep you busy..
I swear, if I were a developer I'd offer two licensing options:

1. Windows only
2. Windows+Mac (costs $10 more)

Why? Because of stuff like that. If Apple's going to make developers spend countless hours recording plugins on a regular basis, the price for Mac plugins should reflect that difference. If enough developers did that and explained the cost, it may give users pause before thinking about buying that next Mac, while also allowing you guys to recoup some Mac development costs that you don't incur as regularly on the Windows side without penalizing those users.

Post Reply

Return to “Effects”