Viewing Issue Advanced Details
|ID||Category [?]||Severity [?]||Reproducibility||Date Submitted||Last Update|
|07103||Documentation||Minor||Always||Sep 21, 2018, 17:18||Aug 20, 2020, 20:10|
|Tester||vidpro1||View Status||Public||Platform||MAME (Official Binary)|
|Assigned To||aaron||Resolution||Fixed||OS||Windows 10 (64-bit)|
|Version||0.200||Fixed in Version||0.224||Build||64-bit|
|Fixed in Git Commit||Github Pull Request #|
|Summary||07103: tacscan: Tac-Scan Sega Universal Sound Board Emulation|
The source code is segasnd.c. I have an idea why the driver is still marked imperfectly.
In Tac-Scan after all these years I've figured out that the ship roar being too loud is most likely the reason the enemy ship explosions and sounds are being drowned out. On older versions of MAME you could press the "~" key and control the specific voices of each sound chip. For example AY-3-8910 voice generator you can control channels A, B, and C. (just an example Sega G80 doesn't use this)
I do not think this feature works anymore unless I have missed something. If the emulator has independent volume control of all the voices/channels in the OSD I believe the sound channel drowning out problem could be fixed. It might not even be a problem with the game driver at all other than all channels are mixing all the sound board sounds at full volume where that is not the case on a real machine. In 1999 I made samples for Tac- Scan before the Sega G80 Universal sound board was actually emulated, there are still notes in there about that.
If you watch TNT Amusements youtube video you will hear what I am talking about.
|Steps To Reproduce|
|Affected Sets / Systems||tacscan|
|There are no relationship linked to this issue.|
Sep 22, 2018, 02:40
Volumes of sound chips/sources are still a slider command, but you access via TAB menu. Some cases where you may need to adjust clock speeds, you need to run -cheat. In tacscan's case, it does indeed seem to be capsulated into one device with a universal volume. Not sure if user adjusted volume will work and may require source code adjusting.
This report isn't something we normally would take. It doesn't note a regression in code and it involves sound balance/proportion issues which, again, are not normally accept as detailed in https://mametesters.org/rules.html You do, however, (haven't viewed it yet) claim to have an original source for comparison so it may be accepted under that guise after someone can look it over.
Aug 20, 2020, 07:42
|Should be fixed in next version.|