BluOS Controller 4.8.0

Answered

Nick Hellcamp

• January 30, 2025 03:12

Hello,

Updated to latest controller on Windows, version 4.8.0. Device controlled is a Node. Prior controller version played all 24/192 material without issues. Now, if I try to open an album from the tray in 24/192, the screen remains blank, no list of tracks, no artwork. This worked fine with prior version, 4.4.1.

Is this a known issue? Any advice, apart from uninstall/reinstall of 4.4.1?

Thanks,

-Nick

0

• Official comment

  

  Alain DW

  Lossless

  • January 30, 2025 04:06
  • Edited

  Node2, controller 4.8.0 windows, fw 4.8.17: works well for me (24/192)

  Getting technical info and returning screen to one level up remains problematic, doesn't always work on the first click.  Probably network communication lag.
• 

  Nick Hellcamp

  • January 30, 2025 06:25

  Hello Alain,

  Thanks for the info. Interestingly, I just received an "invitation" to upgrade the Node.2's f.w. to latest, just 24 hrs after the controller update. After testing, it does see and handle 24/196 correctly. So, mutual dependency, it seems. It would probably help if the RN stated dependencies clearly (I could only find a note about (various changes/improvements without a list) and both f.w and controller were pushed out at the same time.

  I'll play with it and see how things fan out.

  Thanks for your reply,

  -Nick

  0
• 

  Seppi Evans

  Hi-Res

  • January 30, 2025 07:51

  Hi Nick, the BluOS controller has no bearing on what formats the player plays. The firmware update initiates a reboot and it’s the reboot that would have got things working again.

  0
• 

  Nick Hellcamp

  • January 31, 2025 01:42

  Hello Seppi,

  I found that out after my reply to Alain. How? I have two Node 2's in different locations. The first app update gave me issues as reported, it also had already the latest f.w installed. It was that machine that gave me issues. I rebuilt index, no results. I deleted and rebuilt, same problem. On #2 I installed new f.w first, then the app. That worked as expected. Node #1 never got a reboot, on a retry a day later all worked.

  A reboot clears memory, normally. So, I consider this a glitz. Next time, I'll reboot and see what gives.

  Thanks, I seem to have no issues at this time.

  -Nick

  0

Please sign in to leave a comment.