Send cue sheet error

---

Кто онлайн

Просматривают тему:
0 Пользователей: 0 Пользователей и 1 Гость

Cue sheet error only single file cue sheets are supported

Уж не знаю почему, но на трекере постоянно встречаю битые CUE. Не жрет их ни фубар, ни медиапортал.
Причина — не в том порядке теги TRACK и FILE.

Надоело фиксить вручную, написал прогу на перле — CUE Fixer.

Пользоваться так: perl cue_fix.pl «MTV Music History.cue»

файл будет исправлен, оригинал будет бакапнут.

Для запуска необходимо установить перл. Под виндой пользую Strawberry Perl

6) Открываю альбом через CUE и вижу пустой плейлист. Что делать?

Такая проблема часто возникает при работе через CUE. Это связано с тем, что CUE файл ссылается не на тот исходный звуковой файл. Скорее всего CUE ссылается на файл с раширением WAV, а у нас, например, APE. Это связано с тем, что изначально (при создании образа) CUE создается именно для WAV файла, который потом конвертируется в lossless и многие просто не утруждают себя переправить CUE.

Разберемся, как нам это исправить:

1) Откроем CUE в любом текстовом редакторе. Например, в обычном Блокноте (Notepad)
2) Мы увидим сам код CUE файла, который нам нужно немного подправить.

PERFORMER «Rise Against»
TITLE «Appeal To Reason»
FILE «RA-ATR.wav» WAVE
TRACK 01 AUDIO
TITLE «Collapse (Post-Amerika)»
PERFORMER «Rise Against»
INDEX 01 03:21:00
TRACK 02 AUDIO
TITLE » Long Forgotten Sons »
PERFORMER «Rise Against»
INDEX 01 04:01:00

3) Найдем строку, начинающуюся со слова FILE. Именно в ней содержится ссылка на исходный звуковой файл.

FILE «RA-ATR.wav» WAVE

Мы видим, что файл имеет разширение wav, а мой исходный файл, например, в APE. Смотрим в каком формате наш исходный файл и меняем расширение на нужное нам (ape, flac, wv). Получаем строку вида:

Источник

Ошибки,выдаваемые ЕАС при открытии CUE файла.Помогите!

Ошибки,выдаваемые ЕАС при открытии CUE файла.Помогите!

Откройте cue в блокноте (или другом текстовом редакторе).
Проверьте правильно ли указано расширение в указанном файле и исправьте при необходимости. В вашем случаи -flac.
Пример «правильного»:
———————————————

———————————————
В подавляющем большинстве рипающие программы «автоматом» выставляют *wv

Ссылку на образ..будьте добры.

REM GENRE «Rock»
REM DATE 1983
REM DISCID 7C09B90A
REM COMMENT «ExactAudioCopy v1.0b3»
PERFORMER «Rod Stewart»
TITLE «Body Wishes»
FILE «Rod Stewart — Body Wishes.flac» WAVE
TRACK 01 AUDIO
TITLE «Dancin’ Alone»
PERFORMER «Rod Stewart»
FLAGS PRE
INDEX 01 00:00:00
TRACK 02 AUDIO
TITLE «Baby Jane»
PERFORMER «Rod Stewart»
FLAGS PRE
INDEX 00 04:01:68
INDEX 01 04:02:13
TRACK 03 AUDIO
TITLE «Move Me»
PERFORMER «Rod Stewart»
FLAGS PRE
INDEX 01 08:45:45
TRACK 04 AUDIO
TITLE «Body Wishes»
PERFORMER «Rod Stewart»
FLAGS PRE
INDEX 01 12:21:50
TRACK 05 AUDIO
TITLE «Sweet Surrender»
PERFORMER «Rod Stewart»
FLAGS PRE
INDEX 01 17:02:65
TRACK 06 AUDIO
TITLE «What Am I Gonna Do (I’m So In Love With You)»
PERFORMER «Rod Stewart»
FLAGS PRE
INDEX 01 21:03:45
TRACK 07 AUDIO
TITLE «Ghetto Blaster»
PERFORMER «Rod Stewart»
FLAGS PRE
INDEX 00 25:22:65
INDEX 01 25:24:05
TRACK 08 AUDIO
TITLE «Ready Now»
PERFORMER «Rod Stewart»
FLAGS PRE
INDEX 00 29:32:35
INDEX 01 29:32:70
TRACK 09 AUDIO
TITLE «Strangers Again»
PERFORMER «Rod Stewart»
FLAGS PRE
INDEX 00 33:08:35
INDEX 01 33:09:63
TRACK 10 AUDIO
TITLE «Satisfied»
PERFORMER «Rod Stewart»
FLAGS PRE
INDEX 01 37:20:03

«Неизвестная команда в строке 1»

Во-первых, можете удалить первую строку -нечего страшного не будет. и проверить..
Ради истины, скачал именно этот диск. У меня не одна программа ошибок не выявила.
Т.е. траблы у Вас на компе..в софте. Пользуйтесь для нарезки дисков EasyCDDAExtractor — рекомендую.

Т.е. траблы у Вас на компе..в софте. Пользуйтесь для нарезки дисков EasyCDDAExtractor — рекомендую.

Т.е. траблы у Вас на компе..в софте. Пользуйтесь для нарезки дисков EasyCDDAExtractor — рекомендую.

Ссылку на образ..будьте добры.

REM GENRE «Rock»
REM DATE 1983
REM DISCID 7C09B90A
REM COMMENT «ExactAudioCopy v1.0b3»
PERFORMER «Rod Stewart»
TITLE «Body Wishes»
FILE «Rod Stewart — Body Wishes.flac» WAVE
TRACK 01 AUDIO
TITLE «Dancin’ Alone»
PERFORMER «Rod Stewart»
FLAGS PRE
INDEX 01 00:00:00
TRACK 02 AUDIO
TITLE «Baby Jane»
PERFORMER «Rod Stewart»
FLAGS PRE
INDEX 00 04:01:68
INDEX 01 04:02:13
TRACK 03 AUDIO
TITLE «Move Me»
PERFORMER «Rod Stewart»
FLAGS PRE
INDEX 01 08:45:45
TRACK 04 AUDIO
TITLE «Body Wishes»
PERFORMER «Rod Stewart»
FLAGS PRE
INDEX 01 12:21:50
TRACK 05 AUDIO
TITLE «Sweet Surrender»
PERFORMER «Rod Stewart»
FLAGS PRE
INDEX 01 17:02:65
TRACK 06 AUDIO
TITLE «What Am I Gonna Do (I’m So In Love With You)»
PERFORMER «Rod Stewart»
FLAGS PRE
INDEX 01 21:03:45
TRACK 07 AUDIO
TITLE «Ghetto Blaster»
PERFORMER «Rod Stewart»
FLAGS PRE
INDEX 00 25:22:65
INDEX 01 25:24:05
TRACK 08 AUDIO
TITLE «Ready Now»
PERFORMER «Rod Stewart»
FLAGS PRE
INDEX 00 29:32:35
INDEX 01 29:32:70
TRACK 09 AUDIO
TITLE «Strangers Again»
PERFORMER «Rod Stewart»
FLAGS PRE
INDEX 00 33:08:35
INDEX 01 33:09:63
TRACK 10 AUDIO
TITLE «Satisfied»
PERFORMER «Rod Stewart»
FLAGS PRE
INDEX 01 37:20:03

«Неизвестная команда в строке 1»

Во-первых, можете удалить первую строку -нечего страшного не будет. и проверить..
Ради истины, скачал именно этот диск. У меня не одна программа ошибок не выявила.
Т.е. траблы у Вас на компе..в софте. Пользуйтесь для нарезки дисков EasyCDDAExtractor — рекомендую.

Источник

Cue sheet error only single file cue sheets are supported

Почему не работают cue файлы?

Описание: У вас проблемы с foobar2000 и вам необходима помощь? Спрашивайте здесь!
Правила раздела: Одна тема — один вопрос или группа связанных вопросов. Обязательно формируйте внятный заголовок, максимально отражающий суть. Подробно описывайте проблему. Не забывайте указать версию плеера, название сборки, по возможности добавить скриншоты проблемы.

serge8 » 26.12.2019, 14:33

Здравствуйте
у меня foobar 1.4.8
как многие любители музыки я скачиваю
flac’и или ape и хочу их слушать в foobar’e.
С ними часто идут cue файлы.
Так вот эти cue файлы праткически НИКОГДА не работают — т.е
в очень редких случаях они все таки срабытывают
Выдаётся ошибка
либо

«Unable to open item for playback (Object not found):
«E:HERNN ELLISHerb Ellis WindflowerHerb Ellis, Remo Palmier — Windflower.cue» / index: 1

Unable to open item for playback (Object not found):
«E:HERNN ELLISHerb Ellis WindflowerHerb Ellis, Remo Palmier — Windflower.cue» / index: 2

либо такая

«Unable to open item for playback (Error parsing cuesheet: invalid index list (line 20)):
«E:IKE QUEBEC2012.Ike Quebec — With A Song In My HeartWith A Song In My Heart ERR.cue»

Суть в том что в 99 из 100 это какая то ошибка и cue файл нерабочий. Честно говоря это ужасно бесит .

ВОПРОС: почему так? Ведь их же делают, чтобы они работали? Это только у меня так или у других тоже? (Может это обычное дело?)
Может быть у меня что то не правильно?

Я не могу понять . если бы ИНОГДА не работали . я бы ещё понял, а то
они как правило никогда не работают .

postED » 26.12.2019, 15:05

Их делает программа-риппер (EAC) для последующей записи на диск, а для проигрывания в плеере они не предназначены. То, что файлы разметки пришлось использовать как плейлист — это как в поговорке про раков на безрыбье.

Для того, чтобы все работало в фубаре надо чтобы:
1. Кодировка cue-файлов была соответствующей (ANSI, UTF-8 BOM и еще несколько других)
2. Имя референсного файла точно совпадало
Если в cue написано FILE «Herb Ellis, Remo Palmier — Windflower.wav» WAVE , то нужно изменить на имя того файла, который в действительности, например так: FILE «Herb Ellis, Remo Palmier — Windflower. ape » WAVE
3. Фубар не понимает noncompliant-cue в потрековых рипах

serge8 » 26.12.2019, 15:58

А, понял, спасибо
А я думал, что они для проигрывания в программах типа фубара.

Я заменил, как вы порекомендовали, буквы WAVE на ape
Собщение об ошибке теперь другое :

«Unable to open item for playback (Unsupported file format):
«E:HERNN ELLISHerb Ellis WindflowerHerb Ellis, Remo Palmier — Windflower ERR копия.txt»

Unsupported format это в принципе возможно (у меня аудио карта поддерживапет да 48 Кгц) . Но если кликнуть непосредственно на файл аре
то фубар его играет без проблем?

George Smith » 26.12.2019, 16:05

serge8 , попробуйте обновить foobar.
Кстати, откуда рипы берете? На рутрекерских рипах лично у меня проблем никогда не было.

Добавлено спустя 6 минут 10 секунд:

serge8: Собщение об ошибке теперь другое :

«Unable to open item for playback (Unsupported file format):
«E:HERNN ELLISHerb Ellis WindflowerHerb Ellis, Remo Palmier — Windflower ERR копия.txt»

serge8 » 26.12.2019, 18:02

Да, в этом ошибка! конечно TXT
Это я сохранил файл в текстовом редакторе.
Всё поправил. в файле с расширением cue и заработалою)

Рипы беру на Рутракере . но может мы разные рипы берём?
Спасибо

Добавлено спустя 8 минут 40 секунд:
А вот этот почему не работает?

«Unable to open item for playback (Error parsing cuesheet: invalid index list (line 24)):
«E:BURRELLJohn Coltrane — Ballads (1962, 2013, Verve-Japan)Ballads.cue»

Вот cue он небольшой :

TITLE «Ballads»
PERFORMER «John Coltrane»
CATALOG 0008813269423
REM GENRE «Jazz»
REM DATE «1962»
REM DISCID 78079E08
REM REPLAYGAIN_ALBUM_GAIN -0.53 dB
REM REPLAYGAIN_ALBUM_PEAK 1.000000
FILE «01 — Say It (Over and Over Again).flac» WAVE
TRACK 01 AUDIO
TITLE «Say It (Over and Over Again)»
ISRC USMC16211166
REM REPLAYGAIN_TRACK_GAIN -0.48 dB
REM REPLAYGAIN_TRACK_PEAK 0.693665
INDEX 01 00:00:00
TRACK 02 AUDIO
TITLE «You Don’t Know What Love Is»
ISRC USMC16211165
REM REPLAYGAIN_TRACK_GAIN -0.07 dB
REM REPLAYGAIN_TRACK_PEAK 0.999969
INDEX 00 04:18:24
FILE «02 — You Don’t Know What Love Is.flac» WAVE
INDEX 01 00:00:00
TRACK 03 AUDIO
TITLE «Too Young to Go Steady»
ISRC USMC16211161
REM REPLAYGAIN_TRACK_GAIN -0.07 dB
REM REPLAYGAIN_TRACK_PEAK 0.762360
INDEX 00 05:14:74
FILE «03 — Too Young to Go Steady.flac» WAVE
INDEX 01 00:00:00
TRACK 04 AUDIO
TITLE «All or Nothing at All»
ISRC USMC16253798
REM REPLAYGAIN_TRACK_GAIN -1.63 dB
REM REPLAYGAIN_TRACK_PEAK 0.965118
INDEX 00 04:23:26
FILE «04 — All or Nothing at All.flac» WAVE
INDEX 01 00:00:00
TRACK 05 AUDIO
TITLE «I Wish I Knew»
ISRC USMC16336381
REM REPLAYGAIN_TRACK_GAIN 0.07 dB
REM REPLAYGAIN_TRACK_PEAK 0.803162
INDEX 00 03:37:31
FILE «05 — I Wish I Knew.flac» WAVE
INDEX 01 00:00:00
TRACK 06 AUDIO
TITLE «What’s New»
ISRC USMC16251960
REM REPLAYGAIN_TRACK_GAIN -0.80 dB
REM REPLAYGAIN_TRACK_PEAK 0.941589
INDEX 00 04:53:71
FILE «06 — What’s New.flac» WAVE
INDEX 01 00:00:00
TRACK 07 AUDIO
TITLE «It’s Easy to Remember»
ISRC USMC16253796
REM REPLAYGAIN_TRACK_GAIN -1.58 dB
REM REPLAYGAIN_TRACK_PEAK 1.000000
INDEX 00 03:46:08
FILE «07 — It’s Easy to Remember.flac» WAVE
INDEX 01 00:00:00
TRACK 08 AUDIO
TITLE «Nancy (With the Laughing Face)»
ISRC USMC16252383
REM REPLAYGAIN_TRACK_GAIN 1.53 dB
REM REPLAYGAIN_TRACK_PEAK 0.594849
INDEX 00 02:47:41
FILE «08 — Nancy (With the Laughing Face).flac» WAVE
INDEX 01 00:00:00

George Smith » 27.12.2019, 07:45

Источник

Adblock
detector

I have the same problem
1) 8.6.1.1985
2) DVD+R
3) Philips DVDR 1660P1

I am using Windows ME with FAT32 and I don’t know if the full size of the DVD is bigger or smaller than 4GB (very close). I made a backup of the DVD as .isz in 2 GB blocks and tried to burn a DVD from it now.
This happened both with the older driver version (1.4) and after I updated the Philips driver (1.6).

Источник

newbie: cannot send cue sheet

Thread Tools

Display

Ok, I’ve been working over a week trying to get this working. It took half that time for VCDEasy to recognize my drive, but now I’m getting:

«cannot send cue sheet»

I get the same error trying to burn the bin directly in FireBurner (CDRWin refuses to recognize I have a recordable drive).

So: I have a 1.4 Athlon machine, a CD-ROM drive on the secondary IDE master and a Pioneer 103 DVD-RW on the slave secondary IDE (I upgraded the firmware to the general 1.68 release).

I installed the 4.60 ASPI layer (research said that the 4.7 sucked big so I took it out and reinstalled 4.6), capture through a Radeon AIW (32M), and have successfully burned data CD’s (the simple-stupid drag drop way).

I just want to get a VCD burned, then I’ll start fine-tuning. Hopefully someone can get me there.

Hopefully i’ll be able to assist you, first, i suggest you get the Region Free firmware for your drive, i’ve seen it in a few places, step 2 would be to make sure you select Generic-Mmc in VCDEasy or TSCV and then try to use your DVDR to burn the media.

Email me for faster replies!

Best Regards,
Sefy Levy,
Certified Computer Technician.

I updated the firmware to the 1.68 region-free as one of the first things last week. I started out on generic-mmc, and ran through the other settings just for the fun of it.

I’ve got v1.0.8, settings for VCD 2.0, burn only, analyse MPEG, and perform compliance options checked. I’m making chapters every 5 minutes, CDRDAO integration is on, and I’ve tried both Bin/Cue and TOC image types.

I alos tried forced execution and upped the buffer to 128, speed set at max.

Let me know if I should change any other settings or fiddle with anything else that might help.

It is a possibility that the cause of all this problem is the Pioneer 103, have you tried using CDRWin, FireBurner, BlindWriter ? or possibly Nero 5.578 ?

Email me for faster replies!

Best Regards,
Sefy Levy,
Certified Computer Technician.

Before I decided to post, I had tried Fireburner and received the same error (cannot send cuesheet). CDRWin, as I mentioned, doesn’t even recognize that I have a recordable drive. It sees both drives in the ‘readable’ table, but nothing in the recordable drives tab in Setup.

Nero I haven’t been able to get a clean download yet to install (either too many users or the server drops to a crawl).

Has anyone had success with a Pioneer 103? One other thing I was wondering is there an issue that the recordable drive is set as secondary IDE slave instead of secondary IDE master? (since my CD-ROM drive is faster, I use that for normal everyday stuff, so I prefer to keep it as master as opposed to the DVD-r/w)

As far as I can tell, the Pioneer 103 is a pretty popular drive, so I’m more inclined to think it’s a configuration somewhere as opposed to the drive itself.

The drive itself is very popular, the question is if people used it to burn CDR’s using these methods, what I am curious about is if you can try re-doing the Cue/Bin files using TSCV for example and if that problem still happens ?

Email me for faster replies!

Best Regards,
Sefy Levy,
Certified Computer Technician.

Did you open the .cue in like notepad to make sure it doesnt have a path in it that isnt there, Sometimes when you make a bin/cue it will map the bin to a folder. Like this:

If thats the case then you need to delete the path and just leave the name of the BIN.

Dont know if this is the kind of probalem but hope it helps.

Yeah, I checked the cue text files and they look fine.. I have to wait until i get home to test out the other solution (using a different program to create the bin/cue).

Do you always have to create a bin/cue to create a VCD? Is there some other method?

You can always use NERO which doesnt need you to make a bin/cue. You could also try vcdimager or vcdimagerGUI.

As was mentioned, you can use any VCD Authoring software to burn your CD however VCDImager as far as I know creates the most standard Video-CD of them all, but here are other programs that can Author a VCD:

Nero Burning-ROM v5.0 and v5.5
NTI CD Maker 2000 Professional v5
EZ CD Creator Deluxe and Platinum
CeQuadRat/Roxio’s WinOnCD v3.8/5.0

I Hope this helps you out!

Email me for faster replies!

Best Regards,
Sefy Levy,
Certified Computer Technician.

Well, I upgraded to VCDEasy 1.0.9, reduced to slowest speed, and I now have a burned VCD after two coasters.

Thanks for all the help, pointers and so forth. Now I have to go solve my audio/video out of synch issues!

Источник

unixforum.org

Форум для пользователей UNIX-подобных систем

• Темы без ответов
• Активные темы
• Поиск
• Статус форума

K3b не пишет на CD-RW (настройка K3b)

Модератор: Bizdelnick

K3b не пишет на CD-RW

Сообщение Wassermann » 26.07.2008 12:17

Re: K3b не пишет на CD-RW

Сообщение blackdevil » 26.07.2008 12:38

Re: K3b не пишет на CD-RW

Сообщение Full Null » 26.07.2008 14:29

Re: K3b не пишет на CD-RW

Сообщение t2a » 26.07.2008 15:11

«как правильно дозаписать CD-R, DVD-R в k3b»

«можно ли его настроить так чтобы можно было стирать болванки CD-RW, DVD-RW?»

Можно так: «Настройка» -> «Настроить K3b. » -> «Дополнительно» и галочку в «Автоматически очищать CD-RW и DVD-RW»,
можно и просто «Сервис» -> «Очистить CD-RW. «.
DVD-RW — не стираются, а форматируются при первой записи на оный.
И кто мешает изучить настройки K3b?

Re: K3b не пишет на CD-RW

Сообщение Wassermann » 29.07.2008 13:40

Re: K3b не пишет на CD-RW

Сообщение blackdevil » 29.07.2008 15:30

Re: K3b не пишет на CD-RW

Сообщение t2a » 29.07.2008 15:42

«я юзал Mandriv’у и там при первом запуске K3b выходило оконце с предупреждением о правах на запись «

Если память не изменяет, то «оконце» — K3bsetup

«Debian’ском K3b при первом пуске выходит сообщение о том, что нужно установить недостающие модули и все»

Надо было переписать названия и установить, к примеру, через Synaptic.

«Вот я и думаю, мож все проблы из-за прав?»

Попробуйте переустановить (через тот же Synatic) k3b
Должны установиться:
k3b
k3bdata
k3bi18n
libk3b

Для интереса можете попробовать запустить K3b из командной строки:
— как пользователь
потом
— из под root
Кое что поймете, как минимум.

Источник

Arch Linux

You are not logged in.

#1 2018-08-13 20:24:53

[Solved] k3b: Sometimes using TAO writing mode solves this issue

Solution:
My CD drive is external and the power supply was bad.

=> So the solution was to select a USB Port (USB 2.0 or USB 3.0, preferably not yellow) with enough power.

I already searched quite a while in the internet, but didn’t find a solution.

I have a Zacfton Slimtype DVD A DS8A5S WC22 Removable CD-ROM

cdrecord -scanbus says:

And cdrecord says:

When trying to burn with: sudo cdrecord -v -sao dev=/dev/sr0 image.iso

So it says: CUE sheet still not accepted. Please try to write in RAW (-raw96r) mode

But -raw96r gives me:

sudo cdrecord -raw96r -v -clone dev=/dev/sr0 image.iso gives me:

since there is no such .toc file.

And k3b also says:

I enabled TAO in Brasero but this didn’t work. So it does not work in Brasero either.

I am member of the group optical.

Could this be a problem with the iso? I can mount it and it looks exaclty like the original CD.

I used the command

with bs=2048 count=163426 to create the iso.

Last edited by Arch Linux Tux (2018-08-14 18:11:18)

#2 2018-08-14 07:10:43

Re: [Solved] k3b: Sometimes using TAO writing mode solves this issue

the problem looks like it is caused by hardware.
The tangible error messages are

The drive was not in the mood to accept the SCSI/MMC CUE sheet, which
is a description of the ranges and sector types of the tracks which shall
be written in this run of cdrecord.

cdrecord could have repeated the attempt to send the CUE sheet but it
is questionable whether this would have helped.

This advise by the program is rather misleading

You need to be an expert or have expert frontend software to use a raw
mode, because you do not only have to provide the payload data but also
some entrails of the CD sectors which the drive normally produces on its
own.

Could this be a problem with the iso?

k3b: Sometimes using TAO writing mode solves this issue.

Did you already try this ?

With TAO, the burn program does not have to send a CUE sheet but rather
starts to burn with unpredicted track size. If it is only about the drive’s
willingness to accept the CUE sheet, then you might get success.

If the drive is not willing to work with this CD-R at all, then you
will probably get an error with the first write command.

If the problem persists, try other media. If all media fail, get another
drive.

Have a nice day

#3 2018-08-14 14:21:04

Re: [Solved] k3b: Sometimes using TAO writing mode solves this issue

I tried it with another CD unfortunately from the same branch. It’s all «Tevion» and CD-R. Hover the CD says «High Quality — Pure Silver». I would not believe these to be bad CDs anyways. They all look totally clean. And the CD drive is very new with good rating and I wouldn’t have expected it to be bad.

sudo cdrecord -tao -v speed=10 dev=/dev/sr0 image.iso:

I also wanted to try Windows 10 for buring, but I can’t manage to get the Virtualbox running for certain reasons.

(Anybody else) any other ideas?

Last edited by Arch Linux Tux (2018-08-14 14:21:38)

#4 2018-08-14 15:15:43

Re: [Solved] k3b: Sometimes using TAO writing mode solves this issue

It’s all «Tevion» and CD-R.

Well, cdrecord reports different manufacturers (obviously Aldi buys them
wherever they can get them for cheap):

My list of media Ids for libburn has several brands for «97:17/06»
EMTEC, Intenso, Moser Bear India (aka MBI), YAKUMO, PLATINUM, Silver Circle.
These are mostly traders, MBI is a real manufacturer.

The error message of the TAO run is quite unexpected. The drive already
refused when cdrecord announced to start a TAO run. The error code
5,02,00 means that the drive did not expect that announcement.
Nevertheless profile «CD-R» was reported as current.
Regrettably cdrecord did not tell the perceived medium state.

So it would be interesting to see the output of

A blank write-ready medium would look like this:

(Ignore the line about «No Media Present or Unknown Capacity». It is
mislead with CD-R but harmless.)

any other ideas?

My program cdrskin is independent of cdrecord. It might be worth a try:

If it works any better, then you would probably have discovered some yet
unknown bug of cdrecord.

Have a nice day

#5 2018-08-14 15:52:59

Re: [Solved] k3b: Sometimes using TAO writing mode solves this issue

Thank you for your efforts
I think this is getting interesting (could be wrong)

sudo cdrecord -v dev=/dev/sr0 -minfo:

cdrskin -tao -v dev=/dev/sr0 image.iso:

MORE RELEVANT: (PLEASE NOTE)
cdrskin -sao -v dev=/dev/sr0 image.iso

After buring: sudo cdrecord -v dev=/dev/sr0 -minfo

It seemed to be burning (that’s what it says), but then it broke up. And I think the CD-R is still blank.

Last edited by Arch Linux Tux (2018-08-14 16:00:14)

#6 2018-08-14 16:27:06

Re: [Solved] k3b: Sometimes using TAO writing mode solves this issue

sudo cdrecord -v dev=/dev/sr0 -minfo:

The drive reports that the medium is blank and ready for writing.

cdrskin -tao -v dev=/dev/sr0 image.iso:

No problem was recorded when sending the announcement for TAO.
The failure happens after more than three minutes with the first WRITE
command that was sent to the drive.
The drive did not report an error message but rather the Linux kernel
became impatient (probably after waiting 200 seconds).

All further errors are protests from the drive which seems not to
remember the first WRITE which has written 16 blocks. Now it complains
that the target address of the subsequent WRITE command is not 0.

cdrskin -sao -v dev=/dev/sr0 image.iso

The drive obviously accepted the SEND CUE SHEET command, so that libburn
sent WRITE commands. With SAO, writing starts at block address -150.
The first complained WRITE command was for block -118. So the first WRITE
seems to have succeeded and the second WRITE seems to have triggered the
timeout.
Then again, libburn and drive are out of sync about the next writable
block address.

After buring: sudo cdrecord -v dev=/dev/sr0 -minfo

The medium is still reported as completely unused. No trace of the failed
attempts are to see.

Linux timeouts might indicate a poor power supply of the drive or a poor
data cable. Either it gets low voltage when it spins up the medium or it
did not get the WRITE commands which then timed out.

I understand from the web that DS8A5S is a IDE/P-ATA attached internal
drive for laptops. (That’s the more solid power supply compared with a
USB box which gets its power from the USB cable.)
Being built into a laptop makes it more difficult to check cabling,
to exchange cables, or to plug them into different sockets of the computer.

The media are quite out of suspicion for now.

Have a nice day

Last edited by scdbackup (2018-08-14 16:27:57)

Источник

Adblock
detector

Brasero fails with the error, «cannot send cue sheet»(see log file below)

Brasero log file:

imager (BraseroLocalImage) set_output
job (BraseroLocalImage) set_task
imager (BraseroLocalImage) get_track
job (BraseroLocalImage) set_task
Session starting:
 flags = 8535
 media type = 0
 speed = 47
 track type = 8
 track format = 2
 output = none
job (BraseroCDRecord) set_rate
recorder (BraseroCDRecord) set_drive
recorder (BraseroCDRecord) set_flags
job (BraseroCDRecord) set_source
job (BraseroCDRecord) set_task
recorder (BraseroCDRecord) record
process (BraseroCDRecord) getting varg
cdrecord (BraseroCDRecord) set_action
process (BraseroCDRecord) got varg:
 /usr/bin/wodim
 -v
 dev=/dev/scd0
 gracetime=0
 speed=47
 driveropts=burnfree
 -dao
 fs=16m
 -data
 -nopad
 /home/sirzepp/Desktop/gparted-livecd-0.3.4-11.iso
process (BraseroCDRecord) launching command
process (BraseroCDRecord) stderr: /usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.scsidev: ‘/dev/scd0’
process (BraseroCDRecord) stderr: devname: ‘/dev/scd0’
process (BraseroCDRecord) stderr: scsibus: -2 target: -2 lun: -2
process (BraseroCDRecord) stderr: Linux sg driver version: 3.5.27
process (BraseroCDRecord) stderr: Wodim version: 1.1.6
process (BraseroCDRecord) stderr: SCSI buffer size: 64512
process (BraseroCDRecord) stderr: Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
process (BraseroCDRecord) stderr: communication breaks or freezes immediately after that.
process (BraseroCDRecord) stdout: TOC Type: 1 = CD-ROM
process (BraseroCDRecord) stdout: Driveropts: ‘burnfree’
process (BraseroCDRecord) stdout: Device type : Removable CD-ROM
process (BraseroCDRecord) stdout: Version : 5
process (BraseroCDRecord) stdout: Response Format: 2
process (BraseroCDRecord) stdout: Capabilities :
process (BraseroCDRecord) stdout: Vendor_info : ‘PIONEER ‘
process (BraseroCDRecord) stdout: Identification : ‘DVD-RW DVR-212D’
process (BraseroCDRecord) stdout: Revision : ‘1.24’
process (BraseroCDRecord) stdout: Device seems to be: Generic mmc2 DVD-R/DVD-RW.
process (BraseroCDRecord) stdout: Current: 0x0009 (CD-R)
process (BraseroCDRecord) stdout: Profile: 0x002B (DVD+R/DL)
process (BraseroCDRecord) stdout: Profile: 0x001B (DVD+R)
process (BraseroCDRecord) stdout: Profile: 0x001A (DVD+RW)
process (BraseroCDRecord) stdout: Profile: 0x0016 (DVD-R/DL layer jump recording)
process (BraseroCDRecord) stdout: Profile: 0x0015 (DVD-R/DL sequential recording)
process (BraseroCDRecord) stdout: Profile: 0x0014 (DVD-RW sequential recording)
process (BraseroCDRecord) stdout: Profile: 0x0013 (DVD-RW restricted overwrite)
process (BraseroCDRecord) stdout: Profile: 0x0011 (DVD-R sequential recording)
process (BraseroCDRecord) stdout: Profile: 0x0010 (DVD-ROM)
process (BraseroCDRecord) stdout: Profile: 0x000A (CD-RW)
process (BraseroCDRecord) stdout: Profile: 0x0009 (CD-R) (current)
process (BraseroCDRecord) stdout: Profile: 0x0008 (CD-ROM)
process (BraseroCDRecord) stdout: Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
process (BraseroCDRecord) stdout: Driver flags : MMC-3 SWABAUDIO BURNFREE
process (BraseroCDRecord) stdout: Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
process (BraseroCDRecord) stdout: Drive buf size : 1267712 = 1238 KB
process (BraseroCDRecord) stdout: FIFO size : 16777216 = 16384 KB
process (BraseroCDRecord) stderr: Speed set to 7056 KB/s
process (BraseroCDRecord) stdout: Track 01: data 52 MB
process (BraseroCDRecord) stdout: Total size: 59 MB (05:55.37) = 26653 sectors
process (BraseroCDRecord) stdout: Lout start: 60 MB (05:57/28) = 26653 sectors
process (BraseroCDRecord) stdout: Current Secsize: 2048
process (BraseroCDRecord) stdout: ATIP info from disk:
process (BraseroCDRecord) stdout: Indicated writing power: 5
process (BraseroCDRecord) stdout: Is not unrestricted
process (BraseroCDRecord) stdout: Is not erasable
process (BraseroCDRecord) stdout: Disk sub type: Medium Type A, high Beta category (A+) (3)
process (BraseroCDRecord) stdout: ATIP start of lead in: -11634 (97:26/66)
process (BraseroCDRecord) stdout: ATIP start of lead out: 359846 (79:59/71)
process (BraseroCDRecord) stdout: Disk type: Short strategy type (Phthalocyanine or similar)
process (BraseroCDRecord) stdout: Manuf. index: 3
process (BraseroCDRecord) stdout: Manufacturer: CMC Magnetics Corporation
process (BraseroCDRecord) stdout: Blocks total: 359846 Blocks current: 359846 Blocks remaining: 333193
process (BraseroCDRecord) stdout: Starting to write CD/DVD at speed 40.0 in real SAO mode for single session.
process (BraseroCDRecord) stdout: Last chance to quit, starting real write in 0 seconds. Operation starts.
process (BraseroCDRecord) stdout: Waiting for reader process to fill input buffer … input buffer ready.
process (BraseroCDRecord) stdout: Performing OPC…
process (BraseroCDRecord) stdout: Sending CUE sheet…
process (BraseroCDRecord) set_action
process (BraseroCDRecord) stderr: /usr/bin/wodim: CUE sheet not accepted. Retrying with minimum pregapsize = 1.
process (BraseroCDRecord) stderr: Errno: 5 (Input/output error), send_cue_sheet scsi sendcmd: no error
process (BraseroCDRecord) stderr: CDB: 5D 00 00 00 00 00 00 00 20 00
process (BraseroCDRecord) stderr: status: 0x2 (CHECK CONDITION)
process (BraseroCDRecord) stderr: Sense Bytes: 70 00 05 06 00 00 20 0E 24 08 11 40 A8 04 00 00
process (BraseroCDRecord) stderr: Sense Key: 0x5 Illegal Request, Segment 0
process (BraseroCDRecord) stderr: Sense Code: 0xA8 Qual 0x04 (vendor unique sense code 0xA8) [No matching qualifier] Fru 0x0
process (BraseroCDRecord) stderr: Sense flags: Blk 100663328 (not valid)
process (BraseroCDRecord) stderr: cmd finished after 0.019s timeout 200s
process (BraseroCDRecord) stderr: /usr/bin/wodim: CUE sheet still not accepted. Please try to write in RAW (-raw96r) mode.
process (BraseroCDRecord) stderr: /usr/bin/wodim: Cannot send CUE sheet.
process (BraseroCDRecord) stderr: /usr/bin/wodim: Could not write Lead-in.
job (BraseroCDRecord) asked to stop
 status = 1
 error = 1
 message = «the cd information could not be written»
iter (BraseroCDRecord) stopping
process (BraseroCDRecord) got killed
iter (BraseroCDRecord) stopped
job (BraseroCDRecord) got out of loop
job (BraseroCDRecord) set_task
Session error : the cd information could not be written
—end Brasero log-file—

Nero Linux fails with the following logfile:

2CA0-80X3-1800-2000-406M-AA2A-****

Linux 2.6.22-14-generic
Nero API version: 7.5.14.4
Using interface version: 7.5.0.2
Installed in: /usr/lib64/nero/
Application: Nero AGNero Linux
Internal Version: 7, 5, 14, 4

Recorder: <PIONEER DVD-RW DVR-212D>Version: 1.24 — HA 4 TA 0 — 0.0.0.0
 Adapter driver: <sata_via> HA 4
 Drive buffer : 2000kB
 Bus Type : default (0) -> SCSI, detected: ?
Excluded drive IDs:
WriteBufferSize: 83886080 (0) Byte
BUFE : 0
Physical memory : 1509MB (1545812kB)
Free physical memory: 842MB (863112kB)
Memory in use : 44 %
Uncached PFiles: 0x0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Disabled (0)

23.1.2008
NeroAPI
08:25:18 PM #1 Text 0 File DlgWaitCD.cpp, Line 307
 Last possible write address on media: 359845 ( 79:59.70)
 Last address to be written: 26652 ( 5:57.27)

08:25:18 PM #2 Text 0 File DlgWaitCD.cpp, Line 319
 Write in overburning mode: NO

08:25:18 PM #3 Text 0 File DlgWaitCD.cpp, Line 2951
 Recorder: PIONEER DVD-RW DVR-212D;
    CDR code: 00 97 26 66; OSJ entry from: CMC Magnetics Corporation
    ATIP Data:
      Special Info [hex] 1: D0 00 98, 2: 61 1A 42 (LI 97:26.66), 3: 4F 3B 47 (LO 79:59.71)
      Additional Info [hex] 1: FF FF FF (invalid), 2: FF FF FF (invalid), 3: FF FF FF (invalid)

08:25:18 PM #4 Text 0 File DlgWaitCD.cpp, Line 493
 >>> Protocol of DlgWaitCD activities: <<<
 =========================================

08:25:18 PM #5 Text 0 File ThreadedTransferInterface.cpp, Line 792
 Setup items (after recorder preparation)
  0: TRM_DATA_MODE1 (2 — CD-ROM Mode 1, Joliet)
     2 indices, index0 (150) not provided
     original disc pos #0 + 26653 (26653) = #26653/5:55.28
     not relocatable, disc pos for caching/writing not required/not required
     -> TRM_ULTRARAW96_MODE1, 2448, config 4, wanted index0 0 blocks, length 26653 blocks [PIONEER DVD-RW DVR-212D (H:4 T:0)]
 —————————————————————

08:25:20 PM #6 Text 0 File ThreadedTransferInterface.cpp, Line 995
 Prepare [PIONEER DVD-RW DVR-212D (H:4 T:0)] for write in raw writing
 DAO infos:
 ==========
  MCN: «»
  TOCType: 0x00; Session Closed, disc fixated
  Tracks 1 to 1: Idx 0 Idx 1 Next Trk
    1: TRM_ULTRARAW96_MODE1, 2448/0x04, FilePos 0 367200 65613744, ISRC «»
 DAO layout:
 ===========
  ___Start_|____Track_|_Idx_|_CtrlAdr_|_____Size_|______NWA_|_RecDep__________
      -150 | lead-in | 0 | 0x41 | 0 | 0 | 0x00
      -150 | 1 | 0 | 0x41 | 0 | 0 | 0x00
         0 | 1 | 1 | 0x41 | 26653 | 26653 | 0x00
     26653 | lead-out | 1 | 0x41 | 0 | 0 | 0x00

08:25:20 PM #7 Text 0 File Burncd.cpp, Line 4263
 Caching options: cache CDRom or Network-No, small files-Yes (<32KB)

08:25:20 PM #8 Phase 24 File ExtendedProgress.cpp, Line 537
 Caching of files started

08:25:20 PM #9 Text 0 File Burncd.cpp, Line 4382
 Cache writing successful.

08:25:20 PM #10 Phase 25 File ExtendedProgress.cpp, Line 537
 Caching of files completed

08:25:20 PM #11 Phase 36 File ExtendedProgress.cpp, Line 537
 Burn process started at 40x (6000 KB/s)

08:25:21 PM #12 Text 0 File ThreadedTransferInterface.cpp, Line 2712
 Verifying disc position of item 0 (not relocatable, no disc pos, no patch infos, orig at #0): write at #0

08:25:21 PM #13 Text 0 File MMC.cpp, Line 17730
 StartDAO : CD-Text — Off

08:25:21 PM #14 Text 0 File MMC.cpp, Line 22396
 Set BUFE: Buffer underrun protection -> ON

08:25:21 PM #15 Text 0 File ThreadedTransfer.cpp, Line 269
 Pipe memory size 83836800

08:25:22 PM #16 SCSI -400 File SCSIInterface.cpp, Line 622
 SCSI Exec, HA 4, TA 0, LUN 0, buffer 0x0x15d6cc0
 Status: 0x04 (0x01, SCSI_ERR)
 HA-Status 0x00 (0x00, OK)
 TA-Status 0x05 (0x0B, SCSI_TASTATUS_FAILED)
 Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)
 Sense Code: 0xA8
 Sense Qual: 0x04
 CDB Data: 0x2A 0x00 0xFF 0xFF 0xD2 0x8E 0x00 0x00 0x1A 0x00
 Sense Data: 0x70 0x00 0x05 0x06 0x00 0x00 0x20 0x0E
             0x24 0x08 0x11 0x40 0xA8 0x04

08:25:22 PM #17 CDR -400 File Writer.cpp, Line 299
 Unspecified target error
 PIONEER DVD-RW DVR-212D (H:4 T:0)

08:25:22 PM #18 Phase 38 File ExtendedProgress.cpp, Line 537
 Burn process failed at 40x (6000 KB/s)

—end Nero Logfile—

K3b fails with the following logfile:

System
————————
K3b Version: 1.0.4

KDE Version: 3.5.8
QT Version: 3.3.7
Kernel: 2.6.22-14-generic
Devices
————————
CD-ROM CCD-52X6S YS0C (/dev/hdb, ) [CD-ROM] [Error] [None]

PIONEER DVD-RW DVR-212D 1.24 (/dev/scd0, ) [CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL] [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump]
Used versions
————————
cdrecord: 1.1.6

cdrecord
————————
scsidev: ‘/dev/scd0’
devname: ‘/dev/scd0’
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Wodim version: 1.1.6
SCSI buffer size: 64512
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
TOC Type: 0 = CD-DA
Driveropts: ‘burnfree’
Device type : Removable CD-ROM
Version : 5
Response Format: 2
Capabilities :
Vendor_info : ‘PIONEER ‘
Identification : ‘DVD-RW DVR-212D’
Revision : ‘1.24’
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0009 (CD-R)
Profile: 0x002B (DVD+R/DL)
Profile: 0x001B (DVD+R)
Profile: 0x001A (DVD+RW)
Profile: 0x0016 (DVD-R/DL layer jump recording)
Profile: 0x0015 (DVD-R/DL sequential recording)
Profile: 0x0014 (DVD-RW sequential recording)
Profile: 0x0013 (DVD-RW restricted overwrite)
Profile: 0x0011 (DVD-R sequential recording)
Profile: 0x0010 (DVD-ROM)
Profile: 0x000A (CD-RW)
Profile: 0x0009 (CD-R) (current)
Profile: 0x0008 (CD-ROM)
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Drive buf size : 1267712 = 1238 KB
FIFO size : 12582912 = 12288 KB
pregap1: -1
Track 01: audio 33 MB (03:21.57) no preemp swab copy
Track 02: audio 46 MB (04:37.64) no preemp swab copy
Track 03: audio 41 MB (04:06.52) no preemp swab copy
Track 04: audio 39 MB (03:57.09) no preemp swab copy
Track 05: audio 44 MB (04:23.26) no preemp swab copy
Track 06: audio 50 MB (04:57.25) no preemp swab copy
Track 07: audio 44 MB (04:22.48) no preemp swab copy
Track 08: audio 37 MB (03:44.24) no preemp swab copy
Track 09: audio 29 MB (02:53.06) no preemp swab copy
Track 10: audio 39 MB (03:57.36) no preemp swab copy
Track 11: audio 46 MB (04:38.16) no preemp swab copy
Track 12: audio 56 MB (05:36.44) no preemp swab copy
Track 13: audio 19 MB (01:54.32) no preemp swab copy
Track 14: audio 96 MB (09:33.10) no preemp swab copy
Total size: 626 MB (62:02.52) = 279189 sectors
Lout start: 626 MB (62:04/39) = 279189 sectors
Current Secsize: 2048
ATIP info from disk:
  Indicated writing power: 5
  Is not unrestricted
  Is not erasable
  Disk sub type: Medium Type A, high Beta category (A+) (3)
  ATIP start of lead in: -11634 (97:26/66)
  ATIP start of lead out: 359846 (79:59/71)
Disk type: Short strategy type (Phthalocyanine or similar)
Manuf. index: 3
Manufacturer: CMC Magnetics Corporation
Blocks total: 359846 Blocks current: 359846 Blocks remaining: 80657
Starting to write CD/DVD at speed 16.0 in real SAO mode for single session.
Last chance to quit, starting real write in 2 seconds.
Speed set to 2822 KB/s
   1 seconds.
   0 seconds. Operation starts.
Waiting for reader process to fill input buffer … input buffer ready.
Performing OPC…
Sending CUE sheet…
/usr/bin/wodim: CUE sheet not accepted. Retrying with minimum pregapsize = 1.
Errno: 5 (Input/output error), send_cue_sheet scsi sendcmd: no error
CDB: 5D 00 00 00 00 00 00 00 F0 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 06 00 00 20 0E 24 08 11 40 A8 04 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0xA8 Qual 0x04 (vendor unique sense code 0xA8) [No matching qualifier] Fru 0x0
Sense flags: Blk 100663328 (not valid)
cmd finished after 0.019s timeout 200s
/usr/bin/wodim: CUE sheet still not accepted. Please try to write in RAW (-raw96r) mode.
/usr/bin/wodim: Cannot send CUE sheet.
/usr/bin/wodim: Could not write Lead-in.
Writing time: 13.863s
/usr/bin/wodim: fifo had 191 puts and 0 gets.
/usr/bin/wodim: fifo was 0 times empty and 0 times full, min fill was 100%.

cdrecord command:
————————
/usr/bin/wodim -v gracetime=2 dev=/dev/scd0 speed=16 -dao driveropts=burnfree -eject -useinfo -audio /tmp/kde-sirzepp/k3b_audio_0_01.inf /tmp/kde-sirzepp/k3b_audio_0_02.inf /tmp/kde-sirzepp/k3b_audio_0_03.inf /tmp/kde-sirzepp/k3b_audio_0_04.inf /tmp/kde-sirzepp/k3b_audio_0_05.inf /tmp/kde-sirzepp/k3b_audio_0_06.inf /tmp/kde-sirzepp/k3b_audio_0_07.inf /tmp/kde-sirzepp/k3b_audio_0_08.inf /tmp/kde-sirzepp/k3b_audio_0_09.inf /tmp/kde-sirzepp/k3b_audio_0_10.inf /tmp/kde-sirzepp/k3b_audio_0_11.inf /tmp/kde-sirzepp/k3b_audio_0_12.inf /tmp/kde-sirzepp/k3b_audio_0_13.inf /tmp/kde-sirzepp/k3b_audio_0_14.inf

—end K3b logfile—

cdrecord, from the command line, fails at «Sending CUE Sheet». When run with the -raw96r option, it writes to the CD, but the CD is unreadable.

Thanks!

Here is the log file for K3b:

0 Members and 1 Guest are viewing this topic.

2012-03-01 21:31:54

I’m doing a little «project» of mine, and wanted to be able to tell if cue sheet is valid or not. Just regular compliant simple cue sheets.
I wasn’t able to find any tool that would validate cue sheet, except of course audio player that supports cue sheets

So in a lack of command line validator, what are common mistakes in cue sheets, except presence of referenced file name?

---

What are common cue sheet errors

Reply #1 – 2012-03-02 10:11:27

I don’t think errors are common at all, any type of error. Cue sheets get generated by software, so unless there’s a bug in the software causing to to generate the cue wrongly, errors shouldn’t occur ever.

The only time a «mistake» could get into a .cue is if it was typed up by hand — Why would anyone do that?

---

What are common cue sheet errors

Reply #2 – 2012-03-02 10:49:45

Doesn’t matter how cue sheets got bad — could be tempered by hand, HD corruption, transfer problem… anything imaginable. I’m just looking for a way to validate it — to issue *this is valid cue sheet*

Searching previously HA, majority or cue sheet error reports are about non-compliant cue sheet and foobar > 0.9 not being able to parse
There may be issues with character encodings
…

Checking that TRACK is matched with following INDEX 01 is obvious

Done all that in bash script, and looking for more

I guess I’ll have to look at some source code how players parse cue sheets, and try similar procedure

---

What are common cue sheet errors

Reply #3 – 2012-03-02 11:40:27

The only time a «mistake» could get into a .cue is if it was typed up by hand — Why would anyone do that?

I rip vinyl and sometimes manually author cue sheets so these rips can be burned to CD with gaps/indexes, where appropriate. It’s possible to enter cue points in a wave editor-type interface, but if I’m going to have to edit the cue sheet to add metadata, I figure why not just write it all by hand. The syntax is not very complicated. Behold:

REM COMMENT This manually edited cue sheet is non-compliant (EAC-style) because gaps are in the preceding track's file.
REM COMMENT Track divisions correspond to bands visible on the vinyl. Indexes are based on sonic content.
REM DATE 1991
PERFORMER "C-Schulz"
TITLE "10. Hose Horn"
FILE "[A01] C-Schulz - Reis.wav" WAVE
  TRACK 01 AUDIO
    TITLE "Reis"
    PERFORMER "C-Schulz"
    REM COMMENT Track A01 layout=======================================================================================
    REM COMMENT  0:00:00 main song
    REM COMMENT 10:29:08 pause with audible print-through
    REM COMMENT 10:31:16 1st unbanded, unlisted interlude
    REM COMMENT 10:50:25 pause with audible print-through
    REM COMMENT 10:52:32 2nd unbanded, unlisted interlude
    REM COMMENT 11:01:43 pause
    REM COMMENT We could give the interludes their own indexes, but then what to do with the pauses before each one?
    REM COMMENT Give the pauses their own indexes, too? Aren't the non-zero indexes supposed to be for non-pauses?
    REM COMMENT I guess just make the interludes and the pause before them be index 02. *shrug*
    REM COMMENT ====================================================================================================
===
    INDEX 01 00:00:00
    INDEX 02 10:29:08
  TRACK 02 AUDIO
    TITLE "Meister"
    PERFORMER "C-Schulz"
    INDEX 00 11:01:43
FILE "[A02] C-Schulz - Meister.wav" WAVE
    INDEX 01 00:00:00
FILE "[B01] C-Schulz - Ein.wav" WAVE
  TRACK 03 AUDIO
    TITLE "Ein"
    PERFORMER "C-Schulz"
    PREGAP 00:04:00
    INDEX 01 00:00:00
FILE "[B02] C-Schulz - Klang.wav" WAVE
  TRACK 04 AUDIO
    TITLE "Klang"
    PERFORMER "C-Schulz"
    INDEX 01 00:00:00
FILE "[B03] C-Schulz - Glockenspiel.wav" WAVE
  TRACK 05 AUDIO
    TITLE "Glockenspiel"
    PERFORMER "C-Schulz"
    INDEX 01 00:00:00
FILE "[B04] C-Schulz - Tri-Top.wav" WAVE
  TRACK 06 AUDIO
    TITLE "Tri-Top"
    PERFORMER "C-Schulz"
    INDEX 01 00:00:00
FILE "[B05] C-Schulz - Barbapapa.wav" WAVE
  TRACK 07 AUDIO
    TITLE "Barbapapa"
    PERFORMER "C-Schulz"
    INDEX 01 00:00:00
  TRACK 08 AUDIO
    TITLE "1972"
    PERFORMER "C-Schulz"
    INDEX 00 04:05:69
FILE "[B06] C-Schulz - 1972.wav" WAVE
    INDEX 01 00:00:00
  TRACK 09 AUDIO
    TITLE "KreuzChor"
    PERFORMER "C-Schulz"
    INDEX 00 01:05:43
FILE "[B07] C-Schulz - KreuzChor.wav" WAVE
    INDEX 01 00:00:00
  TRACK 10 AUDIO
    TITLE "Star"
    PERFORMER "C-Schulz"
    INDEX 00 01:29:08
FILE "[B08] C-Schulz - Star.wav" WAVE
    INDEX 01 00:00:00
FILE "[B09] C-Schulz - Nr.5.wav" WAVE
  TRACK 11 AUDIO
    TITLE "Nr.5"
    PERFORMER "C-Schulz"
    INDEX 01 00:00:00
FILE "[B10] C-Schulz - Kurze Flitze.wav" WAVE
  TRACK 12 AUDIO
    TITLE "Kurze Flitze"
    PERFORMER "C-Schulz"
    INDEX 01 00:00:00
  TRACK 13 AUDIO
    TITLE "Aus"
    PERFORMER "C-Schulz"
    INDEX 00 01:40:17
FILE "[B11] C-Schulz - Aus.wav" WAVE
    INDEX 01 00:00:00

Mistakes can be introduced when editing machine-generated cue sheets. There are many reasons to edit cue sheets, such as:

• Fixing problems in existing cue sheets (like inaccurate track boundaries)
• Creating track boundaries where there were none (like for a 1-track DJ mix or live CD)
• Converting indexes to tracks (or vice-versa)
• Combining cue sheets
• Editing or adding metadata (e.g. removing quotation marks)
• Adding info that wasn’t able to be scanned for at rip time
• Removing a data track (e.g. the cue sheet refers to the data track, but the track wasn’t ripped)
• Removing a Unicode BOM (to help apps that don’t recognize it)

A few mistakes to watch for:

• First index for a given track not 00:00:00 (even though in theory this should be OK)
• unclosed quotation marks (quote mark count on a line must be even, nothing after the last quote)
• tracks out of sequence (first track must be 01, next 02, next 03, etc.)
• indexes out of sequence (first must be 00 or 01…)
• track or index out of range (must be 00 to 99)
• index times in wrong format (must be MM:SS:FF, SS must be 00 to 59, FF must be 00 to 74)
• PREGAP and INDEX 00 both given for a track
• unrecognized instruction (line starts with unknown keyword)

Questionable circumstances (what’s correct is unclear, maybe issue a warning):

• quotation marks in the metadata or comments (maybe not allowed)
• non-CRLF line breaks (no rule, but LF or CR only isn’t universally compatible)
• non-compliant (TRACK changes before next FILE: not allowed, but no other way to handle ordinary file-per track rips)
• non-ASCII, non-CRLF characters in non-UTF-8 document (no rule, but UTF-8 is de facto standard)
• Unicode BOM present (it helps identify encoding, but isn’t universally supported)
• blank lines (no rule, I think)

Those are just off the top of my head

---

What are common cue sheet errors

Reply #4 – 2012-03-02 12:06:04

Thank you mjb2006, your post is what I wished to get
It will keep me busy for some time, and when I get confident enough with the procedure, I’ll post my results

Cheers

---

What are common cue sheet errors

Reply #5 – 2012-03-04 00:25:38

Here is one try: https://github.com/klonuo/bash-cue-validator

Includes test script and applied (Nautilus thumbnailer) script.
I understand that this should have be done in Python or similar more universal and easier approach, but wanted to try hard luck with bash, nonetheless
Please try it if you can, and comment

---

What are common cue sheet errors

Reply #6 – 2012-03-04 22:39:33

The only time a «mistake» could get into a .cue is if it was typed up by hand — Why would anyone do that?

When a CD is technically an entire track, but in reality has lots of songs? Like http://www.hydrogenaudio.org/forums/index….showtopic=93154 …

---

What are common cue sheet errors

Reply #7 – 2012-03-05 01:42:46

… and on attached screenshots on github, first cuesheet with invalid referenced file was created by foobar under wine — «Boris Kovač…» mp3 file was created and in the accompanied cuesheet it was referenced as «Boris Kovac…», by foobar converter

---