Asset UPnP for Raspberry pi

[Spoon]

Re: Asset UPnP for Raspberry pi

The OS on the NAS could cache the file tree if it has not changed yes.

[simes_pep]

Re: Asset UPnP for Raspberry pi

Update 10th January

- Removed support for serving resized album art images on ARM machines
- Scanning no longer recurses into hidden folders (dot-prefixed, .folder).
- Greatly reduced CPU & RAM usage when refreshing large librarires
- Faster response to user requested library refresh
- Removed unnecessary full library rescan in certain configuration change scenarios.
- Improved internet radio compatibility.
- Improved application stability.

Installed last evening without issue. All seems to be functioning fine and stable.
The periodic rescan is using a lot less CPU & much quicker with my library of 17,504 tracks. What's cool, is that this doesn't cause the disks in ReadyNAS Duo NAS to spin up once 'Sleeping'. It is just using Cache? If so, pretty cool.
Thanks,
Simon.

[Spoon]

Re: Asset UPnP for Raspberry pi

Update 10th January

- Removed support for serving resized album art images on ARM machines
- Scanning no longer recurses into hidden folders (dot-prefixed, .folder).
- Greatly reduced CPU & RAM usage when refreshing large librarires
- Faster response to user requested library refresh
- Removed unnecessary full library rescan in certain configuration change scenarios.
- Improved internet radio compatibility.
- Improved application stability.

[dunc]

Re: Asset UPnP for Raspberry pi

Yes, with the CIFS Read Buffer at the max 16M, there can be some Naim buffer exhaustion and dropout at the end of playing a transcoded 24/192 track when the ND5 makes the request to 'Get' the next track in the playlist, to ensure that there is 'Gapless' playback. This happens about 30s-40s before the end of the current track. The RPi is still processing the current buffer with the current track. So I have gone back to the default CIFS Read buffer size and everything plays fine during the track and at the end. Obviously there is more of a continuous stream of CIFS reads from the RPi to the NAS, with only a 60K buffer, but this seems to be fine over the 'Ethernet over Mains' connection.
So the 'take away' from this is, if you have to use 'Mains Plugs' because you are unable to have a hardwired Ethernet connection between NAS, UPnP Server and Network Player, make it between the UPnP Server and the NAS, and not the Network Player and the UPnP Server.

Network Player <---Hardwired Ethernet---> Asset UPnP on RPi <--Ethernet over Mains--> NAS over
Network Player <--Ethernet over Mains---> Asset UPnP on RPi <--Hardwired Ethernet---> NAS

Thanks,
Simon.

Hi Simon, I've been away for a few weeks, great to see you got this sorted, nice work!

Cheers,
Dunc

[dunc]

Re: Asset UPnP for Raspberry pi

Late reply-
You can start Asset by:
export home=<any path you want> && ./AssetUPnP
Overriding the home directory variable will cause Asset to store its configuration elsewhere.

Even later reply:
Thanks Spoon, and I also spotted the note in a more recent release about using AssetUPnP.LocalConfig

[simes_pep]

Re: Asset UPnP for Raspberry pi

It was set to 100 and was displaying the output incorrectly - ordered A-Z and not by most recent etc.

So with ~18,000 tracks is 60 better?

Thanks,
Simon.

[Spoon]

Re: Asset UPnP for Raspberry pi

Which Count number did you set to when it did not work?

60 minutes is a tradeoff, people who have huge collections do not need it rescanning all the time.

[simes_pep]

Re: Asset UPnP for Raspberry pi

All seems to be working fine.

Quick question on the Playlists - How are these worked out? So, how 'New' is new i.e. the age of the album/track to be included in this playlist, also how 'Recent' is recent? What makes a 'Top Artist' etc.

Also could these be configurable? Or ordered as the newest album/track, most recently played, etc?

Thanks,
Simon.

Sorry - they seem to be working properly again - setting the Dynamic Playlist Item Count to '50', which I think was the previous Default, has the 'New Albums' entry listing them in 'newest' order.

Also I see there is now a 'Check for New Tracks Interval (minutes)' setting - this new setting is defaulted to 60 minutes. Before this was configurable, did I read that this was 15 minutes? What is ideal?

Simon.

[simes_pep]

Re: Asset UPnP for Raspberry pi

Update 30th January

- Fixed more radio handling bugs
- Put AssetUPnP.LocalConfig file ( command: touch AssetUPnP.LocalConfig ) to force storage of configuration data in Asset's installation directory
- MP3 encoding disabled for performance reasons
- Improved album art picture caching - reduced CPU usage with repeated album art requests

All seems to be working fine.

Quick question on the Playlists - How are these worked out? So, how 'New' is new i.e. the age of the album/track to be included in this playlist, also how 'Recent' is recent? What makes a 'Top Artist' etc.

Also could these be configurable? Or ordered as the newest album/track, most recently played, etc?

Thanks,
Simon.

[Spoon]

Re: Asset UPnP for Raspberry pi

Update 30th January

- Fixed more radio handling bugs
- Put AssetUPnP.LocalConfig file ( command: touch AssetUPnP.LocalConfig ) to force storage of configuration data in Asset's installation directory
- MP3 encoding disabled for performance reasons
- Improved album art picture caching - reduced CPU usage with repeated album art requests

[Batleys]

Re: Asset UPnP for Raspberry pi

Maccaa -yes it was immediately apparent on restart - there was some database corruption such that no albums were visible in the album directory - but all tracks could be selected individually - Anyway all ok now once reinitialised

Simon

[Maccaa]

Re: Asset UPnP for Raspberry pi

/

It could be Asset running a 'Detecting Changes Scan' but if you have not set that option, and manually request Asset to rescan to detect any changes.
It could be a NTP request - I have been seen, in the logs from my ReadyNAS Duo, that the disks have been woken up following a NTP check and update.
Is the time on your NAS set to be taken from a NTP source or are you setting it manually?

Simon

Thanks Simon, I have checked that the NTP option is off an have " stopped" all other packages except perl and mail server, as I am not sure if these are needed for functionality, ie is the mail server required to send mails for system functionality ie unsafe shut down emails etc, and not sure what perl does?

I am sure there must be a log to advise why it's waking, will keep looking.

Maccaa

[simes_pep]

Re: Asset UPnP for Raspberry pi

/

Batleys, was your database issue immediately apparent? as mine seems fie at present.

Another question to all if I may, did anyone find out why a NAS will happily go to sleep and then every so often wake up the drives, all lights back on, for no apparent rhyme or reason, and with no regularity (obviously I am not streaming at this time) almost as though Asset has woken it up?

Maccaa

It could be Asset running a 'Detecting Changes Scan' but if you have not set that option, and manually request Asset to rescan to detect any changes.
It could be a NTP request - I have been seen, in the logs from my ReadyNAS Duo, that the disks have been woken up following a NTP check and update.
Is the time on your NAS set to be taken from a NTP source or are you setting it manually?

Simon

[Maccaa]

Re: Asset UPnP for Raspberry pi

Batleys, was your database issue immediately apparent? as mine seems fie at present.

Another question to all if I may, did anyone find out why a NAS will happily go to sleep and then every so often wake up the drives, all lights back on, for no apparent rhyme or reason, and with no regularity (obviously I am not streaming at this time) almost as though Asset has woken it up?

Maccaa

[Batleys]

Re: Asset UPnP for Raspberry pi

A quick note to say, I had .dBpoweramp database issues when I upgraded, so I had to delete it; rm -r ~/.dBpoweramp and restart AssetUPnP, reapply config and all ok. (And of course beta trial duration gets reset as well)
Simon