Live API : Copy Paste?

[Twigg]

There's a copy paste crash bug in M4L that I posted in the bugs forum.
http://forum.ableton.com/viewtopic.php?f=36&t=138760

Is there a way to Copy a clip and Paste a clip using LiveAPI? I couldn't see one in the resources folder they provide. Only scene and track selection.

I want to
1) Copy current Clip.
2) Select 2 track over (I know I can do)
3) Paste copied clip.

[julienb]

There's a copy paste crash bug in M4L that I posted in the bugs forum.
http://forum.ableton.com/viewtopic.php?f=36&t=138760

Is there a way to Copy a clip and Paste a clip using LiveAPI? I couldn't see one in the resources folder they provide. Only scene and track selection.

I want to
1) Copy current Clip.
2) Select 2 track over (I know I can do)
3) Paste copied clip.

copy a clip = copy all notes and copy all envelops + ..
so I guess you can do that, considering the LOM and methods available for the clip leaf of the LOM tree.

[Twigg]

copy a clip = copy all notes and copy all envelops + ..
so I guess you can do that, considering the LOM and methods available for the clip leaf of the LOM tree.

Ya, the LOM doesn't say anything about copying envelopes. Just notes...

[3dot...]

plus ..how do you create a new clip?

[hoffman2k]

These are all things that weren't possible with MIDI controllers before, so it isn't possible with the API at this current time. This is a feature request.

[julienb]

with the keystroke workaround it could be possible, right?

[hoffman2k]

with the keystroke workaround it could be possible, right?

Well yeah, in some situations. But for me the whole point of Max for Live is that all workarounds become native solutions. The only thing that needs to happen to make this possible, is for Ableton to process these requests as if they were new functions on a novation controller.

In the end, whatever Ableton adds to the API will just add up to more possibilities for M4L users, Controller Script creators and controller companies.

We work around what we can't do. If something requires a workaround, its a valid feature request.
I may be paraphrasing this, but Gerhard Behles once said: "Our users should not have to resort to workarounds". And he lived up to that with M4L. Only a few more requests and limitations removed and I'll have almost every wish granted I made in the past 6 years. And believe, I made lots of them

[julienb]

with the keystroke workaround it could be possible, right?

Well yeah, in some situations. But for me the whole point of Max for Live is that all workarounds become native solutions.

you're 100% right!
but it is important for people not to wait for too much and begin to implement their own thing if they need them.

but I agree, of course.

[broc]

In my experience, the problem with workarounds is that sooner or later you'll get frustrated from the inconvenience or imperfection..

[julienb]

In my experience, the problem with workarounds is that sooner or later you'll get frustrated from the inconvenience or imperfection..

it all depends the need at the beginning and the workaround.
waiting for 1 year before making things could be annoying.
fortunately,my little workaround around my protodeck's patch is very ok and fast and made one time and use everytime.

[3dot...]

yes... but m4l fails to be the native workaround.. for many obvious reasons...

no sysex...
jittery sync..
no routing of audio between m4l devices on different tracks..
no support for 'multi-i/o' devices...more than 2 i/o for each device..
no keyboard stroke emulation..
inability to reach various 'control_surface' script such as 'Mackie' and 'NovationSL'
bad m4l documentation..
and no direct access to many of lives basic functions..(copy paste)
the integration isn't tight-
all-around sluggish and weird/inconsistent behavior...
etc..

you can still build very cool stuff..

the premise is good... but it seems to have a long way to go at this rate anyways...
I'm glad though the foundations have been set though..
I'm using many m4l devices on my current setup..

the problem :
... I need to use the runtime patch to get sysex in/out of there..(via OSC !!! )
and midiTranslator to emulate keystrokes...
(which naturally means I nead too use midiYoke as well)
..you see my point ?

btw does anyone know if autoHotKey is compatible with the OSC or MIDI protocols?

[julienb]

3dot...
I'm sure I'm not the only one happy man & happy user of m4L... no?!

[3dot...]

no ..don't get me wrong... I'm happy ...I love it !!!
am building 2 very cool patches which I'll share in due time !!

these are just few simple 'minor' things which make you reach for a workaround..and were not included in m4l features..

[3dot...]

I mean.. even Reaktor has an 8 output version..
most serious drum-machine/samplers plugs have more than 2 audio outputs..
(even in the real world..)

bah...

[hoffman2k]

no ..don't get me wrong... I'm happy ...I love it !!!
am building 2 very cool patches which I'll share in due time !!

these are just few simple 'minor' things which make you reach for a workaround..and were not included in m4l features..

Well they weren't there to begin with. Apart from Live being able to run Max devices, nothing got added.
And personally I'll give them a pass to make Live a wee bit more stable before they go hacking in new API stuff, remove the MIDI limitations and adding multichannel audio.

Our wildcard is Robert Henke! He does ambisonic setups, makes all sorts of cool Max devices, Atlantic Waves, Etc.. Not forgetting he's the dude who most likely talked Ableton and Cycling into doing M4L.
This is 1.0.. We'll get there. Like I said earlier, there will be a Max 6 and a Live 9 eventually.
We can't even imagine which devices will possible with that combo