Activity for jeff
-
jeff posted a comment on discussion General Discussion
Hmmm. Must be a bug. Selecting "Full range slider" should interpolate the range so that 127 sets 255 BPM. But for some reason, it's being ignored. I'll look into it.
-
Yes, go to the Commands screen. Click on "Tempo ->BPM". Make sure "MIDI knob" is checked. By default, MOD Wheel (cc #1) controls tempo. Double-click on Tempo -> BPM, and check the box "Full motion slider". That should scale your Mod Wheel messages so that a value of 127 sets tempo to 255. (Of course by scaling, you have a more coarse control of tempo, but that shouldn't be a big deal. You can always fine tune the tempo + or - one step using "Tempo -> Decrease" and "Tempo ->Increase" messages).
-
Yes, go to the Commands screen. Click on "Tempo ->BPM". Make sure "MIDI knob" is checked. By default, MOD Wheel (cc #1) controls tempo. Double-click on Tempo -> BPM, and check the box "Full motion slider". That should scale your Mod Wheel messages so that a valus of 127 sets tempo to 255. (Of course by scaling, you have a more coarse control of tempo, but that shouldn't be a big deal. You can always fine tune the tempo + or - one step using "Tempo -> Decrease" and "Tempo ->Increase" messages).
-
I'm currently working on the ARM port of BB. But I'm also going out of town this coming week, so it may be a week before I can put out some updated code. As I recall, you have to set the MIDI chan with the GUI version, and save the config file. It may be easier to change SetBFree to use chans 11 and 12 for the two organ manuals. Then you can leave BB at its default setup. (Plus, you'll be able to allow the user to layer, or solo, BB's patches for bass, guitar, piano, strings, etc, by changing a manual's...
-
By playing patches, I mean using the "Human Player" part of BB, and all the patches associated with it. Your human player appears to be confined to playing BFree's organ sounds. You're using only BB's robots (and their patches). So you don't need a MIDI output device for BB's Human Player. Set it "Off". This means that every midi msg not on one of the robots channels, will be used to play chords. By making sure no robot is set to chan 1 or 2, then these chans play chords (rather than notes on some...
-
ok. So you want both hands to play chords. And you want chans 1 and 2 to trigger chords. Set "Human -> MIDI Controller -> Device" to None (since you're not using BB to play patches). Set "Robot -> Bass -> Channel" to 5. Set Master Channel to 1.
-
Is BB flexible enough to produce consistent accompaniements when receiving MIDI note ON/OFF messages on different channels? Not sure what you're asking here. BB has a very complex and versatile MIDI implementation. You should be able to control anything via MIDI (although you may need to setup BB on the Commands screen if you need to use specific MIDI messages to control specific features). Can I build and run BBNoGui on a RPI with no issue? I don't have an RPI to test. But I do have two small Single...
-
Try running back up band from a terminal window, and specify the arduino MIdi Output like so: ./backupband -SEQIN "bb_ctrl MIDI Out" This will cause BackupBand to look for a seq Output port named "bb_ctrl" and connect its Midi IN to it. (You won't need to manually connect using QJackCtl). Make sure your auduino is already running before you run BackupBand. You can also have BB automatically connect to jack's system out:" ./backupband -JACKOUT -SEQIN "bb_ctrl MIDI Out" BB has its own "session manager"...
-
Try running back up band from a terminal window, and specify the arduino MIdi Output like so: ./backupband -SEQIN bb_ctrl MIDI Out This will cause BackupBand to look for a seq Output port named "bb_ctrl" and connect its Midi IN to it. (You won't need to manually connect using QJackCtl). Make sure your auduino is already running before you run BackupBand. You can also have BB automatically connect to jack's system out:" ./backupband -JACKOUT -SEQIN bb_ctrl MIDI Out BB has its own "session manager"...
-
Try running back up band from a terminal window, and specify the arduino MIdi Output like so: ./backupband -SEQIN bb_ctrl This will cause BackupBand to look for a seq Output port named "bb_ctrl" and connect its Midi IN to it. (You won't need to manually connect using QJackCtl). Make sure your auduino is already running before you run BackupBand. You can also have BB automatically connect to jack's system out:" ./backupband -JACKOUT -SEQIN bb_ctrl BB has its own "session manager" built-in, so you...
-
Also, in order for your arduino to select styles, you need the arduino to send program change messages on the Master Channel. (Set Master Channel via "Human -> MIDI Controller"). To start/stop play, you can send a controller number 67 on the Master Channel. To control tempo, send a controller 1. Use BB's MIDI Event Test window to check that BB is receiving the arduino mesages, and that they are activating the desired BB functions.
-
Also, in order for your arduino to select styles, you need the arduino to send program change messages on the Master Channel. (Set Master Channel via "Human -> MIDI Controller"). To start/stop play, you can send a controller number 67 on the Master Channel. To control tempo, send a controller 1. Use BB's MIDI Event Test window to check that BB is receiving the arduino mesages, and that they are activating the desried BB functions.
-
Try running back up band from a terminal window, and specify the arduino MIdi Output like so: ./backupband -SEQIN bb_ctrl This will cause BackupBand to look for a seq Output port named "bb_ctrl" and connect its Midi IN to it. (You won't need to manually connect using QJackCtl). Make sure your auduino is already running before you run BackupBand. You can also have BB automatically connect to jack's system out:" ./backupband -SEQIN bb_ctrl -JACKOUT BB has its own "session manager" built-in, so you...
-
I recently got an ARM system, and have discovered that the gnu compiler generates some very different code on Intel versus ARM CPUs. In some cases, it even results in crashes, particularly with regard to signed versus unsigned variables. Basically anyplace where you have a signed value recast as unsigned, it can be trouble under arm. For example, this works under intel, but can do weird things under arm: unsigned char MyVariable; MyVariable = (unsigned char)-1; I'm currently cleaning up the code...
-
If you have trouble using Jack, I'd suggest that you first set BackupBand to directly use your audio output card. Set sample rate to either 44 or 48 KHz. Then make sure jack is stopped. If you get audio to work directly, then the problem is with jack. Jack is very complicated to setup (plus it has been hacked so much, including having its own libraries replaced by Pipewire, that it's a nightmare to troubleshoot). I make jack output available in BackupBand to try, but I don't recommend jack, and I...
-
Yes, it does. I'm a solo keyboardist, and I use the program for live gigs. In fact, I'm the author of the program, and I've been using it for a decade of weekly gigs. It runs only on Linux. It started out as a Windows program, but later I switched to Linux. I may consider porting it back to Windows at some point. If you've ever played an "auto-arranger" product like a Yamaha PSR, Korg PA, Roland BK, etc, then you've got the idea how this program functions. If you want to control it while playing...
-
Please delete these projects
-
closing BB stops Jack
-
Fixed in version 0.D
-
An extra note in the main docs
-
This limitation has been removed as of version 0.C
-
Apparent array overrun.
-
Fixed in version 0.C
-
Installed but not working properly
-
41k instruments not recognized
-
Updated the zip files with the correct filenames
-
Open the file 22.layout (in the BackupBand/Styles/Window folder) with a text editor. Change line 48 from this: VOLBOOST line 5 to this: VOLBOOST line=5 There was a missing = sign. Save the file.
-
BackupBand is Linux only. But I did initially write it for Windows, so there's a really old version of that. I'm going to bring that version uptodate, so eventually there will be Windows and Linux. I don't do Mac software, so that's right out.
-
Hmmm. ConfigFile.c is for an older version. It should no longer be in the new sources. Did you have a previous version of the source code? If so, delete that .git directory, and download the latest source code. (It fixes one of the errors you got above).
-
turns auto-repeat off in all of X11, leaves it off.
-
execution abort, FYI.
-
I replaced the strlen's with memcpy. That should bypass gcc's overly aggressive buffer checking. I deliberately called strlen, not nstrlen. Gcc shouldn't be substituting.
-
Code is not in buildable state
-
Initial commit
-
Initial commit
1