Zebra 3 final final beta 21764 April 14
-
- KVRian
- 718 posts since 22 Dec, 2015
It seems that the issue with poorly visible dark gray text on a dark background, which many users have pointed out, still remains unresolved.
Is the idea that users should wait for third-party skins to address this? I’m sorry, but that approach feels somewhat unusual. Wouldn’t it make more sense to handle this properly in the official default version?
The contrast problem with such text is definitely not imaginary or merely a matter of personal preference.
Is the idea that users should wait for third-party skins to address this? I’m sorry, but that approach feels somewhat unusual. Wouldn’t it make more sense to handle this properly in the official default version?
The contrast problem with such text is definitely not imaginary or merely a matter of personal preference.
-
- KVRist
- 45 posts since 25 Feb, 2020
Any future plans to bring User-mode in Zebra 3 LFOs, Urs?
You do not have the required permissions to view the files attached to this post.
-
- KVRist
- 117 posts since 9 Jun, 2024
Yeah, this is one thing I constantly find missing in Zebra 3. It could somewhat be done with the mapper but the workflow is super complicated.
- KVRAF
- 3391 posts since 25 Apr, 2011
+1 on this. This would solve the missing "sync to transport" in the MSEG's.
-
- KVRist
- 31 posts since 11 Jun, 2017 from Los Angeles
In the mod matrix, it seems like pushing the mouse wheel up should increase the value in a positive direction, and down should decrease it in a negative direction. It's inverted for me. I'm on a Mac, but I have natural scrolling turned off, so in general pushing wheel up increases values on other parameters.
- KVRAF
- 26939 posts since 3 Feb, 2005 from in the wilds
I'd be fine with the LFO User mode added back. Just pointing out that the Mappers don't somewhat do what the LFO user mode did, the Mappers do everything that it did and then a bunch more.
And it's not super complicated. Leave Mapper on Increment and set the Modulator to LFO and there it is. It's about the same clicks.
- KVRAF
- 3391 posts since 25 Apr, 2011
so,..how would you let a mapper 'run' without "losing" a LFO or MSEG?pdxindy wrote: Wed Apr 15, 2026 12:23 amI'd be fine with the LFO User mode added back. Just pointing out that the Mappers don't somewhat do what the LFO user mode did, the Mappers do everything that it did and then a bunch more.
And it's not super complicated. Leave Mapper on Increment and set the Modulator to LFO and there it is. It's about the same clicks.
- KVRAF
- 26939 posts since 3 Feb, 2005 from in the wilds
I believe they lightened the label text a bit in this new beta.warcat wrote: Tue Apr 14, 2026 10:31 pm It seems that the issue with poorly visible dark gray text on a dark background, which many users have pointed out, still remains unresolved.
It's impossible to satisfy everyone, both because it is subjective and because people all have different monitors, scaling, etc.warcat wrote: Tue Apr 14, 2026 10:31 pm Is the idea that users should wait for third-party skins to address this? I’m sorry, but that approach feels somewhat unusual. Wouldn’t it make more sense to handle this properly in the official default version?
It's not necessary to wait for third party skins if you just want the label text brighter. It's one single color definition change in a text file to change the label text color value across the synth. For example, I set the text to a darker grey to make it less visible in the new beta. For me, it stood out a bit too much.
-
- KVRist
- 117 posts since 9 Jun, 2024
Oh, the moment you need to assign a modulator to run another modulator to do some basic things it's already unnecessarily complicated. It also doubles the number of modulation sources you got to use.
Yet still you can't custom control that LFO you used as modulation source for your Mapper, so you always end up with something tricky.
It's fine to have cool fancy workarounds to do things, but they are and only are workarounds. Relying on a workaround always means a hole in the workflow.
Yet still you can't custom control that LFO you used as modulation source for your Mapper, so you always end up with something tricky.
It's fine to have cool fancy workarounds to do things, but they are and only are workarounds. Relying on a workaround always means a hole in the workflow.
- KVRAF
- 26939 posts since 3 Feb, 2005 from in the wilds
You wouldn't... you need to use an LFO.exmatproton wrote: Wed Apr 15, 2026 12:29 am so,..how would you let a mapper 'run' without "losing" a LFO or MSEG?
Like I said, I'm not arguing against adding a "User" mode to the LFO's. I was making the point that the Mappers can do everything that old user mode could do, plus more.
-
Funkybot's Evil Twin Funkybot's Evil Twin https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=116627
- KVRAF
- 12443 posts since 16 Aug, 2006
Go to the Preferences. You can tweak it there.jrgillam wrote: Wed Apr 15, 2026 12:06 am In the mod matrix, it seems like pushing the mouse wheel up should increase the value in a positive direction, and down should decrease it in a negative direction. It's inverted for me. I'm on a Mac, but I have natural scrolling turned off, so in general pushing wheel up increases values on other parameters.
- KVRAF
- 3391 posts since 25 Apr, 2011
My mistake. Point takenpdxindy wrote: Wed Apr 15, 2026 12:51 amYou wouldn't... you need to use an LFO.exmatproton wrote: Wed Apr 15, 2026 12:29 am so,..how would you let a mapper 'run' without "losing" a LFO or MSEG?
Like I said, I'm not arguing against adding a "User" mode to the LFO's. I was making the point that the Mappers can do everything that old user mode could do, plus more.
-
- KVRian
- 718 posts since 22 Dec, 2015
Yes, I completely understand and agree with that. However, dark text on a dark background becomes less legible regardless of subjective preference. That’s simply how contrast works. And there were quite a few complaints about this in the previous thread.pdxindy wrote: Wed Apr 15, 2026 12:37 am
It's impossible to satisfy everyone, both because it is subjective and because people all have different monitors, scaling, etc.
It's not necessary to wait for third party skins if you just want the label text brighter. It's one single color definition change in a text file to change the label text color value across the synth. For example, I set the text to a darker grey to make it less visible in the new beta. For me, it stood out a bit too much.
In any case, you’re right - ultimately this will likely require manual adjustments, which isn’t very convenient. Ideally, it would be great to have a user-friendly editor for this, or the ability to adjust it directly in the settings, similar to TAL, Phase Plant, Melda, and so on. I think that would be a solution that works for everyone. And hopefully this is feasible with a vector-based interface.
- KVRAF
- 26939 posts since 3 Feb, 2005 from in the wilds
Yeah, it's not so convenient.warcat wrote: Wed Apr 15, 2026 1:30 am
In any case, you’re right - ultimately this will likely require manual adjustments, which isn’t very convenient.
Keep in mind that the new beta has slightly brighter label text, so we will see if some of the complaints have been addressed. Or maybe those people still want it brighter. The worst case scenario is you edit it yourself.warcat wrote: Wed Apr 15, 2026 1:30 am And there were quite a few complaints about this in the previous thread.
