Pro Channel - It finally happened to me

Bub

We have jackets, what size do you wear? You also get a nice patch to sew on your jeans and a bracelet.

yorolpal

Is this like what was happening to Strammy (Steve Strummer) or what was happening to you, Bub?  Or like what was happening to you, Mike?

mike_mccue

I suspect this family of issues will be tough for Cakewalk to troubleshoot because it seems to happen so ephemerally.

yorolpal


Is this like what was happening to Strammy (Steve Strummer) or what was happening to you, Bub?  Or like what was happening to you, Mike?

codamedia

In the link below, it would appear the problem was solved. But since the claim was that this only happened on 64 bit machines, that theory goes all to hell - or it's a new problem. I'm 32 bit here!

Ryan Munnis [Cakewalk]

Maybe if they used the software at home, they may run in to it.

I do use it at home. I also use it 45 hours a week while in the office. I also instruct students on how to use Logic Pro, Pro Tools, Digital Performer, Ableton Live, Garage Band, Reason, Record and a plethora of plug-ins and other music based applications at my second job three days a week, every week. I've also worked hands on with a blind-user trying to learn SONAR who truly tested my knowledge as I tried to explain things to him without visual feedback. My story is just a drop in the bucket for the talent pool of musicians that I work with every day, and I don't consider myself personally very talented.

I'm not sure why the hostility. It's very difficult to read sarcasm on the forums so I'm not sure if you're being sincere or not. ;)

I keep reading that people think I swept your particular issue under the rug of sorts, but that's actually not the case at all. We confirmed, reproduced, reported, and are actually working to address the bug you experienced with the project you uploaded in X1c. I took the time to explain the issue. I've fought harder for your case then you probably will ever know. I'm sure I aggravated a lot of people. And though we are thankful you reported this, we actually already had discovered it before your assistance... so yes we're using the software.

I'm not trying to argue with anyone here, but we're asked to research these issues and I feel like many of our customers are still being misinformed by the community and are unaware of how much work we've done internally to directly acknowledge, research, and resolve questions and concerns in regards to ProChannel. My post count is drastically lower then many users on the forum, so I know my attempts to help often get buried.

If anyone wants to suggest that we're unwilling to research these issues, I welcome you to review my post with the open invitation to send me a private message me with issues related to this.

Bottom line is that the only issues I'm aware of out in the field right now are:

-- an issue where ProChannel will auto-enable if automation snapshots or envelopes are assigned to one of it's parameters (see Noel's post)
-- an installation related issue where ProChannel will not process audio if the VST Scanner did not scan it properly (easily corrected with the info below)

Bub

Ryan Munnis [Cakewalk]

Maybe if they used the software at home, they may run in to it.

I do use it at home. I also use it 45 hours a week while in the office. I also instruct students on how to use Logic Pro, Pro Tools, Digital Performer, Ableton Live, Garage Band, Reason, Record and a plethora of plug-ins and other music based applications at my second job three days a week, every week. I've also worked hands on with a blind-user trying to learn SONAR who truly tested my knowledge as I tried to explain things to him without visual feedback. My story is just a drop in the bucket for the talent pool of musicians that I work with every day, and I don't consider myself personally very talented.

I'm not sure why the hostility. It's very difficult to read sarcasm on the forums so I'm not sure if you're being sincere or not. ;)

Well, I was sincere. What I failed to get across was the difference between testing in a controlled environment and testing at home. I assumed people would understand that but apparently I was wrong.

I keep reading that people think I swept your particular issue under the rug of sorts, but that's actually not the case at all. We confirmed, reproduced, reported, and are actually working to address the bug you experienced with the project you uploaded in X1c. I took the time to explain the issue. I've fought harder for your case then you probably will ever know. I'm sure I aggravated a lot of people. And though we are thankful you reported this, we actually already had discovered it before your assistance... so yes we're using the software.

I've said it before and I'll say it again, perception trumps reality. It may not be fair, but that's how life is. It happens to me a lot more than it does to you here if that makes you feel any better.

I'm not trying to argue with anyone here, but we're asked to research these issues and I feel like many of our customers are still being misinformed by the community and are unaware of how much work we've done internally to directly acknowledge, research, and resolve questions and concerns in regards to ProChannel. My post count is drastically lower then many users on the forum, so I know my attempts to help often get buried.

You kind of lumped two issues in with that statement. Let me stop you at "I feel like many of our customers are still being misinformed by the community ..." That's the kind of statement that gets you in trouble with the perception trumps reality thing. Do you have any idea how many hours some of us spend troubleshooting this software and coming here on your forums trying to get it resolved and help others? We don't get paid. We don't get comped. We just get told we're misinforming people. That's where the "... people think I swept your particular issue under the rug of sorts ..." comes from.

If anyone wants to suggest that we're unwilling to research these issues, I welcome you to review my post with the open invitation to send me a private message me with issues related to this.

EDITED FOR CLARITY Actually, I've been told repeatedly that you are the developers is are in fact unwilling to research issues if I cannot present you them with a replicable problem.

Bottom line is that the only issues I'm aware of out in the field right now are:

-- an issue where ProChannel will auto-enable if automation snapshots or envelopes are assigned to one of it's parameters (see Noel's post)
-- an installation related issue where ProChannel will not process audio if the VST Scanner did not scan it properly (easily corrected with the info below)

Ryan ... listen/look very closely at the following statement I have put in dark blue and set in bold ... I have seen the ProChannel randomly turn 'on' and turn 'off' in a project that has never had an envelope in it starting in X1 (Initial release), X1a, X1b, X1b all builds up to 255, in x86 and x64, in projects started in 8.5, and in new projects started in each of the aforementioned patches and builds of X1.

It's really funny that you single me out here when there are seven other people here who participated that said, yeah, we are seeing the Pro Channel do weird things too. This is where that perception trumps reality thing comes in to play again.

I really do appreciate you taking the time to chime in. I'm really looking forward to X1C and have the utmost faith that it will resolve this weird Pro Channel issue. It has to ... before you guys can move on to X2. This isn't something you can let go when it's affecting so many people.

I hope you don't take anything I've said negatively, I'm just trying to clarify where I stand and sometimes I get long winded and it actually makes things worse. Then I go to the extreme and don't say enough to explain myself (which is what prompted your post in the first place).

Thanks.

Sincerely,

Bub

Oh, by the way ... my PM box is open, it's never been locked. My email address is in my profile too.