external hard drive

  • Thread starter Thread starter JohnBJohn
  • Start date Start date
J

JohnBJohn

Tard
I recently got a motu traveler which i use with a macbook and logic. I want to record all of my logic projects directly to an external hard drive rather than the macbook's internal. How do I set up Logic to do this?
 
Create a new project and save it to the external drive? I assume Logic does the whole "audio files follow project file" style of organization. Most audio apps do.
 
I'd like to stay away from usb but my only firewire input is tied up by the interface. The motu has 2 firewire outs, would I be able to hook up a hard drive to the second output and if so, would that be a wise course of action?
 
Yes you should be able to daisy chain the drive into the motu into the computer.
 
Would the data exchange running to and from the mac in a single port be to much information for the firewire to handle smoothly? Would i ultimately be better off with usb in terms of speed and cpu consumed?
 
i wouldnt think that using USB would be a bad route to go. on my desktop i record to a dedicated internal HDD, but i back up via mirror-USB and i have never had any issues.
 
Would the data exchange running to and from the mac in a single port be to much information for the firewire to handle smoothly? Would i ultimately be better off with usb in terms of speed and cpu consumed?

No. A single FireWire port can handle hundreds of channels of audio (173-ish at 96 kHz/24-bit), and FireWire is specifically designed to ensure that bulk traffic (disk I/O, for example) doesn't interfere with audio streams. USB is always a worse choice for hard drives because it does not support true DMA.
 
Sorry for trying to milk this dead and boring cow but one final question. Since my mac only has firewire 800, would it be a wise course of action to hook an hd up to my mac with fw 800 and then daisy chain the interface with the hd? (mac 800 port<hd 800 port<hd 400 port< interface 400 port) as opposed to (mac 800 port< interface 400 port< hd 400 port) and if so, would this allow for better transfer of data?
 
Sorry for trying to milk this dead and boring cow but one final question. Since my mac only has firewire 800, would it be a wise course of action to hook an hd up to my mac with fw 800 and then daisy chain the interface with the hd? (mac 800 port<hd 800 port<hd 400 port< interface 400 port) as opposed to (mac 800 port< interface 400 port< hd 400 port) and if so, would this allow for better transfer of data?

Yes, I'd put the HD first if it is a FW800 drive. IIRC, the Mac will communicate at the speed of the slowest link between it and a given device, so it will talk to the HD at S800 speeds, but will talk to the interface at S400. By putting the HD first, the bandwidth available to your hard drive can easily quintuple.

A simple example: if your audio interface uses 100Mbps worth of isoch bandwidth, on a FireWire 400 bus (half duplex), you would have 300Mbps total for disk I/O. If half of the isoch bandwidth is going to the device and half is coming from the device (for example), then on a FireWire 800 bus (full duplex) it would be taking 50 Mbps each way, leaving 750Mbps of incoming bandwidth and 750 Mbps of outgoing bandwidth, for a grand total of 1500 Mbps left over for disk I/O. Much better than 300. :D
 
Yes, I'd put the HD first if it is a FW800 drive. IIRC, the Mac will communicate at the speed of the slowest link between it and a given device, so it will talk to the HD at S800 speeds, but will talk to the interface at S400. By putting the HD first, the bandwidth available to your hard drive can easily quintuple.

A simple example: if your audio interface uses 100Mbps worth of isoch bandwidth, on a FireWire 400 bus (half duplex), you would have 300Mbps total for disk I/O. If half of the isoch bandwidth is going to the device and half is coming from the device (for example), then on a FireWire 800 bus (full duplex) it would be taking 50 Mbps each way, leaving 750Mbps of incoming bandwidth and 750 Mbps of outgoing bandwidth, for a grand total of 1500 Mbps left over for disk I/O. Much better than 300. :D

Yeah. What he said. :D:D:D:confused:
 
Back
Top