Jump to content

TK.

Administrators
 View Profile  See their activity

  • Posts

    15,199

  • Joined

 Content Type 

Posts posted by TK.

  2. MIDIbox CV V2 Concept

    in MIDIfication

    Posted

    yes, the clock divider is still not implemented (and DIN sync input isn't implemented as well)

     

    Will be something for my winter vacation, where I (traditionally ;-) work on MBCV

     

    CC: all parameters are already available via NRPN, which is some kind of extended CC

    Is this sufficient?

     

    Best Regards, Thorsten.

  5. Neues Seq V4 Projekt inkl. 16x4 BLM

    in Deutsch

    Posted

    Hallo Sascha,

     

     

    • eventuell 2 AOUT_NG Module für 16 CV

     

    momentan wird nur ein einziges AOUT_NG Modul unterstuetzt, doch ich kann die Firmware so erweitern, dass auch zwei Module funktionieren.

     

    Zu den DOUTs: rechne schonmal mit drei weiteren Shift Registern fuer die Gates und Clocks - diese Ausgaenge werde ich naemlich in Zukunft auch hier zur Verfuegung stellen, so dass die "Fummelloesung" ueber J5A/B und den 74HC541 Buffern entfaellt.

     

     

    Frage: wie versorge ich eigentlich das STM32F4Discovery mit Strom?? Geht das nur über USB??

     

    USB ist eigentlich die einfachste Loesung, schliesse die MIDIbox einfach an einen USB Hub mit externem Netzteil (muss ja nicht an einen PC angeschlossen werden)

     

     

    Die AOUT soll ich ja eh mit externer +12/-12V/5V betreiben .. kann ich da nicht was basteln damit ich auch noch 7V für das Board bekomme?? Wenn ja, was??

     

    Falls das Board nicht ueber USB versorgt wird, kannst Du die 5V (nicht 7V!) an J2 anschliessen.

     

    Ansonsten gibt es gerade hier einen aktuellen Thread zu diesem Thema: 

     

     

    in der 16x4 BLM Doku habe ich gelesen, das die LEDs Duocolor sein sollen (ergo brauche ich 3 DOUT Module für die Kathode und die beiden Anoden) ... 
    Frage: brauche ich dann noch Dual-Color LEDs bei den GP LED's?? Eigentlich doch nicht, oder??

     

    brauchst Du nicht, die Firmware supported jedoch auch hier Duo-Color LEDs als Option.

     

     

    Frage 2: in der Doku steht auch das ich nur 2 Shiftregister für Button Matrix brauche ... wie schliesse ich die dann an??

     

    Auch das ist nur eine Option, die von Wilba's Frontpanel verwendet wird: http://www.midibox.org/dokuwiki/doku.php?id=wilba_mb_seq

     

    Ich habe leider keinen speziellen Schaltplan dafuer parat, werde ich bedarf mal aufmalen.

    Fuer die Matrix benoetigst Du jedenfalls 1 DIN Shift Register, 1 DOUT Shift Register, 64 1N4148 Dioden und 64 Taster.

     

     

    Gate Frage: ich brauche 5V Gates, dazu soll ich die Gates durch 74HC541 laufen lassen .. igendwo habe ich davon ne Zeichnung gesehen wie ich das basteln kann, finde die aber nichtmehr wieder ... :(

     

    Siehe oben - die Loesung mit dem 74HC541 ist demnaechst obsolet

    Ich bin gerade dabei, die Hardware zu vereinfachen - doch das ist ein langsamer Prozess... ;-)

    Mir ist bewusst, dass deshalb die vorhandene Dokumentation etwas verwirrend sein kann, auch hier muss ich nochmal ran.

    Im Grunde sollte ich klar unterscheiden zwischen "recommended" und "optionalen" bzw,. "historischen" Loesungen

     

     

    Frage: brauche ich eigentlich die Track 1-4 Buttons noch wenn ich eh das 16x4 BLM habe??

     

    Ja!!!

     

    Mit den zusaetzlichen Buttons kannst Du lediglich die Trigger setzen, doch die Parameter (bspw. Notenhoehe oder CV Werte) muessen weiterhin ueber die GP Encoder eingestellt werden.

     

    Es gibt uebrigens alternativen zur klassischen 4x16 BLM, siehe auch: http://www.midibox.org/dokuwiki/doku.php?id=mididocs:seq:usingblm

     

    Gruss, Thorsten.

  7. Problem with midimessages on Linux (Raspbian)

    in Testing/Troubleshooting

    Posted

    Hi,

     

    this "junk" are SysEx based debugging messages.

    Your MIDI parser should be able to handle (and ignore them).

     

    You can make the message visible with MIOS Studio, the messages should appear in the terminal window.

    They might give you important hints about the configuration.

     

    E.g. the first message says

    "Button 8 gedrueckt"

     
    and the second message says
    "Encoder 0: 1"
     
    Could it be, that these messages are generated from your .NGR or .NGC file?
     
    Best Regards, Thorsten.
     
     

  8. STM32F4 communication issues with MIOS Studio: no USB-MIDI available

    in MIDIbox Tools & MIOS Studio

    Posted

    Thanks for testing!

     

    Meanwhile I think that you are probably using a wrong Micro-USB cable, but I don't have enough experiences with the different cable types yet so that I'm not 100% sure.

     

    The cable should show a B (for USB Device), and not A (for USB Host):

    usb_micro_b.jpg

     

    Do you see a B letter on your cable?

     

    Independent from this, it seems to be possible to enforce B mode.

    Probably this wednesday I could give you some new test applications (the mini-app and a MIDIbox SEQ build) which fakes the B type.

     

    If this solves the issue, I will make it available as an option.

     

    Best Regards, Thorsten.

  13. Encoder & Buttons acting erratic.. no shorts,dead IC's,bad solderjoints... Please help!

    in Testing/Troubleshooting

    Posted

    Hi,

     

    so your sammichSID was working correctly before the update, some control elements stopped working after the update and you haven't done any modification on the hardware, right?

     

    Could it be that you've uploaded the wrong firmware?

    The release package contains a "setup_sammich_sid.hex" file, please only upload this one

     

    Best Regards, Thorsten.

  16. New newbie, hello from Brazil

    in MIDIbox NG

    Posted

    Hi Alex,

     

     

    1. Is there a way to extend the metal tip of the MFs so the I could have a space buffer between the top surface and the MFs? This way I intend to reduce the noise they produce (along with some acustic internal isolation.

     

    I've no experiences with this.

    If you've luck you will find special fader knobs with some kind of extension

     

     

    2. Would you advise me to start small and then go adding features as it goes? It´s a motorized fader´s control surface. But I thought I would start simple: 8 faders, 8 pan encoders and 2 bank buttons. Later adding Ledrings, solo/mute buttons and channerl displays.

     

    yes, please start it simple and extend over time before building a case.

     

    Motorfaders can first be tested standalone by connecting the MBHP_MF_NG module directly to the PC.

    Once they are working, continue with the STM32F4 based core module, try to get the communication between this core and MBHP_MF_NG working.

    Continue with bank buttons, add encoders, etc. step by step

     

    Best Regards, Thorsten.

  18. STM32F4 communication issues with MIOS Studio: no USB-MIDI available

    in MIDIbox Tools & MIOS Studio

    Posted

    This case really puzzles me!

     

    The MIOS Studio based MIDI IN/OUT monitor log was actually the most useful input, because it shows me that during the query STM32F4 responses with a delay of more than 1 second, which means that something really strange is going on in the application; actually the response should happen within 1..2 mS

     

    Let's continue to check different applications, here some prebuilt ones:

    http://www.ucapps.de/tmp/stm32f4_usb_test_files.zip

     

    Please report your observations on all three .hex files.

    (you can upload a .hex file in bootloader hold mode via MIOS Studio).

     

    app_skeleton_r2023.hex: minimal application with the old USB MIDI driver

    app_skeleton_unmodified.hex: minimal application with the new USB MIDI driver, USB Host and Device mode enabled

    app_skeleton_without_usb_host.hex: minimal application with the new USB MIDI driver, only Device mode enabled

     

    After the app has been started, just check the response by pusing the Query button, that's sufficient.

    (the MIOS terminal won't work since it isn't supported by the application)

     

    Best Regards, Thorsten.

  21. Mixer Map# currently selected jumps

    in MIDIbox SEQ

    Posted

    The mixer map association is fixed with the pattern, not with a track.

     

    The program change parameter layer type is not intended for your use case, it was a special request from a user who wanted to switch patches for each step.

     

    Actually you are asking for a program change value which should be configured somewhere in the track configuration, and sent whenever you are changing a pattern, right?

     

    Best Regards, Thorsten.

  23. STM32F4 Discovery / Core PCB Bootloader Question

    in Testing/Troubleshooting

    Posted

    Hi Robin,

     

    sometimes the LED flashes three times, that's normal and no problem.

     

    Since the LED is flashing, it's ensured that the bootloader is installed properly.

    No need to work with the ST Utility anymore.

     

     

    no response to MIOS STUDIO after installing Tutorial 5 with shorting pins to ground on J5A

     

    Connect a button and toggle it, or just disconnect/connect the cable.

    Whenever you are doing this a Note Event should be sent.

     

     

    makes me doubt whether the bootloader is installed.

     

    very unrelated to the Bootloader.

     

    I guess that you are able to select the MIDI IN/OUT port of your core module in MIOS Studio, right?

    And the Query button returns some board informations, right?

    This would mean that the application is running successfully.

     

    Did you already try out other tutorial applications?

     

    Best Regards, Thorsten.

  24. STM32F4 communication issues with MIOS Studio: no USB-MIDI available

    in MIDIbox Tools & MIOS Studio

    Posted

    Hi,

     

    It seems that even with the old driver USB communication is failing, which indicates that something is wrong with the hardware.

     

    E.g. the message which is sent by the core contains the "MIOS32" string as expected. MIOS Studio would thereafter request the board string, but it seems that the core doesn't respond anymore.

    I never heard about a similar case in the past.

     

    Next experiments:

     

    3) keep the bootloader mode (don't depress the blue button after the reset has been triggered with the black button), restart MIOS Studio and select the USB MIDI interface of the bootloader. Then press Query again, does it work?

     

     

    4) I also need to learn more about how you've built the core module.

    Are you using the MBHP_CORE_STM32F4 PCB, or a selfbuilt version?

     

    Experiment: unplug the STM32F4DISCOVERY board and connect the PA9 pin to the 5V input with a short cable like shown here:

    mbhp_core_stm32f4_standalone.jpg

     

    Try the Query with the MBSEQ application - result?

     

    Best Regards, Thorsten.

  25. STM32F4 communication issues with MIOS Studio: no USB-MIDI available

    in MIDIbox Tools & MIOS Studio

    Posted

    It's normal that the size has changed, because you've flashed a different (especially larger) .hex file.

     

    Next steps under MacOS:

     

    1) download the "USB Prober" app: http://www.ucapps.de/tmp/USB_Prober.zip

    It will display the USB devices, the list will be automatically refreshed whenever something changed in the system.

    Check if you can find the MIOS32 device in "normal mode", and when the bootloader is selected.

    If the device is displayed in "normal" mode, but not recognized by MIOS Studio (means: no MIDI available), we will continue debugging with this tool.

     

    2) try a MBSEQ release which is using an older USB device driver in MIOS32: http://www.ucapps.de/mios32/backup/midibox_seq_v4_083.zip

    If this one is working, we've to continue debugging by setting certain options in MIOS32

     

    Best Regards, Thorsten.

×
×
  • Create New...