I've been trying to get -dev going once I figured out the git syntax, anyways, i'm getting an error while compiling - i'm on slackware, and I suspect it might mean upgrading to a newer version of alsa libs although I thought I was pretty bleedy on that already.
gcc main.c rbkit.c rb1kit.c ghkit.c -o rbdrum2midi -lasound -lusb-1.0
main.c: In function 'setup_alsa':
main.c:323:83: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
if ( verbose >= 0) printf("Error: open_client failed: %s\n", snd_strerror((int)seq));
I am not developery enough to make a project that running aclocal autoconf automake or an autogen.sh and then the configure make etc process or lately frequent lone wscript files with no waf in some projects ... but anyways, I tried the readme instructions, im a bit low on time just wondering if this is some difference in alsalibs between ubuntu (I assume everyone is on debian/ubuntu) and slackware - or what.
This is gregory btw.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
upgraded to a minor point higher in the alsa release pile, it didn't change anything although I dont trust anything these days to update the includes properly (cough lv2) but any hints would be fantastic, I want to give this a try.
Just about to try to get full module signing workign and boot up with a much newer kernel and likely won't have working nvidia thus X for a while and will hit the couch. Tomorrow rain is expected so I will be inside hopefully making a hellish racket since I figured out how to cross compile ardour3 and it looks like carla-git is going to work - except now for some reason jack seems to have stopped passing data in off my capture card. Likely a reboot will help.
Can't wait to have hi hat, so excited.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
still getting nowhere but im also trying to get stupid pam working, I like slackware in large part BECAUSE it doesnt use pam and its various insecurity, I think PAM is next thing to a backdoor but there is a backdoor in the backdoors even these days, Learning the state of affairs of host node security and how insanely simple it is for anything penetrating the host node to just control or manipulate my VPS scares me deeply. root and immutable doesnt mean shit anymore. Welcome to the cloud. The cloud is an example of an intelligence concept that people have only bought into out of the sheer load of advertising,. Sigh. Thats why i'm trying to go cyberluddite and get my music room and go back to thinking about high school emotional stuff to write some music (nothng else seems to work and my muse is gone...sigh) but im encouraging some of my easy to work with great voice / talents band memembers to get practicing even if its an activity with the kid, maybe get my mom to come to look after the kids over a few weekends upstairs (she doesnt live here) and get my singer back into action because she (with a yet to be found backup) was a big personal influence to my sanity and the band is nothing without her even if I am the main producer. I really want to get a 5 song EP published and onto torrent by this time next year, and this time around, fix the biggest regret- no drums on our demo album except a drum machine on the song that everyone automatically likes best,
Close to having ardour with winvst support and also have very low latency settings for reaper and wineasio but right now there is a major midi problem that would be a showstopper without buying a new card or a used 410 card (like I ordered in the first place) because so much jack I take for granted that the asio world doesnt do. Reason is totally a write off to me when it was the first place I learned how to turn modular synth components hooked up to oscilators or LFO or envelopes in strange ways could end up with amazing sounds and now finally its happening for guitar.
Will be going into the weekend with my includes hopefully as good as they should be and hopefully someone can get back to me so I can get the drum middleware compiled and working and im drawing very close to the time when the HTPC and torrent duties of my big new workstation as crippled as it is by a finickly memory socket that wont easily go over 8GB and no money or parts to get it at least up to 32. But I recorded first album with a kawai kc20, a borrowed couple guitars, alesis compressor, a permanently borrowed sb16asp (remember those?) and a little solid state preamp I made out of a written off overdrive boss pedal. And some stellar singers. I would love to have access to the music equipment that floats around that spot now, or access to the young, trained and eager talent dying to get their name on tracks. But now is now and technology is alot better than the P-133 machine I was running samplitude some ancient version and soundforge on likely windows 98. Anyways, getting ready to roll with triple monitors, solid VST's and now LV2's and im going to be getting the best possible hardware and software that no money and slackware running wine heavily modified can handle ... now to find the talent. and, for once, thanks to you guys if I can get this ((#($$* to compile ... I will have drums on the next EP this summer! Sad are the days when you need to arrange babysitting and force practice on your primary talent. I myself am a 36 year old permanent bachelor and children scare me with their inappropriate, deeply honest questions and observations that cut through the veils of bullshit I drape myself with in any kind of social siuation.
End monologue. Thanks both of you!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Wow, you seem to be a lot more knowledgeable than I am on all things unix... I generally tend to walk around with a big stick and hit stuff repeatedly till it works. ;-)
A lot of work has gone into the dev branch recently and I still need to test it on my kits, compilation has always been an issue with this project ... I started it on ubuntu 10.04 and built all the developery stuff and .debs a bit hamfistedly, hence the issues. I'll be setting it all up again soon (hopefully).
Keep us posted and glad you find it useful.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just tested the dev branch from a sf provided snapshot.
I tested it on a ubuntu 12.04 machine, I entered the src diretory and used "gcc main.c rbkit.c rb1kit.c ghkit.c -o rbdrum2midi -lasound -lusb-1.0", this worked without any errors or warnings. Tested the PS3 rb3-pro drumkit and it worked.
alsa-base version 1.0.25 as are the libasound2 and libbasound2-dev pakages.
I'll try and get a package going as soon as I have some time (that may not be soon.)
Ps. I owned at least 2 sb16s and drooled over the AWE32 (still one of the best all round audio cards of all time IMHO), and I kept my sb128 even though I don't have a machine to put it in. ;-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ragemaxis:
From your first post it looks like it issued a warning, but no errors, so it actually should have compiled correctly. Was an executable file named rbdrum2midi generated? If so you should be able to at least run it using the command ./rbdrum2midi in the src folder. Thanks for sticking with it. We'll get you playing hihat eventually.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
sorry i've been in the middle of gardening and a bad chest infection and then moved over to kxstudio - it compiles but I havent had a chance to get hydrogen-git running and test everything because ubuntu is dangerous foreign territory for me compared to slackware, its a whole different world but at least more things work (if you can find the right docs and not just long monologues followed by SOLVED!" and no solution so numerous google is useless - or youtube instructions, something that I find tedious)
Anyways, thanks again for the work, looking forward to having enough time to do some really cool stuff with this and a couple other hardware mods i'm working on or waiting on for delivery. Might repurpose this driver to work with a hardware modded xbox controler to replace all the analog control inputs with knobs or faders on a chassis just to repurpose the excellent core circuit.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
sorry i've been in the middle of gardening and a bad chest infection and then moved over to kxstudio - it compiles but I havent had a chance to get hydrogen-git running and test everything because ubuntu is dangerous foreign territory for me compared to slackware, its a whole different world but at least more things work (if you can find the right docs and not just long monologues followed by SOLVED!" and no solution so numerous google is useless - or youtube instructions, something that I find tedious)
Anyways, thanks again for the work, looking forward to having enough time to do some really cool stuff with this and a couple other hardware mods i'm working on or waiting on for delivery. Might repurpose this driver to work with a hardware modded xbox controler to replace all the analog control inputs with knobs or faders on a chassis just to repurpose the excellent core circuit.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Kxstudio is a nice distro. You should be able to install from source on slack too though. Hopefully it turns out. Good luck with hydrogen. I had to build it from source one time. It took quite a while. It should be fairly up to date in the Kxstudio repositories though. The maintainer is quite vigilant in keeping software up to date. For at least this exercise installing the packaged version will be sufficient.
You can actually use any drum sampler like fluidsynth, drumgizmo, carla, linuxsampler etc just by assigning the drums different midi notes. run ./rbdrum2midi -h for the full useage options.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
its working now, I need to find the proper startup switches for the hihat but it compiled and I have things set up. Stupid canada post lost my package until monday or tuesday so i've got some extra time I otherwise would be spending getting the pedal and button controllers going. So I can rock out on the drums tonight. Its beautiful weather here, perfect for playing some pickup jazz but all my friends with instruments also have families and zero time so that is a thing from time go bad - so sad now with rudimentary drums (and pattern sequencers = )
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
aparently I need to get the udev stuff changed, Are the patches in dev available in the jackmidi fork? or maybe I can configure hydrogen to work in alsa mode. Will mess with it, I think I have udev set stuff set but I tried using /etc/init.d/udev restart etc. and so far nothing changed and the device keeps disappearing. I will figure it out tonight.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
udev is odd that way, even once you add the permission file, to get the permissions to work I need to do a systems reboot, a simple reload or restart of udev doesn't do it. I have no clue why ...
To use rbdrum2midi without root priviledges create a rules file in /etc/udev/rules.d/
I only just got the jack midi working this morning, but it is now merged into dev, so if you'd like to pull and rebuild it worked on my system. To use jack give the -j option. Alternatively you can run in default alsa mode and use a program like a2j that acts as a bridge between the 2 protocols. Also note that you must get the udev rules working if you use jack because running rbdrum2midi as super will make it look for a jack daemon run by super. Just follow the instructions randomas gave above. I was able to restart udev without a full reboot with the commands:
udevadm control --reload-rules
udevadm trigger
I write little scripts that run rbdrum2midi so I don't have to remember all the command line options. Something like:
./rbdrum2midi -j -htdm y -htp ob -hto 46 -htc 42 -ob 44 -r 38 -g 57 -b 41
(That will give you approximately a GM drumkit with hihat, its how I use it). Do you have cymbals? You assign them through options -ycy XX -bcy XX etc.
Last edit: ssj71 2014-06-02
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
yeah, thanks for the refresher - im getting pretty good with jack in general now, just trying to learn the ladish / catia / claudia session management stuff and get my new studio 100% working so I can shift to instant on creativity because the more time my mind spends in technical the less able I am to work creatively, never used to be that way but it is now.
I am very happy to say I am up and running with all features tested and working to a certain degree and the faults are either something to do with the linux usb stack or the internal latency of the piezo pads on the drum kit. kxstudio 14.04 has the bleeding edge versions of felipe's stuff which is pretty cool and if you mod it a little bit on the rt-wine end I am able to run almost all of my plugins including ezdrummer 1.x. There is a chart on google that has the notes so I was able to get it working with your driver. The only problems (in hydrogen and in toontrack) are latency related as well as the way the notes are handled (without velocity) with note-on note-off but I am not really sure I know at the moment without playing with a "pro" equivalent where the issue is. Using the driver with the built in controller gives me somewhat better results, I didnt try the jack midi very much because most of my stuff is alsa midi but i'm gradually moving everything over. I need to figure out where my fst.exe file disappeared to in order to wrap vst's with a shell that supports external midi learn and jack midi. In a week or two i'll try to report back in with anything i've figured out either with the hardware or the usb bus latency.
One thing that I would love to have that the windows driver had (sorry) is to be able to switch the snare drum using the same pedal as the hihat, it screws up how I have it working in theory because I have a tzzt pedal sound attached to the bass pedal that i'd have to make work using some kind of midi plugin - but being able to switch between snare springs and snare rim would be really handy - I am guessing that the code changes you already made (thank you so much btw again) could probably do that without much modification but for now im just going to use 2 pads for the 2 sounds since I only really ever use hi-hat snare and bassdrum to make the snare sounds because it lets me get two hits in for every latency point (or whatever I should call it) letting me drum a little bit faster. Really i'm going to be moving it around after its recorded by hand anyways (havent test driven any linux software in that department yet but I might just try to get reaper running satisfactorily because ardour scares me a bit) .. so I think the way things are its usable and workable for my uses as much as its going to be without some hardware modification or low level linux tweaking that I might have considered on slackware but on ubuntu i'm finding myself very lost.
Thanks again, and glad that everything is working. I might also be able to use some sort of filter to get my switchboard and pedal (a different device) working converting the CC's into notes to add cymbals - but I have requests circulating right now and i'm saving up cash to get a used rb3pro or an rb2 and cymbals if anything pops up locally on kijiji. So please don't waste any time on my behalf in the rb1 department.
I've fallen in love with jack over the last few months. Definitely.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Great. You can set it up to have the pedal switch any of the drums with the command arguments, but only 1 drum.
If you aren't happy with the latency and you are using a client using JACK midi you might consider playing with using the jack driver. I don't know much of the details but I've heard that the alsa sequencer that our driver uses by default has fairly low performance. It might be more related to jitter than latency, but I implemented the JACK driver expecting it to be better (haven't had a chance to measure it yet though). Maybe just your jack settings need to be tweaked a little for lower latency. Any more feedback you have as you use it more is welcome.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've been trying to get -dev going once I figured out the git syntax, anyways, i'm getting an error while compiling - i'm on slackware, and I suspect it might mean upgrading to a newer version of alsa libs although I thought I was pretty bleedy on that already.
gcc main.c rbkit.c rb1kit.c ghkit.c -o rbdrum2midi -lasound -lusb-1.0
main.c: In function 'setup_alsa':
main.c:323:83: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
if ( verbose >= 0) printf("Error: open_client failed: %s\n", snd_strerror((int)seq));
I am not developery enough to make a project that running aclocal autoconf automake or an autogen.sh and then the configure make etc process or lately frequent lone wscript files with no waf in some projects ... but anyways, I tried the readme instructions, im a bit low on time just wondering if this is some difference in alsalibs between ubuntu (I assume everyone is on debian/ubuntu) and slackware - or what.
This is gregory btw.
upgraded to a minor point higher in the alsa release pile, it didn't change anything although I dont trust anything these days to update the includes properly (cough lv2) but any hints would be fantastic, I want to give this a try.
Just about to try to get full module signing workign and boot up with a much newer kernel and likely won't have working nvidia thus X for a while and will hit the couch. Tomorrow rain is expected so I will be inside hopefully making a hellish racket since I figured out how to cross compile ardour3 and it looks like carla-git is going to work - except now for some reason jack seems to have stopped passing data in off my capture card. Likely a reboot will help.
Can't wait to have hi hat, so excited.
still getting nowhere but im also trying to get stupid pam working, I like slackware in large part BECAUSE it doesnt use pam and its various insecurity, I think PAM is next thing to a backdoor but there is a backdoor in the backdoors even these days, Learning the state of affairs of host node security and how insanely simple it is for anything penetrating the host node to just control or manipulate my VPS scares me deeply. root and immutable doesnt mean shit anymore. Welcome to the cloud. The cloud is an example of an intelligence concept that people have only bought into out of the sheer load of advertising,. Sigh. Thats why i'm trying to go cyberluddite and get my music room and go back to thinking about high school emotional stuff to write some music (nothng else seems to work and my muse is gone...sigh) but im encouraging some of my easy to work with great voice / talents band memembers to get practicing even if its an activity with the kid, maybe get my mom to come to look after the kids over a few weekends upstairs (she doesnt live here) and get my singer back into action because she (with a yet to be found backup) was a big personal influence to my sanity and the band is nothing without her even if I am the main producer. I really want to get a 5 song EP published and onto torrent by this time next year, and this time around, fix the biggest regret- no drums on our demo album except a drum machine on the song that everyone automatically likes best,
Close to having ardour with winvst support and also have very low latency settings for reaper and wineasio but right now there is a major midi problem that would be a showstopper without buying a new card or a used 410 card (like I ordered in the first place) because so much jack I take for granted that the asio world doesnt do. Reason is totally a write off to me when it was the first place I learned how to turn modular synth components hooked up to oscilators or LFO or envelopes in strange ways could end up with amazing sounds and now finally its happening for guitar.
Will be going into the weekend with my includes hopefully as good as they should be and hopefully someone can get back to me so I can get the drum middleware compiled and working and im drawing very close to the time when the HTPC and torrent duties of my big new workstation as crippled as it is by a finickly memory socket that wont easily go over 8GB and no money or parts to get it at least up to 32. But I recorded first album with a kawai kc20, a borrowed couple guitars, alesis compressor, a permanently borrowed sb16asp (remember those?) and a little solid state preamp I made out of a written off overdrive boss pedal. And some stellar singers. I would love to have access to the music equipment that floats around that spot now, or access to the young, trained and eager talent dying to get their name on tracks. But now is now and technology is alot better than the P-133 machine I was running samplitude some ancient version and soundforge on likely windows 98. Anyways, getting ready to roll with triple monitors, solid VST's and now LV2's and im going to be getting the best possible hardware and software that no money and slackware running wine heavily modified can handle ... now to find the talent. and, for once, thanks to you guys if I can get this ((#($$* to compile ... I will have drums on the next EP this summer! Sad are the days when you need to arrange babysitting and force practice on your primary talent. I myself am a 36 year old permanent bachelor and children scare me with their inappropriate, deeply honest questions and observations that cut through the veils of bullshit I drape myself with in any kind of social siuation.
End monologue. Thanks both of you!
Wow, you seem to be a lot more knowledgeable than I am on all things unix... I generally tend to walk around with a big stick and hit stuff repeatedly till it works. ;-)
A lot of work has gone into the dev branch recently and I still need to test it on my kits, compilation has always been an issue with this project ... I started it on ubuntu 10.04 and built all the developery stuff and .debs a bit hamfistedly, hence the issues. I'll be setting it all up again soon (hopefully).
Keep us posted and glad you find it useful.
I just tested the dev branch from a sf provided snapshot.
I tested it on a ubuntu 12.04 machine, I entered the src diretory and used "gcc main.c rbkit.c rb1kit.c ghkit.c -o rbdrum2midi -lasound -lusb-1.0", this worked without any errors or warnings. Tested the PS3 rb3-pro drumkit and it worked.
alsa-base version 1.0.25 as are the libasound2 and libbasound2-dev pakages.
I'll try and get a package going as soon as I have some time (that may not be soon.)
Ps. I owned at least 2 sb16s and drooled over the AWE32 (still one of the best all round audio cards of all time IMHO), and I kept my sb128 even though I don't have a machine to put it in. ;-)
ragemaxis:
From your first post it looks like it issued a warning, but no errors, so it actually should have compiled correctly. Was an executable file named rbdrum2midi generated? If so you should be able to at least run it using the command ./rbdrum2midi in the src folder. Thanks for sticking with it. We'll get you playing hihat eventually.
sorry i've been in the middle of gardening and a bad chest infection and then moved over to kxstudio - it compiles but I havent had a chance to get hydrogen-git running and test everything because ubuntu is dangerous foreign territory for me compared to slackware, its a whole different world but at least more things work (if you can find the right docs and not just long monologues followed by SOLVED!" and no solution so numerous google is useless - or youtube instructions, something that I find tedious)
Anyways, thanks again for the work, looking forward to having enough time to do some really cool stuff with this and a couple other hardware mods i'm working on or waiting on for delivery. Might repurpose this driver to work with a hardware modded xbox controler to replace all the analog control inputs with knobs or faders on a chassis just to repurpose the excellent core circuit.
sorry i've been in the middle of gardening and a bad chest infection and then moved over to kxstudio - it compiles but I havent had a chance to get hydrogen-git running and test everything because ubuntu is dangerous foreign territory for me compared to slackware, its a whole different world but at least more things work (if you can find the right docs and not just long monologues followed by SOLVED!" and no solution so numerous google is useless - or youtube instructions, something that I find tedious)
Anyways, thanks again for the work, looking forward to having enough time to do some really cool stuff with this and a couple other hardware mods i'm working on or waiting on for delivery. Might repurpose this driver to work with a hardware modded xbox controler to replace all the analog control inputs with knobs or faders on a chassis just to repurpose the excellent core circuit.
Kxstudio is a nice distro. You should be able to install from source on slack too though. Hopefully it turns out. Good luck with hydrogen. I had to build it from source one time. It took quite a while. It should be fairly up to date in the Kxstudio repositories though. The maintainer is quite vigilant in keeping software up to date. For at least this exercise installing the packaged version will be sufficient.
You can actually use any drum sampler like fluidsynth, drumgizmo, carla, linuxsampler etc just by assigning the drums different midi notes. run ./rbdrum2midi -h for the full useage options.
its working now, I need to find the proper startup switches for the hihat but it compiled and I have things set up. Stupid canada post lost my package until monday or tuesday so i've got some extra time I otherwise would be spending getting the pedal and button controllers going. So I can rock out on the drums tonight. Its beautiful weather here, perfect for playing some pickup jazz but all my friends with instruments also have families and zero time so that is a thing from time go bad - so sad now with rudimentary drums (and pattern sequencers = )
Thanks.
aparently I need to get the udev stuff changed, Are the patches in dev available in the jackmidi fork? or maybe I can configure hydrogen to work in alsa mode. Will mess with it, I think I have udev set stuff set but I tried using /etc/init.d/udev restart etc. and so far nothing changed and the device keeps disappearing. I will figure it out tonight.
udev is odd that way, even once you add the permission file, to get the permissions to work I need to do a systems reboot, a simple reload or restart of udev doesn't do it. I have no clue why ...
To use rbdrum2midi without root priviledges create a rules file in /etc/udev/rules.d/
file 90-drumkit.rules:
SUBSYSTEM=="usb", ATTR{idVendor}=="12ba", ATTR{idProduct}=="0210", GROUP="audio", MODE="0664"
SUBSYSTEM=="usb", ATTR{idVendor}=="12ba", ATTR{idProduct}=="0120", GROUP="audio", MODE="0664"
SUBSYSTEM=="usb", ATTR{idVendor}=="1bad", ATTR{idProduct}=="0003", GROUP="audio", MODE="0664"
SUBSYSTEM=="usb", ATTR{idVendor}=="1bad", ATTR{idProduct}=="0005", GROUP="audio", MODE="0664"
SUBSYSTEM=="usb", ATTR{idVendor}=="1bad", ATTR{idProduct}=="3110", GROUP="audio", MODE="0664"
this will work if your linux distro has an "audio" group and your user is a member, otherwise substitute "audio" with "users".
ragemaxis:
I only just got the jack midi working this morning, but it is now merged into dev, so if you'd like to pull and rebuild it worked on my system. To use jack give the -j option. Alternatively you can run in default alsa mode and use a program like a2j that acts as a bridge between the 2 protocols. Also note that you must get the udev rules working if you use jack because running rbdrum2midi as super will make it look for a jack daemon run by super. Just follow the instructions randomas gave above. I was able to restart udev without a full reboot with the commands:
udevadm control --reload-rules
udevadm trigger
I write little scripts that run rbdrum2midi so I don't have to remember all the command line options. Something like:
./rbdrum2midi -j -htdm y -htp ob -hto 46 -htc 42 -ob 44 -r 38 -g 57 -b 41
(That will give you approximately a GM drumkit with hihat, its how I use it). Do you have cymbals? You assign them through options -ycy XX -bcy XX etc.
Last edit: ssj71 2014-06-02
yeah, thanks for the refresher - im getting pretty good with jack in general now, just trying to learn the ladish / catia / claudia session management stuff and get my new studio 100% working so I can shift to instant on creativity because the more time my mind spends in technical the less able I am to work creatively, never used to be that way but it is now.
I am very happy to say I am up and running with all features tested and working to a certain degree and the faults are either something to do with the linux usb stack or the internal latency of the piezo pads on the drum kit. kxstudio 14.04 has the bleeding edge versions of felipe's stuff which is pretty cool and if you mod it a little bit on the rt-wine end I am able to run almost all of my plugins including ezdrummer 1.x. There is a chart on google that has the notes so I was able to get it working with your driver. The only problems (in hydrogen and in toontrack) are latency related as well as the way the notes are handled (without velocity) with note-on note-off but I am not really sure I know at the moment without playing with a "pro" equivalent where the issue is. Using the driver with the built in controller gives me somewhat better results, I didnt try the jack midi very much because most of my stuff is alsa midi but i'm gradually moving everything over. I need to figure out where my fst.exe file disappeared to in order to wrap vst's with a shell that supports external midi learn and jack midi. In a week or two i'll try to report back in with anything i've figured out either with the hardware or the usb bus latency.
One thing that I would love to have that the windows driver had (sorry) is to be able to switch the snare drum using the same pedal as the hihat, it screws up how I have it working in theory because I have a tzzt pedal sound attached to the bass pedal that i'd have to make work using some kind of midi plugin - but being able to switch between snare springs and snare rim would be really handy - I am guessing that the code changes you already made (thank you so much btw again) could probably do that without much modification but for now im just going to use 2 pads for the 2 sounds since I only really ever use hi-hat snare and bassdrum to make the snare sounds because it lets me get two hits in for every latency point (or whatever I should call it) letting me drum a little bit faster. Really i'm going to be moving it around after its recorded by hand anyways (havent test driven any linux software in that department yet but I might just try to get reaper running satisfactorily because ardour scares me a bit) .. so I think the way things are its usable and workable for my uses as much as its going to be without some hardware modification or low level linux tweaking that I might have considered on slackware but on ubuntu i'm finding myself very lost.
Thanks again, and glad that everything is working. I might also be able to use some sort of filter to get my switchboard and pedal (a different device) working converting the CC's into notes to add cymbals - but I have requests circulating right now and i'm saving up cash to get a used rb3pro or an rb2 and cymbals if anything pops up locally on kijiji. So please don't waste any time on my behalf in the rb1 department.
I've fallen in love with jack over the last few months. Definitely.
Great. You can set it up to have the pedal switch any of the drums with the command arguments, but only 1 drum.
If you aren't happy with the latency and you are using a client using JACK midi you might consider playing with using the jack driver. I don't know much of the details but I've heard that the alsa sequencer that our driver uses by default has fairly low performance. It might be more related to jitter than latency, but I implemented the JACK driver expecting it to be better (haven't had a chance to measure it yet though). Maybe just your jack settings need to be tweaked a little for lower latency. Any more feedback you have as you use it more is welcome.