This happened to me on the weekend at a live gig (FW 1.51)… Highly embarrassing… Playing from front SD card, loaded a track on deck 2 half an hour into my set and even though it had loaded it would not play. I could still scroll through it with the jog wheel… Loaded a few more tracks on deck 2 and they still wouldn’t work… I instantly knew that this was the problem though as I had read this thread a couple of weeks ago… Had to reboot and restart and everything was ok… but… ??? seriously… come on Denon! whats the official line on this bug?
Did u updated to the new firmware 1.5.2? Don’t say much on the Description on the denon site? But I think it’s a fix
1 Like
Thanks for pointing this out, I wasn’t aware there was a newer update. When the 1.5.1 update dropped the device told me there was an update. When I checked on device just now it didn’t notify me that there was a newer update… When looking in the settings it said there was a newer update but then tapping the “check for update” button it spunwait then told me there was a newer update then all subsequent button presses said I was already up to date… either way I just manually downloaded the 1.5.2 to an sd card and successfully updated… this is all very confusing… I do hope this fixes the freeze issue.
Yeah I hope so too! Let us know good luck
1 Like
Ok I updated to 1.52 and it looks like they got the bug out. Also the easy way to update is with a USB cable from PC or Mac directly into the Prime Go. This makes the unit my Favorite again Thanks DENON keep up the good work
2 Likes
Hallo, i have the probleem That deck 2 frezen, recieved my prime go yesterday firmware 1.5.2 ,
Is denon solve thuis problem or is it better to return it to the store and take my mony back ?
Thnx, Paul
Hallo, i have the probleem That deck 2 frezen, recieved my prime go yesterday firmware 1.5.2
This has been discussed alot on this forum. I can not 100% confirm this fixed it. But I just tried it and seems to working ok. Do a reset of you preferences.
I think it has to do with Songs that you have already played and are greened out, but not entirely sure if that is causing this bug.
Just had this happen to me on a 2 day old unit (no response from deck 2). Any word on this getting sorted? im on 1.5.2
I’ve had this problem a few times, but only ever with Tidal.
The device still thinks that deck 2 (right) is playing. You can scan forward and back with the jog wheel and there is audio. You can even hit ‘Cue’ and it will snap back to the cue point, but it just won’t play. The button is responsive though, as you can press it and the light will go solid and you will then be prevented from loading a track to it until you ‘pause’ it - then whatever track you load, be it Tidal or storage will do the same thing. Only thing you can do is reboot.
I’ve never had it just mixing tracks off the SD card.
Hi Everyone,
Just wanted to chime in to provide a bit of hope here. We’re currently testing platter touch improvements for the PRIME GO with our private beta team. So far have seen positive results from this and will make everyone aware once we release publicly. We expect these improvements to be part of the next (v1.6) release.
Also, it’s worth mentioning that all of our capacitive touch platters go through a calibration cycle during the power on/boot-up sequence. During this calibration period (~20sec), it is recommended not to touch the platters as they are detecting/sensing various conditions of the environment and adjusting the touch algorithm as needed to provide the best experience for your environment. I’m not suggesting this is what is causing the issue, just something to be mindful of.
1 Like
When will 1.6 be available ? I just got a Prime GO and updated to 1.5.2 last night and turned on today and the right deck does not play the song even though the platter works.
Can you shed some light JWiLL please???
in the instructions is indicated?
Hi Everyone,
I will be closing this thread as it is very similar to Deck 2 Platter Locked (no playback) After Updating to v1.5.2. Please continue the conversation in that thread.
You’ll see that I posted instructions on how to downgrade the firmware to v1.4.1. Hopefully this provides a workable solution for you while we finish v1.6 which has a fix in place for this issue.
1 Like