Jump to content

TK.

Administrators
 View Profile  See their activity

  • Posts

    15,198

  • Joined

 Content Type 

Posts posted by TK.

  2. Optimizing Encoder Behavior in MBSID Firmware

    in MIDIbox SID

    Posted

    Yes, I read it, and think it makes sense to change the behaviour, so that incoming CC values will also be stored in the edit buffer.

    Only value changes caused by ModWheel, Velocity, Aftertouch, Knobs and Wavetable shouldn't be stored.

    It will be an option which is enabled by default (because I guess that most people will like it), and could be disabled in setup_*.asm (for the minority who doesn't like it).

     

    In addition, I will add a "CC dump request" which will allow to synchronize a MBNG with the current patch CCs.

     

    Behaviour of SHIFT button will be configurable as well, and switched back to the original "slow" switching like in pre-42 releases.

     

    Back to topic: help to find best matching speed parameters, please! ;-)

     

    Best Regards, Thorsten.

  3. Optimizing Encoder Behavior in MBSID Firmware

    in MIDIbox SID

    Posted

    In this case I would propose that you try the testmode in the new firmware.

    Help to find better matching values and give feedback about your thoughts.

     

    With good settings the value range shouldn't matter, it should always feel "good" and "usable".

     

    For encoders I don't really see an advantage if I would try to translate a relative or passthrough (resp. "snap" or "soft-takeover") mode.

    This wouldn't solve the problem that we actually only need better speed parameters.

     

    Best Regards, Thorsten.

  5. Enable MIDI IN4 and MIDI-Routing

    in MIDIbox NG

    Posted

    Of course, it will get motormix values over USB2 since you've configured it as the "config_port".

    I assume, that you get the CC/Pitchbend via USB1, right?

     

    Select another "config_port" for configuration purposes which isn't used by your DAW.

     

    Best Regards, Thorsten.

  6. Optimizing Encoder Behavior in MBSID Firmware

    in MIDIbox SID

    Posted

    @3090: you are mixing pots with rotary encoders - the modes that you are explaining are already supported by typical MIDIbox based controllers since more than 10 years; they are well known to me.

     

    But pots are not supported by MIDIbox SID. Please let's focus to improve the existing hardware!

     

    It would be helpful, if only people join the discussion who already own a MIDIbox SID, know the current behaviour, and help to evaluate various software options.

    Otherwise I fear that I'm more busy with explaining unnecessary details (the "what" and "why") instead of doing the actual work. :-/

    Please also note that I'm not planning to develop a new hardware.

     

     

    @jrp: please find a prebuilt binary with the new "DEFAULT_TESTMODE_ENC_SPEED" under:

    http://www.ucapps.de/mios/midibox_sid_v2_044_enctest1.zip

     

    It's enabled by default (and has to be disabled to get MBSID "productive" again).

     

    All encoders are configured with the same speed mode which doesn't vary automatically depending on the value range (as they are normally doing).

    You can change the speed settings by pressing the SHIFT button + GP button 1 and 2 (to toggle modes and speeds)

     

    Please try to find best matching mode/speed values for following value ranges:

    - CutOff (12bit value range)

    - Resonance (8bit value range)

    - Depth (bidir 7bit value range)

    - Sustain (4bit value range)

     

    I would like to know two sets: one set of mode/speed values for "normal behaviour", and another one which should be used later to slow down the incrementer (when the SHIFT button is pressed).

     

    Best Regards, Thorsten.

  10. Optimizing Encoder Behavior in MBSID Firmware

    in MIDIbox SID

    Posted

    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.

     

  11. SEQ V4 firmware question

    in MIDIbox SEQ

    Posted

    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.

  12. STM32F4Discovery MIDI Anschlüsse und PCB-Layout

    in Deutsch

    Posted

    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.

  13. MIDIbox SEQ V4Lite

    in MIDIbox SEQ

    Posted

    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.

  14. Enable MIDI IN4 and MIDI-Routing

    in MIDIbox NG

    Posted

    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.

  15. MIDIbox SEQ V4 Release + Feedback

    in MIDIbox SEQ

    Posted

    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.

  16. Upcoming MBHP_MF_NG module

    in MIDIbox HUIs

    Posted

    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.

  21. Upcoming MBHP_MF_NG module

    in MIDIbox HUIs

    Posted

    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.

  24. STM32F4Discovery MIDI Anschlüsse und PCB-Layout

    in Deutsch

    Posted

    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.

  25. MIDIbox SEQ Aluminium Desktop Case

    in Bulk Orders

    Posted

    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.

×
×
  • Create New...