Larry Burger wrote:I am close to sorry I started this thread. . . . . .
I usually find the forum helpful and just was looking for an answer if anyone had used Console 1 or might have a reason why it did not respond the way I had hoped.
I have used C1 in a Live Situation via other DAW's (I know they are not made for that and SAC is).
I used SAW Studio live before Bob designed SAC. . . .
I did not plan on just tweaking everything all the time.
If you have reached up and changed an eq on a channel to make it sound better, that is what I would do with Console 1 inside SAC.
But it would not work.
I assume some will use a different Reverb plugin inside SAC even though Bob has his own (which will give remote control).
That's is all I was trying to do since Console one is a VST plugin. . . . .
I don't want to start disputes just looking for help...
Thank you for the ideas and opinions. . . .
Larry...
Larry,
don't be sorry, and nobody is in a dispute.
in order to be helpful we need to know more information than you supplied.
Even if somebody else had tried C1 you didn't provide enough information about what didn't work so there would be no way to assess if they had the same problem or not.
What your describing about controlling EQ on a channel via C1 is not what is usually implied when talking about VST plugins as there is already a fully functional channel strip with gates, compressors, EQ etc.
Please don't read that as meaning your approach wouldn't work or be useful, but it does mean circumventing the core audio engine in order to have a control surface to tweak knobs.
As you've already determined in order to deal with the latency issue you also have to run the console at higher bit rates which means using a lot more of your CPU resources as well as more hardware to make that happen. Many interfaces will limit channel counts when you increase the clock rate.
So as a general approach C1 is going to be pretty inefficient.
I'm not making these statements to say don't do it, you just need to understand what the technical implications and limits are if your going to try to go down that path.
If the desire is to have a fully control surfaced mixing environment then SAW/SAC are not really going to be good solutions for that as they weren't designed with that goal in mind. (and force inserting another console strip into every channel is kind of defeating the whole purpose of SAW/SAC)
SAW/SAC do make very good hybrid solutions and both have good support for basic functionality most people are generally looking for.
Faders, solos, mutes, pans, record enable, transport controls.
If at some point in the future Bob releases an API for SAW/SAC then that would open the door for more customized solutions that could include control of the Gates, Compressor, EQ, phantom power, hardware channel gain, etc
There of coarse may be other work in the pipeline with Bobs more recent hardware alliance and maybe some of these types of issues will be alternatively addressed through that path instead.
[quote="Larry Burger"]I am close to sorry I started this thread. . . . . .
I usually find the forum helpful and just was looking for an answer if anyone had used Console 1 or might have a reason why it did not respond the way I had hoped.
I have used C1 in a Live Situation via other DAW's (I know they are not made for that and SAC is).
I used SAW Studio live before Bob designed SAC. . . .
I did not plan on just tweaking everything all the time.
If you have reached up and changed an eq on a channel to make it sound better, that is what I would do with Console 1 inside SAC.
But it would not work.
I assume some will use a different Reverb plugin inside SAC even though Bob has his own (which will give remote control).
That's is all I was trying to do since Console one is a VST plugin. . . . .
I don't want to start disputes just looking for help...
Thank you for the ideas and opinions. . . .
Larry...[/QUOTE]
Larry,
don't be sorry, and nobody is in a dispute.
in order to be helpful we need to know more information than you supplied.
Even if somebody else had tried C1 you didn't provide enough information about what didn't work so there would be no way to assess if they had the same problem or not.
What your describing about controlling EQ on a channel via C1 is not what is usually implied when talking about VST plugins as there is already a fully functional channel strip with gates, compressors, EQ etc.
Please don't read that as meaning your approach wouldn't work or be useful, but it does mean circumventing the core audio engine in order to have a control surface to tweak knobs.
As you've already determined in order to deal with the latency issue you also have to run the console at higher bit rates which means using a lot more of your CPU resources as well as more hardware to make that happen. Many interfaces will limit channel counts when you increase the clock rate.
So as a general approach C1 is going to be pretty inefficient.
I'm not making these statements to say don't do it, you just need to understand what the technical implications and limits are if your going to try to go down that path.
If the desire is to have a fully control surfaced mixing environment then SAW/SAC are not really going to be good solutions for that as they weren't designed with that goal in mind. (and force inserting another console strip into every channel is kind of defeating the whole purpose of SAW/SAC)
SAW/SAC do make very good hybrid solutions and both have good support for basic functionality most people are generally looking for.
Faders, solos, mutes, pans, record enable, transport controls.
If at some point in the future Bob releases an API for SAW/SAC then that would open the door for more customized solutions that could include control of the Gates, Compressor, EQ, phantom power, hardware channel gain, etc
There of coarse may be other work in the pipeline with Bobs more recent hardware alliance and maybe some of these types of issues will be alternatively addressed through that path instead.