[ANSWERED] AND I STILL CAN'T CRASH X3!!!

piangio
Same situation here. On new project "NO PROBLEM AT ALL".
But if I work on X2 old project I get Crashes...
Maybe X2 projects carry with themself X2 bugs ???
I don't know. I'm trying exporting projects "per tracks" and generate a new project on X3.
hope it works...
 

The couple of X2 projects I've opened have worked fine thus far. Have you tried making all plugins in those projects inactive and then cycling them on and off, to see if maybe there's a particular plug that's crashing the party?

I've not started a single new real project in X3. Only been working on mixing/editing X2 projects. No problems whatsoever!

I managed to crash it repeatedly. But only when I try to use V-Vocal.
 
With Melodyne it does not crash as long as I bounce the audio clip first.
 
I seldom record vocals so I don't know if it's just me... :/

musicroom
Do you guys see any changes in resources used from X2 projects running in X3? Reason I'm asking is I loaded a large X2 project into X3 last evening and I had to raise the buffer settings to play it. 

I haven't noticed anything other than when using Ozone, I no longer get memory spikes. It was never anything super serious but my CPU usage would jump about 8% or so every couple of seconds while running in X2. Engaging PDC would stop the spikes so I never really looked into it any further? With X3 I don't even have to engage PDC with that plug any more, so I'm guessing the overhaul of the VST engine deserves some glory?!!
 
So far X3 is solid as a rock! As I add a plugin the usage meter jumps accordingly but settles and remains quite constant. Melodyne tells me to raise the buffer while using it? I don't bother (haven't since X2) and I am yet to suffer any dropouts or glitches in playback or recording thus far.
 
Actually the only weirdness I have experienced? I talked about in the 'VST Scan Issue' thread. Where my browser wouldn't display producer effects if I clicked 'Default All Plugins.' It would display all instruments and all of my plugs but X3 plugs like compressors, the blue tubes etc. would only display if I had the browser set to 'X3 Producer Effects.' But as I stated in that thread, a close and re-open of X3 sorted it!
 
I must also add that as I have owned, Melodyne Editor, for quite some time now, I have never used v-vocal for anything other than a play around. I have seen a few threads where it looks like that plug is giving peeps grief for some reason. Has Gibson made the purchase yet? Can we flat out start blaming Roland for no other reason than the hell of it?...

ProjectM
Sounds good! I installed X3 yesterday and only played arounda  bit. Seems pretty stable so far. I'm have this thing I need to do with a deadline next monday so it will be interesting to do some stresstesting. So far, I'm really liking what I'm reading here though ;)

With X2 I've had a couple of seconds of the 'Not Responding' appear in the header on the odd occasion (mainly with heavy projects that were pushing my RAM.) But the program always came back online without having to close and nothing was lost or went haywire. It was smooth sailing all 'round!
 
After running a few large projects (large for me) and not being able to make X3 blink. I did what I stated in the OP to see if it would cause any weirdness. Streaming videos and doing multiple things on the net simultaneously, has been able to crash Studio One a couple of times. And though it's never fully crashed Cubase 7? I have had to close the song in app and re-open the song to get it going again. I realise those issues are more likely to be due to my PC nearing maxed, rather than a program problem? But I had to post when X3 stood staunch and unaffected. As if it were daring me to use more than my RAM limit?
 
Somewhere a (many?) producer(s) is (are) shaking his (their) head(s) at my habits...

I crashed X3 by opening a Waves Renaissance comp VST3 as my first action after opening my (X2) project. After closing another (X2) project. No hang, just boom, exit, Sonar stopped working. Couldn't reproduce though.

I had my first crash. I opened LimiterNo.6 in the Pro-Channel and it wouldn't do anything, so I dragged it over to the fx bin. I stopped the playback, and hit play and it worked for about 10sec then crashed. I couldn't see a way to send a report ...everything has been fine since. I'm loving X3 so far!

robert_e_bone
@Royal Yaksman
 
Regarding you "Somewhere a (many?) producer(s) is (are) shaking his (their) head(s) at my habits..." post above, 
 
Don't sell yourself short - it's not just producers that shake their heads at you - us keyboard players do too - hee hee :)
 
Bob Bone
 

Yeah I'm kind of used to getting it from all directions.
 
I will however maintain 'til my grave, that bouncing stems is boring! Clearly I need the comedy channel on during it!!!

LePou's ('Poulin') amp sim plugins destabilise it (they are 64 bit / VST2).
 
The symptoms are that it stops responding.  Those are the only problematic plugins I've found thus far.

Ol

Royal Yaksman
It took a bit of digging but I found an X2 test song from a while back that contained the VST 2 versions of Waves SSL, NLS and Izotope Ozone 5. It took all of about 5 seconds of being open, to crash like a brick through a windshield!!! Turns out, Ozone has it's own fault reporter as well, in case anyone is interested? I filled out the Cake crash dump fault report accordingly...
 
Well my bubble is burst! Thanks heaps, Noel! Hrmmpfff!!! So VST 2 versions are a "no go" of these plugs, when the VST 3 versions are installed in X3!!! 
Incidentally, I've noticed that only the VST 3 versions of waves plugs show up in my browser? I did nothing to make that selection, so I assume this is intended?

You can mix and match VST2 and 3 plugins from most vendors. Only Waves have a problem that we know of when a VST3 and VST2 from waves are loaded simultaneously.
It should be no problem to use a VST2 from another vendor alongside the VST3 from Waves.
By default with waves the corresponding VST3 plugin is loaded using automatic migration to avoid this issue.
 
What is the exact circumstance of your crash?

Noel Borthwick [Cakewalk]
You can mix and match VST2 and 3 plugins from most vendors. Only Waves have a problem that we know of when a VST3 and VST2 from waves are loaded simultaneously.
It should be no problem to use a VST2 from another vendor alongside the VST3 from Waves.
By default with waves the corresponding VST3 plugin is loaded using automatic migration to avoid this issue.
 
What is the exact circumstance of your crash?

I opened a song that was created in X2. Once the general frame work of X3 had rendered, the first thing I saw was the outline of the Waves SSL Eq first appear normally, then it went all grey. What I think is the border (outline) of Ozone 5 then appeared but with nothing inside the border, then the border disappeared. Around this time 'Not Responding' appeared in the header bar. About 5 seconds in all elapsed before first Izotope's Ozone crash log appeared, followed by Sonar's. Unless I missed something, I only had the option to fill in the initial details of the crash. Checking the report online there are empty details as to computer specs, interface etc. I take it I missed something? Is there anyway to go in and update these to give you guys a more complete report to work with? The reporter had 'Not Responding' in its a header twice, while I was filling it out and sending it. The reporter number is: CWBRN-20124.
 
I have been able to open a few songs from X2 prior to this with no problems at all. But they didn't contain any Waves or Izotope plugs.
 
*The OI at the top has me wondering if you took my tone wrong? My thanks and Hrrmpff, was intended jokingly btw*

Royal Yaksman
*The OI at the top has me wondering if you took my tone wrong? My thanks and Hrrmpff, was intended jokingly btw*

Lol no thats a typo in my post thats all :-P