Home » The PARIS Forums » PARIS: Main » I just can't seem to help doing stuff like this
| I just can't seem to help doing stuff like this [message #92722] |
Wed, 14 November 2007 21:30  |
DJ
Messages: 1124
Registered: July 2005
|
Senior Member |
|
|
OK, so I've got Cubase 4.1 running on two computers (master slave in
systemlink) and I'm (as usual) not willing to acknowledge the limitations of
the software until I test them.
Well.....of course, the first thing that anyone would want to do is create a
project on the slave DAW and point it to a directory on the Master DAW over
the network, right? Why hell yes they would so being as curious as the next
guy, I do this, record enable the track and record some audio on the project
on the slave DAW across the network to the hard drive on the master DAW.
Then, while the project is still open on the master DAW, I open it in cubase
on the master DAW and now I've got the same project open on both computers
so I add a track to the project on the Master DAW and record some audio to
this and lo and behold, the audio shows up in the media bay of Cubase on the
master DAW and the project plays back sync'ed to Sytemlink on both DAWs.
"Cool!!" says I...........so then I close the project on the slave DAW and
then on the master DAW but I get an error in closing it and when I reopen
the project on the master DAW, the track I recorded wasn't saved.
"Hmmmmm"....methinks ......."let's explore this further" so I open the
project on both DAWs and now the track that I tracked on the slave DAW is
showing up on the master DAW. the first time I tried to play back the same
audio file simultaneously on both DAws, one of them crashed, but then I was
actually able to accomplish this. Why would I want to you ask???......well,
first of all it's a very cool way to create a slapback delay by tweaking the
buffers on the two machines.......since delay plugins have yet to be
invented...... ..;oD. I also thought I heard some muffled screams from one
or the other DAWs, but I'm not sure.
Further testing reveals going down this path to be complex and frustrating
for a number of other reasons, but I actually was able to accomplish a
somewhat successful workaround which would allow a similar level of
fuctionality to working with the networking features of Nuendo, but .....if
you want to do this, just buy Nuendo. It's not worth the grief
(well...unless you have a twisted intellectual curiousity).
One thing that seems to be gratifying however is that it is possible to
create two folders on the audio drive of the master DAW (master and slave)
and then create a project on the slave DAW and point it to the folder in the
Master DAW over the network, record to it, save it on this same networked
drive and when you open Cubase on the slave DAW it will find the project
again over the network. There seems to be adequate throughput over gigabit
network to stream the audio from a single networked master drive.
I still have some other nefarious ideas as far as bending this audio app to
my will that may actually enhance it's functionality rather than just
laterally pervert it as I seem to have managed to do tonight.
Stay tuned........
;o)
|
|
|
|
| Re: I just can't seem to help doing stuff like this [message #92723 is a reply to message #92722] |
Thu, 15 November 2007 01:15  |
steve the artguy
Messages: 308
Registered: June 2005
|
Senior Member |
|
|
"DJ" <animix _ at _ animas _ dot _ net> wrote:
>OK, so I've got Cubase 4.1 running on two computers (master slave in
>systemlink) and I'm (as usual) not willing to acknowledge the limitations
of
>the software until I test them.
>
>Well.....of course, the first thing that anyone would want to do is create
a
>project on the slave DAW and point it to a directory on the Master DAW over
>the network, right? Why hell yes they would so being as curious as the
next
>guy, I do this, record enable the track and record some audio on the project
>on the slave DAW across the network to the hard drive on the master DAW.
>
>Then, while the project is still open on the master DAW, I open it in cubase
>on the master DAW and now I've got the same project open on both computers
>so I add a track to the project on the Master DAW and record some audio
to
>this and lo and behold, the audio shows up in the media bay of Cubase on
the
>master DAW and the project plays back sync'ed to Sytemlink on both DAWs.
>
>"Cool!!" says I...........so then I close the project on the slave DAW and
>then on the master DAW but I get an error in closing it and when I reopen
>the project on the master DAW, the track I recorded wasn't saved.
>"Hmmmmm"....methinks ......."let's explore this further" so I open the
>project on both DAWs and now the track that I tracked on the slave DAW is
>showing up on the master DAW. the first time I tried to play back the same
>audio file simultaneously on both DAws, one of them crashed, but then I
was
>actually able to accomplish this. Why would I want to you ask???......well,
>first of all it's a very cool way to create a slapback delay by tweaking
the
>buffers on the two machines.......since delay plugins have yet to be
>invented...... ..;oD. I also thought I heard some muffled screams from
one
>or the other DAWs, but I'm not sure.
>
>Further testing reveals going down this path to be complex and frustrating
>for a number of other reasons, but I actually was able to accomplish a
>somewhat successful workaround which would allow a similar level of
>fuctionality to working with the networking features of Nuendo, but .....if
>you want to do this, just buy Nuendo. It's not worth the grief
>(well...unless you have a twisted intellectual curiousity).
>
>One thing that seems to be gratifying however is that it is possible to
>create two folders on the audio drive of the master DAW (master and slave)
>and then create a project on the slave DAW and point it to the folder in
the
>Master DAW over the network, record to it, save it on this same networked
>drive and when you open Cubase on the slave DAW it will find the project
>again over the network. There seems to be adequate throughput over gigabit
>network to stream the audio from a single networked master drive.
>
>I still have some other nefarious ideas as far as bending this audio app
to
>my will that may actually enhance it's functionality rather than just
>laterally pervert it as I seem to have managed to do tonight.
>
>Stay tuned........
>
>;o)
>
>
whatever you do, don't go back in time and kill your parents, ok?
|
|
|
|
| Re: I just can't seem to help doing stuff like this [message #92729 is a reply to message #92722] |
Thu, 15 November 2007 07:31 |
|
|
It's obvious to me that you have too much time on your hands. You need a
couple of kids. I have a wonderful pair that I'd be happy to rent to you
- an adorable 7 (soon to be 8) year old daughter and a strapping 10 year
old son. Let you have both for a week or two cheap. Even cheaper if you
teach 'em to ride (horses that is).
Gantt
"DJ" <animix _ at _ animas _ dot _ net> wrote:
>OK, so I've got Cubase 4.1 running on two computers (master slave in
>systemlink) and I'm (as usual) not willing to acknowledge the limitations
of
>the software until I test them.
>
>Well.....of course, the first thing that anyone would want to do is create
a
>project on the slave DAW and point it to a directory on the Master DAW over
>the network, right? Why hell yes they would so being as curious as the
next
>guy, I do this, record enable the track and record some audio on the project
>on the slave DAW across the network to the hard drive on the master DAW.
>
>Then, while the project is still open on the master DAW, I open it in cubase
>on the master DAW and now I've got the same project open on both computers
>so I add a track to the project on the Master DAW and record some audio
to
>this and lo and behold, the audio shows up in the media bay of Cubase on
the
>master DAW and the project plays back sync'ed to Sytemlink on both DAWs.
>
>"Cool!!" says I...........so then I close the project on the slave DAW and
>then on the master DAW but I get an error in closing it and when I reopen
>the project on the master DAW, the track I recorded wasn't saved.
>"Hmmmmm"....methinks ......."let's explore this further" so I open the
>project on both DAWs and now the track that I tracked on the slave DAW is
>showing up on the master DAW. the first time I tried to play back the same
>audio file simultaneously on both DAws, one of them crashed, but then I
was
>actually able to accomplish this. Why would I want to you ask???......well,
>first of all it's a very cool way to create a slapback delay by tweaking
the
>buffers on the two machines.......since delay plugins have yet to be
>invented...... ..;oD. I also thought I heard some muffled screams from
one
>or the other DAWs, but I'm not sure.
>
>Further testing reveals going down this path to be complex and frustrating
>for a number of other reasons, but I actually was able to accomplish a
>somewhat successful workaround which would allow a similar level of
>fuctionality to working with the networking features of Nuendo, but .....if
>you want to do this, just buy Nuendo. It's not worth the grief
>(well...unless you have a twisted intellectual curiousity).
>
>One thing that seems to be gratifying however is that it is possible to
>create two folders on the audio drive of the master DAW (master and slave)
>and then create a project on the slave DAW and point it to the folder in
the
>Master DAW over the network, record to it, save it on this same networked
>drive and when you open Cubase on the slave DAW it will find the project
>again over the network. There seems to be adequate throughput over gigabit
>network to stream the audio from a single networked master drive.
>
>I still have some other nefarious ideas as far as bending this audio app
to
>my will that may actually enhance it's functionality rather than just
>laterally pervert it as I seem to have managed to do tonight.
>
>Stay tuned........
>
>;o)
>
>
Gantt Kushner
Gizmo Recording Company
Silver Spring, MD
www.gizmorecording.com
|
|
|
|
| Re: I just can't seem to help doing stuff like this [message #92737 is a reply to message #92722] |
Thu, 15 November 2007 09:48 |
rick
Messages: 1976
Registered: February 2006
|
Senior Member |
|
|
bet you had reeeeeeeeeealy hairy palms as a lad...huh...huh...
On Wed, 14 Nov 2007 22:30:57 -0700, "DJ" <animix _ at _ animas _ dot _
net> wrote:
>OK, so I've got Cubase 4.1 running on two computers (master slave in
>systemlink) and I'm (as usual) not willing to acknowledge the limitations of
>the software until I test them.
>
>Well.....of course, the first thing that anyone would want to do is create a
>project on the slave DAW and point it to a directory on the Master DAW over
>the network, right? Why hell yes they would so being as curious as the next
>guy, I do this, record enable the track and record some audio on the project
>on the slave DAW across the network to the hard drive on the master DAW.
>
>Then, while the project is still open on the master DAW, I open it in cubase
>on the master DAW and now I've got the same project open on both computers
>so I add a track to the project on the Master DAW and record some audio to
>this and lo and behold, the audio shows up in the media bay of Cubase on the
>master DAW and the project plays back sync'ed to Sytemlink on both DAWs.
>
>"Cool!!" says I...........so then I close the project on the slave DAW and
>then on the master DAW but I get an error in closing it and when I reopen
>the project on the master DAW, the track I recorded wasn't saved.
>"Hmmmmm"....methinks ......."let's explore this further" so I open the
>project on both DAWs and now the track that I tracked on the slave DAW is
>showing up on the master DAW. the first time I tried to play back the same
>audio file simultaneously on both DAws, one of them crashed, but then I was
>actually able to accomplish this. Why would I want to you ask???......well,
>first of all it's a very cool way to create a slapback delay by tweaking the
>buffers on the two machines.......since delay plugins have yet to be
>invented...... ..;oD. I also thought I heard some muffled screams from one
>or the other DAWs, but I'm not sure.
>
>Further testing reveals going down this path to be complex and frustrating
>for a number of other reasons, but I actually was able to accomplish a
>somewhat successful workaround which would allow a similar level of
>fuctionality to working with the networking features of Nuendo, but .....if
>you want to do this, just buy Nuendo. It's not worth the grief
>(well...unless you have a twisted intellectual curiousity).
>
>One thing that seems to be gratifying however is that it is possible to
>create two folders on the audio drive of the master DAW (master and slave)
>and then create a project on the slave DAW and point it to the folder in the
>Master DAW over the network, record to it, save it on this same networked
>drive and when you open Cubase on the slave DAW it will find the project
>again over the network. There seems to be adequate throughput over gigabit
>network to stream the audio from a single networked master drive.
>
>I still have some other nefarious ideas as far as bending this audio app to
>my will that may actually enhance it's functionality rather than just
>laterally pervert it as I seem to have managed to do tonight.
>
>Stay tuned........
>
>;o)
>
|
|
|
|
| Re: I just can't seem to help doing stuff like this [message #92740 is a reply to message #92722] |
Thu, 15 November 2007 12:43 |
TCB
Messages: 1261
Registered: July 2007
|
Senior Member |
|
|
Hey Deej,
While there are real problems having files open by two applications (and
I expect you could run into problems down the road no matter how you work
around), for my job I've been investigating and iSCSI SAN for some of our
production apps. You don't need bending end gear for iSCSI anymore. Just
a machine that will RAID some drives, a gigabit switch that supports jumbo
frames, and some CPU cycles to spare (they have to calculate the tcp frames,
unless you buy a fancy network card with some built in brains). We're going
for a pretty high end system with all kinds of fancy stuff (snapshots, mirroring,
replication, etc.) but you might want to consider a fileserver.
TCB
"DJ" <animix _ at _ animas _ dot _ net> wrote:
>OK, so I've got Cubase 4.1 running on two computers (master slave in
>systemlink) and I'm (as usual) not willing to acknowledge the limitations
of
>the software until I test them.
>
>Well.....of course, the first thing that anyone would want to do is create
a
>project on the slave DAW and point it to a directory on the Master DAW over
>the network, right? Why hell yes they would so being as curious as the
next
>guy, I do this, record enable the track and record some audio on the project
>on the slave DAW across the network to the hard drive on the master DAW.
>
>Then, while the project is still open on the master DAW, I open it in cubase
>on the master DAW and now I've got the same project open on both computers
>so I add a track to the project on the Master DAW and record some audio
to
>this and lo and behold, the audio shows up in the media bay of Cubase on
the
>master DAW and the project plays back sync'ed to Sytemlink on both DAWs.
>
>"Cool!!" says I...........so then I close the project on the slave DAW and
>then on the master DAW but I get an error in closing it and when I reopen
>the project on the master DAW, the track I recorded wasn't saved.
>"Hmmmmm"....methinks ......."let's explore this further" so I open the
>project on both DAWs and now the track that I tracked on the slave DAW is
>showing up on the master DAW. the first time I tried to play back the same
>audio file simultaneously on both DAws, one of them crashed, but then I
was
>actually able to accomplish this. Why would I want to you ask???......well,
>first of all it's a very cool way to create a slapback delay by tweaking
the
>buffers on the two machines.......since delay plugins have yet to be
>invented...... ..;oD. I also thought I heard some muffled screams from
one
>or the other DAWs, but I'm not sure.
>
>Further testing reveals going down this path to be complex and frustrating
>for a number of other reasons, but I actually was able to accomplish a
>somewhat successful workaround which would allow a similar level of
>fuctionality to working with the networking features of Nuendo, but .....if
>you want to do this, just buy Nuendo. It's not worth the grief
>(well...unless you have a twisted intellectual curiousity).
>
>One thing that seems to be gratifying however is that it is possible to
>create two folders on the audio drive of the master DAW (master and slave)
>and then create a project on the slave DAW and point it to the folder in
the
>Master DAW over the network, record to it, save it on this same networked
>drive and when you open Cubase on the slave DAW it will find the project
>again over the network. There seems to be adequate throughput over gigabit
>network to stream the audio from a single networked master drive.
>
>I still have some other nefarious ideas as far as bending this audio app
to
>my will that may actually enhance it's functionality rather than just
>laterally pervert it as I seem to have managed to do tonight.
>
>Stay tuned........
>
>;o)
>
>
|
|
|
|
| Re: I just can't seem to help doing stuff like this [message #92757 is a reply to message #92740] |
Thu, 15 November 2007 20:42 |
Neil
Messages: 1645
Registered: April 2006
|
Senior Member |
|
|
Why doesn't Deej just clone a file onto another trackset in the
same machine, then nudge over to get whatever desired slapback
or chorus-ey effect he's looking for?
Same result, no dual-app-file-opening conflict.
Neil
"TCB" <nobody@ishere.com> wrote:
>
>Hey Deej,
>
>While there are real problems having files open by two applications (and
>I expect you could run into problems down the road no matter how you work
>around), for my job I've been investigating and iSCSI SAN for some of our
>production apps. You don't need bending end gear for iSCSI anymore. Just
>a machine that will RAID some drives, a gigabit switch that supports jumbo
>frames, and some CPU cycles to spare (they have to calculate the tcp frames,
>unless you buy a fancy network card with some built in brains). We're going
>for a pretty high end system with all kinds of fancy stuff (snapshots, mirroring,
>replication, etc.) but you might want to consider a fileserver.
>
>TCB
>
>"DJ" <animix _ at _ animas _ dot _ net> wrote:
>>OK, so I've got Cubase 4.1 running on two computers (master slave in
>>systemlink) and I'm (as usual) not willing to acknowledge the limitations
>of
>>the software until I test them.
>>
>>Well.....of course, the first thing that anyone would want to do is create
>a
>>project on the slave DAW and point it to a directory on the Master DAW
over
>
>>the network, right? Why hell yes they would so being as curious as the
>next
>>guy, I do this, record enable the track and record some audio on the project
>
>>on the slave DAW across the network to the hard drive on the master DAW.
>>
>>Then, while the project is still open on the master DAW, I open it in cubase
>
>>on the master DAW and now I've got the same project open on both computers
>
>>so I add a track to the project on the Master DAW and record some audio
>to
>>this and lo and behold, the audio shows up in the media bay of Cubase on
>the
>>master DAW and the project plays back sync'ed to Sytemlink on both DAWs.
>>
>>"Cool!!" says I...........so then I close the project on the slave DAW
and
>
>>then on the master DAW but I get an error in closing it and when I reopen
>
>>the project on the master DAW, the track I recorded wasn't saved.
>>"Hmmmmm"....methinks ......."let's explore this further" so I open the
>>project on both DAWs and now the track that I tracked on the slave DAW
is
>
>>showing up on the master DAW. the first time I tried to play back the same
>
>>audio file simultaneously on both DAws, one of them crashed, but then
I
>was
>>actually able to accomplish this. Why would I want to you ask???......well,
>
>>first of all it's a very cool way to create a slapback delay by tweaking
>the
>>buffers on the two machines.......since delay plugins have yet to be
>>invented...... ..;oD. I also thought I heard some muffled screams from
>one
>>or the other DAWs, but I'm not sure.
>>
>>Further testing reveals going down this path to be complex and frustrating
>
>>for a number of other reasons, but I actually was able to accomplish a
>>somewhat successful workaround which would allow a similar level of
>>fuctionality to working with the networking features of Nuendo, but .....if
>
>>you want to do this, just buy Nuendo. It's not worth the grief
>>(well...unless you have a twisted intellectual curiousity).
>>
>>One thing that seems to be gratifying however is that it is possible to
>
>>create two folders on the audio drive of the master DAW (master and slave)
>
>>and then create a project on the slave DAW and point it to the folder in
>the
>>Master DAW over the network, record to it, save it on this same networked
>
>>drive and when you open Cubase on the slave DAW it will find the project
>
>>again over the network. There seems to be adequate throughput over gigabit
>
>>network to stream the audio from a single networked master drive.
>>
>>I still have some other nefarious ideas as far as bending this audio app
>to
>>my will that may actually enhance it's functionality rather than just
>>laterally pervert it as I seem to have managed to do tonight.
>>
>>Stay tuned........
>>
>>;o)
>>
>>
>
|
|
|
|
|
|
Goto Forum:
Current Time: Thu May 23 03:17:46 PDT 2024
Total time taken to generate the page: 0.04218 seconds
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
