We need to talk about Performance Pack

[Quiet Erp]

It pains me to say this but is Performance Pack fit for purpose? In my experience I'd have to say no.
Specifically the Performer device, which is the only one I've used intensively.
I wouldn't dare use it in any live/performance situation because of it's unpredictability.
Mappings becoming unresponsive unless in focus.
Or simply not working & having to be remapped.
Cursor acting drunk & veering from the graph.

While tinkering in the studio or sound designing, with no time pressure, these are irritants that can be fixed.
But in a live setting with the crowd in the palm of your hand, in a sweaty club, begging for that Drop......
......still waiting
.....cause the knob on your controller has lost its mapping.
No chance. Cant risk it.
And that what it is designed to do. Be used in a Performance.

[borg]

great potential, sadly unreliable here as well...

Tried it when 12 came out, soon found out it had the same timing issues as clyphX had many years ago. Too sluggish and little annoyances...
Lives own mapping and automation/envelope system is, to me, the tightest. All these scripting and M4L solutions seem to have a bottleneck somehow.

[Quiet Erp]

I think Iftah, the creator, is a legend & takes his work seriously, with quality control very high.
So it feels weird that this Performance Pack has been released with some many bugs, almost like a beta version.

Annoying really. I thought this was it.
Hopefully an update will be imminent.

[[jur]]

I think Iftah, the creator, is a legend & takes his work seriously, with quality control very high.
So it feels weird that this Performance Pack has been released with some many bugs, almost like a beta version.

Annoying really. I thought this was it.
Hopefully an update will be imminent.

Don't forget to forward the bugs you're coming across to Support. Thx!

[Quiet Erp]

Is it just me? Or is anyone else having issues with Performer & Variation?
If it is just me, then I'll shut the front up

but if stability & consistency issues are more widespread then something must be done.
It would be a to send these potentially game changing devices go to the dreaded MaxNotLive folder

[schlam]

...I have a big issue with Performer, is there some one that can reproduce :

Open a new empty live set
add a performer device
create a slider control in Performer
create an automation of this Performer's control (in a clip or in arrangement)

-> CPU gets crazyy !

Even if the Performer's control is blank and not mapped to a parmater, the problem occurs.

Performer seems to do not be able to be automated without big issues.

thank

win10 /Live 12.1

[[jur]]

Make sure to report to Support @Schlam, thx.

[schlam]

already done.
but I was curious to know if someone can reproduce..

[[jur]]

You're not alone.