EAC Contacting CTDB at the end of ripping then crashes

[sirt]

Hi,

I configured EAC to proceed accurate rips (in FLAC). It is more or loss configured according to what is explained there : link (https://beathau5com.wordpress.com/2015/07/28/exact-audio-copy-eac-how-to-install-and-setup-eac-to-make-flawless-rips-on-windows/).

Then (with Exact Audio Copy 1.0.6 or higher, whatever), I insert a brand new CD and rip it to flac. Everything goes well but at the very end, EAC tries to connect CTDB (see picture below). But it seems to fail and then EAC crashes and exit. The result is I don't get .log file at the end.

I noticed this doesn't happen if I don't rip whole cd (let's say I select track 1, 2, 3 and 17 and perform ripping. Then it apparently finish normally with .log file).

From what I read, EAC fails to check whether my CD is a *true* copy compared to information in database. I think it has to print some checksum in the .log to validate. Then what can I do ? Can I prevent EAC from doing check ? Can I help it do the right check and finish writting the log ?

http://img15.hostingpics.net/pics/637606eac.png

[Ghitulescu]

Is this not so important, then drop the accurate suipport..

[sirt]

It is what I did by disabling CUETools DB Plugin in EAC Options > Audio Plugin but I want to do is to let it active and prevent EAC from crashing. Is it possible ?

[Ghitulescu]

I do not know and care. The reason of using EAC is because it provides (probably always) reliable results, and with the right hardware and settings 100% accuracy. I do not need an extra confirmation.

[sirt]

Well, but it seems stupid to me that this program crashes and I don't get the log. So it is somehow 'blocking'. Disabling that 'Contacting CTDB' phasis at the end is not the solution to solve that issue. So I would like to know whether I can make that phasis work correctly.

[hello_hello]

I don't know the answer as I use foobar2000 for ripping, but if you can't solve the problem you might want to look at CUETools/CUERipper as an alternative.
http://cue.tools/wiki/CUERipper

[sirt]

Well I want to use EAC but thanks for your suggestion.

[Barough]

Have u tested with uninstalling EAC and remove any leftovers then reboot and install again. I had a similar issue sometime ago and could never figure out a solution. So i uninstalled etc. and then everything was working fine again.

Sent from my Samsung Galaxy S7 edge via Tapatalk

[sirt]

Well actually I am on a brand new computer. I installed EAC latest version last sunday and had this issue. Then I uninstalled and reisntalled another version v1.0 beta 6 and still had the issue. Perhaps I could try what you did : which version did you install ? Moreover, could you tell me exactly where are the 'leftovers' exactly to uninstall ?

[Midzuki]

Well actually I am on a brand new computer.

Does that mean Windows 10?

Then perhaps you should run it under a 'Windows 7 compatible mode' :confused:

[sirt]

Yes a Windows 10. Then how can run such a 'Windows 7 compatible mode' ?

[Barough]

@ sirt
With leftovers i mean installation folder, ProgramData folder and the registry.

Think i had the issue with v1.1 but im not 100% sure. Was a while ago. Running v1.3 now without any issues on Win 7, 8.1 and 10.

Sent from my Samsung Galaxy S7 edge via Tapatalk

[sirt]

I tried with another CD and this time it worked, I can see this at the end of the rip (see below). But I manually enter all information regarding that CD, then I don't know...

All tracks accurately ripped

No errors occurred

End of status report

---- CUETools DB Plugin V2.1.6

[CTDB TOCID: acQSUN1gVpk9W37idHgiKKPal8g-] found
Submit result: acQSUN1gVpk9W37idHgiKKPal8g- has been confirmed
Track | CTDB Status
1 | (420/422) Accurately ripped
2 | (420/422) Accurately ripped
3 | (419/422) Accurately ripped
4 | (420/422) Accurately ripped
5 | (419/422) Accurately ripped
6 | (420/422) Accurately ripped
7 | (417/422) Accurately ripped
8 | (417/422) Accurately ripped
9 | (416/422) Accurately ripped
10 | (417/422) Accurately ripped
11 | (415/422) Accurately ripped
12 | (418/422) Accurately ripped
13 | (417/422) Accurately ripped
14 | (412/422) Accurately ripped
15 | (416/422) Accurately ripped
16 | (414/422) Accurately ripped
17 | (413/422) Accurately ripped
18 | (412/422) Accurately ripped


==== Log checksum 161CA3CFF31A6945C3078B484ABFAE0893320DA766AA2F3953BFA5AB58796543 ====

[Saintly]

Yes, I am reviving an old topic (thread), sorry. But it is certainly relevant.

I am using Windows 8.1, and the latest version of EAC.

I have ripped many CDs with EAC, but this same issue has recently happened to me twice now.
The result is no Log file in my album folder, so no idea whether there was any issue during ripping.
The 'Connecting to CTDB' window refuses to close, requiring killing of EAC via Task Manager or logging off/rebooting/shutdown.

Re-ripping the CD again I don't get the issue. But of course that is a waste of time and abuse of my optical drive and hard drive for no good reason that I can tell. And particularly annoying as I am in the midst of ripping a lot of my CDs to WAV for eventual conversion to FLAC and MP3 ... hundreds still to go.

Be nice if that 'Connecting to CTDB' window could be made to close, or if we had an option to skip the connection attempt.

Failing that, EAC writing to a temporary log file before we get to that connecting issue would be useful, rather than EAC waiting until we click OK to create the Log file. Even if some of the accurip results are missing from that temporary log file, I imagine it is better than nothing, as it probably contains whether there were any read or sync errors.

Another aspect of my situation, is that I have come back to my PC and it has gone into hibernation. But it does that regularly when I am ripping CDs. Still it might be a factor.

[Saintly]

Okay, I may have found a solution.

It would appear that the last (latest) version of EAC has an outdated CTDB EAC Plugin.

More recent versions can be found here - http://cue.tools/wiki/CTDB_EAC_Plugin

I actually have latest CUETools installed, so just copied the three relevant CTDB DLL files across from the \Interop\EAC\ folder, to the main EAC folder, overwriting the two older files there. No idea if the third DLL is required, but included it for good measure. Now we wait and see. If I don't reply again here in the next few weeks, presume the issue is solved.

I did re-rip my latest CTDB issue CD, and I saw the connection happening at the end after clicking OK, with a resulting new looking dialog, and no issue.