INTERACT FORUM

More => Old Versions => JRiver Media Center 18 for Windows => Topic started by: jaynyc on February 05, 2013, 06:50:22 am

Title: Playlist columns vs. primary view columns
Post by: jaynyc on February 05, 2013, 06:50:22 am
I have a customized primary view.  When I make a playlist, the columns shown are different than my primary view.  How do I force all playlist columns to be the same as my primary view?
Title: Re: Playlist columns vs. primary view columns
Post by: MrC on February 05, 2013, 07:02:19 am
You can save Presets.  Right-click a column, and notice the Presets sub-menu.  Setup your column choices, and then save as a named preset.  You can then reload this preset elsewhere.

Note that Playlists are a list of files with a sequential order, and the column Seq will be automatically included.
Title: Re: Playlist columns vs. primary view columns
Post by: chrisjj on February 05, 2013, 07:43:06 am
You can save Presets.  ... You can then reload this preset elsewhere.

This is a great feature.

Note that Playlists are a list of files with a sequential order, and the column Seq will be automatically included.

I'd love to get this to work in a primary view of a playlist, but Seq is always zero:

(http://img152.imageshack.us/img152/1140/jrmctestwindowsvirtualp.png)

Any ideas?
Title: Re: Playlist columns vs. primary view columns
Post by: MrC on February 05, 2013, 11:41:21 am
Sequence doesn't make sense on a playlist Group.

There can be more than a single playlist contained by the group, and sequence order for the same track in those playlists may be different.  For example, Track A may be sequenced in position 5 in Playlist A, but in position 100 in Playlist B.

Further confounding group-level sequencing is that the group may contain smartlists, which have no inherent sequence.
Title: Re: Playlist columns vs. primary view columns
Post by: chrisjj on February 05, 2013, 06:23:46 pm
Sequence doesn't make sense on a playlist Group.

I think that depends on how you're using playlist groups. It would often make sense for me.

There can be more than a single playlist contained by the group, and sequence order for the same track in those playlists may be different.

Most useful for playlist work would be for the list to show instances not tracks, and for multiple playlists, show a concatenation - and Seq according with that.

... the group may contain smartlists, which have no inherent sequence.

It seems to me  every smartlist has inherent sequence from its (default or explicit) sort.


Title: Re: Playlist columns vs. primary view columns
Post by: MrC on February 05, 2013, 06:29:43 pm
You made an observation, and I commented on why I think it is the way it is.

But now it seems you really have feature or change requests.

Smartlist sorts may be random.  So what does a sequence number mean generally in this case?
Title: Re: Playlist columns vs. primary view columns
Post by: chrisjj on February 05, 2013, 06:37:31 pm
But now it seems you really have feature or change requests.

Well, if getting Seq to show something more useful than 0 is a feature or change request, then yes.

Smartlist sorts may be random.  So what does a sequence number mean generally in this case?

Same as usual - it means the position in the current sequence.
Title: Re: Playlist columns vs. primary view columns
Post by: JimH on February 05, 2013, 07:54:17 pm
Well, if getting Seq to show something more useful than 0 is a feature or change request, then yes.

You may not realize it, but your posts come across as very demanding.
Title: Re: Playlist columns vs. primary view columns
Post by: chrisjj on February 06, 2013, 04:38:17 am
Well, if getting Seq to show something more useful than 0 is a feature or change request, then yes.
You may not realize it, but your posts come across as very demanding.

Please don't mistake that request for a demand, Jim. If Seq can be made to give sensible values in such a view, I'd be delighted, but if not, fair enough.