After the update, the application does not respond to displaying numbers BPM No more, which was not a problem before.
Device Model (ex. 2025 iPad Air 7th Gen),(ex. 2019 iPhone 11 Promax ):
Version of operating system (ex. iOS 18.4.1):
Version of djay (ex. 5.3.1):
Hardware/controllers used (ex. Traktor Audio 6):
Hardware Firmware Version: 47
Hi @basskaa, when creating new topics, please do not forget to answer the questions in our template with specific details about your setup not just “iPad” or “Latest Version”. This helps all of our community moderators to provide the most effective support to users with the utmost efficiency. Thanks!
Device Model (ex. 2020 iPad Air 4th Gen):
Version of operating system (ex. iOS 17.3.1):
Version of djay (ex. 5.1.3):
Hardware/controllers used (ex. Reloop Ready):
Hardware Firmware Version:
Please also share more details about your issue. Screenshots or a short video would be greatly appreciated. Thanks!
Hi @basskaa, thanks for the video and additional details.
- Please close djay and follow the procedure linked below to perform a Forced Restart of your iOS device:
a. iPhone: https://support.apple.com/guide/iphone/force-restart-iphone-iph8903c3ee6/ios
b. iPad: Force restart iPad - Apple Support (IE) - After rebooting, please navigate to the djay Settings>Audio Devices and select the Reset to Defaults button at the bottom. Retest and let me know if the issue persists. Thanks!
@basskaa in your DVS settings, try disabling Relative Mode.
All platform it’s the same as before, nothing has changed.I apologize for my language usage as I am using Google Translate.
No problem @basskaa. Is this setting OFF?
Hi @basskaa, thanks for checking and for the additional video. Can you please try changing the REL settings near the BPM display?
Djay Pro 5.3.1 DVS
When using it with a MacBook, the REL mode does not work properly, but WIR mode works fine.
On iPad and iPhone, there is only REL mode available, and it behaves the same as on the MacBook — not functioning properly.
VDO
Thanks for the follow up @basskaa. I’ve passed this onto our engineering team for further review. I’ll report back when I have news.
Hi again @basskaa, engineering has identified the issue and is working on a fix which should be included in an upcoming release (likely 5.3.2). Thanks!
@Slak_Jaw Thank you very much.
You’re welcome @basskaa
Thank you very much. The issue has been fixed.
You’re welcome @basskaa. Thanks for the follow up!