INTERACT FORUM
More => Old Versions => JRiver Media Center 25 for Windows => Topic started by: mattlauck on April 10, 2019, 11:03:52 am
-
Using MC 25.0.18 (64 bit on WIN10)
I have many user-created relational fields set up for various meta data that is useful for me to sort and view my large collection.
It doesn't seem to update new files as it once did. ?
Example:
I set a field for '* Year Formed'.
I populate it for an artist.
I import a new album for that artist.
Before, the '* Year Formed' field would auto populate with the relational data.
Now, it does not.
If I have the artist already in my library it will update all with the relational data when I set it.
If I import new files by that artist, it will not.
The library fields are set up as follows:
Data Type 'List (semi-colon delimited)
Relational 'one value for each album artist (auto)' - thanks again for this new change!
Edit Type 'List'
and I have the data saved inside the tags.
This is very important to me as it GREATLY improves my work flow.
I set up a fields for '* Music Genre', '* Year Formed', '* Country of Origin' '* Years Active', '* Artist Tagline', '* Associated Artists'.
I set ONCE and every everything is updated including my future imported files.
-
I'm on the case, but it's proving pretty tricky. More as I make more progress.
-
Ah. I have a couple of custom relational fields, and I did notice this once. But I wasn't taking enough notice to be sure. In my case, it is for video. I shall take more notice next time.
It sounds like you have seen the issue anyway Matt, so I just keep an eye on it.
-
Many thanks for the quick response and trying to track down this bug.
Good Hunting!
-
So next build we'll try setting the relational fields for all the newly imported files after the import finishes.
Here's the history:
Changed: After an import, relational fields are gone through and set on the new files.
Like I said, this was a pretty tricky one. So let me know how it works once the build ships.
Thanks.
-
Once again, Thanks!
I will watch for the new build and let you know.
-
Thanks Matt. I had not caught this either but confirm some relational fields are missing values