Jump to content

TK.

Administrators
  • Posts

    15,247
  • Joined

Posts posted by TK.

  1. You've to use sdcc 2.8.0, please don't try any other version because only this release has been qualified.

    A linux version can be downloaded from: http://sourceforge.net/projects/sdcc/files/sdcc-linux-x86/2.8.0/

    The package contains a INSTALL.txt file, just follow the instructions.

     

    Once SDCC has been installed (e.g. under /usr/local/bin), the "sdcc --version" command should return

    SDCC : mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08 2.8.0 #5117 (Mar 23 2008) (Mac OS X i386)

     

    If it returns another string, your PATH variable doesn't reference the correct binary, in this case try to uninstall the other versions that you've installed so far.

     

    Once this has been done, the original mios8 makefiles will work without modifications (no need to set special flags etc.)

     

    Best Regards, Thorsten.

  2. Ok, I can add these special LED functions without much effort.

     

     

    Feature request: CV inputs can act as momentary or latching "switches" to enable outputs or operate internal controls. As a crude example, see Doepfer's A-151 sequential switch module. (This just distributes a signal to one of four outputs stepped through by a clock.)

     

    This is already possible in conjunction with the modulation matrix! :)

     

    Several operators are available, such as >=, <= but also S&H (Sample & Hold)

    The operations can be applied on two analog inputs, but also between an analog input and an internal modulation source (such as a LFO or ENV)

     

    Best Regards, Thorsten.

  3. Yes, V1.017 is the latest one.

     

    Could you please try the following:

    press & hold the blue button on the STM32F4DISCOVERY board, and then shortly trigger the black button (to reset the device)

    Keep the blue button pressed! This enforces bootloader mode.

     

    Now re-open MIOS Studio. Maybe you've to select a new MIDI IN/OUT device (but mostly the previous setting will work as well).

     

    Check query (blue button still pressed) - does this work?

    Upload a firmware (blue button still pressed) - does this work?

     

    Release the blue button after firmware upload so that the application will be started.

     

    Best Regards, Thorsten.

  4. I spent some time to make this happen: MBSEQ finally provides a "Track Instrument" configuration page:

     

       o new page: "Track Instrument"
         Can be selected with MENU->EVNT->Trk Inst (GP #8) or from the main page (after Track Event item)
         Allows to configure the MIDI port, channel and instrument name.
    
       o the new Track Instrument page also allows to select Program Change and Bank (Low/High byte)
         If activated, these parameters will be sent when the sequencer is started and on pattern changes.
         Please note: a program and bank change can stall your synth so that the first note could be delayed!
         Use this function only when the device can handle patch changes quickly!
    

    could you please help me to check if it works as expected?

     

    Prebuilt firmware: http://www.ucapps.de/mios32/midibox_seq_v4_087_pre5.zip

     

    Best Regards, Thorsten.

  5. Yes, a CTRLR based panel is a feasible option - it will be a lot of work for you, but with the Lemur based solution it has been proven that the NRPN based communication is working, and it's also a good reference how to organize the layout.

     

    Best Regards, Thorsten.

  6. Hi Nate,

     

    MIDIO128 only supports 8x8 matrices, but up to 16 matrices can be defined.

    So, you could combine four 8x8 matrices to two 8x16 matrices, although you will only need 4x11 connections per keyboard.

    In addition the firmware allows you to map map different key values to the scanned inputs to align this with your keyboard layout.

    Channel can be selected as well.

     

    So: you would need:

    - 1 x MBHP_CORE_STM32F4 (alternatively MBHP_CORE_LPC17)

    - 2 x MBHP_DIO_MATRIX (best choice in your case: 4 DOUT and 4 DIN SRs)

    - 1 x MBHP_AINSER64

    - the components for the SCS (1 rotary encoder, 6 buttons, a 2x20 CLCD)

     

    Best Regards, Thorsten.

  7. Hi Mark,

     

    the encoder spec (http://www.cliffuk.co.uk/products/encoders/EncoderSpec.pdf) looks fine, it will work :)

     

    Note that MIDIbox NG allows to connect up to 16 buttons to J10A/B, see also this configuration example: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fdiocfg_1.ngc

     

    This means that you only need a single MBHP_DINX4 module for 16 encoders, the two buttons can be connected to J10A.D0 and D1, and with "DIO port=J10A emu_din_sr=5" they will be available as BUTTON:33 and BUTTON:34

     

    Best Regards, Thorsten.

  8. A new version is available:

     

    MIDIbox NG V1.032
    ~~~~~~~~~~~~~~~~~
    
       o support for mathematical operations in .NGR script.
         They have to be surrounded with square-brackets ([...])
         Syntax: [<left-operand><operator><right-operand>]
         Example:
            - set LED:2000 [LED:2000 + 1]
              will increment the value stored in LED:2000
            - set LED:2000 [LED:2000 - 1]
              will decrement the value stored in LED:2000
    
         Note that nested operations are supported as well, such as:
            - send CC USB1 1 [LED:2000 + [LED:2001 + [LED:2002 + LED:2003]]]
    
         More examples in cfg/tests/runscr5.ngc
    
         Support operators: + - * / % & | ^
    
    
       o number of scanned SRIOs now configurable in .NGC file
         with 'SRIO num_sr=<1..32>'
    
         By default 32 DIN and DOUT shift registers are scanned, which
         result into an update rate of ca. 420 uS on a STM32F4 based core.
    
         With (for example) 'sr_num=8' only up to 8 DIN and 8 DOUT SRs will
         be scanned anymore, but the update rate is reduced to ca. 110..120 uS
         (a little bit more than a quarter due to SR handling overhead)
         
    
        o corrected DebounceCtr parameter (value was not passed to MIOS32)
          Now also part of the SRIO configuration, use:
          SRIO debounce_cycles=<1..255>
    
        o added new meta event "KbBreakIsMake:<keyboard-number>" which will
          already trigger a note event when the break contact is activated
          (nice for playing organ style).
          Trigger it from a toggle button function as shown in cfg/test/kb_5.ngc
          Can be optionally set from the terminal as well with following
          command: "set kb <keyboard-number> break_is_make <on|off>"
          (e.g. "set kb 1 break_is_make on")
    
       o added ain_mode=Toggle for AIN and AINSER events.
         Similar to ain_mode=Switch it can be used if buttons are connected to analog inputs.
         The event will toggle between the min and max value.
    
       o .NGR: added "set_no_dump" command. It allows to change the "no_dump" flag
         which specifies if an EVENT_xxx should be sent during a DumpSnapshot.
         This feature can be used to handle different snapshot setups.
    
       o STM32F4: support for bootloader "enforce_usb_device" flag
    

     

    Best Regards, Thorsten.

  9. Hi,

     

    too difficult at my side...

     

    However, if I would provide access to the "no_dump" flag in the .NGR file, you would be able to enable/disable the flag for the affected events before restoring the snapshot via "exec_meta SetSnapshot <number>", "exec_meta LoadSnapshot" and "exec_meta DumpSnapshot".

     

    Best Regards, Thorsten.

×
×
  • Create New...