So, I’ve been testing the new Engine 5.0 in multiple gigs now and there’s a few things that are changed or bugs that I’ve found. These are quite annoying taking in consideration previous workflow and mucle memory. I’m using SC LIVE 4 & Prime GO.
Swipe left to prepare now loads to deck 1 instead of preparing, now we have to shortly swipe left and click prepare manually which adds more time and steps compared to before. Would love to be able to swap back this option for those who were used to that workflow.
When you go back into view mode, many times the playlist position isn’t remembered, which makes you have to scroll down or anything again, time consuming as well.
Found some more minor glitches that are hard to describe here as I don’t remember properly, I’ll edit after if I can.
Honestly I think that’s a huge step backwards, it now feels way too sensitive and I’ve overwritten a song many times by mistake already… definitely not a nice change in my opinion.
I’m kind of happy not to have to see the Load overlay anymore, but I agree it’s not really a full swipe left/right to load the track on my Prime Go, more like a 1/3rd swipe. So you have to swipe gently to access the Prepare option.
A bug I’ve found is if you connect to WiFi that requires a web page to connect, like hotel WiFi, you won’t be able to turn WiFi off and the system hangs in shutdown. When I boot back up, I get the dreaded 2 bank lights and 2 mic lights suggesting the os failed to initialise.
I went back to 4.3.4, 5.0.1 is the buggiest release I’ve ever had on my Prime 4+ The audio glitches mentioned in other threads along with the bugs make it unusable in a live environment.
I’m also going back to 4.3.4. This update is a disaster. Professionalism cannot be ruined by an update full of bugs. Obviously, there are also those who say it’s not true. Yesterday I had nightmares while playing. The audio would come and go. It happened three times in one set.
I’m glad it isn’t just me, I was starting to lose my mind this weekend when I kept loading tracks instead of preparing. Nevermind the total crash/reboot on a live gig…
hmmm, I have been on 5.0 and then 5.0.1 since day one, my decks are playing continously aprx. 8-10hrs daily and no issues at all, actually performance seems to be faster (loading folders, loading songs) and better/ smoother waveform screen refresh (: I am on P4+
I upgraded to 5.0.1 today and have time to play with it before the next gig. I did play this last weekend on 5.0.0 and had a complete shutdown in the middle of the gig. That is the first and only time I have had issues with any of the updates.
Since this is a problem only you are experiencing, it would be helpful to provide as many details as possible: Equipment, standalone mode? Computer? Lighting on? Streaming? WAV? MP3? Did you use Sync Manager? Do you have analyzed tracks? Or are you doing it from the device? How long has it been since you cleared the database? Storage type? Operating system? Can you reproduce the error? Can you try it with the same tracks?.. At least providing some more information could help us find the problem you’re having.
That makes sense on All-in-one’s - the most frequently used operation during a night is obviously “load to deck” so it should be (and now is) the most easily accessible function
Sending a found track to a prepare list isn’t accessed as frequently as load to deck, so makes sense that it’s a little less accessible
Of course, it would be lovely to have a separate button for every single function but you’d need a console about the size of a front door
There’s nothing stopping you from pulling out the side menu if that’s what the developer decided. But you can do that with a stop for selection, instead of dropping the track into the default deck. That’s inconvenient. It’s basically a choice without a choice.