I agree whtn madxcream. That'd be a nice feature.
Overall, I find cueproc more reliable than foobar's covert tools. I'd like to use cueproc, but I need the cover art processing working for that.

I also got simiar error to coffeebucket when trying to create a list of cue files.

CueProc 1.9 was out.
- Encoder 'lame_nyaochi' was removed to replace 'lame' codec. The 'lame' encoder now supports albumart images. This change was made because my patch has been merged to the lame CVS.
- New option, --albumart-action, to configure the action when albumart images are detected. CueProc now supports 'copy' action, which copies albumart images to the output directory.
- Bug-fix for --find action

Note that CueProc 1.9 requires LAME 3.97 with my patch applied, LAME 3.98b3, or later for lame encoding.

madxcream and urlwolf,
Thank you for the suggestion. Please add "--albumart-action copy" to the cueproc command-line.

coffeebucket,
Sorry for the late action for this problem. I also confirmed that "cueproc --find" did not work with filenames with Japanese characters. I hope this version will sort out your problem at last.

Thanks for the update, nyaochi.

One question though.

I have some cue files that cueProc doesn't understand.
They have INDEX 02, I think this is the only common factor.

Any idea why this happens?

Thanks

Hi Nyaochi,

Thanks for the cueproc. Question: when I run the cueproc 1.9 with a cuesheet pointing at an APE file. It said "WARNING: No suitable input class found for track #xx". I check with "cueproc -l". It doesn't list APE. However, I saw it on the webpage that it supports APE. Does cueproc really support APE? I ran the same cuesheet/ape with ACDIR and it experiences no problem. However, I would like to use cueproc since it seems that it has better support of UTF8 file name....

Lawrence

I added INDEX 02 to my chesheet file, but CueProc worked fine. One possibility is that the tracks do not have INDEX 01 but only INDEX 02. CueProc requires INDEX 01 to exist in all tracks.


Yes, it does support APE files. I confirmed the compatilibity with Monkey's Audio 3.99F.

Please try:
getaudio --test CDImage.ape
If this command outputs "TEST OK", CueProc should handle the APE file.

Thanks for your response. I ran that and I got "TEST OK". I became suspicious that it might be some other reason:

I ran it with:

cueproc -c lame --target o.txt

where o.txt's contect is "情·菲·得意\CDImage.cue". (note: there are some Traditional Chinese character between the first " and \). It still gives me the same error. Anyway, I renamed the directory and changed o.txt to "fayewong\CDImage.cue". It ran partially success wheres the program jumped to lots of command line trying to invoke lame. (It still fail because the all the --tt --ta were messy international characters and my lame doesn't support --tv option.). Now, I think the cueproc couldn't support the traditional Chinese character. I am curious to know if the cueproc supports Japanese character since I guess you are from Japan...

Do you use Windows on traditional Chinese locale? Otherwise, CueProc cannot deal with Chinese characters correctly.

There's no language specific routine in CueProc. It just converts everything from the Windows default codepage to UTF-8 for the internal representation, and coverts back to the Windows default codepage when invoking external encoders. I don't favor any language.

Yes, I do. I have the "Control Panel"->"Regional and Langauge Options"->Advanced->Language for Non-Unicode Program set to Chinese(Taiwan). When I do a "dir", I can see those Traditional Chinese character without any problem. I can also use foobar2000 to play the UTF8 cuesheet without problem (under Traditional Chinese directory). I understand that Windows store those directory name in Unicode. Do you think the reason is the code page convert between Traditional Chinese (big5) & Unicode?

Then, I don't really know What is causing the problem... Here is one .cue that doesn't work:


thanks

I did some more study. I download your "lame" and did:

cd xxxx <- where xxxx is the Traditional Chinese character subdirectory
cueenc -w utf8 -c lame CDImage.cue

it still gave me:

WARNING: No suitable input class found for track #1, G:\xxxx\CDImage.ape
....

I suspect the error is caused by getaudio....

Yet another cue file that doesn't get converted.
Foobar cannot open it either. It has unicode chars, but that should not be a problem, right?



This is an EAC encoded file. Threre are only INDEX 01s. I'm really stumped...

Sorry I have no idea and way to experiment your problem.


I don't think CueProc can handle cuesheets that foobar cannot open. You might fix this problem with -w option, but I'm not sure.

With my little experience with cueproc & foobar2000, I think your problem is caused by those international character, e.g. Vänskä. I ususally my cuesheet is saved in UTF8 format. So, say, you did that. Then, you can use:

cueenc -c lame -w utf8 yourcuesheet.cue

nyaochi,

Thanks. Just out of curiosity: Do you run Japanese song? I remember I tried to run the Momoe Yamaguchi yesterday. The directory name is like "パールカラーにゆれて". I still has a similar problem. If you run with Japanese directory name without any problem, can you tell me what options you are setting (-W -w)?. Maybe it can give me some hint about how to handle Chinese directory name.... Thanks.

Your program CueProc is very nice.

I have two issues one is a bug and the other an extension of your "find" function.

1. If there is a "REM GENRE R&B" in the cuesheet then it will never encode anything. It must be a problem with the "&" character.

2. I have many cue sheets for each rip, and would like to be able to find all *.cue files but not *.[*].cue files.
Can you do this.?

Is it intended for --albumart-files to also utilize variable substitution the way other CueProc options do? I have my album artwork backed up using the same base name as my albums, using the following form:

${ARTIST} - [${DATE}] ${ALBUM}.cue
${ARTIST} - [${DATE}] ${ALBUM}.flac
${ARTIST} - [${DATE}] ${ALBUM}.jpg

It would be nice to be able to combine the --albumart-files and --target options when the artwork name varies.
If there is a way to do this, I haven't been doing it right nor have I figured out how to with CueProc 1.9

Thanks.

Wow! This is exactly how my FLAC library is organized! I wanted to ask Nyaochi the very same question, but you beat me to it.

Nyaochi, it will be great if you implement variable substitution for album art files, which will offer a great deal of flexibility when it comes to organizing ones library.

However, thank you for all the effort. I have used this program before and I love it.

Thank you very much for a great tool. I have one problem and one request.

The problem:
I am attempting to transcode using the lame plugin; however because the genre tag is not quoted, genres of "R&B", "Rock & Roll", and "Drum & Bass" will cause the process to fail.


The request:
I would like to be able to use your standard lame plugin to do the transcoding and tagging of my tracks. Your tool works great, with one exception, identification of the "Various Artists". I know this has been briefly touched on before, but, would it be possible to add an option to output the album artists in the band and/or a user "album artist" frame? I realize that this can fuel the whole ragging debate between "BAND" versus "album artist", but the reality is that the tools I use expects to find "album artist" and pretty much ignores "BAND".

Thank you again for such a great tool.

Hi Nyaochi. I am thinking of moving from MP3 to AAC and am in need of this feature very badly. This is due to the fact that the Nero AAC encoder cannot embed album art into files. We need to use the AAC tagger for this purpose which rules out the usage of the current version of CUEProc. Can you tell me whether you plan to implement this soon? Thanks.

Hi all,

After the long silence, I'm going to release an update of CueProc within a few weeks (in mid of Feb). I would like to include your as many requests from users as possible because I may not release CueProc so often. I do appreciate your suggestions and bug reports before the next release.

These are the issues to be addressed in the next release:

• Quote '&', '<', '>', '|' characters.
• Investigate the problem when a variable used for directory names contains "." or ".."
• Handle UTF-8 BOM sequences properly.
• Support albumart images for MP4/AAC files.
• Assume *.jpg, *.jpeg, *.png, *.gif as albumart images for *.cue
• Review the patch from Smyttie (Sorry for the very late reply).

This is the worst bug in the current CueProc release. I'll fix this.


No. Use grep or other programs to filter out such files.


Right. I'll support this.


Do you want to extract album-artist values from "REM BAND" fields? Please elaborate this item if my understanding is wrong.


I'm going to use neroAACTag.exe to attach albumart images to MP4/AAC files.

Moderation: removed unnecessary (massive) quote.

Wow! Thank you very much Nyaochi . I will wait until you release the new version in February and use it then.

Nyaochi.

Thank you again for sharing this great tool. I apologize for the length of this reply, but I do hope it provides clarity to what I am doing.

I use EAC to rip a CD into a flac image. I then use cueproc to transcode (and split) the flac image file into individual MP3 tracks. For a compilation album (a compilation of different artists), EAC will create the cuesheet with an album level field "PERFORMER Various Artists". The performer of each track will be correctly identified at the track level (e.g., "PERFOMER Frank Sinatra").

When the album level performer is not the same as all the track level performers, cueproc will correctly identify the album as a compilation. For a compilation, one of the things the lame plugin does is to create an additional tag in the MP3 for "BAND", setting the value of the tag to that of the cuesheet's album level "PERFOMER".

Of course, this is what the tool already does, and it works perfectly. My problem is that in addition to outputting the cuesheet's album level "PERFORMER" field in the MP3's "BAND" tag, I would also like to create a user text tag in the MP3 called "album artist" with the same value.

I have tried various methods to create the user text tag using cueproc and the lame plugin; however, I was not successful. Instead, I have resorted to using your cueproc and Tycho's metamp3 as a post process. Following is an sample of the two commands:



The way you identify a compilation and all the additional actions done automatically by the lame plugin are great. I do not want to change any of that behavior. I "simply" would like to create an additional user text tag for "album artist".

Thank you again.
Brian

I released CueProc 1.10 today. The download URL has been changed due to a restructuring of my website.
http://nyaochi.sakura.ne.jp/software/cueproc/

CueProc 1.10 (2008-02-24)

• Quote '&', '<', '>', and '|' characters in variable values when necessary.
• Read CATALOG field in chesheet.
• Evaluate names of albumart images as variable expressions (thanks to Smyttie).
• Detect and ignore UTF-8 BOM sequence properly.
• Support albumart images for FLAC, Nero MP4/AAC files.
• Assume *.jpg, *.jpeg, *.png, *.gif as albumart candidates, given *.cue.
• Add a MP3 plugin (lame_eyed3) that uses LAME encoder and eyeD3. This plugin can attach ID3v2.3 tags in UTF-16 encoding (thanks to HaHaHaHa).
• Source code restructuring (thanks to HaHaHaHa).

The best way to do this is to customize the source code of CueProc for your own purpose. It's difficult to maintain the intersection of the ways in which users manage their music collections, but not so difficult to modify the source code of CueProc, which is written in Python (and Python is easy to learn). The relevant source code is src/ce_lame.py or src/ce_lame_eyed3.py. The following is the procedure to build cueproc.exe

1. Install the windows binary of Python.
2. Install py2exe, which compiles a python script to cueproc.exe
3. Install EyeD3 library.
4. Modify the source code of CueProc.
5. Compile the source code by "python setup.py py2exe"

I once wrote a plugin that uses LAME for MP3 encoding and metamp3 for MP3 tagging, but didn't release it because metamp3 did not seem to support Japanese character properly (at least when I tried before).

Thank you for the update and the pointer (especially the steps necessary to (re)make cueproc.exe):

After installing Python, py2exe, an getting the eyed3 module installed, I was able to accomplish what I needed by modifying ce_lame_eyed3.py by inserting one line of code:

I did a very limited test (one image) and it works great!

Once again, thank you very much for sharing your hard work.

FYI:
When recreating cueproc.exe, I get the following warning:

The following modules appear to be missing
['email.Generator', 'email.Iterators', 'email.Utils']

I could not figure out what I had done wrong; nor could I find any requirements for the email module. I checked that the email module was installed and tried various ways of including the module, but nothing worked. As my Python skills are extremely limited and cueproc.exe is working, I am going to ignore the error for now.

bsleeth,

I'm a bit surprised to see that you had achieved what you want in such a short time. Thanks for the understanding.


Yes, I also got this warning too. I think we can simply ignore this as CueProc does not have a dependency to email module.

Excellent news! Thank you very much, Nyaochi. I've been waiting for this for a while and my patience has finally paid off.

Unfortunately, I cannot test the new version until the weekend, but I will post updates as soon as I do so.

Once again, Nyaochi, thank you very much.

Hi Nyaochi. Sorry about this huge delay. I unfortunately decided to stick to LAME as most of my devices play MP3s and not all of them play AACs. Hence, I am afraid that I may not have any useful feedback as far as the new features are concerned.

However, thank you once again for this excellent utility. Keep up the great work!

Hi there, I've been using Cueproc to break up wav files of interviews, it's been really handy, thanks for the great program!

I have been having a bit of a problem with cue files though, the specifications I have come across have been a bit vague re Index 00 and index 01.

What i would like to do is instead of having exact cuts, I would like to add 1 sec to the start and end of each mp3, to create a slight overlap which will mean if the gap is quite narrow then nothing is cut off. Does anyone know how to do this?

I currently use just one index entry per track to cut the track where required.

Thanks for any help!

Stuart

Hi everyone,

I'm trying to use getaudio.exe to extract short samples (10s~30s each) from my wavpack images. What's the right command line to do this? I know it starts with "getaudio --begin 00:00:00 --end 00:10:00 floyd.wv" (for example), but what's after that?

I also can't get cueproc to work on this new computer, or I would just copy the command line from it. If I use: cueproc -c wave -o "$TITLE" floyd.cue

I get the error: CueProc: floyd.cue [01/10]
WARNING: No suitable input class found for track #1, C:\store\cueproc\win32bin\floyd.wv (repeated for track 2, track 3 etc.)

If I use: cueproc -c wave -o "$TITLE" floyd.wv (i.e. change floyd.cue to floyd.wv)
I get: WARNING: Failed to open a target, floyd.wv

I guess my command line is wrong? I haven't used cueproc for a while. I know that the floyd.wv file is OK because I can use getaudio.exe to make a 10s mp3 file, but that's not what I want...

Thanks,
Stephen

Whenever I've had the 'no suitable input class found' error it was because I had the wrong file name in the cuesheet. Typically I had the wave version listed in the cuesheet even though the file was compressed, or vice versa.

I.e. do you have the file listed as 'floyd.wav' in the cuesheet even though it's now a wavpack file?

Hi Deep_Elem,

The cuesheet has the line: FILE "floyd.wv" WAVE. It should point to the right file.

Could you do me a favour and run cueproc to output .wav files, and tell me what the second half of the getaudio.exe command line is?

Thanks

Edit: Don't worry, it works fine on this computer. I need to add " > .\floyd_clip.wav" to the end of getaudio. I probably should have tried it again before posting...

It's impossible to achieve this by modifying cuesheets. This should be dealt with by modifying the CueProc source code. In cueproc.py, the following line generates the command-line for extracting an audio stream of a track:

Here, track.begin and track.end store the start time and end time of the track in string format. You can modify the start time and end time just before this line. It would be good if CueProc had the scalability to achieve this. But currently, modifying the source code is the easiest approach to achieve what you want.


FYI, this is how CueProc invokes getaudio.exe:

The syntax 1) extracts an audio stream (in the specified period) in AUDIO_FILE to STDIN in WAVE format. The syntax 2) checks if AUDIO_FILE is supported by getaudio.exe. The syntax 3) outputs meta-information in AUDIO_FILE to STDIN.

Thanks For responding, Nyaochi,
I'm sure you know best and I am just going to look like an idiot, but would it be easier to change in cuesheet.py here?



Also how does CueProc handles times so I know how to adjust?

Thanks for any help you can provide.

Stuart.




[quote name='nyaochi' date='Jun 21 2008, 02:23' post='572315']
[quote name='stuarticus' post='571537' date='Jun 17 2008, 21:14']
What i would like to do is instead of having exact cuts, I would like to add 1 sec to the start and end of each mp3, to create a slight overlap which will mean if the gap is quite narrow then nothing is cut off. Does anyone know how to do this?
[/quote]
It's impossible to achieve this by modifying cuesheets. This should be dealt with by modifying the CueProc source code. In cueproc.py, the following line generates the command-line for extracting an audio stream of a track:

Hi Nyaochi, I am still no closer to solving this (I am not a very experienced Python user) am I right in thinking that the track.begin is held as a string? Does this make it difficult to change?

This functionality would be very useful to our project, could you make the modification for a fee, if necessary?

Anyone else with any Python advice that can be help I would also be pleased to hear from.

Cheers, Stuart.