John E. Finster

Members
  • Content count

    273
  • Joined

  • Last visited

Everything posted by John E. Finster

  1. Upcoming MBHP_MF_NG module

    Ok, which program did you load inside the MF tool? Mackie protocol or something else?   Which fader did you touch?   Are you experiencing any problems when you move the fader you touched? Like the motors preventing you from moving the fader?   Are you using a laptop? If so, are you running it on batteries or on a psu when you are using the MF module?   A lot of questions, I know. But answering them could bring us closer to a solution.   my regards
  2. Upcoming MBHP_MF_NG module

    Can you post a few lines of the midi input when you touch one fader? Maybe 30-40 lines?
  3. Upcoming MBHP_MF_NG module

    This is strange indeed. What kind of faders are you using?
  4. Upcoming MBHP_MF_NG module

    Try to start at the most left side (0) and then move the slider slightly to the right (from 0 to 1 to 2 to 3....) and touch and release the fader every time until you find a setting that fits.
  5. Upcoming MBHP_MF_NG module

    Hi Nick,   the expected behaviour would in fact be     If you get a constant stream of on/offs you have to adjust the touch sensor sensitivity in the MF tool inside Mios Studio.   my regards
  6. A lot of midi message when I connect a DIN

    Ok, after your additional descriptions it really seems that there is a problem on the LPC17 core. The problem on my side would be to narrow down where this problem is, a remote diagnosis from here can be very hard.   You can try/check a few things:   1. What kind of computer are you using? PC or MAC? if you are on a PC, I suggest you install the gm5 driver, it´s much more stable than the native windows driver.   2. Visually inspect all the soldering points on the board.   3. If you have access to a multimeter, check the complete core for the expected voltages (look at the LPC17 schematics).   4. Check all the parts, especially those which has a polarity and all the ICs if there are put in the right way.   my regards
  7. A lot of midi message when I connect a DIN

    Hi,   the red led on the LPC17 core is lit, when some kind of data is processed (like the hdd led on a computer). If there´s a short on the DIN module this would be normal since it processes data continously (impulse from din -> midi data out).   I´m a little confused about that button event you posted because it wouldn´t really make sense if it looks that way. Did you post it here exactly like in the *.ngc file?   To test a bit further, I´d suggest you create a new *ngc file and insert some simple button events with an id from 1 to 32 and the midi event NoteOn and key from 1 to 32 (to test all input pins on the DIN):   EVENT_BUTTON id=1 type=NoteOn key=1 EVENT_BUTTON id=2 type=NoteOn key=2 EVENT_BUTTON id=3 type=NoteOn key=3 EVENT_BUTTON id=4 type=NoteOn key=4 ........ EVENT_BUTTON id=32 type=NoteOn key=32   After that you load it and look at the midi in monitor inside Mio Studio. If there is a continous stream of midi events still coming in, just let it stream for a few seconds and then cut the power of the LPC17 core (to stop the stream ).   Then you can study the stream and see, what kinds of notes appear in it. This could help narrowing down where the short sits.   my regards
  8. A lot of midi message when I connect a DIN

    Hi,   my first guess would be a short somewhere. That is sort of what a button would do, it would close the circuit between a DIN pin and ground.   What kind of key values are recognized in Mios Studio when you are using the NG Default script? Maybe this could help narrowing down the error?   my regards
  9. mios8 core error message

    Hi,   in the Mios8 repository there is an app, which can change the ID of a PIC, if you would like to try that:   (root)/trunk/apps/troubleshooting/change_id   I haven´t used it before myself, so I can´t tell you, if it works, TK gave my this info once.   my regards
  10. track leds / group leds confusion

    Hi,   I made the "bug" work again  :D . My track leds always show the selected track and my group leds always show the selected group inside the pattern screen now. I looked at the old source revisions and investigated, what you changed from 4.019 to 4.020.   I´m sorry for being overly excited about this, even I considered this, if at all, a mere aesthetic issue. But somehow I couldn´t let this go....   And now, I don´t have to    :laugh: . For now at least....   my regards
  11. track leds / group leds confusion

    Hi, I´m a little confused by the track and group leds of my seq4:   In my seq4 I only built in 4 track buttons with which I select the group, when I´m in the pattern screen. But I added 4 green leds for the current group as well as 4 yellow leds for the curren group. This works almost all the time, the current track and group is correctly indicated. But when I´m in the pattern screen, the green track led also indicates the current group. I was under the impression, that the track and group leds always indicate tracks and groups, even in the pattern screen.    I tripplechecked the wiring and I don´t think this is a hardware problem. Is there something in the hardware config file I overlooked? Or am I missunderstanding somthing about the leds/button assignments or even the seq4 system completely?   Thanks and greetings
  12. LPC17 and DIN

    Hi,   "autoload off" means, a file is not loaded automatically anymore, when you upload it onto your box or edit and save it in the editor.   If you disable this feature via Mios terminal, you can only load your scripts if you use the "load <script.ngc>" command in the terminal.   The default script always gets loaded, when you power up your box.   my regards 
  13. SD-Card / .NGC Script problem

    Hi,   when you power up your midibox_ng the default.ngc is loaded. You can load your script by typing "load 8x8" into the terminal of Mios Studio.   If you want your script to load up by default you can either save your 8x8.ngc as default (you load your script and then type "save default"). This didn´t work always in my case though, I can´t tell you why.   Or you can open your script with the editor, copy all the content and insert it in the default.ngc manually.   my regards
  14. Alphatrack Clone

    Hi,   this is a little something I whipped up today. The Frontier Alphatrack was my favorite midi controller and I used it a lot until it broke down some day. Today I´m into something a little bigger, but I always thought about integrating some parts of the Alphatrack protocol into my Midibox. So I created a MB_NG Patch that emulates the Alphatrack, which I want to share.     The Alphatrack´s host message sits on the right side of the screen. The other stuff on the left side (Volume bar, Solo/Mute/Rec state and "Vpot"assignement) I put in, because I created this script with my SEQ4 and this looks more clean than using the SEQ4´s leds.   For the Alphatrack clone a 2x16 character lcd is sufficient, but I think it doesn´t hurt to have a little more lcd space for custom labels.   Instead of the fader I´m using an encoder, the volume level can be reflected on the lcd, the touch sensor is replaced with a buton event.   The original Alphatrack features touch sensitive encoders, which is a very nice and handy feature. In my design I also replaced these touch sensor events with simple button events, but with some metal-shaft encoders and metal encoder knobs one can easily build some touch sensitive encoders.   All other buttons and leds are assigned in the NGC script, just the hw_ids would have to be adapted.   The MB_NG Firmware has to be modified a little bit, inside mbng_event.c a number has to be altered:   u8 x_wrap = (*stream == MBNG_EVENT_SYSEX_VAR_TXT56) ? 56 : 64;      has to be changed to: u8 x_wrap = (*stream == MBNG_EVENT_SYSEX_VAR_TXT56) ? 56 : 16;   So that the variable ^txt can set the cursor to the second line after 16 characters.   Then the MB_NG source has to be compiled again and uploaded onto the Midibox.   I tested it with Reaper (using the genius Alphatrack-Pro extension) and with Reason 5, no problems so far.       There are some issues I couldn´t find a solution for yet:   1. Using an encoder (or a fader) for volume doesn´t work completey. One can send the volume value, and the midibox somehow "picks up" the right volume value from the daw, when the encoder is moved. But the Midibox doesn´t receive this value, when it is just sent by the daw.   2. I wasn´t able to recreate the touchstrip from the Alphatrack. I can create 2 buttons with the events for a 1-finger touch and a 2-finger touch, but when I tried to emulate the touchstrip movement with an encoder, it didn´t work   I believe this has to do with the pitchbend values. The fader would need to send/receive a 10bit pitchbend value and the touchstrip a 5bit pitchbend value. But the MB_NG only provides a 14bit pitchbend value. This is not really a problem for me, since I wouldn´t use any of those 2 features for my own box, but for a complete clone, those issues would have to be resolved.   Maybe someone has an idea for a workaround?     Anyway, perhaps this can be of some use to someone.   My regards     Midibox_Alphatrack.zip     P.S. Inside the Zip are the .NGC script and a .NGL script for the extra labels I use on the left side of the lcd.
  15. alphatrack clone 4

  16. alphatrack clone 3

  17. alphatrack clone 2

  18. alphatrack clone 1

  19. 10bit pitchbend via encoder event

    Hi TK,   a pitchbend event with a 14bit value works, but only in one direction. I can control the value (volume fader in daw) with no value jumps, the encoder somehow "picks up" the value when I´m moving it, but it doesn´t get updated, while I move the fader inside the daw. But that´s alright for now. This is a little side project, I´m working on, while I´m away from my main project. I´m with my folks for 2 weeks and I was only allowed to take my SEQ4 with me (strict orders from my wife :wink: ). So I thought I could work an some other ideas.   Many thanks for your advice.   My regards
  20. 10bit pitchbend via encoder event

    Hi,   can anyone tell me if it is possible to send/receive a 10bit pitchbend event via encoder? I want to emulate a fader, that uses this.   The event has the form of "E9 xx yy" while xx refers to 3 LSBs and yy to 7 MSBs.   In Midiox it looks like this     when I drag the fader up.   Thanks.   my regards
  21. Spam in Recent Status Updates

    The last few days this forum seems to be overrun with Spam.   - Eudenut - cicEncorseTes - Siegspurine
  22. Long notes

    Hi,   you have two options:   1. set one parameter layer to control the gatelength of the notes (Menu -> Event : assign "Len." to a parameter layer). 2. enable sustained notes for the track (Menu -> Mode : sustain on/off).   my regards
  23. Upcoming MBHP_MF_NG module

    Hi Gergo,   this is a bit strange. Can you please check, if the MF module (I´m assuming, that the PIC already sits on the MF module) sends an upload request? You have to connect the MF module to the USB MIDI interface or to the LPC17 Core (Midi i/o 2) and power it up. If everything is alright, the PIC on the MF module sends an upload request that appears in the MIDI IN section in Mios Studio. It looks something like this:   [timestamp]  f0 00 00 7e 40 00 01 f7   And can you tell me, what kind of PIC you are using?   my regards
  24. Upcoming MBHP_MF_NG module

    Ahh, Thanks. Once again, I was looking in the wrong place. I still get lost sometimes in the Ucapps Galaxy.....
  25. Upcoming MBHP_MF_NG module

    Hi Gergo,   sorry for the delay, I´ve been held up.   First, you can´t install the bootloader via midi, I´m sorry if I misguided you in any way.   You only need the LPC17 Core and the MIDI 2x2 app to upload mios1.9g. You have to connect the MF module to MIDI IN/OUT 2. If you connected it to MIDI 1, Mios Studio would have given an error message saying, that both MIOS8 and MIOS32 Core had been detected. Of course you could use any other USB MIDI interface but this doesn´t work with all interfaces (There is a list somewhere, I have to search for it though).   If you tried to create Midi loopback and it didn´t work, there might be an issue with your midi in/out section on the LPC17 module.   If you are suffering from a hardware issue (bad soldering, misplaced parts maybe,....), then it would be a good idea to look at this document and go through the debugging steps.   Did reburning the PIC change anything?   my regards