First post, by zeromus
- Rank
- Newbie
Unless there are any objections, I shall use this thread to report on and discuss my efforts to promote the adlib dumping scene:
---
current status:
1. substantial adplug modifications to support opl3 core in addition to opl2. situation pending discussion with adplug maintainer. running in winamp plugin. not in cvs.
2. dosbox adlib.cpp bugfixes. dro file format changes; specifications not yet finalized. nothing in cvs.
presently, every game I try plays in adplug identically to dosbox: shadow warrior, doom, descent, warcraft II. dual opl2 mode should be supported, but I haven't actually tried it ^_^ (which games??). further test results are forthcoming.
I can post beta binaries somewhere upon request.
My next step is to make a slicer&dicer gui utility for editing the raw logfiles. I have some curious ideas about ways to make that fun and easy, but if anyone has specific experience in such utilities I would be glad to discuss it.
Things on my mind are:
* id3 tag for dro files? dosbox can write the relevant information directly to the correct spot without having to futz with the tags; but the slicer&dicer utility could export more extensive information; but adplug can't directly use it. The benefit would be: as soon as anyone starts making adlib music archives, they would be filling the tracks with as much information as they have, even if the current plugins can't really use it yet.
* philosophy of compressibility and filesize of dro logfiles. I am pretty sure that the logfiles compress better if you de-interleave the commands and the values. This could be done in dosbox (somewhat inefficiently)--or it could be defined as a separate disk format mode
zeromus