Hi @Kaloyan, I don’t know. I’ll pass your comments onto the team though. Thanks!
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
One technical thought, tho. Having some decent programming experience myself (as many among us, including you, I gather), I don’t exactly understand what would make Reloop Buddy so different than DDJ-REV5, or FLX4, or some other controllers. This is a mystery to me, tbh.
I understand some other controllers might differ from “standard” with more specific stuff, like GRV6.
But FLX4, REV5, and so many others should be fairly basic, regarding “mode” buttons.
I really don’t get how this is unsolved 2 years after your initial post in 2023, which is exactly the same request as mine, 2 years later.
1 Like
@Davidv100 some of the coding for these controllers is being done “under the hood” and outside of our MIDI Learn tool. We have a close collaborative working relationship with Reloop so it’s much easier to achieve this functionality with their hardware.
Also, bear in mind that djay works cross platform on iOS, macOS, Windows, Windows on ARM, Meta Quest and VisionOS. So our dev team needs to ensure proper functionality across all of these platforms with a wide variety of hardware.
2 Likes
I did the opposite and first picked up a reloop buddy and recently picked up an flx4 and at least with djay pro doesn’t live up to the hype that is portrayed amongst non djay pro users and especially compared to the buddy.
If the buddy was the same size as the flx4 the flx4 wouldn’t be in the same league imo
1 Like
I honestly don’t get why this thread is polluted with exceptions and custom devices… What we want is midi mappable (pages) or windows to display and we will do the rest ourselves.
3 Likes
I agree. I posted about DDJ-REV5 to make it more concrete and real.
But the issue is general (not device related).
I also wanted to reactivate this thread a bit (previous post was in December (3 months ago).
Sorry if this seemed “specific hardware pollution”. It was not my intent.
So far the closest universal “view mode” controls we have is in the midi mapping of switching the overall views, for example switching between, pro mode to 4 deck mode, etc. I don’t understand xml formatting but I do have the reloop buddy and can maybe export the midi mapping file and see what message is sent to the ipad that makes it switch views with each pad mode.
Hello @Slak_Jaw,
This topic has now reached 53 votes.
Would this amount be enough for this topic to be reckoned as having a decent dev priority level.
It is n°5 by vote ranking.
Thank you.
Hi @Davidv100, thanks for continuing to push this topic. This is already a priority for the dev team, but they ran into some complications with the implementation as previously discussed above.
Hello @Slak_Jaw for your swift reply as always.
However, this doesn’t really tell us whether this has been abandoned or is still being investigated/polished.
May I offer a suggestion about the performance mode buttons (Hot Cue, Loops,…) activating the corresponding modes in Djay :
What about :
- Offering mappable entries to activate the performance mode screens, in next Djay release.
- Without activating these features in the controller-specific pre-mappings. So it is clear this is still in beta and it is the user responsibility to map this, or not, in a kind of “take it for what it is” (=beta) approach.
So, at least people willing to use it, even if incomplete, can already try it. And adopt it, or unmap it again if it is not useable. This would help us understand what are the limit cases where it does not work, and maybe these limit cases are actually not that bad, or we can help with suggestions.
This would also ease the frustration.
I think this would be a very open, transparent, and collaborative approach.
Good for customers, good for Algoriddim.
Can we please proceed this way.
Thank you.
