Skip Menu |

This queue is for tickets about the Audio-Cuefile-Parser CPAN distribution.

Report information
The Basics
Id: 41836
Status: open
Priority: 0/
Queue: Audio-Cuefile-Parser

People
Owner: matt.koscica [...] gmail.com
Requestors: greg.johnstone [...] ihug.co.nz
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: The way you're handling $cue->title needs correcting.
Date: Sun, 21 Dec 2008 00:25:49 +1300
To: bug-audio-cuefile-parser [...] rt.cpan.org
From: Greg Johnstone <greg.johnstone [...] ihug.co.nz>
Hello Matt, I don't know if you're still maintaining this or not as it's not changed since 2005 however I've noticed an issue which will affect people who create audio files for each track and then use .cue files to tie them together into the album definitions. The specification of the .cue file format explicitly allows multiple source file definitions. Each track is then found within that file until either the end of the .cue file is reached or another file specification line is found in the .cue file telling the system that the tracks specified are found in the new file from that point on. It is possible that each track in a .cue file of 16 tracks is found in a seperate audio file. Consequently you should make the adio file specification part of the track definition rather than part of the album definition. For myself, this is no biggie. Both because I burn entire CD image files as single FLAC files and then use .cue files to find the tracks within them and also because I wrote my own module that does pretty much exactly what yours does before finding yours. Yours is on CPAN though so I recon getting yours correct is the way to go. Cheers, Greg.
Hi Greg, Thanks for the bug report - will get this fixed. Cheers.