Home Forums Macros Modular Looper – Autofade Immediate

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #7191
    Patrick KiznyPacocreative
    Participant

    Hey,

    While controlling modular loopers directly (not via Korpus)
    The documentation reads:

    AutoFade
    Fade out if playing, Fade in if muted - Can be followed by 'Immediate

    So I try

    InsertSendMessage fx1 1 AutoFade Immediate
    or 
    InsertSendMessage fx1 1 AutoFade "Immediate" 

    And it does not seem to work. What am I missing?

    I managed to force the behavior:
    InsertSendMessage fx1 1 Mute
    WaitDuration 10
    InsertSendMessage fx1 1 Mute

    Which mutes the player with a quick AF.

    #7193
    Philippe OllivierPhilippe
    Keymaster

    Hi,

    With this, the autofade will start at the loop’s end
    InsertSendMessage fx1 1 AutoFade

    If you add immediate, the autofade will start immediately
    InsertSendMessage fx1 1 AutoFade Immediate

    If you mute the loop, there is a 40 ms fade out before the mute.

    There is no current possibility to change the fade length, which is the loop duration when you don’t use Korpus.
    Philippe

    #7232
    Patrick KiznyPacocreative
    Participant

    Hey,

    I’m having difficulties with controlling Korpus loopers with autofade via macros.
    Specifically, I want to frequently put all loopers under Korpus to a long autofade, but be able to cancel the autofade and resume playback or recording on user action (via macro)

    So I have something like that:

    
    $SS_Head$ = 500
    $SS_Tail$ = 5000
    …
    InsertSendMessage dt3 1 AutofadeAllWithLength 0 $SS_Tail$

    and before the autofade is done, I want to use play, overdub or autofade 1 to cancel out the fade out and take it’s effect.

    // trigger play
    InsertSendMessage dt3 1 AutofadeAllWithLength 1 $SS_Head$
     
    
    // or overdub
    InsertSendMessage dt3 1 Overdub 1 
    
    // or record directly in looper, not via korpus
    InsertSendMessage fx9 1 Record $SS_Buffer$

    This is where things get whacky.
    It seems that when Korpus is during a long AutofadeAll fading out, when I click rec or overdub via Korpus UI it does cancel autofade and records properly.
    But it does not happen so when using macros. During a long autofade out, I can start overdubbing, the autofade is not cancelled, the overdub ends, and afterwards the autofade comes to an end and mutes looper.

    Also, it seems that macro korpus autofade is not handled properly.
    Here’s an example:

    
    // Looper under korpus, content recorded and playing
    // Call a long autofade out
    InsertSendMessage dt3 1 AutofadeAllWithLength 0 5000
    
    // then call a short autofade in (manually, but from macro)
    InsertSendMessage dt3 1 AutofadeAllWithLength 1 500

    What happens is:
    AutofadeAll gets cancelled from Korpus UI
    Autofades are not cancelled in individual loopers

    It means that there are probably discrepancies between UI operation vs macro functions.
    I’d love some explanations and workarounds on how to deal with this.
    Particularly, is there any way to cancel autofade that is in progress?

    #7234
    Patrick KiznyPacocreative
    Participant

    Following further investigation it seems that once Korpus Autofade (out) is in progress, there’s really no way to recall/break/stop it via macros.
    I tested all possible combinations of available commands, both to Korpus and to the looper, and had no luck.

    #7236
    Philippe OllivierPhilippe
    Keymaster

    In fact, it’s much more problematic than it sounds.

    Imagine you request an autafade out.
    And when it’s started, you stop it.
    The loop’s sound level is no longer at a normal level, yet it’s not mutated…
    As there’s no fader, it’s impossible for the user to know what’s going on.

    This is an example, but there are many other cases that will be problematic…

    So, to do this kind of thing, you have to fade out using the track volume faders, and that way you can stop it whenever you want, and the level you’re at is visible by looking at the fader status.

    #7239
    Patrick KiznyPacocreative
    Participant

    Yeah, understand it.
    I actually tried implementing it with faders.
    Even created a side-macro, independent from Matrix, whose only purpose was to handle faders.
    But got to the same issue with not being able to intervene during a fadeout executed with “During”.
    Which made me abandon this idea.

    Last resort would be to have a separate slot macro running in a loop and slowly approaching the targets set by a Matrix macro.
    But for some reason I don’t trust the looped macros for performance reasons.

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.