WE need a SONAR X3 E Update ;) SOON!!!!!!!!

Alex, I already read the original post, but as long as the title says, "Outstanding Issues as of X3D...," I think any outstanding issues confirmed by CW or several posters are eligible to be listed in this thread. And, if you think about it, why create a thread for an issue that has already been confirmed by CW? As I said, all my issues I posted in my last post have been confirmed by them, and, no, I didn't create any thread about them because I was very sure they were reproducable issues. What I always do (and what I recommend posters to do as well) is submit a bug report to CW if you're very sure it's a bug (to save time), and if you're not sure, then post it in this forum.
 
Most of the issues I posted in my last post are very easy to reproduce (takes only 5 min or so), and unfortunately I don't have time to summarize each issue. Maybe you could do it but of course it's not an obligation. So if it's hard, just leave them there (or tell me to delete them). Maybe the title should be "Summary of Issues Posted as of X3D," I don't know. But anyway, I appreciate your effort summarizing the issues others posted. I know it's a very time-consuming job.
Thanks

> unfortunately I don't have time to summarize each issue

We find ourselves in the same boat...
 
>why create a thread for an issue that has already been confirmed by CW?
 
To avoid debating issues on this thread (like we are now), I totally understand what you are saying, but then when things change it's going to be difficult to manage it within the same thread, at least a thread can be closed off.. Anyways we know you posted them here.... Cheers..

I think there won't be any debate if the issue has already been confirmed by CW. If someone says, "No, that's not a bug," then you just need to say, "Shut up mate, it's been confirmed by CW. So contact them if you want to debate about it."
 
Anyway, maybe I should have posted the bugs one bug per post and one post per day to give you time, so that the link in the original post could direct to the post.
 
I'll post no more issues here unless I find time to summarize them. Thanks for your effort again.
 
 
 

Hey Jlien you've already stated these are confirmed by Cake. I believe you :)

You can keep posting and will put them in the first post if you can give me links to the thread discussions (so they aren't discussed here). Any new issues just post a new thread about  it and tell me here (or maybe I will find it). Just don't want a load of issues embedded into one thread, I'm just compiling a shopping list if you like. I totally understand if you don't have the time though... Thanks...

CakeAlexS
> unfortunately I don't have time to summarize each issue

We find ourselves in the same boat...
 

 
I know everyone's busy, but there's at least one thing that's different between you (and most of the others) and me, which is, as you know, I'm not a native English speaker and it's probably taking me at least twice as long as others to write posts here. Submitting a bug report to Cake isn't a piece of cake (although not so difficult, either), so both creating a thread here for confirmation and creating a report to CW are a little too hard for me. Also, I know there are posters who don't have to work or who can post from their work computer during work. I have a day job (although I reduced it to 4 days a week recently) and it's very busy, so my time to spend on making music is very limited. I might be able to find time to summarize the issues I posted one day, but I guess you'll learn something by reproducing them. Who knows? They may improve your workflow.  

Thank you, CakeAlexS, for starting and organizing this thread.
 
Has anyone ever took the time to cross-reference the X3d update/bugfix log to see his/her own, submitted fixes; also checking for "when" said fixes were submitted?
 
http://www.cakewalk.com/s...reader.aspx/2007013355
 
And I'd still like to see an update/bugfix log for X3.
 
Makes you wonder if it's two steps forward, one step back. Are all of the problems that remain in X3d carried over from the X2a days or are they all new?

Just my opinion this should be taken with total scepticism:
98% of the bugs are legacy (pre X3D), some from a galaxy far far away.
Maybe 3 have turned up with X3D going by these forums.
 
In a way what I'm doing is useless, I hope it's helping Cake QA though (although I suspect they are way ahead of me).
 
I do want to demonstrate though that maybe it's time to make reproducible issues public like open source software so we can see it in tabular format. People actually like it if you have something like a bug tracker, it can actively engage an online community.
 
The reality is that Cake has probably about 1000+ bugs in their internal bug tracker (this is normal with most software, and most software gets by just fine with bugs, I bet this will be typical with any DAW) and they are worried what will happen if we see it.
 
This is a pathetic attempt from my end to say..... be transparent !:)
 
Cake seem to be ever more moving towards it (check out their activity in these forums recently) so maybe we're all swimming the right direction...
 
Cheers...

On second thought, I'll probably create threads for the issues I posted earlier (just to provide links to the threads) because I believe this thread can be helpful for specific groups of people (e.g. pre-X3 users wondering if they should upgrade, current X3 users wondering if the bug they've just found themselves has already been reported to CW). But that's only if Alex promises to keep using Sonar and update the original post (at least till X4 comes out, hopefully till he dies or till CW makes known issues public).
 
Anyway, when the number of issues in the original post gets much larger, I really think they should be categorized by feature or type of issue. Also, I think the thread title should be in capital letters and the exclamation icon should be applied to differentiate the thread from ordinary threads.
 
Thanks

Yes You could keep a bug summary similar to mine if you like just for your bugs if you think this is easier... I can just point to it saying this is a list under your control if you think you are going to have loads and loads of them. Maybe you could point to mine. We can merge them later if necessary.
 
Anyway, when the number of issues in the original post gets much larger, I really think they should be categorized by feature or type of issue. Also, I think the thread title should be in capital letters and the exclamation icon should be applied to differentiate the thread from ordinary threads.
 
Problem is this is forums software not bug tracking software, so quick and dirty is what I'm doing (for speed more than anything). There is no particular order...
 
My rules are:
if Cake can reproduce = bug
if other people (say 2) can reproduce exact steps given (test case) = bug.
 
Thanks...