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 1907940 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 #2400 –
The last time I checked some time ago already, Cuetools wasn't working correctly with mono nor with wine + mono for windows which afaik it is the default wine configuration to run .Net applications. The workaround I found was to install the required dependencies for windows through the command winetricks (.Net 2.0, .Net 2.0 SP2 and the Visual C++ 2008 libraries) under a 32-bit wineprefix or the installers wouldn't work:

winetricks dotnet20sp2
winetricks vcrun2008

(the first command installs both, the main package and the service pack)

After doing this, at least here under Arch, everything seems to be working fine with no big issues so far.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #2401 –
Quote from: unfinished.hide on
After doing this, at least here under Arch, everything seems to be working fine with no big issues so far.


I've had some issues with wine (couldn't figure out how to setup 32-bit winprefix) so I did the easier way, using Playonlinux. After installing  dotnet20sp2 and vcrun2008 everything works fine. Thanks.
Btw I'm on Manjaro (arch based distro).

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #2402 –
I'm trying to split a .cue file into separate .flac files but for some reason I keep getting a Exeption: Access to 'D:\User\Desktop' is denied. I have full administrative rights. I tried another path but the same thing happens. Everything was working fine last night. The only big change that I did since then was change my system locale but I've changed it back. Thanks for the help!

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #2403 –
CUETools v2.1.4

Artist.Album.Year.cue
Artist.Album.Year.flac
Artist.Album.Year.log (with checksum)



When splitting a Disc Rip (ie. All Tracks in a Single FLAC file) with CUETools into individual FLAC files.

CUETools somehow amends the log file in the destination folder (that also contains the newly split individual flac tracks and cue file)

which makes it fail (no checksum found or something to that effect) EAC's CheckLog.exe.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #2404 –
EAC's CheckLog only work with the original flac 'image' and cue sheet. Testing the log with the individual tracks will make the log check fail.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #2405 –
Quote from: NetRanger on
EAC's CheckLog only work with the original flac 'image' and cue sheet. Testing the log with the individual tracks will make the log check fail.



What?

EAC's CheckLog just checks the log to verify that it has not been altered/edited/modified in any way.

It doesn't check the log against any flac file (disc or individual tracks)...

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #2406 –
Quote from: nospamorban on
CUETools somehow amends the log file in the destination folder (that also contains the newly split individual flac tracks and cue file)

which makes it fail (no checksum found or something to that effect) EAC's CheckLog.exe.

CUETools 2.1.4 rewrites the extraction logfile ANSI. Later versions of EAC write the extraction logfile Unicode.
CUETools 2.1.5 does this also.
korth

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #2407 –
Quote from: korth on
CUETools 2.1.4 rewrites the extraction logfile ANSI. Later versions of EAC write the extraction logfile Unicode.
CUETools 2.1.5 does this also.



Oh okay. Thanks.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #2409 –
i'm sure i've had the tak decoder working before but i can't get it working at all now.  all i'm looking to do is verify files. if i try and modify the path to takc.exe in the options, it doesn't make any difference. also, on a restart, this change is lost and it resets to default. i've also tried putting takc.exe in the cuetools folder and that didn't work either. this is the error:

Quote
Object reference not set to an instance of an object..


using 2.1.5.

edit: 2.1.4 works fine. i can set the path to takc.exe in my encoders folder, job done. i guess i must have used that previously.. 

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #2410 –
Quote from: marc2003 on
i'm sure i've had the tak decoder working before but i can't get it working at all now.  all i'm looking to do is verify files. if i try and modify the path to takc.exe in the options, it doesn't make any difference. also, on a restart, this change is lost and it resets to default. i've also tried putting takc.exe in the cuetools folder and that didn't work either. this is the error:

Quote
Object reference not set to an instance of an object..


using 2.1.5.

edit: 2.1.4 works fine. i can set the path to takc.exe in my encoders folder, job done. i guess i must have used that previously.. 


Hi marc2003,

It is funny how I just wanted to post the same issue. Have you been able to solve this and use Takc.exe with CUETools 2.1.5?

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #2411 –
nope, i'm just running 2.1.4 now.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #2412 –
Bummer. 2.1.5 has so many improvements over 2.1.4.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #2413 –
@d125q....could you elaborate please.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #2415 –
HI,
help needed, aplaing offset with CT CRC first track missmatch. How to correct it (may be digital silence somewhere is missing)

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #2416 –
Quote
CRC first track missmatch.

This is a bit vague. Which CRC?
Example: If the FLAC decoder throws a "Frame CRC Mismatch" error when track1.flac is input into CUETools then that FLAC file is likely corrupt.
korth

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #2417 –
O.K.,
Some CD Rips (ripped according EAC for 100% copy) ONLY SOME rips do not shift (when applying offset correction) properly:
1.I take (Flac/APE) CDimage+Cue+Log
2.Using CUEtools - to verify CRC32 whole CDimage and tracks if they are accurately ripped (they are !)
3.My CD drive offset is +6
4.burning software is NERO
5.With CUEtools I apply offset +6 to this wave CDimage
6.Using CUEtools - to verify CRC32 whole CDimage and tracks if they are shifted correctly BUT...,
first and last tracks CRC32 mismatch to CDimage before applying offset +6
THAT is a PROBLEM

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #2418 –
When you apply offset, samples are lost at one end of the wav image and null samples padded to the other. The CRC32 (null samples included in calculation) of the wav image (and each track) will change.
korth

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #2419 –
Quote from: oleg1000corsar on
O.K.,
Some CD Rips (ripped according EAC for 100% copy) ONLY SOME rips do not shift (when applying offset correction) properly:
1.I take (Flac/APE) CDimage+Cue+Log
2.Using CUEtools - to verify CRC32 whole CDimage and tracks if they are accurately ripped (they are !)
3.My CD drive offset is +6
4.burning software is NERO
5.With CUEtools I apply offset +6 to this wave CDimage
6.Using CUEtools - to verify CRC32 whole CDimage and tracks if they are shifted correctly BUT...,
first and last tracks CRC32 mismatch to CDimage before applying offset +6
THAT is a PROBLEM

Try looking at the W/O NULL entry.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #2420 –
I have a rip of one of my CDs made originally with Read Offset: 0. The correct read offset for the drive used is 48. Can I fix that using CUETools by selecting the "Encode" action and entering 48 as Offset in "Extra" section? Or is that not the method to do that? Thanks.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #2421 –
Quote from: tahaa7 on
I have a rip of one of my CDs made originally with Read Offset: 0. The correct read offset for the drive used is 48. Can I fix that using CUETools by selecting the "Encode" action and entering 48 as Offset in "Extra" section? Or is that not the method to do that? Thanks.

That is exactly the method of doing it. Just be sure that the offset should be 48 before doing it (look at AccurateRip logs, offset databases, and so on).

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #2422 –
Do be aware that 48 samples is only about 1/1000th of a second and you don't gain anything by re-encoding the original rip with that offset.  It's not more accurate or better.  Since CueTools can verify the rip as is, you might consider just leaving it alone.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #2423 –
the problem is i can't extract some tracks and not all tracks from cd!

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #2424 –
Quote from: d125q on
It is funny how I just wanted to post the same issue. Have you been able to solve this and use Takc.exe with CUETools 2.1.5?


I'm using takc.exe v2.3.0 with both the latest beta and CT v2.1.4, no problem. Not sure what I'm doing differently.