Thanks! I wished something like this would happen. 😁

You're welcome 😀

Hopefully, someone with Mac compiling experience, could step in. 😎

When the baby is asleep and the family gone, I might be able to try my hands tonight (GMT)

Edit: uhm, no, never experienced lazarus/free pascal before...

You just need XCode (I believe you already have it) and the Lazarus .dmgs for Lazarus, FPC and Sources, the tools include install scripts, so it should be pretty easy to setup; the cuegen project itself includes several pre-defined build modes, you probably want "Release", just go to the Lazarus "Run" menu, click "Build" and you will get a nice binary (should be wherever you placed the source under the bin/release folder), if you want an application bundle go to the "Project" menu, "Project Options", under "Application", click on "Create Application Bundle", it should mostly work, I might do a build script for the different platforms when I have some time.
The only real problem I've had when compiling under OS X is that Lazarus (for whatever perverse reason) DOESN'T strip the generated binary, so it comes out rather large and you have to run the strip command by hand, again, if I get around to doing a command line script for building the project, that should be taken care of automatically.
It's also missing an icon in icns format, but that should be easily generated from the .png included in the source.

Thanks for the writeup. Sounds like a bigger project but I'll give it a try just will need more time 😉
If someone else wants to do it for OS X, I won't be sad 😉

The platform building scripts have been done, along with an OS X icon, you can build an Intel or Power PC binary and it will create an application bundle all by itself, if you build both, it will create a universal ("fat") binary. Just install Lazarus and its requirements, get the SVN code and run

1buildosx.sh

. Lazarus sometimes behaves oddly and if it doesn't build on the first run, execute the script again, if it still refuses, please DO tell me 😜

Downloaded lazarus and the needed packages and will give it a try soon 😉

I'm more interested in the reverse!

Have a game with bin/cue and compressed audio tracks and convert it back to a bin/cue which you can burn onto a disc.

Using compressed audio is blessing, but a curse because now all the GOG.com games come with compressed tracks.

The steps I do to get a working disc for my DOS machine is:

- Convert tracks to WAV
- Remove references to compressed tracks from CUE file
- Change the reference to the bin file so it refers to the renamed one
- Rename the GOG and INST files to bin and cue
- Create a mixed mode project with infrarecorder
- Burn the disc

If your cue files work with

1Index 01 00:00:00

it should be an easy addition to the program (write AUDIO instead of MP3 in the Track portion) and add .wav to the extension list (that functionality is already present and can be controlled by the user). You probably don't need to rename anything, in the end, it doesn't have to be a .bin file to be recognized using a .cue.
Example:

1FILE "somefile.ext" BINARY

And...you get a .cue sheet generated by the program.
So, really, the only change would be to allow the user to select whether they want the audio tracks to be listed as AUDIO or MP3.
I'll add that option if you're willing to test it and see if the CD works.
Of course the end user would be responsible for making the audio tracks correct for CD standard (44100 KHz sample rate, signed 16 bit)

I just posted a beta version that can generate cue files with uncompressed audio (as per Mau1wurf1977's suggestion). Look under the options menu. You can probably skip the part about renaming the .bin file from .gog or .inst as long as you use the correct file name and place everything in the same folder. The audio decompression and burning you still have to do with other programs. The beta version also includes some improvements and slight bug fixes. It can be found under the "BETA" folder in the Sourceforge files repository.

Cool!

I will check it out 😀

Let me know if it works.

bloodbat:
had a little time, some problems:
- in the buildosx.sh you call the wrong buildparameters.
lazbuild --bm="release os x ppc" cuegenerator.lpi
lazbuild --bm="release os x intel" cuegenerator.lpi
while in the cuegenerator.lpi you have "Release OS X PowerPC" and "Release OS X i386"

- building with lazbuild --bm="release os x i386" cuegenerator.lpi, I got the following output and error

1lazbuild --bm="release os x i386" cuegenerator.lpi
2primary config path: /Users/Dominus/.lazarus
3TranslateResourceStrings A Lang=en FallbackLang=en
4TCompiler.Compile WorkingDir="/Users/Dominus/Code/SVN/cuegen/" CompilerFilename="/usr/local/bin/ppc386" CompilerParams=" -MObjFPC -Scghim -CX -WR -O3 -Tdarwin -Pi386 -Xs -XX  -k-framework -kCarbon -k-framework -kOpenGL -k-dylib_file -k/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib:/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib -vewnhi -Filib/i386-darwin -Fu/Developer/lazarus/components/synedit/units/i386-darwin/carbon -Fu/Developer/lazarus/ideintf/units/i386-darwin/carbon -Fu/Developer/lazarus/lcl/units/i386-darwin/carbon -Fu/Developer/lazarus/lcl/units/i386-darwin -Fu/Developer/lazarus/components/lazutils/lib/i386-darwin -Fu/Developer/lazarus/packager/units/i386-darwin -Fu. -FUlib/i386-darwin/ -l -FEbin/release/i386/ -dLCL -dLCLcarbon -dCUEGEN cuegenerator.lpr"
5[TCompiler.Compile] CmdLine="/usr/local/bin/ppc386  -MObjFPC -Scghim -CX -WR -O3 -Tdarwin -Pi386 -Xs -XX  -k-framework -kCarbon -k-framework -kOpenGL -k-dylib_file -k/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib:/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib -vewnhi -Filib/i386-darwin -Fu/Developer/lazarus/components/synedit/units/i386-darwin/carbon -Fu/Developer/lazarus/ideintf/units/i386-darwin/carbon -Fu/Developer/lazarus/lcl/units/i386-darwin/carbon -Fu/Developer/lazarus/lcl/units/i386-darwin -Fu/Developer/lazarus/components/lazutils/lib/i386-darwin -Fu/Developer/lazarus/packager/units/i386-darwin -Fu. -FUlib/i386-darwin/ -l -FEbin/release/i386/ -dLCL -dLCLcarbon -dCUEGEN cuegenerator.lpr"
6Hint: Start of reading config file /etc/fpc.cfg
7Hint: End of reading config file /etc/fpc.cfg
8Error: Illegal parameter: -WR
9ERROR: failed compiling of project /Users/Dominus/Code/SVN/cuegen/cuegenerator.lpi

ok, editing the cuegenerator.lpi and deleting <RelocatableUnit Value="True"/> from the i386 target helped building it.

running the create_osx_bundle.sh chocked on line 24 (create_osx_bundle.sh: line 24: createbundle.resp: No such file or directory), commenting line 24 and 25 made that run and produced a "working" bundle.

On starting it breaks with

1error reading MemoCue.SelectedColor.StrikeOutPriority:
2Unknown property: "StrikeOutProperty"
3
4Press OK to ignore and risk data corruption.
5Press Cancel to kill the program.

Either OK or Cancel kill the program.

The scripts have been fixed.
The -WR parameter is unneeded for OS X and has been removed from those modes.
About the SynEdit error...I call no strikeout properties, get the latest SVN code of the generator, the Lazarus implementation of SynEdit is a bit...odd and barfs if I disable some properties I don't use (though it shouldn't).
Also, try using the latest Lazarus 1.2 Release Candidate, I'm using that (though it really shouldn't be a problem).
Edit: Indeed...the StrikeOut property isn't the latest Lazarus release version, use the RC2 for building the program 😉.

Will download and try. Hopefully sooner than weeks 😉

Is optimization level 3 stable? At least with gcc I thought the general advice is, to stick to -O2.
OTOH, it's not something complicated as DOSBox, so -O3 probably doesn't hurt...

compiled and runs.
BUT... how does it work? am I supposed to write down each file with path?
Drag'n'drop doesn't seem to work and I see no other way to put files there.

I don't know what you'd want to drag and drop.
Anyway, set starting and ending tracks, a extension (should default to .ogg) and, optionally, a data track, and click generate...there you go, you have a cue sheet, it can be edited, copied, saved...
The data track can be chosen (in the SVN version) using the "open" icon next to the data track text box. That's all.
I don't know about GCC and its evils, but my build modes should default to -O3, Free Pascal doesn't go through GCC...ever.