OPLx wrote on 2020-04-11, 14:22:

Dual SN76489 is supported on Game Blaster or the TexElec SAAYM though.

well, i gathered some information about SAAYM. i found it's two SAA1099 on SAAYM instead of two sn76489 and i didn't find any information about Game Blaster. so, which sound card support dual sn76489 and do you have any resource about these cards? i'm tring to integrate these cards on my board such as AdLib which i have got schematic diagram of RadLib.

by the way, i didn't notice the frequency of clock which is driving the chip is from a fourfold frequency divider, so my clk freq is 14.31MHz / 3 = 4.77MHz

黄禄轩 wrote on 2020-05-15, 12:42:

OPLx wrote on 2020-04-11, 14:22:

Dual SN76489 is supported on Game Blaster or the TexElec SAAYM though.

well, i gathered some information about SAAYM. i found it's two SAA1099 on SAAYM instead of two sn76489 and i didn't find any information about Game Blaster. so, which sound card support dual sn76489 and do you have any resource about these cards? i'm tring to integrate these cards on my board such as AdLib which i have got schematic diagram of RadLib.

I apologize for the misunderstanding. What I meant was that dual SN76489 VGMs can be played back on the Game Blaster or TexElec SAAYM since SBVGM does some internal translation of the VGM data. To my knowledge, there are not (yet) any dual SN76489 sound cards for the PC. Though these days it's possible to have two SN76489 sound cards in one machine. @matze79 also seemed to suggest that such a sound card could easily be made. Since we last spoke, I have been thinking of a way to enable SBVGM to support multiple sound chips of the same family. Since things are a bit busy right now, it may take some time before such a version is ready.

黄禄轩 wrote:

by the way, i didn't notice the frequency of clock which is driving the chip is from a fourfold frequency divider, so my clk freq is 14.31MHz / 3 = 4.77MHz

That makes sense why the frequency of the sounds in the video sounded slightly different from the original VGM data.

Hi,
Just received my TexElec SAAYM and did some testing with YM2151 tunes in my old 386. It's working great !
Is there anyway, maybe in future, to combine the SAAYM with a simple SoundBlaster in order to play both YM2151 and PCM parts (many YM2151 tunes uses SegaPCM/OKIM6295 for the PCM parts) ?

Thanks anyway for your sbvgm tool and yout hardwork!

DjLc wrote on 2020-05-17, 16:26:

Hi, Just received my TexElec SAAYM and did some testing with YM2151 tunes in my old 386. It's working great ! Is there anyway, […]
Show full quote

Hi,
Just received my TexElec SAAYM and did some testing with YM2151 tunes in my old 386. It's working great !
Is there anyway, maybe in future, to combine the SAAYM with a simple SoundBlaster in order to play both YM2151 and PCM parts (many YM2151 tunes uses SegaPCM/OKIM6295 for the PCM parts) ?

Thanks anyway for your sbvgm tool and yout hardwork!

Thank you for the kind comments! I'm glad the program is working well for you. I have considered adding in PCM support, but that would mean that PCM support would only exist on 386 (and higher) class machines because of the amount of memory the extra sample data may require and CPU time that would be needed to decode the SegaPCM format (I think it's ADPCM based) and also mix the channels. It's definitely not out of the question, but may just take some time.

Thanks for your answer, i'm glad to hear that's not impossible.

DjLc wrote on 2020-05-18, 07:11:

Thanks for your answer, i'm glad to hear that's not impossible.

You're welcome! I did forget to mention that the current version (v1.30) is capable of playing back Sega MegaDrive VGMs. While there are some similarities, some VGMs won't sound 100% the same because the YM2151 lacks a DAC, has different LFO timings, and effective frequency range is different from that of the YM2612.

OPLx wrote on 2020-05-17, 21:26:

I have considered adding in PCM support, but that would mean that PCM support would only exist on 386 (and higher) class machines because of the amount of memory the extra sample data may require and CPU time that would be needed to decode the SegaPCM format (I think it's ADPCM based) and also mix the channels.

well, it will be wonderful if you try to implement it on 8086 even if it may have to pause to load and decode.

黄禄轩 wrote on 2020-05-18, 16:29:

OPLx wrote on 2020-05-17, 21:26:

I have considered adding in PCM support, but that would mean that PCM support would only exist on 386 (and higher) class machines because of the amount of memory the extra sample data may require and CPU time that would be needed to decode the SegaPCM format (I think it's ADPCM based) and also mix the channels.

well, it will be wonderful if you try to implement it on 8086 even if it may have to pause to load and decode.

On a sufficiently fast 8086 machine some form of PCM support should be feasible. One issue is since the VGM data is processed in real-time there is a lot of CPU time spent on that which may leave little CPU time for PCM playback. It will be a lot easier to support the OKIM6295 since it is only 4-channel mono ADPCM as opposed to SegaPCM which I believe can be up to 16-channel stereo.

recently i'm working on integrating both 2xSN76489AN, AdLib, SAAYM and a YMF262 (the base io address of both of them can be programmed by software to anywhere maybe from 0x0000 to 0xFFFF) onto my board. and can you tell me how the program check whether YMF262 exists so i can make it compatible.

黄禄轩 wrote on 2020-06-04, 16:41:

recently i'm working on integrating both 2xSN76489AN, AdLib, SAAYM and a YMF262 (the base io address of both of them can be programmed by software to anywhere maybe from 0x0000 to 0xFFFF) onto my board. and can you tell me how the program check whether YMF262 exists so i can make it compatible.

Hello, I used the method described here: Appendix B - Detection Methods.

OPLx wrote on 2018-11-28, 13:22:

Aaaah! I remember now; we were talking about this last year. The VGMs in that the screenshot you kindly provided support the S […]
Show full quote

dr.zeissler wrote:

https://www.flickr.com/photos/94839221@N05/37 … 57687526598300/

Aaaah! I remember now; we were talking about this last year. The VGMs in that the screenshot you kindly provided support the SN76489 chip which is 3 square wave and one noise channel. SBVGM will playback SN76489 data on either actual hardware (like the Tandy 1000) or on the earlier Sound Blaster 1.x & 2.0 series because they support the C/MS option.

Unfortunately the source code and PDFs that you kindly provided don't contain any information about the nature of ESFM in "native" mode. SBVGM currently doesn't have support for SN76489 playback on OPL3. If I ever get time, it is something I could possibly look into, but I currently am not sure how to adequately simulate the SN76489 noise channels on the OPL3; it will likely not sound the same.

From the screenshot it does look like SBVGM works and you should be able to hear VGM playback for VGM data for Zeliard and Cybersphere for example. I hope you are able to use the program for any VGM files that have OPL2 or OPL3 data in them.

Thank you. Is there any chance for getting the old ISA-ES1688 to work with OPLx?
https://stason.org/TULARC/pc/sound-cards-mult … ard-CINAAC.html

dr.zeissler wrote on 2020-06-05, 06:20:

OPLx wrote on 2018-11-28, 13:22:

Aaaah! I remember now; we were talking about this last year. The VGMs in that the screenshot you kindly provided support the S […]
Show full quote

dr.zeissler wrote:

https://www.flickr.com/photos/94839221@N05/37 … 57687526598300/

Aaaah! I remember now; we were talking about this last year. The VGMs in that the screenshot you kindly provided support the SN76489 chip which is 3 square wave and one noise channel. SBVGM will playback SN76489 data on either actual hardware (like the Tandy 1000) or on the earlier Sound Blaster 1.x & 2.0 series because they support the C/MS option.

Unfortunately the source code and PDFs that you kindly provided don't contain any information about the nature of ESFM in "native" mode. SBVGM currently doesn't have support for SN76489 playback on OPL3. If I ever get time, it is something I could possibly look into, but I currently am not sure how to adequately simulate the SN76489 noise channels on the OPL3; it will likely not sound the same.

From the screenshot it does look like SBVGM works and you should be able to hear VGM playback for VGM data for Zeliard and Cybersphere for example. I hope you are able to use the program for any VGM files that have OPL2 or OPL3 data in them.

Thank you. Is there any chance for getting the old ISA-ES1688 to work with OPLx?
https://stason.org/TULARC/pc/sound-cards-mult … ard-CINAAC.html

Since I don't own an ISA card with the ES1688, I'm not entirely familiar with the chipset, but it does seem to emulate the OPL3 (at least in DOS mode) so SBVGM will work when playing back any VGMs that support the OPL2 or OPL3. Is your question related to playing back Tandy 1000 (SN76489) VGMs on the OPL3 chipset?

Thx, where can I find VGM's that have OPl2/3 support?

dr.zeissler wrote on 2020-06-05, 14:06:

Thx, where can I find VGM's that have OPl2/3 support?

OPL2:
https://vgmrips.net/packs/chip/ym3812
OPL3:
https://vgmrips.net/packs/chip/ymf262

That REALLY helps!

There are also many files here: OPL Archive (it's mentioned in SBVGM.TXT).

it's quite strange, the program says there's a YMF262 at 388.

but actually it's a YM3812

i think something is wrong but it's playing correctly

debug:
-o388 4
-o389 e0
-i388
06
-o388 2
-o389 ff
-o388 4
-o389 21
-i388
C6
-

now i'm not quite sure does it sound correct. i recorded it and when playback it sounds a little werid. http://b23.tv/av883386261

In what kind of computer? If the computer has no pull-up resistors on the ISA bus, the documented "port 388 returns 06" check will not work correctly.

NewRisingSun wrote on 2020-06-10, 10:05:

In what kind of computer? If the computer has no pull-up resistors on the ISA bus, the documented "port 388 returns 06" check will not work correctly.

although i didn't build any pull up res to the data bus, it shouldn't cause the problem. i tried to use debug.exe to figure out what's wrong, and the result shows that the hardware is correct.

================
debug:
-o388 4
-o389 e0
-i388
06
-o388 2
-o389 ff
-o388 4
-o389 21
-i388
C6
-