Solved Does Studio One have a macro method to set a specific length for a MIDI event?

[Trucky]

Here they are again, I tried on an Audio-Track, of course that didn´t go well!
View attachment 742

@Wolfger - Can you confirm an issue I'm seeing (1 bar part instead of 8 bars) with the "Insert 8 bar part" macro using the following steps?

1. Create a new song
2. Enable Launcher
3. Run "Insert 8 Bar Part" macro

Observe results...
It creates a 1 bar part instead of 8 bars when running macro the first time.
It creates an 8 bar part thereafter.

*** It works as expected if you run the macro (as shown here) before enabling the Launcher.
1. Create a new song
2. Run "Insert 8 Bar Part" macro
3. Enable Launcher

Result running steps first time...

Result after removing track and running steps 2nd time and thereafter...

 

[Wolfger]

Yes, it´s somehow weird. when an empty launcher cell is selected it creates an 1bar part the first time and an 8 bar part afterwards.
no idea why. Have no time today, can´t go into more detail.
kind regards
Wolfger

 

[Vocalpoint]

I am sure everyone is starting to get the hint that if the Launcher is going to be worth pursuing longer term - it needs to get some major TLC soon.

For me - its rote simplicity is somehow it's biggest drawback - it's impossible to try to figure out what a cell is doing or why it's doing it - all coupled with no editing function or utility whatsoever.

If you guys REALLY want some fun - try dragging in a 1:32 WAV sample of a light rainstorm (for some nice ambient background noise) into a cell - but then only wanting a specific section of this file to loop. I have tried everything I can think of to get this to work - a raw file. Futzing with start points, loop markers, cutting the actual sample file, adding SampleOne to the actual track and loading it in there - nothing I could do would allow me to easily loop playback for just the specific 24 sec section I want - between :50 and 1:14".

This scenario is begging for a Consolidate function (auto trim head and tail) and leave the result in the cell - then it would work. But there is nothing like this in the Launcher.

These cells just seem to be containers that you can either fill or empty - but not much else.

VP

 

[chichogp]

Hope I'm not too late for this but I found a workaround with a macro. There's no prompt but you can easily add this to a macro bar as global buttons or on a menu. I haven't stress tested it but works fine so far:


Macro: Add 4 Bar MIDI Event

- Instrument Part/Insert Instrument Part
- Edit/Duplicate
- Edit/Duplicate
- Edit/Duplicate
- Navigation/Left Extend
- Navigation/Left Extend
- Navigation/Left Extend
- Event/Merge Events ("")


As you can see, for the amount of Duplicate and Left Extend commands you need to subtract 1 from the number of bars you want the event to be, so for a 4 bar event it's three times each, and for a 16 bar event it would be 15 times each.

This macro will work with or without snap engaged, meaning if you fire it up while the cursor is between beats for example it will create an empty event with a 4 bar length anyway except it will start and end in a non-bar position. If this bothers you it might be a good idea to add "Toggle Snap (1), Transport/Forward Bar, Transport/Rewind Bar" to the beginning of the macro before Insert Instrument Part. If you want you can add the "View/Editor (1)" command at the end.

 

[Trucky]

Hope I'm not too late for this but I found a workaround with a macro. There's no prompt but you can easily add this to a macro bar as global buttons or on a menu. I haven't stress tested it but works fine so far:


Macro: Add 4 Bar MIDI Event

- Instrument Part/Insert Instrument Part
- Edit/Duplicate
- Edit/Duplicate
- Edit/Duplicate
- Navigation/Left Extend
- Navigation/Left Extend
- Navigation/Left Extend
- Event/Merge Events ("")


As you can see, for the amount of Duplicate and Left Extend commands you need to subtract 1 from the number of bars you want the event to be, so for a 4 bar event it's three times each, and for a 16 bar event it would be 15 times each.

This macro will work with or without snap engaged, meaning if you fire it up while the cursor is between beats for example it will create an empty event with a 4 bar length anyway except it will start and end in a non-bar position. If this bothers you it might be a good idea to add "Toggle Snap (1), Transport/Forward Bar, Transport/Rewind Bar" to the beginning of the macro before Insert Instrument Part. If you want you can add the "View/Editor (1)" command at the end.

Your macro doesn't work when running it with the Launcher open...

See results...

 

[chichogp]

Your macro doesn't work when running it with the Launcher open...

See results...
View attachment 783

Yeah I just tried it with the launcher opened, it gets wonky. It does work (sometimes) if you set the launcher's Global Quantize to the number of bars (up to 8). You can add it at the beginning of the macro or experiment on different orders. So it might would look like this:

- Launcher/Global Quantize 4 Bars
- Instrument Part/Insert Instrument Part
- Edit/Duplicate
- Edit/Duplicate
- Edit/Duplicate
- Navigation/Left Extend
- Navigation/Left Extend
- Navigation/Left Extend
- Event/Merge Events ("")

 

[Trucky]

Tried your suggestion but it's still not working.

 

[Trucky]

Macro Update!
Unfortunately, other macros in this thread have issues when the Launcher is open.
I'm going back to the macro(s) I posted originally in the following link...
I attached the 4 & 8 bar part macros to the post.

Macros for 4, 8, 12 or 16 empty bar parts

 

[sintil8]

Promising. Clearly there is something going on here - as I have been dragging and dropping all morning

No matter what part length I drop - it gets clipped in half once in a Launcher cell.

VP

Spent a couple of minutes with this little nugget yesterday and it appears to have been fixed with 7.02.
Keeping my fingers crossed I'm not speaking too soon!!!

 

[Vocalpoint]

Spent a couple of minutes with this little nugget yesterday and it appears to have been fixed with 7.02.
Keeping my fingers crossed I'm not speaking too soon!!!

Did you actually mean 7.20?

7.02 takes us all the way back to Dec 2024...

VP

 

[sintil8]

Did you actually mean 7.20?

7.02 takes us all the way back to Dec 2024...

VP

Mea Culpa... sorry Ver's 7.20
I did post whilst half awake 5.00 am. gawd if I was a Dev there would be a riot going down.

I was hoping you might respond...
Have you tried your rainfall loop that brought this to light, I have yet to check with an external sequencer that the Rec Quantize is working as expected.

Kindest, you know the drill. Take care.

 

[Vocalpoint]

Mea Culpa... sorry Ver's 7.20
I did post whilst half awake 5.00 am. gawd if I was a Dev there would be a riot going down.

I was hoping you might respond...
Have you tried your rainfall loop that brought this to light, I have yet to check with an external sequencer that the Rec Quantize is working as expected.

Kindest, you know the drill. Take care.

I am going to give 7.2.0 a good run through tomorrow - and yes - the good ole Launcher will be tested (again).

VP

 

[Vocalpoint]

Mea Culpa... sorry Ver's 7.20
I did post whilst half awake 5.00 am. gawd if I was a Dev there would be a riot going down.

I was hoping you might respond...
Have you tried your rainfall loop that brought this to light, I have yet to check with an external sequencer that the Rec Quantize is working as expected.

Kindest, you know the drill. Take care.

OK - most interesting day of testing on 7.2.

Either I have been completely blind - or just in a better mood to "learn" this time around but I have noticed some key (but -psuedo-obscure - to me anyway) improvements in 7.2 and the Launcher.

First - I need to shout out to Lukas - who posted a video recently about Info View - which frankly - I had never really paid attention to. This time - I turned it on and learned a whole new way (after 14 years) to set my loop points (CTRL and ALT). Using these in the Launcher is perfect when I want to get the whole "rainfall loop" going in a Launcher cell. Let's call this Discovery 1

Discovery 2 - was the one that pulled it all together.

Now - this item was so obscure - I am not even sure it existed in previous versions of 7 - I know it is not in v6 - and I never would have even noticed it if it were not for Info View.

While I was cobbling together a little ditty to test the Launcher cells - I had Info View on and noticed this (1):

I had never heard of a "Play Start Marker" before - so I start poking around and sure enough - if you look closely at the arrowhead at (2) - you will see colored triangle superimposed over the start of the Loop Range.

You can of course grab it and move it wherever you want and presto - the Launcher cell starts it's playback - from where you drop this thing.

That - combined with the CTRL and ALT to set the loop points - suddenly makes the waterfall loop a reality. And essentially performs a "consolidate" feature with a few moves.

This is not as elegant as say - in Bitwig - where once you determine your exact loop range - you can right click on the Launcher cell and chose Consolidate - which removes the head and the tail data that fall outside the loop range.

That could be a job for a macro....hmm...

VP

 

[sintil8]

AV
Nice one, you are not alone, I don't know if that Play start marker was there before Ver 7.2 either?
In both of the other DAWs that have these cell based tools they use two loop braces so it can start in one then the next loop brace takes over.
You can use it as intro section that then gets captured by the second loop brace which will loop any number of times ad infinitum.

Thank you for getting back, good find, I will need to look at this and learn how to use it myself at some point.

 

[Lukas]

Nice one, you are not alone, I don't know if that Play start marker was there before Ver 7.2 either?

Yes, it's a Studio One V3 (2016) feature.

 

[Vocalpoint]

Yes, it's a Studio One V3 (2016) feature.

I fired up 6.6.4 just before I posted - did not see a play start marker in any MIDI event in my test project.

If it is there - it is VERY well hidden.

VP

 

[sintil8]

Yes, it's a Studio One V3 (2016) feature.

I'm not at my station at the mo, Is this the standard loop brace?
I may have misunderstood AV, with the ref to a Green loop brace, I thought the Dev's had sneaked a second brace into the Launcher slots.

It's all good tho' we live and learn.
Note to myself, I must look this stuff up and get my head in gear.

Kindest regards to all

 

[Vocalpoint]

I'm not at my station at the mo, Is this the standard loop brace?

I am in 6.6.4 right now - all we get is the standard loop brace. With "info" on - there is no reference to a "Play Start Marker"

And logically - the loop brace start - should be all we need.

I may have misunderstood AV, with the ref to a Green loop brace, I thought the Dev's had sneaked a second brace into the Launcher slots.

That green triangle can be moved anywhere and is only found in the MIDI contained within a Launcher cell that I can see.

VP

 

[sintil8]

Next time I fire up SO1 I will be checking this out, it will be interesting to see if it can be set pre the main loop brace?

That's what intrigued me a small green triangle?

Anyway for now regards.

 

[Vocalpoint]

Next time I fire up SO1 I will be checking this out, it will be interesting to see if it can be set pre the main loop brace?

That's what intrigued me a small green triangle?

Anyway for now regards.

It can. You can drop it anywhere you want. This is exactly what was making me crazy with my "rainfall" loop in the first place.

While I specifically set the actual Loop start/end points - the clip itself was starting from the beginning of the audio clip (where the Play Start Marker was) and this was the reason for my crazy out of sync action on this clip.

Once I clued into this marker yesterday and of course - dropped it right on Loop Start - problem solved.

Not exactly sure of a use case where one would set a specific loop range for an audio or MIDI event and then NOT want playback to start at Loop Start - but it does make for some interesting possibilities - like playing "into" a loop zone for a specific length of bars (or time) and then having the actual loop range take over on the next pass.

I think my logical brain simply thought that in a Launcher cell - if I actually set a Loop Range (Start/End) - that would determine WHERE my content would start looping - but with this "new" marker - that does not seem to be the case unless you drop it right on the Loop Start location.

VP