Jump to content

TK.

Administrators
 View Profile  See their activity

  • Posts

    15,247

  • Joined

 Content Type 

Posts posted by TK.

  2. MIDIbox SEQ V4Lite

    in MIDIbox SEQ

    Posted

    The new version V4L.082 provides a new CLEAR button and sequence recording handling based on this discussion with Florian:

     

    MIDIboxSEQ V4L.082
~~~~~~~~~~~~~~~~~~

   o CLEAR button now allows to clear individual tracks with the GP buttons:
     - CLEAR+SEQ1: clear entire Seq1 + configuration (*)
     - CLEAR+SEQ2: clear entire Seq2 + configuration (*)
     - CLEAR+GP1: clear note triggers (values are kept but not played)
     - CLEAR+GP2: reset velocity values to 64
     - CLEAR+GP3: reset note length values to half step
     - CLEAR+GP4: clear Track 4 (Pitchbend + last CC lines)
     - CLEAR+GP5: clear CCs of Track 5
     - CLEAR+GP6: clear CCs of Track 6
     - CLEAR+GP7: clear CCs of Track 7
     - CLEAR+GP8: clear CCs of Track 8
     Same for GP9..16 for Seq2

     (*) track configuration won't be changed if 'PasteClrAll' set to 0 in MBSEQ_GC.V4 file

   o changed the track and layer assignment algorithm for CCs in recording mode:
     Previously new CC lines were recorded into Track 4, Layer B upwards.

     Now they are assigned the following way:
     - 1st CC line is recorded into Track 5, Layer A
     - 2nd CC line is recorded into Track 6, Layer A
     - 3rd CC line is recorded into Track 7, Layer A
     - 4th CC line is recorded into Track 8, Layer A
     - 5th CC line is recorded into Track 8, Layer B
     - 6th CC line is recorded into Track 8, Layer C
     - 7th CC line is recorded into Track 8, Layer D
     - 8th CC line is recorded into Track 7, Layer B
     - 9th CC line is recorded into Track 7, Layer C
     - 10th CC line is recorded into Track 7, Layer D
     - 11th CC line is recorded into Track 6, Layer B
     - 12th CC line is recorded into Track 6, Layer C
     - 13th CC line is recorded into Track 6, Layer D
     - 14th CC line is recorded into Track 5, Layer B
     - 15th CC line is recorded into Track 5, Layer C
     - 16th CC line is recorded into Track 5, Layer D
     - 17th CC line is recorded into Track 4, Layer B
     - 18th CC line is recorded into Track 4, Layer C
     - 19th CC line is recorded into Track 4, Layer D
     Same for Track 12..16 for Seq2

     Advantage: if only a few CC lines are recorded, we've dedicated tracks
     for PitchBend and CCs (Track 4-8, Layer A) which can be individually muted
     and cleared.
     Additional CCs populate the remaining layers from Track 8 backwards, so that
     PitchBend remains an individual track if not more than 17 CC lines are recorded.

     

    Best Regards, Thorsten.

  3. Doing some math

    in MIDIbox NG

    Posted

    The meta events are finally implemented: http://www.ucapps.de/mios32/midibox_ng_v1_030_pre4.zip

     

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

     

    So, there is an individual pitchbend (14bit or 7bit) for each CV channel which controls the fine pitch over the configurable pitchrange

     

    And there are individual octave and semitone transpose values for each CV channel as well.

     

    The example forwards the configuration value from EVENT_RECEIVERs to EVENT_SENDERs.

    Of course, you could also control the values from another source, e.g. forward from EVENT_AIN to EVENT_SENDER which then performs the meta operation.

     

    Best Regards, Thorsten.

  4. New STM32F4 core - how powerfull is it?

    in Design Concepts

    Posted

    Hi Johannes,

     

    the numbers came from the EEMBC benchmarks linked above, but I wouldn't take this comparison too serious for your application.

    E.g. if STM32F4 would only process 8bit values, the benefit isn't so high.

    Or if a benchmark just toggles a pin, it could be that the performance is almost the same depending on the peripheral bus architecture ;-)

    The truth is typically in the middle...

     

    Anyhow, as you already mentioned above, STM32F4 provides features such as 32bit calculation and DMA, which are advantageous for the use case, and if it turns out that it isn't possible to replace all Atmel CPUs, just take a cheap second one... :smile:

     

    There are some apps and tutorials in the respository which give you a good entry:

    - Output audio via the I2S based DAC in 024_i2s_synth: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftutorials%2F

    - C++ based synth engine (w/o audio, only controllers like LFO, ENV, etc): http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsynthesizers%2Fmidibox_sid_v3%2F

    - another C++ based CV engine: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fprocessing%2Fmidibox_cv_v2%2F

    - simple project to output audio samples: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsynthesizers%2FSD+card+sample+player%2F

     

    We've no specific application which would really get use of the STM32F4 processing power while generating audio - you are in the pole position! :smile:

     

    Best Regards, Thorsten.

  6. MIDIbox CV V2 Concept

    in MIDIfication

    Posted

    Today I spent some hours to make the WebSVN download button working - without success!

    This seems to be related to some webserver security settings. Due to my limited knowledge about such topics (I don't want to open a security hole!!!), I've disabled the download button now.

    Only proper way to download files is via a SVN client, such as Tortoise under Windows, or "svn" under MacOS/Linux.

     

     

    Currently only the global settings can be saved from the SCS.

     

    With the latest sources we are now able to save/load patches from the SCS! :)

    • move the SCS encoder or trigger GP button #2/3 to select the current patch
    • store/load a patch under Menu->Disk->Patch
    • A001 is loaded after startup

    Best Regards, Thorsten.

  10. New STM32F4 core - how powerfull is it?

    in Design Concepts

    Posted

    Hi,

     

    from my point of view, this is possible, but mainly depends on the effort you want to spend for the implementation.

     

    Performance-Wise the STM32F4 is a beast, this is what several MIOS32 benchmarks are showing.

    Typically STMF4 is 2 times faster than a LPC1769, and 3.5 times faster than a STM32F1

     
    Compare against ATmega: see for example EEMBC benchmark comparison charts: http://www.eembc.org/benchmark/index.php
    Typically STM32F4 is 5..6 times faster than a ATmega644
     
    You are right, that by moving to a 32bit architecture additional performance improvement can be expected, and you can take advantage of it and increase the sample rate & accuracy.
     
    If performance is still not sufficient, then consider to replace timing critical routines by hand optimized assembly code.
    This is what Xavier did in his Preen2 FM project: http://ixox.fr/preenfm2/
     
    Best Regards, Thorsten.
     

  13. MIDIbox CV V2 Concept

    in MIDIfication

    Posted

    Not really (too difficult)

     

    I could provide a save_patch and load_patch command in the terminal if this helps

    The first patch will be loaded automatically after startup - and will then contain your default settings.

     

    Best Regards, Thorsten.

  16. Song sync issue

    in MIDIbox SEQ

    Posted

    Thanks for the files!

    I was able to reproduce the sync issue at my side, but after 1 hour of analysis I still haven't fully understood why it happens.

    However, I found a workaround which might be acceptable: if a pattern is already loaded and actively running, it won't be reloaded anymore.

    I guess that most users will prefer this handling anyhow, because interactive changes in the pattern won't get lost.

    Please try this version: http://www.ucapps.de/mios32/midibox_seq_v4_081_pre3.zip

    Best Regards, Thorsten.

  17. Doing some math

    in MIDIbox NG

    Posted

    Than longer I'm waiting, than better ideas... ;-)

     

    Meanwhile I think that the best way would be to give direct access to the AOUT_PinSlewRate*, AOUT_PinPitchRange*, AOUT_PinPitch* functions of the AOUT driver via meta events, so that any controller could change them directly.

     

    TODO marker

     

    Best Regards, Thorsten.

  18. STM32F4 Discovery

    in Design Concepts

    Posted

    The most simple strategy would be the following:

    - download the repository into a separate directory and change your MIOS32_PATH accordingly

    - change the PLL frequency configuration in mios32/STM32F4xx/mios32_sys.c, because STM32F401 can only be clocked at 84 MHz

    I assume that the corresponding SFR configuration can be found somewhere in the internet

    - compile a new bootloader under bootloader/src with "make STM32F4DISCOVERY"; this will refresh mios32/STM32F4xx/mios32_bsl_STM32F4DISCOVERY.inc

    (this step requires a perl installation)

    - recompile bootloader/updater and program it into the flash

     

    If this already helps, let me know about the changes and I will consider MIOS32_PROCESSOR=STM32F401VC in the main branch, so that you can use a common repository again.

     

    Best Regards, Thorsten.

  22. trying to understand core32 options for SEQV4

    in MIDIbox SEQ

    Posted

    Hi,

     

     

    I assume since this is for the SEQ with the SD card I would just leave the arrays off.

     

    yes, not required for J16

     

     

    Also I cannot seem to determine what the Jumper selection would be as I find this in the guide. What is expected here?
    J24/J25/J26    3    5V/3.3V supply options for serial ports TODO

     

    J16 (SD Card) has to be supplied with 3.3V, therefore J24 should select 3.3V

    J25 and J26 should select 5V

     

     

    Again, I understand that these arrays are not installed and I could just skip this section

     

    No, please install 220 Ohm arrays for J8/9 and J19

     

     

    I plan to have an external power but not just yet. If a populate these parts but just leave J17 in place for now will it still work? I guess I could just remove the jumper when I am ready for external power.

     

    yes

     

    Best Regards, Thorsten.

  24. Controlling OP-1 with SEQV4 ?

    in MIDIbox SEQ

    Posted

    MBSEQ isn't a USB host device as well.

     

    This could become a feature of the STM32F4 based "MIDIbox SEQ V4 Plus", but it has low priority at my side (because I know that this will result into some remote troubleshooting for devices which I don't own by myself)

     

    Best Regards, Thorsten.

×
×
  • Create New...