Thanks for the info @Five-0. Can you please try eliminating Tidal tracks to see if that changes anything?
If this is a Tidal issue I am going to be furious!
Iām paying an extra premium for that service and it needs to work.
Yes, I. Believe it was. I djād last night at a small bar and it crashed. I went back in history to the exact point and i was playing a local song and I remember clicking a tidal track and the software shut down. I wasnāt in search mode and my panels was closed/ had a vibe going right before it crashed.
Just played a four hour gig, no side pane or search involved and it went without incident. A combination of Tidal and local files.
Tried search and side panel match when I got home and it crashed twice in 2 minutes.
Hello, I am also experiencing crashing but while playing. After about 20-30 minutes of playing it crashes and shuts down the entire app. I would then have to restart the app and after another 30 minutes it crashes again. I hope an update will be out soon to fix this issue. I have experienced this in the past it was fixed but now it is back.
Hi @Bean_Town, to help us troubleshoot your crash and to confirm that it is the same issue as above, please submit an Official Support Ticket using the procedure below so the engineering team can review your crash reports in more detail.
- Open the djay app on your device.
- Navigate to Settings>Contact Support.
- Fill out the submission form and title your email "ATTN: MARIE ā ā5.2.3 crashed 2 times when search for songsā in the provided subject line. Thanks!
Worrying every song that tool you use to make money might fail you is the worst feeling in the world! Not looking forward to use this product at my gig today
Crashed at a gig last night and now preparing for a gig tonight and it has already crashed three times. I do not hear this from DJs using Traktor or Rekordbox. Itās so embarrassing. I honestly feel like you owe me money. Iāve had my fair share of crash history with Djay. Probably my fault for sticking with you. This just can not happen every now and then for a professional setting.
Update: In my case it crashes when Iām loading songs into the deck. 4th crash in 3 hours. App closes completely.
Update 2: 5th crash - also crashes when just editing the playlist and nothing playing
Even worse this problem seems to be existing for almost two weeks
Hopefully algoriddim will provide a stable update soon.
When it does I will be making sure to deactivate the option to auto update the app and remain with a competent version so I can work with less agro.
This last year has seen some amazing new features which I love but part of the problem with this constant innovation is the more frequent appearence of bugs.
The ios app as it stands has more than enough for me to get by so when they steady it up and get it working flawlesly Iāll be sticking with that version.
Hi @Fresh27, to help us troubleshoot your crash and to confirm that it is the same issue as above, please submit an Official Support Ticket using the procedure below so the engineering team can review your crash reports in more detail.
- Open the djay app on your device.
- Navigate to Settings>Contact Support.
- Fill out the submission form and title your email "ATTN: MARIE ā ā5.2.3 crashed 2 times when search for songsā in the provided subject line. Thanks!
Thanks for the quick reply. I do wonder about a refund. It crashed at a gig, super embarrassing. Whatās your policy on that?
Thanks @Slak_Jaw for the quick reply. I do wonder about a refund. It crashed at a gig, super embarrassing. Whatās your policy on that?
Like all software companies I would imagine. Every software company there is risk of crashes. Seems to be more often though with Djay Pro. I havenāt had a crash yet, not whilst playing live anyway. I did have crashes whilst midi mapping though. Which were investigated. Itās the risk we take. Crashes in ideal world shouldnāt happen but sometimes they do. Not easy and frustrating but thatās software for you.
So whatās your point or contribution to this thread? We are looking for a solution to specific problems that can be addressed.
My point and contribution is whatās called an opinion and in the spirit of free speech. One of which is very much allowed on this forum, to even try to question someoneās opinion is rather controlling of you. That being said, the engineers I am sure will get to grips with this and sort it as they always do. Stability does need to be their focus right now.
Iāve been using Djay for about four years now, and Iāve experienced over 15 gig crashes, maybe even more. At first, I thought it might be because of my old iPad, so I upgraded to a new iPad Pro. I also switched between different controllers because I kept feeling like the sound quality wasnāt greatāand I still feel that way. Often, it doesnāt matter too much because the crowd is usually drunk, but it still bothers me.
At least the crashes stopped over the past year. I think the software is fantasticāI love the touch experience with the iPad, itās just awesome! But I feel like Iām reaching my limit. I need to have confidence that the software will work reliably. The sound quality needs to be excellent. This is crucial and should always be prioritized!
Iām paying for this, Iām not a beta tester. Iāve submitted countless bug reports, logs, and who knows what else. Yet, I keep feeling like Iām constantly ending up beta testing. Thatās just not acceptable. Offer a beta version for free, fix the bugs beforehand, and only release updates when youāre sure itās at least stable!
The number of crashes I can generate right now is ridiculous. The software clearly hasnāt been tested enough. And now itās taking forever to fix the issuesāI can only assume itās because itās summer and people are on vacation. Otherwise, please re-release the last stable version so we can at least keep playing safely.
Honestly, Iām frustrated. I love Djay, and I feel like Iām being forced to leave it behind. Iām already the odd one out for not using the provided CDJs, and itās only justified if what Iām offering actually works. Sadly, right now, it doesnāt and honestly we need a promise by Algoriddim, this will be different in the future. Cause the past has shown otherwise.
Some great advice here from @Slak_Jaw from a previous post regarding problems like this and how to avoid them in future.
Iāll certainly be borrowing this workflow.