Major db difference between Rip and other programs
Re: Major db difference between Rip and other programs
Can we not have both? RG info but not put into the file? XLD does this.
- disneymike
- Posts: 31
- Joined: Sat May 23, 2009 4:00 am
- Location: Murrieta, CA
- Contact:
Re: Major db difference between Rip and other programs
I tried Rip v1.0b12 with the RG calculation turned off, but I still get the same result in iTunes. I tried examining my AIFF file using iVolume and it indicates there is no iTunNORM Tag associated with the file. Apparently the iTunNORM tag can be embedded in the file, but it isn't on the AIFF file ripped using Rip. I'm not sure if this helps at all. Is anyone else getting proper volume levels using Rip v1.0b12?
Re: Major db difference between Rip and other programs
Was this with a new disc or one that you had ripped before?
- disneymike
- Posts: 31
- Joined: Sat May 23, 2009 4:00 am
- Location: Murrieta, CA
- Contact:
Re: Major db difference between Rip and other programs
This was with a disc I had ripped before with Rip v1.0b11.sbooth wrote:Was this with a new disc or one that you had ripped before?
Re: Major db difference between Rip and other programs
There is a new version of RIP? Great! I will try a few discs in just a couple of hours and report back. Thanks so much.
Re: Major db difference between Rip and other programs
Since this disc has been seen before, the RG data has been saved. To get rid of it you'll need to either delete Rip's data (~/Application Support/Rip/Ripped CDs.sqlite) or manually set the RG to 0 for the tracks/album.disneymike wrote:This was with a disc I had ripped before with Rip v1.0b11.
- disneymike
- Posts: 31
- Joined: Sat May 23, 2009 4:00 am
- Location: Murrieta, CA
- Contact:
Re: Major db difference between Rip and other programs
Thanks. That did the trick. I search Doug's iTune Scripts but found no script to reset the RG to zero. I guess I'll have to rip the CDs which were affected again. BTW, I'm still having issues with the automatically determined read offset either not returning a value or returning multiple values with low confidence numbers.sbooth wrote:Since this disc has been seen before, the RG data has been saved. To get rid of it you'll need to either delete Rip's data (~/Application Support/Rip/Ripped CDs.sqlite) or manually set the RG to 0 for the tracks/album.disneymike wrote:This was with a disc I had ripped before with Rip v1.0b11.
Re: Major db difference between Rip and other programs
I am having the same drive issues as well.
Also, for some reason I cant find the Album Art feature that existed in MX. I loved being able to query Amazon for album art but for some reason I cant seem to find it in the latest version of RIP.
Also, for some reason I cant find the Album Art feature that existed in MX. I loved being able to query Amazon for album art but for some reason I cant seem to find it in the latest version of RIP.
Re: Major db difference between Rip and other programs
If you choose Compact Disc -> Search For Metadata -> Amazon does it work?rydenfan wrote:I am having the same drive issues as well.
Also, for some reason I cant find the Album Art feature that existed in MX. I loved being able to query Amazon for album art but for some reason I cant seem to find it in the latest version of RIP.
There is no guarantee that drive offset detection will work for with discs- this depends on what information is in AccurateRip, track length, and disc integrity. Rip does its best to guess what the offset should be, but with a new drive you should always try with more than one disc to be sure you get the correct value.