Set channel properties for Sound resources in Companion?

[Kawa]

I'll have to look again when I'm back on my laptop instead of my phone but I think you might be on to something, Doomie.

[doomlazer]

Yes, I think it might be confirmed. Further changing channel 1 (0) from 0 IVs to 1 increments the second byte.

Code: [Select]

0x0000  00 01 FF 03 FF 00...

[MusicallyInspired]

I've already worked this out with Ravi's writeup on the ScummVM SCI wiki (Kawa referenced earlier). All the answers are there. It's the SCI1.0 sound resource format I'm not sure of. I know what to change for SCI0 sound resources I just couldn't edit the Companion source. (also, I don't fully know how to implement setting byte values in a binary file within the GUI realm)

[Kawa]

Back on the laptop, will study Doomie's findings later.

The thing about Ravi's writeup is that at least the part I referenced doesn't match my hypothesis:

The upper 4 bits of that byte specify how many voices each logical MIDI channel will be playing. The lower 4 bits specify which drivers should react on that channel. Bit 0 set means AdLib shall react. Bit 1 set means PCjr shall react. MT32 will react on all channels. Bit 3 signals the control channel.

Not only does that imply AdLib's channelMask is 0x01 (it's 0x04) but I wasn't aware the PCJr was able to run SCI so that's something I'd prefer to take heavily salted.

[Kawa]

Having looked closely at Doomie's data, there's one thing I'd like to confirm first: what devices are those two channels set to play on?

[MusicallyInspired]

Back on the laptop, will study Doomie's findings later.

The thing about Ravi's writeup is that at least the part I referenced doesn't match my hypothesis:

The upper 4 bits of that byte specify how many voices each logical MIDI channel will be playing. The lower 4 bits specify which drivers should react on that channel. Bit 0 set means AdLib shall react. Bit 1 set means PCjr shall react. MT32 will react on all channels. Bit 3 signals the control channel.

Not only does that imply AdLib's channelMask is 0x01 (it's 0x04) but I wasn't aware the PCJr was able to run SCI so that's something I'd prefer to take heavily salted.

He's referring to Tandy 3-voice as Tandy and IBM PCjr share the same sound chip (as does the Sega Master System and the Game Gear). Ravi wrote SoundBox which works as you'd expect so no salt needed here.

[Kawa]

Good, good. Thanks for clearing that up cos I don't like my meals too salty.

[doomlazer]

Having looked closely at Doomie's data, there's one thing I'd like to confirm first: what devices are those two channels set to play on?

I had all devices enabled on channels 0 and 1. (initial voices chan0: 1 chan1: 3)

Code: [Select]

0x0000  00 01 FF 03 FF 00 00...
Disabling Adlib on chan1, with no other changes alters the 5th byte

Code: [Select]

0x0000  00 01 FF 03 FB 00 00...
So the Initial voices word comes before the device types I guess and there is 00 at the start.

Edit: Just an observation, but that was with a SCI0 patch altered in Soundbox. I can replicate the same results for SCI0 patches right in SC by disabling Adlib for chan1.

In SCI1, If I try disabling Adlib in a random PQ3 sound patch within SCICompanion, the header is drastically different. In the attached pic the left is with Adlib disabled on chan2 and enabled on the right.

[Kawa]

I had all devices enabled on channels 0 and 1. (initial voices chan0: 1 chan1: 3)

Code: [Select]

0x0000  00 01 FF 03 FF 00 00...
Disabling Adlib on chan1, with no other changes alters the 5th byte

Code: [Select]

0x0000  00 01 FF 03 FB 00 00...

All devices enabled would be 0xFF. "And Not" AdLib (4) would be 0xFB. So that makes some sense... guess I'll have to experiment with implementing this now.