- 第 4 页 -
剛又試了一下, 資源運用方面, 相當不錯。開了35軌 (不計 AUX & SUB GROUP), 目前>8-10 eq & compressor , 3 gate, aux - 8 軌送到2 studio reveb , master output -1 levelizer
用 force single cpu 模式- 佔用了 13-18% , dual cpu 12-18% (分別不大)。
HaHa 連BCF2000 也可以用......
1) options > midi setup > 選 IN , OUT
2) SMPTE/MIDI > 選 MIDI CONTROL IN ACTIVE 和 MIDI CONTROL OUT ACTIVE
3) FILE > MIDI CONTROL TEMPLATE FILE > 選 MACKIE CONTROL 或 MACKIE HUI 也可。
[ Last edited by himhui on 2005-8-16 at 01:48 ]
用 force single cpu 模式- 佔用了 13-18% , dual cpu 12-18% (分別不大)。
HaHa 連BCF2000 也可以用......
1) options > midi setup > 選 IN , OUT
2) SMPTE/MIDI > 選 MIDI CONTROL IN ACTIVE 和 MIDI CONTROL OUT ACTIVE
3) FILE > MIDI CONTROL TEMPLATE FILE > 選 MACKIE CONTROL 或 MACKIE HUI 也可。
[ Last edited by himhui on 2005-8-16 at 01:48 ]
看來經網絡做現場或遙控錄音也是不錯。
簡單說, 它分為三個模式, master(主機), remote(遙控), slave (被支配)
remote(遙控) 模式可利用 laptop 控制 master(主機), 而laptop亦無須要裝上聲卡。
slave (被支配) 模式可讓兩部電腦同步, 一為master,一為 slave (最多可拖八部 slaves) ,處理不同數據。master 和 slave的 output 可直接出到 mixer。同步初時會有點延遲, 若網絡速度夠快, 延遲將會咸至很少。
slave 模式亦可用作現場即時備份, 當一部電腦有問題時, 另一部(或八部)馬上可頂上。
There are three different modes of this feature... Master, Remote and Slave.
The original idea behind the remote feature was to allow the use of a second pc (possibly a laptop) to control the main pc system in the studio from a remote location. The studio pc is placed in Master Mode... the second pc is set to remote mode.
The remote pc does not actually even need a soundcard in it... it does not play audio, but it does display the edl regions and waveforms that it gets from the Master pc. Most controls for working the engine and record operations are active... pretty much all mixer controls are active. You can arm tracks, change layers, name tracks, start playback or SRP, punch in, retake... etc... you can also control the mix... all from a remote location... so you could be in a drum booth for example running the session on the main pc.
Very few editing commands are active and editing should be done with the remote pc dis-engaged (from the menu)... the details of all active commands can be found in the TCP/IP section of the helpfile.
The Slave mode is slightly different. It actually allows 2 pcs to run in sync (with whatever network latencies there may be) such that you could process certain tracks or plugins on one machine running in sync with the Master machine and then blend the two machines audio outputs together in an external mixer or back as a live input signal to the master.
This can be used to link up to 8 slave machines together with a master for extended processing power. I have used this on huge sessions that carry video to split the video load off to a slave machine.
The Lon Bronson session (search the threads for details) was done using 2 laptops as master/slave to record 35 tracks live across the 2 machines which each only had 24 chans of i/o.
The slave machine, once started will stay locked when you lock the soundcards together with word clock or some other common clock method... but there will still be a slight latency at the start due to network randomness.
There is a latency compensator feature to compensate for large repeatable delays... but with a fast network, these latencies can be reduced to very small sample values.
In the case of Lon's project, I actually transferred the slave machine files back to the master in a blended edl... zoomed in and slid the slave tracks into position using the countoffs of the songs... then I worked the final editing and mixing in the one machine.
If you split your i/o for the recording, you could definitely use this method to do a live backup of the session... the 2 machines will start and stop together and punch in together... etc... if the master goes down, the slave will keep running on its own... I have used this concept to do large production shows, where the clients wanted a duplicate machine running as backup in case the master machine failed during performance... a quick switch of some mutes on the house console and the music continues without skipping a beat...
[ Last edited by himhui on 2005-8-18 at 17:41 ]
簡單說, 它分為三個模式, master(主機), remote(遙控), slave (被支配)
remote(遙控) 模式可利用 laptop 控制 master(主機), 而laptop亦無須要裝上聲卡。
slave (被支配) 模式可讓兩部電腦同步, 一為master,一為 slave (最多可拖八部 slaves) ,處理不同數據。master 和 slave的 output 可直接出到 mixer。同步初時會有點延遲, 若網絡速度夠快, 延遲將會咸至很少。
slave 模式亦可用作現場即時備份, 當一部電腦有問題時, 另一部(或八部)馬上可頂上。
There are three different modes of this feature... Master, Remote and Slave.
The original idea behind the remote feature was to allow the use of a second pc (possibly a laptop) to control the main pc system in the studio from a remote location. The studio pc is placed in Master Mode... the second pc is set to remote mode.
The remote pc does not actually even need a soundcard in it... it does not play audio, but it does display the edl regions and waveforms that it gets from the Master pc. Most controls for working the engine and record operations are active... pretty much all mixer controls are active. You can arm tracks, change layers, name tracks, start playback or SRP, punch in, retake... etc... you can also control the mix... all from a remote location... so you could be in a drum booth for example running the session on the main pc.
Very few editing commands are active and editing should be done with the remote pc dis-engaged (from the menu)... the details of all active commands can be found in the TCP/IP section of the helpfile.
The Slave mode is slightly different. It actually allows 2 pcs to run in sync (with whatever network latencies there may be) such that you could process certain tracks or plugins on one machine running in sync with the Master machine and then blend the two machines audio outputs together in an external mixer or back as a live input signal to the master.
This can be used to link up to 8 slave machines together with a master for extended processing power. I have used this on huge sessions that carry video to split the video load off to a slave machine.
The Lon Bronson session (search the threads for details) was done using 2 laptops as master/slave to record 35 tracks live across the 2 machines which each only had 24 chans of i/o.
The slave machine, once started will stay locked when you lock the soundcards together with word clock or some other common clock method... but there will still be a slight latency at the start due to network randomness.
There is a latency compensator feature to compensate for large repeatable delays... but with a fast network, these latencies can be reduced to very small sample values.
In the case of Lon's project, I actually transferred the slave machine files back to the master in a blended edl... zoomed in and slid the slave tracks into position using the countoffs of the songs... then I worked the final editing and mixing in the one machine.
If you split your i/o for the recording, you could definitely use this method to do a live backup of the session... the 2 machines will start and stop together and punch in together... etc... if the master goes down, the slave will keep running on its own... I have used this concept to do large production shows, where the clients wanted a duplicate machine running as backup in case the master machine failed during performance... a quick switch of some mutes on the house console and the music continues without skipping a beat...
[ Last edited by himhui on 2005-8-18 at 17:41 ]