First post, by TheMechanist
- Rank
- Newbie
Hi folks,
the raw opl capture feature is really cool ! The whole dosbox project is really amazing, thanks for it !
Atm I'm trying to develop an adlib core for some demo stuff (i286 code) and now I'm stuck with a DRO v2 files player .. the format is really straight forward so I don't know what I'm doing wrong.
1.) DRO Files play slower compared to e.g. Audacious (Linux) .. the Short/Longdelay is realized through function 0x86 int 0x15, which works pretty reliable.
2.) playing routines crashes without any visible reason coincidentally - sometimes the *same* song is fully played, sometimes it crashes after short time.
3.) "Pure" OPL2 captures contain register information > 127 which seems to point to OPL3 or dual OPL2
4.) DRO Files are quite big - form the technical point of view I guess it's 'cause of redundant instrument information compared to tracker files with instruments section - but here http://nerdlypleasures.blogspot.de/2014/03/ra … ith-dosbox.html is stated "that dro files quite small" .. I've caputured 124 kb for about 1 minute ?!
5.) Does dosbox care about write delays to opl2 address and value registers ? I emulated the suggested 12 & 84 cycles wait with CLC (on real machines 2 cycles per instruction) ..
Will the adlib emulation break if illegal instructions are sent to adlib ?
What are the best conf settings for emulating adlib opl2 ?
Do you have any hints what to take care of if writing playing routines for adlib (emulation) ?
I'm using DOSBox 0.74 from the offical repositories, Linux 32 bit, Ubuntu 16.04 LTS .. maybe it's only a problem with the linux version ?
The same code runs fine with PCem v12 - no matter if I'm using Ami286 clone 6 MHz or Pentium Overdrive 83 MHz ..
Greetz
TheMechanist