Camcorder & firewire issues

Hi have a new Mac Pro and I could IMOVIE HD could not see my camcorder untill I unplugged my 2 firewire drives. Are there any hints to why and how I can fix this?

Was it a Canon Camera?
http://docs.info.apple.com/article.html?artnum=61603
:)Sue

Similar Messages

  • Firewire Issues: External Hard Drives & DV  Deck Sony DSR 11 not recognized

    So, I have this brand new $6000 Mac Pro that will not recognize a simple DV deck, nor the external HD's.
    Thus, after spending seven hours searchig around last night, trying every configuration possible from updates, unplug power source, and everything else, I began making calls as of 4 am this morning.
    I was referred to FCP Europe where I was informed that I needed FCS friver updates. (unavailable for 1.0.1) or perhaps it was a Sony issue. The deck & drives work fine with my G4 & Powerbook G4. With six fire wire ports on the Mac Pro, and nothing being recognized via a single fire wire port, does anyone have a simple, expedient solution? Thank you.

    Ahhhh. Firewire issues. I'm convinced that these Macpros have some serious problems here. I am running a sony dsr11 also with a digi002. MY issues is bootup. . I have a mac pro with Tiger installed. My issue is I intermittently get a prohibitted error on bootup. The error looks like a no smoking sign without the cigerett. I have to re boot and sometimes the os boots right up othertimes not. I have sfound that I have to boot my sytem with noting hooked up first. It seems when you have high end firewire devices that the Bus just can't handle it. Real ****** for thos who bought the system for A/V work. Everything woks fine on my powerbook and my G5. Problem is with MACPRO! Do you also have other firewire devices hooked up? Are they daisychained together?
    Vito

  • CS5 support is falling down - the famous firewire issue

    As a loyal user of Adobe professioanl editing solutions for the last 10 years this past month has been a nightmare.  When I inquired about upgrading to CS5 from CS3 I was advised during an online chat with an Adobe person here on the site to upgrade to CS4 and because of the timing I would get a complimentary CS5 upgrade.  I purchased CS4 on April 14th and had so many issues it was never even used in the edit suite.  When CS5 became available I decided to cut my losses and decided if I was going to have to go through all the hoops I might as well only go through them once with CS5.  I have had numerous long discussions with Adobe "support" regarding various problems and now I am at the end of my rope.  Even though they say the are taking notes during our conversations each subsequent "support" person claims to not know most of the pariculars discussed in previous phone calls.  I didn't think I had to follow up each phone call with a note here but evidently that is the case.  Today I have a deadline to deliver content on TAPE to a national cable network and the series contract could be in jeapordy if I can't deliver the first of 26 episodes.  I CANNOT PREVIEW ON AN EXTERNAL TELEVISION MONITOR OR EXPORT THROUGH FIREWIRE TO MY MAIN DV DECK.  It is a deck I have used for YEARS with Premiere CS2 and CS3 and i NEVER had an issue like this.  I have been told repeatedly that the issue would be resolved and most recently on Tuesday of this week I was promised a callback between "1PM and 2PM" Central Standard time on Wednesday, THAT CALL NEVER CAME.  When I followed up with another call MOST of the days previous discussion was NOT in my case notes.  I was told my main Sony VTR and secondary JVC VTR were not HDV decks even though I have been using BOTH for many years for just that purpose and even though that didn't address the most pressing of all my issues which was just getting output through firewire to tape.  After a very frustrating call I was promised another callback "in an hour" by a "supervisor".  That call NEVER came.  Both Adobe "support" and PNY Quadro "support" claim that they have "never" heard of the firewire issue even though it is all over the forums at Adobe.  I will be posting this and every subsequent communication between me and Adobe on the forums, at Yelp and any other web sites that take reviews of professional video products.  For the record just some of my other issues include the inability to capture HDV from the Sony HDV deck I have been capturing from for years, Alpha Glow not working and no split screen when doing color correction in a number of effects where it is offered.   Also for the record I have tried turning off the MPE GPU acceleration to export to tape and that doesn't work either.  System is a Supermicro dual processor motherboard with lots of ram and a Quadro FX 3800 operating with 64 bit Windows 7.

    Read here:
    http://kc.flex-radio.com/KnowledgebaseArticle50433.aspx
    It may get firewire working again on your older deck with Windows 7.  If the solution on that page works, then the problem is down to Microsoft, not Adobe.
    FWIW, it's getting to be pretty well known around these parts that the current implementation of Adobe Customer Service is awful.  That said, several Adobe employees, including some Premiere Pro engineers, have been hanging out in the forums recently.  This is a big change from earlier releases of Pr, where an Adobe presence was rarely seen at all.
    These same folks have also said that Adobe is working to improve their Customer Service.  Like the inertia of a large ship forcing it to take a long time to change course, I suspect that it will take a bit longer for Adobe to make that improvement than it would for a smaller company.  Don't give up on 'em just yet.
    -Jeff

  • 10.8.4  update firewire issues

    10.8.4  update is not fixing the firewire issues that 10.8.3 caused with my macpro.  my printer (professional Epson)
    hard crashes when accessed.   I'm reporting this because there are many people having firewire issues with firewire
    printers and 10.8.3. 

    Use the workaround until the FW issue is resolved:  use a USB cable.
    OT

  • FireWire Issues - anyone else?

    Have a PB G4, 1.67, with an Apple-repaired logic board [from Nov 08]. After latest Security updates, I have had trouble connecting either 800 or 400 FW drives. I've tried them on an iMac and iBook; both work. Tried different cables, three different drives [2 OCW, one Verbatim]. Nothing works. Wiggled cables. Used both bus and external power.
    HELP please. I don't want to spend another $350 [plus postage from UK via APO] to fix this a third time [was a refurb, used from PowerMax, they looked at logicboard once, and then I used Apple's fix it service]. The Apple repair warranty expired in Feb 09.
    I might try an $80 cardbus FW800/400 if I can find one still.
    Thanks in advance.

    Frustrating trying to get it to work .... You can zap the PRAM as well as reset the PMU anytime. At this point, if you haven't go ahead and do the PRAM and might as well do the PMU again. Reset PRAM. Note the effects are immediate, there's no advantage to waiting overnight:
    1. Shut down the computer.
    2. Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
    3. Turn on the computer.
    4. Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
    5. Hold the keys down until the computer restarts and you hear the startup sound for the second time.
    6. Release the keys.
    It sounds like you may have had hard drive issues that Drive Genius fixed for you. For comparison, did you run the Disk Utility disk repair after Drive Genius fixed the hard drive .. just to see if Disk Utility gives the drive a clean bill of health?
    When you ran the Apple hardware test, did you run the extended test? Do you have either of the TechTool programs available? They do similar testing to the Apple hardware test, it would be interesting to see if they also say the hardware is OK.
    You've reloaded the operating system a couple of times. Did you use the combo update to update to 10.4.11? I prefer that to letting Software Update make the updates, as sometimes it doesn't update correctly. Repair disk permissions before and after the update, too. Then run software update to pick up any other required updates.
    You've, by this time, reset PRAM and PMU, I assume the PRAM reset didn't change anything? If so, sorry, but I don't know what else you can do. At this point, I'd take it to a genius at the Apple store, and get their opinion.
    I didn't address sleep as I think you need to resolve the Firewire issue first, then see if there is a sleep problem.

  • Quad-Core/Dual-Core Front firewire issue with VX2100 camcorder

    Hi,
    My VX2100 camcorder will not work (isn't recognized) by the front firewire port on my quad-core G5. The camcorder works on the back port, and I have tried this at the apple store on other machines, all with the same result. Has anyone else had this issue or can offer some advice? Other firewire devices and camcorder have worked fine (I have a canon one that works with the front).
    ikiris

    Well, I went back into Best Buy to test on 3 other laptops (2 Asus, and their floor model for this Sony). It seems to be doing the same problem so at least I was able to rule out broken hardware issue on my particular laptop.
    Here's what I did to test:
    Since I couldn't really install Adobe Premiere on their machines, I used the DVIO software (http://www.carr-engineering.com/dvio.htm) and a 5 min clip I captured.  I transferred onto their machines, hooked up my Sony D8, and attempted to play the video.  It would play for 15 seconds and then stop and jitter with a loud noise (like it does on my laptop).  I even tried changing each machine's firewire driver to the legacy one and same results.  I pulled a brand new 4 pin to 4 pin firewire cable off their shelf and still the same problem.
    I think I've nailed it down to Win7x64 bit Home Edition not playing nice with Firewire driver.  Very annoying.  I can't find any concrete evidence of this from other users on any of the forums that have my particular problem, but from my own testing, it's all I can conclude.
    I have 2 other things I can try:
    1.  Opening the laptop and looking at the firewire to maybe find appropriate driver (ugh, I don't want to have to open this thing up).
    2.  Upgrading to Win7x64bit Pro and possibly testing with XP on the new MS Virtual PC (http://www.microsoft.com/windows/virtual-pc/).  I can't do it with my Home edition apparantly.
    Who needs to view video on an external TV anyways....sheeesh...(scarcasm).
    Tim

  • Camcorder connection issues (not the simple type)

    Note: Also posted in OS and Hardware forums
    I have a Panasonic PV-GS400 camcorder that my Mac Pro refuses to recognize. First a list of what I have confirmed.
    1) There is nothing wrong with the camcorder (It will work with an iMac at my work running Leopard)
    2) There is nothing wrong with the cable I am using (Connected a friend's cam corder using it)
    3) There is nothing wrong with my firewire (I have a LaCie drive and have been able to interface to a different camcorder)
    4) I have reinstalled quicktime w/o fixing the problem.
    5) I installed my orig Tiger OS on my firewire drive and still see the same problem.
    6) Both iMovieHD and FinalCut fail to recognize the camcorder.
    7) All of my software and firmware is up to date.
    8) I have confirmed all settings on my camcorder (It worked with another mac)
    Now for the information regarding my mac:
    2x3GHz Dual Core Xeon
    OS X 10.4.11
    Model MacPro1,1
    Rom Version MP11.005C.B08
    SMC Version 1.7f10 (Don't know what this is)
    I appreciate any suggestions, there are only 2 things left to try (as far as I can see)
    1) New OS
    2) Try a Firewire 800 cable
    I have searched the net quite a bit over this issue and I feel I have done my homework with no success. I have also heard some disturbing comments / BS regarding certain camcorders "just not working" with certain Mac / PCs. Is this really true?
    Again thanks for any thoughts.

    I thought this initially myself, but when I had the other camcorder working with my mac I went through the following steps
    1) Use Canon Camorder (iMovie works, I can see the camera in the profiler)
    2) Plug in the GS400 and nothing happens (Can't see it in the profiler)
    3) Use Canon Camcorder again to make sure my cam is not killing the firewire and everything works as in step 1.
    Thank you very much for the suggestion, I also tried a 30 min reset a couple of days ago and no difference.
    Do you know if there are any firewire utilities for looking at plug in events and such?

  • New Mac Pro, Firewire issues

    I just purchased a Mac Pro and have only had it for a couple of days. I installed several internal drives and moved my data from my Windows machine to the Mac using a firewire drive. That went well, but the Mac could only read it as it was NTSF. I decided to format it as a mac drive (journaled) so I could use it to back up to. The Mac Pro will not format the drive. It fails the verify and repair. I hooked it up to my son-in-laws computer i-Mac and it formatted perfectly. I hook ti back to the mac pro and it is really buggy. Reads slowly and writes even slower. I again run the verify and it does not pass. Hook it again to my son-in-laws computer and it passes the verify. Is there an issue with my mac, or the operating system and firewire drives?

    This is the only firewire drive that I have, but my mini DV camcorder works fine, but that is a different cord. When I plug in the drive to my son in laws imac with the same cord, it works fine.

  • Firewire issue--Backup drive not found w/Time Machine after imac sleeps

    I've had a lot of problems with Time Machine on my G4 imac since starting to use it a month ago. I think I have isolated the problem:
    Time Machine functions properly while the computer is in use, and it has no problem after a restart or shut down, but if the computer goes to sleep and then TM runs its hourly backup, I get an error that it cannot find the Backup Drive. Once this happens, TM will no longer work until I've deselected the drive in TM, unplugged it, plugged it in again, and reselected the drive as the backup Drive. Sometimes this requires a shut down or restart too.
    Here's what I've tried:
    1. connected the drive via USB--it operated without a problem
    2. unplugged all devices from the computer, shut down, waited, 20 mins, restrted, plugged the external drive back in via Firewire--the problem persists as described above.
    3. deleted the TimeMachine.plist file, restarted--problem persists.
    I've read that the Firewire port can be reset with other procedures such as zapping the PRAM or updating the firmware. I've also read that new problems can arise after reseting the PRAM so I'm hesitant to do this. Can anyone shed some light on the PRAM option?
    I cannot find where the firmware updates are located on the mac site. Could someone point me in the right direction? I've looked under downloads and after searching, came up with a long list, but nothing was labeled clearly. Each listing mentioned firmware in the header, but it seemed to always pertain to a certain issue (eg. superdrive, or installing appleworks). I could not tell what was the most recent firmware released for my machine, and I fear installing something retrograde that will create new problems.
    If anyone has any thoughts on how to deal with the firewire problem, or if you think my issue with using a FW connected drive with Time Machine might be rooted with something else, please comment.
    Thanks!
    HM
    Message was edited by: imaginary_forest

    fzgy wrote:
    "Mac OS X can't repair the disk.  You can still open or copy files on the disk, but you can't save changes to files on the disk.  Back up the disk and reformat it as soon as you can."
    It's possible a heavy-duty 3rd-party disk repair app can fix it, but they're expensive (DiskWarrior is about $100), and there's no guarantee it can do it.
    Am prompted to reformat but I don't have a good understanding of what this means and how to do it.
    That will erase it.  See Time Machine - Frequently Asked Question #5.
    It sounds very much like the disk is beginning to fail, although it's possible there's a bad port, cable, connection or power supply (if it has its own).
    I'd suggest getting a new one, and using it for your Time Machine backups; once you have a good backup there, reformat the old one (and select Security Options to write zeros to the whole drive -- if that fails, you know the drive is toast).  Use it for secondary backups, per FAQ #27.   If it has failed, get a second new one for secondary backups. 

  • 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

  • Firewire issues with DV camera

    When connecting a Samsung VP-D305i mini DV camera to the firewire port (4pin to 6pin cable) Mac OS fails to recognise it.
    I know this is an issue that has been covered in this forum a few times, but none of the answers seem to work for me. Furthermore rather than get the "unable to list firewire devices" in system profiler, system profiler displays it as unknown device. The following is given as the detail:
    Manufacturer: 0xF0
    Model: Unknown
    GUID: 0xF000084139E5
    Maximum Speed: Up to 400 Mb/sec
    Connection Speed: Up to 400 Mb/sec
    Sub-units:
    Unknown Unit:
    Unit Software Version: 0x10001
    Unit Spec ID: 0xA02D
    Final Cut Pro and iMovie both fail to work with the device, however they do recognise that a camera has been plugged in. My MacBook Pro has the Texas Instruments Firewire chipset, is this not supposed to be the more reliable chipset?
    Flushing the SRAM doesn't work, I've formatted reinstalled Mac OS X, didn't work. The DV camera works fine through the same cable on my sister's MacBook. Furthermore, the DV port works 100% fine when booting my MacBook Pro, using Bootcamp, in XP. This port did work, I've used it before with iMovie in November last year. (with Bootcamp and Windows installed). Does anyone else know anything that may help?

    Is the sound mixer physically connected to the mac via firewire? Maybe just unplugging it will help; there is only one firewire bus, and sometimes the capturing you are trying to capture from needs to be the only device connected.

  • Camcorder Firewire problem

    Help! New iMac 24", 2.8. Firewire 800 has two drives attached, daisy-chained to another -- one is for video capturing / scratch disk, other is for time machine drive. The Firewire 400 port is used for my Canon camcorder. My plan seemed to me a good one. However, when I first connected my camcorder, my time machine drive seemed to unexpectedly "eject" itself, and a warning message appeared basically saying I did not eject it properly. Furthermore, and most disturbing, is that iMovie 08 gave me a "communication error" message and I could not import video no matter what I did. It did detect my camcorder and did seem to communicate enough to make the camcorder play video on its own lcd, but no video actually transferred to the Mac. I tried iMovie 06 and with some luck it seemed to work. That firewire port (400) has worked recently with a different hard drive. Interestingly, when I disconnected both of my 800 drives, the import actually worked in iMovie 08! Yet I need one of those drives as my scratch disk! When I reconnected my scratch disk, the import screen told me my camcorder was disconnected or off! What gives! Help! If it makes a difference, my time machine drive is actually a 400 speed drive daisy-chained to the back of an 800 drive which in turn is connected to my 800 port. Thanks in advance. Frustrated to say the least.

    Trouble is in the air Stevo and I can't help you. There is something critically wrong with the firewire system in our new computers! They apparently can read to/from most hard drives, but are leaving many pro and semi-pro users high and dry when it comes to supporting video cameras! I have a two-week old 20" iMac , a brand new Lacie Pro 1TB external triple interface and two Canon XL video cameras. With the Lacie connected via Firewire 800 and a camera connected via Firewire 400, we get a "VTR OK" prompt in FCP for a few seconds, then it switches to 'no communication'. The computer simply isn't seeing the camera properly because of a weak/faulty/cheap firewire system. We've tried to capture directly to our main hard drive without the Lacie connected, and every other permutation we can think of, with no success.
    iMovie and FCE will not see our cameras either (or our Panasonic camcorder) so I'm completely stranded with a brand new computer and external hard drive. New firewire cables were also tried, to no avail. Maybe Apple would suggest I buy new $6000 video cameras at random until I find one that hopefully works?
    As a home-based videographer, I am now shopping for an entirely new editing system that will NOT include Apple products at ALL. What a shame - I have completed hundreds of video projects using a G4 iMac laptop over the past three years without problems. Keeping Apple in my business venture has now cost me dearly - a $2000 computer that is completely useless and a growing list of clients that aren't receiving my video work. Apple would rather let its customers search for their own answers through vast forums than provide reliable computer technology or meaningful customer support. My affiliation with Apple computers should have stopped when my G4 finally died a peaceful death.

  • Firewire issues after upgrading to 10.6

    I mentioned this is a prior post, and have really still not got a resolution to it. I have a 1st. gen Mac Pro 2 x 2.66 dual core. I have encountered several disturbing issues using Firewire 400/800 devices on my machine after the upgrade. When I boot into 10.5, I have all the access and performance of my Firewire devices (a LaCie 1 TB external drive, A Sony CD/DVD burner, and a WD Passport FW 800/USB) All devices work in both USB and Firewire natively... but only work properly under 10.6 when using USB. All firewire access on my machine is sketchy at best under 10.6. The devices show up.. and mount.. but when I attempt to use/I.O to them.. the speed moves in bursts.
    For example.. copying a folder that is 5GB to one of the FW 800 HDs takes about 2-4 minutes on 10.5... and under 10.6 it bursts. When under 10.6, I get fast transfers for about 200-300 mb, then about a 5-10 minute pause.... then another burst of normal performance for 200 Mb. Then another pause. Taking an estimated 3-4 hours to copy a 5GB folder.
    In a test... I switched to the USB interfaces of these devices, and the transfers are fast as expected. (2-4 minutes, no pauses) Furthering the test.. the FW interfaces perform as expected under 10.5.
    Anyone else experiencing this? (I have tried resetting PRAM, and total shutdown etc.)
    Any assistance would be most welcome.
    Thanks!

    I have had Firewire problems since moving to 10.6. Some optical drives in an enclosure containing the Oxford 934 chip will not mount disks unless I pull the Firewire cable and reinsert it. They work fine using USB 2.0. The problem is a result of Apple's update of the Firewire drivers. The problem extension is
    IOFirewireSerialBusPRotocolTransport.kext
    Replacing this extension with the one from 10.5 causes everything to work properly. If you do choose to replace this extension, you may wish to replace all five with those from 10.5. Additionally, after making the exchange, repair permissions and restart so as to make sure the replacement extensions are properly recognized. You must repair permissions BEFORE restarting. If you restart and then repair permissions, the replacement extensions may not get recognized, even after a subsequent restart, and you will have to repeat the procedure.
    During permission repair, I received alerts that one or more of these extensions could not be used. I ignored the alert with apparently no adverse consequences.
    My Firewire only hard drives, and one Firewire/USB 2.0 hard drive seem to have no problem.
    K

  • Camcorder Compatibility Issues

    I have a Sony DCR-HC40 camcorder and USB cord, and I want to capture video onto my new Mac.
    I do not believe iMovie is compatible. Is there any way I can use this camera to upload the video?

    For a miniDV camcorder, you need to buy a Firewire cable. Sony calls it iLink. If that MacBook Pro is new, it will have a 9 pin firewire port (800), so you need to buy a 9 to 4 pin firewire cable.
    USB will not work to capture the video, but is used to take still pictures off of the cam's memory stick.

  • IMac firewire issues...

    Hi all
    I'm wondering, after having recent problems with using a Metric Halo Mobile I/O and a USB hard drive at the same time (massive latency issues, crackles, etc. in Logic Pro 7), if anybody has any more information on it.
    I read that there is only Firewire bus on the iMac that I have and that is the problem - is there any way around this or is my second Firewire socket just a waste of time when the Mobile I/O is connected?
    Any thoughts welcome! Or, of course, feel free to point me in the direction of any previous discussions I've missed.
    Thanks.
    Steve

    Most (all?) Macs have only a single Firewire bus, but that doesn't stop me, or others, from using a FW audio interface and a FW hardrive together.
    Your post says you were using a USB hard drive, that's totally different from Firewire.

Maybe you are looking for

  • Oracle12c SQL*NET blocked by Windows 2008 firewall - what is the correct solution?

    Hello, I have a question with regards to the SQL*NET traffic being blocked by the Windows 2008 firewall. This document shows that disabling the firewall can resolve the problem: https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=16677350

  • Resizing an image without AWT

    Hello, here is my question: I have seen many examples on the Web explaining how to resize an image in Java. All of them use AWT. The problem is, my application is web-based, hosted on a server without X11 installed. Now, I know from the Java2D FAQ th

  • Repeated applications in "Open With..." menu

    Hello, This is not an emergency or anything, but I hope somebody could help me with this. Whenever I 'right-click' a file and select "Open With...", a menu of compatible apps comes up. However, some apps are repeated in the list. For example, the men

  • Change in sales activity

    Hi All When i craete sales activity in VC01N,when i want to edit it will generate new number,for ex when i wnat change statuss of the activity it is generating new number how to avoid this regards

  • Error code 1 was returned by the audio driver :(  randomly!

    hey all! ive been getting this messege "error code 1 was returned by the audio driver" almost every time i try and merge tracks, bounce track in place, bounce region in place, or mixdown stereo regions per tracks. NOT when i do a real song bounce tho