Ten hours of work on X2: impressions and issues

piangio


It seems that there is some module but it's not visible and/or able to be modifyed. 

Did you see this by chance?
 

 
Close up view: https://dl.dropbox.com/u/4909348/WhatTheHeck.jpg
 
The space I circled...actually has a Concrete Limiter in it that you can't see yet is enabled in the project. If you look close you can even see the little button to the left that enables and disables it. Pressing it does nothing. This has happened twice to me so far and I can't find a recipe to repeat it. Opening and closing the project brings the limiter back. Saving with it in this state doesn't affect it either. When you open the project again, all is well. Is this the sort of thing you are seeing?
 
-Danny

piangio


Exactly! The missing module I didn't find was L2A... The Audio engine always stops acting on VX64. Sometimes happens with other plugins or virtual synths. Good: Audio metronome switchable on the fly, while playing!!! Great!

Ok, though it pains me to say this....I'm glad I'm not alone. I spoke to one of the Bakers on this but since I can't come up with a recipe and it hasn't happened to me since, we may need to buddy up on this one piangio and see if between the two of us, we can find out what's going on. If you can, try to remember what you did to make it happen or try to make it happen again based on what you think you may have done.
 
I've been trying everything I can think of to make it happen but so far, I haven't been successful. I'm wondering if it may have something to do with screen sets. Maybe we change screens, work a while in a screen set and then we lose the plug? I gotta figure out what this is.
 
The good news is, if it's happening to others, chances are we'll get a fix. The bad news is, if it's just you and me, it may not hold much of a priority. That said, I don't think (I could be wrong though) we need to worry about it when you see it happen. Even if you save your project with the plug missing, when you reopen it, the plug will be back. The first time this happened to me, I chalked it up as a weird anomaly of sorts. The second time it happened, I saved the project in hopes of opening it and the plug would still be gone so I could submit it to support. But low and behold, closing the project and reopening it...the plug was back. So though I don't think it's anything to worry about, it definitely shouldn't be happening.  
 
Let me know if you find out anything more on this. I'll get back to you as well if I find out anything else. :) If we figure this out, the next time I'm in Italy (my homeland!) I'll buy you a beer! Hahaha. :)
 
-Danny

mudgel


I used to get this in X1C but not since x1D and haven't had a hint ignition in X2. 
Will keep an eye out for it and bookmark this thread to come back to.
If we could start a thread and list and number issues like this to refer to and update I'm sure It would be a great resource for troubleshooting and bug reporting.

Hmm...interesting observation there Mike. I wonder if the Bakers can back-track and take a look at what may have been broken in C that was fixed in D that would contribute to this. I didn't have Expanded at C at the time, so I never saw this before. I got it at D I believe. I just wish I could find a recipe for it. Thankfully it doesn't mess up anything other than a reload of the project.
 
-Danny

Danny,

I'm getting the same "missing module" as shown in your picture but with me it's the Console Emulator. Add one crash when dragging an FX chain into the PC, another adjusting a knob in a PC FX Chain and another when resizing the track view and I'm crashing more than X1. My first impressions of X2 are not good despite really liking some of the new features...

Ken

I've seen the mysterious module too but I encountered a strange volume drop while using markers or the shuttle to control where the playback cursor is. I'm using a project created in X1 with all the Pro Channel modules bypassed (Global On/Off button). The volume drop was happening when I would shuttle backwards in the timeline. At first I was stumped but after enabling the Pro Channel modules in the console view, I noticed that upon rewinding, the Pro Channel modules would unbypass themselves and cause a BIG volume drop. Really wierd. I fixed it by bypassing all the Pro Channel modules in the Console View (again) with the Global On/Off again AND bypassing each individual module in each Pro Channel. I then saved the file, reopened it and the problem went away. I did get a mysterious freeze up while opening up the piano roll in this project. After a reboot, it didn't happen again but this happened before i experienced this volume drop issue. Indeed strange gremlins are lurkin... Here we go again...

I saw this behavior in X1 plus a lot of other PC bugs. The whole reason I upgraded to X2 was the hope that they would finally fix this PC disaster. How many people are going to have to report this before the whole "we cant reproduce this so theres nothing we can do" isnt tolerated any more?

UNREAL. 2 VERSIONS IN AND IT STILL DOESNT WORK RIGHT. 

SORRY FOR CAPS. CELL GETS STUCK ON CAPS LOCK HERE. 

Perhaps it would help to list your graphics card and driver version.

 
Good idea, John.  These do sound mostly like graphics/redraw issues.  Not that it makes it any less frustrating...
 

I can give you my impression after 1 minute of work: it doesn't work -- it crashes. I'll be sticking with X1 until the bugs with X2 are addressed.

Btw, some of the bugs in X1 made it into X2, e.g. in PRV, when you add tracks, all of the controllers (128 of them, I think) appear at the bottom. Cakewalk had acknowledged that this is a bug, but have managed to preserve it in X2.

lol, seriously?

When has it ever been different, with any software?

And what "errors" are you experiencing on your X2 installation?

it's not beta, it's "early adopter" ;)

i'd wager there's a patch by the end of the month maybe?

X2 hangs. ProChannel does not work well. Scrin here.

hi bub, what are the engine improvements?

lol, I just experienced the same ProChannel issue in the picture above. My Concrete Limiter was just a top bar. I couldn't remove it.

But when I inserted another instance of it, the other Concrete Limiter became visible. I then removed the other instance and all appears to be working okay again now. No crashing while moving between different tracks and ProChannels.

After a few hours of playing around, I find X2 to be relatively stable -- not much different from X1d in that regard -- EXCEPT for the missing PC module issue.  It's happened to me several times, with several different modules other than than the standard 3: Console Emulation, Softube FET Compressor, and a few others.  As with the other reports, adding the same module to the strip fixes the problem, as does closing and re-opening the project. 
 
My DAW is using the Intel integrated graphics on a Sandy Bridge CPU, nothing fancy.  Seems like this should be a pretty easy thing to diagnose.  Thanks again for all the extra support!
 
Cheers,
Eddie

I tried and tried but could not get the missing PCM to happen, just the menu not going away over a PCM draw issue.