Thanks ProjectM... you are a true gentleman, a valued acquaintance, and a thoughtful and challenging debater!!!

all the very best,
mike

as with some of the Lexicon hardware, the ability to use a hardware EQ or Compressor as a plugin within the host. Imagine the sweetness of that? I first saw this when looking at the Lexicon reverb units and it struck me as a brilliant idea. I really had forgotten all about it until just now... how in hell do they pull that off? Anybody tried one?

They didn't pull it off. I have a hardware PCM96 and it only worked intermittently in OSX 10.5 and got completely broken in OSX 10.6. It never had an integrated plugin in Windows. They do have their System Architect software that lets you remote control just about any Harman hardware that does run on Windows/OSX but it isn't DAW integrated.  Sorry for the OT bit...

Regarding Pro Channel: It has a fatal flaw for how I work. In the track view (I never use the console view), its UI is displayed according to which track you have selected.  No other plugin UI in Sonar behaves that way. So if I'm adjusting the ProChannel on one track and I accidentally select another track (happens a lot to me), then the PC's UI is now being displayed for that other track. I have to think about what just happened--why did my PC change?  It's a stutter in working with it. It isn't a workflow improvement.

Essentially for that reason, I don't use the PC. It's whole user interaction and experience is not conducive to how I work.

Are you saying that should be changed?

All I'm saying is what I said.  I didn't say anything about track inspector, I didn't say anything about midi, I didn't say anything about changing anything, I know that's how it's s'posed to be.

So I'll just repeat: the PC's UI integration doesn't work for me. If others like it, or can use it without error, then that's great. I find it error prone.  It's an effect whose UI doesn't behave like any other effects in Sonar.  Sure, there are others, like VVocal, but it's not nearly as much of a disconnect to use VV than PC. Again, IMO.  And just because I didn't mention time/pitch stretch, don't infer that I think it should be changed to a binnable effect.

I don't have trouble with MIDI tracks. They behave consistently. The track inspector behaves consistently. What doesn't behave consistently is the PC in that it's a VST effect that doesn't behave like the other VST effects. I don't have to select a track in order to enable any open plugin windows of non-PC effects on that track.  And it causes me to have to think harder about it when I use it. I have deadlines and anything that slows me down will be unused unless it is necessary.  The PC is not necessary, it's sound affecting features are amply covered by other plugins.

For what I do, the PC is a slowdown. If others like it then hooray! I just felt like offering up my experience so that cakewalk can take it and file it away in the appropriate basement.

Karyn


Steve,  I'm not trying to have a go at you or anything.  It's just that you singled out a "problem" in your workflow as being a "problem" with PC.

So I'll just repeat: the PC's UI integration doesn't work for me. If others like it, or can use it without error, then that's great. I find it error prone.

Saying it twice doesn't alter the fact that there is anything wrong with the PC's UI intergration,  even for you.   If you were adjusting the pan, or vol fader, or a send level and "accidentaly clicked another track" then those would change as well...
I'm simply saying you're singling out as a problem using PC when all the rest of Track Inspector  works the same way and always has.

The same sort of thing would happen if you had 2 identical VSTs open - unless you are very careful or know exactly where you've put the window, you could easily edit the wrong one.  When you potentially have multiple VSTs for each track (if you replace the PC), I'm quite happy to have the PC in a consistent location and not a mass of overlapping VST windows to navigate.

James_S

Karyn


Steve,  I'm not trying to have a go at you or anything.  It's just that you singled out a "problem" in your workflow as being a "problem" with PC.

So I'll just repeat: the PC's UI integration doesn't work for me. If others like it, or can use it without error, then that's great. I find it error prone.

Saying it twice doesn't alter the fact that there is anything wrong with the PC's UI intergration,  even for you.   If you were adjusting the pan, or vol fader, or a send level and "accidentaly clicked another track" then those would change as well...
I'm simply saying you're singling out as a problem using PC when all the rest of Track Inspector  works the same way and always has.

The same sort of thing would happen if you had 2 identical VSTs open - unless you are very careful or know exactly where you've put the window, you could easily edit the wrong one.  When you potentially have multiple VSTs for each track (if you replace the PC), I'm quite happy to have the PC in a consistent location and not a mass of overlapping VST windows to navigate.

I have to agree 100% with this

You know you don't have to look at this thread...

it's not like anyone is asking you to involuntarily run a buggy thread in the background of your SONAR project.

Forum rubberneckin.  It hurts so good!

ampfixer


I want the ability to delete this thread. I know I don't have to look at it, but knowing it's on the system at all times and may be malfunctioning drives me crazy. I constantly have to check on it to see what it's doing and how it's affecting my S/N ratio. It's definitely adding distortion to my perception.

Mother, get out the Gordon's!

Thanks for the Laugh!

Bub


Ok ... I've been gone for a few hours ... what did I miss?

Pro channel has bugs...lol

spanky

Bub

Green Day? Honestly? LOL!

I take it you've offered something better than they have? Lol!

Depends on who you ask.

Now get off my lawn sonny!

Candyman Candyman Candyman.

Oh wait ... wrong chant.

There's no place like off, there's no place like off, there's no place like off.

SCorey

It's an effect whose UI doesn't behave like any other effects in Sonar.

+1.

Is PX64 GUI built-in? What about LP64? Perfect Space?

And what if they did implement all of Cake's plugins into X1 GUI? Would everyone be pleased then?

n0rd

SCorey

It's an effect whose UI doesn't behave like any other effects in Sonar.

+1.

Is PX64 GUI built-in? What about LP64? Perfect Space?

And what if they did implement all of Cake's plugins into X1 GUI? Would everyone be pleased then?

By virtue of that logic then the Sonitus EQ in Producer from SONAR 3-8.5 should have bothered folks too. It's an effect that doesn't behave like a plugin either.

You could extend the argument and say that a panner is the same thing. Why not use a panning plugin and an EQ plugin on every channel? I mean you don't really need pan (or EQ) on every track. Why not just add it when you need it?

Bub

Brandon Ryan [Cakewalk]

n0rd

SCorey

It's an effect whose UI doesn't behave like any other effects in Sonar.

+1.

Is PX64 GUI built-in? What about LP64? Perfect Space?

And what if they did implement all of Cake's plugins into X1 GUI? Would everyone be pleased then?

By virtue of that logic then the Sonitus EQ in Producer from SONAR 3-8.5 should have bothered folks too. It's an effect that doesn't behave like a plugin either.

You could extend the argument and say that a panner is the same thing. Why not use a panning plugin and an EQ plugin on every channel? I mean you don't really need pan (or EQ) on every track. Why not just add it when you need it?

Ahhh ... I was wondering who was going to be the first one to bring up Sonitus EQ being embedded.

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.

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

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.

Gotta go, I'll check the thread tomorrow.

Bub

I reported this issue way back when....


back when I was trying to use X1.


Tilt.