Micro! Thanks for the response good to hear from you!
I've been perusing your vids on the utube channel but didn't find the answer to my particularly historical question.
I'll take a look at the link.

I'm recently retired so now getting back into the audio production groove of things.
Man-o-man the RME RayDat was almost the only piece of my rig that is still supported and not obosolete!
No mind.. a few key purchases n' my rig is back and better than ever.

Been doing a deep dive into the AI audio production world.. which is insane..!
N' making me feel the gravitational pull back home to SawStudio.


Thanks again!

Peace

Not sure if this will help, but on my site, there is a link to the old SAWStudio website on the Wayback Machine I found. [url=https://www.learnsawstudio.com/silverwood][B][U]Click Here[/U][/B][/URL]

Hey Gang, long L O N G time no talk to...
I'm no Math Surgeon, but according to the date on this thread, its been something like 13+ years!! :eek: :D

Great that SawStudio is still alive and kicking! It's still my homebase DAW app.


Follow on issue with my Alesis QS6 midi setup that's been kicking my b~tt.
All of the config details above still hold true. All of it is the same and all of it is still working. Program Change messages too.

Program patches are addressed in the .ini file thusly:
<><><
[DEVICE NAME]
"QS6"
;
[BANK FORMAT]
"MSB-ONLY"
;
[OFFSET FORMAT]
"ZERO"
;
[PATCHES]
;BANK PRG NAME GROUPS (Max 8)
;---- --- ---------------------------------------------------------------- --------------
;Bank 0 = Program User Bank
0 000 "ClasclGrnd" 0
0 001 "Pianooohs" 0
0 002 "HousePiano" 0
;etc etc
;Banks are User (0), Preset1(1), Preset2(2), Preset3(3), GenMidi(4)
<><><>

Midi Program Change messages for the "Program" patches are working just fine.

The QS6 also has "Mix" patches and I've been unable to address them via Midi Program Change messages.
My search on the interWebz has only resulted in this bit of info. from an unnamed source.

[B][I]The Alesis QS6 does not use MIDI Bank Select (MSB/LSB) messages to select Mix Banks. Mixes are recalled directly using Program Change messages (0-63). [/I][/B][B][I]User Mix Bank: Send a Program Change message (0-63) to select one of the 64 user mixes.


[/I][/B]Nothing I've tried in the patch.ini file so far, has worked.
As always, any help would be much appreciated.

[quote="tomasino"]

Next I integrate the ControlPad (drum pad trigger doodad). Has it's own USB Midi interface. :confused:

Any tips on how to configure it in with MWS would also be appreciated.

As always, you guys rock. :cool:
Thanks again![/quote]

I got the ControlPad integrated as a standard Midi device and working groovy.

The ControlPad has:

[LIST]
[*]Midi-In
[*]Midi-Out (NOT a Thru!:mad :)
[*]USB Midi
[/LIST]
MWS sees the USB Midi port as the "ControlPad" device (but it's not an instrument.) I could not find a way to activate the Midi-Thru from the ConrolPad USB In port to a RayDat Midi-Out port.
So was able to record midi events, but wasn't triggering the drum module.


The 2nd Midi Port on the RayDat made it real easy.[INDENT][B]ControlPad Midi-Out => RayDat In2
RayDat Out2 => DM5 In
[/B][/INDENT]Done.

If using the USB Midi port is possible in this config, I'm obviously missing something.. please fill me in.

Peace
M

Hey thanks guys.

Looks like I got it. :)
Appears it was wonky "Group Number lists" in the .ini file.
By [I]wonky [/I]I mean they weren't lined up nice and neat anymore post transfer from XP to Win7..
Spacing was OK, but many of 'em were kicked out to the right a Tab or two.
Tidyed that up and [I]Shazaam! [/I]Worky worky.

Got more acquainted with the Routing features of Midi-Ox. Pretty cool.
Checked both midi ports outside of MWS and was able to verify all I/O.

In the process I verified the Midi Ports on the RayDat are NOT Multi-Client. MWS squawked if Midi-Ox was still running and had the ports opened.


Next I integrate the ControlPad (drum pad trigger doodad). Has it's own USB Midi interface. :confused:
Any tips on how to configure it in with MWS would also be appreciated.

As always, you guys rock. :cool:
Thanks again!

The audio interface should not have anything to do with bank changes...

The patch ini info for the QS6 is correct... but also make sure your individual patch list items for bank 1 and 2 etc... have the number 1 and 2 listed as the first number in each line in the ini file... notice the first 128 patches start with the number 0 as the first entry in each line.

Perhaps also check that your QS6 does not have some internal setting adjusted to ignore bank change messages.

Bob L

I cannot be of much help with most of this. But in regards to the MIDI-Ox issue, this might be caused because the RME MIDI ports are not multi-client, where the M Audio ports might have been. I'm not saying this is certainly the cause. I'm just saying that it might be the issue. I don't know for certain if the RME drivers are or are not multi-client or if the M Audio drivers were or were not multi-client.

But if that is the case it might explain it. I'm assuming that you mean you are not able to patch MIDI Ox to the MIDI I/O of the sound card at the same time you're using MWS? If so that might be the issue. If you mean it won't work at all... as in you are only running MIDI Ox and nothing else, then I would take that to mean that there is something wrong either a driver issue or a hardware issue and that the MIDI ports are not working properly. In fact that is probably where I would start first. Run just MIDI-Ox and make sure you can receive and send MIDI data to your keyboard. That way you can be sure the ports are working correctly. Then once you've done that I would go back and work with MWS to figure out what is going wrong some place.

Hope this helps at least a bit..

I've been consolidating my gear. Jettisoned the old (2.5 years) dedicated studio DAW w/M-Audio interface in favor of the SAC/SawStudio Rig w/RayDat interface.
Just makes sense these days.

RTFM'd.. Searched this Forum and the RME Forum.. No love.

So, implementing Midi on the RayDat for the first time.
Everything is working fine except for Bank Program Change Messages.
I can:

[LIST]
[*] record and playback midi no prob.
[*] change program patches (instruments) no prob.
[/LIST]
Just can't change the Program Bank on the Alesis QS6 Synth. It's stuck on Bank 000 no matter what I do.

Here's the header config in the synth.ini file:

[DEVICE NAME]
"Alesis-QS6"
;
[BANK FORMAT]
"MSB-ONLY"
;
[OFFSET FORMAT]
"ZERO"
;

This config worked fine with the M-Audio interface.
MWS Track Properties are displaying all the correct Bank/Patch info. values selected from the Patch Library window. It's all lining up just as it always has.

Attempts to use any other [Bank Format] config ("MSB-LSB" or "ZERO") didn't fix it.. n' worse, causes a reset to Bank 000 upon playback.. which is not functional at all.
Leaving it at "MSB-ONLY" allows me to set the Bank on the synth manually without any Bank changes on playback.

Another odd thing is that I can't seem to monitor the midi port traffic with Midi-Ox.. which I could do all day long with the M-Audio.

Any help would be appreciated.

Thanks
M