Page 1 of 1
Plug's Waves crash LIVE5 (GHRRRRRRR!!!!!!)
Posted: Thu Sep 29, 2005 7:43 am
by wlad
Insert plug Waves crash live5!!! F....K! it's the same as LIVE4.0.4 version!!!
When ableton upgrades it, he must integrate this!!!!
I'm with my new LIVE5 version and i can't use it, because i can open my version live4 set!!! I'm very ANGRY!!!!
When can i hope a LIVE 5.1.0 version?????
(my english is dirty, i know...)
Posted: Thu Sep 29, 2005 10:07 am
by wlad
I heard a solution: delete waves VST and work with AU only... i'll try this later.
Posted: Mon Oct 03, 2005 7:36 am
by wlad
I deleted waves 5 VST and now i can working with L5 and waves plug.
BUT I CAN'T OPEN MY SET LIVE FROM L4!!!!!
Where are you ALEX???? Please HELP ME!!!!!
Posted: Mon Oct 10, 2005 10:24 am
by wlad
LIVE 5.0.2 crash every time i want open my set live4...
I must resart all my work since live4????
DON'T BUY LIVE 5!!!! IT's A BIG S...T!!!!!!
A COMERCIAL OPERATION?????
GRRRRRRRRRRRRRRRRRRRRRR!
Posted: Mon Oct 10, 2005 11:55 am
by mdb
You need version 5.2 from waves.. Its the 5.0 shell dll thats making your plugins not work. I had the same problem. Update or upgrade to 5.2 and get the new 5.0 shell dll and you should be good to go..
Posted: Mon Oct 10, 2005 12:20 pm
by jbible
Never experienced problems with Wave Shell 5.2 and the L3 plugs used as VSTs inside Live v4 or v5.
same problem with waves
Posted: Mon Oct 10, 2005 1:04 pm
by allears
I went to the waves site and the latest update I saw was 5.01, where is this "waves 5.2" you speak of????????
Posted: Mon Oct 10, 2005 1:08 pm
by amo
Guys,
Have you simply given a look to a sticky thread, just up that one ?
http://www.ableton.com/forum/viewtopic.php?t=25171
Best,
amo
Posted: Mon Oct 10, 2005 3:55 pm
by wlad
I didn't find waves 5.02 version.... what about this?
amo: yes, i read this topic! it's not a solution!!!!
my question is : live4 run perfect why not live5?
I think i loose 120euro for moment because i can't use live5 with my set!!!
Sorry but this is not good for ableton...
(excuse my dirty english)
Posted: Mon Oct 10, 2005 3:59 pm
by amo
I don't mean to say that there is a solution in the thread I pointed out, but that the problem is acknoledged by people both at Ableton and Native Instruments, and that a solution may come quite soon. On top of that that information was there since first day of Live5 release, though I understand you maybe didn't pay attention.
Sorry for you, but you'll get sorted soon,
cheers,
amo
Posted: Mon Oct 10, 2005 5:11 pm
by atom_b
wlad wrote:Sorry but this is not good for ableton...
Sorry, but obviously it is not good for you:-)
Anyway it doesn't necessarily have to be ableton's fault, but who cares, they say they're working on it.
I had some trouble getting 5.0 Waves Shell and 5.2 Waves Shell running in parallel (wich was needed because not all Waves plug-ins are updated to 5.2). But I tripped Live 5.02 by deleting shell 5.0 and adding it again later on while Live was running, I then let Live rescan the plug-ins folder. Works fine since then.
But I had to readd most of the Waves plug-ins to my sets after that, and since then most of them work fine, except the cpu-expensive ones. But after all no crashes when starting up live, and a way to save sets where Waves plug-ins are used for now.
I suggest, you give Waves 5.2 a try.
Good luck with your gig
BV
Posted: Mon Oct 10, 2005 7:45 pm
by Johnisfaster
I like how he thinks ableton isn't aware that there are some bugs. or that they haven't acknowledged it.