Asset UPnP v4

[Spoon]

Re: Asset v4 WHS2011 "networked data"

Asset R4 Released

[acjv]

Re: Asset v4 WHS2011 "networked data"

You're right; it only works when you're not running Asset as a service. The junctions did not work either, as they're not allowed to non local discs. I have the USB disks mapped to a drive letter, and that works fine.

Arthur

[Spoon]

Re: Asset v4 WHS2011 "networked data"

If you add folder in Asset then it should allow selection from the Network tree.

Mapping the drive possibly will not work for Asset running as a service (not 100% sure though, it is worth a try).

[dvdr]

Re: Asset v4 WHS2011 "networked data"

Arthur
there are just two things that I can think of:
a.) if the VM treats them as "network locations", try mounting the network location as a "local disc" by giving them a drive-letter and point Asset to that drive letter
b.) links will not work, create junctions. On my WHS2011, I am working with junctions, and Asset works. Only downside at the moment is, that (used to work before) the automatic rescan doesn't start, when I add new music to the music-folder, that is referenced via the junction.

I am running (as a test) WHS2011 as a VM, and have several USB disks containing music data connected to the host machine (mac). As the VM sees the disks as "network locations" they seem invisible to Asset (running a registered version of WHS2011). I tried creating links in the local Music dir to the locations where the actual data resides, but Asset won't be fooled. If I copy some of the data to the local disk, it sees the data, and adds it to its db. Is there a fix for this, a workaround, or am I trying to do something that can't be done. In that case, networked data is a no go.

Arthur

[acjv]

Asset v4 WHS2011 "networked data"

I am running (as a test) WHS2011 as a VM, and have several USB disks containing music data connected to the host machine (mac). As the VM sees the disks as "network locations" they seem invisible to Asset (running a registered version of WHS2011). I tried creating links in the local Music dir to the locations where the actual data resides, but Asset won't be fooled. If I copy some of the data to the local disk, it sees the data, and adds it to its db. Is there a fix for this, a workaround, or am I trying to do something that can't be done. In that case, networked data is a no go.

Arthur

[Spoon]

Re: Asset UPnP v5

It will not make the final release...

[DaFork]

Re: Asset UPnP v5

Asset cannot currently search for partial matches.

That explains it, thanks I tested it and it behaves just like that. Put partial matches for artists and album names on the list of features that ship with v4 final please :-)

[Spoon]

Re: Asset UPnP v5

Asset cannot currently search for partial matches.

[DaFork]

Re: Asset UPnP v5

DaFork,

The final release of Asset will correct the search feature with Bubble (bubble also has to be updated also, to accept '*'). Can you switch on the debug feature of Asset then do some searches you think are not properly handled then post the debug log?

Now that I switched on 'force upnp search' in Bubble it works. However I am wondering if other tags than the title tag will give results as well in an upcoming version of Asset. If I search for 'dire' I do not get results matching 'Dire Straits'. This is likely as intended for now, but am wondering if it would be up in a future release. If that should already give results I can post the log you request of course.

[Spoon]

Re: Asset UPnP v5

DaFork,

The final release of Asset will correct the search feature with Bubble (bubble also has to be updated also, to accept '*'). Can you switch on the debug feature of Asset then do some searches you think are not properly handled then post the debug log?

[Spoon]

Re: Asset UPnP v5

Upstream artwork just uses the first file which has artwork, be it folder.jpg or embedded. You cannot guarantee which order the files will be scanned in.

[DaFork]

Re: Asset UPnP v5

Quick update on BubbleDS (Android UPnP control point) usage for UPnP search on the r4 latest beta: BubbleDS 1.4.1 was released yesterday. If you force UPnP search enabled under the advanced options menu, search will give back results. Asset does not (yet?) correctly broadcast its support for search to control point software.

Furthermore: Asset r4 seems to support a limited search though, the search will only provide results if the pattern is part of a song name. You cannot search for other tags (artist, label, composer, ...), just song names. Although this already is a major improvement that I will use a lot, it would be nice if it could be extended.

[WonderingWho]

Re: Asset UPnP v5

Hi Folks,

I have a question on UpStream Artwork (i.e. artwork display when browsing Artist)....

Assume the following folder structure:

- Music

- Artist1

-Album1
-Album2

- Artist2

-Album3
-Album4

etc.

It appears as if Asset will use Album1's art for Artist1 and Album3's art for Artist2. i.e. it will extract the art from the first media file it finds (and this will be based on folder naming). and that it has to be in the media file rather than as a folder.jpg.

Is there perhaps a way to be able to stick a folder.jpg in the Artist1 and Artist2 folder and have it use that? This woud be much better, and allow the user to control which image is used without having to resort to a "dummy" file.

Or perhaps I am missing something obvious - not unusual!

either way let me know what you think.

cheers
s.

[Oliviander]

Asset UPnP v5

Hi Spoon, and everybody interested in the development of Asset UPnP
maybe this post would be more appropriate for the wishlist, but i would rather see a discussion from the users which are actually taking part in the beta installment of asset upnp server like myself.

The main reason I am using asset server software is the possibility to set up a search tree for the music collection that fits my taste, and therefore the support of custom tags.

May be I'm wrong but I guess there are many other users out there who have a similar motivation.

Clearly it is not wrong to implement new features in the software like Upnp search or the Dynamic searching, But I actually didn't miss it.

I would rather see a refinement of the possibilities of the classic search tree:
I actually have seen threads from other forum users that go in this direction, but I always had the impression that you didn't always really got the point of what they meant.

So as the Version 4 is going final I am sure the following suggestions won't fit but please consider
them for asset 5 (or maybe 4.1)

1. One should have the possibility to rename the tags, as they are sended to the Controlpoint.

This way it would be possible to adjust asset to other languages and it would be possible to use standard tags for other purposes which in some cases is easier than use custom tags.

Especially for the second use it would be appopriate to have the renaming on a search-tree-entry level
rather than a global renaming.
(and I guess this would be rather easier to implement than on global level).

I imagine the possibility to simply rename each element in the search tree independently, even if it is
the same tag in another position in the search tree, so that you can rename AlbumArtist to "Künstler(Album)" when you are in the Pop Branch of your Search tree and "Komponist(Album)" when you are in the Classical branch.

2. There should be an optional "ALL" entry on each level of the search tree

There should be the possibility to activate an "All" entry to a tag choice including all tracks that have
that tag regardless of its value, ignoring all tracks that don't have that tag.

3. There should be a function to select this "All" entry automatically

So why would I want those features 2 & 3:

Some people asked for conditional branching, meaning that the structure of the search tree
should depend on your choices of an upper level selection:
Assuming you would have a tag "MainGenre" with only 2 possible entries Pop and Classical
there then would be a different search tree depending on the Genre you select.

I think this kind of branching is simply too complicated to generate:
To get that same effect I would use 2 Tags "PopGenre" and ClassicalGenre" each tag only existing in the appropriate tracks. Using this tag on any level of the search tree, you can actually get the same effect. And as far as that, I can do this with Asset now as it is.

But when I select "PopGenre" I actually have to select between the genres even if I don't want to do it.
And even if there exists only 1 value for PopGenre in all my tracks and therefore is only one entry in the list - I have to actually select it to get to the next level of the search tree.
An Autoselection of all tracks that actually have this tag would spare me to do this selection.

Another possibility would be to actually use the "PopGenre" so that there would be more than one entry in the list
.
But in this case there should be at least the possibility to manually select "ALL" as for in some cases I do not envision a specific genre, while selecting the music.

Actually you could circumvent this problem if the Custom Tag PopGenre could handle more than one entry per track, then you could give the Tag two values a "specific" Value" and an "ALL" Value
and by that simulating the "ALL" entry suggested under 2.

This would be my main wishes Number 1 having the highest priority

Alternatively to number 2 & 3 you could implement:

4. Custom Tags should support multiple entries

I think I don't have to comment that. Should it be too complcated to do that really customized,
then you could at least make some standard tags custom1 - custom2 - custom3 which could be renamed to any name by point 1. (I could live with that)

Other wishes would be:

5. Possibility to Suppress any internally handled normalizations

I would like my tags to show up the way I wrote them in:
I don't want tho show up: "Beatles, The" as "The Beatles"
and I really I don't see how anybody would want his manually filled Values to
show up in any other form as written in.

I don't even have the chance to put anything in the tag that would show up as "Beatles, The"
which is the way I would want the Beatles to show up.

6. Sort Tags should work with mulitple Value Tags and should have the option to be used exclusively

As you outpointed in one post to me, the Sort tags don't work correctly with multiple entry Tags:
that should be fixed. And there should the option that only the sort Values are actually used in the search tree.

Why would I want point 5 and 6:
I would like to have Artists in the search list only with their SortValues as for Example:

[Artist] Tags of one track: "Martha Argerich" and "Gidon Kremer"
[ArtistSort] Tags of one track: "Argerich, Martha" and "Kremer, Gidon"

In the search tree ONLY the 2 sort sort values should show up:
"Argerich, Martha" and "Kremer, Gidon"

The artist values "Martha Argerich" and "Gidon Kremer"
should only be used for showing up in the now playing display (of the controlpoint and renderer).

Does anybody support my suggestions?

[WonderingWho]

Re: Asset UPnP v3.1

Just installed the Code Final for R4 (WHS addin version).

I had Asset v3 registered installed and running on WHS2011 (and using the Remote Launcher addin to provide shortcuts to Asset's config).
That was working reasonably well, but at times a bit sluggish with FLAC and my Cambridge Audio NP30.

Grabbed the WHS installer and it went on fine, no problems, picking up that it was registered. So far, very good. Liking the new artist artwork rendering, and it seems alot snappier - especially when refreshing the library. Will post more once I've been able to give it real test.