Bridge doesn't display and generate RAW previews right

Hi everybody,
1. problem:
Bridge doesn't load the prewiews of RAWs, just if I click on the picture. Before, it loaded the miniature pictures within a few seconds. We didn't change any settings.
2. problem:
Bridge doesn't display DNG formates right (see picture). CR2 (Canon) is shown right.
Informations:
- Win 7 Professional 64bit, Photoshop/Bridge CS6
- Photoshop/Bridge doesn't need updates
Help badly needed...!

Since FLV are similar to other video files I suggest you read thread #7 of the following post and see if any of the suggestions help.  Perhaps the G spot program would tell you what codec you need and if it is installed on Bridge.  Beyond that I know nothing.
http://forums.adobe.com/thread/557614?tstart=0

Similar Messages

  • WEB.SHOW_DOCUMENT sometimes doesn't display the generated PDF file

    Hi all,
    I'm using the following code to generated my report from Forms:<br><br>
    V_REPORT_ID := FIND_REPORT_OBJECT(V_REPORT_NAME);
    V_REPORT_SERVER_JOB:= RUN_REPORT_OBJECT(V_REPORT_ID,P_LIST);
        V_JOB_ID := substr(V_REPORT_SERVER_JOB,length(:GLOBAL.REPORTS_SERVER)+2,length(V_REPORT_SERVER_JOB));
        V_REPORT_STATUS := REPORT_OBJECT_STATUS(V_REPORT_SERVER_JOB);
    LOOP
       IF V_REPORT_STATUS = 'FINISHED' THEN          
          V_TMP_PDF := :GLOBAL.APACHE_HTML_FOLDER ||'rpt'|| V_JOB_ID  ||'.pdf' ;
         COPY_REPORT_OBJECT_OUTPUT(V_REPORT_SERVER_JOB, V_TMP_PDF );
        WEB.SHOW_DOCUMENT(:GLOBAL.AS_HOME_URL ||  'rpt'|| V_JOB_ID  ||'.pdf' ,'_BLANK');     
        END IF;
    END LOOP; <br><br>
    Everything works fine except the WEB.SHOW_DOCUMENT part. In some clients, this command does what it required from it and opens a new browser window with the PDF report displayed on it. In some other clients, this command does nothing: now window dispalyed. When I refer to the Application Server, I see the PDF report successfully generated there. When I put the URL of the generated report manually in the browser address, I can see the report.
    <br><br>
    <b>Why the WEB.SHOW_DOCUMENT doesn't display the generated PDF report in some clients?</b>

    I agree with the previous 2 posters.
    Also firefox and ie handle it differently. Make sure you test on what your clients use.
    Sometimes acrotray.exe is completely retarded and doesn't work.

  • HTML doesn't display after generating the HTML files.

    There don't seem to be any errors during the generation of the HTML help project, but when I view the results, the content doesn't display and the window displays the following:
    Navigation to the webpage was canceled

    This sounds like you are running the file on a networked drive. Read this link.http://www.grainge.org/pages/authoring/chm_mspatch/896358.htm. If not, can you post an image of what you are seeing.
      The RoboColum(n)
      @robocolumn
      Colum McAndrew

  • After Installing Logic Pro X, my Logic Pro 9's 32-bit AUs don't work. The 32-bit bridge doesn't open and run either in my Logic pro 9. My 32-bit AU plugins are crossed out. Help?

    After Installing Logic Pro X, my Logic Pro 9's 32-bit AUs don't work. The 32-bit bridge doesn't open and run either in my Logic pro 9. My 32-bit AU plugins are crossed out. Help?

    michaelvee wrote:
    As an overworked professional, I simply have to consider the very viable options out there. Never thought I'd be seriously considering a Cubase product.
    It's a Steinberg product, not a Cubase product.. in case you haven't been paying attention Steinberg developed the virtual instrument for use in it's programs way back in Cubase 3.55.. the plethora of virtual instruments and the advent of low-latency drivers can be directly traced to Steinberg/Cubase development.. Logic also borrowed Cubase's arrange page format back in the 1980's. Cubase has borrowed from Logic to be sure but Steinberg has long been an innovator for many of the things we take for granted today. It was Logic/Emagic who licensed the VST technology and ASIO low latency format to use in Logic 4.xx. It was Apple who adapted VST to it's own AU format. Also, Cubase and Nuendo have undergone a lot more innovation over the past three years, Yamaha has been good as a parent company. Cubase is not Nuendo's little brother by the way, they are very close, same exact audio engine, same robustness, they can exchange files, the only difference being Cubase doesn't have some of the high end post features that Nuendo has. I use both Cubase and Logic and occasionally Nuendo at the University here.. I know both programs fairly well, believe me, both Cubase 6 and 7 can hold their own with any DAW out there, they just don't come with a bunch of ready made loops and preset instruments.
    LogicX will never be able to use 32-bit instruments without a third party solution, nor will it ever include the Bridge. At least according to the people I know.

  • Photshop CC, Bridge CC, Flash CC and Camera Raw update (Windows 7 Ultimate)

    Photoshop CC, Bridge CC, and Flash CC will not update. The error message says to obtain Camera Raw plugin update (Windows). What should I do?

    Hi Michelle
    I am new to the forum so I apologise.  I should have mentioned in my update that the installer that fixed the problem was the ACR 9.0.  I had originally used the 8.8 installer which caused the problem from ACR 7.1.
    Initially the installer didn't work  64 bit version still had 7.1 but it installed ACR 9.0 on the 32 bit.  I then proceeded to manually unzip the exe file ACR 9.0 and coped the 8bi file to the locations stated in my update.  This didn't affect the 32 bit cs6 but completely removed ACR from the 64 bit.  I re ran the ACR 9.0.exe file and everything was fixed.
    I hope that this makes sense.  I have now developed a problem on Bridge though.  I can open raw file in photoshop but I can't view previews and the camera raw preferences are greyed out.  I have read elsewhere that other people have had the same problem.

  • Glossary tab doesn't display and Glossary pop ups don't work

    TCS 3.5 (FrameMaker 10, RoboHelp HTML, version 9)
    Windows XP version 5.1 sp3
    Internet Explorer 8.0
    My apologizes if this should be in a different forum.  Also, from searching I have found that the problem is usually that the DLL has not been loaded -- I have done that. So I am at a loss. Thanks in advance for your help!
    Problem: My .chm output does not have a Glossary tab and the Glossary text pop-ups in my topics do not work.
    Background: Since I am new to TCS 3.5 I'm going to give my entire process. Quite frankly I'm not even sure if my entire process is correct.
    Steps:
    Before I began: I loaded the HHActiveX.dll. Here's the proof:
    Create a blank project.
    Import master page (File > Import > Master Page).
    Load project settings (File > Project Settings > Import).
    Link FrameMaker Book (File > Link > FrameMaker Document)
    Configure Properties (Right-click the book file in RH and click Properties).
    In Properties, select Convert FrameMaker Table of Contents and give a name.
    In Properties, select Convert Glossary and give a name.
    In Project Manager pod, right-click the Glossary topic (System Management GLO) and click Set as Default.
    Update Project (File > Update > Update All).
    Run Glossary Hotspot Wizard (when running wizard, select the glossary topic that was set as default in step 8)
    Edit the UpdateMarkedGlossaryTerms.jsx script (change the GlossaryName variable to the Glossary topic created in step 8 and change the GlossaryStyle variable to TextPopUp)
    Run Update Marked Glossary Terms script (In Script Explorer pod, right-click the UpdateMarkedGlossaryTerms.jsx script and click Run).
    Run graphicinreferencepages.jsx script (this inserts my note graphics from FM reference pages)
    Configure Microsoft HTML Help layout.  Here's the properties file:
    16. In the properties file I selected the Glossary topic that I had set as my default in step 8.
    17. Click Save and generate.
    Result: In the .chm file (and in View Selected Item in RH) when I click a glossary term in a topic, I get "This program cannot display the webpage". Also, the Glossary tab is not displayed.

    Welcome to our community, Linda
    In RoboHelp, if you open the Glossary pod (View > Pods > Glossary > Select Glossary) do you see terms and definitions listed there?
    If not, that would explain it as the Glossary has no entries.
    Assuming it does have entries, you may simply need to enable the tab by clicking View > Pods > Project Set-up. Expanding the Windows section in the pod and double-clicking your CHM window.
    A CHM window looks like this:
    If you don't see a CHM window, you will need to create one. If you do see a CHM window, double-click it. Then ensure the Glossary is enabled.
    Keep us posted! Rick
    Helpful and Handy Links
    RoboHelp Wish Form/Bug Reporting Form
    Begin learning RoboHelp HTML 7, 8 or 9 within the day!
    Adobe Certified RoboHelp HTML Training
    SorcerStone Blog
    RoboHelp eBooks

  • [SOLVED] Thunar 1.6 doesn't drag-and-drop with the right mouse button

    Hallo all.
    It might be something I've done (though I did delete my ~/.config/Thunar directory before upgrading), but Thunar doesn't let me drag-and-drop with the right mouse button, thus stopping me from copying something instead of moving it, etc. Has anyone else had that too?
    Last edited by GordonGR (2012-12-28 14:34:20)

    Joel wrote:
    anonymous_user wrote:Is it supposed to be with the right-mouse button? I always thought drag and drop was done with the left button?
    Could be right-hand user
    Come on! Read what GordonGR wrote!
    Microsoft Windows, Nautilus, the Haiku Tracker, and probably many other file managers have a feature where, when you right-click or middle-click and drag an icon to a new location, a pop-up menu appears and asks what you'd like to do (Move, Copy, Link). I thought I used to use this feature in Thunar too but it seems to have stopped working in recent versions. Has anyone else had any experience with it?
    EDIT: Here's random blogger talking about the feature in an older version of Thunar: http://jeromeg.blog.free.fr/index.php?p … and-tricks So that's good, I wasn't just imagining the feature.
    Last edited by drcouzelis (2012-12-12 03:45:05)

  • My Firefox 8 Menu button doesn't work and neither does the right click in the firefox window

    It seems that all the drop down buttons in the browser, including the bookmarks dropdown menu in the toolbar and the main menu button (firefox button), no longer work. This happened after i upgraded to firefox 8. I've tried uninstalling and reinstalling several times while also deleting user preferences and stuff but that doesnt work. But everything seems to work in safe mode properly. So i disabled all my addons in the normal mode but it still doesn't solve the problem. My right-click doesnt work anywhere in the browser window either. And also, although the menus are not showing, it seems that they are still there because if i click in the area that a button would be in the function activates, this is how i was able to disable the addons.

    Perhaps, it's a multi-monitor setup issue. I noticed that the problem happens on my right monitor, but it doesn't happen on my left monitor! I have an nvidia card.

  • Photo gallery created in Bridge doesn't display thumbnails and links work but don't display photos

    The gallery works in preview and in live view in Dreamweaver, but not when posted to the website. I did one last week which worked just fine, and nothing has been updated in either CS 5.5 or the server software.

    Try to recreate the thumbnails for that folder.
    Use the latest version of the converter (5.4)

  • Loupe in Bridge doesn't display DNG images created using DNG Converter correctly. Why?

    I have noticed recently an anomaly in Bridge when viewing DNG files that are created by converting my Nikon NEF files to DNG using the DNG converter. Specifically, when clicking on the preview image of a DNG file, in order to open the loupe, the 100% image seen in the loupe remain fuzzy, whereas when clicking on a preview of the original NEF file the 100% view in the loupe is sharp and clear.
    I am using DNG Converter version 4.6.0.3, and it also occurs when using version 4.4.1. I am using Bridge version 2.1.1.9.
    I have no reason to believe that Bridge is at fault, since the loupe function does work properly when viewing the NEF file. It would seem that there's a problem in the DNG conversion.
    However, despite this anomaly seen in Bridge, when I open the DNG file in Camera Raw, it is perfectly normal at 100% or any magnification.
    I have tried re-setting the JPEG review size in the DNG converter, but that makes no difference.
    What's going on here? I don't want to keep both the NEF and DNG versions, for reasons of space, but I'd like the loupe to work correctly. Help, please?

    Try to recreate the thumbnails for that folder.
    Use the latest version of the converter (5.4)

  • Aperture and shooting Raw+Jpeg

    In camera Jpeg processing becomes better and better with each generation of cameras. One example is the dynamic range optimizer in my Sony A700. You often have a hard time to get similar results from the Raw. So for quite a lot of shots - especially the not so important ones - using just the Jpegs is a real time saver. Still it is good to have the Raw handy in case the camera processing went in the wrong direction, which still happens occasionally. With 8 or 16 GB cards it is not an issue meanwhile to shoot Raw+Jpeg. Unfortunately IMO there is no smooth Raw+Jpeg workflow within Aperture. Especially it is almost impossible to delete the Raw without loosing the Jpeg and vice versa in a managed library (see thread mentioned below).
    Thus I just posted this to www.apple.com/feedback. If you think this is an important issue, that should be added in a future version of Aperture, you might sent your feedback as well:
    It is nice, that Aperture already imports both pictures, if you shoot in Raw+Jpeg mode. But the further workflow of dealing with the Raw+Jpeg combo is not optimal:
    The main reason to shoot Raw + Jpeg is, to save time in using the ready processed Jpegs for the less important shots or the ones, where the in-camera processing left not much to improve, but still having the safety-net of the Raw for a more advanced development, in case the picture asks for it.
    So instead of showing the Raws and hiding the Jpegs by default it should be vice versa. If there is a Jpeg accompanying the Raw, the Jpeg should be displayed and the Raw should be hidden. At least you should be able to set in the preferences, whether you prefer to see the Raw or the Jpeg. If you realize while rating the picture or doing adjustments, that the Jpeg doesn't fit the bill, you should be able to give precedence to the Raw, aka showing the Raw and hiding the Jpeg.
    After having finished the work, you should be able to either delete or archive the not used version (either Raw or Jpeg), without loosing any metadata or adjustments already applied to the other version.
    Currently it is an extremely complex task, to get rid of the unused version. Workarounds are suggested in this thread: http://www.oreillynet.com/digitalmedia/blog/2007/09/gettingrid_of_unwanted_manage1.html
    Peter

    SierraDragon wrote:
    I am unfamiliar with Sony DSLRs and do not know what might make a Sony JPEG visually equal to a Sony RAW image file.
    What I refer to is the dynamic range optimizer, which is based on Apical’s IRIDIX image processing engine. I think it is used in recent Nikons as well, but as I have only a Sony DSLR I mentioned this.
    Basically it is a kind of highlights and shadows adjustment, but it works very well and in many cases you have a hard time to generate similar good results with your RAW processor (aka. Aperture).
    However, JPEG is still a lossy image format that IMO should only be used for low end usages. RAW converted by the camera vendor's software to non-lossy formats like TIFF should generally be quite superior to JPEG.
    Of cause the RAW holds more information and carefully processed often leads to better results than the in-camera JPEGs. But not every picture will be printed in poster size. And although JPEG is a lossy format, with a low compression setting the artifacts are almost undetectable at least with my DSLR.
    Shooting in RAW+Jpeg mode can be a real timesaver. You look at the Jpegs firsthand, rate them, make small adjustments, if neccessary. For the majority of the pictures you can use these Jpegs even for slideshows and prints. If you step over a picture, where the in-camera processing went wrong, like oversharpened, oversaturated picture with wrong WB etc., you can easily resort to the accompanying RAW and process it to your heart's content. The only drawback with this workflow is the increased temporary storage capacitiy you need. But with today's low memory card prices, the benefits outweigh the cost by far IMHO.
    That said, the reason for my post was not to discuss the benefits of a RAW+Jpeg workflow, but Aperture's issues in dealing with it.
    Peter

  • I redownloaded my Photoshop CS5 and Camera Raw will not accept my RAW files nor will the Adobe Bridge display the picture view of these files. A message displays saying it doesn't support this camera.  I have a Nikon 5100 DSLR Camera.  It always displayed

    I redownloaded my Photoshop CS5 and Camera Raw will not accept my RAW files nor will the Adobe Bridge display the picture view of these files. A message displays saying it doesn't support this camera.  I have a Nikon 5100 DSLR Camera.  It always displayed them in the past.  How can I get it to display these photos in Bridge and open them in RAW?

    Adobe - Adobe Camera Raw and DNG Converter : For Windows : Camera Raw 6.7 Update
    Adobe - Adobe Camera Raw and DNG Converter : For Macintosh : Camera Raw 6.7 Update
    Benjamin

  • DNGs produced from Hasselblad .fff files display a different image in Bridge and Camera Raw

    Lately, not sure when this started exactly, Bridge CC (and Camera RAW 8.7) are displaying incorrect DNG images!  Instead of showing the image I expect to see, I'll see an old image from days ago.  This seems to carry on from Bridge through to Camera RAW.  But then if I continue on to Photoshop with the image, it'll finally show the correct image. 
    I'm assuming this has something to do with DNG, because if I load another raw file type (like .fff or .NEF), it seems ok.  Also it seems to be ok with DNGs produced from other cameras like Nikon D90.
    My set up:
    - Mac OS X 10.9.5 (Mavericks)
    - Bridge CC
    - Camera Raw 8.7
    - Photoshop CC 2014
    - Hasselblad H4D-50

    HI, I managed to fix the trouble by reinsatalling once again and running updates BEFORE opening bridge. It seemed that if I ran the update AFTER opening bridge I would get either an up to date status when checking for updates or I would get an install failure notice on all 4 updates that were trying to install. The updates were for camera raw, bridge and PS. I can't explain why but that helped a little. I also changed permissions on my whole user accnt to include read/write for all users. I can't say if this helped or not. I also had to go into my camera B/U files on a sepate HD and replace some of the CR folders I was using o nthe desktop. Still the CR files would not show a thumb nor a preview till I then went to each individual file inside that folder and purged the cashe for that file so it could repopulate the cashe yet again. This has been the strangest few days in PSCS6 history! Well my personal history. I will report back here if more quirks emerge. I would prefer quarks though....aloha, U

  • I re-downloaded my Photoshop recently and Adobe Bridge no longer displays my Nikon NEF files and Camera Raw will not open them.

    I re-downloaded my Photoshop recently and Adobe Bridge no longer displays my Nikon NEF files and Camera Raw will not open them.  I get a message saying that Camera Raw does not support my camera type but it always has in the past.  The bridge no longer shows the picture view of my NEF files.  These are Nikon NEF files from the Nikon 5100 DSLR camera.  How do I fix this?

    I re-downloaded my Photoshop recently and Adobe Bridge no longer displays my Nikon NEF files and Camera Raw will not open them.  I get a message saying that Camera Raw does not support my camera type but it always has in the past.
    When you re-installed Photoshop, you also re-installed the version of Camera Raw which shipped with Photoshop - in other words you reverted to an older version of Camera Raw which does not support the D5100.
    Camera Raw plug-in | Supported cameras
    The D5100 was first supported in Camera Raw version 6.4.
    In Photoshop, click Help > Updates to update Camera Raw.

  • HELP!!??? Trouble with PS CS-6 displaying/ producing grainy and pixelated images after being imported using PS Bridge and Camera-Raw 8.5

    Help!??? I am having trouble with PS CS-6 displaying/ producing/ saving grainy pictures when import NEF files!!!
    Hi all,
    When I import all NEF or RAW files into CS6 from Bridge and Camera Raw from the Nikon D200 and D5000, they become grainy/ pixelated.  However, RAW files from the D800 did not have problem. I set the Color Space in my Nikons to AdobeRGB, in PS Camera Raw 8.5 to AdobeRGB, in PS CS-6 ColorSpace to AdobeRGB, and Save As Jpeg with Max quality (12). When comparing between CS-6 produced file and the original, I can see a big drop in quality and the picture become grainy and pixelated. What can I do to make this right? Any help/ suggestion is appreciated.
    Thank you!
    HN

    Can you show us a screen-shot of the raw in Camera Raw that shows this noise, or if you only see it in the saved JPG, then show us a side-by-side of the raw in Camera Raw and the JPG?  Show the same area of the photo and zoom to 100%.
    It is normal for raw photos to have grain but you can mostly remove it with the Luminance Noise-Reduction sliders in the Detail tab of Camera Raw.
    The amount of grain depends on the ISO sensitivity setting on the camera.

Maybe you are looking for