BR [fixed] - LiveSlice causes EXT to quit unexpectedly

[stuman]

This is happening on LiveSlice v1.42. Here are the steps to reproduce:

1) Open EXT standalone.
2) In the main area, right-click and select LiveSlice.
3) Double-click the LiveSlice icon to open.
4) Close the LiveSlice window.
5) Right-click on the LiveSlice icon and select delete.
6) In the main area, right-click and select another VST. (I tried Vanguard and Reaktor5)
7) EXT displays several 'Buffer Overrun Error' messages, then disappears.

[Juanjo]

I cannot reproduce this... what version of eXT are you using? Does it only happen with LiveSlice? Any other info that might help identify the problem?

[DarkStar]

Hmm, Works fine here.
Tried with 3 other VSTis.

[stuman]

Hey guys,

I'm using the latest versions of everything. This only happens after deleting LiveSlice from the main area in Ext. So far I only tried Reaktor5 and Vanguard. I'll try some other VSTs and then report the results. Which VSTs did you guys try that isn't reproducing the problem? Hope I'm not the only one seeing this problem.

System Specs:
Intel CPU P4 3GHz
2 Gigs RAM
ASUS Mobo
M-Audio AP2496
Edirol PCR30

[scuzzphut]

I tried it here with the latest beat of EXT and Livelslice 1.42
Works fine

loaded ASynth, Tau, Imposcar, ST2LE

[Juanjo]

Stuman, I tried Wusikstation, a few freebies and energyxt itself as I don't own reaktor or vanguard... try to reproduce it with a free VST or with eXT-vst so we can try to emulate your setup.

[Guenon]

I can reproduce this in eXT 1.3.6 with LiveSlice 1.42 and the free Superwave P8 v1.6. Although, as I posted in another thread, I still can't quite put my finger on it: the behavior seems to be slightly different every time, and I think it's not that dependent on the other plugin used.

Anyway, just a moment ago I tried it with the steps listed in the first post, using Superwave as the secondary plugin, and nothing happened. Then I inserted another LiveSlice instance, clicked around in the main eXT GUI, dragging modules slightly and right-clicking their context menus visible and so on. Poof, the whole eXT window vanished.

While writing this, I continued to try the combo on two quite different machines (Intel Pentium M based laptop / AMD Athlon based desktop), this time with eXT as a VSTi hosted inside Ableton Live. After repeating the same steps I actually got the otherwise very stable laptop to throw a sudden blue screen and -- get this -- the incident wrecked the Ableton Live unlock data. Live started up in demo mode and wanted to be reactivated. I did have fresh system partition Ghost images handy, however, so status quo is already restored

The desktop computer didn't show a blue screen but went completely blank, then rebooted from the BIOS POST screen onwards.

[stuman]

Hmmmm. After further testing, looks like I'm experiencing much of the same behaviour that Guenon is noticing. I've tried various NI plugins, Imposcar, String Theory, Vanguard, and Oatmeal.
So far, the only time I see the 'buffer overrun' msgs is when I open Vanguard (after deleting LS). Overall, I'm getting haphazard results. Sometimes, just simply right-clicking in Ext's main area causes Ext to disappear. Also, after a number of times that this happens, I notice that I can no longer select my midi controller for input. I actually need to reboot my system in order to select it again.
FWIW, this behaviour doesn't occur with LS v1.40. I appreciate all the replies. Hopefully I can figure this out. As of now, I'm at a loss.

[Juanjo]

I still cannot reproduce any of this behaviour sorry, I tried all the suggestted nuances several times with Superwave P8, the Vanguard demo and other plugs. Note that I'm doing the test on my ancient PentiumIII home machine on purpose. I'll try to have a go at my main daw during the weekend if time allows, but hopefully somebody else will take a look as well?

That said, I wonder if you should report this in the energyXT forum as well once you have a consistent way of reproducing it... from past betatesting experience, energyXT can be quite picky sometimes where other hosts might not even blink...

[GilJ]

I have had Live 5.2 quit a couple of times while playing with LiveSlice 1.42.
I have not been able to find how to reproduce it however

[ohm]

There definately were some problems with closing and deleting LiveSlices - I was able to partly reproduce and hopefully fix the problems described in this thread.
Are all those of you having problems with 1.42 on the beta list? If not can you please contact me via email - I have done a few bugfixes that I'd like to have verified - sending out a beta as soon as I hear word from GilJ, Stuman and Guenon.

[GilJ]

Waiting for the 1.42 beta to verify the new bugfixes

P.S. Ohm, have you been able to reproduce/fix my last B.R. in my last post here: http://www.kvraudio.com/forum/viewtopic ... &start=165 in the 1.42 beta?

Cheers
GilJ.

[Guenon]

As GilJ noted that v1.42 has also made Ableton Live crash when hosted alone (not specifically inside eXT VSTi), I decided to revert back to v1.40 for now. Other than testing purposes, of course

Ohm, I sent you a PM so that you can add my contact info on the beta list.

[-{n8}-]

I have had Live 5.2 quit a couple of times while playing with LiveSlice 1.42.
I have not been able to find how to reproduce it however

I have the same issues, glad to see i am not the only one

Ohm, I'd also like to be a beta tester. The sooner this pluggin is stable again, the better.

1-0ne

[ohm]

beta testers: check your inbox - I am very confident the latest beta will take care of all the issues mentioned