Jump to content

TK.

Administrators
  • Posts

    15,247
  • Joined

Posts posted by TK.

  1. I got some complains about the rotary encoder behavior in the MBSID firmware lately, and think that this can be changed & optimized in the firmware easily.

     

    Different variants are possible - let's try to find the best suitable solution together!

    Who would be interested to test some variants?

     

    Best Regards, Thorsten.

     

  2. Hi,

     

    this hidden "remote control" feature exists since several years. My intention was to access "slave cores" from the UI of a "master core", this would make the design scalable. But it turned out, that the setup and handling is too cumbersome, therefore I never released this (and actually I considered to remove it from the firmware, since I don't use this feature by myself and therefore can't check if it is still working...)

     

    For which purpose do you want to send strings?

    And should they be displayed as a temporary, or permanent message on screen?

     

    Best Regards, Thorsten.

  3. Der STM32F4 Bootloader unterstuetzt nur USB und kein UART basiertes MIDI, weil dafuer der reservierte 16k Speicher zu klein ist.

     

    Der Query funktioniert jedoch, und dies ist auch der einfachste Weg, um eine bidirektionale MIDI Verbindung unabhaengig von der Applikation zu testen.

    Wenn der Query nicht antwortet, ist etwas mit der Hardware nicht in Ordnung.

     

    Ich habe das auch gerade mal mit meinem midiSport 2x2 ausprobiert - funktioniert problemlos.

     

    Gruss, Thorsten.

  4. Hi Tom,

     

    thanks for the hint!

    I've updated the MBHP_CORE_LPC17 page, it now suggests the download of version 5.2.6

    Is this the version that you tried (successfully?)

     

    I'm not aware of a schaeffer version of the frontpanel.

    If you create one, please share it here and I will publish it at the MBSEQ V4L page.

     

    Best Regards, Thorsten.

  5. I tested this at my side with:

    set router 1 IN4 all USB1 all
    set router 2 USB1 all OUT4 all
    

    and it works.

    Need more informations to understand the issue.

     

     

    MF: the Motormix events will be filtered automatically.

    Don't use the router for this, configure the MF module instead and forward/convert events via EVENT_MF like shown in the configuration examples.

     

    Best Regards, Thorsten.

  6. I was able to fix this earlier :)

     

    New release is available now:

    MIDIboxSEQ V4.083
    ~~~~~~~~~~~~~~~~~
    
       o fixed potential hang-up during pattern change which was introduced with V4.081
    

     

    I can't see the euclid generator issue, and need some more detailed informations to reproduce this at my side.

     

    Best Regards, Thorsten.

  7. Did you follow the configuration steps described in this file?

    http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fmf_multi.ngc

     

    Which informations are missing (I will add them)

    E.g. the MF configuration can be found in this file as well - it has been tested by multiple users.

     

    For the case you haven't considered this yet: always ensure that you are using the latest MBNG version.

     

    Best Regards, Thorsten.

  8. No, this was actually a clever question: especially the "sine" function allows you not only to check the calibration values, but it also checks if the motor voltage provided by your PSU is robust enough when all faders are moved concurrently.

     

    If the sine function fails as well, then the problem is related to power integrity.

    If the sine function is working, further debugging is required for the MIDI event forwarding (a MIDI monitor could help to troubleshoot this)

     

    Best Regards, Thorsten.

  9. Die MIDI OUTs des STM32F4 sind im Open Drain Mode, deshalb sollten 220 Ohm statt 47 Ohm Widerstaende verwendet werden, ausserdem wird dann M+ der MIDI Buchse via 220 Ohm an 5V (und nicht an 3.3V) angeschlossen.

    5V sind am Pin J11E:Vd verfuegbar.

     

    Ansonsten sollte es aber so funktionieren. Ich erwarte keine Probleme am MIDI IN, wenn Du den Optokoppler so verschaltest.

     

    Gruss, Thorsten.

  10. I appreciate your activities! :)

     

    Please consider to make a backpanel for the new MBHP_CORE_STM32F4 module instead of MBHP_CORE_LPC17 (the new module is already available in SmashTVs shop)

     

    I consider to work on an enhanced version (called "MIDIbox V4 Plus") which will utilize the additional resources of the STM32F4

     

    Best Regards, Thorsten.

  11. Let's call it an imperfection... ;)

    In this version inverted and reduced ranges should be supported properly: http://www.ucapps.de/mios32/midibox_ng_v1_030_pre5.zip

     

     

    Rotated LCD view: would only work with graphical LCDs, and would require a special LCD driver (not the universal one) which has to be developed for the specific display.

    The driver would also consume some memory (which has to be removed from the pool), since direct writes to the display are not possible anymore.

    And it would slow down display output.

    So: not supported from my side.

     

    Best Regards, Thorsten.

  12. Hi Johannes,

     

    I've no comparison available for integer vs. float.

     

    But if the required shift operation is your only concern, I assume that fixed point is still faster.

    A shift operation (regardless how many bits) takes only 1 cycle.

    See also: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0439b/CHDDIGAC.html

     

    I know that you don't like this tip, but anyhow: consider to use the special Cortex-M4 DSP instructions for fixed point operations (see also the bottom of the page that I linked above).

    I guess that they can be embedded into C code by using intrinsics.

    And in order to keep CPU independency, you could write another set of intrinsics which are doing the same operations with native C code.

     

    Best Regards, Thorsten.

  13. Sorry for the trouble! :-(

     

    This was due to a corrupted build which can only happen with the special Makefile setup of MBSEQV4L (it uses some source files of the midibox_seq directory).

     

    I fixed the release script, the binary is working now.

    Version: V4L 082a

     

    Best Regards, Thorsten.

  14. In the last months I created many preliminary releases, it's time for a new official release: V4.082

     

    From the ChangeLogs:

    MIDIboxSEQ V4.080
    ~~~~~~~~~~~~~~~~~
    
       o SELECT+PASTE transfers the parameter layer, which was active during COPY, to
         the current parameter layer.
         If a drum track is selected, it's doing this for the trigger layer (and not
         for the parameter layer).
    
       o SELECT+CLEAR clears only the current parameter layer.
         If a drum track is selected, it's doing this for the trigger layer (and not
         for the parameter layer)
    
       o it's now possible to control the track steps with CCs.
         Each track has a dedicated CC which has to be configured in the
         MIDI->Ext.Ctrl page.
    
       o it's now possible to turn off the track clock by enabling the new "Manual"
         mode in the DIVIDER page. Once enabled, a step will only be played if:
         - manually triggered in the MANUAL page
         - set with the new CC based step control feature (MIDI->Ext.Ctrl page)
    
         Use cases:
         - predefined MIDI events, stored in the track layers, should be manually
           triggered (and not sequenced).
           E.g. in conjunction with a sampler, you could set each step to a note
           which "fires" a certain sample. In addition, you can fire CCs,
           Program Change, Aftertouch etc. from the MANUAL page.
    
         - the track should be controlled from an analog modulation source (e.g. a
           sawwave from a LFO). MIDIbox SEQ doesn't provide analog inputs, so that
           an external CV-to-MIDI interface is required.
           Note that this interface also has to scale the CC value over the desired
           step range. If the modulation source should sweep over step 1..16, then
           the CV-to-MIDI interface has to scale down the converted value to the
           CC value range 0..15!
    

     

    MIDIboxSEQ V4.081
    ~~~~~~~~~~~~~~~~~
    
       o added USB MIDI workaround for Windows
    
       o fixed synchronisation issue in Song mode
    

     

    MIDIboxSEQ V4.082
    ~~~~~~~~~~~~~~~~~
    
       o Options in LIVE page are now stored in session specific MBSEQ_C.V4 file
    
       o initial release for MBHP_CORE_STM32F4
    

     

    Best Regards, Thorsten.

×
×
  • Create New...