his looks very much like some Theme or Skinning software to me that went haywire. Please check that and disable it if found.
Yes, If I disable theme support dialog looks OK, but I use this theme for a long time and never seen such behavior before in any dialog.
If I understand you correctly, you wish to burn normal WAV files with some additional track information in a CUE file? Nope, that's not supported, and it probably won't be (this plugin sure isn't supposed to be/become a full-blown Nero-competing burning software with all those bells and whistles Smile ).
Don't be so modest! For now this feature is only difference between your plugin and Nero (for me, of course). It is really pity, because if you want to make lossless copy of audio CD any modern audio extraction software create WAV/CUE files. It is very popular format.
VadiMGP wrote:Don't be so modest! For now this feature is only difference between your plugin and Nero (for me, of course).
Well thanks, never thought I'd be that easy to outbid Nero.
It is really pity, because if you want to make lossless copy of audio CD any modern audio extraction software create WAV/CUE files. It is very popular format.
What information exactly is stored in that CUE file for audio tracks? All I can do at the moment is forward this as a suggestion to the responsible FoxBurner coder.
Another problem might be legal aspects. If that feature is mainly used to create exact copies of audio CDs, I can already hear the beloved music industry scream "evil program! can copy audio CDs! lawsuit!" I'd like to avoid that.
PERFORMER "Mireille Mathieu"
TITLE "Ciao Bambino Sorry CD1"
FILE "CDImage1.wav" WAVE
TRACK 01 AUDIO
TITLE "Ciao Bambino Sorry"
PERFORMER "Mireille Mathieu"
INDEX 01 00:00:00
TRACK 02 AUDIO
TITLE "Un Jour Tu Reviendras"
PERFORMER "Mireille Mathieu"
INDEX 00 02:58:38
INDEX 01 02:59:40
...
Actually burning engine only need info about start/end of track and gap between tracks.
I can already hear the beloved music industry scream "evil program! can copy audio CDs! lawsuit!"
Come on! Even if copy is illegal it already made by audio extracting software. I speak about burning only. Anyway today I do it with Nero and no one accuse Nero, AFAIK.
Can you add a function of creation cue file if you have bin only?
I know it's easy to make such file manually, but it would be very handy having one click only.
And I think small bug: Today I was burning some files on CD with your plugin and the total size on the panel did not match the figure displayed in "burning" dialog.
After all, computers crash, people die, relationships fall apart. The best we can do is breath and reboot.
piranha wrote:Can you add a function of creation cue file if you have bin only?
The SDK I use has no such function. If you tell me precisely how to do it manually, I might be able to code something myself.
And I think small bug: Today I was burning some files on CD with your plugin and the total size on the panel did not match the figure displayed in "burning" dialog.
All data sizes except for the one in the actual Burn Progress dialog are estimates. Only after preparing the project the final size is known.
Loc2262 wrote:
The SDK I use has no such function. If you tell me precisely how to do it manually, I might be able to code something myself.
The cue definition is here:
Well, if you know what a CUE manually-made from an existing BIN has to look like, please tell me directly, I don't really feel like going through a PDF now and try to figure it out (and test it) myself.
Lefteous wrote:2Loc2262What do you think about my approach (used in Shelldetails) to save the INI file in a well chosen default path.
Thanks for your idea, I've implemented it precisely in that way now. Also with a built-in function to move the ini file to one of the available locations.
2Loc2262
One problem: what happens if tcburner.ini is not writeable (no rights)? I suppose thats my problem: if I want to use tcburner as normal XP-user it blocks TC for some seconds and after that it closes TC.
The doorstep to the temple of wisdom is a knowledge of our own ignorance. Benjamin Franklin
nevidimka wrote:One problem: what happens if tcburner.ini is not writeable (no rights)?
The default location for new ini files will be the same directory where your wincmd.ini is located in 0.9.3. That directory should always be writable for you, otherwise TC itself couldn't write its config file.
From there, you can move the config file to any of the aforementioned four places; the move will only be performed if your access rights suffice.
I have had problems installing (using the old way) the plugin on a restricted user account.
Some error message samples:
---------------------------
TOTALCMD.EXE - Fehler in Anwendung
---------------------------
Die Ausnahme "Unbekannter Softwarefehler" (0x0eedfade) ist in der Anwendung an der Stelle 0x77e538b2 aufgetreten.
---------------------------
TOTALCMD.EXE - Fehler in Anwendung
---------------------------
Die Anweisung in "0x03242e2c" verweist auf Speicher in "0x0331d034". Der Vorgang
"read" konnte nicht auf dem Speicher durchgeführt werden.
---------------------------
TOTALCMD.EXE - Fehler in Anwendung
---------------------------
Die Anweisung in "0x03287c19" verweist auf Speicher in "0x033118e8". Der Vorgang
"read" konnte nicht auf dem Speicher durchgeführt werden.
---------------------------
TOTALCMD.EXE - Fehler in Anwendung
---------------------------
Die Anweisung in "0x77f4b2ab" verweist auf Speicher in "0x03310b90". Der Vorgang
"read" konnte nicht auf dem Speicher durchgeführt werden.
---------------------------
Error
---------------------------
Runtime error 216 at 0000B2AB
---------------------------
OK
---------------------------
2Loc2262
OK looking at the debug log it seems the program tries to write the INI file into the plugin directory which doesn't work and then crashes.
It doesn't matter if the file exist or not.