Mainstage 2 and SL.....Sweeeeeet!

[jesse]

OK, I might have found a fix for the parameter list notification to show the other loops, try the version I linked to below to see if it is any better. This version also fixes updating for loop_pos, loop_len, cycle_len, and free_time.

Let me know how it goes!

http://essej.net/sooperlooper/SooperLoo ... 4test1.dmg

[PS: this is an Intel only build]

[Stavros]

Still no bindings beyond loop 1 unfortunately. Bummer!
I cant imagine why mainstage cant see them if AULab can.

The Position and Length bindings are giving a numeric readout now. Yeah!
The were not before.
Time is rounded out to the second as you can see in the screenshot.

Is there a way to have the Loop Position provide visual feedback on the horizontal bar?
The scratch position binding works with a graphic bar giving visual feedback of position.See image. Very nice.

Mainstage lets you use a dial or bar or readout..whatever graphic you want.
I guess it would have to be a percentage or something so mainstage knows how much of the total length of the bar to fill.

Thanks!

[jesse]

OK, this test release should make four loops worth of parameters show up at first. Also the position is now displayed as a ratio so the bar should work. Also changed the unit of the other time fields so they should show more digits (hopefully).

http://essej.net/sooperlooper/SooperLoo ... 4test2.dmg

Let me know....

[Stavros]

SUCCESS
YOU ROCK JESSE!@#$%^&*
This is a game changer!
The 4 sets of bindings show up in mainstage! Awsome!!!
Any additional loops I create however still do not...limited to the 4 you created.

THe position binding now WORKS beautifully !@#$%^
Full visual feedback on the bar, meter, slider, dial...whatever.
The numerical readout also displays 10th of a second increments...nice.

It is now possible to setup a fully customized SL interface in mainstage with full visual feedback!
Ever so grateful
Thank you
Thank you
Thank you


ps- now if mainstage would just allow us to string bindings together like macros?....that would just take the cake...maybe applescripts does allow that somehow...I'll look into it....but thats another conversation.
Ill post some images here once I get my final interface setup so you can see how Im using it.

Cheers mate!
Stavros

[jesse]

Cool. It sucks that an apple product just ignores the notification that the parameter list has changed. It should probably be reported as a bug to Apple...

In the meantime I can prepopulate the list with as many loops worth as you want, I should probably do 8.

jlc

[Stavros]

8 would be awsome!
cant see using more than that...it gets unruley!

Im using funky little nano kontrol to set this up
freakin unbelievably cool!
post pics soon

[jesse]

OK, you now have 8. I also threw in your requested commands record_exclusive, record_exclusive_prev/next which end any operations on other loops, and start recording on the specified/selected, or switch to the next/prev then record.

http://essej.net/sooperlooper/SooperLoo ... 4test3.dmg

Test it out for me and if it looks good, this will probably become the next released version.

[Stavros]

Great Jesse...Thanks for doing that.
All 8 bindings are showing up....beautiful.
Heres some preliminary Record_Exclusive feedback.
1-
If quantize is turned OFF, the RECORD EXCLUSIVE binding behaves as expected. Nice. Current loop is not SELECTED. however.
I think the loop should also be automatically selected so you can immediately use other commands for selected loop.
This also makes sense for the general record commands....to activate current loop.
2-
If quantize is OFF, RECORD NEXT EXCLUSIVE works as expected.
And it automaically SELECTS the new loop....nice.

RECORD EXCLUSIVE PREVIOUS does not work for some reason(true for all)...simply toggles record on and off.

3-
If quantize is ON....RECORD EXCLUSIVE has a small problem.
If used while recording the FIRST loop.....it waits one cycle before entering record on the second loop.
So it plays the first loop back again before it starts recording....should kick into record immediatley.
After the second loop it behaves as expected.
Also does not SELECT current loop automatically....should.
4-
If quantize is ON...RECORD EXCLUSIVE NEXT behaves the same as above.
Waits one cycle before recording second loop....should kick in immediately.
After that it behaves as expected.
5-
REL SYNC appears to mess things up real good.
Second loop kicks into record immediately
but subsequent loops keep flashing, waiting irratic on off
6-
It would be REALLY nice if you had the RECORD_or_OVERDUB variation with these EXCLUSIVE commands.

Hope that feedback helps!

FINALLY....you've done a ton of stuff here.....but just have to ask...for future thought perhaps.

as is common with most of the hardware pedals...
Live's new looper plugin has a very cool multi-function SINGLE BUTTON binding.(alongside to usual ones)
First click REC(EXCLUSIVE)
if recording...Second click goes into PLAY
if playing....next click goes into OVERDUB
if overdubbing...next click goes into play
etc
Double click STOPS
Hold for more than 2 seconds UNDO

It allows for alot of control with a simple button.
4 pedals on the floor and your rockin'

Would it be possible to create such a binding for SL?
Something to think about for future release perhaps.

Thanks for doing all these revisions Jesse...code makes dizzy
I cant imagine how you pull this stuff off.....
You rock man!

cheers mate

s

[Ecchi]

Hey guys,

been following this the last couple of days and I'm really impressed! You've made SL even more valuable than it already was and I'm also really impressed with your dedication, making changes this fast!

I'm gonna try this out as soon as I get home and I'll definitely come over to keep checking the progress (and finding that donate button)!

[jesse]

Re 1: Agree, for this exclusive commands it should select the loop. As for the general record command, I disagree for the moment.

Re 2: will check out the prev issue.

Re 3: I had hoped you wouldn't discover this so quickly I did notice this already, and unfortunately the fix is not straightforward. Due to
latency compensation when you finish a record the playback loop position jumps forward a bit to compensate for the audio buffering already queued up
in the playback system. The sync logic (without rel sync) is pretty strict and won't trigger since it is past time. The fix would touch a lot of stuff I didn't want to touch just yet.

Re 5: Yeah, I saw this rel sync problem too, but didn't have time to get into it as the logic is a little complex for late night.

Re 6: Do you want prev/next variations of that too?

Re SINGLE BUTTON: As a matter of fact I also updated record_or_overdub last night to do a UNDO ALL on a long press (>1s) but didn't bother to tell you!
Big problem for you is the that the exposed AU command parameters don't have the ability to have press/release logic. I have no idea how you would present them to the plugin host
so that you could actually have a "momentary" logic involved with them, maybe treat them as a control with 2 values, 0 or 1, and if the host can provide you with a momentary logic? However, if you instead use SL's builtin midi bindings and have a controller that can actually send separate press/release events (for instance the FCB1010 in note mode) you can make the midi bindings in SL to do it. In the meantime you can check it out using the GUI's keybindings, if you set a keystroke for it, the long-press logic will work.
Adding some sort of double-click logic into SL would be an interesting feature too, not yet there.