Business Template Forums Macros GranulaterreGrain, NextLoopDirect and UndoRecord

This topic contains 2 replies, has 2 voices, and was last updated by  Olivedep 2 months, 3 weeks ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #4163

    Olivedep
    Member

    Hi Philippe !

    There is a strange thing with the macro actions for define the grain size of Granulaterre. When i use GranulaterreGrain In 4000 Out 6000 to select a grain in a sample with a size of 8000ms, it select a grain of 1 ms. In take the good value (4000) but It seems like Out can’t go over 1000ms.
    Same result with GranulaterreGrainIn and GranulaterreGrainOut.

    I have another problem with NextLoopDirect : manually, it work fine, but with the keyboard (configured) and the macro action NextLoopDirect, it has no effect.

    Finally, i want to erase the loop B and after, the loop A with this macro :
    //****** Begin of the macro *****
    UndoRecord
    Sleep 20
    NextLoop
    Sleep 20
    UndoRecord
    // ************End *************

    Each macro action work fine separately, but when they are chained in the macro, a new loop is recorded in B and A … It’s very strange !

    Good afternoon !

    Olivier

    #4164

    Hi Olivier,

    1/ You are right, there is an issue in Logelloop 5, I made a mistake while making the possibility to select a track as a sample source for Granulaterre. I found it last week and it is fixed for the next release, sorry for the inconvenience.

    2/ Haha… I think you just won the prize for finding the oldest bug in Logelloop. I forgot to implement the NextLoopDirect listener for the keyboard and this probably happened between 2002 and 2005, while Logelloop still was in alpha. I fixed the issue, it should work perfectly in the next release or beta version. Concerning the NextLoopDirect macro command, it’s a bit weird as it works here, i made some improvement in this, it may fix something on your computer…

    3/
    Undo and Erase have a dedicated wait function named WaitEndEraseOrUndo, I think if you use it in place of the first sleep, everything is OK.

    //****** Begin of the macro *****
    UndoRecord
    WaitEndEraseOrUndo
    NextLoop
    Sleep 30
    UndoRecord
    // ************ End of the macro *************

    Why don’t you use

    //****** Begin of the macro *****
    EraseAllLoops
    // ************ End of the macro *************

    Or

    //****** Begin of the macro *****
    EraseAllLoops
    WaitEndEraseOrUndo
    LoopADirect
    // ************ End of the macro *************

    Please use one message for one topic, this will make easier the search on the forum.
    Thanks,
    Best regards,
    Philippe

    #4170

    Olivedep
    Member

    Thanks for the macros ! And i’m very proud of my price !!!
    And sorry for the grouped topics. The next time, i will do many topics !
    Best regards,

    Olivier

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.