Calling Sense 3 Beta Testers, who's in?

For those encountering the beta Radio issue, please could you test something for us.
In Sense app SETTINGS, please disable your UPNP function completely, then reboot the system. After that, please try again to use the new radio/podcast services.
Hi Stephen, just done as you suggested and unfortunately for me at least no change and I'm still getting the spinning wheel for both Podcast and Radio
 
for me, where it works perfectly since the first BETA version, the UPNP function has always been disabled.
 
for me, where it works perfectly since the first BETA version, the UPNP function has always been disabled.
I already had UPNP disabled and am also getting the spinning wheel. In addition, despite a remote session which proved to be unsuccessful and a subsequent promise of a hot fix to address the issue, I continue to experience resetting of the volume control to 50 from the preferred 100 whenever restarting Sense and random drops in volume to 50 when playing music.
 
For those encountering the beta Radio issue, please could you test something for us.
In Sense app SETTINGS, please disable your UPNP function completely, then reboot the system. After that, please try again to use the new radio/podcast services.
I tried it as you suggested but it still doesn’t work unfortunately.
 
For those encountering the beta Radio issue, please could you test something for us.
In Sense app SETTINGS, please disable your UPNP function completely, then reboot the system. After that, please try again to use the new radio/podcast services.
it also does not help for me... Still the spinning wheel
 
I’m glad I could help narrow down the issue. I can confirm that Radio & Podcasts work fine. There’s an amazing selection of stations! The icons of the stations are displayed in the Web browser and the public app, but not in the current 1.5.0. (101) Beta version. However, the developers are aware of this and it’s being fixed soon. So, I guess we’re getting closer to an official release of Sense 3.1 :)
 
Thanks to some direct assistance from @mountainview we believe we have found the source of the issue affecting some users, so is now on the development sprint for the next beta increment.
Edit: typo
I get a notification that 3.1.0-8 is available but when I click on that I get 3.1.0-7 and the messagetaht I am up to date...
 

Attachments

  • Screenshot 2024-11-05 at 15.39.03.png
    Screenshot 2024-11-05 at 15.39.03.png
    198.6 KB · Views: 6
  • Screenshot 2024-11-05 at 15.39.11.png
    Screenshot 2024-11-05 at 15.39.11.png
    390.9 KB · Views: 5
Are you referring to Radio page issue, while the white page issue is in same way correlated to this or we still need to wait for a fix in that case?
Yes, I was referring to the Radio and Podcasts overhaul that will be introduced in 3.1. For several testers, the platform was not working at all which was surprising as it worked fine during all our internal testing, so there was more work to be done!
 
  • Like
Reactions: luca.pelliccioli
Just a potential heads-up for the users who had earlier beta versions of 3.1; you might find that if you saved any podcasts as favourites during the beta period, you may find now that after the official update these saved presets on the widget no longer work - you simply need to unfavourite then re-favourite these podcasts to resolve.
The problem does not seem to apply to Radio station presets, only to Podcast presets.
 
  • Like
Reactions: luca.pelliccioli
Calling on beta participants; version 3.2.0-2 has just been made available to you. You may install at your discretion. There will be more features added in the final release, but for now this beta includes the following new features:
  • Idagio streaming service
  • Revamped UPnP Player
  • Added player group functionality for Sense endpoints and Squeezebox players allowing for multi-room playback synchronisation
  • Revamped Player Queue to allow for up to 10.000 tracks in queue

We have also now made amendments that Innuos systems will now automatically appear as a shared network location via Windows.
The new name will be Model-Last 5 Digits of the Serial Number (e.g., ZEN-01234).

To access the shared folders, you will need to enter the following credentials when prompted by Windows:

  • Username: guest
  • Password: innuos
 
Thank you for sharing. Just installed the update which went smoothly. Integrated a Pair of Devialet Phantom I and a Sonos Soundbar via UPnP. Had to restart the Server to make them available in the Player. I have to do some testing now. Inititial findings. The Phantoms work (not in compatible mode 99,6Khz). If I may suggest, please reduce the Volume to the standard 35 setting. 50 is with the Phantoms already quite loud ;) The icons and info of the streaming media for Radio Paradise would neither be shown in Sense, nor in the Devialet app. A locally stored file would show the info in Sense, but not in the Devialet app.
 
Thank you for sharing. Just installed the update which went smoothly. Integrated a Pair of Devialet Phantom I and a Sonos Soundbar via UPnP. Had to restart the Server to make them available in the Player. I have to do some testing now. Inititial findings. The Phantoms work (not in compatible mode 99,6Khz). If I may suggest, please reduce the Volume to the standard 35 setting. 50 is with the Phantoms already quite loud ;) The icons and info of the streaming media for Radio Paradise would neither be shown in Sense, nor in the Devialet app. A locally stored file would show the info in Sense, but not in the Devialet app.
Some of these behaviours are to be expected - to increase compatibility across as many devices as possible with a smooth operation, we simply have to cut back on many other variables such as the way metadata is presented. UPnP devices vary so hugely that we have to adapt the platform so that you can customise more with maximum resolution, DSD support and how track data is transmitted to your own system. If it works, great! If not, then compatibility will be the best we can offer for now, which should at least give you stable performance.
 
  • Like
Reactions: mountainview
Some of these behaviours are to be expected - to increase compatibility across as many devices as possible with a smooth operation, we simply have to cut back on many other variables such as the way metadata is presented. UPnP devices vary so hugely that we have to adapt the platform so that you can customise more with maximum resolution, DSD support and how track data is transmitted to your own system. If it works, great! If not, then compatibility will be the best we can offer for now, which should at least give you stable performance.
The implementation sounds and works really promising. The Phantoms are certainly not the easiest to manage via UPnP, but so far no issues :)
 
  • Like
Reactions: Stephen Healy