brconflict

Mod Bod

rabeach


I mean no offence to anyone and without a doubt it is my on ignorance of working in this field but this has been gnawing at me for a while. Why do any of you allow your clients to watch you work. What is to be gained by that? I do electrical and security design work mostly for the DOD and I would never allow them to watch me work. I prepare for any and all meetings with them and ready myself to handle any and all criticism of my work in a diplomatic manner, which means with the DOD I'll do it the way you want it done. But I can't imagine allowing anyone to watch me work. Now that being said I have been put under the microscope upon rare occasions in meetings and been forced to design on the fly in front of high-ranking personnel. 

I want them to see how totally amazing I am.  

haha! But seriously, being a Mix engineer isn't a magic show. It takes good ears, and although sometimes you can work faster without the client present, when you're working major-label gigs, be assured that not only will you have multiple egos in the room, you're likely to have label suits on their mobile phones watching, too. It's a very common thing, actually. I'm a Network Engineer by day, and I can say that not only does that job benefit from the client NOT being in the room with me, they get bored very easily. 

Thanks for the post. Wow, that must be a very stressful occupation being a mix engineer then. I guess I have a better understanding of why software stability is such a big issue. I use cad and several analysis software, they all lock up and do funky stuff on occasion. They are very complicated tools doing calculations that would take weeks by hand in a matter of seconds. So I'm thankful that they are at my disposal. But I can't imagine it being a issue with the type of work I do even if someone is watching. At some point in time mixing engineers messed up and began allowing clients in on the secrets. Shame on them. :-)

Mod Bod

rabeach


I mean no offence to anyone and without a doubt it is my on ignorance of working in this field but this has been gnawing at me for a while. Why do any of you allow your clients to watch you work. What is to be gained by that? I do electrical and security design work mostly for the DOD and I would never allow them to watch me work. I prepare for any and all meetings with them and ready myself to handle any and all criticism of my work in a diplomatic manner, which means with the DOD I'll do it the way you want it done. But I can't imagine allowing anyone to watch me work. Now that being said I have been put under the microscope upon rare occasions in meetings and been forced to design on the fly in front of high-ranking personnel. 

I want them to see how totally amazing I am.  

:-)

A lot of mix engineers, including Chris-Lord-Alge don't mind sharing all of their secrets, but that's because secrets are conjured by engineers that tend to be self-critical to the max. The more successful they are, they tend to be more willing to enlighten and to tell you they don't have secrets, just experience, excellent gear, and a great pair of ears. If you ask Chris how he got the kick drum so punchy on Green Day's American Idiot record, I'm sure he'd show you. The thing is, you would probably have to have his equipment, ears, and experience to know what's too much or not enough. By knowing his secrets, you're not going to take business away from him. He still gets his fill. In fact, the more you learn from him, the more likely he'll hire you to work for his studio. In fact, that's how Adam Ayan started working for Bob Ludwig. 

Many views are that one should be willing to spend a great deal of time and effort trying to solve and correct problems that shouldn't be there in the first place.

 
I guess that's one nice thing about being me - I don't spend a great deal of time and effort trying to solve and correct problems.  I just don't have all those problems waiting for me to solve and correct.
 
SONAR X2a, Win7 64 running on a Q9300  w/ 8GB RAM, and a Focusrite 18i6.   Definitely not a cutting edge system but it runs well.
 
 
 
 
PS... I also run S1 v2.5 on this system.  Latency/performance-wise I don't see much difference between the two.
 

I don't see it that many users are just complaining or trolling. I see it that there are many people that expected things to work and they don't.

True, but I don't recall seeing anyone post that they like bugs and workarounds and everybody should join them in their new found hobby of using workarounds. What I've grown weary of is posts about things that the poster can't possibly know to be true. I can't recall how many thousands of post that I have read over the past decade of posters stating that cake is going to go out of business because this or that and that they could run cakewalk better than cakewalk or cakewalk should be doing this or that. Anybody who runs a business can appreciate that often these post lack any true insight. It is funny for the first couple of years after a decade or two it wears thin. But I defend the right of these people to post such things as much as I defend my right to find them a little silly.

Greg Hendershott would probably buy it back....

SteveStrummerUK

Keni


BTW...
 
Happy (belated) Birthday Steve... Did you actually just celebrate 51?
 
Don't worry... I doubt you'll catch up to me too fast as I'm more than 10 years farther gone! ;-)
 
Keni
 

 
LOL - cheers Keni
 
And yeah, 51 it is!
 
Although I find acting like a petulant teenager helps me to feel a lot younger
 
 
 

Congrats Steve! I hope the little kid NEVER grows up! I myself suffer from a well known disease called "Peter Panitis"... I WON'T grow up! ;-)
 
Keni
 

What was this thread about?  Ohh...
 

Still I have found "bugs" /problems still no one seem to care to fix them at Cakewalk? Cakewalk use to be fast on sending out update not slooooooooooowwwwwww as today. I really like that. Also they use to add new things, listing on the customers. I will soon leave this boat if this pattern continue.

 
78% of all 'bugs' are simply the result of ignorant users who have failed to read the instructions.
10% of 'bugs' are the result of the end user having a different idea of how a feature should have been implemented than the software designer specified in the functional specifications.
7% of 'bugs' are the result of improperly applied configuration or interaction with third party components that do not match the API specifications.
5% of 'bugs' are actually software nor performing as designed.
 
This forum is a great place to help users in handling 95% of these things that are somehow considered to be 'bugs' by users who don't know any better than to call them that.  Look, unless someone else can reproduce what someone thinks is a 'bug' it probably isn't.  If someone else can't make it happen it is probably something that YOU are doing wrong - not Cakewalk.
 
X2a works wonderfully and without trouble for me.  So far, I have only been able to reproduce two 'bugs' that users have reported on this forum, and I did it just to see if things were really as buggy as the flaming trolls insist that it is.  I'm perfectly happy with how things are now in X2a and see no real need for an X2b release (possibly a small patch sometime).  I'm actually looking forward to what new features will be released in X3 or whatever they call the next major release has in store for us.
 
Glen

I really hope that the next version, X2b or X3 etc,doesnt end up on the steam cloud like music creater 6....lol

78% of all 'bugs' are simply the result of ignorant users who have failed to read the instructions. 10% of 'bugs' are the result of the end user having a different idea of how a feature should have been implemented than the software designer specified in the functional specifications. 7% of 'bugs' are the result of improperly applied configuration or interaction with third party components that do not match the API specifications. 5% of 'bugs' are actually software nor performing as designed.

Probably damn near the true numbers there Glen.


I notice that quite a few people cry 'BUG' the second something, anything goes wrong.
Bugs usually are something that can be replicated by more than one user.


When someone post's a 'recipe' so to speak and most people can reproduce the issue I then consider that a bug.


Mike