Firewire conflicts

What do people use to output digital audio from the Quad to external monitors (speakers)?
I have M-Audio's firewire 410 but i causes more conflicts with iSight, DV cameras and eyeTV than I care to mention. It takes a lot of work to get firewire back up and running afterwards.
I'm thinking about getting a digital mixer such as Yamaha 01v96 V2 to take a direct input from the Quad and hopefully eliminate all the firewire problems. At £1600 it's not a cheap solution. What do people do?

I'm now looking at Behringer DDX3216 with the optical expansion option (£500 from Germany, about £650-700 in the UK).
I'm not finding exactly what i want though, essentially a mixer with mostly digital I/O's instead of analogue.

Similar Messages

Macbook, Snow Leopard, Pro Tools 8 Firewire Conflict

I apologized in advance if this issue has already been posted, but I was unable to find it using the search function.
I have been getting a 6101 error while running M-Powered Pro Tools 8 (8.04)using 2 different M-Audio Firewire Interfaces (Firewire410 and Profire 610). I am only playing back 3 audio track w/no plug ins. CPU usage hasn't gone over 5% and I am getting a Hardware Buffer Error, whcih I have changed numerous times to no avail. I have a new, clean install of Snow Leopard, ProTools, and Interface Drivers with all of the latest updates. Hardware Settings: (1024 Samples, 1 Processor, 95% CPU Available)
However, I tried the M-Audio Fast Track Ultra USB 2 interface and have had no issues. I have ran through the session over 15 times and haven't had a crash.
Is there any known conflict between Snow Leopard, the firewire drivers and, the latest ProTools/M-Audio components? And, is there a workaround/new firewire driver that will fix this problem??
Thanks,
JIM
Black Macbook
2.15GHZ Intel Core 2 Duo, 2GB RAM
Snow Leopard 10.6.4
M-Powered Pro Tools 8.0.4

Ok, that's what I have done... I have Snow Leopard Installed, 10.8.6 and it's got Boot Camp 3.0.4... my questionis the Mac Windows Install Drivers you add after installing Windows. Windows looks terribly awkward and I'm guessing it has something to do with the ATI graphics card sofware the mac disk installed. Is is ok to use the one I created years ago? I can't seem to find a place to create a new one using the 10.8.6 and 3.0.4.
When I orignially installed Boot Camp you had to create a disk using Boot Camp that you installed in Windows after the initial OS installation.

Firewire Conflict with HD & Canopus 110

Anyone have any exeprience with Firewire 400 conflicts like this...?
The only way I can use both my LaCie HD (big disk extreme 500G) and Canopus ADVC 110 (C-110) is to first boot my system with the HD on and the C-110 powered off. When I then connect the C-110, the system is able to see both and everything works fine (so far). BUT...
If I boot my system with both the LaCie HD and the C-110 connected via Firewire 400, the system doesn't see either one. If I then go into the sytem profiler and look under Hardware>Firewire, the system hangs and I have to reboot. I've also had the sytem hang when trying to load FCE HD 3.5, forcing yet another reboot.
Are there known conflicts like this? I've searched this forum and couldn't find anything specific to this set up. While I do have a work around, it's not convenient and it still suggests something is amiss.
Any insights would be greatly appreciated. I'm eager to get down to some productive work,and this isn't helping.
2GHz PowerPC G5 Mac OS X (10.4.8) Canopus ADVC 110 and LaCie d2 connected via Firewire 400
2GHz PowerPC G5 Mac OS X (10.4.8)
2GHz PowerPC G5 Mac OS X (10.4.8)

Hi,
I have Lacie d2's (no big disk extreme, however) and the ADVC-110. Haven't had any problems with them when connected at the same time, but I could make a few suggestions -
If you have the ADVC daisychained off the drive, don't. If you have them on the same FW controller, put them on separate ones if possible, although I realize that may require an additional FW card.
Sometimes there are issues with miniDVcams connected to the front FW port on the G5, if that's where you have the ADVC connected that may be a factor.
Also, if you ever connected/disconnected the FW cable to the ADVC while it was powered on or the G5 was powered, the FW chip in the ADVC may have been damaged. (And the FW ports on the G5 are powered even when the machine is shut down, unless you have disconnected power at the wall or at your surge protector/UPS).
But maybe you've already checked all this ...

Firewire conflict? aka I don't know what's going on!

Running OS 10.4.9, QT 7.1.5, and FCP 5.1.4 on a PowerMac Dual 2Ghz G5 with a LACIE 500GB FWD and Sony DSR-11 attached via firewire.
Brand new problem here: When I have the LACIE drive mounted and try and use my DSR-11 to 'View External Video' (over NTSC Firewire), I get the spinning beach ball that won't go away until I power down my DSR-11. If I don't have the LACIE mounted, I can 'View External Video' via firewire, but that doesn't help when my media for my project is on the LACIE. I've never seen this before.
Another weird thing about it: I tried emptying the trash with both the LACIE and DSR-11 powered on. One of the items in the trash was from my startup disk (FCP preferences file) and one was from the LACIE drive (a QT media file). I got the spinning beach ball in the Finder and the trash stalled during emptying. I powered down the DSR-11 and it instantly finished emptying the trash.
Any suggestions? I already trashed preferences... Not totally sure this is even a FCP problem, but this seemed the best place to post.

Well, the main thing was that the DSR-11 was registering in the System Profiler on the laptop. Just mentioned iMovie because that was the only app on that computer that utilizes the DSR-11 and wanted to point out that it was functioning with software.
The bigger news is: I finally got everything up and operational on the G5. DSR-11 connected to rear bus and fucntioning properly - LACIE connected to fron bus and functioning properly. Both devices appear in the System Profiler.
I think the issue was that the Bizarro World was overlapping too much with the Real World. A bunch of disconnecting/reconnecting and 5 or so restarts seem to have fixed whatever problem there was. Thanks for all help - sorry I can't offer a clear cut solution (I think this was just one of those "deadline-based" problems - you know: the ones that appear out of nowhere whenever you have a tight deadline and you're already behind
Message was edited by: Mr. Landers

FireWire conflict

I just got a new LaCie external 3TB hard drive connected to my Mac Pro via FireWire 800. I started using it as a secondary Time Machine backup drive, but when Time Machine is backing up to it, I cannot use my iSight camera with Messages. I am still using an external iSight camera which is plugged into an adapter for FireWire 400 to 800. I also have a WD external hard drive using FireWire 800 as my first Time Machine backup drive and have not had any problems with my iSight camera while using that. If I stop my Time Machine backup, I can use my iSight camera for a videochat, but I wonder if there is any fix for this problem. Or do I have to always do a workaround?
I don't think this should matter but the WD FW drive is plugged into the back of my MacPro and the LaCie is plugged into one of the front FW ports.

Maybe another workaround would be to daisy-chain the hard drives and connect the iSight directly to the front FW port.
I don't think you should have to use any workaround, but I don't have enough experience with FW daisy-chaining to answer authoritatively.

Firewire Issues Caused By Apple Isight!

For months, I've been having an intermittent Firewire audio problem, which I initially thought was A) Quad G5 or B) RME Fireface 800!
Testing the RME on another Quad G5 resulted in no errors, though for piece of mind a replacement RME was given! Back home the same intermittent problems occurred, it had to be the Quad G5???
Livid, this time I persisted on Google searching for FW issues, (a few hours later) to my amazement I came across an article on MacFixIt, that pointed the finger to Apple's own iSight FW camera, which I had connected!
The transcript below explains how to resolve this problem, it worked for me!
Mini-Tutorial: Dealing with FireWire problems (drives not mounting, devices unrecognized, etc.)
As an Apple-invented technology, FireWire (IEEE 1394a and IEEE 1394b) should be (and usually is) one of the most solid and efficient means for interfacing with external peripherals. Indeed Apple's "i"-branded devices -- the iPod and iSight -- have, in large part, been made possible by the quick transfer rates, power sourcing, and hot pluggability offered by FireWire.
Occasionally, however, conflicts between FireWire-connected devices arise and can result in a variety of issues including DV cameras dropping frames, FireWire drives not mounting, and erratic behavior from the iPod (disappearing from iTunes, etc.). In the midst of these issues, you might also experience "buffer underrun" errors when trying to burn CDs or DVDs with FireWire-connected recorders.
The iSight is especially notorious for causing issues of this nature, and exhibiting symptoms.
There exist a number of methods for dealing with FireWire device interference, a few of which are explored here.
Switching Ports The first procedure you should try when experiencing a problem that you believe to be caused by device interference is to simply reconfigure the arrangement in which your FireWire peripherals are connected.
Try switching each device to a different port, or temporarily disconnecting one or more of the devices. In particular, if you are a PowerMac G5 owner, trying switching devices from the front to back ports or vice versa.
Adding an external hub In some cases, it appears that FireWire devices are not drawing enough power from the computer. This can cause a sundry of strange issues, including apparent conflicts between devices and unexpected power-offs during device operation. In these instances, adding an externally powered FireWire hub can clear things up.
One of the reasons an "under-powered" situation can occur is that different Mac models have varying power capacities available through their FireWire ports.
PowerBooks and iBooks have the least, generating around 7 watts. The iMac G5 also generates a relatively low amount of FireWire power, sharing 8 watts between its two FireWire 400 ports.
The Power Mac G5 shares 15 watts between its one FireWire 800 port and two FireWire 400 ports.
Place devices on different FireWire busses/Isolate the iSight Similar to the above procedure, adding another FireWire bridge -- via an extra PCI-based FireWire adapter or another means -- can eliminate conflicts from devices that reside on the same bridge.
Power cycling the system Simply cycling the power on your system may be enough to temporarily eliminate a few FireWire conflict issues.
Shut down your Mac, and disconnect all FireWire devices as well as the computer's power cord. Leave the system off for about 10 minutes, then plug it back in. First turn your Mac back on, then re-attach the FireWire devices one at a time and check for the conflict to resurface.
Disconnect the iSight As noted above, the most common cause of interference is Apple's own iSight. In case after case, simply disconnecting this single device has eliminated problems with other FireWire devices.
Disconnecting the iSight has proved particularly successful for an issue where the iPod disappears from the Desktop and from the iTunes playlist, while the iPod status screen cycles from the Apple logo to a "Do not Disconnect" message over and over.
The exact reasons why the iSight causes more than its fair share conflicts with other FireWire devices are many, and sometimes unclear. One potential source of conflict, however, could be the unit's high bandwidth usage.
The iSight captures video at a 640 x 480 pixel resolution, at 30 frames per second in millions of colors. Such throughput uses a significant chunk of the standard FireWire port's 400 Mbps bandwidth. As such, when other devices are connected, the bandwidth requirements for satisfactory performance may not be met.
Apply the latest updates Make sure that your FireWire drives are using the latest firmware (check the manufacturers' Web site) and the most recent iPod update has also been applied.
Of higher importance, if you have an iSight, is the iSight 1.0.2 updater. In a large number of cases it has resolved conflicts caused by the camera.
Re-apply the most recent Mac OS X combo updater In some cases, re-applying the most recent combo updater can resurrect seemingly defunct FireWire ports and allow devices -- drives included -- to be recognized again.
The most recent combo updater is available from Apple's download page.
Clear caches Try using a tool like Tiger Cache Cleaner or Cocktail to remove potentially corrupt system caches. Restart, then check if your FireWire devices are recognized.
Ps. There was no iSight connected when testing the RME on another Quad!
Power Mac G5 Quad 2.5 GHz Mac OS X (10.4.4) 2x 2.5 GB HD, 2.5 GB RAM, iSight, iPod, RME Fireface 800 Audio Interface

TA

AJA IOLA and fire wire

I'm confused. I am setting up a FCP system on a brand new G5 dual 2.7 gHz with a 375 GB hard drive. I am using an AJA IO LD for input. From what I read, I can't digitize to the internal hard drive if the AJA is also using this hard drive (which sort of seems like a waste of 300 GB of perfectly fine space). I will be using a DVCam DSR 80 and a Sony Beta UVW 1800? as component input sources. Can I digitize to an EXTERNAL 7200 RPM Firewire hard drive?

Ronnie,
I do have an extra firewire card - but its a recent extra to my system to simply increase the number of my firewire sockets.
I've been using the AJA with the standard sockets for about a year with no problems, (observing the AJA / video deck thing that I mentioned in my previous post.)
As to running the AJA with Firewire video decks / cameras:
I've had conflicting advice as to whether a PCI card for extra firewire sockets helps with firewire conflicts when using the AJA and a firewire video deck.
Some have said that the 400 and 800 sockets are on independent busses but again others have said that it may still get confused.
Some say that the PCI card is on a completely different buss and so will not be confused with firewire connections on the actual Mac, others disagree.
I prefer to avoid conflicts, (my life is complicated enough and I like to keep my edit suite in a friendly mood...) so I just run the AJA or the firewire DSR-11 deck.
As to normal editing once the material is digitised, then feel free to run your AJA on a 400 port and a drive on either a 400 or 800 port.
LEE.

NO IMAGE IN VIEWER

Just replaced FCE with Pro 4.0. All is well, until I try to play a clip in either the timeline (CANVAS) or a clip in the VIEWER screen. I have a firewire device attached,and the playback is good through the device, but the Canvas and clip VIEWER screens go blank when I hit the play button. In fact they turn solid yellow. When the image is stopped, the picture reappears. Sounds like some kind of REAL TIME vs. FIREWIRE conflict, but I can't figure it out. I even disconnected the DV CAmera and rebooted FC PRO< but I can't get moving images to appear on any of my viewers in the edit mode. What button have a forgotten to uncheck?

Perhaps a stupid suggestion, but have you tried whacking the 'W' key? It doesn't sound like your problem (yellow frames do sound strange), but it is frequently the reason for people not seeing moving video in either window. Worth a try anyway before you diagnose hardware probs.

Still shot with isight

Using Latest iMovie '08 (v7.1.1) with external iSight camera
After launching, and trying to use the isight camera, it opens window with a frozen photo, not real time action?
I've tried many things, which include trashing preference, reinstalling iMovie. Once in a great while, I will get real time window but the odds are for the frozen window.
Has this happened to anyone else?
PS: I just recently, erased my boot HD and reinstalled everything from scratch and eliminated about 50 GB of stuff that I will probably not miss. This may not be relevant but it couldn’t hurt the cause. Everything on my Mac is as UPDATED as can be.

Thanks for sharing the fix for your Firewire conflict, Nick.
Firewire hardware or software conflicts with external iSight are not uncommon. The explanation I have most often seen claims that the problem arises not from power limitations but from the sizable bandwidth required for video.
Cheers,
EZ Jim
PowerBook 1.67 GHz w/Mac OS X (10.4.11) G5 DP 1.8 w/Mac OS X (10.5.2) External iSight

How do I move existing Logic projects to an external hard drive?

My internal hdd is getting close to capacity on my iMac so i've purchased an external 500GB USB hdd.
I have about 10 existing projects that i'd like to move to my new drive.
These projects consist of WAV files imported from a portable digital recorder, fresh recorded tracks using my audio interface, and midi tracks. Most of my tracks are at the 'final mix' stage and are sounding pretty sweet
Would it benefit me to move my Logic projects to my external drive, or should I scrap the idea and move my huge itunes library instead? If it is worth moving my Logic projects - what is the best way to do it? I really don't want to have to remix, re-record anything. I also don't want to get lost in Finder.
I'm quite new to Logic but I intend to 'use best practice' if possible. I get the impression that using an external hard drive with Logic may offer performance gains. My audio interface is firewire (M-Audio FW 410). The USB external hdd was brought to avoid firewire conflicts.
Any tips would be most welcome.
Thanks in advance. Rich

In theory, you should be able to copy all of your projects to the external and open and use them exactly as before with no problems and no need to re-mix anything...
BUT, and its a big BUT...
Are you sure all of your projects were started AS projects with all the audio files, instrument samples etc. stored in the relevant folders in the project's folder?
Before doing anything, go through all of your "projects", make sure they ARE projects (there should be a project folder, the song file stored in the project folder, with audio, undo etc. folders within the main project folder for each one) - if they are not, do a "save as project" - it should give you a number of options to copy any external audio files etc. to the project folder. If for any reason it doesn't I would then choose "project - consolidate" from the main file menu, which will give you the same options. Even if you are SURE that all your projects ARE projects, I would choose "consolidate project" just to be sure...
You should then be able to proceed... but don't delete the originals until you are sure everything is working fine. I would even suggest backing up the originals in another location (it could even be a back-up folder on the same external), so you can just move them straight back to the original location if there are any problems.
When I first started using Logic many years ago there was no option to save projects, and I learnt the hard way to create the folder structure that logic now does for you. But even so, unless you started out knowing how to use this function, its possible some of your audio files are still stored in the wrong location. "Consolidate project" should solve this.
As for the USB HD - I would avoid using a USB drive for audio. It is said that USB 2 is faster than firewire 400, but I don't know any musician or film maker that would use one.
You can daisy chain firewire devices with no problems in my experience. If you do experience problems I might suggest you search up on any posts to do with M-Audio interfaces and Macs...
Good Luck!

Not enough disk space to render?!?!?

Trying to render my project, I'm getting the error message 'insufficient disk space for render - free up space before continuing'...
Thing is, I'm saving it to my external drive, and, at present, this has 310gb available!
Surely it won't need more than that?!?! I'm trying to resize the footage, about 25 mins of footage...

It sure sounds like your drive is formatted as FAT32.
Regarding the RAID setting, if you did not set up a RAID set, the 'settings' under the RAID button are irrelevant. And anyway, you wouldn't have a RAID set with a FAT32 drive, much less a single FAT32 drive.
I think you have two problems - 1) the drive is not formatted properly - needs to be Mac OS Extended and 2) your cam & external FW drive attached at the same time - I think you have a Firewire conflict between them.
But you have to fix the formatting first. Be sure to back up anything you need to keep because formatting will completely erase the drive.
Finally, not to alarm you, but regarding your internal drive, with only 4GB left you are dangerously close to crashing your system if that drive fills all the way up. You need to get stuff off that drive. You should really keep at least 15% - 20% of your system drive empty at all times. OSX needs that room to operate.

Isight causes Time Machine to stall

Hi everyone,
I've been struggling since getting Leopard to get Time Machine running. It has run intermittently for me, but usually just starts backing up and stalling after a period of time. I seem to have found a fix I thought I would post for other people struggling with this problem--if you have an old, external isight camera, disconnect it! It doesn't matter if it's actually "on" or not.
I realized that I used to have a similar problem with Carbon Copy Cloner, and taking the isight off fixed it in that instance, as well. I should point out that this problem has occurred across two different iMacs, so it's not likely a weird fluke. Something about the camera interferes with the backup process.
Cheers!
Tony

Good info, Tony!
If you are using a Firewire hard drive as your Time Machine backup device, my guess is that you are experiencing a Firewire conflict with your external iSight.
I am using one of my internal drives on my tower Mac for my Time Machine backups, and I do NOT share your problem while my external iSight is connected. Time Machine backups do pause while my iSight is active, but backups proceed normally with my iSight connected and on, even when iChat is open and connected to my iSight.
External (Firewire) iSight users who must use external drives for Time Machine backup might want to choose a USB drive as their backup device if they do not want to turn Time Machine backups off while their iSights are connected. Doing so would likely eliminate problem you experience.
Cheers,
EZ Jim
PowerBook 1.67 GHz w/Mac OS X (10.4.11) G5 DP 1.8 w/Mac OS X (10.5.1) External iSight

Aggregate devices and sample clock sync

Hi All,
Finally got the 2.8 8 core Mac Pro and am wondering how easy it is to sync multiple interfaces with sample accuracy. Would word clock be the route to take ?
Has anyone done this with 2 devices from different manufacturers ?
Btw, no cpu spikes here. Everything runs smoothly.... however , everything is all Apple.
Cheers !!

Hi,
I just had a terrible time with a TC Konnekt 24D on brand new MacPro. Let down by really awful drivers but a lovely piece of kit otherwise. How do the m-audio drivers fare? I'll be using it with a Yamaha 01v96 v2 mixer, world clock delivered through the lightpipe itself but there is also a separate connection.
Do you have firewire conflicts say with a FW iSight or FW Printer/Scanner?
30/03/2008 09:08:20 kernel ential FireWire workloop deadlock!
30/03/2008 09:08:20 kernel Naughty cmd is a IOFWCompareAndSwapCommand

Capture Issue

Hi.
I'm running an iMac with FCP with a 500 gig internal drive and have a Lacie 300 gig hard drive connected via firewire.
I can capture video from my XL2 to my internal iMac drive via firewire and have no problem capturing. However, when trying to capture video to my external drive (connected via firewire), the system freezes. Also, when theexternal hard drive is turned on, I can't see my preview video even when capturing to the internal drive.
1) Is this a firewire conflict?
2) What can I do to capture to my external drive? And, is it even necessary to capture to that drive. I do have a firewire connector to my external drive. However, of course, I won't be able to go through FCP.
My concern is I'm under the impression that I cannot, or at least should not, edit and capture video on the same drives as this could cause a crash.
Am I correct on this? Or, is it that I can capture on the internal drive, but have to save the project on another drive?
iMac Mac OS X (10.4.8)

http://discussions.apple.com/thread.jspa?messageID=3299225&#3299225
In your situation it may be best to capture to the system drive then close FCP. Move the captured files to the external drive then launch FCP and reconnect the media at it's new location.
-DH

Using iMovie6 with projects on external FW400 and FW800 drives ...SLOW!

Shouldn't iMovie6 work smoothly with movie projects stored on external Firewire 400 or 800 hard-drives?____ ...or am I expecting too much?!!
With the FW400 drive, the performance I'm experiencing is unacceptable. It's excruciatingly slow (even simply mouse/slider movements take forever) and the playback is so choppy, it's useless. (this is after converting an iMovie3 project to iMovie6 -- could this be a factor too?__)
Those on FW800 seem to work better (as they should) but even though the audio seems OK, the video playback is very jerky and it still takes a few seconds for it to respond to any mouse action.
Is FW400 simply too slow for iMovie?____
I presume USB2.0 would be just as bad.

Is FW400 simply too slow for iMovie?
Both types of FireWire drives should work fine. I'd look for another cause.
If your camcorder is a Canon, search the forum for how to avoid FireWire conflicts.
Otherwise, perhaps there's a clue here:
http://discussions.apple.com/message.jspa?messageID=1852869#1852869
Try resetting your FireWire ports? Disconnect all FireWire devices, do a Shut Down, disconnect your Mac's power cord from the wall outlet, wait 15 minutes, then reboot.
Karl

Firewire conflicts

Similar Messages

Maybe you are looking for