Jump to content

TK.

Administrators
 View Profile  See their activity

  • Posts

    15,246

  • Joined

 Content Type 

Posts posted by TK.

  1. Where can I find the sources for MIOS Studio 2.4.6?

    in MIDIbox Tools & MIOS Studio

    Posted

    What do you mean with "live" version?

    Do you mean the sources that I used during a certain release? Then just check the SVN log entries.

    E.g. the last release was based on r1832 of the repository, but when you check it with the latest r number, you won't find changes.

     

    Juce: just unpack tools/juce/unpack_me.zip

     

    Only use this juce version, don't try another one because it might be incompatible.

     

    Best Regards, Thorsten.

  3. Display options

    in MIDIbox NG

    Posted

    No, this display is definitely not KS0108 compatible.

    E.g. it would require 8 CS inputs for 8 segments... such a higher number doesn't make much sense, therefore KS0108 isn't used for large display sizes anymore.

    The display interface looks more like a T6369c

     

    Best Regards, Thorsten.

  6. External control of steps

    in MIDIbox SEQ

    Posted

    Here some first updates for testing at your side:

    -> http://www.ucapps.de/mios32/midibox_seq_v4_080_pre2.zip

     

       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!

     

    Note that the scaling over track length that I mentioned earlier doesn't take place since it's problematic in some cases (e.g. if the value slowly sweeps over the CC value range).

    Instead, scaling has to be done externally.

     

    In MBNG you would do this with:

    # in MIDIbox SEQ V4, we've configured CC#16 for Step Control in the MIDI->Ext. Ctrl page

# AINSER8 hardware
AINSER n=  1   enabled=1  muxed=0  cs=0  resolution=7bit

# Track 1: control step 1..16
EVENT_AINSER id=  1  type=CC  chn= 1 cc= 16 range=  0:15

# Track 2: control step 1..32
EVENT_AINSER id=  2  type=CC  chn= 1 cc= 17 range=  0:31

# Track 3: control step 1..64
EVENT_AINSER id=  3  type=CC  chn= 1 cc= 18 range=  0:63

# ... etc.

     

    Best Regards, Thorsten.

  7. Display options

    in MIDIbox NG

    Posted

    The T6369c has a very poor performance and requires buffering in memory. Therefore it's not part of the universal driver (it's a dedicated driver), and probably compile will fail due to unavailable RAM resources.

     

    Best Regards, Thorsten.

  9. I'm confused about pattern length and synchronization

    in MIDIbox SEQ

    Posted

    Hi,

     

     

    apparently there can be only one guide track per song?

     

    yes

     

     

    Could you explain a bit further what the "normal operation" of the MBseqv4 is, and how guide track changes that?

     

    It's accurately explained in the ChangeLog:

     

    • Song Mode now provides a "Guide Track" which can be configured by pressing SELECT in SONG page: the length of this track defines the loop length and once the last loop has been played, all tracks will be synchronized to step 1.
      This allows to program breaks with a step length which is independent from the measure.
    • The "Guide Track" now synchronizes tracks and pattern changes independent from the "steps per measure" option

    So, the guide track is nothing else than a "steps per measure" replacement for song steps.

    The length of the guide track defines the loop length for the song position, and this gives you a high flexibility.

     

     

    Apparently you can have lots of tracks with different lenghts & dividers run in parallel, but somehow they have to match the overall measure, right?

     

    Yes.

    Resp. if the guide track is used, they have to match with the length of this track (which defines the measure)

     

    Best Regards, Thorsten.

  13. External control of steps

    in MIDIbox SEQ

    Posted

    Aha, I should have mentioned that I was considering using an AIN. Would that be feasable i.e. could MBSeq scan AINs? I will make sure that the modular voltages don't exceend the AIN specs of course....

     

    J5 is already allocated for Gate outputs, and another problem would be the bad accuracy of STM32 and LPC17 ADCs...

    I could support an MBHP_AINSER8 module instead, but this could affect the performance of the sequencer :-/

    Therefore the usage of CCs is maybe the better approach, just use a second core for the conversion (you could also use it for other purposes as well)

     

     

    Were you referring to the idea of using DINs to step through the track with this last comment?

     

    yes.

    16 DIN pins to step the 16 tracks individually, right?

     

     

    While we are here: multiple clock/divider outputs independent from the tracks would be awesome. Maybe some day....

     

    If it's ok to assign a whole DOUT SR (= 8 outputs) for this function, I could easily add this.

    What type of clock outputs would be for interest?

     

    - PPQN/24 (DIN clock)

    - 64th

    - 32th
    - 16th
    - 8th
    - 4th (1 clock per bar)
    - 1/2
    - 1 (4 bars)
     
    Since PPQN/24 is redundant (already available at J28), it could be replaced by another interesting clock - any proposal?

     

    Best Regards, Thorsten.

  14. KS0108-LCD Issue

    in MIOS programming (C)

    Posted

    @John: KS0108 has a special treatment where lcd_num_x doesn't play a role. J28 always has 4 CS lines enabled.

    Actually it's a part of the universal driver which needs to be overworked, so that CS lines are specified with lcd_num_x

     

    However, I changed MIOS32_LCD, so that lcd_width 255 results into the actual width 256

    This coding could become important in future. E.g. if there are displays which support 320 pixel, I could use the number 254 for this, etc.

     

    Best Regards, Thorsten.

  15. AVR-Synthesizer "WAVE 1"

    in Deutsch

    Posted

    Hallo Rolf,

     

    wenn Du bereits ein STM32F4DISCOVERY Board hast, koenntest Du bspw. mit diesem Tutorial direkt loslegen, einen Synthesizer zu programmieren: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftutorials%2F024_i2s_synth%2F

     

    MIOS32 bietet ja schon alles was man dafuer braucht. Vor allem die I2S und MIDI (USB und UART basierend), scannen von Buttons, Encodern, LEDs, verschiedene LCD typen (character oder graphisch), SD Card, usw. usw.

     

    Die Toolchain basiert auf gcc mit nanolib: http://www.midibox.org/mios32_toolchain/

    Und zum Aufladen von Code, sowie zum Debuggen via printf verwendet man MIOS Studio: http://www.ucapps.de/mios_studio.html

     

    Alternativ koennte man auch mit Eclipse debuggen (falls Du eine IDE suchst, mit der man bspw. Breakpoints setzen kann, waehrend der Laufzeit Variablen abrufen kann, usw) - irgendwo gab es mal ein Thread zu diesem Thema.

     

     

    Die ATMEL MCU's haben ihren Vorteil in der Menge der angebotenen internen Peripherie und sowie einen großen Funktionsumfang. Im Vergleich dazu sieht so ein schneller STM32F4 etwas alt aus.

     

    Welche Peripherals bietet die Atmel MCU, die nicht im STM32F4 enthalten sind?

    (wenn man mal vom Audio DAC absieht, doch ein externer DAC ist u.U sogar vorteilhaft, weil man die Spannungsversorgung besser gegen Stoerungen aus der digitalen Spannungsdomaene isolieren kann)

     

    Gruss, Thorsten.

  17. urgent need help for problem for the new firmware updater on my sammichSID

    in MIDIbox SID

    Posted

    This wasn't the upload window, but the MIDI IN monitor window... however - this message:

     

    [865654.760] f0 00 00 7e 40 00 0e 03 32 f7

     

    indicates a checksum mismatch!  :shocked:

    (see also http://svnmios.midibox.org/filedetails.php?repname=svn.mios&path=%2Ftrunk%2Fdoc%2Fmios%2Fmios_sysex_implementation.txt )

     

    It seems that the Behringer MIDI interface doesn't work reliable!

    With some luck it will work when you are trying it multiple times (10..20 tries could lead to success)

    But I fear that you need another MIDI interface.

     

    Btw.: Behringer is already on the blacklist: http://www.midibox.org/dokuwiki/doku.php?id=midi_interface_blacklist

     

    Best Regards, Thorsten.

  25. I'm confused about pattern length and synchronization

    in MIDIbox SEQ

    Posted

    I remember that somebody else had similar problems, and we solved this with the "guide track" function.

    In order to set a guide track, press the SELECT button in SONG page and change it with GP encoder 11 - this item is only visible in song mode, not in phrase mode.

     

    The guide track will take over the control of the song step. E.g. if the selected guide track has a length of 72, the sequencer will switch to the next song position whenever these 72 steps (*loops) are processed.

     

    Best Regards, Thorsten.

×
×
  • Create New...