Tone2 Gladiator 2.6 update

[Ingonator]

Thanks for the naming bug heads up!

Neither in Live 9.6 nor Logic X Pro 10.2.2 (Mac OS 10.9.5) will Gladiator 2.6 allow any renaming of patches. Whatever I type, using SHIFT or not, nothing appears in the Name field which stays blank.

I'm seeing the UI response has gone to total crap. Slllooooooooower than a slug in molasses in January. CPU use is fine. I'm on a garden variety Dell running the latest Windows. It's become unusable.

Renaming seems to work here with Live 9.7.1 64-bit at Windows 10 64-bit and i also do not notice a slow GUi there.

UPDATE:
The 64-bit VST2 plugin of Gladiator 2.6 besides Live 9.7.1 64-bit also seems to work properly here in Cubase Pro 9.0.10, Studio One 3.3.4 64-bit, Bitwig 1.3.16 (full version) and Bitwig 2.0 (demo version) too.

[ENV1]

I remember seeing plugins not taking certain characters too once or twice. I cant recall their names or type anymore, (could have been synths or effects or both), but if i remember correctly i was able to type the no-show characters when i held down CTRL or ALT. (Dont recall which. Could have been both but i dont believe so.)

So if you havent tried that yet, give it a shot.

It might not work in every case but i know it does at least in some cases.

[zvenx]

Lfo changing shape works fine in sierra on cubase 9.
However the rename (which I have never used before) doesn't seem to be working, cubase is stealing all the keyboard entries as I try to type any rename name.

rsp

I don't have any GUI issues thus far either on my mac or pc with 2.6
rsp

Try this (just to confirm):

Select any preset.. then hit the "rename button" and type 'mmmmmmkay'. Does it allow you to type the letter 'm' into the naming field?

Also, try moving through the LFO shapes quickly and see if the mouse clicks are properly registered. So if you go 'click, click, click', do the LFO shapes actually change at the same pace? For me it's lagging behind.. seemingly randomly.

Note: This could all be related to Reaper + Gladiator 2.6.. some kind of odd combination. Once I get back to work I'll try it in other DAWs as well and see if the problem persists.

[zerocrossing]

Thanks for the naming bug heads up!

Neither in Live 9.6 nor Logic X Pro 10.2.2 (Mac OS 10.9.5) will Gladiator 2.6 allow any renaming of patches. Whatever I type, using SHIFT or not, nothing appears in the Name field which stays blank.

I'm seeing the UI response has gone to total crap. Slllooooooooower than a slug in molasses in January. CPU use is fine. I'm on a garden variety Dell running the latest Windows. It's become unusable.

Renaming seems to work here with Live 9.7.1 64-bit at Windows 10 64-bit and i also do not notice a slow GUi there.

UPDATE:
The 64-bit VST2 plugin of Gladiator 2.6 besides Live 9.7.1 64-bit also seems to work properly here in Cubase Pro 9.0.10, Studio One 3.3.4 64-bit, Bitwig 1.3.16 (full version) and Bitwig 2.0 (demo version) too.

Hm, I tried it in Bitwig (the light version) and it was fine. Retried it in Live and it's still the same. Very slow.

[robindrieghe]

lfo works great in flstudio,renaming not.

[replicant X]

deleted

[Caine123]

installed the v2.6 yesterday and all was running well so far! didnt a/b test the sound yet.

for the renaming issues i got an official reply from Markus, i didnt test the renaming myself yet:

"The 'rename patch' function can only work properly if the host supports submitting keypresses to the plugins. That's why it wrote in the patch notes:

"- In the Mac version patches can now be renamed from within the plugin (if the host supports it)"

What does happen if the host does not support it?
No or not all keypresses are submitted to the plugin.
Example: Orion does not submit the space key to the plugin. The 'space' key is assigned as a hotkey in the host for start/stop playback. If you type in 'new name' only 'newname' will be received by the plugin, since the host does submit it to Gladiator.

What can you do to solve the issue?
Please do note that this is not a bug in Gladiator. For technical reasons this problem can not be solved from the plugin's companies site. It does affect also many plugins from other companies.
The problem is a host issue. The host does not forward keyboard input properly to the plugins.
Contact the host's company and request a support for submitting keyboard input to the plugins."

[D N A]

One of the most fun synth to create presets for Need to reinstall it

[bmanic]

installed the v2.6 yesterday and all was running well so far! didnt a/b test the sound yet.

for the renaming issues i got an official reply from Markus, i didnt test the renaming myself yet:

"The 'rename patch' function can only work properly if the host supports submitting keypresses to the plugins. That's why it wrote in the patch notes:

"- In the Mac version patches can now be renamed from within the plugin (if the host supports it)"

What does happen if the host does not support it?
No or not all keypresses are submitted to the plugin.
Example: Orion does not submit the space key to the plugin. The 'space' key is assigned as a hotkey in the host for start/stop playback. If you type in 'new name' only 'newname' will be received by the plugin, since the host does submit it to Gladiator.

What can you do to solve the issue?
Please do note that this is not a bug in Gladiator. For technical reasons this problem can not be solved from the plugin's companies site. It does affect also many plugins from other companies.
The problem is a host issue. The host does not forward keyboard input properly to the plugins.
Contact the host's company and request a support for submitting keyboard input to the plugins."

Well, Markus is wrong. Reaper has an option that transfer ALL key presses to the plugin. 'm' key still doesn't work.. besides, it was working just fine in the previous version of Gladiator and works just fine in Electra X (and original v1.0 of Gladiator which I still have installed).

It's definitely buggy.

[Caine123]

installed the v2.6 yesterday and all was running well so far! didnt a/b test the sound yet.

for the renaming issues i got an official reply from Markus, i didnt test the renaming myself yet:

"The 'rename patch' function can only work properly if the host supports submitting keypresses to the plugins. That's why it wrote in the patch notes:

"- In the Mac version patches can now be renamed from within the plugin (if the host supports it)"

What does happen if the host does not support it?
No or not all keypresses are submitted to the plugin.
Example: Orion does not submit the space key to the plugin. The 'space' key is assigned as a hotkey in the host for start/stop playback. If you type in 'new name' only 'newname' will be received by the plugin, since the host does submit it to Gladiator.

What can you do to solve the issue?
Please do note that this is not a bug in Gladiator. For technical reasons this problem can not be solved from the plugin's companies site. It does affect also many plugins from other companies.
The problem is a host issue. The host does not forward keyboard input properly to the plugins.
Contact the host's company and request a support for submitting keyboard input to the plugins."

Well, Markus is wrong. Reaper has an option that transfer ALL key presses to the plugin. 'm' key still doesn't work.. besides, it was working just fine in the previous version of Gladiator and works just fine in Electra X (and original v1.0 of Gladiator which I still have installed).

It's definitely buggy.

ok, it would be good if you would reply in the tone2 forums where he is quite active .

[GeorgeZ]

I have 2.4 installed still, and the "m" issue is there too, so certain previous versions have had that problem as well.

[planetearth]

It's working properly in SONAR Platinum and SONAR X3. No issues with renaming patches or changing the LFO.

Steve

[bmanic]

It's working properly in SONAR Platinum and SONAR X3. No issues with renaming patches or changing the LFO.

Steve

Did you try specifically the 'm' key? Can you type 'mmmmmmmmmmkay?' as a patch name?

[Musical Gym]

Wild guess (and probably wrong) but could your m key already be assigned to something else like Mute?

[bmanic]

No. Like I said, Reaper has an option to send absolutely all keypresses to the currently active plugin. Also, the 'm' key works just fine in all other plugins that allow custom preset saving or any kind of renaming. That was of course the first thing I tried.