Well I think we can rule out XP in what ever incarnation.  The hardware is a strong possibility. But what I am thinking is the install of X1 may have some flaws that either mess up some run time libs of C or it could be that some DLs have a corrupted part that is not noticed right off the bat. One reason I think that some have reported a messed up 8.5.3 install after an install of X1 is due to C run time libs being effected somehow. I don't know how one could test this but I think it should be looked into.

I do know that the DM Pro install is broken for X1. 

By the way if someone can come up with a better title please submit it.  I really don't know how to ask this question well enough in very few words! I'm not really kidding though.

Biggest show stopper: if you have multiple clip layers overlapping in one track, you can only edit clip automation on the bottom-most clip.

Also, I used to be able to highlight a bunch of measures and then automatically add automation nodes at the beginning and end. That will not work anymore.

Still using X1, though, but the little nits are beginning to drive me batty. X1b better be the siht or I will be asking for my money back.

Using the loop construction view , ends up with either a crash or a memory leak. Meaning after using the LCV , doing a simple bounce you need to restart the software. The fact having multiple sends on one track , just disables by it's self, Restart needed,  And the most annoying bug is the lost of sound playback( Asio problems).
 Pro channel is useless when it turns off by itself. Going back to activate snap is pita.
 And then there's the Lasso bug,That makes arranging clips at different lengths impossible to cntrl copy.
 These are most annoying problems im having. not a 100% show stopper's but more so as a workflow killer. when you have 5 restarts a session , your workflow just sucks and you spend more time trying to figure out what went wrong.
 BUt even with all the problems I continue to use it everyday, I did notice 3 grey hairs since the release of X1. OHHH Boy.. Thanks CW,

This might be a bit off topic, but the plan is that whenever X1b is released, the first thing I'm going to do (after backing up/setting restore points etc) will be to completely uninstall 8.5.3 and let X1 do what it wants and put stuff where it wants (again, apart form a couple of libraries that need to go to a specific location).

I'm hoping I won't have to install 8.5 again afterwards.

James I don't see those as show stoppers at all. They may be annoying but they wont stop you from making music.

If you hadn't been able to do that in 8 then is it something you would have even noticed?

djjhart@aol.com


Using the loop construction view , ends up with either a crash or a memory leak. Meaning after using the LCV , doing a simple bounce you need to restart the software. The fact having multiple sends on one track , just disables by it's self, Restart needed,  And the most annoying bug is the lost of sound playback( Asio problems).
Pro channel is useless when it turns off by itself. Going back to activate snap is pita.
And then there's the Lasso bug,That makes arranging clips at different lengths impossible to cntrl copy.
These are most annoying problems im having. not a 100% show stopper's but more so as a workflow killer. when you have 5 restarts a session , your workflow just sucks and you spend more time trying to figure out what went wrong.
BUt even with all the problems I continue to use it everyday, I did notice 3 grey hairs since the release of X1. OHHH Boy.. Thanks CW,

I would say the crashing is a big show stopper.

May I ask for as much detail on your system specs and exactly what you are doing when it crashes?

The sends problem is a new one for me. I have not had that problem as of yet nor heard of it so far. Again more detail would help. What are you sending to, what sort of plugin?

Bristol we have never had to uninstall a previous version in the past. This sort of makes me wonder about the install of X1 as being a problem child by itself. I think CW needs to look a bit closer at it. We do know that the install for Dim Pro of X1 is broken.

My X1 doesn't have any showstoppers.  Annoying issues here and there but they don't prevent me being more productive than ever.

Asus P6T Deluxe, 12 GB DDR3
2 x RME Fireface 800 @ 64 samples, 1394b card TI based
System: Intel SSD
Data: few 1-2 TB drives
Win7 64, SONAR X1 64

Easiest way to crash X1 in my setup:
- loop Amplitube plug-ins
- use multiple Melodyne x64 instances.

Hey John , I create an audio track with a kick , used that as a trigger track for gating another track, and I use the same track and send another insert to another bus or track , when I have more than 1 send at weird times the trigger track out of the blue starts playing, I click post on off turn it on off nothing works , If I restart the sends work as they should. Real Pita..
 Crashing has improved 10 fold since I dont use ASIO drivers, My Tascam fw1884 , works like **** only in X1.Right now Im using a Stanton Open scratch amp WDM working ok .My delta card dosn't work at all Crap.
 Im on Xp 3rd edition, which will change as soon as x1b is out , Going 64bit on an SSD. Hoping that will resolve alot of problems will see. Yeah crashing is a big problem but Im into the habbit of saving alot almost after every good edit. I keep chugging along.. Bascilly when ever I come onto the forums its cause im waiting for a restart. and Cw killed my workflow.