PS CS6 / Firewire / Issue

MacBook Pro / 10.8.2
I have now noticed that when my Western Digital external firewire is connected, PS will open an image but most of the options are greyed out. I can't work with the image.
When I eject the WD drive, PS works.
Has anyone run into this issue?

you dont state the obvious - why
how did you format the FWHD
did you Disk Utility> Repair Disk on all drives
is Photoshop set to use it as scratch disk
how much free space (how many GB drive is it)
are you working off it
did you try rebooting...

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.

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.

CS6 installation issues on my desktop, but not my laptop?

I recently purchased CS6 Production Premium, and am attempting to install it. I've installed Premiere on my laptop, as that and Affter Effects are the only programs I would conceivably need on it; the bulk of the programs are for my desktop computer.
However, upon attempting to install, I get the "Installer failed to initialize" error. I know that there are questions relating to this already, but I feel that the two-computer scenario gives me enough info that the issue should be significantly narrowed down.
If it helps, here are the potentially-relevant differences between the two computers:
1) The desktop is 2009 and originally ran Vista, but now runs 7. The laptop is newer and runs 7.
2) The desktop already has Adobe Flash CS3 installed; Flash CS6 is incidentally included in this new package.
I'm kind of expecting that the presence of Flash CS3 is the main impediment to installing, but that's speculation on my part. Any thoughts on the issue? Would uninstalling Flash CS3 resolve this?

I checked my specs, and everything seems to be fine. The only things it doesn't meet are the recommendations for Adobe SpeedGrade, which I don't plan on using.

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

Windows 8 Release Preview/Photoshop CS6 Licensing issue

I bought and installed Photoshop CS6 on Windows Consumer Preview and it worked flawlessly. I then installed Windows 8 Release Preview. This had to be a clean install. I didn't know I had to deactivate Photoshop before doing the clean install. Installed without a problem. Now when I try and run CS6 it says that the license has expired. I have done all the web and Adobe support told me to do but still has the same issue. Other than waht this article says: http://helpx.adobe.com/creative-suite/kb/error-licensing-product-expired-cs4.html Adobe support isn't interested in helping.
Can anybody help?

I do know there's at least one person on this forum who is using Windows 8 (Kelly is I believe his name) and has gotten Photoshop activated properly.
I've been testing Windows 8 for the past several days (in virtual machines). Microsoft has actually made it worse to use in the release version. They've completely removed Aero Glass, for example, so now everything just looks flat and lifeless. I've written a book that describes how to configure and augment the OS so as to get work done with it. But I'm not sure people are going to want to upgrade to it wiith it looking this bad!
Have you tried removing Photoshop CS6 and using the Creative Suite Removal Tool to clean remnants of it up, then reinstalling? I'm sure the telephone support people would have suggested that; I'm just confirming.
Only thing I can imagine is that Windows 8's UAC system is somehow getting in the way of Photoshop retaining its activation data. It's no longer possible, using the Windows 8 UI, to completely disable UAC, though it is still possible to do it through registry manipulation (something best done by power users and system gurus). If one does apps will no longer run in the "UI formerly known as Metro" - which suits me fine, but may not be good for most folks.
Have you tried running the installer As Administrator?
-Noel

InDesign CS6 PDF Issue: Unsearchable PDF document

Hello all,
I have an issue that I've exhausted with days of Google searches. I have a text catalog created with ID CS6. Sections were PDF documents given to me from our engineering department. The book was created, exported and all went well until I found out that when I try to copy and paste the text into Microsoft Word or Note Pad, I get a lot of small boxes in place of the letters. When I try to search the text in Adobe Reader, I can't find words which I can see are there.
This is the first catalog I've created in CS6. Previous catalogs created in the exact same manner in CS4 & CS2 do not have this issue. I thought it could have been the infamous Arial Narrow font issue and researched that to death.
Any ideas would be most helpful. This is a 1300 page catalog that customers cannot search.

1. LAUNCH Adobe Acrobat
2. Using the File menu, OPEN the corrupted document. (I don't know what to do if you're not even able to open the file. Sorry!)
3. (VERIFY that Acrobat can't search the document, in case you haven't done so, just to avoid unnecessary work.)
4. EXPORT: Once the document is open, use the File menu again, and choose EXPORT / IMAGE / PNG. Your corrupted pdf will be saved as a series of images with the file extension ".png", one for each page of the pdf document. Don't worry, they will be numbered automatically by Acrobat, and they aren't terribly large. My document was 200 pages long, so I got 200 little image files in .png format. The export may take a couple of minutes. You won't get any further signals from Adobe to tell you it's done--just go look in the directory that contains the original and see if it made png files with names like:
chemistryBook_Page_001.png
chemistryBook_Page_002.png
5. COLLECT: Once you have the image files, collect them all by cut and paste into their own directory.
6. OCR: Under the Document menu, choose OCR TEXT RECOGNITION / RECOGNIZE TEXT IN MULTIPLE FILES USING OCR
7. ADD FILES: You will be shown a dialog box with the title "Paper Capture Multiple Files" with the subtitle "Run OCR on a set of images. There is a button that says "Add Files". Click this button, choose ADD FOLDERS, and browse to the folder that contains your png files. Highlight that file, click OK. The files will then appear within this dialog box. Make sure that the files are in the proper order, or you will be sad. Click OK.
8. CHOOSE OUTPUT OPTIONS: Now you will get a dialog box entitled "Output Options". You have several choices to make here:
TARGET FOLDER: Click "Specific Folder", then Browse to your folder full of images, click "Make New Folder", name the folder (something like "CHEMISTRYBOOKIMAGEFILES" so you can find it easily and know what is in it, click OK.
FILE NAMING: Click "Keep Original File Names". This will preserve Acrobat's automatic numbering of your files--you will need that to get the page ordering right! UNcheck "Overwrite existing files" just to avoid a terrible mishap, unless you are very pressed for disc space or unless this is your 5th time attempting to follow these instructions and you've already got 'way too many duplicates of the output files. If you have the disc space, just make new empty folder for your 6th try.
OUTPUT FORMAT: Select "Save File(s) as Adobe PDF. Click OK.
Now wait for Adobe to execute optical character recognition on the image files. Its output will be one little pdf file for each little image file that it OCR's.
9. COLLATE THE FILES INTO ONE: Under the File menu, select COMBINE / MERGE FILES INTO A SINGLE PDF. This step is optional; maybe you wanted a bunch of little files, or maybe you wanted to divide your enormous original document into 2 or 3 more manageable documents. To divide the file, just make a separate directory for the png files you want in each smaller final document, and repeat steps 6 through 9 for each directory. BE CAREFUL WITH NAMING! Make sure you choose a unique name, because if you got something wrong, you will want to be able to go back to your original corrupted pdf and try again. If your original is named "CHEMISTRY.PDF", please remember to name this new file something like "CHEMISTRY-FIXED.PDF".
If you really despise pdf, you can try using different output formats in Step 8. I do hate pdf, but I chose pdf for two reasons: one is that I had more confidence that that pdf would retain important features like charts and graphs and labeled photos in my document. The other is that I was so so so so SO tired of doing all this pdf crap instead of the chemistry work that I'd gotten the ebook to help me with that I didn't want to do anything fancy with file formats at this point. Let me know if you try output to rtf or ascii and get good results.
10. TEST: Open the merged document(s) in all of the pdf readers and web browsers you will want to use with it, and try searching with it. Use your file browser and try to search for text in the directory with a word you know the file contains. Searchable? Good job, you're done, cheers!
Not searchable? Oh noes! Check that you opened the correct document (maybe you opened the original by mistake). Try the entire process again. If that doesn't help, try the entire process again, but output to plain text this time. My apologies, but, being a complete newbie myself, I have no further advice on this topic.
NB! My output PDF is of rather low quality. It looks like it was literally scanned from a 10th-iteration paper copy. Don't know how to fix that, after the fact or somewhere in the above process. It's good enough, so I'm just dealing with the shakey blurriness. I seem to remember somewhere that I could choose a high quality output, but, again, I didn't want to do anything fancy with vectors and rostering and layers and other terms that I don't know before I verified that I could do something basic and get back to chemistry asap.

Adobe Bridge CS6 File Issues

Hello all, I just upgraded to the Creative Cloud on my PC, downloaded PS CS6 - Bridge and Camera Raw. I'm configuring and working with CR2 files, no problem, however, Bridge will not let me delete, rename or update the metadata of my jpgs.
Any suggestions?
Captain

Curt, I'm running Windows 7 with 4 GB RAM - mother board won't support more than that. I don't think permissions is the problem - same internal drive and the .CR2's work fine. I can delete bad ones, batch rename and update the metadata no problem, it's just the jpegs.
OK, I have the same setup on another computer - same Bridge version, no problems with the Jpegs. Issue here is, it's the backup computer and not my digital processing one with all the necessary drives.
Both computers are running Win 7 SP1 with 4 GB RAM 3.0 GHz processors. Only difference is the digi system has 2 monitors.
Where would I check about "Read Only" for just the jpgs?

CS6 Firewire 16:9 preview is letterboxed on widescreen monitor

With CS6, is there a setting to fix the Firewire Preview since the 16:9 video is incorrectly letterboxed on a widescreen video monitor? It is basically letterboxing something that doesn't need to be letterboxed.This is for a 1080 24p AVCHD project with 1080 24p video files.
Adobe Encore & After Effects CS6 properly dsiplay the Firewire Preview on a widescreen monitor.
In Encore, there is acctually a setting in the Preview Menu that lets you change the TV Mode from 16:9 to 4:3 Letterbox. That only affects the preview when choosing to the Preview the DVD. When playing the video from the Timeline or clicking on a DVD Menu that setting doesn't change how the Firewire Preview displays and is always 16:9. Premiere is always 16:9 letterboxed.
Any suggestions on how to get Premiere to display 18:9 using Firewire Preview without letterboxing it?
Randy

I checked it using various Firewire devices but they all act the same in this situation. Pioneer DVD recorder, Sony DV camcorders.
The unique thing with Premiere CS6 compared to CS5.5 or earlier versions is that it allows Firewire previews with the Mercury GPU on, it doesn't force you to turn that feature off and use the Mercury Software setting instead which is lower performance if you have the proper video card.
I just checked it using Premiere CS5.5 and it does the same thing. In 1080 HD Sequences, Firewire out has the 16:9 incorrectly letterboxed, or what I call "double" letterboxed.
With both CS5.5 and CS6, the Firewire preview is correctly displayed in a DV 480i 16:9 Widescreen Sequence.
A little annoying but this is where an old Sony PVM 4:3 broacast video monitor works well in combination with a widescree 16:9 video monitor still. Simply turn off the 16:9 mode and it will dsiplay it correctly when editing an HD Sequence. When using a DV widescreen Sequence you would then click on the Sony PVM's 16:9 mode so it would letterbox correctly.
Surprised Adobe didn't fix this in Premiere CS6
Randy

Photoshop CS6 Raw Issue

I am unable to open a RAW file from my Nikon D7100 DSLR camera in Photoshop CS6. My version of Photoshop CS6 is 13.0.1.2. My camera raw version is 8.1.0.43.
Is there a solution to tis issue?

Have since gotten direction from Adobe Support. As long as I upload camera images to my computer using Adobe Bridge, there is no problem opening any Raw files in PS CS6 or Camera Raw.

Adobe Bridge PS CS6 Update Issue

Using Windows 7, I am able to open RAW files into Camera Raw but since I bought a new Canon camera (6D) I can not open these Raw files. I went to the update menu and I get a "Update Server not responding" message saying to server might be down temporarily or I have to check Firewall/internet settings. Now I'm lost and frustrated. Any help would be greatly appreciated

Sign in, activation, or connection errors | CC, CS6, CS5.5
http://helpx.adobe.com/x-productkb/policy-pricing/activation-network-issues.html

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.

PS CS6 / Firewire / Issue

Similar Messages

Maybe you are looking for