INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Newbe - Fix database/library after changes  (Read 1385 times)

MighTiVo

  • Regular Member
  • Recent member
  • *
  • Posts: 26
  • nothing more to say...
Newbe - Fix database/library after changes
« on: April 10, 2003, 01:38:29 pm »

I searched and failed to find, I am sure this has been addressed before though.

New user so I had a lot of cleanup, moving of files with autorename, etc. Now I have enteries in the library that don't seem to point to the files anymore.
I tried Update library and that didn't seem to work, now I am trying to clear the library and reimport. A couple questions.

1)What is the best way to assure that the database/library don't get out of sync with the files.
2)When they do get out of sync what is the best way to get them back in sync.
3)What is the difference between library and database? I selected File-Library-Clear Library and was asked:
Are you sure you want to clear your media Library?
-- I assume this means it will delete entries for all media and I can reimport with no loss of any changes I made.
Next I was asked:
Do you want to clear your database fields and have them revert back to the defaults?
-- What does this mean?

Read the help and all it said was:
This will completely clear your library of all files and Playlist information. Be very sure that this is what you want to do. If it is, backup your library first, just in case you change your mind later and want to restore it.

In my case I said yes to clear the library and said no to restoring database and my views were changed. This is not what I expected.
Thanks in advance
Logged

xen-uno

  • Regular Member
  • Citizen of the Universe
  • *****
  • Posts: 2489
  • Checking your hard disk for errors...
Re: Newbe - Fix database/library after changes
« Reply #1 on: April 10, 2003, 01:49:34 pm »

1) Do all your media file moves and editing from within MC
2) You'll have to handle this on a case by case basis - follow (1) and then (2) won't occur.
3) There really is no difference...the library is the database. Some entries are stored in the files (ie Artist) and won't be lost, while others are database entries (ie Rating) and are history if you lose your library.


10-27

MighTiVo

  • Regular Member
  • Recent member
  • *
  • Posts: 26
  • nothing more to say...
Re: Newbe - Fix database/library after changes
« Reply #2 on: April 10, 2003, 01:52:32 pm »

Quote
1) Do all your media file moves and editing from within MC
2) You'll have to handle this on a case by case basis - follow (1) and then (2) won't occur.
3) There really is no difference...the library is the database

10-27


1- I did
3- Then why did it ask if I wanted to revert to default database after I said clear library?
Logged

xen-uno

  • Regular Member
  • Citizen of the Universe
  • *****
  • Posts: 2489
  • Checking your hard disk for errors...
Re: Newbe - Fix database/library after changes
« Reply #3 on: April 10, 2003, 01:57:10 pm »

MC has the ability to have several libraries. If you only have one then it IS the default library. The "Do you want to revert to Default DB" is contextually incorrect in this case.

10-27

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 42325
  • Shoes gone again!
Re: Newbe - Fix database/library after changes
« Reply #4 on: April 10, 2003, 02:06:29 pm »

Quote
Then why did it ask if I wanted to revert to default database after I said clear library


You can create custom fields like "Radio Station" or "Artist's Favorite Breed of Cat"

After MC removes the files from your library, it asks if you want to get rid of your custom fields.  Maybe we need to word it better...
Logged
Matt Ashland, JRiver Media Center

MighTiVo

  • Regular Member
  • Recent member
  • *
  • Posts: 26
  • nothing more to say...
Re: Newbe - Fix database/library after changes
« Reply #5 on: April 10, 2003, 02:12:30 pm »

Quote


You can create custom fields like "Radio Station" or "Artist's Favorite Breed of Cat"

After MC removes the files from your library, it asks if you want to get rid of your custom fields.  Maybe we need to word it better...


Thanks, that makes sense.

Is it correct to say that if I make all changes in MC that I shouldn't have any thing get disassociated and if it does I shuld try to figure what steps I did to cause it and report it as a bug?

Should there be any difference between:
clear database - save custom fields - re import media
and
Update library - no cleanup - update database fileds

If it should be the same it didn't seem to be as I still had disassociated files after cleanup.....
If it isn't supposed to be the same I don't understand the difference.

Logged

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 42325
  • Shoes gone again!
Re: Newbe - Fix database/library after changes
« Reply #6 on: April 10, 2003, 02:28:46 pm »

Quote
Is it correct to say that if I make all changes in MC that I shouldn't have any thing get disassociated and if it does I shuld try to figure what steps I did to cause it and report it as a bug?


Exactly.

Quote
Should there be any difference between:
clear database - save custom fields - re import media  
and
Update library - no cleanup - update database fileds


Well, clearing your DB discards saved playlists, smartlists, and view schemes.

Also, "Update Library->Cleanup->Remove files which do not exists" is the way to get missing files out of the MC database.

Thanks!
Logged
Matt Ashland, JRiver Media Center

nila

  • Guest
Re: Newbe - Fix database/library after changes
« Reply #7 on: April 11, 2003, 12:38:01 am »

Matt,
obviously not for this release,
but possibly for the next one (MC9.1 or whatever)
how about the possibility of creating a field inside the files (presuming the file types are capable of storing data in them) called: MJuniqueID or something and storing a Unique ID inside of the files.
That way if they're moved outside of MC, if we re-import them MC will spot the ID number and be like:
hmm, this number is already meant to be in my library at location X, why is it now at location Y and can then check to see if a copy is still at X and if it's not can prompt us to 'reassociated' all the new files with their db entries.

It would be a great tool to allow us to keep our db integrity when we play with the files outside of MC. :)
Logged
Pages: [1]   Go Up