Daryn Posted April 11, 2019 Share Posted April 11, 2019 I was just thinking about this as I ran into a few CD's the ripped successfully but had errors. If you have the information on where those errors occurred, would it be possible to surface that after the rip gets done as timestamps in the affected tracks? Sometimes, even if a rip doesn't validate as accurate, the errors aren't audible, so it'd be nice to be able to know where they happened and hear if they matter or not. Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted April 16, 2019 Share Posted April 16, 2019 On 4/11/2019 at 10:40 AM, Daryn said: I was just thinking about this as I ran into a few CD's the ripped successfully but had errors. If you have the information on where those errors occurred, would it be possible to surface that after the rip gets done as timestamps in the affected tracks? Sometimes, even if a rip doesn't validate as accurate, the errors aren't audible, so it'd be nice to be able to know where they happened and hear if they matter or not. That is a great idea, though it's more of a suggestion for CUETools/CUERipper than MBA. It's also possible that CUETools has something like that built-in already, but I'm not aware of it. Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted April 16, 2019 Share Posted April 16, 2019 I'm guessing maybe the log file would report where the errors occur? I think it does. Quote Link to comment Share on other sites More sharing options...
Daryn Posted April 16, 2019 Author Share Posted April 16, 2019 Currently, the log just shows that there were errors, but not where in the track they were. It's possible that CueTools may have a more verbose logging level, though. Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted April 17, 2019 Share Posted April 17, 2019 20 hours ago, Daryn said: Currently, the log just shows that there were errors, but not where in the track they were. It's possible that CueTools may have a more verbose logging level, though. Yeah, it might. I'll take a look. Quote Link to comment Share on other sites More sharing options...
mauimate Posted July 17, 2019 Share Posted July 17, 2019 I have ripped 4 cds after downloading the newest version and all have playback errors, although the rip indicated the rip was successful. Any suggestions for improvement? Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted July 17, 2019 Share Posted July 17, 2019 18 hours ago, mauimate said: I have ripped 4 cds after downloading the newest version and all have playback errors, although the rip indicated the rip was successful. Any suggestions for improvement? I would need more details here. What is the log of the rip? If the rip is saying that it's accurate, then it's guaranteed to not have any errors as it's comparing with other rips from the web. Quote Link to comment Share on other sites More sharing options...
mauimate Posted July 17, 2019 Share Posted July 17, 2019 I changed the playback latency to 300 without improvement. Then increased latency to 400 and stuttering, skips disappeared. Is there an optimal setting for latency? Thanks Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted July 18, 2019 Share Posted July 18, 2019 4 hours ago, mauimate said: I changed the playback latency to 300 without improvement. Then increased latency to 400 and stuttering, skips disappeared. Is there an optimal setting for latency? Thanks I see; that makes sense. I would set the latency to whatever works on your system without stuttering. The only disadvantage of longer latency is that it takes a tiny bit longer to start or stop tracks, so higher latencies are not much of an issue. You can also try the other various playback engines. I prefer DirectSound though, personally. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.