Print

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

[comox]

1. NEW: Added a new field "Source" for image media type, and mapped it to IPTC and XMP "Source" tag.

I have a user field named "Source".
Do I need to rename it before installing 31.0.74?

[marko]

You can't rename fields. Only their display names can be changed. Best to create a new user field, copy the existing data from source to your new field, then install 74 🙂

[comox]

Ouch. My Source is saved in file tags. This means changing 3 TB of audio files which I really don't want to do.

Any other solutions?

Perhaps MC should append "(1)" to new standard field names when a collision with a user field is detected? Just like it does when a filename collision is detected.

[marko]

Is your field saved in the files for use in other software? If not, you don't really need it saved in file. The regular automatic library backups will preserve your data. Deselect the save in file tags option for that field. Create your new field, without activating the save in tags option for it for now. Copy the data from source to new field.
Install 74 and test. Pick a file, do an update library from tags on it. Does it populate the new source field? Figure out what you want to do from there...

[bwaldron]

Ouch. My Source is saved in file tags. This means changing 3 TB of audio files which I really don't want to do.

Ouch here also! I have always used a user-defined Source tag for my (over 40K) audio files. I do save it to the files and use it in other software -- not to mention that I use it in a number of JRiver smartlists.

I have already upgraded from .43 to .74 today to get access to the new Date Last Rated field, which I have use for.

Obviously I have some thinking and work to do...

[JimH]

Source is an image tag.  I don't think it will affect audio files. 

[comox]

Source is an image tag.  I don't think it will affect audio files.

I fill in Source for all files types in my library.

What will happen to my data in Source assigned to image files?

Please also confirm that if I leave my Source field as is, nothing will break with my audio files.

[bwaldron]

Source is an image tag.  I don't think it will affect audio files.

Correct, it doesn't. Thank goodness the data that I had previously stored in the field/tag remains in all my files and in the library. 

However, my user-defined Source field that I used for audio is gone in Manage Library Fields (including the acceptable list values I specified). I can create a new MySource field and copy all existing Source field data to it. I will need to change my various views and smart lists to use this new Field. I will also need to write the new tag to all my audio files, and change the other applications where I use the tag to reflect the change.

Backing up all the changed files -- especially to my online backup storage -- is going to take some time.

Nothing fatal, but no fun. That's life!

[JimH]

We don't really have a choice if we want to support standards. 

It's pretty easy to copy tags to a new location.  Start a thread if you want help.

[mattkhan]

We don't really have a choice if we want to support standards. 

It's pretty easy to copy tags to a new location.  Start a thread if you want help.

you have a simple alternative, for fields that have a name coming from upstream, add a prefix consistently (e.g. IPTC_Source)

if you don't do that, I think this suggestion is surely a must have otherwise your default setup (auto update enabled) seems careless with user data

Perhaps MC should append "(1)" to new standard field names when a collision with a user field is detected? Just like it does when a filename collision is detected.

[bwaldron]

We don't really have a choice if we want to support standards. 

Of course. However, I use JRiver only for audio, and have done for decades now -- since the Media Jukebox days. Source is not a standard audio tag, so I have always felt safe using it as a custom tag for my library.

It's pretty easy to copy tags to a new location.  Start a thread if you want help.

No help needed. Copying the tags is simple. Replacing the old tag with the new one in all my view schemes and smartlists is also simple -- but a good bit of work. I would also need to reflect the change in the other applications that use my custom tag.

The big issue for me is having to overwrite all my audio files to my local backup sets and to cloud storage. Since I write the Source field/tag to my audio files, all 58,505 of them need to be overwritten. My internet service has only 20Mbps upload speed -- we're talking a *long* time to upload.

[JimH]

We'll see what we can do.  No promises.  For now, I've pulled the build.

[comox]

Thank you for trying to find a solution.

[bwaldron]

Thank you for trying to find a solution.

I second this

[JimH]

Please try this build:  https://yabb.jriver.com/interact/index.php/topic,137207.0.html

[bwaldron]

Wonderful! Thanks so much to you and Matt.

[elprice7345]

I too had a custom user field named "Source".

I upgraded to v76 per this thread and now my custom field is back, but all of the "Acceptable Values" are gone from the "Manage Library Fields Screen".

They still show in the drop-down list, but not in the "Manage Library Fields Screen", therefore, I can't modify or add any new values.

I can manually recreate them, but I was hoping there is an easier way. They must still exist somewhere in MC, because they show up in the drop-down list.

TIA

[Hendrik]

The easiest fix would be to restore a backup from before 31.0.72 to get everything back to normal.

[elprice7345]

If I restore from a backup, won't I lose all changes made after the backup?

[JimH]

If I restore from a backup, won't I lose all changes made after the backup?

Yes.

[comox]

If I restore from a backup, won't I lose all changes made after the backup?

Back everything up before you try this, but what I would try in your situation is extract the file "field (source).jmd" from your last backup and then overwrite the existing fie in your JRiver library folder.

Then filter on all files imported since the last backup and re-enter the missing source data.

[elprice7345]

All good now!

I exported a playlist with the Source field, found the unique values, and then copy and pasted them into the custom field.

Much easier than backing up, restoring and making all my changes again.

Thanks for your help!