sys err messages on the tr rack
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
sys err messages on the tr rack
when i am in the middle of programming the tr rack i will get a message that says "SYS ERR[EC:00000002]#3 +0 +0"
or a sys err message with weird characters that varies
when i change the p/c select rate from 31.25kBPS to 38.4kBPS it will still crash with the sys err message
is there something i'm missing in the settings of the tr rack?
Thanks
or a sys err message with weird characters that varies
when i change the p/c select rate from 31.25kBPS to 38.4kBPS it will still crash with the sys err message
is there something i'm missing in the settings of the tr rack?
Thanks
midiquest
Hi skyler
Now I have the sysex for the TR-Rack I will be spending time going into the midiquest 10 editor and checking the code. Did you get the error doing anything in particular: Combi, program, parameter change etc.
I use midi cables to connect to my old XP PC, which has a cheap PCI sound card with a gameport (serial to midi cable cheap as chips) rather than the other connections on the back of the TR-Rack.
MQ has some useful ways of seeing the data in and out of the unit. Chances are the sysex transmission did not get there fully, or the format is wrong. The editor is designed to work with the whole family (kit that has the same sysex) and then because some kit can have expansion boards/do extra than others, this where the problems arise. I strip it all out, and just leave the code for the bit of kit I have.
Will keep you posted.
Regards
ProfPlat
Now I have the sysex for the TR-Rack I will be spending time going into the midiquest 10 editor and checking the code. Did you get the error doing anything in particular: Combi, program, parameter change etc.
I use midi cables to connect to my old XP PC, which has a cheap PCI sound card with a gameport (serial to midi cable cheap as chips) rather than the other connections on the back of the TR-Rack.
MQ has some useful ways of seeing the data in and out of the unit. Chances are the sysex transmission did not get there fully, or the format is wrong. The editor is designed to work with the whole family (kit that has the same sysex) and then because some kit can have expansion boards/do extra than others, this where the problems arise. I strip it all out, and just leave the code for the bit of kit I have.
Will keep you posted.
Regards
ProfPlat
hi profplat
i got the error when i was editing the regular program
i havent gotten into the combis yet
wow you are using the old game port to midi cable adaptor:-) i remember that way of connecting stuff
i am planning on using sound diver once i get my xp up and running again
i tried to install xp on a partition and didnt work well
i have an old computer laying around i might use that. i really want to do it all on one machine instead of two. i just wish sound diver worked on w7
midi quest is kind of slow but its ok
i got the error when i was editing the regular program
i havent gotten into the combis yet
wow you are using the old game port to midi cable adaptor:-) i remember that way of connecting stuff
i am planning on using sound diver once i get my xp up and running again
i tried to install xp on a partition and didnt work well
i have an old computer laying around i might use that. i really want to do it all on one machine instead of two. i just wish sound diver worked on w7

midi quest is kind of slow but its ok