You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(branch "Limiter-and-Overdrive")
One other small issue: I don't understand how to exit the menu and get into the default display.
If I am in the menu I can press the "Menu_Ret"-button (assigned on my keyboard or in the HTML-Gui). This will bring me back to the top level of the menu, but never back to the default display...
Other than this, the branch seems to work very well!
The text was updated successfully, but these errors were encountered:
Hello kaixxx,
I don't understand / can't reproduce.
There is no default display in my understanding, just the top level of the menu.
This top level browses / rotates through the main categories: general, reverb, ...., arpeggiator, general etc.
This feature is primarily meant for using physical buttons in combination with an LCD/OLED display and aimed at using as less button presses as possible.
Thinking further about it might be useful to have an "ultimate return" which will go back to the fixed "general" starting point in order to have some sort of reset base when using it without a display (like with a midi device only setup).
Does this answer your question?
Hello Hans
Thank you for looking into this issue. By "default display" I mean the display that appears after starting up the box. It has the volume in the first line and the current preset in the second (if I remember correctly). Once I opened the menu, there is no way back into this default display.
(branch "Limiter-and-Overdrive")
One other small issue: I don't understand how to exit the menu and get into the default display.
If I am in the menu I can press the "Menu_Ret"-button (assigned on my keyboard or in the HTML-Gui). This will bring me back to the top level of the menu, but never back to the default display...
Other than this, the branch seems to work very well!
The text was updated successfully, but these errors were encountered: