rick.repsher

TK, Once again, thanks for your cooperation. I am interested in building a unit... I just want to make sure I'll have something that meets my needs (at least in part!) I'm sure many other users have started off the same way... a project in mind that morphs into something else. I'm ready to play! RR

TK, First off, I want to thank you for you patience with me on this matter. I actually did look at the document http://www.midibox.org/dokuwiki/doku.php?id=midibox64_e_patchmode, but I think due to my misunderstanding of the “bank†portion of the whole discussion, I just didn’t see the whole picture. I also did not see any discussion about patch mode in the MidiBox64E Tutorial, but I may have missed it. I have a couple more questions, and hopefully we can out this thread to bed. 1) Is it possible to save encoder "positions" as part of a patch? 2) As part of a patch, you can send sysex. Any sysex (obviously events only)? Program changes? 3) You state that, by default, program changes are available through the menu or via midi. Is it possible to program a series of buttons to control this? Thanks again for you help RR

How 'bout if we look at this a different way. What does patch mode get me? Or am I going in completely the wrong direction? I guess I misunderstood the part in the tutorial under 'Bank Submenu' and 'Select Group / Bank'... The Deluxe Solution. Thanks again. RR

Now I am even more confused... I am looking to build a MidiBox64E as a controller for a live setup. I guess that means that I want to be in "patch mode." My goal is to have 8 encoders dedicated to volume on 8 channels, and at least 4 encoders that I can map to functions depending on the patch. Maybe an analog input or two. Of course I'll need an LCD, the mandatory menu buttons, and whatever extra buttons to select the patch. So I'm guessing that the size of each patch will depend on the number of parameters I'm looking to save. Where does that leave me? Can I save the data for... lets say 50 patches to an internal "bank stick array." Thanks RR

From what I see, I can connect a maximum of 8 24LC256's together. Is there really any reason I need to use the "bank stick" format, instead of just putting them right in the box? Is it possible to save the data on from this array via MIDI... by default... as in without additional "programming"?. Also, the documentation talks about groups and banks. Just so I have this right, a group consists of 8 banks, and each bank is the data for one setup, snapshot, patch... whatever you want to call it. Each 24LC256 stores 1 group, so with the maximum stuffing, you have 64 banks (setups, patches, etc.) Do I have all of this straight? Thanks RR

So, by the looks of your diagram, the pulses are there to start with... but with the detent, you are "seeing" 4 events as 1. Does that make sense? RR

On the uCApps site, it states that "rotary encoders which are not mechanically detented should be prefered for MIDIbox64e." Contrary to this, it seems that all the encoder documentation I see on the site is about detented encoders, that may be modified to remove the detents. I spent many years working in an R&D "lab" on prototype equipment. It doesn't seem like just removing the detent solves anything. If the resolution is 24 pulses per rotation... then that is what it is, detents or not. What am I missing? Thanks Rick

OK, I've spent the last few weeks perusing the forum and I'm still a little lost. Im a keyboard player with a multi unit setup. I'd like to build a controller with encoders to basically send sysex messages to my setup (volume, etc, and patch selections.) I'd also like to be able to store multiple "patches." Basically, it would function as "the mother ship." I definitely have the chops to build the components and enclosure, but I'm a little confused on what programming skills I'll need out of the box. I've written quite a few programs in VB (my day job.) Comments, suggestions? Thanks Rick