Show Posts
|
|
Pages: [1] 2 3 ... 45
|
|
6
|
GENERAL DISCUSSION / Everything Sierra / Re: King'ssssss Quest V, MPC Edition
|
on: February 16, 2013, 05:32:12 AM
|
Were there multiple versions of the blue MPC CD-ROM version?
I can't claim to be a hardcore Sierra collector or anything, but it does look like there were at least two versions. I imagine the version with the glittery box and MPC-label (as in my photo above) was both early and short-lived, given some of the file dates, and the references to Windows 3.0, which was succeeded by Windows 3.1 just a few months later. Here are some additional audio sample comparisons. I'm a bit conflicted as to which I prefer, and think some combination of the two would be ultimately preferable. In the cases of pronounced sibilance, as with the Weeping Willow song, the filtering is welcome, but in many others (as the following examples show), the audio quality was needlessly compromised. http://www.symphoniae.com/misc/KQ5CD/Audio5001_0.wavhttp://www.symphoniae.com/misc/KQ5CD/Audio5001_1.wavhttp://www.symphoniae.com/misc/KQ5CD/Audio5083_0.wavhttp://www.symphoniae.com/misc/KQ5CD/Audio5083_1.wavhttp://www.symphoniae.com/misc/KQ5CD/Audio7053_0.wavhttp://www.symphoniae.com/misc/KQ5CD/Audio7053_1.wavhttp://www.symphoniae.com/misc/KQ5CD/Audio10109_0.wavhttp://www.symphoniae.com/misc/KQ5CD/Audio10109_1.wavhttp://www.symphoniae.com/misc/KQ5CD/Audio10113_0.wavhttp://www.symphoniae.com/misc/KQ5CD/Audio10113_1.wavhttp://www.symphoniae.com/misc/KQ5CD/Audio10121_0.wavhttp://www.symphoniae.com/misc/KQ5CD/Audio10121_1.wavThere's an AUDCOMPU.DRV driver for use with the CompuAdd Multimedia card on the original release, if anyone cares about such things. 
|
|
|
|
|
7
|
GENERAL DISCUSSION / Everything Sierra / Re: King'ssssss Quest V, MPC Edition
|
on: February 13, 2013, 11:43:24 PM
|
|
Frequency spectrums tend to paint a more comprehensive picture (I'm going to be lame and not post pictures), but it looks like pretty standard low-pass, "EQ" filtration of the high-end. (In addition to the amplification your waveform diagrams show for the newer version.)
|
|
|
|
|
8
|
GENERAL DISCUSSION / Everything Sierra / King'ssssss Quest V, MPC Edition
|
on: February 13, 2013, 08:14:50 PM
|
 I recently found a copy of King's Quest V MPC at a thrift shop, the likes of which I've not seen before (having both the textured/glittery box and an MPC-logo-bearing requirements label). I imagine this is the original CD-ROM release. Compared to the version that I have as part of the 15th Anniversary Collection, the audio files are noticeably different... MPC edition: AUDIO001.002, 114MB, 12/12/1991 15th Anniversary edition: AUDIO001.002, 92.6MB, 04/17/1992 While the size discrepancy seems mostly due to unexplained file duplicates, and a number of audio samples are altered besides, the biggest difference is that the audio samples themselves have gone through a filtering process between the two versions. Here is an example from each version demonstrating the difference: http://www.symphoniae.com/misc/KQ5CD/Audio9999_0.wavhttp://www.symphoniae.com/misc/KQ5CD/Audio9999_1.wav
|
|
|
|
|
9
|
MUSIC & SOUND CARDS / Miscellaneous MIDI & Sound Cards / Re: E-MU SoundEngine Music Module not in stereo?
|
on: February 12, 2013, 02:15:52 AM
|
|
It doesn't seem like normal behavior, based on the manual and MIDI implementation. Have you tried hard left/right panning, and are the rear outputs and headphone jack similarly affected?
It's nice to finally see the inside of one of these things. I definitely wasn't expecting a different SoundEngine board. (Creative's "Wave Blaster," as you're probably aware, is an OEM version of E-MU's earlier, EMU8801 SoundEngine board.)
|
|
|
|
|
10
|
MUSIC & SOUND CARDS / Roland Sound Canvas/Yamaha XG / Re: Hidden/Lesser-documented GS SysEx
|
on: January 21, 2013, 12:50:14 AM
|
Other than the "Test Mode" information, everything is documented in various owner's manuals. I've not seen the "WAVE ROM" check in anything other than the Japanese E-70 manual, however... http://lib.roland.co.jp/support/jp/manuals/res/1809514/E-70_jei.pdfhttp://media.rolandus.com/manuals/SCC-1_OM.pdfThe "Test Mode" stuff is still mostly derived at this point. I'd questioned Roland Japan about it recently, and was simply told that it's for internal use only. How nice. Notwithstanding, it is briefly mentioned in the two MIDI implementations noted below, and the specific "WORK RAM" test comes from the CM-300/500 Service Notes. Everything else I'd posted regarding the Test Mode was the result of poking around with SysEx using the CM-500, and comparing the audible results to the panel-initiated tests described in the SC-55mkII Service Notes. While I'm pretty comfortable with the Sound Test descriptions used, "EXIT TEST MODE" may not be the most accurate description of the first entry, as it's more of a reset, and perhaps more closely comparable to a "factory reset" at that. http://lib.roland.co.jp/support/jp/manuals/res/1809347/MT-200_IMPL_j.pdfhttp://lib.roland.co.jp/support/jp/manuals/res/1809388/FG-10_-1000_IMPL_j.pdfHere are my notes on some of the remaining unknowns. Size bytes don't actually seem to be required. F0 41 10 42 11 4F 41 00 00 00 01 6F F7 Sends everything from MIDI IN to MIDI OUT? F0 41 10 42 11 4F 42 00 00 00 01 6E F7 Reset/ Followed by no MIDI response? F0 41 10 42 11 4F 43 00 00 00 01 6D F7 Reset/ Followed by no MIDI response? F0 41 10 42 11 4F 44 00 00 00 01 6C F7 Reset/ Followed by no MIDI response? F0 41 10 42 11 4F 45 00 00 00 01 6B F7 Reset/ Followed by no MIDI response? F0 41 10 42 11 4F 46 00 00 00 01 6A F7 Reset/ Followed by no MIDI response? F0 41 10 42 11 4F 47 00 00 00 01 69 F7 Reset/ Followed by no MIDI response? F0 41 10 42 11 4F 48 00 00 00 01 68 F7 Increments Checksum by 1 + size bytes (Part 1?) F0 41 10 42 11 4F 48 01 00 00 01 67 F7 Increments Checksum by 1 + size bytes F0 41 10 42 11 4F 48 02 00 00 01 66 F7 Increments Checksum by 1 + size bytes F0 41 10 42 11 4F 48 03 00 00 01 65 F7 Increments Checksum by 1 + size bytes F0 41 10 42 11 4F 48 04 00 00 01 64 F7 Increments Checksum by 1 + size bytes F0 41 10 42 11 4F 48 05 00 00 01 63 F7 Increments Checksum by 1 + size bytes F0 41 10 42 11 4F 48 06 00 00 01 62 F7 Increments Checksum by 1 + size bytes F0 41 10 42 11 4F 48 07 00 00 01 61 F7 Increments Checksum by 1 + size bytes F0 41 10 42 11 4F 48 08 00 00 01 60 F7 Increments Checksum by 1 + size bytes F0 41 10 42 11 4F 48 09 00 00 01 5F F7 Increments Checksum by 1 + size bytes F0 41 10 42 11 4F 48 0A 00 00 01 5E F7 Increments Checksum by 1 + size bytes F0 41 10 42 11 4F 48 0B 00 00 01 5D F7 Increments Checksum by 1 + size bytes F0 41 10 42 11 4F 48 0C 00 00 01 5C F7 Increments Checksum by 1 + size bytes F0 41 10 42 11 4F 48 0D 00 00 01 5B F7 Increments Checksum by 1 + size bytes F0 41 10 42 11 4F 48 0E 00 00 01 5A F7 Increments Checksum by 1 + size bytes F0 41 10 42 11 4F 48 0F 00 00 01 59 F7 Increments Checksum by 1 + size bytes (Part 16?) F0 41 10 42 11 4F 48 10 00 00 01 58 F7 Infinite repeat? F0 41 10 42 11 4F 4C 00 00 00 01 64 F7 01 (unknown) F0 41 10 42 11 4F 4D 00 00 00 01 63 F7 01 (unknown) F0 41 10 42 11 4F 4F 00 00 00 01 61 F7 00 (unknown)
|
|
|
|
|
11
|
MUSIC & SOUND CARDS / Roland Sound Canvas/Yamaha XG / Hidden/Lesser-documented GS SysEx
|
on: January 19, 2013, 11:35:44 PM
|
|
Here's a collection of less-common (and in the case of the "Test Mode," non-publicly documented) GS SysEx. There happens to be much more to the Test Mode than I've listed below, with regard to MIDI channel testing and such, but since I haven't conclusively determined the functions/responses, I've left those portions out.
And if anyone happens to know what the heck "ASSIGNER SEPARATE WALL" even means, do share.
[MODEL: 42H]
[SYSTEM PARAMETERS]
Address(H) Size(H) Data(H) Parameter Description =========================================================================================================
40 00 7E 00 00 01 00 - 7F LGC CONTROLLER NUMBER 0 - 127 (default=54)
[PATCH PARAMETERS]
Address(H) Size(H) Data(H) Parameter Description =========================================================================================================
40 01 20 00 00 01 00 - 0F ASSIGNER 0 - 15 SEPARATE WALL (top part number of the wall)
[INFORMATION] ----- RQ1 Only -----
*r: ROM number (0 - 2)
Address(H) Size(H) Data(H) Parameter Description =========================================================================================================
40 30 00 00 00 20 20 - 7F SYSTEM INFORMATION ASCII Character : # ex. "GS Standard VER=1.11" : # : # 40 30 1F#
40 3r 20 00 00 20 20 - 7f WAVE ROM INFORMATION ASCII Character : # ex. "0 VER120 1991-01-11 8" : # : # 40 3r 3F#
[TEST MODE] ----- RQ1 Only -----
00: Fail, 01: Pass
Address(H) Size(H) Data(H) Parameter Description =========================================================================================================
4F 40 00 00 00 01 00 - 01 EXIT TEST MODE
4F 49 00 00 00 01 00 - 01 EFFECT TEST 1 DLY - SINE WAVE 4F 49 01 00 00 01 00 - 01 EFFECT TEST 2 S&D - SINE WAVE, 1SEC.
4F 4A 00 00 00 01 00 - 01 EFFECT TEST 3 CHO 4F 4A 01 00 00 01 00 - 01 EFFECT TEST 4 RV1 - SNARE W/REVERB 4F 4A 02 00 00 01 00 - 01 EFFECT TEST 5 RV2 - SNARE W/PANNING REVERB
4F 4B 00 00 00 01 00 - 01 SOUND TEST VOICE 1 SINE WAVE, CENTER BALANCE 4F 4B 01 00 00 01 00 - 01 SOUND TEST VOICE 2 : 4F 4B 02 00 00 01 00 - 01 SOUND TEST VOICE 3 : 4F 4B 03 00 00 01 00 - 01 SOUND TEST VOICE 4 : 4F 4B 04 00 00 01 00 - 01 SOUND TEST VOICE 5 : 4F 4B 05 00 00 01 00 - 01 SOUND TEST VOICE 6 : 4F 4B 06 00 00 01 00 - 01 SOUND TEST VOICE 7 : 4F 4B 07 00 00 01 00 - 01 SOUND TEST VOICE 8 : 4F 4B 08 00 00 01 00 - 01 SOUND TEST VOICE 9 : 4F 4B 09 00 00 01 00 - 01 SOUND TEST VOICE 10 : 4F 4B 0A 00 00 01 00 - 01 SOUND TEST VOICE 11 : 4F 4B 0B 00 00 01 00 - 01 SOUND TEST VOICE 12 : 4F 4B 0C 00 00 01 00 - 01 SOUND TEST VOICE 13 : 4F 4B 0D 00 00 01 00 - 01 SOUND TEST VOICE 14 : 4F 4B 0E 00 00 01 00 - 01 SOUND TEST VOICE 15 : 4F 4B 0F 00 00 01 00 - 01 SOUND TEST VOICE 16 : 4F 4B 10 00 00 01 00 - 01 SOUND TEST VOICE 17 : 4F 4B 11 00 00 01 00 - 01 SOUND TEST VOICE 18 : 4F 4B 12 00 00 01 00 - 01 SOUND TEST VOICE 19 : 4F 4B 13 00 00 01 00 - 01 SOUND TEST VOICE 20 : 4F 4B 14 00 00 01 00 - 01 SOUND TEST VOICE 21 : 4F 4B 15 00 00 01 00 - 01 SOUND TEST VOICE 22 : 4F 4B 16 00 00 01 00 - 01 SOUND TEST VOICE 23 : 4F 4B 17 00 00 01 00 - 01 SOUND TEST VOICE 24 :
4F 4E 00 00 00 01 00 - 01 WORK RAM CHECK
|
|
|
|
|
13
|
MUSIC & SOUND CARDS / Roland MT-32 Sound Module / Re: Working on a MT-32 guide / FAQ - Compiling topic list
|
on: December 20, 2012, 05:00:46 PM
|
Someone interested in using the MT-32 for gaming might find a guide detailing its use with newer systems/software/interfaces useful, but may not have a lot of use for hardware technicalities. From a technical standpoint, most of the relevant topics are already detailed in other publications (Wikipedia, owner's manuals, service notes). A few of the topics seem arbitrary (Power-draw comparison? Number of PCBs?), and I'd leave out any sort of personal recommendation. How do you check the ROM version on a CM unit? I remember you had to send information to the MIDI module and it would respond with the ROM version. http://queststudios.com/smf/index.php/topic,1654.msg30306.html#msg30306MIDI-OX can be used for this.
|
|
|
|
|
14
|
GENERAL DISCUSSION / Anything & Everything / Re: Leisure Suit Larry 3 soundtrack (featuring Roland INTEGRA-7)
|
on: December 18, 2012, 10:11:34 PM
|
|
The 16-part limitation may coincide with the effect-processor's 16 separate and concurrent MFX. When compared to, say, the XV-5080, where 3 MFX are shared amongst 32 parts, the trade-off of not having to effect-juggle seems pretty well justified.
I can't imagine what technical limitation (if there even was one) might have resulted in the 128-voice polyphony. It certainly seems like a poor decision, whatever the case may be.
|
|
|
|
|
17
|
MUSIC & SOUND CARDS / Roland MT-32 Sound Module / Re: A question about MT-32 drums
|
on: December 10, 2012, 03:27:00 AM
|
On the other hand, when talking about flexibility I'm simply referring to the fact that there's not a strict distinction between "instrument" patches and "drum" patches given the architecture of the MT-32.
Which is, of course, the same architecture shared by the baby-D synths...  I may have overlooked something, but I couldn't see any difference in the MT-32's handling of timbre selection, as compared to the D-series synths. Thank-you for starting this topic, by-the-way. The MT-32 doesn't seem to get much recognition for being as innovative as it was - its rhythm capabilities being another excellent example.
|
|
|
|
|
18
|
MUSIC & SOUND CARDS / Roland MT-32 Sound Module / Re: A question about MT-32 drums
|
on: December 09, 2012, 01:57:37 AM
|
As Datschge pointed out, Roland's drum machines were basically either analog synthesizers or straight sample players prior to the MT-32, which leverages the LA chip to reduce the number of required PCM waveforms for a drumset through approximation (pitch-shifting, synth waveform generation, etc.). The MT-32 drumset really was another "Roland first" in this regard, despite my presumption that it was more of a cost-cutting measure than anything else. Take a look at the "Quijada." This instrument is a 32K waveform sample in the TR-727, but is approximated by a corresponding timbre in the MT-32 that utilizes the looping Rim Shot and Hand Clap samples.  There's a lot of shared PCM commonality between Roland's TR/CR units. Based on names/dates/sizes, it seems to me that the MT-32 shares waveforms with the TR-505/CR-1000 and TR-727, while the later D-10/110/20 synths appear to draw from both the TR-727 and the larger waveforms in the TR-626. I'm a bit surprised you find the MT-32 drumset to be superior, frankly, and what's this about the MT-32 being more flexible? At the time, the rhythm section found in the D-10/110/20 was technically superior to contemporary Roland offerings. Is it the waveforms that you're comparing, or the timbre/tone programming (which also drastically differs)?
|
|
|
|
|
19
|
MUSIC & SOUND CARDS / Miscellaneous MIDI & Sound Cards / Re: Innovation SSI-2001
|
on: November 28, 2012, 08:48:03 PM
|
|
Yep, just a raw SID and simple joystick port - no MIDI capabilities whatsoever. While the music does have to be specifically programmed/converted for the SID, the idea was that developers would have been able to (more) easily port wares from the Commodore 64 to the PC. The premise was nice, but the Innovation board was released as the larger U.S. companies were ending C64 development, and was presumably an immediate marketplace failure.
|
|
|
|
|