FireWire broken since.....?

Anyone else got problems with importing DV via FireWire?
I do not know since when things got broken but last night I tried to import a DV tape via FireWire as I did many many times before. But iMovie does not 'see' my Sony cam anymore. I checked the FireWire in System Profile and it does not show my cam. I tried two different Sony cam's (dcr-tvr12 and dcr-hc44e) and two brand new FireWire cables. Nothing works!
What is going on? I do not understand where or what busted the connectivity

Here's a bit more info
I'm currently using Snow Leopard where my previous imports where all done in Leopard. Reading some fora I read that Apple stopped supporting FireWire400, I guess this could cause the problem.
Anyone having the same issue?

Similar Messages

  • I have a mid 2007 iMac w/ mac OS X Lion 10.7.5. My time machine (LaCie) is not responding through firewire port (since day one).  Did an update mess this up?

    I have just recently realized that my time machine has not backed up in a couple of weeks. I am using a LaCie external hard drive that I purchased with the iMac and has been plugged into the firewire port since day one.  When I try to establish a connection it only gives me airport utility.  When I look through network connections it shows that my fire wire is not connected or at least it doesn't find anything connected. 
    I have also been getting a start up disk message off and on that I need to close applications due to no more memory? (or something similar to that). 
    Just curious what might have changed.  Did an update re configure something? Are these two issues connected? 
    I have always loved my Mac for the fact that it just always worked.  I'm not super savvy with computers and the settings so I'm not the kind that just goes in to tweek things. This is the first real issue that I have had with it.  I would think that it was the fact that I upgraded to lion but I did that quite a while ago.

    Hello,
    It isn't the fw in Network you want o use or look at, that's for something completely different.
    My first suspect is the Power Adapter on the LaCie has gone.
    At the Apple Icon at top left>About this Mac, then click on More Info, then click on Hardware>Firewire, what is listed there?
    Reset the Firewire bus
    If your Firewire or USB isn't recognizing any device.  A solution which has worked for some whose hard drive became invisible in 10.4 was simply to follow these four steps to reset the Firewire/USB bus:
    1. Shut the machine down.
    2. UNPLUG the power lead to the computer and any firewire/USB drive or devices.
    3. leave it for 10 minutes.
    4. Connect back up and reboot.
    http://www.macmaps.com/firewirebug2.html

  • Asset Generator broken since recent update to Photoshop CC

    With this latest update to Photoshop CC, the asset generator no longer seems to support having masks on a folder - asset will NOT generate if this is the case. Seems the only work-around is to clip everything down to a shape layer, which is highly awkward. Is this a bug? Can it please be fixed? This used to work just fine and has only been broken since the most recent update.

    My team is having the same issue.  I'd love to hear about a fix to this.

  • Rendering of Arabic/Transliteration broken since upgrade to 29

    Hello,
    Mozilla Firefox 29.0.0 - 29.0.1, MacOS X 10.9.2
    Problem: Arabic fonts (Lateef, Sheherazade) as well as transliteration Arabic > Latin is broken since update to 29. They were fine before. This happens when loading pages from a database. The protocol uses 'mixed content' and there seems to have been an update in Firefox's handling of such content. However, even explicitly unblocking such content doesn't solve the problem (apparently, one has to deblock every single page or is there an option for an entire domain? Otherwise, this is a pain in the neck and completely impractical). Firefox 'chooses' to select encoding seemingly at random: View > Character Encoding > Unicode/Western. Unfortunately, this version of Firefox scratched the possibility to select default encoding.
    Now, the pages loaded do not declare their encoding. However, this was not a problem because FF would use Unicode (UTF-8) by default. Setting instead "Default for Current Locale" is obviously useless. That's where the problem seems to be. Why was the plain default option changed so that we have no longer access to it? As you will understand in mixed environments (using a variety of languages and keyboard layouts), 'default locale' is pointless. Any suggestions are most welcome.

    FredMcD. Thank you for the hints. I'm sure they help in most cases. It didn't solve my problem though. Normal websites work actually quite well, it's just the internal ones that have this problem.
    cor-el. Thank you also for your hints. I checked and I'm pretty sure that it's not a corrupt font. The problem, as I've mentioned, is that the server does not declare its encoding. This wasn't a problem as long as UFT-8 could be declared as fall-back. Now, as I've written, there is only the option 'Default for Current Locale' which doesn't help. I suppose either Mozilla puts back the older option or we have to do something here. Would love to post link but I'm not sure there is general access to our servers (probably not) but I'll ask.
    I attached an exampled of how the 'garbled' text looks. It's more than garbled there just no font 'resolution'.
    Thank you both again for taking the time to give advice. I think your hints will come in useful in general use of Firefox.

  • Mac Pros extra two internal sata ports broken since Leopard 10.5??

    I have a Mac Pro and according to xlr8yourmac.com and the newertech website, there are four sata ports for your hard drives PLUS an additional two more sata ports directly on the motherboard. Through a complicated and difficult disassembly, it is possible to dissect your mac pro and install their cable which they sell for about $30, and get at the rear of your mac pro housing connectors for these two internal sata ports. In short, it's nothing more than an extension cable that fits into a neat housing at the back of the mac pro. You can then plug up to two esata drives into those jacks and they are basically hooked into the macpro motherboard. I ordered this cable and it worked splendidly since 10.4.8 and for 10.4.9 without any issue (that I could tell). I was even able to raid them together etc etc. (edit to be clear I mean I had two Lacie 500Gb drives with esata, firewire 800, 400 and USB 2 on them).
    When I installed 10.5 it was all broken!! What a disaster. I can't use these drives on the firewire bus (which by the way they work fine on) because I am already tieing up that with other devices and drives. I need these extra two buses, plus they were **** fast before- I guess it's the same bus as the internal drives get.
    I have contacted Lacie - no luck - and also newertech, and did so again today, but so far no luck, and apple, no luck and even submitted a feedback request back when we were on 10.5.1 (just released at that time), and no luck. I hoped 10.5.2 would restore this functionality.
    I was told Apple do not normally go out of their way to kill unintended functionality but could this be the case on this occasion?

    www.xlr8yourmac.com its over my head but...
    A Copy of the April 23rd, 2007 news page post is below (in reply to eSATA Extender cables (w/PCI slot bracket) from Newer Tech for use with the 2 unused ports on the Mac Pro motherboard.)
    " this may be of some interest for your readers.
    From the Intel 631xESB/632xESB I/O Controller Hub data sheet:
    "Hot-Plug Operation
    Dynamic Hot-Plug (for example, surprise removal) is not supported by the SATA host controller. However, using the PCS register configuration bits and power management flows, a device can be powered down by software, and the port can then be powered off, allowing removal and insertion of a new device. "
    (I asked if he knew of any way to do that in OS X.)
    the SATA controller does support AHCI mode, which enables hot plugging (same as with the raid southbridges ICH6R - ICH8R which support hot plugging with raid drivers from Intel without Intel assuring this).
    But it does not support AHCI if the PATA port is used as in the Mac Pro. And without AHCI there is no way to do hot plugging.
    Using a SATA DVD drive may not mean AHCI is used automatically. The controller has to be switched from IDE to AHCI mode. Maybe the Mac Pro does it on startup or some EFI specialist can finds out how to do that.
    BTW Tiger can handle an ICH8R in AHCI mode on all SATA ports without a problem.
    Kind regards,
    Martin S. "
    Info/Tips on using Spare SATA Ports with Windows: (from Jan 15th, 2008 news page) This may have come up in the past and I'd forgotten it (don't own a Mac Pro yet) but in reply to a post yesterday (1/15/2008) on the Pioneer SATA Blu-Ray reader/Superdrive combo drive, a reader mentioned the spare SATA ports are not usable in Windows XP at least with the standard drivers with Bootcamp. (Most readers have used the ports in OS X although I've not searched drive db reports for anyone that mentioned using Bootcamp/Windows also. BTW - The spare ports are bootable for OS X use, as noted in this article - although drives are not shown/usable when booted from Windows with standard drivers.)
    (Update) Here's a reader mail w/tips on using the spare ports with Windows via a replacement chipset driver install and grub bootloader edit:
    " after finding this thread in the onmac forums I finally was able to get my pioneer sata drive to work under bootcamp. Basically you have to do the following:
    - Install Win XP and ubuntu linux with a pata dvd drive in XP, change the ide 2680 driver to the intel ahci driver found here (downloadcenter.intel.com) S5000 Based Server AHCI SATA Storage Driver for Windows.
    - Boot into ubuntu and change the stage1 file of the grub bootloader to this:
    http://www.olofsson.info/grub/stage1
    This keeps the mac pro in ahci mode when booting a foreign OS
    Now you can boot windows using the linux partition, this will start grub and keep the mac pro in the correct mode
    I also installed Refit to make things a little easier but as far as i know using Alt key when booting should work too.
    if anyone tries this and has any questions feel free to ask
    -Forrest"

  • Weird Firewire Issue since 10.5.6 update

    Hey guys!
    I'm a musician so I use an audio interface (Presonus FP10) to record my stuff. It's a firewire interface and it used to work perfectly fine.
    However, since the 10.5.6 update there seems to be something wrong with my firewire port and I haven't found anything on the web that fits my problem.
    If I plug in my interface into the firewire port, it doesn't work. It neither goes on nor is recognized by the OS.
    Although, once I plug in my ethernet cable for internet access, it works fine.
    Problem with this is that in my music room there is no possibiliy of pluging an ethernet cable.
    I hope somebody can tell me what to do in order to get this fixed, whether this problem is caused by Leopard or by my interface.
    Thanks,
    Mark

    That was my first guess, too. See, that's what makes it all so weird:
    I have the device plugged in with no other cable. Nothing happens. I have the ethernet cable plugged in without anything connected to that. Nothing happens. I then plug it into an internet router ét voilá! It works...Could it maybe be a lack of electricity coming from a damaged AC-Unit connected to the device?
    But then again, it all worked fine up to the 10.5.6 update. Did the apple people do something to the firewire driver?I hear the new Macbooks come without Firewire...

  • Mail is broken since 10.8.2 update

    I updated to v 10.8.2 two days ago, since then Mail has been broken.  I can see the sender, date, a snippet of message in the in box column but cannot read the message if I attempt to highlight it or click to expand it. It is completely blank, no sender, no date, no subject line. I can read the message if I opt to return the mail, however, mail shuts down "unexpectedly" after I type five characters, an error box comes up to advise the problem will be reported to Apple and gives me the option of reopening. Reopening only makes the ugly cycle begin again.
    I have attempted turning off mail and restarting it, taking all accounts offline and then bringing them back up, shutting down computer completely and go through regular start up, using restart. I attempted to copy the the area of the error message to be of better assistance but it was gone before I could click copy. It says 'Terminating app due to uncaught exception' and 'could not find our own bundle'... "throwing an exception".
    Seems to be having a fair sized hissy fit, any patch to fix this bug or do I just deal with the inconvinience until the next update and hope for the best?
    K-

    Please ignore irrelevant responses to your question. Mail is at least as good as any other mail client for the Mac platform.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    Step 1
    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
    View ▹ Show Log List
    from the menu bar.
    Enter the name of the crashed application or process in the Filter text field. Select the messages from the time of the last crash, if any. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V).
    When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
    Please do not indiscriminately dump thousands of lines from the log into this discussion.
    Important: Some private information, such as your name, may appear in the log. Anonymize before posting.
    Step 2
    Still in the Console window, look under User Diagnostic Reports for crash reports related to the process. The report name starts with the name of the crashed process, and ends with ".crash". Select the most recent report and post the entire contents — again, the text, not a screenshot. In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.) Please don’t post shutdownStall, spin, or hang logs — they're very long and not helpful.

  • Time Machine backup problems with firewire 800 since Mavericks

    Since I installed Mavericks about a week ago, I have had problems with TM not working with my LaCie external drive. At best, it would not back up when the mac was awakened from sleep mode and in use.  When I would open time machine preferences, I would see the "preparing for back up" prompt that would last forever. Not only was it doing that, I have found that it would freeze my mac. I figured this out when I was not able to get my mac to respond from the login screen. It was basically frozen and couldn't log on.  I noticed the back up drive light flickering but nothing would happen even with waiting a long time. I finally figured out that shutting off the TM EHD would unfreeze the mac and it would start functioning normal again. This was happening with my external HD daisy chained to another external drive that contains my iPhoto, iMovie and Itunes files. That drive was also connected to the mac using firewire 800. I tried many different configurations, switched the order the drives were daisy chained, tried different cables and even directly connected the TM drive with firewire 800 to the mac, but the problems still persisted. The strange thing is that when I connect the TM drive through USB, it works flawlesly and no hanging up of the computer. Thats what Ive been forced to do. I have my other EHD connected directly through firewire 800 and it works fine. I only have one firewire 800 port, and since it works fine with my other LaCie drive, it makes me think its not the port or macs hardware? I can only guess this is a Time Machine issue or something wrong with my TM drive?  I have been in contact with LaCie and given them all these details but I have not heard back yet on what they feel the problem is. I thought I would post this to see if anyone else had some experience with this problem.

    Forgot to mention I did that. Completely erased and reformatted HD and then reconnected to TM. Didn't help. I did have the mac hang up while installing Mavericks and had to eventually shut off the external drive. It did that to me the firs time I tried to install Mavericks and I lost all my data because it did a clean install after that. I had another back up on CCC so I just restored from there. This time the update to Mavericks transferred my data. I have had TM hang up my mac in the past on occasion, but I was always able to shut down the drive and then the mac would return to normal. Perhaps I should try to erase and reformat again?

  • Is Firewire broken in 10.4.9 (Intel)?

    My iPod photo, that has been connected to my Intel iMac 1.83, 2 MB RAM for nearly a year, became unreliable upon the OS X 10.4.9 and iTunes 7.1 update. Syncing with iTunes and copying files to and from the iPod in the Finder became unreliable, with lots of beach balls.
    The Firewire cable was used with PowerBook G4 with no issues. An USB2 cable was introduced into the Intel iMac and it works fine.
    Restoring the iPod to factor specs had no effect.
    About the only test I have not tried (that I can think of) is bringing another FW device onto the iMac as I do not have one handy.
    Do I have a software issue? A hardware issue? Any thoughts?

    I have had the system hang on an Intel iMac running OS 10.4.9, with latest Security Updates, after importing an image into Photoshop CS3 via firewire connection to an Epson scanner. No problem previously with the firewire scanner on an iMac G5 running OS 10.4.9. Since everything was more or less updated at the same time, not sure where the problem lies. The scan is complete and just as the image opens in Photoshop, the system hangs, and Force-Quit doesn't work. The Force Quit dialogue box shows 'Photoshop is not responding'. I've had to manually shut down the system by holding the power button down. This has all happened within the last few days, and the issue appears intermittently--some scans complete normally.

  • Aperture RAW profiles broken since 10.7.4 update

    Since updating to OSX 10.7.4 last week it seems to have broken some of Apertures RAW profiles for some cameras.
    My Nikon D700/D300 files are all fine but my RAW files for my Lumix GX1 are green!
    I also get the message "This Photo was adjusted using an earlier version of Apple's RAW processing" and then it offers me the option to Reprocess.
    This fixes the green issue but doing this file by file when you've imported over 100+ is a real pain. The RAW for the GX1 was supported and was working fine before updating to OSX 10.7.4
    Any ideas whats going on?

    See this support article: list: http://support.apple.com/kb/HT4757
    The support for the gx1 seems to have been moved directly into MacOS 10.7.4, and for Aperture this is a change of raw support.
    Regards
    Léonie
    P.S: Perhaps this will help:No guarantees, I never tried it:
    Re: This photo was adjusted using an earlier version of Apple's RAW processing

  • Firewire problem since upgraded to 10.4.3

    Hi there,
    since I have upgraded my iMac G5 to 10.4.3, it is no longer recognising my external Lacie firewire drives. These work fine as I have tried them on a machine running 10.4.1, and they worked fine on the iMac G5 before I upgraded to 10.4.3
    The iMac powers the devices but they do not mount or show up in disk utility or apple system profiler...
    any ideas?

    Robert,
    Take a look at this thread:
    http://discussions.apple.com/thread.jspa?threadID=260074
    Also, which update method did you use when you went to 10.4.3? Did you use Software Update or did you download the update from Apple's website? Some users have reported a resolution of Firewire problems by downloading and installing the 10.4.3 Combo Updater from Apple. You can do this even thought you are already at 10.4.3.
    Regards,
    Steve M.

  • Firewire problem since 10.4.6 upgrade

    none of my firewire drives show up since 10.4.6 upgrade if i connect through usb they do what do i do to get my firewire back. can i some how go back to 10.4.5?
    [email protected]

    they work with usb2 yes i was stupid and didn't disconnect the firewire drives during the update but they weren't turned on either. The package i upgraded with was about 45 mb i see there is a 10.4.6 upgrade combo at about 140 mb when i get to a high speed computer connection i'm goin to try that with the drives unhooked. i've already tried this with the 45 mb one and nothing also reset pmu

  • ITunes is completely broken since the last update!

    Since the last time I updated both iTunes (10.4.0.80) and iOS (4.3.5) on my iPod touch, I can't do anything!! 
    Every time I open iTunes, i eats up 50% of my CPU while Mobile Device Manager eats up the other 50%.  This is the case EVEN WHEN THEY'RE NOT DOING ANYTHING!!  I don't have enough CPU left to back up or sync ... no that there's anything TO sync since I can't access the Store.
    When I click on the link to go to the iTunes store, the program tries for 15-20 seconds, then just gives up and leaves me staring at a blank page.
    Does anybody have any idea what's broken and how to fix it?  This is on Windows 7.

    Thank you Ed for your reaction.
    At home with version 8.0 there is a artwork tab. At work I have version 8.1.1.10 and there is if I do it the way you discribe only a place to drop the jpg. if I select the whole album. After dropping the .jpg it apears in the square but after clicking OK the .jpg wil not apear in the library. I'm doing this for years without any problems. I can't get it.

  • Sky+ HD box broken since recent software update? what to do?

    I'm going round in circles...SKY+ box now is not working since software update !.. I've been on the phone and online chat about the broken sky box ( account and box approx 3 years old ).  I spoke to someone on chat who re-negotiated my package "cheaper" which was very nice but a bit pointless without a working sky box...was advise he would transfer me to different department to discuss replacement of the sky+ box, got through to other department and they had no idea why I'd been put through to them had no record of my previous conversation .. and unable to help!.. Yes I'm now getting agitated !.. phoned 03442 414 141 instead, on his advice and they said we can give you a new sky box for £214.00 ! , or get multiroom? for another £11 a month?? not helping ... annoyed as prior to the sky software update the box wasnt the problem !... Ive been then trying the fix by following the solutions online to still be in the state of amber light and no sky TV.... it then directs me to an engineer call out at £65.  Who apparantly will either fix the old box ( until the next time ) or replace it with a refurbished one ? Obviously looking on e-bay etc you can buy boxes for between £10 to £40 ...feel annoyed why as a customer for well over 14 years I'm being shoved away at a massive cost to myself. Oh and look... a new customer could potentially have £125 from being recommend via friend, TV or Tesco /M&S £100 voucher... I'm annoyed and what do I do next ?.....

    Same problem for me, 1TB Sky box. Box updated on the 22nd of July 2015. Scheduled recordings now do technical fault 7 (33) picture breaks up on play back, but not all the time. Others fail with fault 10. Done the full software, re-download (backup and switch on), new install, planner rebuild. Even down to a full system reset. All other features work. On demand works only if I let it download to 100%. Try any sooner and TF7 (33) faults again. All I can think is the update is causing excessive CPU usage. Call out this Sunday bringing a reconditioned box. So if it's same 1TB and same EPG I might get the same problem. I'll post more after the engineer had been.

  • Mac G4 external firewire broken

    I've recently encountered this problem which caused me to lose a lot of data. The setup is mac mini g4 + external firewire hard drive from Freecom.
    What is happening is that read/write operations do not result in copy fidelity. Here's a terminal log to illustrate:
    ariel:Freecom FW 1TB kaitlin$ cp another.avi another1.avi
    ariel:Freecom FW 1TB kaitlin$ ls -lh another*
    -rw-r--r-- 1 kaitlin staff 176M 2 Sep 11:48 another.avi
    -rw-r--r-- 1 kaitlin staff 176M 2 Sep 12:07 another1.avi
    ariel:Freecom FW 1TB kaitlin$ md5 another.avi
    MD5 (another.avi) = 6eedf37d80b81f61f0c4a8f71dfea57c
    ariel:Freecom FW 1TB kaitlin$ md5 another1.avi
    MD5 (another1.avi) = b8cffac964d494279a508f11151ee529
    So basically the original and its copy have different hashcodes which means they're not the same file, so I can't trust the firewire. It does this consistently with any file read/write operation to/from any destination. The machine does NOT behave like this with external USB drives or the internal drive.
    I've got two computers, both G4 1.5 GHz of the same era (Mac mini and Powerbook 15"), and the same symptoms appear on both machines, as well as when hooking the drive up to a FW800 port.
    I tried connecting the drive to a friend's Intel Mac Mini, and it does NOT exhibit this behaviour. So I'm suspecting it's a recent software update that caused the drive to fail, since I have used the same firewire disk for a few months without any problems.
    My question is, has anyone else had this experience? and if so, is there a fix?

    This problem seems to be with Mac OS X 10.5.8. I've reinstalled a clean Mac OS X 10.5.0 and the issue doesn't occur.

Maybe you are looking for