Print

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

[AustinBike]

I have a lot of older music in my collection that was ripped back when I only had a 4GB mp3 player so it was ripped at 128-bit.  Now that I have a bigger player and listen to more over my stereo, I have been updating to 192-bit for better sound.

I set up a view that is low bit rate (128-bit or less) so that I can refresh my library.  I re-ripped a CD at 192VBR and imported it into my library (I deleted the older files first).  In other programs, the files show up with the right bit rate, but in MC it still shows up as 128.

How do I refresh this?

[scthom]

Try selecting the files you just imported, and then Update Library from Tags.

Though, typically, an import will do this automatically.

[Mr ChriZ]

VBR = Variable bit rate, ie it goes up and down, so you can't select 192 bit rate.
The displayed bit rate should vary from track to track.

[AustinBike]

User error.  I found the "update library" command.

Why isn't this part of the "import process"?  If I delete a file from the library and then re-import, the program should pull from the new file, not its old data.

[AustinBike]

VBR = Variable bit rate, ie it goes up and down, so you can't select 192 bit rate.
The displayed bit rate should vary from track to track.

Actually, they all showed 128.  All of the other VBR files show various bit rates.

[AustinBike]

Try selecting the files you just imported, and then Update Library from Tags.

Though, typically, an import will do this automatically.

Yes, this fixed it.  However the import did not do this automatically.  Bug or feature?

[Mr ChriZ]

Did you delete the original files from within MC?

I guess if you ripped the files using something else, over writing the
original files, then MC wouldn't have known to reimport them?

Saying that if you have Auto Import switched on, with
"Update for External Changes" activated, then it should still pick
up the changes... if it doesn't then I'd imagine that's a bug.

[scthom]

User error.  I found the "update library" command.

Why isn't this part of the "import process"?  If I delete a file from the library and then re-import, the program should pull from the new file, not its old data.

It is, but for some reason which I am not able to guess, it either didn't happen or it used the old info instead.

[AustinBike]

Did you delete the original files from within MC?

I guess if you ripped the files using something else, over writing the
original files, then MC wouldn't have known to reimport them?

Saying that if you have Auto Import switched on, with
"Update for External Changes" activated, then it should still pick
up the changes... if it doesn't then I'd imagine that's a bug.

So here are the steps:

1. re-rip files on my notebook
2. go to server, delete originals
3. copy from notebook to server
4. run import (files not imported, of course)
5. run import with "ignore deleted" turned off
6. new files show up with old bit rate
7. run "update with file data"
8. files now show right bit rate

[Mr ChriZ]

So here are the steps:

1. re-rip files on my notebook
2. go to server, delete originals
3. copy from notebook to server
4. run import (files not imported, of course)
5. run import with "ignore deleted" turned off
6. new files show up with old bit rate
7. run "update with file data"
8. files now show right bit rate

Sounds like a bug to me  

[scthom]

I don't think it's a bug.  The files have to be deleted from the library, not just from the hard drive.
When you delete the files, do it from within MC so it removes from the library first.  Then, it will be a new import and will import correctly the first time.

[PPatla]

MC 11 used to catch this properly.  This seems like a bug in 12, I've gone ahead and used Tag and Rename to put new tags on files that had none and JR MC 12 doesn't catch the updates.  This used to work fine with 11.