More > JRiver Media Center 30 for Mac
DMG That Cannot Be Opened [Solved]
Day Radebaugh:
To be more precise in my question, what is the protocol for changing tags, saving them, and then refreshing MC screen to check results?
Thanks
blgentry:
Generally speaking, once you click out of a field where you made a change, or press enter, the tags are "set". These fields are saved in the MC database essentially instantly. The tags that are inside the files can optionally be written also. You can set this to be done automatically (I think that's the default) at:
Tools > Options > General > Importing & Tagging > update tags when file info changes.
You can make this happen manually by selecting one or more files and then: <right click> > Library Tools > Update Tags (from Library)
I've never done a lot of checking to see that the tags are written. When I do it manually it shows in the bottom status area. If you want to check the tags INSIDE the file from the Tag window, scroll down to the Tag Dump area and open it up. Then find the tag you are interested in. In my experiment just now, the Tag Dump (inside the file tag) was updated by the time I was able to scroll and click.
As I said, I believe that tags are written to the files fairly quickly if not instantly.
Brian.
Day Radebaugh:
These fields are saved in the MC database essentially instantly. The tags that are inside the files can optionally be written also...did you mean to say to the original music database?
[/b]
As I read your explanation, I get the sense that there are two places the tags live: a) inside my music file or b) to the MC database.
If this is correct, how are they related? Does MC import your music file, the derive from it a database of its own that it uses as tagging information?
I have another question please. Which of the tagging fields controls the display of the Artist screen? That is, I have a number of albums of related music. i would like to collect them under one item in the Artist screen, since they are (more or less) from one Artist. Which field does that?
Appreciate your help.
blgentry:
--- Quote from: Day Radebaugh on November 02, 2022, 04:21:04 pm ---As I read your explanation, I get the sense that there are two places the tags live: a) inside my music file or b) to the MC database.
--- End quote ---
Correct. The contents of the MC database are what you see reflected in all of the views of your music in MC.
--- Quote ---If this is correct, how are they related? Does MC import your music file, the derive from it a database of its own that it uses as tagging information?
--- End quote ---
I think you've got the right idea. When you have a brand new empty MC library, there's no data in the database. As soon as you import one or more files, MC reads the tags from the files and populates the database with their values for Artist, Album, song Name, etc.
You can edit these fields, and they are stored back in the database. Writing those same values back to the original music files is optional. There are some customers that never, ever, ever want MC to write values to their files.
The MC database can also store arbitrary fields that may not be supported by the music files themselves. For example you could import a bunch of WAV files, which have extremely limited tag support, and then edit lots of data about those files (Artist, Album, and lots more). MC knows that this data goes with these files. But it doesn't necessarily have to write it back to the files. MC only uses it's database to show you information about your files.
--- Quote ---Which of the tagging fields controls the display of the Artist screen? That is, I have a number of albums of related music. i would like to collect them under one item in the Artist screen, since they are (more or less) from one Artist.
--- End quote ---
Tricky question. Let's start with this:
The Artist "screen" is a database view. You can look at what fields it uses and other details by doing Customize View on it. You can make your own views! You can edit existing views. Though most of the basic views are locked and will warn you that they are locked. You can change them anyway, but you'll get a warning before you do.
How to solve your "related artists" thing is kind of up to you. It might make sense to establish a new field, or fields, for related artists. Or it might make sense to set them all to the same [Artist] field value. You also might use the [Album Artist (auto)] field for this. It really depends on the specifics.
I have a small number of artists like this. For example:
D'Angelo
D'Angelo and the Village Vanguard
For these two "artists" which are practically the same thing, I have the [Artist] field set to appropriate Artist name above. Some are the first one. Some are the second one. But for ALL OF THEM, I have the [Album Artist (auto)] field set to "D'Angelo".
I just checked my Artists view and it is grouping by [Album Artist (auto)] so this does what I want it to. That might work for you. If you want to check yours, go to the artists view and then pull down the little arrow next to the word Artists and select "Customize view". Cancel out of it after you look around a bit.
I think that's probably enough information for now.
Best of luck to you.
Brian.
Day Radebaugh:
You can edit these fields, and they are stored back in the database. Writing those same values back to the original music files is optional. There are some customers that never, ever, ever want MC to write values to their files.
I am among such users; believe that I would not want to write these changed tags back into the original music file, so I have disabled the default as you specified to not update tags when file info changes.
. I think, in terms of integrity, that it makes better sense to modify the tagging information that is unique and associated with MC, but to preserve the original music file intact.
For the second question, your example was spot on. i will follow your example, and distinguish among related artists (such as D'Angelo vs. D'Angelo and the Village Vanguard)
in the Artist field, but use the Album Artist to group them.
A final question: what is the Name field, and what does it do?
A final final question that is a bit off-track. I'm using a package called Amvidia Tag Editor to manage the tags in my 600 GB music file or database. I've massaged these tags endlessly over the past several weeks to get the results I desire. I submit this re-tagged file to Audirvana, which is my current library manager, and find that they don't give me the results I want. So i further tweak the tags inside Audirvana, sometimes to good effect, sometimes not. Would it be reasonable to assume that the tag tweaking I do in Audirvana is similarly just held in a database that Audirvana keeps locally (that is, for their own use only) and not written back to my original file? I am not aware of any parameter inside Audirvana that controls whether such tags are or are not written back into the original music file.
Thank you again. This is enormously helpful.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version