Jump to content

Hawkeye

Administrators
  • Posts

    3,632
  • Joined

  • Last visited

  • Days Won

    36

Posts posted by Hawkeye

  1. @silverlight2004 Thanks a lot for the suggestions, Dave!

    The dynamic memory allocation feature is on the to-do list (but it's not easy to implement...)

    Multi MIDI channels per track/clip unfortunately most likely cannot be supported, as the whole architecture of LoopA is based on having a single MIDI OUT or a single instrument per track - basically all code relies on that.

    Supporting notes with potentially different MIDI channels within a single clip would both consume more memory (which is quite maxed out already) and would make it super difficult to visualize what is going on using the OLED. Supporting this would also make it impossible to remap existing clips to other instruments (which have only a single OUT/CHN pair). Ultimately, i think it could confuse users, when some notes in a clip are played, back while others are not played (i.e. because there is no synth listening to "their" MIDI channel).

    For multi-recording two synths at once (i.e. two keyboards), it would be easiest to rely on a second LoopA, that is MIDI-synced to the first - which also doubles the amount of parallel tracks available. I know at least one power user (not me), that uses two LoopAs for this :).

    Many greets,
    Peter

  2. How about multitasking?

    In app_init you could create a thread/task that updates the user interface and screen and which is responsive, directly after app start.

    Then, you could create another "heavy lifting" task that does calculations/sd card operations etc as needed by your app.
    That task will probably need mutex locks, but can do the copy operations in the background while you can show the progress "on screen" in the first task.

    Best regards,
    Peter

  3. Hi Matt,

    great to hear that your LoopA works now and sorry for the late reply, there's a lot going on at the moment :).

    Basically the LoopA has now maxed-out memory for everything (i see no chance for multiple UNDO levels) and it has been quite complex to fit every feature in 192kB RAM. I've added your requests on the development wishlist, but we're currently and still working hard to finally release the MatriX, so can't promise any direct LoopA code work in the immediate future.

    You can save a lot of power, by using the new "OLED off" screensaver mode i think present since v.207 - a few single LEDs that are illuminated won't draw too much power, especially if the LoopA is stopped and you only have a single active track with no other mute/unmute LEDs being lit up.

    Note clean-up, de-duplication and pedal handling is a tricky process, would need to look into it in more detail.

    For the time being, we're discussing with Thorsten on how to proceed with general code releases (expect a statement from him in March 2021).

    Many greets,
    Peter

  4. @flyweight hopefully there's no need to be disappointed - when you use the SEQ v4/v4+ with long pattern lengths (e.g. 256 steps instead of 16) and a clock divider set up to play back the individual steps quickly, this is very close to unquantized recording. If unquantized recording is your top item, i would recommend to additionally add a LoopA to your sequencer setup - it is optimized for that, but can't do a lot of things the bigger v4/v4+ can do. Our "dream" sequencer setup would be one v4/v4+, one LoopA and one MatriX (BLM) connected to both, for 16 tracks of step-sequencing plus 6 tracks of unquantized note-roll sequences plus hands-on-control with a large button matrix.

    @srmaietta can't really speak for Thorsten, but i believe the v4/v4+ was basically developed as a step sequencer with rigid timing, basically for electronic music. With the availablity of long sequences AND clock dividers, it is absolutely possible to record "human" sequences that are not consisting of 16th notes or 16th note positions. This method avoids introducing the "delay-per-step" parameter layer, which is difficult to interpret - i.e. what happens when swing is applied, what happens with other fx (like echo) and non-linear sequence progression modes and so on.

    Best regards,
    Peter

  5. @SimonSays regarding the firmware question - v4.097 is the current beta firmware release (which is stable!), the current official release is v4.096 - no need to change anything, but of course hoping for an official v4.097 release soon! :)

    Best regards and have a good new year 2021!
    Peter

     

  6. Thanks @talon and @Karg - hope you enjoy your LoopAs! :)

    Talon, currently you can modulate the dampening only manually in the FX screen, but using the left SELECT encoder you can switch through tracks quickly while the dampening command is active and then you could use the right DATA encoder to change the dampening values quickly and "live" per track - is that good enough?

    If not, and if external dampening control would be nice, it might be possible to add external CC control for the dampening values of the six tracks, but it's a longer shot, the next firmware release will mostly concentrate on adding MatriX support for the LoopA :).

    Have a good new upcoming year 2021 ! :)
    Best regards,
    Peter

  7. And, its out! :)
     
    LoopA firmware version 2.08 with a lot of new features has just been released - highlights:
     
    - Autoloop recording (dynamic length clips, BPM detection)
    - Session naming
    - Undo, Redo, clip playback inversion
    - Scene map - graphical active clip matrix overview
    - Global direct track selection: push and hold upper-row keys
    - Transposition of forwarded notes (via TRACK Fwd)
    - Fine-granular note position adjustments now supported in note editor
    - "Uneven" clip zoom levels are now supported for polyrhythmic experiments
    - New "MIDI Panic" function available via hotkey
     
    Enjoy! :)
     
    Best regards and have happy holidays!
    Peter
  8. @srmaietta LoopA has a different, non-step-sequencer approach - its code was mostly written to extend the features of the SEQ v4+, so unquantized polyphonic recording would be easily possible. It also adds a few other things, like the beatloop mode, named user instruments, high-resolution CC recording/editing/generation and graphical noteroll views, while it also can't do a lot of things its bigger brother does easily - so they compliment each other nicely :).

    Best regards,
    Peter

×
×
  • Create New...