[flac-dev] metaflac crashes adding cuesheet

[James]

Erik,

The command used by abcde is

    metaflac --no-utf8-convert  
--import-cuesheet-from=/home/me/Audio/abcde.50107806/cue-50107806.txt   
--import-tags-from=-  /home/me/Audio/abcde.50107806/track1.flac

but I get the same result re-trying without the --no-utf8-convert
and -no-utf8-convert.



Here's the cuesheet:

  PERFORMER "William Shakespeare"
  TITLE "A Midsummer Night's Dream (Disc 1)"
  FILE "A_Midsummer_Nights_Dream_(Disc_1).flac" WAVE
    TRACK 01 AUDIO
      TITLE "Act I Scene i"
      INDEX 01 00:00:00
    TRACK 02 AUDIO
      TITLE "Act I Scene ii"
      INDEX 01 14:53:05
    TRACK 03 AUDIO
      TITLE "Act II Scene i"
      INDEX 01 21:00:22
    TRACK 04 AUDIO
      TITLE "Act II Scene ii"
      INDEX 01 38:13:57
    TRACK 05 AUDIO
      TITLE "Act III Scene i"
      INDEX 01 50:34:28
    TRACK 06 AUDIO
      TITLE "Act III Scene ii (to line 121)"
      INDEX 01 63:22:63

The track1.flac file is about 390 Mbytes.

James



On Mon, 23 Jan 2017 00:20:07 -0800, Erik de Castro Lopo  
<mle+la at mega-nerd.com> wrote:

> James wrote:
>
>> (Apologies if I'm in the wrong place for this...)
>>
>> I'm trying to use the abcde program to archive CDs to flac files.
>> (Each CD to 1 file, and ultimately multi-disk performances to 1
>> file.)  It extracts the audio to a .flac file and creates a cue
>> sheet with track names & locations.  However, when it tries to
>> run metaflac with the --import-cuesheet-from option, it core
>> dumps.
>>
>> I'm using the latest version (1.3.2), which I downloaded & compiled
>> myself. I've tried to run gdb on the core file, but just get a message
>> about using zypper to download separate debug info, but when I
>> try to run the specified command, it says the info doesn't exits.
>> I'm running OpenSUSE 42.2.
>>
>> I have compiled everything with the --enable-debug flag, but I
>> can't figure out where to run metaflac from to pick up the source.
>>
>> Any help would be appreciated.  If there isn't something obvious
>> that I'm doing wrong, I can dig into debugging the code, but it'd
>> be nice to have some idea of where to start.
>
> Please provide the command that causes this. It would also be useful
> if you could make the cue sheet available.
>
>
> Erik