About the next MuLab 9

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Please include linked/ghost clips when dragged into arrangement section. So when clip is edited, also previously dragged clips in arrangement view adjust accordingly or even better, let user decide when dragging them.

Post

Yes that will be possible :tu:

Post

Part start>{<loop start>...<loop end>} too?
If so, sometimes there will also be a need to ‘start directly at loop start’ attribute for a dragged clip. Meaning an option to start at clip’s ‘loop start’ rather than ‘clip start’😉

Post

Good question. I cannot yet answer it.

Post

mutools wrote: Sun Jul 12, 2020 11:13 am Not yet atm. Eventhough the clip launcher is already working in it's current development state (and it's fun :party: ) it would be just a bit too early to share screenshots/videos/details. I hope to share more detailed info in a couple of weeks.
:tu: Take Your time :tu:

Post

Of course. In such scenario pre-loop section can only cause confusion when triggering a looping scene, unless it has exactly the same length as clip's looping section.
I'm looking forward to first public realease. I think this is really a step into the right direction :clap:

Post

Happy to see that the Skalooper pointed in the good direction for the future . Can't wait this new feature!
(By the way, I uploaded a V3 in the Mulib, with transpose, FX, song sequencing and random fuctions).

Post

Wow cool ... I'll have to check it out 👍

Post

Looking forward to checking this out! Could be a game changer.

Post

mutools wrote: Sun Jul 12, 2020 11:37 am The clip launcher is positioned between the tracks and the timeline composer. It can be easily shown & hidden.
As Rapht1987 noted, this would invade GUI space, would it be better suited as a browser tab?
Just trying to offer some advice. I'm not sure about the whole clip thing personally, so your placement is probably the better idea?

Post

You have quoted the sentence that gives you the answer. If you don't want to use the CL, hide it, then it won't take GUI space. And even if you use it, you decide how much space it takes. In fact all just like with the browser: Toggle it on/off with a button, drag a splitter bar to control its width.

Post

The existing browser is a "tab" - you can show/hide it with the "Browser" button on the tab bar, next to the show/hide "Mixing Desk" button. If the control is there and it works the same way it will add no more space. I'm getting the strong feeling this integrates closely with the Composer in MuLab - and may not even be present in standalone Mux - so you're likely to want it alongside the tracks for the workflow offered. Having it separate (like the docked/floating modular view) might not be the best way. I'd be interested to hear more about the planned workflow, though.

Post

skarabee wrote: Sun Jul 12, 2020 10:40 pm Happy to see that the Skalooper pointed in the good direction for the future . Can't wait this new feature!
(By the way, I uploaded a V3 in the Mulib, with transpose, FX, song sequencing and random fuctions).
See Muzys, Jo introduced clips ala Ableton nearly 20 years ago

Post

awesome :party: with probability, so there´d be a percentage to set the chance to actually play the clip or jump to the next one or a random one????? this would be even more awesome. :pray: and it would make it even more flexible :D

and will it be possible to midi record live into a clip?

and when?

Post

mutools wrote: Mon Jul 13, 2020 1:22 pm You have quoted the sentence that gives you the answer. If you don't want to use the CL, hide it, then it won't take GUI space. And even if you use it, you decide how much space it takes. In fact all just like with the browser: Toggle it on/off with a button, drag a splitter bar to control its width.
But not as accessible as having it always shown in the browser. I always have the browser open as it doesn't take up much space on a full HD setup. So having the browser contain the Clip Launcher would take up no space and combines the Show/Hide function you already stated. This is actually a better solution for saving GUI space as it doesn't interfere with anything else when open, which was the point of the original comment, a point which you seem to have missed. :dog: :D

But after reading pljones comment, perhaps your implementation is better! I'm just trying to offer some advice for a more streamlined operation :hyper:

Post Reply

Return to “MuTools”