Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mud_shark]

I currently have around 90,000 audio files in JRiver.
I host an occasional community radio show.

A fair amount (let's say 50% for the sake of discussion) are suitable for inclusion in the radio show's playlists.
Whenever I'm trying to create a new playlist, I'd like to be able to just see the music that I've marked as being suitable for possible inclusion - so it basically halves the volume of tracks I need to sift through.

I was thinking of adding a keyword for suitable music, tagging the tracks from relevant artists (not a crazy amount) then having a JRiver view that only displays tracks with that keyword.

Is there a better way?

[zybex]

That's a good approach. You can also create a new field to classify the files as you need, but that is very similar to using the [Keywords] field anyway.

You can also create a playlist called "Not for Radio" (or something), drop all files there, then create a view with "file not in 'Not for Radio' playlist". Or the opposite: a playlist called "Radio tracks", then a view that only shows files in that playlist.

Personally I prefer the tag approach.

[marko]

Reads to me like the playlist route is absolutely the way to go... Why?

I would create a playlist group, call it, say, Radio.
Add a playlist for inclusion in radio
Add a playlist for exclusion in radio
Add a smartlist that includes all audio, excluding any audio in the other two playlists.

Next, create a panes based library view. The first pane needs to be that playlist group, other panes can be anything desired.
Pane tagging needs to be enabled. It is by default.

Now, the revelation...
In this view, selecting the smartlist will list music not yet reviewed for inclusion in radio. Select a track or tracks that should be included in radio.


Note the pane tagging check boxes that have appeared beside the two playlists in the first pane? Ticking one will place those selected files on that playlist.

If a file is no longer suitable for inclusion in radio, select the playlist in the pane, find the file and select it, tick the exclude playlist to add it there, untick the radio list to remove it from there.

All radio management can be right there, in one view, for example, easy creation of playlists for specific broadcasts via the "new playlist" item in the group pane.

Just a thought that sprang to mind upon reading

-marko

[mud_shark]

Ooh, this has been fun. Thanks to you both for your responses.

I tend to prefer Categories views rather than Panes, so have adopted a slightly hybrid solution which I think will work for me.

I have set up 3 Views:  Radio (songs tagged as being suitable), Not for Radio (songs tagged as being unsuitable) and Unassessed (tracks that contain neither the Radio or Not for Radio tags).

This gives me a clear view of each scenario.  (I love JRiver's versatility).

Thoughts?