Jump to content

anderspe

Members
  • Posts

    19
  • Joined

  • Last visited

Posts posted by anderspe

  1. Ok, well thanks very much for the advice - I do appreciate it - even though we did not fix it :-)

     

    I don't think there is a problem with the bi directional connection with mainstage, since every thing works. I can change encoders and buttons from mainstage perfectly. The thing with midi is that it only sends a status once, so if a button is on, its just because the last message it got was "on", and it will stay "on" until it gets an "off" message. It's midibox64e that turns off the led's when I change bank, not mainstage.

     

    It seems I need to get a midi box_ng going to get this functionality... Then I could probably get the "in-ear encoders" to work perfectly as well. Just seems to be a bit tricky - when you are a musician and not a programmer :-)

  2. Yeah, thats the same problem....

     

    Mainstage does report the status back from those buttons, but as soon as i switch bank all the led's turn off, even though they are still on in Mainstage. So it's actually working - but it's a bit difficult for me to see whats going on.

     

    Here is what the board does:

     

    16 encoders:

    1-8: Controlls amp settings for my ampsim (channel, gain, bass, mid, treble etc.)

    9-15: Controlls the levels in my in-ear monitor (vocals, guitar, other guitar, bass, metronome etc.)

    16: Guitar tuner output

     

    12 footswitches:

    1-4: Changes bank to change guitar sound (clean, crunch, drive and lead)

    5: Vocal effect: throw delay which is momentary,

    6: Filter vocal effect wich is toggle.

    7: Guitar Dim toggle

    8: Guitar Boost toggle

    9: Guitar Mute toggle

    10: backtrack Play/stop toggle

    11: backtrack previous momentary

    12: backtrack next momentary

     

    Now: everything works, except that all LED's turn off when I change banks - which leaves me "in the dark" :-) The buttons still are activated in Mainstage - so there is no problem sound-wise.

     

    Obviously it would be nice to have encoder 9-15 be "Fixed" as well, so my in-ear levels would stay the same regardless of which bank I'm in... But thats no biggie - I don't fiddle to much with that...

  3. So I tried the group thing! And it almost worked.... It looked right, but unfortunately the encoder did not send the midi data for the new value of the encoder when changing banks. So even though the encoder changed no data was sent to my application (kind of like when you dont have auto-snapshot and switch banks or patches).

     

    Are there no other possibilities?

  4. I'll test it out this evening when I get home from work.

     

    I'm controlling Mainstage on an apple mac. It's a live performance software thingy. It can send values if I want it to.

     

    I was thinking about upgrading to a lpc17 core with a mb_ng. I am reading the documentation at the moment - and haven't found (or understood, more likely) that function yet...

  5. i think this is possible if you use groups instead of banks for the encoders. you can send up to 128 midi events with 8 encoders if you assign them to the 16 available groups (or 16 encoder with 8 groups, .....). the button assignments do not change if you change the group.

    Ok, I'll give that a try...

     

    But I need the encoders to change value when i change groups, not the event. So my 16 encoders always control the same event and just change value. Is that possible with groups?

  6. I've asked this question in one of my other threads, but did not get any replies, so I'll try to make a new thread....

     

    What I need are fixed buttons that stays the same even if I change bank/patch.

     

    4 of my buttons are toggle buttons. If one of them is on, I need it to stay on even if I change bank. Is this possible with midibox64e? Right now the buttons revert to what they are set to in the recalled bank...

     

    The pedal_box project does exactly that - but unfortunately don't support rotary encoders.... http://www.midibox.o...hp?id=pedal_box

     

    One solution could be if the banks only stored and recalled the encoder positions, and not the buttons... Is that possible?


    Another solution could be to have 2 cores, one running pedal_board for the for the buttons, and one running midibox64e for the encoders only. Then with midi merge enabled on both boards and just sending programchanges from pedal_board to midibox64e running patch mode to change the encoder positions.... But that seems a bit excessive, or is that what i need to do?

  7. Hello Again.

     

    Now my box is completed, I have started to program it (just need the frontpanel and enclosure). And I still have something that puzzles me....

     

    What I need are fixed buttons/encoders that stays the same even if I change bank/patch.

     

    4 of my buttons are toggle buttons. If one of them is on, I need it to stay on even if I change bank. Is this possible with midibox64e? Right now the buttons revert to what they are set to in the recalled bank...

     

    The pedal_box project does exactly that - but unfortunately don't support rotary encoders.... http://www.midibox.org/dokuwiki/doku.php?id=pedal_box

     

    One solution could be if the banks only stored and recalled the encoder positions, and not the buttons... Is that possible?

  8. The MB64E application isn't prepared for inverted selection signals.

    You either have to replace the sink drivers (uln2803) by bridges, or you've to wait for the next version where this option will be available as a compile switch (i haven't integrated it yet...)

    Best Regards, Thorsten.

    Great!! That worked! Thanks alot!

     

    One last thing, how do i get it to use all 16 led's in the encoder rings? Right now it's only using the first 11 led's

  9. I have grounded the pins on j5. But I tried your suggestion anyway - but it did not help.....

     

    I made a quick little video describing the problem:

     

    http://youtu.be/EmKPuMzeqYk

     

    If someone could please help me with this I'd be really happy!

     

    just wondering, did you ground the pins on J5 if you have no analogue inputs or did you change the asm file?

    this is from on of my earlier posts:

    When i need to test just one or two pots i just connect directly to J5, and i then go into the asm file and change these lines and then recompile, it saves me having to ground things.

    So obviously i connect the pots as follows, Pot1: Vs/Vd/A0 Pot2: Vs/Vd/A1 Pot3: Vs/Vd/A2 (connecting to correct pins on pot!!)

    So i open for example setup_midibox64e.asm in my text editor


    #define DEFAULT_NUMBER_AIN 64 (the amount of pots/faders connected, more than 8 needs an ain board and MUX to be enabled)

    #define DEFAULT_ENABLE_AIN_MUX 1 (needed for when you use the ain boards and more than 8 pots)

    I then change them to this as i only need say for example 3 pots and no mux as im connected directly and not through an AIN board

    #define DEFAULT_NUMBER_AIN 3
    #define DEFAULT_ENABLE_AIN_MUX 0

    by doing this, the software only looks for the first 3 inputs on J5, the other 5 are not looked at and therefore i do not need to ground them.

    So if you do not have any pots or faders then change it to this
    #define DEFAULT_NUMBER_AIN 0
    #define DEFAULT_ENABLE_AIN_MUX 0

    if the J5 pins are not grounded then they cause spurious midi data that is constantly running. As explained changing the code saves soldering!

    see if that helps first

    Its surprising how easy it is to forget to ground the pins on j5 or edit the asm.
  10. I have made a midibox64e like this:

     

    post-9684-0-45708800-1359019896_thumb.jp

     

    Everything works perfectly, except for the LED rings.

     

    The LED rings are turned all the way up regardless of what the encoder position is. When i go into "LED Patterns" and change to another pattern, all the rings starts to move except for the selected ring. Selecting a new pattern does not change anything - the encoder stays on pattern #1 and is turned all the way up.

     

    Here is my .asm file:

     

    setup_midibox64e.asm

     

    What am I doing wrong here? Can somebody give me a pointer?

     

    Kind Regards

     

    Anders

  11. I checked this by measuring the delay caused by the Bank Load - and noticed that it was actually done twice! ;-)

    So: please try this version: http://www.ucapps.de/mios/midibox64e_v2_2e.zip

    Now it takes ca. 300 mS to load a bank. Unfortunately I can't make it faster due to the huge bank size (8 groups are loaded at once)

    Best Regards, Thorsten.

    Cool! 300 ms should be fast enough. I'm just on my way on christmas vacation, but I'll check it out when I come home next week.

    Thanks a lot!!

  12. Hi Anders,

    I'm surprised that it takes so much time to switch between the banks.

    Could you please check, if you've enabled the "AUTO_SNAPSHOT" option, which dumps all events of a bank to the MIDI OUT interface on every bank change?

    You could check this with a MIDI monitor.

    This would take some time - the MIDI bandwidth is the bottleneck.

    Best Regards, Thorsten.

    Auto_snapshot was not enabled. I tried to enable it, but that changed nothing....

  13. So I've built my first midibox (mb64e). I'm going to use it as a foot controller where I can store and recall the encoder and button settings for different patches.

    At the moment it's working exactly as it's supposed to by having 4 dedicated bank recall buttons (FF 02 0n for the buttons). So when I press button 1 it changes to bank 1 patch 1, button 2 bank 2 patch 1 etc.)

    The problem is that it takes a second or two to change bank - and since I'm gonna use this for playing live, it's too slow. Changing patches, however, is instant.

    So is there a "quick access" switch to patch button meta event?

    Kind regards,

    Anders

  14. Hi there

    I've just completed building a midibox64e based floorboard, and have realized that i need to work in patch mode.

    I've read this article:

    http://www.midibox.org/dokuwiki/doku.php?id=midibox64_e_patchmode

    but my problem is this line:

    Note: Patch mode is a compile option, it needs to be enabled in the main.asm file of the application. Thereafter a new .hex file has to be build and uploaded.

    .... I have no idea how to make a .hex file - and can't seem to find any info on how to do it.

    How do I make the .hex file?

    Anders

  15. Cool!! Thanks Thorsten!

    What about the "global" buttons? Is that possible?

    Anders

    Hi Anders,

    yes, you will need a bankstick to store different setups.

    Then you need to configure 5 buttons as "special function buttons" as documented in midibox64e_sfb_table.txt

    E.g. let's say that the buttons are connected to the first 5 inputs of the first shift register, then write:

    
        1.1  =  FF 02 00   # switch to Bank 1  --  for quick access
    
        1.2  =  FF 02 01   # switch to Bank 2  --  for quick access
    
        1.3  =  FF 02 02   # switch to Bank 3  --  for quick access
    
        1.4  =  FF 02 03   # switch to Bank 4  --  for quick access
    
        1.5  =  FF 02 04   # switch to Bank 5  --  for quick access
    
    

    in your .ini file (which then has to be converted to a .syx file)

    This has to be done for all banks, so that the SFBs are always available (this makes the SFB "global")

    Best Regards, Thorsten.

  16. Sorry if this is a newbie question, but if someone can answer this, I'd be really happy!

    I want to build a midi controller based on the MIDIbox64E.

    I want to have 5 dedicated recall buttons (program change I guess), like a pedal board. So i can recall what ever the other buttons and encoders are set to in that preset (and of course store presets as well). Is this possible? It seems like this, but requires bankstick, have I understood this correctly?

    Is it possible to have some of the encoders/buttons to be "global", so they are unaffected by a program change?

    Kind regards,

    Anders

×
×
  • Create New...