Repro 1.1.3, Zebra Legacy 2.9.4, Presswerk 1.1.6 public beta

[robisme]

Bug in Zebra Clap version : the modwheel cc1 switch the views SYNTH, PERFORM, PRESETS on its firsts values
Also, it sometimes crashes both Zebra and Reaper instantly.

[Urs]

I suppose you have MIDI Learned something that shouldn't be MIDI Learned...

What do your MIDI Controller Assignments look like?

And how did you get there?

[robisme]

I have tried to use the same controller to see which command it does, and it is cc1.
The issue doesn't occur with vst3 version.
I ignore how I could map this display change to a midi cc, it is not displayed in the midi mapping of Zebra.

[Fannon]

The 2 extra modulation slots are really nice together with the new MPE feature. For me it's the highlight of this update.

I wonder, is there a chance that Diva also gets additional mod slots in the future? I'm aware that Uhbik and Zebra 3 are higher priority for now. Just saying: Diva is such a good synth, but without additional, flexible mod slots its a bit limited and difficult to make good use of the MPE functionality. Could also be a good feature for Diva 2 (Hive 2 like mod matrix).

[tasmaniandevil]

Bug in Zebra Clap version : the modwheel cc1 switch the views SYNTH, PERFORM, PRESETS on its firsts values
Also, it sometimes crashes both Zebra and Reaper instantly.

You might be using the "last clicked control" feature in Zebra's MIDI learn section.
This way, the tabs are controllable via MIDI CCs.
Seems this can sometimes crash. We'll look into it. Thanks for spotting this.

[Alexander_D]

I was purchased Presswerk. It's a really nice and musical tool. BUT why it's got the small silence when I am bypass it or activate in the insert in Cubase 13? It's really annoying... I can't compare the signal.. And it's really hard to use... ;(

[tasmaniandevil]

This is connected to the host adjusting the latency compensation.

[Alexander_D]

This is connected to the host adjusting the latency compensation.

Yeah. But it's not so useful also in HQ mode of Presswerk...
I haven't this latency on Pro-C2 for example or in my other plugins...

[robisme]

Bug in Zebra Clap version : the modwheel cc1 switch the views SYNTH, PERFORM, PRESETS on its firsts values
Also, it sometimes crashes both Zebra and Reaper instantly.

You might be using the "last clicked control" feature in Zebra's MIDI learn section.
This way, the tabs are controllable via MIDI CCs.
Seems this can sometimes crash. We'll look into it. Thanks for spotting this.

Exactly, sorry for this. It was actually that (given I have just discovered this feature, It looks like I abused it, thanks for the tip )

[Alexander_D]

And it's so strange, that Presswerk gives for example 0.4 latency in Cubase. I load the Vintage preset for example. The latency is 0.9. But when I bypass it - it's again 0.4! It's the reason of that silent! Honestly I don't know any other plugin that reset the latency in bypass disappointed about Presswerk honestly

[Urs]

And it's so strange, that Presswerk gives for example 0.4 latency in Cubase. I load the Vintage preset for example. The latency is 0.9. But when I bypass it - it's again 0.4! It's the reason of that silent! Honestly I don't know any other plugin that reset the latency in bypass disappointed about Presswerk honestly

Yes, I wasn't aware of this, I'm afraid it might have slipped our test procedures

I'm going to bring it up and we might be able to fix this before the release. It makes perfect sense to me that the internal bypass should not change the latency.

(changes of latency are needed for look ahead processing - but changing latency causes DAWs to drop out, and I agree this should not happen on bypass)

[robisme]

(not english fluent, sorry if my phrase sounds terrible)
I have noticed that, in Bitwig at least, pressing the Presswerk bypass button generate a little noise (click or whatever the name), while, pressing the bypass fx button on Bitwig doesn't generate this unpleasant noise. Curious that an internal feature is less aware of its behavior than an external one.

[Urs]

(not english fluent, sorry if my phrase sounds terrible)
I have noticed that, in Bitwig at least, pressing the Presswerk bypass button generate a little noise (click or whatever the name), while, pressing the bypass fx button on Bitwig doesn't generate this unpleasant noise. Curious that an internal feature is less aware of its behavior than an external one.

It's a bug. I have traced the code for a good two hours, analysing the cause and the changes that have been made in the past 10 years. The glitch was fixed in 2014, but the developer left the broken code inside, just put it on hold ("commenting it out"). In 2019 the same developer stumbled across the same code and reversed the fix, I assume probably because he thought the fix was bug and the bug would fix it. Too bad he did not remember why he fixed it in the first place, and too bad he made the fix look like an unintentional omission.

Anyhow. I'll probably be able to just fix the issue now and make it right with the next beta or next release. And I will document the incident as a reminder for our devs to keep things tidy and well explained.

[Urs]

Also, our testing team (^^tasmaniandevil) had already come across the issue of the latency changing bypass button a few years ago, and it was on our radar, but it was marked as low priority. Thanks to Alexander_D we now understand the larger implication of it (which might be new since we only recently overhauled latency reporting), and I guess we'll have it sorted quickly. I hope.

[Alexander_D]

Also, our testing team (^^tasmaniandevil) had already come across the issue of the latency changing bypass button a few years ago, and it was on our radar, but it was marked as low priority. Thanks to Alexander_D we now understand the larger implication of it (which might be new since we only recently overhauled latency reporting), and I guess we'll have it sorted quickly. I hope.

Happy to help. Really. Because I like the Presswerk. But it's absolutely impossible to work with it right now... really. So it will be fixed, right? I mean these problems with bypass...
And do you need a video of this bug BTW?