Hey guys, quick question.
I just created a midi instrument map in qsampler which has 2 banks, 0 and 1.
I want to switch between the two banks using my M-audio Keystation 88es midi controller, but I don't know which to use, bank MSB or Bank LSB. Attempting to incrementally increase bank MSB/LSB, results in no change from the instrument..
Can someone help me out here?
Bank MSB/Bank LSB?
-
- User
- Posts: 67
- Joined: Mon Sep 01, 2008 8:53 am
Re: Bank MSB/Bank LSB?
My bad, I just read the feature list..
qsampler only appears to support 1 chromatic bank and 1 drum bank..
Also, does anyone know where to find swingx.jar?
qsampler only appears to support 1 chromatic bank and 1 drum bank..
Also, does anyone know where to find swingx.jar?
Re: Bank MSB/Bank LSB?
LSB is good, but I just tried this with changes to both MSB, and LSB, and LS responded to both. (woohoo)
I have a lot of midi maps built for full orchestra, and i suggest the following for not only speedy use, but good sample management based on personal experience:
Method 1.
Set up midi maps according to instrument, in other words, 1 for each.
Create a midi port for each instrument map.
my maps are built as:
Port0
1st Violins
MSB=0 LSB=<number>
Port 1
2nd Violins
MSB=0 LSB=<number>
etc...........
This is useful for those instruments that number more than 128 variations/articulations. you simply add a new bank (LSB=1, LSB=2, etc) to each MMap/Port.
In Linux, we have the luxury of unlimited ports, so this is good. If this is not the case for you, then:
Method 2.
If you want a single port in, then set out your midi maps as follows:
Single port 0
MSB=0
1st violins LSB=0
2nd violins LSB=1
violas LSB=2
etc..
If you have more than 128 articulation/instrument variations, then go to method 1, and create a port per instrument, or continue the single port maps with something like:
Single port 0
MSB=0
1st violinsA LSB=0
1st violinsB LSB=1
1st violinsC LSB=2
2nd violinsA LSB=3
2nd violinsB LSB=4
etc........
These can be triggered successfuly from Rosegarden, using patch changes, per track.
i.e. If you have 3 banks of 1st violins in LS, each with 128 instruments/variations, then create three 1st violin tracks in RG, one for each bank. Use patches as normal.
Easy.
Alex.
I have a lot of midi maps built for full orchestra, and i suggest the following for not only speedy use, but good sample management based on personal experience:
Method 1.
Set up midi maps according to instrument, in other words, 1 for each.
Create a midi port for each instrument map.
my maps are built as:
Port0
1st Violins
MSB=0 LSB=<number>
Port 1
2nd Violins
MSB=0 LSB=<number>
etc...........
This is useful for those instruments that number more than 128 variations/articulations. you simply add a new bank (LSB=1, LSB=2, etc) to each MMap/Port.
In Linux, we have the luxury of unlimited ports, so this is good. If this is not the case for you, then:
Method 2.
If you want a single port in, then set out your midi maps as follows:
Single port 0
MSB=0
1st violins LSB=0
2nd violins LSB=1
violas LSB=2
etc..
If you have more than 128 articulation/instrument variations, then go to method 1, and create a port per instrument, or continue the single port maps with something like:
Single port 0
MSB=0
1st violinsA LSB=0
1st violinsB LSB=1
1st violinsC LSB=2
2nd violinsA LSB=3
2nd violinsB LSB=4
etc........
These can be triggered successfuly from Rosegarden, using patch changes, per track.
i.e. If you have 3 banks of 1st violins in LS, each with 128 instruments/variations, then create three 1st violin tracks in RG, one for each bank. Use patches as normal.
Easy.
Alex.