jrp

I am using a remote script for ableton live that allows only note on evnts to trigger software functions. I like to use encoders for some functions (like remote arrow keys, cycle quantisation, etc) since i like the feel of it. Turning the encoder right should send a note on, turning it left should send a different note. Is this possible with the MB-IO128 or 16e? Just hooking my encoder to two AIns on the 128 i have running didn´t do the trick, since the encoder will trigger both events shortly after another. Thanks!

I wanted to get into programming for quite some time and the documention on programming for mios is really good. I already read a bit on C, so maybe i´ll just give it a try. If i manage to put together a little program that puts out one note-on with a button and uses a set of other buttons to change that note on event to different midi numbers i am on the right track. I am a bit scared i will mess up with all the tools and rutines involved, but i will try. Haven´t programmed since GW-Basic 25 years ago... BACK on toppic: I see different approaches for this besides from writing my own application, maybe you can confirm that there is no missunderstanding: Have one bank setup for all the controlls and the first eq-band. Use a bankstick housing banks with the same setup exept for the eq-controlls that will send different events with every bank. Not very ellegant but it should work, right? Other ideas i had use more than one core and are even less elegant...

thank you!

Hello, In the documention of the MB64e i read about groups all the time, but i couldn´t figure out what they actually are... What i am wishing to acomplish (and maybe groups is just the concept needed) is this: On a controller resembling my channelstrip setup (gate, eq, comp) i wish to use three controllers and a switch to build one eq band. Frequency, Gain, Q-Factor, EQ-band On/Off I wish to use 5 dedicated switches to select between 5 EQ-bands to controll. At the same time everything else on my MB64e should stay the same. I am sure this can be done, but i am not sure how it should be implemented with minimum effort.

Hi I plan about the same thing, although i still building my drum modules right now... I can´t find it right now, but i think it was explained somwhere how to alter the code so the MBCV outputs 1ms triggers instead of gates. I´m wondering if the same thing could be done with the cv outs, turning them into velocity dependant triggers. Anyone know? With these an Release Generator could be fead directly (without comparator). Much easier than generating an normal envelope and using a second vca for velocity.

Looks like i solved this one myself, wasn´t that hard. If there is a button in the design that i don´t use than i just set it to sr 0. Still not sure why the track group leds are supposed to be dual colour.

Well, i don´t know, maybe it would have worked in both cases. I can check tomorrow if i get a new hex file when using %programfiles% or if it has to be %programme%.

Thanks alot, it worked!!! Not sure why it didn´t before, but now everything is ok. i reinstalled all the tools, changed the makefile.orig and all is fine. I also changed %programfiles% in the set path line to %programme% since i´m using the german version of xp. Don´t know if that makes a difference, if it does than this info should be added in the quick start guide. Happy now, greetings!

Thanks! I´ll read through your posts, see if i find my mistake. For creating a file with a new name i have to add my asm in this line in the makefile.orig, i guess: # default rule that defines the .hex files which should be created # note: always require a "cleanall", since dependencies (e.g. on .h and .inc files) are not properly declared all: cleanall setup_mbseq_v3.hex setup_mbseq_cd_cd.hex setup_mbseq_tk.hex SETUP_SEQ_JRP.hex With Notepad++ i replaced this in the setup_mbseq_v3.asm: DIN_ENTRY SEQ_BUTTON_Pause, 1, 5 DIN_ENTRY SEQ_BUTTON_Play, 1, 6 with this: DIN_ENTRY SEQ_BUTTON_Pause, 1, 6 DIN_ENTRY SEQ_BUTTON_Play, 1, 5

i also have an ibook g4, but i can´t find a guide on how to make a hex file on osx anywhere.

Hi together. I´m close to crying... tried everything exactly as described in the wiki windows guide, but i just can´t get my edited setup*.asm to be converted to a hex file. No idea what´s wrong. I Installed all tools in their default directories, followed all the steps, but nothing is happening. First i saved my setup to a new file. When i do the set path command and type make i get three hex files: The v3 one, the tk and the cd. My own asm file is simply ignored. Next thing i tried is do just a little change to the setup v3 file (interchange play and stop pins) and tried again. I get a new v3 hex file, but when i upload it the seq behaves as before, the pins are not interchanged. What could be wrong? I was so happy to finish this fantastic machine, and now i´m stuck...

Any easy way to do this? Some cmos counter thing and an r2r maybe? Idea is this: I will have LEDs on top of all my buttons. Most of them will Correspond to the function of the button. But there are some functions that have a button, but no LED (like ff and rew) To make them all look alike i want leds on those buttons as well, even though they´ll have no function. To make them look like something i thought about lighting those buttons dimmly. But even cooler would be this: Leds fading from dim to bright with every 16 steps. I would like that look...

Hi Forum! Finally i really have time to work on my seq, finally i´m getting somewhere. Right now i´m soldering buttons and leds. To match to my hardware i have decidet to use my own definition for the buttons and leds. First of all: I can´t programm and i feel it´s really great how the setup.asm file is commented. Think i have understood almost everything, only few questions remain (sorry if these are answered elswhere, i didn´t really find it here or in the wiki): LED_GROUP1 EQU (((11 -1)<<3)+ 0) ; OPTIONAL! see CHANGELOG.txt LED_GROUP2 EQU (((11 -1)<<3)+ 2) ; assigned to pin 2 due to DUO LED LED_GROUP3 EQU (((11 -1)<<3)+ 4) ; assigned to pin 4 due to DUO LED LED_GROUP4 EQU (((11 -1)<<3)+ 6) ; assigned to pin 6 due to DUO LED I thought the track group buttons are normal leds. Really confused now. Next thing, If for example i change the dout pinning so that the play led is on pin 1 of shift register nr5 than this will of course interact witch the definition for the bpm display. What do i do? Simply this? ; === BPM digits === ; ; set to 1 or 2 to enable the 3 optional BPM digits ; 0: BPM digits disabled ; 1: digits with common cathode ; 2: digits with common anode #define DEFAULT_BPM_DIGITS_ENABLED 0 ; ; define the shift register to which the segments are connected (0=disabled) #define DEFAULT_BPM_DIGITS_SEGMENTS 0 ; define the shift register to which the common pins (cathodes or anodes) are connected (0=disabled) #define DEFAULT_BPM_DIGITS_COMMON 0 ; 3rd question: If a din pin that has a function in the original design will be unused in my setup, what do i have to do? Eg, in my design pin D4,5,6 of register 4 will be unused. I will adjust this entry to my need anyway: DIN_ENTRY SEQ_BUTTON_Solo, 4, 4 DIN_ENTRY SEQ_BUTTON_Fast, 4, 5 DIN_ENTRY SEQ_BUTTON_All, 4, 6 After that D4,5,6 will not be definened any more. Done? Thanks, Jens

of course, my mistake. I had read about the new buttons for the v3 design and overlooked that they were not included in your Seq. So no use having the track group buttons twice? One set for the GP row (instead of F4), one set for the matrix?

THanks. I´ll read and try to learn. Maybe that mirracle of someone turning me into a programmer will sooner or later happen... why not now? And yes, that´s the idea: select programs stored within a midibox, not by midi but by dedicated din pins.

Ok, i see. can´t wait to finish my design! about the track group buttons: I understand you reffer to the difference between track and track group buttons. That one is clear. But i noticed that on your design (using the matrix in a breakout box) you have track group buttons on both units. Now i´m not sure how they interact. Are the two sets of buttons doing the same (like they were wired in parallel), or are they independant: The ones on the seq to select the track together with the track buttons, the ones on the matrix to select the group to be displayed, independant of the track selected on the seq? Hope that question is clear (bit difficult sometimes). I just want to finish the frontplate first, then install the buttons/Leds, then wire everything up. Otherwise it could get a bit messy... BTW Have i told you that this page is very impressive? It is!

Hi. Just wondering if there is any function like this "hidden" in the code. Have a set of buttons on your midibox to directly select a saved patch/setup. Of course the obvious way would be to build another midibox (128?) and programm it to send programmchanges when the desired button is pressed. But maybe that same function could be had much easier with an din pin and a little line of code? This could be useful for different things, eg ommit the display on a mbcv: store all the setups you will need and select them with a handful of buttons directly. Or have direct access to different sequencer patches while playing live. etc. thanks!

thanks. just found out that my last reply didn´t make it. I´m still not sure: Is there any advantage in having both the matrix and the gp buttons/leds? Is it possible to controll 5 rows then at the same time? And do i need the track group buttons for the matrix or will the do the same as the track groub buttons on the seq?

the title may be a bit confusing, but here´s my question: When building a sequencer v3 plus the button/led matrix, will one of the matrix rows be the same as the gp button/leds? Or for example: Can i set the matrix to track group one, while editing track 9 (group 2/track 1) with the gp buttons and encoders? Or: Since i´m building both into one box, could i leave out the gp buttons on the seq? Thanks btw, great job tk...!

i see. think now i understand this. Thanks! Ok, so if i want to do this i´ll have to go for two 2*40 displays.

Just too explain myself, and one :) from me, since i don´t want to get on anyones nerves: I know it was aimed at me. Didn´t have a chance to reply yet. I also know that this forum is full of fans like me who don´t have a clou of changing the code. Still these fans keep on asking can i do this or that... hoping someone replies: "yes, i´ve done it: just change this 0 to 1" That is because uCapps is so cool. These projects are great, and the way it´s all open makes me feel like anything is possible. So i can´t resist posting. I know this a lot from the analog forums out there, and i´m always glad to remember how it got started for me and give a newbe some hint, rather than saying go figure it out if you want to know! Ok, this happens a lot, and i didn´t know there is a wishlist. What i really like about this forum is how everyone is encouraged to contribute. Really. For me the solution is easy. Takes one more vca, or easier an analog switch turning on the cv when a trigger is high. I guess the delay between the two is not too big? That´s really the only question i have in mind. When a new key is hit, will the trigger go high while the cv is still at it´s old value? And Thorsten, i belive it´s easy compared to your sequencer and other projects. In fact i have been reading lots of the code. Since you wrote more explanaitions than actual code, even someone like me can figure out little bits of the more general functionality of such a programm. Still i´m suprised every time again of how much language even such a "simple" program consists. Sure some effort. - and all going into that little chip... Fascinating!

ok. hadn´t noticed.

i don´t know, but i think that can´t be it. In all sequencers you can have many tracks with the same name.

Just came across this while browsing electro-music.com: http://matrixsynth.blogspot.com/2007/07/mempot-potentiometer-with-memory.html Imagine what a cool lfo or envelope this could be! Record the motion and fire it with a trigger!

Wow, i wouldn´t have thought that. I know no midi cv out there with such cool functions (number of outs, different responce, curves, etc) And i kow no midicv that is easy to use.... i wouldn´t even expect it to be. Did i mention that your design even has a display? Anyway, normaly it´s set it up once and leave it. There are propably few people who want to switch between different setups. One feature that might be really useful, and maybe easy to implement, would be to assing some of the cv outs as dynamic triggers. So any cv-out could be swiched to give a short velocity dependant pulse when reciving a note. Or in another mode keep the pulse till the key is released and return to 0v after that. Then it could fire an lag circuit directly. Much easier than triggering an envelope generator with a trigger out and multiplying the envelope-cv with a cv out.