New old guy here, just a casual turntablist from 20 odd years ago making the leap into the digital world of mixing.
Decided to purchase the mixstream pro go just for fun & to mix around the house/shed with all my recorded vinyl from years ago (sadly all sold along with my technics 1210s).
Anyways the issue I have & have read about a few others in the past is this strange wifi bug that disables wifi on random engine os versions.
I’m unable to physically turn the wifi on under engine os 3.4 or 3.3, controller version 1.0.0.1.1 on my mixstream pro go.
The only way to enable wifi & gain network access is to downgrade to engine os 3.2 (maximum), controller version 1.0.0.1.0.
I’ve factory reset the machine 3 times, & tried to update the unit both via usb & pc mode to no avail, so there must be a issue/bug with either engine os 3.3/3.4 or the controller version 1.0.0.1.1 as the only way the unit will allow me to turn on wifi & access any streaming services via wifi is to stay on engine os 3.2, controller version 1.0.0.1.0.
I’ve raised a ticket with numark about this but don’t believe this is a hardware issue, more like a random software issue that raises it’s head once in a while.
Getting rid of the Technics and vinyl must have been hard but I get that. Many DJs do it now and just go digital.
As for the issue, that does sound strange. Personally I’ve not seen it as a widespread problem but as it’s a really fundamental feature and it’s failing off the bat then that could be faulty hardware.
I’m not technically minded with the interiors but they do go though hardware revisions throughout their lifespan and a WiFi module or chip could be sourced from other manufacturers, making compatibility issues more likely. I’m pretty sure the Denon DJ team test every version against every hardware combo but something could slip through.
Raise a ticket with inMusic help and they maybe able to help as it seeks the WiFi chip works up to a certain version. This maybe able to be fixed with a patch but it could also mean the unit may have to be exchanged.
Yeah, getting rid of it all was emotional, but space & cash was needed when I left home so I had to do it unfortunately.
I’ve raised a ticket with InMusic & spoke to them via chat regarding the issue so at least the ball’s rolling.
The weird thing is I’ve only had it about 3 weeks (bought new) updated from 3.0 out the box to 3.4 & everything was fine, tested out a few things like using it as a controller in serato through usb connection from my pc & streaming amazon music over wifi (3 months free).
Then I thought I’ll have a mix with my tunes on usb, turned the wifi off to save battery & due to the fact I was out of range anyway down in the mancave/shed.
When I turned the thing on a couple of days later the wifi wouldn’t turn on, so I done a factory reset but nothing changed, so I thought I’ll downgrade the os back to 3.0 (default from new) but could only find 3.1 on the website for the pro go (3.0 was only available for the pro +) & the wifi worked again.
This is where my testing started, how high can I go with the os before my wifi turns off, so I tried 3.2 (still worked) 3.3 & 3.4 produced a dud so I put it back to 3.2 & here we are.
As I specified in my previous message os 3.3 & above also introduces a controller update so I wonder if that’s where the issue lies who knows, technical gremlins mate.
Hi Andy, does it not turn on at all, or is it not connecting? … stupid question but have you tried just doing a normal reboot after the initial turn on? And what about disabling bluetooth?
Exactly the same issue this guy had, posted in this forum back in 2020 on his denon unit
@STU-C hi mate, will not physically let me toggle it on/off next time I try to update as a test I’ll try disabling bluetooth to see what happens, but as it stands at the moment it all works so I’m hesitant, don’t need/use Bluetooth anyway but any additional fixes are always welcome hence why I’d like to get it sorted & updated.
Found another video of someone else having the same issue from 2021, again posted in this forum.
This is definitely a strange bug across multiple units at various os updates.
I personally would stay on 3.2 and keep the update file handy… then wait for the next update and try that, but keep this issue open so it can be looked at in the meantime.
There’s a lot to be said about picking a stable version of firmware, even though we all like the updates
So, curiosity got the better of me & I decided to try again, connected it up to my pc, installed os 3.4, didn’t download a new file just used the same one I’ve been trying for days & it all works again.
Controller updated fine, wifi works fine, didn’t even need a reboot after updating, but I did one anyway.
