Re: Asset UPnP v3 Discussions
Re: Asset v3 05 June release, Album By Release is still not consistent.
Some directories are sorted with newest releases first, some are sorted with newest releases last.
Asset UPnP v3 Discussions
Collapse
X
-
Re: Asset UPnP v3 Discussions
@spoon - yep - goes into counting tracks mode, then works its way through the whole directory structure rebuilding all the track information. By the way, it does this even though I've unticked the automatic rebuild option.Leave a comment:
-
Re: Asset UPnP v3 Discussions
Deleted the old one and installed the one that is currently linked to download.
Did a full rebuild, then another just in case, but no go.
Please let me know if there's any debug info I can gather.
thanksLeave a comment:
-
Re: Asset UPnP v3 Discussions
I have tested the latest version of Asset (released today 5th June) against the latest KinskyDesktop v3.3.6 and the 'Composer as Artist' does not seem to be an issue.
If anyone who was having troubles if you can try the latest Asset and do a full rebuild of the database.Leave a comment:
-
Re: Asset UPnP v3 Discussions
@dvdr - yes I think it is, I will look into this.
@petes - when you say that asset is reindexing its database - you can see in Asset Configuration that is it 'Counting Tracks', etc?Leave a comment:
-
Re: Asset UPnP v3 Discussions
Are V3-betas from 25.&26.5 mistakedly putting out "Conductor"-tag-entries into Plugplayer/Songbook, where the Artist should appear in the playlist and Playing Now?
What I see in Playing Now is:
Track title
Album title
(unknown conductor)
if the track does not have a conductor's tag, otherwise, the conductor's name is displayed there.
With all previous versions, I saw:
Track title
Album title
ArtistLeave a comment:
-
Leave a comment:
-
Re: Asset UPnP v3 Discussions
WMP is accessing the music through UPnP only (asset)?Leave a comment:
-
Re: Asset UPnP v3 Discussions
OK - worked something out. It's actually something to do with WMP12 / Win 7. When WMP12 hits the server to get a list of tracks, it's causing the server to rescan it's db. Tried some other clients today, and it's nice and stable. As soon as I point WMP12 at Asset, the server goes into constant rebuilding mode.Leave a comment:
-
Re: Asset UPnP v3 Discussions
It is worth a try, also try playing back through your PC (with the force to LPCM option selected), you can install dbpoweramp renaissance to enable the PC to become a UPnP Renderer (player):
http://forum.dbpoweramp.com/showthread.php?t=17415
This will test lpcm playback, it could be the bdp-80 has an issue where as the bdp-83 does not.Leave a comment:
-
Re: Asset UPnP v3 Discussions
Thank you for your answer!
Since the BDP-80 only supports UPnP since a firmware update two days ago, I had no other version of Asset UPnP installed before that.
I just installed the newest beta version and found myself confronted with the white noise issues.
Do you think uninstalling the beta and installing v2.1 would still be worth a try?
Regards,
nosurrenderLeave a comment:
-
Re: Asset UPnP v3 Discussions
Yes please email:
nosurrender - make sure you unninstall the old version first, we keep the version numbers the same for a beta so to get the lastest install uninstall (install v2.1 registered if you have that), then v3 over the top.Leave a comment:
-
Re: Asset UPnP v3 Discussions
So, I don't see alot in the log file - just that it finishes scanning, having skipped some files as "in use", and then starts again. Could I email it to you to see if there's anything you can tell me?
pete SLeave a comment:
-
-
Re: Asset UPnP v3 Discussions
@Petes
Close down asset, then enable the debug option in Asset Configuration, let it do a scan, and the next one then stop asset and look in the log, it will state what triggered the scan.Leave a comment:
Leave a comment: