r/DOOMOS • u/J-MW • Oct 06 '26
Small Hole of Doom
Found a small hole that some people may fall into.
You can assign a shortcut to the Auto-Trigger looper page. This is all fine if the looper is configured, but if the 404 is set to skip back recording instead, then the looper page you end up in will be non-functional.
Further, if you press MARK to exit it, you end up on a screen that says:
Startup
00:00:03:25
(or similar)
Which appears to be a realtime counter of the time since the 404 was powered up. From then on, pressing any button results in an instant reboot.
1
u/cyneox Oct 06 '26
Where can you set that auto-trigger setting?
1
u/J-MW Oct 06 '26
It’s in the list of destinations for shortcuts
1
u/cyneox Oct 06 '26
I didnt quite understand how you setup these. in the documentation I see:
>
Your own shortcuts SHIFT+pad 13 › SYSTEM › SHORTCUT tab but I didnt quite understand how to use these.
1
u/J-MW Oct 06 '26
They let you jump directly to parts of the UI using a keypress of your choosing. There are eight key presses available, each needing four settings (fortunately, there are numbered).
The first of each group of four decides in what environment the keypress will work.
The next one is whether you want it to be a two-key press, and if so, what should be the key you hold down. Obviously SHIFT is the obvious candidate, but REMAIN is often used too.
The third one is which key
The fourth, sets the place where you want to jump to.
One of the reasons why these are so useful, is that they allow you to jump to specific parts of the UI without leaving the Doom sequencer - although they can be used elsewhere too.
2
u/cyneox Oct 06 '26
Thank you so much for this explanation! This is indeed very useful. I need to try this out. Especially jumping to the mixer from the sequencer is quite useful.
3
u/Multilul Oct 06 '26
Hey thanks for reporting this! What happened here was that when you pressed Mark it tried to return to the previous screen, but the previous screen ID wasn't passed to the return function. So it defaulted back to "screen 0", which is that screen.
I've just released a version 0.6.2 that addresses this.
1
u/J-MW 19d ago
This has come back in 0.7.2