yorolpal


Who?

Bapu


It's always Bapu


Unless it's Mooch.

Brandon Ryan [Cakewalk]

Is there a prize?

:)

My response to that is, Sonitus EQ never behaved the way the PC is behaving, that's why this kind of attention was never brought to it. That, and it wasn't as invasive as the PC is.

The ProChannel doesn't behave the way it does for you for most. That's a fact - although I'll admit one that does not favor or improve your situation. I've put your issue and video (thanks!) to support and it's currently being researched against known/existing bugs. I don't have any information yet. All I can say from my own experience is that I've never seen that happen for whatever reason.

It has happened to others here on completely different configurations than mine, it just happens I was lucky enough to catch it and document it before I rectified it. Once you turn on Saturation, the problem goes away. I should have sent the project in before I did that but I was caught up in the moment of documenting my find. :( The video I sent is just one of 4 bugs I have found with the Pro Channel that have been there since day 1.

I don't know in which way the PC is "invasive".

It's invasive due to the fact that myself and others are having technical problems with it and we can't remove it like we would any other VST. It's pretty much rendered X1 unusable.

Isn't there a way to make it so PC can be disabled? It's only available in the Producer edition so there must be some way to do it relatively easily I would think?

You might be able to remove the .dll, but it seems a pity.

I disagree. Everyone should have the ability to remove it just for cases like this, just like they would with any other VST, which is the whole point of the discussion in this thread. It's about options.

Pro Channel is a VST ... and Cakewalk's track record on VST's isn't stellar. Session Drummer 3 got broke when X1 was released, Sonitus Delay was still buggy, VX64 still has problems with the controls disappearing, PX64 is unresponsive in some circumstances in X1. I can honestly say the only plug-in's from Cakewalk that have never displayed some sort of problem are the Sonitus Compressor and EQ, and I'm talking over a span of 10 + years and 4 different DAW's. So can you see why some of us are a little shell shocked over the Pro Channel being embedded?

Thanks for the tip on the .DLL. I didn't even think to look for it, I just assumed it was hidden somewhere since it was embedded. I'll give it a shot and see what happens.

Thanks for responding,

Bub

John T

I don't disagree. However, it is still true of several of the other bundled effects. Vintage Channel and Boost 11 off the top of my head, and I know there are more.

So since it's been done before makes it ok?

This is a non-reply. Let me rephrase. You have no idea how long it took to implement.

I don't work for Cake so *of course* I don't have the exact figures. But there is this concept of estimation through experience is there not?

How a third party VST qualifies as a feature of Sonar is not something I understand.

Ah John, you're slipping... The whole point of this thread is that PC has it's GUI embedded into Sonar and not it's own as per a normal VST.

If you had any idea, you wouldn't be using words like "most likely" and "theoretically". If we're concerned about not being silly, let's not waste time with this.

If you do something ten times and it takes on average 10 minutes each time... The eleventh time would take how long? Hmm?

Indeed, it would. But I'm personally not terribly inclined to sit here worrying about stuff that's not yet happening and there's no indication of it happening in the future. It would suck if the keyboard I'm typing at suddenly exploded too.

Hahahaha... oh John!

Irrelevant? Makes development & testing *so* much easier when you're not coupled to another app in development.

Now this is just plain nuts. If you're not testing something in the way it is to be used, you aren't testing it.
Imagine the uproar if a plug in had a bug, and Brandon came on said "well, it worked okay in Ableton, we thought it'd be fine".

John, I don't think you understand. It has nothing to do testing on another App (Ableton?! What the?). The whole point is that Sonar and a VST (lets say PC64) become two separate items instead on one embedded into the other. (You know, the whole point of this thread... Embedded GUI? Ring a bell?)


But that's exactly the reason why I'm done here...

Too many times in this thread people have had to move it off-topic to get their point across without the realization that by doing so, their point is... well... pointless. (Ableton? Exploding keyboards? Hahaha... funny).

Good day.

I have been following this thread from day one.  I guess I am missing something.  If you don't like PC, can't you just turn it off, close the PC window and save this as one of your screen sets.  Now every time  you open up a new project to that screen set, it appears as your old track view.  If PC is off and hidden, I have never had it just turn itself on and open the window on its own.

I thought one of the real beauties of the new screen sets is that you can set up your work flow to look how ever you want it to look.  I have screen sets customized with the PC window opened and others with it closed.  

Since X1B, I have only had one instance where I thought....maybe....that the PC disengaged and turned a blue light off on the compressor.  It could have just as easily been my fault, "user error".  Not to say that others may have issues with this, but I could not be absolutely certain that it did it on its own.

MakeShift


I have been following this thread from day one.  I guess I am missing something.  If you don't like PC, can't you just turn it off, close the PC window and save this as one of your screen sets.  Now every time  you open up a new project to that screen set, it appears as your old track view.  If PC is off and hidden, I have never had it just turn itself on and open the window on its own.

I thought one of the real beauties of the new screen sets is that you can set up your work flow to look how ever you want it to look.  I have screen sets customized with the PC window opened and others with it closed.  

Since X1B, I have only had one instance where I thought....maybe....that the PC disengaged and turned a blue light off on the compressor.  It could have just as easily been my fault, "user error".  Not to say that others may have issues with this, but I could not be absolutely certain that it did it on its own.

I don't mind having the PC in general, but I do wish there was an option NOT to have it.

One of the problems with it for some (including me) have run into is when using the Inspector it takes an extra click / gesture to get off the PC tab if that's where you last left things.   So in that one regard, it's a tiny bit annoying.

I wouldn't mind a "hide" function for the tab.

Beagle

mike_mccue


One of the points I have been trying to make is that most of the people who have stood up and explained that they finally realized that ProChannel was switching on and off WERE happy ProChannel users saying positive things about what they heard.

It took many of the satisfied and happy users a few months or even more to find the time to observe and figure out there was a problem. 

I'm sorry Mike, but that's simply not true for everyone.  I don't know the difference in your system and mine or Bub's system and mine, but I have been using PC extensively in the last few projects I've been working on and liking it more and more as I use it.  since this thread started I've been scrutenizing PC to make sure each instance on each track is behaving the way it should.  i.e. the ones that I've been using are staying ON and the settings have not arbitrarily changed, and also checking the ones I haven't used to make sure they stay OFF.  I also have been verifying that the ones I am using are actually doing their job (and not doing what is happening to Bub where it's not actually affecting the track signal at all until he touches the tube saturation).  I've even been using PC both with and without the tube saturation and have seen no problems at all.
 
so to say that "(most of the people)...finally realized that ProChannel was switching on and off..." is quite an exaggeration, IMO.  It does apparently apply to some people - but let's not say that "most people" are not smart enough to realize if they are having problems with it or not, which is what it seems to me that you're elluding to.
 
Also, I am not saying that you and Bub and others are not having the problems that you're describing.  I'm simply saying that there are some of us who do NOT have these problems and you seem to be lumping all of us in the same boat without statistics to back up your claim.

Hi Beagle,

I believe that if you had quoted my sentences in their entirety

"One of the points I have been trying to make is that most of the people who have stood up and explained that they finally realized that ProChannel was switching on and off WERE happy ProChannel users saying positive things about what they heard."

"It took many of the satisfied and happy users a few months or even more to find the time to observe and figure out there was a problem."

That you could have had an opportunity to review them and see that the intention is to convey the idea that most of the people that say they see the problem in ProChannel actually like(d) ProChannel.

I may be the only guy that has observed the problem that also didn't want it wedged into SONAR merely in the abstract. I get the impression the other people reporting the problem actually like ProChannel.






Perhaps you are contending my claim that no one, even if they look carefully, can observe all the circumstances at once?





all the very best,
mike





edited some spelling

mike_mccue

Beagle

mike_mccue


One of the points I have been trying to make is that most of the people who have stood up and explained that they finally realized that ProChannel was switching on and off WERE happy ProChannel users saying positive things about what they heard.

It took many of the satisfied and happy users a few months or even more to find the time to observe and figure out there was a problem. 

I'm sorry Mike, but that's simply not true for everyone.  I don't know the difference in your system and mine or Bub's system and mine, but I have been using PC extensively in the last few projects I've been working on and liking it more and more as I use it.  since this thread started I've been scrutenizing PC to make sure each instance on each track is behaving the way it should.  i.e. the ones that I've been using are staying ON and the settings have not arbitrarily changed, and also checking the ones I haven't used to make sure they stay OFF.  I also have been verifying that the ones I am using are actually doing their job (and not doing what is happening to Bub where it's not actually affecting the track signal at all until he touches the tube saturation).  I've even been using PC both with and without the tube saturation and have seen no problems at all.

so to say that "(most of the people)...finally realized that ProChannel was switching on and off..." is quite an exaggeration, IMO.  It does apparently apply to some people - but let's not say that "most people" are not smart enough to realize if they are having problems with it or not, which is what it seems to me that you're elluding to.

Also, I am not saying that you and Bub and others are not having the problems that you're describing.  I'm simply saying that there are some of us who do NOT have these problems and you seem to be lumping all of us in the same boat without statistics to back up your claim.

Hi Beagle,

I believe that if you had quoted my sentences in their entirety

"One of the points I have been trying to make is that most of the people who have stood up and explained that they finally realized that ProChannel was switching on and off WERE happy ProChannel users saying positive things about what they heard."

"It took many of the satisfied and happy users a few months or even more to find the time to observe and figure out there was a problem."

That you could have had an opportunity to review them and see that the intention is to convey the idea that most of the people that say they see the problem in ProChannel actually like(d) ProChannel.

I may be the only guy that has observed the problem that also didn't want it wedged into SONAR merely in the abstract. I get the impression the other people reporting the problem actually like ProChannel.






Perhaps you are contending my claim that no one, even if they look carefully, can observe all the circumstances at once?





all the very best,
mike





edited some spelling

sorry Mike - even re-reading the whole quote I still didn't gleen that from what you said - sorry to misunderstand!

Beagle
James (skull) - I just realized that yes, even tho the module will float, you can't have multiple instances of the GUI open since you have to choose which track you're looking at, so your example of having sonitus float so that you can carve out EQ space for different instruments would not be possible with PC since you can't float "track A's PC" to look at the EQ on it while you're working on EQ for "track B's PC"

Reece....
 
Correct me if I'm wrong, but I specifically used the mixer view for accessing the ProChannel.  Because that's the way my work flows....
 
I don't recall being able to float the ProChannel interface there.  I seem to recall that it is LOCKED to the channel it corresponds to.  I opens to the side of the channel, and collapses back into the channel.  You CAN have multiple instances of it open there, but they're all locked to the corresponding tracks.  And of course, by the time you open two or three of them up, they're so large that half of your screen is ate up....and god forbid there are several channels between the two or three you're fooling with, you're forever scrolling back and forth trying to see what's what.  Clunky.
 
I'd love to love it....but I don't.

So join us next week when our guests will be; Dennis Cole, Tovah Feldshuh, Sherman Hemsley, Lawanda Page, John Ritter and Jaclyn Smith on The Love Boat ...er the X1 Forum!!
 
http://www.youtube.com/watch?v=ZmUlKPthrag
 

mike_mccue



You know what Beagle,

I have reread your post... and although I don't think you choose to quote the most effective statement to illustrate your opinion I now understand what you were saying to me.

I think I was preoccupied with the way you used that particular quote.

I just want to be honest with you. You are a friend.

I have indeed been implying that I don't think many people are aware of what PC is or isn't doing. I think that's what you are saying you think I am saying.. so yes, I agree with you on that.

I'd rather be frank with you and simply disagree than to seem evasive.

I'm in good company though... some of the guys that admit to have been fooled are as serious about their work as I imagine you are about yours. It's good to think that you are experiencing good use of ProChannel.

All the best,
mike

no worries my friend!
 
I do feel bad that some of you are having problems with it and I wish I could help figure out what the differences are between what I'm seeing and what you guys are experiencing.  I just don't know why it works on my system and not yours.

skullsession

Beagle

skullsession


Oh...and HI MIKE!

Nice dick measuring contest you got going here...LOL.  I've tried to stay off your thread, but it looks like Reece accidentally answered me on this thread for something I said on a different one.

It's all good.

I did?  oops!
 
yeah, james, you can float the module (from the TRACK VIEW), but as I remembered later and thought I had corrected, you can't open MULTIPLES of it, which is what I think you are wanting to do when you said you can't use it to carve out EQ space between tracks.  and I agree with you now that I realize what you meant.
 
you CAN float the module - but you can't open multiple instances of PC to show what's on 2 or more tracks at the same time like you can with sonitus.

Either way, it's a strange and very slow way of dealing with multiple tracks quickly.

I don't disagree with that!  I would like to be able to float multiple instances for the reason you're describing.

Seth Perlstein [Cakewalk
]

You can open multiple instances of the ProChannel in the Console View.

SP

And you can float them?

No...the question is...and more of a suggestion is...

It would be nice if you could unteather the ProChannel from the actual channel on the mixer view...drag it around, move it to another screen....and when you close it, it goes back home.  Just like every other VST does.

I can't be the onlyone that this is killing on work flow.  Seriously.

Sometimes it's nice to have three/four/five different eq's (or whatever) up on the same monitor, side by side, while you tweak.

Near impossible to do with ProChannel if say you want to work on ProChannel:  Track 1, Track 13, and Track 27.  Not gonna be on the same screen...without scrolling all over hell to do it.

Your embedded EQ on the tracks allows you to open up multiple EQ's from different tracks and drag them anywhere on any screen.  Not sure why this wouldn't make sense for the ProChannel as well.

They ought to get all you guys together for a steel cage death match. My money is on Bub... he looks like he could whup any of you guys. The winner gets the final say on the ProChannel.