mike_mccue


"Sorry if my grammar was not the best. I thought I made a valid point just the same. No one has to agree with it but its the way I see it.

As to the poster my post was about and how often he has posted it could be seen as one reason we still have so many bugs. Not enough posts.

Together we can have a big impact on the direction CW takes. We have seen this in the past. MIDI tools in Sonar7 or 8 for example. Or we can ring our hands and be upset or we can give valuable feedback that the CW people can use to make the product better. One reason I don't find Mike's posts all that bad.

The one thing I found repugnant in the Burkek post was the admonishment to not participate in any form to help us all get a better DAW.

I am not too sure why one would object to that point when one is on here all the time with criticism of X1 as Mike is.  It seems contradictory to me. 

Or is it just simple bitterness? "



I've noticed you have taken on a new habit. Are we going to proceed by addressing each other indirectly in the third person? It seems trollish.

I'll give it a try... but I have to admit I find it sort of creepy.

John might make a more compelling argument if he pointed out that if I no longer intend to make a hobby of bug hunting I'll end up depending on John to spot bugs.

I guess if I thought about that too deeply I might find the idea terrifying.

Lucky for me I don't spend my valuable time worrying about what John thinks.


yeah that felt creepy... I think in the future I'm going to go back to addressing John directly.

Danny Danzi


Mike V: Your bug is confirmed on my end. Also confirmed in instrument track template saves. When the track template loads up, the PC settings are jacked from what was saved.

As far as the discussion you guys are having, I have mixed feelings about the whole thing. When I first started really taking part in the forums here, one of my first messages was how upset I was for feeling the need to fill out a problem report or "do their job" so to speak. All the stuff you guys that are opposed to as well as the time etc, were all my issues too. I was a bit blunt with my replies during that time because I was frustrated.

Let's face it, to those of us that make money using this software, there is a trust barrier that really can't be explained. We have deadlines, important decisions to make, clients to make happy, contractual obligations that could get nasty if we don't deliver the goods on time...the list is endless.

My feelings haven't changed totally in the way I think, but I've altered a few things here and there which I'll get to. I sincerely feel I would be much happier waiting for a Sonar release every 2 years or more and paying more for it if there were the possibility for it to be more stable. I've said this numerous times. The old bugs need to be fixed...this is a must.

We all have quite a few versions of Sonar that have, in a sense, let us down at times. The 3 best versions for me have been Sonar 5, 8.3 and 8.5. That's really all I need from a working DAW at this time....and even those have some bugs that stem back a ways.

What we are seeing with X1 is frustration which is why the hostility is on the forum. I can only compare our new software each year with a date you are really looking forward to that goes sour every time you try the dating game. You know, you're all excited, can't wait to get there...you find out it's either a complete waste, or it wasn't what you thought it would be. I made up my mind with the release of Sonar 8, that I was no longer going to even visit the forum (unless I had questions or problems) or buy anymore Sonar products because we all know how bad that was when it first came out. I really had a bad taste in my mouth from it...I cannot tell a lie.

Now here's where my opinion has altered. From my past experiences with Sonar 8, I've had the chance to talk to Noel behind the scenes as well as Willy Jones and 2 Seth's. They've explained quite a few things to me that I had never thought of and they helped me each time other than one issue that no one can seem to fix. Whether anyone would consider those things credible or not depends on the person. I found them credible and sincere.

However, due to a few things that I had assisted with that were bothering me as well as my bug reports, I was able to assist in getting some important midi issues fixed that drove me crazy. If I wouldn't have stepped up to report the issues and wasn't willing to try the things Willy had asked me to try along with sending some crash dumps, maybe this issue would have never been fixed because it was broken in Sonar 6 and Sonar 7.

I'm not crazy about stopping what I have to do to fill out a bug report or search for things on my system that I know nothing about. It does take time and time is money for those of us that make a living from the engineering field. BUT, I'm glad that I made a difference and helped to fix an issue I had as well as one others may have been having. It was actually quite rewarding to me to have taken part in that. On the other hand, there are quite a few people that have done this and haven't had the results in which I have had. Why? I have no idea...but I'd be pretty upset if I didn't have the end result I've been fortunate enough to have.

It's pretty cut and dry to me. We either try to make a difference when we can, or we don't and unfortunately have to use an older version of the software or switch to something else. The release of Sonar X1 and all the stuff that has come with it, has altered my opinion once again. If or when it gets fixed, I will DEFINITELY wait until things are stable before I ever consider purchasing a new version. I need to get my work done with software I can trust. Though X1 works for me and how I use it for the most part, there are things that I still do not like about it and I would never do a project for a client in it because it has let me down a few times on my test projects for myself. I can't take that risk and no one else should either if they are in a similar situation to mine. If I have the time to report something, I definitely will because I like to make a difference. If I don't have the time...I don't have the time and chances are the thing may get missed. My loss.

Do I think the Bakers are working hard? Most definitely...but something is wrong somewhere and if it isn't with them, it's somewhere. There's no doubt these guys are working countless hours trying to make a difference. Maybe it's the beta team? Maybe it's who they have in charge of what gets tested in the beta team? Maybe they were rushed to release? I don't know. I posted a thread asking how people would feel being the creators of Sonar seeing the list of bug fixes that were in X1b. I was sincerely curious as to what answers I would get from anyone in the Bakery. Not as a dig on them, but because if I were a Dev or whatever, and saw all that stuff posted on something I helped to create, I would really think that something went wrong somewhere within myself or my staff. Though I think highly of them for sharing that list with us as well as the updates each week...we have to keep in mind that X1 came out immediately with an X1a patch...which was helpful for some and good they were able to catch some stuff....then a load more stuff with X1b...something is wrong somewhere...that's all I can say and we really can't be upset with ANYONE on this forum that is frustrated by this no matter which road you decide to take here.
 
I can't fathom the frustation Mike V has had with this. He's been around as long as me or longer. He definitely knows how to use the software. I'd be absolutely livid if the initial release of X1 didn't work at all for me and I had to wait for the X1b patch to even see it install and at least fire up. If anyone doesn't see this as wrong even if you've been successful with X1, have a heart....you may be in that position some day.

The one thing I found repugnant in the Burkek post was the admonishment to not participate in any form to help us all get a better DAW.

mrfitz


Beyond the whole "Cakewalk X1b public beta" that is being run, this pretty much renders the Prochannel useless. If you can't tell by looking at it what the settings are how can you safely add it to a project?

The more cakewalk giveth, the more they taketh away.

spanky

mrfitz


Beyond the whole "Cakewalk X1b public beta" that is being run, this pretty much renders the Prochannel useless. If you can't tell by looking at it what the settings are how can you safely add it to a project?

The more cakewalk giveth, the more they taketh away.

I have no scientific proof but I often wonder if the Pro Channel is responsible for a lot of the problems X1 has had. ???

mudgel


No need to as Noel's been on this very thread and said they can duplicate the problem. It was he in fact that confirmed it.
And because I'm annoyed with Noel and Cakewalk I'm not going to.

There are also personal issues involved between cakewalk and myself that I'm not at liberty to go into because I promised I wouldn't. nuff said.

mudgel


No need to as Noel's been on this very thread and said they can duplicate the problem. It was he in fact that confirmed it.
And because I'm annoyed with Noel and Cakewalk I'm not going to.

There are also personal issues involved between cakewalk and myself that I'm not at liberty to go into because I promised I wouldn't. nuff said.

trimph1


I thought it was DarkNight....

Noel Borthwick [Cakewalk
]

We were able to reproduce the issue with the pre/post state not being applied on loading files. This issue was NOT logged earlier hence was not on our radar. The issue that was fixed in X1B was the problem with the prochannel enable buttons not saving properly. I must emphasize that bugs MUST be logged to guarantee that they are investigated. Talking about them on the forum is not sufficient.