Understood. Please make a separate suggestion topic for this @daniel_curley. Thanks!
Currently there is no way to select hot cue, loop, fx display panels from a controller on ios. (Buddy and Mixtour Pro excluded and also limited).
It would be a much better experience to able select or scroll through these options from a device rather than having to select with your finger on the screen.
If I were to load a new track I haven’t familiarised myself with yet I would first want hot cues, then I would like to select a saved loop and then an effect.
This would involve 3 or even 4 personal ineractions with the screen which I do not find pleasant while working.
Library navigation and selection can be done without the need to get “hands on” I believe the same could be done for the above mentioned functions and make the user experience a lot smoother.
3 Likes
When I first saw this on the Mixtour Pro, I also thought that it made a lot of sense and that there should at least be an option to activate automatic switching of the view. In addition, you could perhaps add the option of whether the switchover only takes place after the pad mode has been selected twice (as is now the case with the Mixtour Pro) or immediately on the first selection.
Hi @daniel_curley, please use search before creating new topics. I’ve merged yours with this existing one. You can vote for this feature at the top left of this page. Thanks!
1 Like
What do you know about these commands @Slak_Jaw?
They would appear to be somewhere in the region of what I’m looking for but when I assign them to various buttons nothing happens.
Hi @daniel_curley, yes, the commands were added a few releases ago, but had to be disabled as the engineering team found some issues with certain hardware. These remain the stepping stones towards adding this functionality in the future.
2 Likes
Reasons to be optimistic then.
1 Like
This would have to be the biggest let down of DJAY PRO and such a pity for what’s otherwise a granted feature in every DJ software for years…
2 Likes
I have few requests for abilities to MIDI map the View modes management of the layout. My main aim is the iPad, but it can be made to be in harmony with the MacOS & Windows versions as well.
-
Direct MIDI action selection of the View Modes - “Hardware Mode”, “4 Decks”, (maybe Video, etc.) with a direct MIDI action.
Hardware Mode is awesome and use this one mostly, but I often need 4 decks display during a set and it’s inconvenient to go through the screen flow for switching this. There’s the action to cycle through the available “View Modes” but it’s annoying and makes me worry that the app may crash while playing (silly me
). -
MIDI Actions to switch on/off the mini-Looper / mini-File Browse / Tools panels (applicable to Hardware/Pro/4 Decks mode) as Direct actions - On/Off Mini-Looper; On/Off Tools; On/Off Mini-Library, similarly how the on-screen control work, but mappable to controller buttons through MIDI.
-
Properly functioning “Toggle *” actions in the “General → View” section. There are “Toggle Tools/FX/NM/etc” that work on Computer, but on iPad they do nothing.
On iPad, the Tools panel has NM/Cue/Loop/FX/EQ tabs, but we cannot select them from controllers. There are similarly named MIDI action commands, which work on the Computer version, and can possibly be enhanced to activate the 5 panels in the “Tools” tab as direct MIDI actions, and make it more consistent across computers and iPads.
Writing this in one request, as they are all related to the same application area - MIDI mapping. I hope many users will enjoy this set of MIDI mappable commands.
Hi @Kaloyan, please use search before creating new topics. I have merged your new topic with this existing one as they are closely related. You can use the blue Vote button at the top left of this page to show your support for adding this feature.
There is a new MIDI command option that does allow you to select a specific View Mode.
- In the MIDI Learn tool, press the button you want to map to a specific View Mode
- Set the Target to General
- Set the Action to View Mode Select
- Expand the Advanced Control Configuration section
- Adjust the Action Parameter: to one of the 7 available View Mode options.
Oh great, thanks @Slak_Jaw!
Indeed - #1 is Hardware mode, #2 is a full screen Looper, #5 is 4 decks mode. I’m good with point #1 of my request.
Point #2 from the post remain valid new suggestions/feature requests. They are about functionality from within the selected View Mode - to open the mini-looper, and the tools panel. It’s not the Toggle discussed above.
#3 I see here that the Toggles to the different Tools panels are not working due to defect. But they are very needed indeed. They seem to have been designed for the Computer version, while the UI on iPad is different and adaptation is needed.
You’re welcome @Kaloyan. Happy to help. I see what you’re saying regarding points 2 and 3. I think it would be best to handle these in their own topics actually.
Just tested the mapping of these on Mac & iPad - the values of the layouts in Mac and iPadOS are different and the button mapping does different things. 
I think that it would be appropriate that these values get equalized/consistent and we can reuse our mappings across the different DJ platforms.
On Mac:
#1 is two deck mode
#2 is single deck
#3 is Automix
#4 is 4 decks
#5 is Video
on iPad:
#1 is hardware 2 deck
#2 is the big Looper
#5 is 4 decks
(there are few other values too)
If I were a QA/PM of the app, I would suggest that the Mac set of values (1-5) is best to be applied to the iPad’s respective set of View Modes, and the iPad/iOS specific view modes will follow from number 6 and above. The set of Mac specific View modes are the most widely used ones by controller people.
Not that it’s a huge thing, but it’s best that we will have consistent mapping commands & actions across the platforms.
If setting “4” stays for 4 decks HW mode, #5 to stay for Video and the Looper can become value 7 (aligned with the keyboard shortcut on Mac) it would be great. It would also #1 makes some sense 1 to be single deck, and #2 Two decks HW Mode.
2 Likes
@Slak_Jaw , do you if the iOS implementation for selecting on-screen panels will be independent from the PadModeSelect MIDI action?
IMO, they should be independent. If needed/disered, connecting a “toggle” panel to a PadModeSelect is better to be done through a “Duplicate” action, as I don’t always want the screen to follow the PadMode selection. For example, there is visual indications of the Cue slots on the HW buttons, so I don’t usually want to see the Cue panel, but have the FX panel on the screen, or the Library Panel, regardless of the selected pad mode. I want to see the advanced panels only when I want to, and can implement it through explicit or combined, “Duplicate” actions. Whatever fits my workflow on a specific controller and mode.
Dear @Slak_Jaw,
You have sent me here, after I created another related topic : DDJ REV5: UI not changing to match pad modes - #3 by Slak_Jaw
I thank you for that, as I feel already less lonely.
Just like you in your original post from 2023, what I want to do is having the pad modes of my controller (DDJ-REV 5) toggling the appropriate pad screen on DJay. (Hot Cue → Hot Cue and so on).
It seems so natural, necessary, and obvious.
I have read everything above.
I am very disappointed that this is not existing yet.
It seems so simple (from an external POV).
However, I see some progress is ongoing, so there is hope, as another member said.
I have one immediate question though.
How come a click on my DDJ-REV5 performance mode buttons doesn’t seem to be detected at all by Djay.
For example, when I click the P1 button (“Hot Cue” mode), DJAY doesn’t seem to detect it at all.
Here below is an extract from the DDJ-REV5 user guide.
I boxed the “P1” line in list (second screenshot).
How can we help improving the attention of the Dev Team to this specific point.
I mean, it is cross-platform : it is a huge global win for everyone.
Ofc, I voted already. What else ?
I mean isn’t it enough that this topic has 1,700 views ?
Thank you very much.
Hi @Davidv100, you could double check if your hardware sends MIDI commands for those buttons using another software like MIDI Scope. If it is sending MIDI commands to this software, then likely our hardware engineering team is blocking these commands internally to ensure optimal functionality in some way.
Regarding this suggestion in general, during testing, the hardware engineering team discovered some edge cases with certain hardware that were causing issues. Apparently this is a complex issue to solve and our team is still working on it. I hope that helps!
For more info on how our voting system works, please refer to the following topic:
1 Like
