...wicked


Ohhhhh, that's a very clever idea! 

You could then save the screenset with all the EQs you want up at once, which kind of takes the best of an actual console and the best of a digital UI. 

Indeed. Screensets will remember hiddin/ shown tracks. And you can have the TV and CV show/ hide tracks together or separately. Having them hide tracks seperately would be ideal in this scenario since you would probably still want to see all the tracks in the TV while you work on a few EQs on the other monitor in the CV.

SP

skullsession

 
I'd love to love...

But Beagle just loves to dance!



All this talk of the on/off bug has ruined my week. How can really be sure it's not happening inside my projects?

Sven

ProjectM

SvenArne

skullsession


I'd love to love...

But Beagle just loves to dance!



All this talk of the on/off bug has ruined my week. How can really be sure it's not happening inside my projects?

Sven

Well, you should be able to hear it. If not, then it probably doesn't matter

^^^^ This!!!

I don't swear on forums - only face to face!

Indeed. Screensets will remember hiddin/ shown tracks. And you can have the TV and CV show/ hide tracks together or separately. Having them hide tracks seperately would be ideal in this scenario since you would probably still want to see all the tracks in the TV while you work on a few EQs on the other monitor in the CV.

 
I think Screensets is one of the best new features of X1. 
 
Again, so if you don't like PC and don't want to use it on your projects, you can simply close the PC window and save it as a Screenset; then it will never be in your way.

MakeShift

Indeed. Screensets will remember hiddin/ shown tracks. And you can have the TV and CV show/ hide tracks together or separately. Having them hide tracks seperately would be ideal in this scenario since you would probably still want to see all the tracks in the TV while you work on a few EQs on the other monitor in the CV.

 
I think Screensets is one of the best new features of X1. 
 
Again, so if you don't like PC and don't want to use it on your projects, you can simply close the PC window and save it as a Screenset; then it will never be in your way.

But then the screensets are in my way. Screensets are intrusive. Why did they have shove screensets into my Sonar (are the screensets on a hidden bus too)? You'll never please me so please stop trying.

All the worst,
Grouch

ProjectM


That's the only way to swear;)

I just never figured out what "^^^^" symbols do, that's why I asked. I might be slow with this, but I have to learn it somewhere

It simply means "referring to the ABOVE post"

Need more screens per screenset?

Bristol_Jonesey

ProjectM


That's the only way to swear;)

I just never figured out what "^^^^" symbols do, that's why I asked. I might be slow with this, but I have to learn it somewhere

It simply means "referring to the ABOVE post"

Got it. Thanks;)

Maybe this will remedy the screen width problems :)

Native Display Resolution:
1366 x 398


I'm guessing you can use that screen to see the bottom, top, or middle of 5 instances of PC.


Pixels is pixels.



I'm cheap... so I like to use them wisely.





:-)

HA ha! I didn't look at the resolution. That's actually not very impressive. Probably why it's marketed for digital signage aplications

ba_midi

FastBikerBoy


I've been reading this thread for the entertainment value. I haven't seen the prochannel on/off bug as yet but if it's a "problem" that takes half witted amateurs such as myself a long time to notice it's not much of a problem really, is it?

I prefer it embedded mainly for speed when switching from track to track. If it was to be VST'd in the effects bin opening and adjusting will be far more time consuming.

But that's the kind of thinking that keeps companies (CW in this case) from fixing some bugs.   It's not that they don't exist -- it's that some people never run into them based on how they use the software.    But it serves no one to disavow their existence when there's enough evidence that more than one user has run into the bug(s).

Also - as for having the PC there for 'speed', well, that is one argument to be made (I'm in the camp that doesn't want the PC inline), but one could also use BUSSING with one instance in the simplest case.   Takes about 2 clicks ;)

And nice to see you Karl


Nice to see you too Billy.

I'm not saying that the bug shouldn't be fixed, of course it should but like many (not all) of the bugs I have yet to see it. I was being a bit dry and insinuating that I might be experiencing it but not noticing because I'm not 'experienced' enough, as has been suggested by some. I'd like to think that even cloth ears like mine might notice when a compressor/EQ is active on a track though.

I very rarely use exactly the same EQ, or compression settings on more than one track so the Buss idea wouldn't work for me. I really don't like the idea of having to open a VST interface every time I want to tweak a track or Buss EQ or compression setting though. Not to mention the convenience of not having to load it each time I add a new track or Buss. I know I could use templates but the fact is no one has to use it, for those that don't like it ignore it. Seems simple enough to me. I can't understand why there was no objection to the Sonitus EQ being embedded but when it is replaced with something that is arguably better it's a problem for some. ** Once the bug that some experience is fixed of course, but the bug is a slightly different issue than an embedded compressor/EQ that works correctly.

ProjectM

trimph1


Need more screens per screenset?

Maybe this will remedy the screen width problems;)

I could see something like that being used for it...problem is with the resolution...wonder if it could be tweaked a bit....

FastBikerBoy

ba_midi

FastBikerBoy


I've been reading this thread for the entertainment value. I haven't seen the prochannel on/off bug as yet but if it's a "problem" that takes half witted amateurs such as myself a long time to notice it's not much of a problem really, is it?

I prefer it embedded mainly for speed when switching from track to track. If it was to be VST'd in the effects bin opening and adjusting will be far more time consuming.

But that's the kind of thinking that keeps companies (CW in this case) from fixing some bugs.   It's not that they don't exist -- it's that some people never run into them based on how they use the software.    But it serves no one to disavow their existence when there's enough evidence that more than one user has run into the bug(s).

Also - as for having the PC there for 'speed', well, that is one argument to be made (I'm in the camp that doesn't want the PC inline), but one could also use BUSSING with one instance in the simplest case.   Takes about 2 clicks ;)

And nice to see you Karl

Nice to see you too Billy.

I'm not saying that the bug shouldn't be fixed, of course it should but like many (not all) of the bugs I have yet to see it. I was being a bit dry and insinuating that I might be experiencing it but not noticing because I'm not 'experienced' enough, as has been suggested by some. I'd like to think that even cloth ears like mine might notice when a compressor/EQ is active on a track though.

I very rarely use exactly the same EQ, or compression settings on more than one track so the Buss idea wouldn't work for me. I really don't like the idea of having to open a VST interface every time I want to tweak a track or Buss EQ or compression setting though. Not to mention the convenience of not having to load it each time I add a new track or Buss. I know I could use templates but the fact is no one has to use it, for those that don't like it ignore it. Seems simple enough to me. I can't understand why there was no objection to the Sonitus EQ being embedded but when it is replaced with something that is arguably better it's a problem for some. ** Once the bug that some experience is fixed of course, but the bug is a slightly different issue than an embedded compressor/EQ that works correctly.

The Pro Channel is on a bus. Its very own bus.

All I am pointing out is that I ought to be able to delete stuff off that bus.


That way... if you really like using ProChannel on that bus... do it!!!!!! and enjoy!!!!!!

And, if you don't want ProChannel on that bus... delete it.

It's like getting a free bus that is already there.




Remember a few versions back when the other hidden bus suddenly added gain to your track?

That is not the bus I'm speaking of... I am speaking of the bus that ProChannel is on.

If you are using ProChannel, you are already using that bus.

I think I am too...


very best,
mike

mike_mccue

The Pro Channel is on a bus. Its very own bus.

All I am pointing out is that I ought to be able to delete stuff off that bus.

That way... if you really like using ProChannel on that bus... do it!!!!!! and enjoy!!!!!!

And, if you don't want ProChannel on that bus... delete it.

It's like getting a free bus that is already there.

Remember a few versions back when the other hidden bus suddenly added gain to your track?

That is not the bus I'm speaking of... I am speaking of the bus that ProChannel is on.

If you are using ProChannel, you are already using that bus.

I think I am too...

very best,
mike

Yesterday Brandon suggested I could try to delete the .dll's for the Pro Channel.

I found 4 .dll's. A bus, comp, eq, and sat .dll all in the 'C:\Program Files\Cakewalk\Shared Utilities\Internal' folder. I didn't delete them, but I made a backup folder and moved them.

I started a new project 44.1/32, so far 4 full length audio tracks (iow not 10 second clips), and Session Drummer 3. I haven't had a single glitch except for the tool bar disappearing, which is a pita, but is easily fixed by min/max X1.

The whole bus thing didn't make sense to me until I saw there is a PCS-BusCM.dll. I would think there would have to be a separate bus every time one of the modules of the PC is used. If it was on a single bus, it would just be an FX send and effect all the tracks. So if I'm thinking correctly on this, there is potentially 3 virtual buses per track being created if you use the PC Comp/EQ/Sat. They would have to do it this way rather than tie it to the FX Bin because if you would bypass the FX Bin the PC would also be bypassed.

Another thing I noticed, when I moved the .dll's, the PC graphics still showed up and I could adjust all the knobs and turn all the modules on and off. I would get an error saying the VST didn't load, but appearance wise, everything was still working normally. Which means that the interface and graphics are not part of the .dll's. Therefor the PC modules turning on/off by themselves could have nothing to do with the actual VST .dll's for it. Also, I should get a pop up with an error now when they turn on/off by themselves.

For those of you having troubles with the PC ... it can be disabled but in a roundabout way. Just go to 'C:\Program Files\Cakewalk\Shared Utilities\Internal' and make another sub folder and move the 4 PC .dll's there.

Hope this helps.

Bub