Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: CUETools versions 1.9.5 through 2.1.6 (Read 1894430 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1600
However it turns out CUETools.ConsoleRipper.exe does not seem to be entirely compatible with the MATSHITA DVD-RAM SW-9584 mechanism that is in the changer.

This seems to be a rare drive, there's only one submission in the database that uses this drive (unsuccessful rip of Genesis - Abacab), and i assume it's yours. Does EAC work ok with this drive?

I am also curious if CUETools.ConsoleRipper.exe has the ability to submit to the CUETools DB.

No, it doesn't. It was basically a test project for CUERipper development. It could be turned into a fully functioning CD ripper by adding a few features, if there is a demand for this, but this is not a priority right now.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1601
It seems that the disk two and three has the confidence from the AR database and was submitted to the database by CUETools, but the second disk was ripped with CUERipper or EAC. Why doesn't the second disk has the same confidence as the as AR confidence (36)?

Maybe, once a rip has been made, the confidence level should include only the submitted rips, and only a disk without a rip, submitted by CUETools, should have the AR confidence level.

A confidence level beyond 2 or 3 becomes irrelevant for checking the accuracy of a rip. But I like statistics, and the confidence level tells you how popular a disk is, unfortunately this is not possible right now.

When the database was created, we had only AccurateRip confidence levels to go on. There was also hope of a closer integration with AccurateRip, which would allow the database to update confidence numbers directly from AR.

By the time EAC plugin was created, it have become clear that there will be no integration with AccurateRip, so new submissions from EAC don't use AR confidence levels.

In the near future, i plan to reset CTDB confidence levels to the actual number of independent submissions.

You'll have AccurateRip confidence scores in your ripping log anyway, so what's the point to duplicate them in CTDB section.

The only drawback is that when repairing a rip, you'll have to re-verify it after repair to find out AccurateRip confidence levels for the repair result. But this can be fixed. I will probably have to make CUETools show the "future" AccurateRip verification log when selecting an entry to use for repair. Does this make sense?
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1602
Thanks. I will have to re-generate the logs for my entire collection, so I can feed updated data in my charts and pies generating scripts  can't wait for the reset.

I think that the cases when a rip is repaired are so rare that a re-check isn't that big of a deal.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1603
This seems to be a rare drive, there's only one submission in the database that uses this drive (unsuccessful rip of Genesis - Abacab), and i assume it's yours. Does EAC work ok with this drive?
Yep that was probably mine, sorry.  The drive works great with EAC as well as dBpoweramp.  With EAC it works best if I leave over read disabled.  With dBpoweramp it works best leaving C2 disabled as well.  EAC works just fine with C2 enabled with this drive however.  Are there any logs I can provide to get to the bottom of this? I really appreciate your help!
No, it doesn't. It was basically a test project for CUERipper development. It could be turned into a fully functioning CD ripper by adding a few features, if there is a demand for this, but this is not a priority right now.
Even with its limited features it pretty much does exactly what I want if only it would work properly with my drive.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1604
hi gregory... i've been using cuetools for a few versions now and i love the product and the constistent improvements. 

i have been wanting to use the cue ripper and responded to this thread about problems i was having and am hoping you can help.

http://www.hydrogenaudio.org/forums/index....c=82797&hl=

Quote
i have the same error with plextor drives W2410A, fw 1.03 and W1210A fw 1.10. the error occurs on windows XP and windows 7 x64, and three different physical computer systems. cueripper freezes when you hit "go" and it starts "detecting drive features..." it will take about 5-10 minutes, the give the error "Error Reading CD IoctlFailed". after that the drive is dead in windows and i have to reboot to get it back.

i have an internal laptop drive that is ok (HL-DT-ST DVD+RW GSA-T21N A1R1) and which can rip a CD, so i know the application works. when i try the same system with the plextors, it does not work.

any ideas?


the drives are both ide, and i have tried them through USB enclosures as well.  i do have a SCSI version of the 1210 but i have not brought it home yet.

what do you think?

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1605
It's sad. Unfortunately, support for old drives is not my priority. I don't have that drive, and even if i could get one, by the time i'm done with it i would probably be one the last people on earth who use it  I'm much more concerned with support for new drives, which EAC often has problems with. Of course i'd like CUERipper to at least fail gracefully when encountering unsupported drives, so i'll try to look into it.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1606
hallo dear developer

what you see is a difference in appearance when you change display 100% to 125% in win 7. you cant see or access offset settings (right on the bottom of the window). also you notice a strange border on the left side, which i can live with, but also would be happier without it. would you PLESE fix it in your next release?

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1607
I'll try
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1608

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1609
It's sad. Unfortunately, support for old drives is not my priority. I don't have that drive, and even if i could get one, by the time i'm done with it i would probably be one the last people on earth who use it  I'm much more concerned with support for new drives, which EAC often has problems with. Of course i'd like CUERipper to at least fail gracefully when encountering unsupported drives, so i'll try to look into it.


i am pretty sure i have an extra ide of the 1210a... i'd be happy to send it to you without any need to return it.  they're pretty reliable and it'd be great if your app could work with them.  i had thought quite a few people still used these for their reliability and full feature set (accurate stream, c2 errors, HTOA, and overread into both).  i use the plextor-specific switch " -usefua" with eac to disable the write cache.

anything i could try in the meantime and maybe debug info i could send your way?  maybe the console ripper?

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1610
i couldn't edit my above post.

here is the log output of the console ripper:

Code: [Select]
C:\Users\user\Desktop\CUETools_2.1.1\CUETools.ConsoleRipper.exe -D d: -O +99 -P --be

CUERipper v2.1.2 Copyright (C) 2008-10 Gregory S. Chudov
This is free software under the GNU GPLv3+ license; There is NO WARRANTY, to
the extent permitted by law. <http://www.gnu.org/licenses/> for details.
Drive       : d: [PLEXTOR  CD-R   PX-W1210A 1.10]
Read offset : 99
Read cmd    : BEh, 12h, , 16 blocks at a time
Secure mode : 2
Filename    : Jimi Hendrix - Kiss the Sky.wav
Disk length : 46:42:40
AccurateRip : ok
MusicBrainz : Jimi Hendrix - Kiss the Sky

Error: Error reading CD: IoctlFailed
   at CUETools.Ripper.SCSI.CDDriveReader.FetchSectors(Int32 sector, Int32 Sector
s2Read, Boolean abort)
   at CUETools.Ripper.SCSI.CDDriveReader.PrefetchSector(Int32 iSector)
   at CUETools.Ripper.SCSI.CDDriveReader.Read(AudioBuffer buff, Int32 maxLength)

   at CUETools.ConsoleRipper.Program.Main(String[] args)
[/size]

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1611
Thank you for your offer. I guess i should take it, because there's not much that can be done without having an actual drive to run tests on.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1612
At some point in the development adding a CTDB entry in the folder browser that would automatically sort "By CTDB Status":

- CTDB: Differs (maybe fixable)
- CTDB: Could not be verified (likely not fixable)
- CTDB: Not present in database (unknown)
- CTDB: Verified OK

would be interesting IMHO. CTDB is slowly becoming big enough to justify it.

As a side note, I don't have any grief anymore against the horizontal displaying in log for AR V2. I have tested AR V2 enough now to think that it didn't change anything noticeable for an end user at all. I wasn't too hot to adopt this instanly but my FUD is gone now & the longer logs are just annoying me now as, visually, I often mix them up with rips without fixed offset.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1613
Agree.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1614
Is there a possibility of changing the numbering format that the (HTOA) files are numbered?

The Cue looks like this..
Code: [Select]
REM ACCURATERIPID 00144f96-00d7aee7-b509520e
REM DISCID B509520E
REM COMMENT "ExactAudioCopy v0.99pb4"
PERFORMER "Green Day"
TITLE "Dookie"
CATALOG 0075994552927
REM DATE 1994
REM DISCNUMBER 1
REM TOTALDISCS 1
FILE "01.00. (HTOA).flac" WAVE
  TRACK 01 AUDIO
    PERFORMER "Green Day"
    TITLE "Burnout"
    INDEX 00 00:00:00
FILE "01. Burnout.flac" WAVE
    INDEX 01 00:00:00
  TRACK 02 AUDIO
    PERFORMER "Green Day"
    TITLE "Having a Blast"
    INDEX 00 02:07:37
FILE "02. Having a Blast.flac" WAVE
    INDEX 01 00:00:00
  TRACK 03 AUDIO
    PERFORMER "Green Day"
    TITLE "Chump"
    INDEX 00 02:44:46
FILE "03. Chump.flac" WAVE
    INDEX 01 00:00:00
  TRACK 04 AUDIO
    PERFORMER "Green Day"
    TITLE "Longview"
    INDEX 00 02:54:00
FILE "04. Longview.flac" WAVE
    INDEX 01 00:00:00
  TRACK 05 AUDIO
    PERFORMER "Green Day"
    TITLE "Welcome to Paradise"
    INDEX 00 03:59:04
FILE "05. Welcome to Paradise.flac" WAVE
    INDEX 01 00:00:00
  TRACK 06 AUDIO
    PERFORMER "Green Day"
    TITLE "Pulling Teeth"
    INDEX 00 03:44:46
FILE "06. Pulling Teeth.flac" WAVE
    INDEX 01 00:00:00
  TRACK 07 AUDIO
    PERFORMER "Green Day"
    TITLE "Basket Case"
    INDEX 00 02:30:59
FILE "07. Basket Case.flac" WAVE
    INDEX 01 00:00:00
  TRACK 08 AUDIO
    PERFORMER "Green Day"
    TITLE "She"
    INDEX 00 03:01:00
FILE "08. She.flac" WAVE
    INDEX 01 00:00:00
  TRACK 09 AUDIO
    PERFORMER "Green Day"
    TITLE "Sassafras Roots"
    INDEX 00 02:14:18
FILE "09. Sassafras Roots.flac" WAVE
    INDEX 01 00:00:00
  TRACK 10 AUDIO
    PERFORMER "Green Day"
    TITLE "When I Come Around"
    INDEX 00 02:37:44
FILE "10. When I Come Around.flac" WAVE
    INDEX 01 00:00:00
  TRACK 11 AUDIO
    PERFORMER "Green Day"
    TITLE "Coming Clean"
    INDEX 00 02:58:11
FILE "11. Coming Clean.flac" WAVE
    INDEX 01 00:00:00
  TRACK 12 AUDIO
    PERFORMER "Green Day"
    TITLE "Emenius Sleepus"
    INDEX 00 01:34:64
FILE "12. Emenius Sleepus.flac" WAVE
    INDEX 01 00:00:00
  TRACK 13 AUDIO
    PERFORMER "Green Day"
    TITLE "In the End"
    INDEX 00 01:43:71
FILE "13. In the End.flac" WAVE
    INDEX 01 00:00:00
  TRACK 14 AUDIO
    PERFORMER "Green Day"
    TITLE "F.O.D. / All by Myself"
    INDEX 00 01:46:28
FILE "14. F.O.D. _ All by Myself.flac" WAVE
    INDEX 01 00:00:00
Since i rip my files in track mode the (HTOA) files show up in explorer out of order.
e.g.


Would it be possible to have these (HTOA) tracks show up as 00 instead of 01.00?

Also another request, would it be possible to have a button added that would allow all the metadata to automatically change its capitalisation? much like how the feature in EAC.
Who are you and how did you get in here ?
I'm a locksmith, I'm a locksmith.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1615
I will add it to my list
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1616
Thank you kind sir
Who are you and how did you get in here ?
I'm a locksmith, I'm a locksmith.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1617
I have a decent bug report,

1. CUEttols doesnot popup the album info dialog before 1st conversion conversion if invoked by CUEtools <dirname>. On 2nd and further conversions the dialog shows correctly.

2. Could it have a better support for album info import, ie. manual Query for muscibrainz and Discogs, plus tracklist import and parsing from clipboard /or/ file

3. I still didnot get how "Fix offset" script really works. I guess that it should adapt the offset out of AccurateRip report with highest matches, but it don't so. Here's an example of AccuRip report:

Code: [Select]
Track   [ CRC    ] Status
01     [e274b577] (015/122) Accurately ripped
02     [5da97f6a] (014/121) Accurately ripped
03     [041db81b] (014/123) Accurately ripped
04     [00e56701] (014/122) Accurately ripped
05     [3f437ebd] (014/122) Accurately ripped
06     [894e8496] (014/120) Accurately ripped
07     [49bce785] (014/120) Accurately ripped
08     [3946afa4] (014/123) Accurately ripped
09     [1df65554] (014/120) Accurately ripped
10     [0820057c] (014/121) Accurately ripped
11     [cfca8f8f] (014/122) Accurately ripped
12     [03bf1bf3] (014/119) Accurately ripped
Offsetted by 664:
01     [10b8d6ef] (056/122) Accurately ripped
02     [6c0a3d7a] (056/121) Accurately ripped
03     [2b3eaa13] (056/123) Accurately ripped
04     [c61ae5e9] (057/122) Accurately ripped
05     [e933e195] (057/122) Accurately ripped
06     [1450505e] (055/120) Accurately ripped
07     [42063585] (055/120) Accurately ripped
08     [cdabef54] (056/123) Accurately ripped
09     [bf35f214] (055/120) Accurately ripped
10     [a295d98c] (056/121) Accurately ripped
11     [0443f077] (057/122) Accurately ripped
12     [6373387b] (055/119) Accurately ripped
Offsetted by 1387:
01     [a6f45f9e] (016/122) Accurately ripped
02     [dc14bc3c] (016/121) Accurately ripped
03     [e60b04d2] (016/123) Accurately ripped
04     [b3f83b46] (016/122) Accurately ripped
05     [88690c70] (016/122) Accurately ripped
06     [a6465157] (016/120) Accurately ripped
07     [caf97f45] (016/120) Accurately ripped
08     [98e4344a] (016/123) Accurately ripped
09     [8ec979ac] (016/120) Accurately ripped
10     [63d49b0e] (016/121) Accurately ripped
11     [61a4a214] (016/122) Accurately ripped
12     [dc3841e7] (015/119) Accurately ripped
Offsetted by 1492:
01     [a5673e5b] (019/122) Accurately ripped
02     [e0aaf922] (019/121) Accurately ripped
03     [8d631ebf] (019/123) Accurately ripped
04     [ddf3326d] (019/122) Accurately ripped
05     [684b9771] (019/122) Accurately ripped
06     [5bdee412] (019/120) Accurately ripped
07     [11d9e885] (019/120) Accurately ripped
08     [2a305c0c] (019/123) Accurately ripped
09     [08491ff4] (019/120) Accurately ripped
10     [f29dfc34] (019/121) Accurately ripped
11     [836301fb] (019/122) Accurately ripped
12     [b492e7eb] (019/119) Accurately ripped
Offsetted by 1522:
01     [12aca291] (008/122) Accurately ripped
02     [98d5e5f6] (008/121) Accurately ripped
03     [2aea0195] (010/123) Accurately ripped
04     [e9f1c22f] (008/122) Accurately ripped
05     [a8432cdf] (008/122) Accurately ripped
06     [d8e5e96c] (008/120) Accurately ripped
07     [93d0e205] (008/120) Accurately ripped
08     [9cd86768] (010/123) Accurately ripped
09     [4f922ae4] (008/120) Accurately ripped
10     [d2453c88] (008/121) Accurately ripped
11     [6874d43d] (008/122) Accurately ripped
12     [ce74a9a3] (008/119) Accurately ripped


Here the offset 664 has the highest match but CueTools didnot use it. The album was converted with existing offset. Could anyone explain?

3. And finally, is there available a complete list of all supported metadata fields and their mappings to media files tags,  that can use in Template field?

I'd Appreciate more foobar metadata and functions supported! Thank U !

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1618
3- CT will only "fix" offset to highest if you tick (Edit: Untick) the right radio button in the option, by default it "fix" to nearest, but as you rip is already found with the actual offset I am not sure it will fix anything.

Edit: In Settings/AccurateRip/Untick "to nearest" if you want to fix to Highest.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1619
Here the offset 664 has the highest match but CueTools didnot use it. The album was converted with existing offset. Could anyone explain?


I guess (not sure though) that 'fix' is only supposed to fix something when there are no matches with the current offset. But in your example, there is no need to fix anything, as the current offset matches already.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1620
Here the offset 664 has the highest match but CueTools didnot use it. The album was converted with existing offset. Could anyone explain?


I guess (not sure though) that 'fix' is only supposed to fix something when there are no matches with the current offset. But in your example, there is no need to fix anything, as the current offset matches already.


Ah so, then is there a way to modify the script the way of my idea ie. adapting the offes with highest match reagdrless if the current offset has or not some matches?

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1621
The answer is two posts above. (With a Typo in it: you rip=your rip).

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1622
Until now I used CUEtools just to verify against AR (only verify mode). All fine so far.

But recently I tried to split a big flac into tracks, and went into a problem.
I have a source directory with my flac, the cue and the eac log for input.
I chose the cue for input, "encode and verify", "lossless" and so on, and a output directory (different from input dir).

But when I click on go I instantly get an exception, that the access to the directory is denied    (Windows 7 x64).
Directories have been freshly created with the current user, folder permissions are alright (I think), I even tried to run CUEtools as administrator: no success.

Did I miss a configuration step? Anything else?



CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1623
A misbehavior report:
With a damaged but CTDB fixable rip that have an extra data file but don't have a log (so no length info):

If CT automatically finds the data track length & you try to repair it, after the reparing the rip is AR not found as it seems the data track length is not automatically applied after the reparing.

Exemple:
Damaged:
Code: [Select]
[CUETools log; Date: 28/10/11 12:33:19; Version: 2.1.2a]
CD-Extra data track length 32:53:50.
[CTDB TOCID: NSFKOWYhdRg5JvTHPsSbYUIVH6I-] found.
        [ CTDBID ] Status
        [205e81aa] (1/1) Differs in 12 samples @04:35:57
[AccurateRip ID: 000f1d51-007811a9-7f11af0a] found.
Track   [ CRC    ] Status
01     [251c8174] (2/2) Accurately ripped
02     [de2afa36] (0/2) No match but offset
03     [aaddb5c4] (2/2) Accurately ripped
04     [80eefc16] (2/2) Accurately ripped
05     [14ea8187] (2/2) Accurately ripped
06     [a78830c5] (2/2) Accurately ripped
07     [b96f1704] (2/2) Accurately ripped
08     [538cf213] (2/2) Accurately ripped
09     [987b6e4b] (2/2) Accurately ripped

Track Peak [ CRC32  ] [W/O NULL]
--   98,7 [31E95D45] [439F38B1]          
01   59,7 [E28F0A65] [35FF4800]          
02   98,7 [11C967E5] [49FA5025]          
03   98,7 [56420A86] [0841F570]          
04   98,7 [396F04C5] [BA7238A5]          
05   98,7 [250AC844] [3EAFDFD3]          
06   98,7 [405E456A] [D89DABCC]          
07   98,7 [828BB200] [4C6E261F]          
08   98,7 [9976F05A] [F8FA4991]          
09   98,7 [4CECDF52] [36B60187]


After reparing:
Code: [Select]
[CUETools log; Date: 28/10/11 15:42:10; Version: 2.1.2a]
CD-Extra data track length 32:53:50.
CUETools DB: corrected 12 errors.
[AccurateRip ID: 000f1d51-007811a9-7f11af0a] disk not present in database.

Track Peak [ CRC32  ] [W/O NULL]
--   98,7 [437B0988] [82B5FA4C]          
01   59,7 [E28F0A65] [35FF4800]          
02   98,7 [342F4426] [D9F55817]          
03   98,7 [56420A86] [0841F570]          
04   98,7 [396F04C5] [BA7238A5]          
05   98,7 [250AC844] [3EAFDFD3]          
06   98,7 [405E456A] [D89DABCC]          
07   98,7 [828BB200] [4C6E261F]          
08   98,7 [9976F05A] [F8FA4991]          
09   98,7 [4CECDF52] [36B60187]


Should have been: (Manual re-verification of the same fixed data as above)

Code: [Select]
[CUETools log; Date: 28/10/11 15:43:50; Version: 2.1.2a]
CD-Extra data track length 32:53:50.
[CTDB TOCID: NSFKOWYhdRg5JvTHPsSbYUIVH6I-] found.
        [ CTDBID ] Status
        [205e81aa] (1/1) Accurately ripped
[AccurateRip ID: 000f1d51-007811a9-7f11af0a] found.
Track   [ CRC    ] Status
01     [251c8174] (2/2) Accurately ripped
02     [9c754a56] (2/2) Accurately ripped
03     [aaddb5c4] (2/2) Accurately ripped
04     [80eefc16] (2/2) Accurately ripped
05     [14ea8187] (2/2) Accurately ripped
06     [a78830c5] (2/2) Accurately ripped
07     [b96f1704] (2/2) Accurately ripped
08     [538cf213] (2/2) Accurately ripped
09     [987b6e4b] (2/2) Accurately ripped

Track Peak [ CRC32  ] [W/O NULL]
--   98,7 [437B0988] [82B5FA4C]          
01   59,7 [E28F0A65] [35FF4800]          
02   98,7 [342F4426] [D9F55817]          
03   98,7 [56420A86] [0841F570]          
04   98,7 [396F04C5] [BA7238A5]          
05   98,7 [250AC844] [3EAFDFD3]          
06   98,7 [405E456A] [D89DABCC]          
07   98,7 [828BB200] [4C6E261F]          
08   98,7 [9976F05A] [F8FA4991]          
09   98,7 [4CECDF52] [36B60187]


Not that it matters much if you are aware of it, but it is missleading as I could have thought that my rip wasn't fixed if I would not have manually re-verified.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1624
I chose the cue for input, "encode and verify", "lossless" and so on, and a output directory (different from input dir).

Sounds like an older version.

But when I click on go I instantly get an exception, that the access to the directory is denied    (Windows 7 x64).

I'm still using XP but I know Windows 7 has very strict access rights inside the "Program Files" directories. If you are running CUETools from there, you might try running from something like C:\CUETools instead.
korth