Home » The PARIS Forums » PARIS: Main » Arrrgggghhhh!!!!!!!!!!! CUBASE 4 MUST DIE!!!!!!!!
|
|
| Re: Arrrgggghhhh!!!!!!!!!!! CUBASE 4 MUST DIE!!!!!!!! [message #87912 is a reply to message #87905] |
Tue, 10 July 2007 22:09   |
Neil
Messages: 1645
Registered: April 2006
|
Senior Member |
|
|
May I suggest something?
OK, I'm using my system as an example here since you & I have
different convertor sets, but follow for a moment & maybe this
will help if you apply similar principals to your setup...
I have two Multifaces... let's say I have various
inputs on Multiface #1 assigned to INPUTS as follows in
the "VST Connections" dialogue:
Multiface ch1 = Mono Input/Kick
MF Ch 2 = Mono Input/Snare
MF Ch 3 = Mono Input/Hat
MF Ch 4 = Mono Input/Cowbell & digital cowbell sample triggers
MF Ch's 5&6 = Stereo Input/OH's
MF Ch's 7&8 = Stereo Input/Drum Room-Ambience Mics
MF Ch's 9&10 = (SPDIF/Not used in this scenario)
MF Ch's 11 to 14 = ADAT (Lightpipe) inputs used for 4 tom mics.
.... and the only OUTputs you have assigned are:
MF Ch's 1&2 (OUTPUTS) = main monitors
OK, so that wipes out ALL the inputs except for SPDIF in the
first Multiface, yes? All the other inputs would have to be
routed through the 2nd Multiface in this scenario... here's the
thing... when you get to mixdown & external EFX routing, let's
say you want your VST connections to look like this on your
first (Master!!!) Multiface - i.e the same one as above:
MF Ch's 1&2 OUTPUTS = main monitors (no change there)
MF Ch 3 OUTPUT = send to external EFX/Distressor on vox track
MF Ch 3 INPUT = return from external EFX/Distressor on vox track
MF Ch 4 OUTPUT = send to external EFX/Massenburg EQ on kik
MF Ch 4 INPUT = return from external EFX/Massenburg EQ on kik
MF Ch's 5&6 OUTPUTS = send to external Lexi 480L, Engine "A"
MF Ch's 5&6 INPUTS = return from external Lexi 480L, Engine "A"
MF Ch's 7&8 OUTPUTS = send to external Lexi 480L, Engine "B"
MF Ch's 7&8 INPUTS = return from external Lexi 480L, Engine "B"
MF CH's 9&10 OUTPUTS = SPDIF to Quantec Yardstick IN's/Sends
MF CH's 9&10 INPUTS = SPDIF to Quantec Yardstick OUTS/Returns
<lightpipes not used in mixdown in this example>
Quite a bit different routing scenario than the one you used for
tracking, yes? I suspect what's happening is that you're not
saving your VST connections routing - if that's the case, every
time you open up a project it'll take you to the last "saved"
version, including any routing changes you've made & saved,
but NOT any routing changes you've made, but not saved!
You can save these routing/patching changes in one of two ways:
1.) set up all your routing for your patching & external EFX,
and make sure you save the project again once you do that
(either under a new project name or just overwrite what you've
got... I tend to save under a new name in case I fuck anything
up - or simply hate what I've done - and need to go back :) )
2.) Save your routing scenarios in the "VST Connections"
dialogue... there's an option that let's you save those...
you could go from:
"ScreamingOkapis-SongOfWorldPeace-BasicTrackRouting", to...
"ScreamingOkapis-SongOfWorldPeace-OverdubRoutingA", to...
"ScreamingOkapis-SongOfWorldPeace-VocalOverdubs", to...
"ScreamingOkapis-SongOfWorldPeace-MixdownRoutingA", to...
"ScreamingOkapis-SongOfWorldPeace-MixdownRoutingB"
Now, it's true I have SX3 and you have C4, but I would bet it's
the same basic idea. Got it? Kewl?
Let us know if that works for you.
Neil
"DJ" <animix _ at _ animas _ dot _ net> wrote:
>Every time I close a project and then reopen it, various patches to my
>external gear are disabled.....especially prevalent on the inputs, but not
>always, and sometimes the outputs are reassigned to different ones. I never
>know what I'm going to be faces with when I recall a project. Sometimes
it
>takes me 10-15 minutes just hunt everything down to repatch.
>
>This really sucks........and I mean to the point that I'm about to kick
this
>damn thing out the window. Does Nuendo do this too? I need to be able to
>save a project with AD/DA's assigned to external processors and be able
to
>recall it.......CONSISTENTLY!!!. This **FUCKING POS** is about to PISS ME
>OFF!!!!!
>
>
|
|
|
|
| Re: Arrrgggghhhh!!!!!!!!!!! CUBASE 4 MUST DIE!!!!!!!! [message #87918 is a reply to message #87912] |
Tue, 10 July 2007 22:27 |
DJ
Messages: 1124
Registered: July 2005
|
Senior Member |
|
|
Hmmmm........the I/O busses can be saved, but the external FX are constant
from project to project so that sorta' doesn't make sense to me, but then
again it might.......sorta.......maybe............I guess. I'm fried tonight
so I've shut it down.
BTW......there's a Neve Portico tape emulator on Gearslutz for $1200.00
right now (or at least there was last night). You need this.
;o)
"Neil" <OIUOIU@.com> wrote in message news:4694660a$1@linux...
>
> May I suggest something?
>
> OK, I'm using my system as an example here since you & I have
> different convertor sets, but follow for a moment & maybe this
> will help if you apply similar principals to your setup...
>
> I have two Multifaces... let's say I have various
> inputs on Multiface #1 assigned to INPUTS as follows in
> the "VST Connections" dialogue:
>
> Multiface ch1 = Mono Input/Kick
> MF Ch 2 = Mono Input/Snare
> MF Ch 3 = Mono Input/Hat
> MF Ch 4 = Mono Input/Cowbell & digital cowbell sample triggers
> MF Ch's 5&6 = Stereo Input/OH's
> MF Ch's 7&8 = Stereo Input/Drum Room-Ambience Mics
> MF Ch's 9&10 = (SPDIF/Not used in this scenario)
> MF Ch's 11 to 14 = ADAT (Lightpipe) inputs used for 4 tom mics.
>
> ... and the only OUTputs you have assigned are:
> MF Ch's 1&2 (OUTPUTS) = main monitors
>
> OK, so that wipes out ALL the inputs except for SPDIF in the
> first Multiface, yes? All the other inputs would have to be
> routed through the 2nd Multiface in this scenario... here's the
> thing... when you get to mixdown & external EFX routing, let's
> say you want your VST connections to look like this on your
> first (Master!!!) Multiface - i.e the same one as above:
>
> MF Ch's 1&2 OUTPUTS = main monitors (no change there)
> MF Ch 3 OUTPUT = send to external EFX/Distressor on vox track
> MF Ch 3 INPUT = return from external EFX/Distressor on vox track
> MF Ch 4 OUTPUT = send to external EFX/Massenburg EQ on kik
> MF Ch 4 INPUT = return from external EFX/Massenburg EQ on kik
> MF Ch's 5&6 OUTPUTS = send to external Lexi 480L, Engine "A"
> MF Ch's 5&6 INPUTS = return from external Lexi 480L, Engine "A"
> MF Ch's 7&8 OUTPUTS = send to external Lexi 480L, Engine "B"
> MF Ch's 7&8 INPUTS = return from external Lexi 480L, Engine "B"
> MF CH's 9&10 OUTPUTS = SPDIF to Quantec Yardstick IN's/Sends
> MF CH's 9&10 INPUTS = SPDIF to Quantec Yardstick OUTS/Returns
> <lightpipes not used in mixdown in this example>
>
> Quite a bit different routing scenario than the one you used for
> tracking, yes? I suspect what's happening is that you're not
> saving your VST connections routing - if that's the case, every
> time you open up a project it'll take you to the last "saved"
> version, including any routing changes you've made & saved,
> but NOT any routing changes you've made, but not saved!
>
> You can save these routing/patching changes in one of two ways:
>
> 1.) set up all your routing for your patching & external EFX,
> and make sure you save the project again once you do that
> (either under a new project name or just overwrite what you've
> got... I tend to save under a new name in case I fuck anything
> up - or simply hate what I've done - and need to go back :) )
>
> 2.) Save your routing scenarios in the "VST Connections"
> dialogue... there's an option that let's you save those...
> you could go from:
> "ScreamingOkapis-SongOfWorldPeace-BasicTrackRouting", to...
> "ScreamingOkapis-SongOfWorldPeace-OverdubRoutingA", to...
> "ScreamingOkapis-SongOfWorldPeace-VocalOverdubs", to...
> "ScreamingOkapis-SongOfWorldPeace-MixdownRoutingA", to...
> "ScreamingOkapis-SongOfWorldPeace-MixdownRoutingB"
>
> Now, it's true I have SX3 and you have C4, but I would bet it's
> the same basic idea. Got it? Kewl?
>
> Let us know if that works for you.
>
> Neil
>
>
>
>
>
>
>
>
>
>
>
>
>
> "DJ" <animix _ at _ animas _ dot _ net> wrote:
>>Every time I close a project and then reopen it, various patches to my
>>external gear are disabled.....especially prevalent on the inputs, but not
>
>>always, and sometimes the outputs are reassigned to different ones. I
>>never
>
>>know what I'm going to be faces with when I recall a project. Sometimes
> it
>>takes me 10-15 minutes just hunt everything down to repatch.
>>
>>This really sucks........and I mean to the point that I'm about to kick
> this
>>damn thing out the window. Does Nuendo do this too? I need to be able to
>
>>save a project with AD/DA's assigned to external processors and be able
> to
>>recall it.......CONSISTENTLY!!!. This **FUCKING POS** is about to PISS ME
>
>>OFF!!!!!
>>
>>
>
|
|
|
|
| Re: Arrrgggghhhh!!!!!!!!!!! CUBASE 4 MUST DIE!!!!!!!! [message #87919 is a reply to message #87912] |
Tue, 10 July 2007 22:29 |
Dedric Terry
Messages: 788
Registered: June 2007
|
Senior Member |
|
|
DJ - I would bet this is what is happening as well. I/O assignments are
global, not on a per project basis.
In N3 this is the only reason I end up with re-routed I/O - the reason being
that your default or last project may have a different setup and in order to
accommodate regular I/O assignments, external gear is taken offline Saving
your I/O assignments, including CR setup can be a lifesaver, assuming this
is the problem you are seeing.
Do note that the two (VST I/O and the control room config) are separate and
you need to save both, even though they will impact one another when
allocating I/O (if you use the Control Room at least - it is *not* saved
with the I/O presets at the moment, though I think it should).
This is also one feature I would ask for in N4/C4.x - I/O and Control Rooms
settings saved with each project, in addition to retaining global preset
list/default setting option.
Hope that solves the problem DJ - I know rerouting is massively frustrating.
Regards,
Dedric
On 7/10/07 11:09 PM, in article 4694660a$1@linux, "Neil" <OIUOIU@.com>
wrote:
>
> May I suggest something?
>
> OK, I'm using my system as an example here since you & I have
> different convertor sets, but follow for a moment & maybe this
> will help if you apply similar principals to your setup...
>
> I have two Multifaces... let's say I have various
> inputs on Multiface #1 assigned to INPUTS as follows in
> the "VST Connections" dialogue:
>
> Multiface ch1 = Mono Input/Kick
> MF Ch 2 = Mono Input/Snare
> MF Ch 3 = Mono Input/Hat
> MF Ch 4 = Mono Input/Cowbell & digital cowbell sample triggers
> MF Ch's 5&6 = Stereo Input/OH's
> MF Ch's 7&8 = Stereo Input/Drum Room-Ambience Mics
> MF Ch's 9&10 = (SPDIF/Not used in this scenario)
> MF Ch's 11 to 14 = ADAT (Lightpipe) inputs used for 4 tom mics.
>
> ... and the only OUTputs you have assigned are:
> MF Ch's 1&2 (OUTPUTS) = main monitors
>
> OK, so that wipes out ALL the inputs except for SPDIF in the
> first Multiface, yes? All the other inputs would have to be
> routed through the 2nd Multiface in this scenario... here's the
> thing... when you get to mixdown & external EFX routing, let's
> say you want your VST connections to look like this on your
> first (Master!!!) Multiface - i.e the same one as above:
>
> MF Ch's 1&2 OUTPUTS = main monitors (no change there)
> MF Ch 3 OUTPUT = send to external EFX/Distressor on vox track
> MF Ch 3 INPUT = return from external EFX/Distressor on vox track
> MF Ch 4 OUTPUT = send to external EFX/Massenburg EQ on kik
> MF Ch 4 INPUT = return from external EFX/Massenburg EQ on kik
> MF Ch's 5&6 OUTPUTS = send to external Lexi 480L, Engine "A"
> MF Ch's 5&6 INPUTS = return from external Lexi 480L, Engine "A"
> MF Ch's 7&8 OUTPUTS = send to external Lexi 480L, Engine "B"
> MF Ch's 7&8 INPUTS = return from external Lexi 480L, Engine "B"
> MF CH's 9&10 OUTPUTS = SPDIF to Quantec Yardstick IN's/Sends
> MF CH's 9&10 INPUTS = SPDIF to Quantec Yardstick OUTS/Returns
> <lightpipes not used in mixdown in this example>
>
> Quite a bit different routing scenario than the one you used for
> tracking, yes? I suspect what's happening is that you're not
> saving your VST connections routing - if that's the case, every
> time you open up a project it'll take you to the last "saved"
> version, including any routing changes you've made & saved,
> but NOT any routing changes you've made, but not saved!
>
> You can save these routing/patching changes in one of two ways:
>
> 1.) set up all your routing for your patching & external EFX,
> and make sure you save the project again once you do that
> (either under a new project name or just overwrite what you've
> got... I tend to save under a new name in case I fuck anything
> up - or simply hate what I've done - and need to go back :) )
>
> 2.) Save your routing scenarios in the "VST Connections"
> dialogue... there's an option that let's you save those...
> you could go from:
> "ScreamingOkapis-SongOfWorldPeace-BasicTrackRouting", to...
> "ScreamingOkapis-SongOfWorldPeace-OverdubRoutingA", to...
> "ScreamingOkapis-SongOfWorldPeace-VocalOverdubs", to...
> "ScreamingOkapis-SongOfWorldPeace-MixdownRoutingA", to...
> "ScreamingOkapis-SongOfWorldPeace-MixdownRoutingB"
>
> Now, it's true I have SX3 and you have C4, but I would bet it's
> the same basic idea. Got it? Kewl?
>
> Let us know if that works for you.
>
> Neil
>
>
>
>
>
>
>
>
>
>
>
>
>
> "DJ" <animix _ at _ animas _ dot _ net> wrote:
>> Every time I close a project and then reopen it, various patches to my
>> external gear are disabled.....especially prevalent on the inputs, but not
>
>> always, and sometimes the outputs are reassigned to different ones. I never
>
>> know what I'm going to be faces with when I recall a project. Sometimes
> it
>> takes me 10-15 minutes just hunt everything down to repatch.
>>
>> This really sucks........and I mean to the point that I'm about to kick
> this
>> damn thing out the window. Does Nuendo do this too? I need to be able to
>
>> save a project with AD/DA's assigned to external processors and be able
> to
>> recall it.......CONSISTENTLY!!!. This **FUCKING POS** is about to PISS ME
>
>> OFF!!!!!
>>
>>
>
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Arrrgggghhhh!!!!!!!!!!! CUBASE 4 MUST DIE!!!!!!!! [message #87935 is a reply to message #87912] |
Wed, 11 July 2007 07:25 |
DJ
Messages: 1124
Registered: July 2005
|
Senior Member |
|
|
Ok Neil,
I have reread your post.
> 1.) set up all your routing for your patching & external EFX,
> and make sure you save the project again once you do that
> (either under a new project name or just overwrite what you've
> got... I tend to save under a new name in case I fuck anything
> up - or simply hate what I've done - and need to go back :) )
I have done this. Doesn't make any difference........probably
because........
> 2.) Save your routing scenarios in the "VST Connections"
> dialogue... there's an option that let's you save those...
> you could go from:
> "ScreamingOkapis-SongOfWorldPeace-BasicTrackRouting", to...
> "ScreamingOkapis-SongOfWorldPeace-OverdubRoutingA", to...
> "ScreamingOkapis-SongOfWorldPeace-VocalOverdubs", to...
> "ScreamingOkapis-SongOfWorldPeace-MixdownRoutingA", to...
> "ScreamingOkapis-SongOfWorldPeace-MixdownRoutingB"
I have not done this, but I will try it. I think herein may lie the
(Germaincally screwballishly logical) answer.
;o)
"Neil" <OIUOIU@.com> wrote in message news:4694660a$1@linux...
>
> May I suggest something?
>
> OK, I'm using my system as an example here since you & I have
> different convertor sets, but follow for a moment & maybe this
> will help if you apply similar principals to your setup...
>
> I have two Multifaces... let's say I have various
> inputs on Multiface #1 assigned to INPUTS as follows in
> the "VST Connections" dialogue:
>
> Multiface ch1 = Mono Input/Kick
> MF Ch 2 = Mono Input/Snare
> MF Ch 3 = Mono Input/Hat
> MF Ch 4 = Mono Input/Cowbell & digital cowbell sample triggers
> MF Ch's 5&6 = Stereo Input/OH's
> MF Ch's 7&8 = Stereo Input/Drum Room-Ambience Mics
> MF Ch's 9&10 = (SPDIF/Not used in this scenario)
> MF Ch's 11 to 14 = ADAT (Lightpipe) inputs used for 4 tom mics.
>
> ... and the only OUTputs you have assigned are:
> MF Ch's 1&2 (OUTPUTS) = main monitors
>
> OK, so that wipes out ALL the inputs except for SPDIF in the
> first Multiface, yes? All the other inputs would have to be
> routed through the 2nd Multiface in this scenario... here's the
> thing... when you get to mixdown & external EFX routing, let's
> say you want your VST connections to look like this on your
> first (Master!!!) Multiface - i.e the same one as above:
>
> MF Ch's 1&2 OUTPUTS = main monitors (no change there)
> MF Ch 3 OUTPUT = send to external EFX/Distressor on vox track
> MF Ch 3 INPUT = return from external EFX/Distressor on vox track
> MF Ch 4 OUTPUT = send to external EFX/Massenburg EQ on kik
> MF Ch 4 INPUT = return from external EFX/Massenburg EQ on kik
> MF Ch's 5&6 OUTPUTS = send to external Lexi 480L, Engine "A"
> MF Ch's 5&6 INPUTS = return from external Lexi 480L, Engine "A"
> MF Ch's 7&8 OUTPUTS = send to external Lexi 480L, Engine "B"
> MF Ch's 7&8 INPUTS = return from external Lexi 480L, Engine "B"
> MF CH's 9&10 OUTPUTS = SPDIF to Quantec Yardstick IN's/Sends
> MF CH's 9&10 INPUTS = SPDIF to Quantec Yardstick OUTS/Returns
> <lightpipes not used in mixdown in this example>
>
> Quite a bit different routing scenario than the one you used for
> tracking, yes? I suspect what's happening is that you're not
> saving your VST connections routing - if that's the case, every
> time you open up a project it'll take you to the last "saved"
> version, including any routing changes you've made & saved,
> but NOT any routing changes you've made, but not saved!
>
> You can save these routing/patching changes in one of two ways:
>
> 1.) set up all your routing for your patching & external EFX,
> and make sure you save the project again once you do that
> (either under a new project name or just overwrite what you've
> got... I tend to save under a new name in case I fuck anything
> up - or simply hate what I've done - and need to go back :) )
>
> 2.) Save your routing scenarios in the "VST Connections"
> dialogue... there's an option that let's you save those...
> you could go from:
> "ScreamingOkapis-SongOfWorldPeace-BasicTrackRouting", to...
> "ScreamingOkapis-SongOfWorldPeace-OverdubRoutingA", to...
> "ScreamingOkapis-SongOfWorldPeace-VocalOverdubs", to...
> "ScreamingOkapis-SongOfWorldPeace-MixdownRoutingA", to...
> "ScreamingOkapis-SongOfWorldPeace-MixdownRoutingB"
>
> Now, it's true I have SX3 and you have C4, but I would bet it's
> the same basic idea. Got it? Kewl?
>
> Let us know if that works for you.
>
> Neil
>
>
>
>
>
>
>
>
>
>
>
>
>
> "DJ" <animix _ at _ animas _ dot _ net> wrote:
>>Every time I close a project and then reopen it, various patches to my
>>external gear are disabled.....especially prevalent on the inputs, but not
>
>>always, and sometimes the outputs are reassigned to different ones. I
>>never
>
>>know what I'm going to be faces with when I recall a project. Sometimes
> it
>>takes me 10-15 minutes just hunt everything down to repatch.
>>
>>This really sucks........and I mean to the point that I'm about to kick
> this
>>damn thing out the window. Does Nuendo do this too? I need to be able to
>
>>save a project with AD/DA's assigned to external processors and be able
> to
>>recall it.......CONSISTENTLY!!!. This **FUCKING POS** is about to PISS ME
>
>>OFF!!!!!
>>
>>
>
|
|
|
|
|
|
|
|
|
|
| Re: Arrrgggghhhh!!!!!!!!!!! CUBASE 4 MUST DIE!!!!!!!! [message #88066 is a reply to message #87919] |
Fri, 13 July 2007 23:08 |
audioguy_editout_
Messages: 249
Registered: December 2005
|
Senior Member |
|
|
My I/O routing is saved with N3.... I don't get this. If I
open different project files, I have different I/O set-ups
in each.
David.
Dedric Terry wrote:
> DJ - I would bet this is what is happening as well. I/O assignments are
> global, not on a per project basis.
>
> In N3 this is the only reason I end up with re-routed I/O - the reason being
> that your default or last project may have a different setup and in order to
> accommodate regular I/O assignments, external gear is taken offline Saving
> your I/O assignments, including CR setup can be a lifesaver, assuming this
> is the problem you are seeing.
>
> Do note that the two (VST I/O and the control room config) are separate and
> you need to save both, even though they will impact one another when
> allocating I/O (if you use the Control Room at least - it is *not* saved
> with the I/O presets at the moment, though I think it should).
>
> This is also one feature I would ask for in N4/C4.x - I/O and Control Rooms
> settings saved with each project, in addition to retaining global preset
> list/default setting option.
>
> Hope that solves the problem DJ - I know rerouting is massively frustrating.
>
> Regards,
> Dedric
>
> On 7/10/07 11:09 PM, in article 4694660a$1@linux, "Neil" <OIUOIU@.com>
> wrote:
>
>
>>May I suggest something?
>>
>>OK, I'm using my system as an example here since you & I have
>>different convertor sets, but follow for a moment & maybe this
>>will help if you apply similar principals to your setup...
>>
>>I have two Multifaces... let's say I have various
>>inputs on Multiface #1 assigned to INPUTS as follows in
>>the "VST Connections" dialogue:
>>
>>Multiface ch1 = Mono Input/Kick
>>MF Ch 2 = Mono Input/Snare
>>MF Ch 3 = Mono Input/Hat
>>MF Ch 4 = Mono Input/Cowbell & digital cowbell sample triggers
>>MF Ch's 5&6 = Stereo Input/OH's
>>MF Ch's 7&8 = Stereo Input/Drum Room-Ambience Mics
>>MF Ch's 9&10 = (SPDIF/Not used in this scenario)
>>MF Ch's 11 to 14 = ADAT (Lightpipe) inputs used for 4 tom mics.
>>
>>... and the only OUTputs you have assigned are:
>>MF Ch's 1&2 (OUTPUTS) = main monitors
>>
>>OK, so that wipes out ALL the inputs except for SPDIF in the
>>first Multiface, yes? All the other inputs would have to be
>>routed through the 2nd Multiface in this scenario... here's the
>>thing... when you get to mixdown & external EFX routing, let's
>>say you want your VST connections to look like this on your
>>first (Master!!!) Multiface - i.e the same one as above:
>>
>>MF Ch's 1&2 OUTPUTS = main monitors (no change there)
>>MF Ch 3 OUTPUT = send to external EFX/Distressor on vox track
>>MF Ch 3 INPUT = return from external EFX/Distressor on vox track
>>MF Ch 4 OUTPUT = send to external EFX/Massenburg EQ on kik
>>MF Ch 4 INPUT = return from external EFX/Massenburg EQ on kik
>>MF Ch's 5&6 OUTPUTS = send to external Lexi 480L, Engine "A"
>>MF Ch's 5&6 INPUTS = return from external Lexi 480L, Engine "A"
>>MF Ch's 7&8 OUTPUTS = send to external Lexi 480L, Engine "B"
>>MF Ch's 7&8 INPUTS = return from external Lexi 480L, Engine "B"
>>MF CH's 9&10 OUTPUTS = SPDIF to Quantec Yardstick IN's/Sends
>>MF CH's 9&10 INPUTS = SPDIF to Quantec Yardstick OUTS/Returns
>><lightpipes not used in mixdown in this example>
>>
>>Quite a bit different routing scenario than the one you used for
>>tracking, yes? I suspect what's happening is that you're not
>>saving your VST connections routing - if that's the case, every
>>time you open up a project it'll take you to the last "saved"
>>version, including any routing changes you've made & saved,
>>but NOT any routing changes you've made, but not saved!
>>
>>You can save these routing/patching changes in one of two ways:
>>
>>1.) set up all your routing for your patching & external EFX,
>>and make sure you save the project again once you do that
>>(either under a new project name or just overwrite what you've
>>got... I tend to save under a new name in case I fuck anything
>>up - or simply hate what I've done - and need to go back :) )
>>
>>2.) Save your routing scenarios in the "VST Connections"
>>dialogue... there's an option that let's you save those...
>>you could go from:
>>"ScreamingOkapis-SongOfWorldPeace-BasicTrackRouting", to...
>>"ScreamingOkapis-SongOfWorldPeace-OverdubRoutingA", to...
>>"ScreamingOkapis-SongOfWorldPeace-VocalOverdubs", to...
>>"ScreamingOkapis-SongOfWorldPeace-MixdownRoutingA", to...
>>"ScreamingOkapis-SongOfWorldPeace-MixdownRoutingB"
>>
>>Now, it's true I have SX3 and you have C4, but I would bet it's
>>the same basic idea. Got it? Kewl?
>>
>>Let us know if that works for you.
>>
>>Neil
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>"DJ" <animix _ at _ animas _ dot _ net> wrote:
>>
>>>Every time I close a project and then reopen it, various patches to my
>>>external gear are disabled.....especially prevalent on the inputs, but not
>>
>>>always, and sometimes the outputs are reassigned to different ones. I never
>>
>>>know what I'm going to be faces with when I recall a project. Sometimes
>>
>>it
>>
>>>takes me 10-15 minutes just hunt everything down to repatch.
>>>
>>>This really sucks........and I mean to the point that I'm about to kick
>>
>>this
>>
>>>damn thing out the window. Does Nuendo do this too? I need to be able to
>>
>>>save a project with AD/DA's assigned to external processors and be able
>>
>>to
>>
>>>recall it.......CONSISTENTLY!!!. This **FUCKING POS** is about to PISS ME
>>
>>>OFF!!!!!
>>>
>>>
>>
>
|
|
|
|
| Re: Arrrgggghhhh!!!!!!!!!!! CUBASE 4 MUST DIE!!!!!!!! [message #88071 is a reply to message #88066] |
Sat, 14 July 2007 07:00 |
DJ
Messages: 1124
Registered: July 2005
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0359_01C7C5ED.0AC879A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I called Steinberg USA. They called Germany. I got the following in an =
e-mail:
Maybe the 2x audio cards are cascaded differently each time on booting =
up the machine? This would explain how the busses are set wrong in =
Cubase as a result of the changed hardware order. Maybe a driver issue =
or control panel setup question here.
Check with RME to be sure that you have the latest driver, and also see =
if there is anything they can recommend to stop the cards from altering =
their boot order. I hope this information helps, let me know if there =
is anything else I can do.
Nice theory, but wrong. I have the lateas drivers and all of these cards =
midi I/O are patched into a big midi patchbay and quite a bit of the =
digital I/O is patched into a Frontier Apache. If the cards were =
initializing differently each time, then the patchbay assignments would =
get scrambled. These patches remain consistent. the only thing that =
doesn't remain consistent is Cubase 4.=20
As I said before, Cubase 4 must DIE!!!!
"Dave(EK Sound)" <audioguy_editout_@shaw.ca> wrote in message =
news:469869c6$1@linux...
> My I/O routing is saved with N3.... I don't get this. If I=20
> open different project files, I have different I/O set-ups=20
> in each.
>=20
> David.
>=20
> Dedric Terry wrote:
>> DJ - I would bet this is what is happening as well. I/O assignments =
are
>> global, not on a per project basis.
>>=20
>> In N3 this is the only reason I end up with re-routed I/O - the =
reason being
>> that your default or last project may have a different setup and in =
order to
>> accommodate regular I/O assignments, external gear is taken offline =
Saving
>> your I/O assignments, including CR setup can be a lifesaver, assuming =
this
>> is the problem you are seeing.
>>=20
>> Do note that the two (VST I/O and the control room config) are =
separate and
>> you need to save both, even though they will impact one another when
>> allocating I/O (if you use the Control Room at least - it is *not* =
saved
>> with the I/O presets at the moment, though I think it should).
>>=20
>> This is also one feature I would ask for in N4/C4.x - I/O and Control =
Rooms
>> settings saved with each project, in addition to retaining global =
preset
>> list/default setting option.
>>=20
>> Hope that solves the problem DJ - I know rerouting is massively =
frustrating.
>>=20
>> Regards,
>> Dedric
>>=20
>> On 7/10/07 11:09 PM, in article 4694660a$1@linux, "Neil" =
<OIUOIU@.com>
>> wrote:
>>=20
>>=20
>>>May I suggest something?
>>>
>>>OK, I'm using my system as an example here since you & I have
>>>different convertor sets, but follow for a moment & maybe this
>>>will help if you apply similar principals to your setup...
>>>
>>>I have two Multifaces... let's say I have various
>>>inputs on Multiface #1 assigned to INPUTS as follows in
>>>the "VST Connections" dialogue:
>>>
>>>Multiface ch1 =3D Mono Input/Kick
>>>MF Ch 2 =3D Mono Input/Snare
>>>MF Ch 3 =3D Mono Input/Hat
>>>MF Ch 4 =3D Mono Input/Cowbell & digital cowbell sample triggers
>>>MF Ch's 5&6 =3D Stereo Input/OH's
>>>MF Ch's 7&8 =3D Stereo Input/Drum Room-Ambience Mics
>>>MF Ch's 9&10 =3D (SPDIF/Not used in this scenario)
>>>MF Ch's 11 to 14 =3D ADAT (Lightpipe) inputs used for 4 tom mics.
>>>
>>>... and the only OUTputs you have assigned are:
>>>MF Ch's 1&2 (OUTPUTS) =3D main monitors
>>>
>>>OK, so that wipes out ALL the inputs except for SPDIF in the
>>>first Multiface, yes? All the other inputs would have to be
>>>routed through the 2nd Multiface in this scenario... here's the
>>>thing... when you get to mixdown & external EFX routing, let's
>>>say you want your VST connections to look like this on your
>>>first (Master!!!) Multiface - i.e the same one as above:
>>>
>>>MF Ch's 1&2 OUTPUTS =3D main monitors (no change there)
>>>MF Ch 3 OUTPUT =3D send to external EFX/Distressor on vox track
>>>MF Ch 3 INPUT =3D return from external EFX/Distressor on vox track
>>>MF Ch 4 OUTPUT =3D send to external EFX/Massenburg EQ on kik
>>>MF Ch 4 INPUT =3D return from external EFX/Massenburg EQ on kik
>>>MF Ch's 5&6 OUTPUTS =3D send to external Lexi 480L, Engine "A"
>>>MF Ch's 5&6 INPUTS =3D return from external Lexi 480L, Engine "A"
>>>MF Ch's 7&8 OUTPUTS =3D send to external Lexi 480L, Engine "B"
>>>MF Ch's 7&8 INPUTS =3D return from external Lexi 480L, Engine "B"
>>>MF CH's 9&10 OUTPUTS =3D SPDIF to Quantec Yardstick IN's/Sends
>>>MF CH's 9&10 INPUTS =3D SPDIF to Quantec Yardstick OUTS/Returns
>>><lightpipes not used in mixdown in this example>
>>>
>>>Quite a bit different routing scenario than the one you used for
>>>tracking, yes? I suspect what's happening is that you're not
>>>saving your VST connections routing - if that's the case, every
>>>time you open up a project it'll take you to the last "saved"
>>>version, including any routing changes you've made & saved,
>>>but NOT any routing changes you've made, but not saved!
>>>
>>>You can save these routing/patching changes in one of two ways:
>>>
>>>1.) set up all your routing for your patching & external EFX,
>>>and make sure you save the project again once you do that
>>>(either under a new project name or just overwrite what you've
>>>got... I tend to save under a new name in case I fuck anything
>>>up - or simply hate what I've done - and need to go back :) )
>>>
>>>2.) Save your routing scenarios in the "VST Connections"
>>>dialogue... there's an option that let's you save those...
>>>you could go from:
>>>"ScreamingOkapis-SongOfWorldPeace-BasicTrackRouting", to...
>>>"ScreamingOkapis-SongOfWorldPeace-OverdubRoutingA", to...
>>>"ScreamingOkapis-SongOfWorldPeace-VocalOverdubs", to...
>>>"ScreamingOkapis-SongOfWorldPeace-MixdownRoutingA", to...
>>>"ScreamingOkapis-SongOfWorldPeace-MixdownRoutingB"
>>>
>>>Now, it's true I have SX3 and you have C4, but I would bet it's
>>>the same basic idea. Got it? Kewl?
>>>
>>>Let us know if that works for you.
>>>
>>>Neil
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>"DJ" <animix _ at _ animas _ dot _ net> wrote:
>>>
>>>>Every time I close a project and then reopen it, various patches to =
my
>>>>external gear are disabled.....especially prevalent on the inputs, =
but not
>>>
>>>>always, and sometimes the outputs are reassigned to different ones. =
I never
>>>
>>>>know what I'm going to be faces with when I recall a project. =
Sometimes
>>>
>>>it=20
>>>
>>>>takes me 10-15 minutes just hunt everything down to repatch.
>>>>
>>>>This really sucks........and I mean to the point that I'm about to =
kick
>>>
>>>this=20
>>>
>>>>damn thing out the window. Does Nuendo do this too? I need to be =
able to
>>>
>>>>save a project with AD/DA's assigned to external processors and be =
able
>>>
>>>to=20
>>>
>>>>recall it.......CONSISTENTLY!!!. This **FUCKING POS** is about to =
PISS ME
>>>
>>>>OFF!!!!!=20
>>>>
>>>>
>>>
>>
------=_NextPart_000_0359_01C7C5ED.0AC879A0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16414" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>I called Steinberg USA. They called =
Germany. I got=20
the following in an e-mail:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><EM>Maybe the 2x audio cards are =
cascaded=20
differently each time on booting up the machine? This would explain how =
the=20
busses are set wrong in Cubase as a result of the changed hardware =
order. Maybe=20
a driver issue or control panel setup question here.<BR><BR>Check with =
RME to be=20
sure that you have the latest driver, and also see if there is anything =
they can=20
recommend to stop the cards from altering their boot order. I hope =
this=20
information helps, let me know if there is anything else I can=20
do.</EM></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><EM></EM></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Nice theory, but wrong. I have the =
lateas drivers=20
and all of these cards midi I/O are patched into a big midi patchbay and =
quite a=20
bit of the digital I/O is patched into a Frontier Apache. If the cards =
were=20
initializing differently each time, then the patchbay assignments would =
get=20
scrambled. These patches remain consistent. the only thing that doesn't =
remain=20
consistent is Cubase 4. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>As I said before, Cubase 4 must=20
DIE!!!!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> </DIV>
<DIV><BR><BR></DIV></FONT>
<DIV><FONT face=3DArial size=3D2>"Dave(EK Sound)" <</FONT><A=20
href=3D"mailto:audioguy_editout_@shaw.ca"><FONT face=3DArial=20
size=3D2>audioguy_editout_@shaw.ca</FONT></A><FONT face=3DArial =
size=3D2>> wrote in=20
message </FONT><A href=3D"news:469869c6$1@linux"><FONT face=3DArial=20
size=3D2>news:469869c6$1@linux</FONT></A><FONT face=3DArial=20
size=3D2>...</FONT></DIV><FONT face=3DArial size=3D2>> My I/O routing =
is saved with=20
N3.... I don't get this. If I <BR>> open different project =
files, I=20
have different I/O set-ups <BR>> in each.<BR>> <BR>> =
David.<BR>>=20
<BR>> Dedric Terry wrote:<BR>>> DJ - I would bet this is what =
is=20
happening as well. I/O assignments are<BR>>> global, not on =
a per=20
project basis.<BR>>> <BR>>> In N3 this is the only reason I =
end up=20
with re-routed I/O - the reason being<BR>>> that your default or =
last=20
project may have a different setup and in order to<BR>>> =
accommodate=20
regular I/O assignments, external gear is taken offline =
Saving<BR>>> your=20
I/O assignments, including CR setup can be a lifesaver, assuming=20
this<BR>>> is the problem you are seeing.<BR>>> <BR>>> =
Do note=20
that the two (VST I/O and the control room config) are separate =
and<BR>>>=20
you need to save both, even though they will impact one another =
when<BR>>>=20
allocating I/O (if you use the Control Room at least - it is *not*=20
saved<BR>>> with the I/O presets at the moment, though I think it=20
should).<BR>>> <BR>>> This is also one feature I would ask =
for in=20
N4/C4.x - I/O and Control Rooms<BR>>> settings saved with each =
project, in=20
addition to retaining global preset<BR>>> list/default setting=20
option.<BR>>> <BR>>> Hope that solves the problem DJ - I =
know=20
rerouting is massively frustrating.<BR>>> <BR>>>=20
Regards,<BR>>> Dedric<BR>>> <BR>>> On 7/10/07 11:09 =
PM, in=20
article </FONT><A href=3D"mailto:4694660a$1@linux"><FONT face=3DArial=20
size=3D2>4694660a$1@linux</FONT></A><FONT face=3DArial size=3D2>, "Neil" =
<</FONT><A=20
href=3D"mailto:OIUOIU@.com"><FONT face=3DArial =
size=3D2>OIUOIU@.com</FONT></A><FONT=20
face=3DArial size=3D2>><BR>>> wrote:<BR>>> <BR>>>=20
<BR>>>>May I suggest =
something?<BR>>>><BR>>>>OK, I'm=20
using my system as an example here since you & I=20
have<BR>>>>different convertor sets, but follow for a moment =
&=20
maybe this<BR>>>>will help if you apply similar principals to =
your=20
setup...<BR>>>><BR>>>>I have two Multifaces... let's =
say I=20
have various<BR>>>>inputs on Multiface #1 assigned to INPUTS as =
follows=20
in<BR>>>>the "VST Connections"=20
dialogue:<BR>>>><BR>>>>Multiface ch1 =3D Mono=20
Input/Kick<BR>>>>MF Ch 2 =3D Mono Input/Snare<BR>>>>MF =
Ch=20
3 =3D Mono Input/Hat<BR>>>>MF Ch 4 =3D Mono Input/Cowbell =
&=20
digital cowbell sample triggers<BR>>>>MF Ch's 5&6 =3D =
Stereo=20
Input/OH's<BR>>>>MF Ch's 7&8 =3D Stereo Input/Drum =
Room-Ambience=20
Mics<BR>>>>MF Ch's 9&10 =3D (SPDIF/Not used in this=20
scenario)<BR>>>>MF Ch's 11 to 14 =3D ADAT (Lightpipe) inputs =
used for 4=20
tom mics.<BR>>>><BR>>>>... and the only OUTputs you =
have=20
assigned are:<BR>>>>MF Ch's 1&2 (OUTPUTS) =3D main=20
monitors<BR>>>><BR>>>>OK, so that wipes out ALL the =
inputs=20
except for SPDIF in the<BR>>>>first Multiface, yes? All the =
other=20
inputs would have to be<BR>>>>routed through the 2nd Multiface =
in this=20
scenario... here's the<BR>>>>thing... when you get to mixdown =
&=20
external EFX routing, let's<BR>>>>say you want your VST =
connections to=20
look like this on your<BR>>>>first (Master!!!) Multiface - i.e =
the same=20
one as above:<BR>>>><BR>>>>MF Ch's 1&2 OUTPUTS =3D =
main=20
monitors (no change there)<BR>>>>MF Ch 3 OUTPUT =3D send to =
external=20
EFX/Distressor on vox track<BR>>>>MF Ch 3 INPUT =3D return from =
external=20
EFX/Distressor on vox track<BR>>>>MF Ch 4 OUTPUT =3D send to =
external=20
EFX/Massenburg EQ on kik<BR>>>>MF Ch 4 INPUT =3D return from =
external=20
EFX/Massenburg EQ on kik<BR>>>>MF Ch's 5&6 OUTPUTS =3D send =
to=20
external Lexi 480L, Engine "A"<BR>>>>MF Ch's 5&6 INPUTS =3D =
return=20
from external Lexi 480L, Engine "A"<BR>>>>MF Ch's 7&8 =
OUTPUTS =3D=20
send to external Lexi 480L, Engine "B"<BR>>>>MF Ch's 7&8 =
INPUTS =3D=20
return from external Lexi 480L, Engine "B"<BR>>>>MF CH's =
9&10=20
OUTPUTS =3D SPDIF to Quantec Yardstick IN's/Sends<BR>>>>MF CH's =
9&10=20
INPUTS =3D SPDIF to Quantec Yardstick =
OUTS/Returns<BR>>>><lightpipes=20
not used in mixdown in this =
example><BR>>>><BR>>>>Quite a=20
bit different routing scenario than the one you used=20
for<BR>>>>tracking, yes? I suspect what's happening is that =
you're=20
not<BR>>>>saving your VST connections routing - if that's the =
case,=20
every<BR>>>>time you open up a project it'll take you to the =
last=20
"saved"<BR>>>>version, including any routing changes you've =
made &=20
saved,<BR>>>>but NOT any routing changes you've made, but not=20
saved!<BR>>>><BR>>>>You can save these =
routing/patching=20
changes in one of two ways:<BR>>>><BR>>>>1.) set up =
all your=20
routing for your patching & external EFX,<BR>>>>and make =
sure you=20
save the project again once you do that<BR>>>>(either under a =
new=20
project name or just overwrite what you've<BR>>>>got... I tend =
to save=20
under a new name in case I fuck anything<BR>>>>up - or simply =
hate what=20
I've done - and need to go back :) )<BR>>>><BR>>>>2.) =
Save=20
your routing scenarios in the "VST =
Connections"<BR>>>>dialogue... =20
there's an option that let's you save those...<BR>>>>you could =
go=20
from:<BR>>>>"ScreamingOkapis-SongOfWorldPeace-BasicTrackRouting "=
,=20
to...<BR>>>>"ScreamingOkapis-SongOfWorldPeace-OverdubRoutingA ", =
to...<BR>>>>"ScreamingOkapis-SongOfWorldPeace-VocalOverdubs ",=20
to...<BR>>>>"ScreamingOkapis-SongOfWorldPeace-MixdownRoutingA ", =
to...<BR>>>>"ScreamingOkapis-SongOfWorldPeace-MixdownRoutingB "<B=
R>>>><BR>>>>Now,=20
it's true I have SX3 and you have C4, but I would bet =
it's<BR>>>>the=20
same basic idea. Got it? Kewl?<BR>>>><BR>>>>Let us =
know if=20
that works for=20
you.<BR>>>><BR>>>>Neil <BR>>>><BR>>>><=
BR>>>><BR>>>><BR >>>><BR>>>><BR>>&g=
t;><BR>>>><BR>>>> <BR>>>><BR>>>><BR=
>>>><BR>>>><BR>>>> "DJ"=20
<animix _ at _ animas _ dot _ net>=20
wrote:<BR>>>><BR>>>>>Every time I close a project =
and then=20
reopen it, various patches to my<BR>>>>>external gear are=20
disabled.....especially prevalent on the inputs, but=20
not<BR>>>><BR>>>>>always, and sometimes the outputs =
are=20
reassigned to different ones. I =
never<BR>>>><BR>>>>>know=20
what I'm going to be faces with when I recall a project.=20
Sometimes<BR>>>><BR>>>>it=20
<BR>>>><BR>>>>>takes me 10-15 minutes just hunt =
everything=20
down to repatch.<BR>>>>><BR>>>>>This really=20
sucks........and I mean to the point that I'm about to=20
kick<BR>>>><BR>>>>this=20
<BR>>>><BR>>>>>damn thing out the window. Does =
Nuendo do=20
this too? I need to be able to<BR>>>><BR>>>>>save a =
project=20
with AD/DA's assigned to external processors and be=20
able<BR>>>><BR>>>>to=20
<BR>>>><BR>>>>>recall it.......CONSISTENTLY!!!. =
This=20
**FUCKING POS** is about to PISS =
ME<BR>>>><BR>>>>>OFF!!!!!=20
<BR>>>>><BR>>>>> <BR>>>><BR>>></FON=
T></BODY></HTML>
------=_NextPart_000_0359_01C7C5ED.0AC879A0--
|
|
|
|
|
|
|
|
| Re: Arrrgggghhhh!!!!!!!!!!! CUBASE 4 MUST DIE!!!!!!!! [message #88078 is a reply to message #88074] |
Sat, 14 July 2007 13:23 |
Neil
Messages: 1645
Registered: April 2006
|
Senior Member |
|
|
If you've got money (and reputation) riding on it, I would
migrate back to SX3 - or I think you said you went from SX2
to C4, so maybe you ca't migrate back to 3, but you COULD buy
v3 straight-up... get with you dealer & tell him what the
probems are and mybe he'll cut you a deal or try to get
Swineberg to kick in a half-price copy of SX3 or SOMETHING.
At least you could be working right along until until they get
C4 version 1-point-bugfix released.
I can tell you for sure that 3 will save the routing. It saves
it with the project, as long as you don't forget to save the
project once you've changed any patches around... which is easy
enough to forget, since AFAIK that's the one feature that it
DOENS'T prompt you to save any changes made therein. And as I
mentioned, it'll also save specific routing scenarios if you'd
rather go that additional route (which can be nice - that way
you can have a basic trax recording patch template, for
example).
So, Deej, what you're saying is that you tried saving routing
changes in both ways that I had pointed out & it still isn't
doing so?
Neil
"DJ" <animix _ at _ animas _ dot _ net> wrote:
>
>"John" <no@no.com> wrote in message news:469910ea$1@linux...
>>
>> DJ, you're becoming a real drama queen. Either figure your shit out
or
>> go
>> with a simpler setup. Drama is for girls.
>
>Let me ask you this John. Are you trying to use Cubase 4 in a professional
>environment or are you using it for your own personal stuff?
>
>Are you trying to interface it with over 20 analog processors?
>
>Are people looking over your shoulder saying things like, "shit man, this
>sucks.........are you gonna be able to get this out for me today?"
>
>Do you have any money riding on the results you are getting with it?
>
>If you did and it wasn't working *as advertized*, would you be a little
>stressed?
>
>BTW, I am not the only one having this problem.
>
>
>
>
>
|
|
|
|
|
|
| Re: Arrrgggghhhh!!!!!!!!!!! CUBASE 4 MUST DIE!!!!!!!! [message #88081 is a reply to message #88078] |
Sat, 14 July 2007 13:27 |
DJ
Messages: 1124
Registered: July 2005
|
Senior Member |
|
|
Hi Neil,
I do have SX3. I bought SX 4 for some of the features, but it seems this
proggie isn't ready for prime time in some areas. I thought the people on
the Cubase.net forum who were going ballistic about the ugs were just a
bunch of wankers until I started trying to push this program a little. I may
go back to SX3....or I may just upgrade to N3. One of my clients is writing
music for video and I think N3 may be a logical move to make. It's got the
features of C4 that were the reason I upgraded from SX3, plus it's got the
post capabilities.
I did try saving the routing scenarios as you described. Sometimes I can
save a project, shut the computer down, reboot it, open the project and
everything is saved. Other times, the patches (inputs mostly) are
disconnected and sometimes different inputs and outputs have been assigned
to the external FX. the idea of the drivers initializing in a different
sequence would make sense except that the I/O that are patched into my
digital patchbay are not being switched, and if these remain the same, that
would indicate that the cards are showing up in the same order each time.
Deej (the drama queen)
"Neil" <OIUOIU@OIU.com> wrote in message news:469930a8$1@linux...
>
> If you've got money (and reputation) riding on it, I would
> migrate back to SX3 - or I think you said you went from SX2
> to C4, so maybe you ca't migrate back to 3, but you COULD buy
> v3 straight-up... get with you dealer & tell him what the
> probems are and mybe he'll cut you a deal or try to get
> Swineberg to kick in a half-price copy of SX3 or SOMETHING.
> At least you could be working right along until until they get
> C4 version 1-point-bugfix released.
>
> I can tell you for sure that 3 will save the routing. It saves
> it with the project, as long as you don't forget to save the
> project once you've changed any patches around... which is easy
> enough to forget, since AFAIK that's the one feature that it
> DOENS'T prompt you to save any changes made therein. And as I
> mentioned, it'll also save specific routing scenarios if you'd
> rather go that additional route (which can be nice - that way
> you can have a basic trax recording patch template, for
> example).
>
> So, Deej, what you're saying is that you tried saving routing
> changes in both ways that I had pointed out & it still isn't
> doing so?
>
> Neil
>
>
> "DJ" <animix _ at _ animas _ dot _ net> wrote:
>>
>>"John" <no@no.com> wrote in message news:469910ea$1@linux...
>>>
>>> DJ, you're becoming a real drama queen. Either figure your shit out
> or
>>> go
>>> with a simpler setup. Drama is for girls.
>>
>>Let me ask you this John. Are you trying to use Cubase 4 in a professional
>
>>environment or are you using it for your own personal stuff?
>>
>>Are you trying to interface it with over 20 analog processors?
>>
>>Are people looking over your shoulder saying things like, "shit man, this
>
>>sucks.........are you gonna be able to get this out for me today?"
>>
>>Do you have any money riding on the results you are getting with it?
>>
>>If you did and it wasn't working *as advertized*, would you be a little
>
>>stressed?
>>
>>BTW, I am not the only one having this problem.
>>
>>
>>
>>
>>
>
|
|
|
|
| Re: Arrrgggghhhh!!!!!!!!!!! CUBASE 4 MUST DIE!!!!!!!! [message #88082 is a reply to message #88078] |
Sat, 14 July 2007 13:27 |
audioguy_editout_
Messages: 249
Registered: December 2005
|
Senior Member |
|
|
AFAIK, SX3 will run on a C4 dongle... I know for sure that
the N3 dongle will run SX3...
David.
Neil wrote:
> If you've got money (and reputation) riding on it, I would
> migrate back to SX3 - or I think you said you went from SX2
> to C4, so maybe you ca't migrate back to 3, but you COULD buy
> v3 straight-up... get with you dealer & tell him what the
> probems are and mybe he'll cut you a deal or try to get
> Swineberg to kick in a half-price copy of SX3 or SOMETHING.
> At least you could be working right along until until they get
> C4 version 1-point-bugfix released.
>
> I can tell you for sure that 3 will save the routing. It saves
> it with the project, as long as you don't forget to save the
> project once you've changed any patches around... which is easy
> enough to forget, since AFAIK that's the one feature that it
> DOENS'T prompt you to save any changes made therein. And as I
> mentioned, it'll also save specific routing scenarios if you'd
> rather go that additional route (which can be nice - that way
> you can have a basic trax recording patch template, for
> example).
>
> So, Deej, what you're saying is that you tried saving routing
> changes in both ways that I had pointed out & it still isn't
> doing so?
>
> Neil
>
>
> "DJ" <animix _ at _ animas _ dot _ net> wrote:
>
>>"John" <no@no.com> wrote in message news:469910ea$1@linux...
>>
>>>DJ, you're becoming a real drama queen. Either figure your shit out
>
> or
>
>>>go
>>>with a simpler setup. Drama is for girls.
>>
>>Let me ask you this John. Are you trying to use Cubase 4 in a professional
>
>
>>environment or are you using it for your own personal stuff?
>>
>>Are you trying to interface it with over 20 analog processors?
>>
>>Are people looking over your shoulder saying things like, "shit man, this
>
>
>>sucks.........are you gonna be able to get this out for me today?"
>>
>>Do you have any money riding on the results you are getting with it?
>>
>>If you did and it wasn't working *as advertized*, would you be a little
>
>
>>stressed?
>>
>>BTW, I am not the only one having this problem.
>>
>>
>>
>>
>>
>
>
|
|
|
|
|
|
|
|
| Re: Arrrgggghhhh!!!!!!!!!!! CUBASE 4 MUST DIE!!!!!!!! [message #88106 is a reply to message #88100] |
Sun, 15 July 2007 05:33 |
John [1]
Messages: 2229
Registered: September 2005
|
Senior Member |
|
|
I have always had trouble with paris but I didn't built a franken-daw like
DJ. Just a simple 2 card setup was never solid for me where now in cubase
i'm very solid but i don't have a franken-daw either, just one lowly 9652
audio card.
I'm sure I have thrown some drama around though and for that I apologize.
John
"Martin Harrington" <lendan@bigpond.net.au> wrote:
>OOhh, that's calling the kettle black.
>I remember a few posts regarding Paris that were written in much stronger
>language than that.
>Do you remember, John? ;>}
>
>Martin Harrington
>www.lendanear-sound.com
>0414 913 247
>
>"John" <no@no.com> wrote in message news:469910ea$1@linux...
>>
>> DJ, you're becoming a real drama queen. Either figure your shit out
or
>> go
>> with a simpler setup. Drama is for girls.
>
>--
>
|
|
|
|
Goto Forum:
Current Time: Fri Dec 20 22:46:03 PST 2024
Total time taken to generate the page: 0.01314 seconds
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
