Jump to content

TK.

Administrators
 View Profile  See their activity

  • Posts

    15,247

  • Joined

 Content Type 

Posts posted by TK.

  1. 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.

  6. 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.

  9. 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.

  11. 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.

  14. 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.

  16. 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.

  17. 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.

  18. 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.

  19. MIDIbox KB

    in MIDIfication

    Posted

    New release:

     

     

    MIDIbox KB V1.014

    ~~~~~~~~~~~~~~~~~

     

       o added "break_is_make" option which allows to trigger a note when the break

         contact is activated (nice for playing organ style)

     

     

    MIDIbox KB V1.013

    ~~~~~~~~~~~~~~~~~

     

       o the MIDI router forwards SysEx messages regardless if channels are filtered,

         or "All" is used. It's ensured that messages are only sent once if multiple

         router nodes forward to the same destination port.

     

       o added "make_debounced" parameter: Note Off will be played when the

         Break contact has been released, and not when the Make contact has been released.

     

       o support for MBHP_CORE_STM32F4

     

     

    Best Regards, Thorsten.

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

    in MIDIbox Tools & MIOS Studio

    Posted

    I don't think that you need a new STM32F4.

     

    It would be interesting if you still notice the same issue under MacOS.

    Please use one of my latest prebuilt binaries for reference, e.g. this one: http://www.ucapps.de/mios32/midibox_ng_v1_032_pre4.zip

    You can upload the .hex file directly with the ST Link tool (under Windows) - it contains the bootloader + the MIDIbox NG application.

     

    If no success: we should continue the troubleshooting under MacOS (I will give you further instructions in this case)

     

    If success: try also under Windows.

    If the USB device is not recognized, you could uninstall the MIDI driver assigned to the USB port somewhere in the system settings, and re-connect the USB cable. This enforces a driver re-installation which might help.

     

    Btw.: did you already try another USB cable?

    I remember that there a Micro-USB cables which are only intended to supply power, e.g. for recharging mobile phones. They can't be used for the USB connection itself!

     

    Best Regards, Thorsten.

  22. MB CV2 AOUT Gates

    in Testing/Troubleshooting

    Posted

    Hi David,

     

    yes, the second AOUT based gate should work (but I haven't tested it yet - I only use DOUT pins in conjunction with a AOUT_NG board).

     

    However, I just checked the MIDI channel selection with the Lemur patch and noticed that the value display wasn't accurate.

    In a certain range Channel 2 was displayed, but actually Channel 1 was still selected.

    I fixed this (for all dials) by surrounding the calculated value with floor() - this seems to work now

     

    The updated Lemur template can be found in the repository (I hope that I haven't damaged something because I manually edited the .jzml file instead of doing the changes in the editor)

     

    DOUT pins: there is no interconnection test available for MIOS32, but maybe the Lemur update will already help to clarify this.

    Note that the first gate is available at D7, the second at D6, etc...

     

    Best Regards, Thorsten.

  24. Sammich preset upload: Only 2 patches take?

    in MIDIbox SID

    Posted

    Hi,

     

    it seems that you are trying to upload SysEx with a bad MIDI interface.

    Please check the blacklist: http://www.midibox.org/dokuwiki/doku.php?id=midi_interface_blacklist&s[]=whitelist

     

    There is also a whitelist: http://www.midibox.org/dokuwiki/doku.php?id=midi_interface_whitelist

    The recommended "least cost" interface is Neusonik uMIDI/O22, available for 15 EUR e.g. from Thomann: http://www.thomann.de/de/neusonik_umidi_o22.htm

     

    Best Regards, Thorsten.

  25. Newbie problem with Fatar keyboard- help

    in MIDIbox NG

    Posted

    Hi Bartosz,

     

    this is a quite old posting, did you solve this meanwhile?

     

    I'm a bit unsure if a SD Card will be required for these tests - it shouldn't, but to be honest: I never tried out a keyboard without writing the definitions into a .NGC file.

     

    It might be required to enter "RESET_HW" before these commands to ensure that no other configuration overlays the keyboard functions.

     

    Best Regards, Thorsten.

×
×
  • Create New...