Home Forums Logelloop 6 (English spoken) Transport start/stop?

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

    Hey,

    I’m mostly working on the following setup:
    – Modular loopers under data plugin Korpus and FX plugins on channels FX1 – FX8
    – Tracks – used only for Granulaterre, granular etc…
    – “normal” loopers – not using that at all

    With that in mind, I seem to come back at missing something like a global transport bar.
    Like a master start/stop for everything.

    I could try to implement via macros, but started wondering if that’s not something you considered or have in mind?
    What would be considerations against it?

    A macro would be have to be specific to the configuration.
    Something like:

    Transport stop:
    – stop metronome
    – stop all modular loopers
    – stop granulaterre, granular, ceratin plugins etc…
    – stop LFOs


    and a lot of these would have to be hard-coded addresses depneding on what’s loaded where, so the macro would not be really universal.

    Thoughts?

    Additionally:
    – do you plan on thinning out LL out of all legacy/deprecated stuff anytime soon?
    – do you have any idea regarding when to expect a new release? there were some stuff we talked about a month ago that I would find useful.

    Thanks!

    #7196
    Philippe OllivierPhilippe
    Keymaster

    Hi,
    I think you have everything to code the global transport with a macro.

    With $sfx1$ // $sfx8$ you will know which sfx is loaded in each slot.
    With $insert_fx1_rank_1$ // $insert_fx(n)_rank_(n)$ you will know which insert is loaded in a slot.

    But yes, that will not be easy to code nor fast during the execution.

    During this year 2025 we will release many new devices and maybe some of them may help you for this… I don’t know, but will keep that in mind…

    – do you plan on thinning out LL out of all legacy/deprecated stuff anytime soon?

    No. The way I do it is to first replace old things by more modern tools. Then announce that the legacy ones are deprecated. Then remove them from the documentation. Then remove them from the code. So you have time… -) I don’t want to put users of older versions in a situation of confusion.

    As soon as I have time I will make a post to explain what is the future orientation of Logelloop. Nothing revolutionary but useful to be known by users.

    – do you have any idea regarding when to expect a new release? there were some stuff we talked about a month ago that I would find useful.

    We are currently finishing many things and testing all the new features and bug fixes (the list is not short and contains some good surprises) and I hope to release the new one before the end of this month.

    Philippe

    #7222
    Patrick KiznyPacocreative
    Participant

    Awesome! Thanks a lot for sharing these thoughts.

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