More > JRiver Media Center 21 for Windows
This tool is not available when connected to a server
blgentry:
^ A good number of people here auto import their files, but mark them with a Tag like "not approved" (or something similar). Then, they use an administrative view that specifically looks for that tag. The tag could be a key word, or a custom defined field that you set up. The point is simply that anything auto imported gets tagged and can be easily found with the admin view.
Then in the admin view, you review the relevant Artist, Album, etc, tags and make sure the they are correct. Editing them as you go until you like them. Then you just remove the "not approved" tag, and they are no longer in the admin view.
The really slick way of doing this, is to also modify your top level view(s) to *exclude* files with "not approved". That way new stuff only shows up in the admin view, until it's approved. After approval (and possible edits) it then magically shows up in all of the other views as appropriate. Note that this doesn't require much work. Just modify "audio" (for example) and EVERY VIEW under audio will follow the rule you just added to exclude "not approved" files.
I think it's a really nice solution for situations where you can't be confident in the tags of new files.
Brian.
Vocalpoint:
--- Quote from: Mike Foran on February 14, 2016, 10:10:30 am ---Is this not how anyone else uses JRiver? Is there a better way for multiple stations to add media to the shared library? Since this is the only means of getting support on this program I'd appreciate some feedback.
--- End quote ---
We have 5 PCs (and 4 iPhones/iPads) accessing JRiver in the house here - but none of the "clients" ever get to add anything to the master library. Our layout works as designed. Clients are clients and the server is the server.
Now for media admin - I do something a bit different but I find it much more flexible than allowing "clients" to mess with the master library.
On my personal workstation - I have my own local library set up which points to the identical location for the media as the shared library on the HTPC (Server) does. (\\MEDIA-PC\Music). There are no drive letters in use here.
When I need to add or change anything with the music or video - I do all the tagging work on my PC and simply move the results to the drives on the HTPC. Then the "server" instance of MC (running on the HTPC) picks up these changes (Has Auto-import) running and all clients instantly get the fresh new stuff.
This method allows me full access to the master "media" without dealing with having to use admin passwords, using a "client" connection to the library or getting any messages about tools not being available. It also ensures no family member can mess with the stash and ensures that I preside over all approved changes.
I also use a series of different "approved/non-approved" views - accessible ONLY on my PC to ensure the library is correct and everything that has been approved appears where it should be on "client" instances when accessed.
My personal PC never even connects to "client" library as I find it much easier to keep a local library for admin purposes.
Just another take on possibilities.
VP
glynor:
If you go with the Mark as Approved/Not Approved method mentioned above... Make your field [Approved] instead of the reverse, to make your life a bit easier.
Since all new files will initialize with fields set to blank or zero, then you won't need a Tag on Import rule to set everything imported to "not approved". All new files will automatically get [Approved] = 0.
Mike Foran:
--- Quote from: Vocalpoint on February 18, 2016, 11:39:42 am ---On my personal workstation - I have my own local library set up which points to the identical location for the media as the shared library on the HTPC (Server) does. (\\MEDIA-PC\Music). There are no drive letters in use here.
--- End quote ---
Thanks, this is similar to the way I am just now setting things up. I have essentially created a new local library that will be used for tagging and then RMCF to the network drive. With tags in shape, the server scoops them up and puts them in their proper place. I can then switch back to the shared library for general usage. This works ok for me, but is a little involved for other family members.
Mike Foran:
--- Quote from: glynor on February 18, 2016, 01:47:58 pm ---If you go with the Mark as Approved/Not Approved method mentioned above... Make your field [Approved] instead of the reverse, to make your life a bit easier.
Since all new files will initialize with fields set to blank or zero, then you won't need a Tag on Import rule to set everything imported to "not approved". All new files will automatically get [Approved] = 0.
--- End quote ---
This and the previous comment are a good idea. I'll implement something like this to easily identify tracks I didn't personally enter into the library.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version