Jump to content

TK.

Administrators
 View Profile  See their activity

  • Posts

    15,247

  • Joined

 Content Type 

Posts posted by TK.

  2. Midi and Sysex directory on SD

    in MIDIbox SEQ

    Posted

    There is no SysEx backup option available, all files to restore a MBSEQ setup are located on SD Card.

    So, it might be better if you would backup the entire SD Card with your computer (SD Card Readers are more suitable for fast file access)

    The "sysex" directory is intended to send SysEx dumps from the SysEx menu - for this purpose, you've to create subdirectories (e.g. choose names which correspond with your synths), and copy the .syx files into these directories.

    Best Regards, Thorsten.

  4. MIDIbox NG Release + Feedback

    in MIDIbox NG

    Posted

    A new version is available: 

    MIDIbox NG V1.035
~~~~~~~~~~~~~~~~~

   o Support for secure keyboard handling if patch is switched: keep original
     MIDI port, note, channel when playing Note Off
     (this feature is not supported for LPC17 due to high memory consumption)

    o Fixed encoder incrementer in absolute mode

    Best Regards, Thorsten.

     

  9. Question about expected behaviour in Song Mode

    in MIDIbox SEQ

    Posted

    Your contribution to the documentation project is very welcome, you've my full attention to sort out some details! :)

    Some months ago Borfo started with a new Wiki page: http://wiki.midibox.org/doku.php?id=mididocs:index
    You could either try to integrate your manual there, or start with a separate one.
    In any case I will link to the manual from the uCApps page once you feel that it's ready for broader publication.

    To your questions:

    Quote

    The question is: is there a purpose for a song mode setting where the Guide Track is disabled and no tracks are sync'd to Measure? If yes, what should be the expected behaviour in that case?

    The pattern synchronisation is a very cumbersome part of the firmware, and the behavior might change based on user requests in this or the other direction.

    So: the behavior without guide track isn't specified, it works "as is" ;-)

    Quote

    • What good are Drum track type presets 64/64, 128/128 or 256/256? There's other drum track options that provide everything these three do, but in addition with the others you can have one extra parameter or trigger layer. (See the manual, section 'Track Event Configuration'). It seems these three named options are inferior and redundant, unless there is some benefit in having just one parameter and one trigger layer.

    256/256 is the only option where we have 256 individual steps in the parameter layer, which is typically velocity.
    128/128 and 64/64 are redundant, but they exist due to legacy reasons. It could be, that some users have patterns which use this configuration, by removing the configuration option the menu handler wouldn't be able to show it anymore.

    Quote

     Does RollG trigger do something? The user manual says "Roll and Roll2 parameter layers will be gated by this trigger", but Roll and Roll2 parameters work ok even if the RollG trigger is not assigned to any trigger layer (on the TRIGGER page).

    If RollG is not assigned to a trigger layer, it's always 1
    The same "trick" is used when the Gate trigger is not assigned to a layer.

    Quote

     Roll2: What's the strange value 2x++ between 2x96 and 3x03?

    It means >96. Since each step has 96 ticks, values >96 won't lead to an effect and therefore displayed as "++"

    Quote

    Nth: What are the first selectable operations, from --2 to --16, for the Nth parameter layer? (Apparently the ?? at the end is a place holder for a yet-to-be-added operation.)

    "--" means that there is no effect at all.
    Due to the way how parameters are stored in the parameter layer, I had to handle the first 16 values as dummy entries.

    Quote

    Is there a reason why Inc. setting is not available for Poly step recording? The user manual does state Inc "[w]orks only in Mono recording mode", so I guess it's intended.

    Inc increments the step with each played note.
    Since in poly mode multiple notes have to be entered into a single step, the Inc option is disabled in this case.

    Quote

     If AStart is 'off' and the sequencer is not running, recording will always be Step recording and will use step recording settings from the Jam page, even if Live recording is selected on the Jam page. I'm just asking if this is intended, and don't mean that it should necessarily be changed. In my opinion it makes good enough sense if this is intended. If it is, I'll just document it

    Yes, this is intended: 

    /////////////////////////////////////////////////////////////////////////////
// Called from SEQ_MIDI_IN_Receive() if MIDI event has been received on
// matching IN port and channel
/////////////////////////////////////////////////////////////////////////////
s32 SEQ_RECORD_Receive(mios32_midi_package_t midi_package, u8 track)
{
  // step recording mode?
  // Note: if sequencer is not running, "Live Recording" will be handled like "Step Recording"
  u8 step_record_mode = seq_record_options.STEP_RECORD || !SEQ_BPM_IsRunning();

    (as you can see, some answers are in the source code ;-)

    Quote

    Possible bugs:
    ...
    Requests:

    added to the wishlist for V4: 

    ----------------------------------------------------------
Track Event page: CC message for GP ENC 11-13 only if CC is visible
http://midibox.org/forums/topic/19774-question-about-expected-behaviour-in-song-mode/#comment-173653
----------------------------------------------------------
AStart: ensure that recording is started with first step
http://midibox.org/forums/topic/19774-question-about-expected-behaviour-in-song-mode/#comment-173653
----------------------------------------------------------
Allow to delete presets
http://midibox.org/forums/topic/19774-question-about-expected-behaviour-in-song-mode/#comment-173653
----------------------------------------------------------
Add option which avoids that each 4th gate will be turned on in the initialisation pattern.
http://midibox.org/forums/topic/19774-question-about-expected-behaviour-in-song-mode/#comment-173653
----------------------------------------------------------
Song Page: add "Mute Pattern" (all 4 tracks) command
http://midibox.org/forums/topic/19774-question-about-expected-behaviour-in-song-mode/#comment-173653
----------------------------------------------------------
Add command which copies the current pattern configurations into multiple pattern slots (e.g. current patterns -> A1/A2/A3/...)
http://midibox.org/forums/topic/19774-question-about-expected-behaviour-in-song-mode/#comment-173653
----------------------------------------------------------
Check behaviour of "BUTTON_SAVE_ALL" and "BUTTON_TAP_TEMPO" - they are implemented, but it seems that they aren't working?
http://midibox.org/forums/topic/19774-question-about-expected-behaviour-in-song-mode/#comment-173653
----------------------------------------------------------
Integrate revised F1..F4 assignments into mbseq_hw.v4 files:

# Following button functions are usually assigned to Fx
# buttons, or to dedicated (labeled) buttons
# In Wilba's frontpanel layout:
# F1 is located at SR M3 Pin 3; by default it is set for quick access to the Bookmark page.
# F2 is located at SR M2 Pin 2; by default it is set for quick access to the Jam page.
# F3 is located at SR M2 Pin 3; by default it is set for quick access to Tap tempo [if that can be made available]
# F4 is located at SR M1 Pin 2; by default it is set for quick access to Save all patterns [if that can be made available]
# and there are dedicated buttons for Copy/Paste/Clear/Utility/StepView

#                    SR  Pin
BUTTON_BOOKMARK      M3   3
BUTTON_RECORD        M2   2
BUTTON_TAP_TEMPO     M2   3
BUTTON_SAVE_ALL      M1   2

http://midibox.org/forums/topic/19774-question-about-expected-behaviour-in-song-mode/#comment-173653
----------------------------------------------------------

     

    Added to wish list for V4 Plus (since much more memory will be consumed, too much for the old cores, feasible with the MBHP_CORE_STM32F4): 

    - allocate some memory to sort the directory view instead of loading directly from SD Card
http://midibox.org/forums/topic/19774-question-about-expected-behaviour-in-song-mode/#comment-173653


- allow to define delays based on ports & channels instead of only the port.
http://midibox.org/forums/topic/19774-question-about-expected-behaviour-in-song-mode/#comment-173653

    Best Regards, Thorsten.

  10. Anzahl Digitaleingänge der CORE_STM32F4 Module

    in Deutsch

    Posted

    Hallo Holger,

    das Problem tritt bei allen cores auf, und ausschliesslich unter Windows.

    Unter Linux und MacOS koennen die 4 USB Ports problemlos bedient werden.

    Leider kann hier nur Microsoft weiterhelfen.
    Ich habe uebrigens noch kein USB MIDI Interface mit >= 2 Ports unter Windows gesehen, das mit dem von Microsoft mitgelieferten Treiber problemlos funktioniert. Deshalb haben Firmen angefangen, ihre eigenen Treiber zu implementieren (was wohl nicht so ganz trivial ist), und diese so geschuetzt, dass sie nur mit den eigenen MIDI Interfaces zusammenspielen.

    Ich sehe nun allerdings keinen Zusammenhang mit einer 16x8 Matrix?

    Gruss, Thorsten.

  12. is the STM32F4 EOL?

    in Parts Questions

    Posted

    Cortex M3 or M4 compatibility is a must, I don't plan to introduce a new CPU which wouldn't allow to run existing applications.

    Of course, external memory would open new possibilities.

    On the other hand (and contrary to this): wouldn't it be nice to have a much smaller form factor?
    Something like Teensy, but with a more powerful microcontroller which is (or meets the specs) of a STM32F407, and gives access to at least 3 SPI, 2 UARTs and 1 I2C port?

    Best Regards, Thorsten.

  13. is the STM32F4 EOL?

    in Parts Questions

    Posted

    As mentioned by Hawkeye, the predecessor STM32F4DISCOVERY has exactly the same chip (with 1 MB flash) like the new STM32F407G-DISC1 development board.

    My assumption (not confirmed) is, that ST just initiated a new batch production run of the board and changed the name to differentiate from other variants with similar names, but different feature set.

    The ST page (-> http://www.st.com/web/catalog/tools/FM116/SC959/SS1532/PF252419 ) shows that the old board is almost out-of-stock, but Farnell got 1000 pieces of the new board and offers it for the old price, which is a good sign.

    So - let's assume it's only a temporary outage.

    But we should also start to search for the next generation MBHP_CORE_xxx candidate! ;-)

    Best Regards, Thorsten.

     

  16. Mixing C and C++

    in MIOS programming (C)

    Posted

    malloc/free overlays are part of the programming model: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fprogramming_models%2Ftraditional%2Ffreertos_heap.cpp

    Big C++ based MIDIbox application: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fprocessing%2Fmidibox_cv_v2%2Fsrc%2F (major object orientied code located in src/components)

    I don't use dynamic object allocation, but prefer static instead for deterministic behaviour.

    Btw.: please move your cpp_issues program to a different location, e.g. /playground.
    The apps/troubleshooting directory is intended to collect troubleshooting applications for the users, and not to discuss programming problems.

    Best Regards, Thorsten.

  20. extended chords (dominants & tensions)

    in MIDIbox SEQ

    Posted

    The intention of the duplicates was to get Minor chords in the same order like major codes, so that it's easier (faster) to remember & access the chord.

    In addition we've the problem, that any change in the table will lead to compatibility issues with existing patterns.

    But there might be a good compromise:

    • additional chord tables could be defined, selectable as "Chord1", "Chord2", "Chord3", ... parameter layer
    • currently there are only 4 notes per table item, but I could enhance it to 6 or 8 notes if required
    • chord tables won't be editable in RAM, but I can integrate them directly in the firmware so that they are available for all users

    So - how would "your" chord table look like exactly?
    I need 32 entries

    Best Regards, Thorsten.

  21. MIDIbox SEQ V4 Release + Feedback

    in MIDIbox SEQ

    Posted

    In comparison to Bitwig we've a different situation: while Bitwig is developed by a professional company with focus to satisfy as many users as possible (to earn as much money as possible ;-), MBSEQ is only a sparetime project, mainly developed by myself.

    Of course, MBSEQ is open source, and there is something like a API which could be enhanced or customized by users, but it requires some selfeducation about MIOS32 and the firmware architecture + C programming skills. E.g. somebody could adapt the "BLM_SCALAR_MASTER" driver, which transfers LED states and converts button actions, to another controller: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fmodules%2Fblm_scalar_master%2F

    Or somebody could customize the next upper layer called "SEQ_BLM" which allows the external controller to access sequencer functions: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsequencers%2Fmidibox_seq_v4%2Fcore%2Fseq_blm.c

    Concerning direct USB connection to the launchpad: unfortunately there are three reasons why this doesn't work with the launchpad: 

     

    Best Regards, Thorsten.

  23. MIDIbox NG Release + Feedback

    in MIDIbox NG

    Posted

    Yes, this command should do the trick.

    It seems that there are variables which are not reset, this isn't intended - on the other hand I've currently no idea what I'm missing here.

    Would it be possible to create a minimal .NGC file which I could use to reproduce the issue at my side?

    Best Regards, Thorsten.

  24. Mixed DIN/DOUT board -- clock and latch chaining?

    in Testing/Troubleshooting

    Posted

    In the past J8/9 RC1/RC2 was a common line at the core (MBHP_CORE_PIC, MBHP_CORE_STM32), but always routed as separate lines at DIN/DOUT PCBs.

    With MBHP_CORE_LPC17 and MBHP_CORE_STM32F4 I introduced separate RC1/RC2 lines at J8/9 core side for future enhancements.

    This feature isn't used by MIOS32 yet (it just sets both pins at once), but it could be used in future for whatever reason.

    Best Regards, Thorsten.

×
×
  • Create New...