|
Subject:Problems with XG Midi using QS300
Posted by: devolution
Date:2/21/2003 2:20:28 PM
I am trying to get a MIDI file to playback in Acid as part of a song, but Acid doesn't seem able to send the correct bank change codes to select the QS300 sounds that the MIDI file uses. I can get the channels assigned correctly, but only manually by opening the MIDI Track dialog and changing the bank and program number in mid-stream while the project is playing. This is ridiculous. It obviously isn't sending the correct channel change/bank select messages at the start. Any workarounds? |
|
Subject:RE: Problems with XG Midi using QS300
Reply by: Iacobus
Date:2/21/2003 3:28:54 PM
Mmm. I'm having a problem sending MIDI CC messages to my guitar effects processor as well. Seems to send the first message in the list OK but subsequent commands are not executed. I'm giving SoFo an email buzz. You should too. Iacobus |
|
Subject:RE: Problems with XG Midi using QS300
Reply by: SonyNateM
Date:2/21/2003 3:32:06 PM
Once you add the MIDI file to your ACID project and set the channels as you wish (on the General page of the Track Properties window for the MIDI track, they should stick with save/reload of the ACID project. As for your bank/program/patch changes, have you inserted the proper changes at the beginning of the MIDI file? If these changes work when you make them during playback, a permanent insertion at the beginning of the MIDI file should change them properly. What channel(s) are they on? At what time? etc? Also, if you are inserting your changes at 1.1.000 in the MIDI file, do you actually have that portion of the file painted onto the ACID timeline, or have you trimmed it off and are only using a clip from the middle? Nate |
|
Subject:RE: Problems with XG Midi using QS300
Reply by: Iacobus
Date:2/21/2003 7:39:42 PM
Hmmm. OK, I'm making progress. I seem to be able to execute a list of CC commands except for the very last CC command, which sometimes executes and sometimes doesn't. For example, I set the stompbox on my guitar processor to shut off at 2.1.000 via MIDI CC number 84 and then turn back on at 3.1.000. I use the standard MIDI CC commands for toggling on (127) and off (0). If I change commands via different combinations of channels, I get the same results. Everything works fine until that last CC command in the list. It sometimes works and sometimes doesn't. Most of the time it does. (This is with the entire MIDI event painted on the timeline.) I've noticed too that if I add channels to the MIDI track, save the properties and then close and reopen, track names and assigned channels are not saved. Example: Each separate track is assigned channels 1, 2, 3, 4, 5. They become 1, 1, 3, 1, 1 respectively, all with the track name, "New MIDI Track". Will keep at this... Iacobus |