With 1.6.1 older Live project crashes

[vaikl]

Had upgraded to 1.6.1 some hours ago, tried to open my actual project in Live 9.0.1 (no 9.0.2, because that crashes too ) on OSX 10.7.5. Live crashes with Spark as the crashing VST plugin in Thread 0 (in crash report).

Reopened the project with the 1.6.1 VST plugin deinstalled, trying to load the 1.6.1 AU verson on the same old track - plug opens, scans for controller, finds it, loads last project ("The Hive" from factory), boom, crashes Live again. Reinstalled 1.6.1 VST version, loading project, putting VST on same old track, scanning for the controller - nothing, nada, no spinning wheel, Spark's just freezing.

Problem was solved by removing any Spark-related old tracks from the Live project and rebooting the controller between restarts of Live. But that can't be a reasonable workflow after a simple upgrade

Is this issue known by Arturia or should I open a ticket (I don't wanna reset any controllers 'cause I have to deliver)??

[Hippojoe]

I have a similarly issue. but for me live 9 crashes when i start the Spark vst and Spark hardware is connected and On. I'm assuming it's bugs in this update. So i reverted/downgraded back to 1.5 and the vst starts with live no probs, hardware and all, so maybe try downloading one of the older updates i.e 1.5 and maybe this would work.. Hope they help you with your issue. Good Luck

[vaikl]

Thanks Hippo, but after deleting the old tracks and using new tracks with a "fresh" plugin all seems to work ok now. Changing from VST to AU plugin or vice versa without rebooting the controller is a long existent bug which still isn't solved.

I didn't had the time to check other old projects, but will do that to verify if it could be an issue with Live 9 (upgraded from 8.3) too.

[Kevin]

Hi guys,
Thanks for reporting this, the issue has not been reported during the beta test.
And so far am am not able to reproduce it.
I will try to find out what is the problem.
If you have a Live project where this is happening, could you sent it to me so I might be able to reproduce it.

thx
Kevin

[mauronedj]

On windows all work really well!
I can't reproduce it on Mac!
Are you working with 64bit live?

[Kevin]

Ok,
I managed to reproduce the issue.
I don't know why I did not get it previously because I tested opening Live project saved with 1.5 (Mauro can confirm ).
Anyway I might have a bugfix very soon.

Kevin

[vaikl]

Thanks, Kevin!

If you want me to do, I could try to reproduce it with my older projects (all made/last saved with Live 8.3.4) for myself and send you either a project or a crash report (what will come first ). I just don't know when I could spend some time on it. I'll pm you my first Live crash log with the 1.6.1 update from yesterday.

@mauronedj: No, it's 32bit.

[Kevin]

Hi Vaikl,
thanks for your help.
I think I have found what is the problem.
Would you be willing to try the new version once I will have it?

Kevin

[Terrym]

Hi Vaikl,
thanks for your help.
I think I have found what is the problem.
Would you be willing to try the new version once I will have it?

Kevin

is there another rc kevin

[vaikl]

Would you be willing to try the new version once I will have it?

Of course.

I've just found another old Live project which crashes during loading the 1.6.1 VST version and trying to connect to the controller. Will not modify it to use it for testing.

Cheers
Klaus

[Kevin]

is there another rc kevin

1.6.1 is now released so I have to make a 1.6.1.1

[Kevin]

Would you be willing to try the new version once I will have it?

Of course.

I've just found another old Live project which crashes during loading the 1.6.1 VST version and trying to connect to the controller. Will not modify it to use it for testing.

Cheers
Klaus

Thanks, I will give you the download link as soon as I have uploaded it.

Kevin

[koochey]

i've a lot of crashes caused by the new spark 1.6.1 here on logic 9 too...

[Kevin]

Hi,
Klaus has confirmed that it resolves the problem.
I will upload a hotfix ASAP.

Kevin

[Kevin]

You can download the new version from here.
It is still under testing that's why it is not publicly released.