The return of....CDA2SFX!, CASBAH is born, new cmd for self burning exe Options

[Captain Dan]

Once upon a time, in a forum not so far away, there was a discussion about creating self extracting and self buring ISO applications....

http://www.911cd.net/forums//index.php?sho...c=18845&hl=

Imgburn was used as the burner in that case.

The requests went in, and the concept expanded into a similar idea for audio CDs, which cannot be stored as ISO files......

http://www.911cd.net/forums//index.php?sho...st&p=126109

But alas, imgburn could not be used because it would not handle audio data (.cue / .wav / .bin)

So cygwin and cdrecord were used and beatifully fashioned by jaclaz to work in this respect.

But NOW! in 2008, a little over 1 year later....

The new imgburn handles AUDIO CD .cue files!

http://www.imgburn.com/index.php?act=changelog

There are some exotic choices there too....

*using a CUE file - this includes Audio CD's from anything DirectShow/ACM can handle - AAC/APE/FLAC/MP3/MPC/OGG/PCM/WAV/WMA etc

Naturally, I wondered if the code can be dug up and re-jigged so that we can kiss goodbye to cygwin / cdrecord and the ugly DOS box that was used to input user choices.....

I'm off to play some more with imgburn now....yay...

Dan

[cdob]

Does ImgBurn support your .cue audio files?

Try commandline:

CODE

ImgBurn.exe X:\temp\sound.cue

or

CODE

ImgBurn.exe /mode write /SRC X:\temp\sound.cue

Remember there are different DirectShow/ACM files at different machnines.
A wav file should be possible always.

As for v2.4 ID3 tags a updated ImgBurn is required
http://forum.imgburn.com/index.php?showtopic=6027
http://forum.imgburn.com/index.php?showtop...amp;#entry62969


Which ugly DOS box? There is a fine DOS box at current solution.

[Captain Dan]

Does ImgBurn support your .cue audio files?

Yes it does. It works great (from both the GUI and the command line) I'm using a .cue and .wav as created by EAC.

This is the command line in my test:

imgburn.exe /PORTABLE /MODE WRITE /SRC C:\Documents and Settings\Administrator\Desktop\test\"Missy Higgins - Live at the wireless.cue" /SPEED MAX /EJECT YES /IGNORELOCKVOLUME /START /WAITFORMEDIA /CLOSESUCCESS /NOSAVESETTINGS

The full path is needed after /SRC otherwise ImgBurn can't find the corresponding .wav file.

Anway, I've just spent half a day mucking around with Burn_CDA.cmd (jaclaz' code) to make it use Imgburn, but I'm not very good at coding so it's not working!

Which ugly DOS box?

Oh, you know.....the ugly one...... LOL (!)



This post has been edited by Captain Dan: Feb 18 2008, 06:42 AM

[jaclaz]

This is the command line in my test:

imgburn.exe /PORTABLE /MODE WRITE /SRC C:\Documents and Settings\Administrator\Desktop\test\"Missy Higgins - Live at the wireless.cue" /SPEED MAX /EJECT YES /IGNORELOCKVOLUME /START /WAITFORMEDIA /CLOSESUCCESS /NOSAVESETTINGS

The full path is needed after /SRC otherwise ImgBurn can't find the corresponding .wav file.

Ok, now that I know the "right" command line, I'll see what I can do.

About the "ugly" DOS BOX, it's all a matter of what one wants to do.

Once the DOS batch works, I guess that anyone familiar with AutoIt could "convert" it , the point is to find a volunteer....

jaclaz

[Captain Dan]

Ok, now that I know the "right" command line, I'll see what I can do.

Terrific

I guess you'll have to see if the command can integrate a variable like %cuefile% instead of the actual .cue filename.

Hope it can.

About the "ugly" DOS BOX, it's all a matter of what one wants to do.

Indeed.

Don't get me wrong, I appreciate DOS and its box...I just always consider how it looks to an end user who often has no idea what DOS (or sometimes even a box) might be.

God bless end users.


Dan

[hilander999]

An interesting solution to the dos box, pointed out by Siegfried a while back, is WIZAPP (The Wizard's Apprentice).
http://wizapp.sourceforge.net/

Seems to work quite well and is a very easy way to add a gui to any command script.
Autoit would certainly be better, but also requires someone who knows how autoit works.

[Captain Dan]

Yes the wizard's apprentice has has been shown to me before...

It's probably overkill and more work?

I was thinking that just the imgburn gui itself on display would be 'pretty' enough (as in ISO2EXE)

This post has been edited by Captain Dan: Feb 18 2008, 08:20 PM

[jaclaz]

An interesting solution to the dos box, pointed out by Siegfried a while back, is WIZAPP (The Wizard's Apprentice).
http://wizapp.sourceforge.net/

Seems to work quite well and is a very easy way to add a gui to any command script.
Autoit would certainly be better, but also requires someone who knows how autoit works.

Siegfried?

Good to know, I thought I was the only one using it!

jaclaz

[hilander999]

Siegfried?

http://www.911cd.net/forums//index.php?showuser=8680

[jaclaz]

@hilander999
Of course I know Siegfried, I simply thought the Wizard's Apprentice to be a "poor man's" solution for dinosaurs like me, and that advanced users/programmers, like Siegfried undoubtedly is, used more sophisticated tools .

@Captain Dan
Try the attached.

Something curious:
I did not try the actual burning, just the SFX procedure, and found that it throws an error with file name "test.cue", as well as with "trest.cue" but works allright with "crest.cue" and with "wrest.cue", there must be a bug in the parsing engine of IMGBURN command line, that "misses" the initial "t"

Tested versions:
IMGBURN 2.4.0
7z457_extra.7z (7zSD.sfx)
7za457.zip (7za-exe)


jaclaz

P.S.:
Since now we can use IMGBURN for .cue also, maybe it would be possible to "unify" ISO2SFX and CUE2SFX in a single batch?

This post has been edited by jaclaz: Feb 20 2008, 06:03 AM

Attached File(s)

 CUE2SFX.zip ( 1.91K ) Number of downloads: 198

 

[Captain Dan]

P.S.:
Since now we can use IMGBURN for .cue also, maybe it would be possible to "unify" ISO2SFX and CUE2SFX in a single batch?

Yes that also occurred to me.

I guess it depends if anyone was interested enough. I didn't want to mention it because it's just creating extra work (that I can't contribute much to).

Thanks for the batch file, I will test in the morning (AEST).


Dan

[Captain Dan]

Bugger it!

I can't sleep so I'm testing it now.

Note to self: Don't eat a huge Pizza 2 hours before going to bed......

Ok, in principle the batch works except that it doesn't 'pick up' and include the actual filename.wav......

It only compresses and packs the filename.cue and imgburn.exe.

[jaclaz]

Sure it does not, I just changed the command line and some references to .iso in the ISO2SFX.CMD.


I will add the .cue parsing routine to it later, can you post an example .cue file, so I can test it in a "real world" situation?

jaclaz

[cdob]

@jaclaz

ImgBurn creates a cue file

FILE "sound_01.wav" WAVE
TRACK 01 AUDIO
TITLE "sound_01"
INDEX 01 00:00:00
FILE "sound_02.wav" WAVE
TRACK 02 AUDIO
INDEX 01 00:00:00

Goldenhawk Cdrwin

FILE "X:\TEMP\SOUND.BIN" BINARY
TRACK 01 AUDIO
INDEX 01 00:00:00
TRACK 02 AUDIO
INDEX 00 01:53:22
INDEX 01 01:55:22

You may remember
http://www.911cd.net/forums//index.php?s=&...st&p=126220

There are FILE and CDTEXTFILE.

FILE filename filetype
Arguments
filename The audio or data file’s filename (can include device and directory). If the filename contains any spaces, the filename must be enclosed in quotation marks.

Examples
FILE C:\DATA\TRACK1.ISO BINARY
FILE C:\MUSIC\TRACK2.WAV WAVE
FILE “C:\MUSIC\LONG FILENAME.MP3” MP3


CDTEXTFILE filename
Argument
filename The CD-Text file’s filename (can include device/directory). If the filename contains any spaces, then it must be enclosed in quotation marks.

Examples
CDTEXTFILE C:\TEST\DISC.CDT
CDTEXTFILE “C:\LONG FILENAME.CDT”

@Captain Dan
For wav testing purposes try

CODE

cd %~dp0
.\7za.exe a "%destpath%files.7z" imgburn.exe "%~fx1" "%~dp1*.wav"

[Captain Dan]

CODE

cd %~dp0
.\7za.exe a "%destpath%files.7z" imgburn.exe "%~fx1" "%~dp1*.wav"

Yes as a test that worked very well.
I know that using *.wav might cause some issues later on though, for example in a multi .cue / .wav directory.

Observations:

On running the batch and creating the .exe package, the DOS box reports an incorrect estimate size for the target .exe file.

The resulting .exe file no longer carries the ImgBurn icon - it is a bog standard Windows .exe icon.

However, these are minor details of course.

[jaclaz]

@Captain Dan

I will add the .cue parsing routine to it later, can you post an example .cue file, so I can test it in a "real world" situation?

Can I assume that the "IMGBURN" example posted by cdob is correct?

What program do you use to create the .cue + .wav?


@cdob
What does CDRWIN matter?

Or should I provide for both "WAVE" and "BINARY" ?

jaclaz

[cdob]

What does CDRWIN matter?

Goldenhawk developed cue sheet. Goldenhawk's cdrwin use cue sheets.
Cue sheet documentation is poor.
Goldenhawk's cdrwin.hlp and cdrwin.pdf are a de facto cue sheet specification.

Explanation and more example:
http://wiki.hydrogenaudio.org/index.php?title=Cuesheet

Other application adopted cuesheet idea. But made some own enhancements.
All use file section similar to cdrwin.


What to support? Wav files only? Or a more general cue sheet support?

Different choices:
CDA2SFX: only wav files
CDA2SFX: wav and mp3 files
CDA2SFX: wav, mp3 and aiff files
CDA2SFX: any file names

CUE2SFX: general cue sheet approach.
However I doubt ImgBurn support all possibilities. Future ImgBurn version maybe enhanced.


Added:
Or do not parse cue file at all. No error detection.
Support: CDA2SFX directory
directory has to contain one cue file and addional files. Cue sheet has to use relative path.
If a user dosn't respect requirements, this creates false results.

This post has been edited by cdob: Feb 21 2008, 04:41 PM

[Captain Dan]

@jaclaz

I will add the .cue parsing routine to it later, can you post an example .cue file, so I can test it in a "real world" situation?

Please find an example I just created here:

http://classoneproductions.podcastactive.com/audio/boot/

It's called example.7z. It contains a small .cue and .wav pair.

Can I assume that the "IMGBURN" example posted by cdob is correct?

Yes, to a point. The command works fine but would I suspect be flawed when run from a directory containing multiple .wav files.

What program do you use to create the .cue + .wav?

I still use Exact Audio Copy (EAC).

[cdob]

Does previous posted ImgBurn CUE SHEET example makes sense?

The named IMGBURN command line was for basic testing purposes. Without cue sheet parsing, there has to be some assumptions.
It's assumes, one directory contains one *.cue and relating *.wav files. There maybe several *.wav files to one CD.
Cue sheet has to use relative path. That's no path in that case.

Do you create at Exact Audio Copy (EAC) one *.cue file and one *.wav file?

What's the final goal?
Support one *.cue file and one relating *.wav file?
Support several CDA possiblities?
Support CUE Sheets in general?

[Captain Dan]

Does previous posted ImgBurn CUE SHEET example makes sense?

Yes.

Do you create at Exact Audio Copy (EAC) one *.cue file and one *.wav file?

Yes I do. The cue sheet provides the track layout for the complete CD, thus eliminating the need to split the CD into a bunch of separate .wav files.

What's the final goal?
Support one *.cue file and one relating *.wav file?
Support several CDA possiblities?
Support CUE Sheets in general?

For me the goal is the first idea...'Support one *.cue file and one relating *.wav file'

The app should know which .wav because it should read/parse the .cue file

I myself certainly have no need for anything extra as you have listed above. However it's really up to the person who codes the app.
It might be easy to include support for uncompressed formats that the burner (in this case imgburn) can accept because it's only (as far as the app is concerned) an issue of file extension. For example, imgburn can accept .cue/.wav and .cue/.bin - both are used for audio CD images and both are uncompressed formats. When you start talking about compressed formats like MP3 you then have to introduce a codec and a transcoding routine.....unnecessary IMHO.

However, as jaclaz pointed out, there may be enough reason to unify functions from similar apps, ISO2EXE for example.

Dan

This post has been edited by Captain Dan: Feb 22 2008, 08:22 AM