Can't Rip a Complete CD Without Hanging

[galtfrog]

Re: Can't Rip a Complete CD Without Hanging

Thanks for your help Spoon & Jailhouse. Not sure what I'll do. I will probably move my library to a local disk for other reasons. Other than that, I guess I'll just have to re-rip the failures. Hope ya'll have a great 2018!!!!

[Spoon]

Re: Can't Rip a Complete CD Without Hanging

Because it encodes without pipes. m4a and mp3 use STDIO pipes.

[galtfrog]

Re: Can't Rip a Complete CD Without Hanging

I ran four or five tests. The last two were with mp3 encoding and targeting my usual drives. The very last run hung. It would take more tests to confirm. Why would it be WAV make a difference? Encoding, but no compression?

[Spoon]

Re: Can't Rip a Complete CD Without Hanging

Try ripping to Wave

[galtfrog]

Re: Can't Rip a Complete CD Without Hanging

If you mean change the encoder to single thread, no. I do not use any DSP effects. In the CD ROM settings, I see that Sample Offset is set to +6. I don't recall changing it. I've assumed it was set by the software. Could this have an impact. Regarding the encoder setting, I do rip to two encoders (mp3 & Apple Lossless) with path & filename settings using Dynamic Naming.

[Spoon]

Re: Can't Rip a Complete CD Without Hanging

If you change the encoder, and not use any dsp effects, does that help?

[galtfrog]

Re: Can't Rip a Complete CD Without Hanging

Usually, the encoding moves along while the next track starts ripping. There can be multiple tracks encoding using the four CPUs. Typically for me, one to three tracks hang during encoding on any given CD. (Sometimes, it completes without a problem.) Whether a track hangs or not, the next track usually starts right away after a track completes the ripping cycle.

[Jailhouse]

Re: Can't Rip a Complete CD Without Hanging

My experience:

1. A track is ripped.

2a.

• For that track, the Rip Status column displays, e.g., CPU2 Encoding x%, where x is a rapidly rising number.
• At the same time, the next track is being ripped.

-OR-

2b.

• The Rip Status column displays CPU2 Encoding 0%.
• The CD drive spins down.
• Within a few seconds, encoding begins.
• After encoding is complete, the drive spins up and ripping begins on the next track.

Return to 1.

-------------

Your experience (I assume our steps 1 and 2a are the same):

2b.

• The Rip Status column displays CPU2 Encoding 0% and doesn't change. Ever.
• Ripping immediately begins on the next track.

Return to 1.

Have I gotten this right?

-------------

So. Encoding occasionally pauses momentarily for me, whereas it occasionally refuses to run at all for you. We're running the same version of CD Ripper on different CPUs and Windows versions.

Very interesting behavior. (Read: I don't have a clue.) I sure hope Spoon and Peter can find the answer.

[galtfrog]

Re: Can't Rip a Complete CD Without Hanging

No. It hangs by my definition. It sits at 0% for minutes until I kill it.

[Jailhouse]

Re: Can't Rip a Complete CD Without Hanging

What I define as hanging is when the encoding percentage stays at 0% for minutes. I have left it for as long as 6 minutes or so several times and even longer a time or two.

Good definition. It seems to me to infer that sometimes encoding doesn't start immediately, but sits at 0% for a few seconds, or maybe tens of seconds, and then runs. Am I correct?

[galtfrog]

Re: Can't Rip a Complete CD Without Hanging

What I define as hanging is when the encoding percentage stays at 0% for minutes. I have left it for as long as 6 minutes or so several times and even longer a time or two.

[Jailhouse]

Re: Can't Rip a Complete CD Without Hanging

Perhaps in the handoff from rip to encode.

I opened Resource Monitor from Task Manager and see activity of some sort on all 8 CPUs (4 cores w/2 threads each); in Task Manager I see Steam, Rapport, ESET and various other background tasks running intermittently. So it's easily possible to have all cores/threads in use when CoreConverter.exe needs to run. But for me it runs fairly soon (perhaps because of the eight threads), while for you it seems that CoreConverter.exe queues up for an available core and is subsequently completely ignored.

Now I'm curious. I'm going rip some disks with Task Manager open.

Does paused encoding always hang until you end the CoreConverter.exe process, or do you have instances where it finally runs?

[galtfrog]

Re: Can't Rip a Complete CD Without Hanging

I ripped one track 5 times in secure mode without a hang. When it does hang it is always after rip at "CPU* Encoding 0%" where * is 1 to 4. Perhaps in the handoff from rip to encode.

I've attached a pdf showing two screenshots. The first shows the processes running just after starting Rip - CDGrab.exe is running for the main application and 3 instances of CoreConverter.exe are running. The second screenshot shows the running processes as the rip progresses - multiple instances of CoreConverter.exe.

The issue seems to be with CoreConverter.exe. Manually ending the Core.Converter.exe process in Windows Task Manager completes the Rip, displays the Information popup and I am able to continue.

[Spoon]

Re: Can't Rip a Complete CD Without Hanging

Try ripping just track 1 over and over. When does it hang? during encoding (after ripping if on secure mode) or during encoding.

[galtfrog]

Re: Can't Rip a Complete CD Without Hanging

When the application hangs on encoding one or more tracks, I cannot do anything in the application. I have to force it closed through task manager or taskbar. I can open a new instance and run it on the remaining tracks. This may take multiple tries. For example, 1st run - 17/20 tracks successfully encode, 2nd run - 2/3 remaining tracks encode, 3rd run - last track encodes.