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: CUERipper / CUETools - Invalid Frame error (Read 3374 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

CUERipper / CUETools - Invalid Frame error

I was ripping a few CD's today with CUERipper 2.2.4 and two discs gave an 'Invalid Frame' error just after completion of the rip. No AccurateRip log is created and no metadate is added to the files (FLAC).

The CUERipper logs are looking fine for both CD's/
When using CUETools 2.2.4 to retro-verify the discs it also gives the 'Invalid Frame' error.

Any clue what can be the case? Any suggestions howto troubleshoot this further?

/edit: upon double checking the integrity of the FLAC files, F2K gives FLAC stream errors when using the verify option. Will delve into this further, strange that the logfiles are looking ok. The files are playable as well...

Re: CUERipper / CUETools - Invalid Frame error

Reply #1
Which encoder?

Verify in CUETools uses the 'cuetools' FLAC decoder by default. Do you get a similar error using the libFLAC decoder? ([Advanced] Settings > 'Formats' tab)
korth

Re: CUERipper / CUETools - Invalid Frame error

Reply #2
Which encoder?

Verify in CUETools uses the 'cuetools' FLAC decoder by default. Do you get a similar error using the libFLAC decoder? ([Advanced] Settings > 'Formats' tab)


I am using the default CUETools FLAC encoder. A second rip of one of the discs gives the same error. EAC rips fine. Will test with CUERipper/libFLAC as well and post the results.

 

Re: CUERipper / CUETools - Invalid Frame error

Reply #3
Note: CUERipper adds the metadata/cover just after completion of ripping the CD.
The CTDB TOCID of each CD (from the EAC log if the CD ripped fine there) might be helpful.
korth

Re: CUERipper / CUETools - Invalid Frame error

Reply #4
Note: CUERipper adds the metadata/cover just after completion of ripping the CD.
The CTDB TOCID of each CD (from the EAC log if the CD ripped fine there) might be helpful.

The CTDB TOCID's of the problematic discs are:
- CTDB TOCID: XoR1QOq09yjWhBaIAGIot0YUEmo-
- CTDB TOCID: n1lAZ0_Bg1s921OB9YWKQCCdHOw-

When using libFLAC both rips stop a few seconds after gap detection with the error
"Exception: Unable to initialize the encoder"


Re: CUERipper / CUETools - Invalid Frame error

Reply #5
Other discs are encoded properly on your system using libFLAC?

Re: CUERipper / CUETools - Invalid Frame error

Reply #6
Other discs are encoded properly on your system using libFLAC?

I have tried one of the other discs (which already ripped ok with the default settings) with libFLAC and it rips fine.

Re: CUERipper / CUETools - Invalid Frame error

Reply #7
Note: CUERipper adds the metadata/cover just after completion of ripping the CD.
The CTDB TOCID of each CD (from the EAC log if the CD ripped fine there) might be helpful.

The CTDB TOCID's of the problematic discs are:
- CTDB TOCID: XoR1QOq09yjWhBaIAGIot0YUEmo-
- CTDB TOCID: n1lAZ0_Bg1s921OB9YWKQCCdHOw-

When using libFLAC both rips stop a few seconds after gap detection with the error
"Exception: Unable to initialize the encoder"


Is there anything else I can do?

Re: CUERipper / CUETools - Invalid Frame error

Reply #8
What happens, if you rip the affected discs using a different CD drive?

Re: CUERipper / CUETools - Invalid Frame error

Reply #9
What happens, if you rip the affected discs using a different CD drive?

I don't have a different drive to rip with, but as mentioned: Exact Audio Copy rips the two affected discs perfectly fine with the same drive, so the issue must be software related.

Re: CUERipper / CUETools - Invalid Frame error

Reply #10
Update: CUERipper 2.2.5 gives the error 'block size too large' directly after ripping one of the problematic discs. Retro verifying with CUETools 2.2.5 still gives the 'invalid frame' error. The files still fail when verifying with F2K.

Re: CUERipper / CUETools - Invalid Frame error

Reply #11
Update: CUERipper 2.2.5 gives the error 'block size too large' directly after ripping one of the problematic discs. Retro verifying with CUETools 2.2.5 still gives the 'invalid frame' error. The files still fail when verifying with F2K.
Did you try both flac encoders again (cuetools and libFLAC)?

Re: CUERipper / CUETools - Invalid Frame error

Reply #12
Quote
Did you try both flac encoders again (cuetools and libFLAC)?

Currently only with 'CUETools', will test again with libFLAC within a few days.


Mod edit: fill missing quote tag

Re: CUERipper / CUETools - Invalid Frame error

Reply #13
Using libFLAC still isn't possible either, see attached screenshot.

When using flac.exe from the latest Exact Audio Copy it still doesn't work 100% in CUERipper, but there is some progress:
Directly after ripping CUERipper gives the error 'Block Size Too Large'. No AccurateRip logfile is created and no metadata is added to the files. It is however possible to retro-verify the files succesfully with CUETools and F2K now verifies all the flac files als 'OK'.  This is an improvement.

I don't have any ideas left, but this really must be a bug in CUERipper.

Re: CUERipper / CUETools - Invalid Frame error

Reply #14
In order to avoid the Exception 'Block Size too large', you can reduce the album art size or avoid embedding the large album art.

CUERipper Options:
Album Art Size: Large -> Small
or
Embed Album Art: True -> False

Remark:
The size of the default, large album art in case of CTDB TOCID: n1lAZ0_Bg1s921OB9YWKQCCdHOw- is 25.9 MB, which is too large for embedding.


Re: CUERipper / CUETools - Invalid Frame error

Reply #15
I didn't have CTDB TOCID: XoR1QOq09yjWhBaIAGIot0YUEmo- but did have a different version 
Using http://coverartarchive.org/release/9dd5485e-e715-4bbd-8531-930d3884758e/22801989564.jpg
the error can be reproduced
X

So CUERipper either needs a built-in size limit (perhaps per format) to automatically reduce over-sized embedded art
or a user option to set a size limit on embedded art (reducing size to that limit)
or both.
korth

Re: CUERipper / CUETools - Invalid Frame error

Reply #16
Follow-up
MaxAlbumArtSize= apparently ignored by CUERipper (checked back to 2.1.9)
CUERipper 2.1.6 used http://coverartarchive.org/release/9dd5485e-e715-4bbd-8531-930d3884758e/22801989564-250.jpg instead when http://coverartarchive.org/release/9dd5485e-e715-4bbd-8531-930d3884758e/22801989564.jpg was selected.
Selecting same linked large album art not an issue in CUETools 2.2.5. Resized per option.
korth

Re: CUERipper / CUETools - Invalid Frame error

Reply #17
CUERipper 2.1.6 used http://coverartarchive.org/release/9dd5485e-e715-4bbd-8531-930d3884758e/22801989564-250.jpg instead when http://coverartarchive.org/release/9dd5485e-e715-4bbd-8531-930d3884758e/22801989564.jpg was selected.
Which CUERipper setting was used in this case? It looks like "Album art search: Small", which is the default in CUERipper 2.1.6.

In CUERipper 2.1.6 it is possible to embed album art, which is larger than 16 MB. However, this leads to invalid flac files, which can be tested afterwards:
Code: [Select]
flac -t "01 - Electricity.flac"
flac 1.4.3
01 - Electricity.flac: *** Got error code 0:FLAC__STREAM_DECODER_ERROR_STATUS_LOST_SYNC
*** Got error code 1:FLAC__STREAM_DECODER_ERROR_STATUS_BAD_HEADER
*** Got error code 0:FLAC__STREAM_DECODER_ERROR_STATUS_LOST_SYNC
...

This has been fixed in newer versions of CUERipper:
Prevent taglib from corrupting flac files when embedded album art exceeds 16Mb
https://github.com/gchudov/taglib-sharp/commit/8590ad068dade84e9bc15656a451221b852f11d7

In case of too large album art, the exception "Block size too large" is shown since then.


Re: CUERipper / CUETools - Invalid Frame error

Reply #18
Quote
Which CUERipper setting was used in this case? It looks like "Album art search: Small", which is the default in CUERipper 2.1.6.
nope


Quote
This has been fixed in newer versions of CUERipper:
Prevent taglib from corrupting flac files when embedded album art exceeds 16Mb
https://github.com/gchudov/taglib-sharp/commit/8590ad068dade84e9bc15656a451221b852f11d7

In case of too large album art, the exception "Block size too large" is shown since then.

If 'auto resize' or 'skip embedding the art' isn't an option, CUERipper should throw an error when the art is selected. That's not really good fix if you have to wait until the rip finishes to receive the error. That's a waste of someone's time and forces them to re-rip.
korth

Re: CUERipper / CUETools - Invalid Frame error

Reply #19
I wasn't aware of the size limitation, never having run into it, but it prompts the following question as I do occasionally store alternative artworks along with booklet images in the metadata;
as the flac format allows multiple artworks to be stored in the metadata (19 different types according to mp3tag; front cover, back cover... lyricist... recording location... etc) is each image stored in it's own frame or block, thereby getting the full 16MB image size allowance, or are they all stored in the same frame or block and the total of the stored image sizes is limited to 16MB ?

Re: CUERipper / CUETools - Invalid Frame error

Reply #20
CUERipper only embeds the Front Cover
CUETools only embeds the Front Cover when adding new cover art during encode.
Perhaps you should look in the FLAC board
https://hydrogenaud.io/index.php/topic,60122.0.html
korth

Re: CUERipper / CUETools - Invalid Frame error

Reply #21
Quote
If 'auto resize' or 'skip embedding the art' isn't an option, CUERipper should throw an error when the art is selected. That's not really good fix if you have to wait until the rip finishes to receive the error. That's a waste of someone's time and forces them to re-rip.

Agreed. And it is also confusing, because the error doesn't give you a clue what might be wrong. Afaik the error is (at least) present in CUERipper 2.1.5 and 2.1.6.

Re: CUERipper / CUETools - Invalid Frame error

Reply #22
Thanks korth, that fully answers my question.