Colour Management in Adobe Premiere

Hello,
I'm working with Adobe Premiere to create animated slideshows.
I develop my Photos with Photoshop.
I import them in Adobe Premiere.
My issue is that, once the photos are imported in Adobe Premiere, the colors are wrong, whatever the format. I have tried jpeg, tiff, psd...
When, within Adobe premiere, I select "edit in", I open the photo and the colors are ok, but not in the animation or my final product.
I don't find in the preferences, where to manage colors.
Please help me.
Olivier.

PrPro is not colour aware application. So as to use Photoshop images in PrPro properly you need to make sure they are in sRGB colour space.

Similar Messages

  • Adobe Premiere wont appear in my Application Manager list for download

    I have just purchased Adobe Photoshop CS6 and Adobe Premiere Pro CS6 for 19.90 each monthly. When i went to download Photoshop it appeared in my Adobe application Manager list and allowed me to install it with no issues. However when i went to download Adobe Premiere Pro it does not appear in my Adobe manager list and thus wont allow me to install it. Where do i install Adobe Premiere and why won't it let me install it as it doesn't appear in my adobe application manager?

    Adobe Premiere Pro CS6 will only install and run on 64 bit systems
    http://www.adobe.com/au/products/premiere/faq.html#64bit-support
    I suspect you're running a 32 bit system in which case it will not appear in the AAM for download.

  • Adobe Premiere elements 10 has lost HDV camera in device manager..help

    Our Sony V1E camera was recognised in Adobe Premiere Elements and we could capture footage fine.. suddenly the device manager can't see the camera..but ..strangely..it can play and rewind the camera etc etc.. just cannot capture?? waht has gone wrong?? It's connected with firewire.
    Help?

    All our configs are for Pal HDV 1080i mode in camera and Adobe element project preset is Pal HDV HDV 1080i 25 to match camera.
    The elements device manager can shuttle the tape in the camera forward/back etc but cannot capture in the HDV capture mode
    If we put the device manager into DV mode it will capture the footage even though the camera is in HDV mode?
    Previously the device manager captured the HD footage and recognised the camera itself in the window and suddenly it doesnt recognise the camera in that window and can only capture HDV footage if we go to capture mode for DV camera where it only recognises a Micorsoft DV camera VC generic setting??
    That tells me that the port and cable are working perfectly.
    Could a setting in Premiere elements be wrong??    DV/HDV device control is selected in preferences. HD anomorphic is also selected.

  • Adobe Premiere CC 2014 not Project Managing properly

    I need to be able to Project Mange my Premiere Pro CC 2014 project and send it to the east coast by morning and it is giving me the old " An Unknown Error Occurred during the Project Manager operation. Please save your project and retry the operation." message.
    Why does this happen and why does Adobe Premiere Pro CC 2014 crash on my 40 times a week?
    Please if someone can help me....!
    I am running Premiere Pro v8.0 Single Barrel (8.0.1 (21) Build on a iMac 3.4 GHz Intel Core i7 with 24 GB 1600 MHz DDR3 ram --- OSX 10.9.4
    Thanks

    I'm experiencing the same error with the Project Manager since the latest update to CC 2014.
    sotrabdj, did you have any luck figuring out what was going on?
    I've had one crash so far. Completely frozen machine. Had to hold the power button down to force restart.
    I am running an Early 2008 2 x 2.8 GHz Quad-Core Intel Xeon with 14 GB RAM and a NVIDIA GeForce GTX 285

  • "Adobe Premiere CC" free trial says "Go to Subscription Manager..."

    I downloaded the "Adobe Premiere CC" free trial, and, when I try opening it, it says "Go to Subcription Manager to renew subscription"...?

    This is mostly a user to user forum, with a "few" Adobe staff who "sometimes" post
    Adobe contact information - http://helpx.adobe.com/contact.html
    Help for Download & Install & Setup & Activation http://forums.adobe.com/community/download_install_setup
    Next link has a "Chat Now" button near the bottom http://helpx.adobe.com/x-productkb/policy-pricing/activation-deactivation-products.html

  • I'm using windows 8 and when I open premiere pro then it says i need application manager, so i get it and that says i need adobe support advisor but that is discontinued and now i cant use adobe premiere pro

    I'm using windows 8 and when I open premiere pro then it says i need application manager, so i get it and that says i need adobe support advisor but that is discontinued and now i cant use adobe premiere pro. what do i do now?

    Do a clean (re)install:
    * Download a fresh Firefox copy from http://www.mozilla.com/firefox/all.html and save the file to the desktop.
    * Uninstall your current Firefox version and remove the Firefox program folder before installing that copy of the Firefox installer.
    * Don't remove personal data when uninstalling.
    * It is important to delete the Firefox program folder to remove all the files and make sure that there are no problems with files that were leftover after uninstalling.
    You can initially skip the step to create a new profile, that may not necessary for this issue.
    See http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Clean_reinstall

  • Another: a serious error has occurred that requires Adobe Premiere Pro to shut down

    I know a few people have had the same notification:
    sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project
    I have tried a whole series of things to fix it and no luck. Here are all the computer stats... does anyone have any ideas???
    Premiere Pro
    Version number: CS5, with most recent update
    Installation language: English
    Updates applied: Most recent… installed AFTER problem started
    Project/sequence settings… NA
    Operating System
    Name: Windows 7, 64bt
    Update/patch level: Service Pack 1
    Installed language: English
    Display resolution and color depth. 1920x1080; 32bit color
    CPU type and speed Core i7 950
    Amount of memory (RAM) 12GB
    Video card 
    Manufacturer: Nvidia
    Model: FX3800
    Driver version: Latest (installed after errors started)
    Number of monitors (displays): in use 2 (with one disabled for testing)
    Audio card
    Manufacturer Gigabyte Technology 82801J HD Audio Controller
    Model
    Driver version: 6.1.7601.17514 (latest version)
    Each hard drive's capacity and space remaining Disk setup (partitions used, raid configuration, what is where for OS/projects/media/scratch/audio)
    C and D, no partitions. D is raided, controlled by hardware controller. All software on C. Media kept on D.
    Hardware capture device NA
    Manufacturer
    Model
    Driver version number
    Capture software NA
    Name
    Company
    Version
    Comprehensive list of third-party plug-ins you installed.
      None for Premiere I don’t think. A couple for After Effects. Have been installed for a while with no recent updates.
    Exact text of any error messages
    sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project
    Explain clearly what you want to do, what you are doing and what the result is
      Open Premiere to do some work 
    Be sure to mention if it is something that worked before using the same procedure
    Nothing has changed on the PC prior to program failure.
    Very importantly: Post details of troubleshooting you have already done to avoid "did that" reponses to questions people ask when trying to help.
    Tried:
    Reinstalling
    Reducing to one screen.
    Holding Shift when starting until first screen (New/ Open Existing/ Help)
    Holding Ctrl, Shift Alt when starting until first screen (New/ Open Existing/ Help)
    Programme crashed regardless of clicking directly on loading icon and opening New or Existing via first load screen, or via clicking directly from a project file.
    Removed all fonts installed since last opened.
    Restarting.
    Updated Graphics Driver.
    Updated Premiere

    Hi guys; I thought I would share my experience and how I managed to fix this problem. It might help someone.
    In my case I kept receiving this message; eventually after re-launching Premiere, I actually paid close attention to the "software loading" information and saw that it got stuck on my installed "Colorista ii" which is a colour grading software.
    Now the red bulb came on my head ping!
    I recently just upgraded my Mac to the OS X Yosemite & that affected pretty much any non-updated application, which in my case was that and many more of the Red Giant Pacakge; so I searched for the upgrade via Red giant Link, and low and behold I found it and did so. Immediately everything loaded up perfectly fine.. and now can't even do the work, cos I'm so exhausted from an 'almost heartattack'; so going to sleep and commence later in the day I guess..
    Now, you might probably want to check if any application on your system needs upgrading to whatever is the operating system on your Mac or PC at this very time. It might help.
    Always back-up.
    I hope I helped someone :-)
    @ToleXElijah
    Extreme Studio Manager

  • No Manual for Adobe Premiere Elements 9?

    Hi, First time posting.  I just purchased Adobe Premiere Elements / Photoshop 9 this weekend for my Mac.  My first (of probably many questons) is whether an electronic manual comes with it.  I can't seem to find it either on the the DVDs or installed on my computer.  Am I missing something?

    Hi Valmundo,
    can appreciate your frustration - I had the same trouble with Adobe.
    Try this site:- prodesigntools.com  They have a 95 page manual in pdf which should suit.
    And if you are wondering where the adobe gamma they promised to include with the software has gone ?
    If using W7 try this:-
    go to Control Panel and
    click on        "screen resolution"
                       "Advanced Settings"
                       "colour management" (twice)   
                       "Advanced"
                       "Calibrate display" and follow the instructions. It works OK with my LCD monitor.
    Good photography, Jaunogre.

  • My problem is that after printing the first photo or picture, when I come to print a second, both the Colour Management and Epson Colour Controls are greyed out and showing No Colour Management

    I have recently purchased a Mac computer (updated to Maverick) to go with my Epson Stylus Photo RX500 printer which has given excellent service with my old Windows computer. However, when trying to print pictures or photos via Photoshop Elements 11, the best results I can get are using the Colour Management and Epson Colour controls in the printing options box.
    My problem is that after printing the first photo or picture, when I come to print a second, both the Colour Management and Epson Colour Controls are greyed out and showing No Colour Management, The only way I can reset the controls is to shut down the printer and computer and restart.
    Could there may be a setting somewhere that I need to adjust please?  I have been in touch with Epson and they say that the Epson Colour controls are part of the Photoshop Elements software but a post on the Adobe forum brought no results and I am unable to contact Adobe.
    <Edited by Host>

    Hello Garry. Thanks for the reply. I guess I should have used a different title from "How do I post a question?" That should come after trying to resolved the colour settings first. However, to answer your question, after experimenting with all the different settings in Photoshop Elements and Epson software, I now start with PSE11 Colour settings then click "no colour management" then after clicking Print, I choose "More Options/Colour Management/Colour Handling/Printer Manages Colour" then I choose "Page Setup/Layout/Colour Matching" which then shows Epson Colour Controls but I also choose "Layout/Colour Management" which then shows "Colour Controls/Mode" I then of course choose an Epson printer profile depending on the paper I am using. I get good results but as I said, the Colour Matching and Colour Controls are then greyed out. Hope that makes sense.

  • Adobe Premiere Pro CS4 4.0.1

    An update to Adobe Premiere Pro CS4 will be available via Adobe Update Manager shortly. The file will also be available for download tomorrow (November 20) on Adobe.com, as will the readme (at http://www.adobe.com/support/documentation/en/premierepro/releasenotes.html). In the meantime, here is the text of the readme.
    We're really excited about this update, especially considering we released CS4 just one month ago. To force an update, choose help --> find updates from any Adobe application. The AME update that releases with this update is required as well.
    Important note: if you are using the Elemental Technologies RapiHD plug-in, you must update to the latest version in order to use Adobe Premiere Pro CS4 4.0.1. You can update the plug-in by visiting the Elemental Technologies web page: http://www.rapihd.com/?q=node/129
    New in this release
    - OMF export
    - Final Cut Pro import
    - Edit in Audition (Windows only)
    - Surcode support
    - AAF import and export
    - High quality motion
    - Third-party support
    Notable fixes
    - Attempting to trim locked tracks results in a crash (#1888355)
    - Crash on Win and error on Mac when using Numpad-Asterisk keys to generate marker when
    playing in Program Pane when Effect Controls pane is closed (#1890626)
    - Crash when the Metadata panel is brought into focus when a DVCPro HD clip is selected
    (#1884633)
    - When a filter/search is applied in the Metadata Panel and then a different asset is selected, the
    filter does not update (#1876954)
    - Custom schema causes Adobe Premiere Pro to crash performing many basic operations,
    starting with New Project (#1888938)
    - Render of transition in imported EDL-based sequence fails; on Mac, causes application to hang
    indefinitely, user must be force-quit application (#1873434)
    - After ASND is saved, an effect is always ON if it turns OFF while playing (#1864978)
    - Crash when attempting to load a project that contains a composition if headless Adobe
    Premiere Pro is serving Adobe After Effects (#1871578)
    - Exporting video as MPEG 4 will create a video file that imports at the incorrect length
    (#1851063)
    - Trimming both ends of a clip, then moving the clip will cause looped playback to be silent, or
    only playback portions of the clip (#1868409)
    - When exporting a timeline containing cuepoints, deleting a cue point via AME Batch-> Export
    Settings, the cue point is still present in the output file (#1866690)
    - Playing an audio-only file in the source monitor will cause the application to lock up (#1887330)
    - Exporting any MT session as 24bit WAV leads to garbled audio Mac only (#1881684)
    - Adobe Premiere Pro allocates too much memory and reads too much data from disk when
    loading project files on the Mac (#1890579)
    - With camera connected, opening clip from Timeline into Source and selecting File  Debug
    results in a serious error (#1889197)
    - Export to tape is active from DVCPRO HD sequences (#1863718)
    - Application intermittently crashes when exporting a movie (#1868405)
    - Render and Replace of offline clips takes over 20 minutes (#1885273)
    - Application crashes when cancelling Normalize Audio Track dialog (#1887615)
    - When an AVCHD clip is inserted into a DV timeline with Scale to Frame Size applied, rendered
    previews of the clip show artifacts during Timeline playback (#1863988)
    - Using scale to frame size in a timeline lowers output quality and softens detail and sharpness;
    typing in scale attributes manually or using Adobe After Effects produces much better results
    (#1527669)
    - Multiplexed MPEG files exported to HD size and then imported back in to Adobe Premiere Pro
    show up as 601 color space instead of 709 color space and hence the colors of the imported
    files are off (#1852977)

    Other users have reported having trouble with VOB files from DVD recorders.  Properly authored DVDs work.
    Where did you get the VOB files that won't work for you?
    -Jeff

  • Help me before I turn to Adobe Premiere Pro and PC!

    I am desperately trying to import HVD footage from a Sony HVR-A1 in OfflineRT mode. I have a pretty slow Mac which does not allow me to work with native HDV or Apple intermediate codec and I WILL HAVE TO turn to PC if I do not find a quick solution… Argh…
    I have tried the following :
    1. OfflineRT HD esay setup specifying HDV as Capture setup and Sony HDV 1081i50 Firewire.
    - It has worked once and not more after that
    - The sequence is in JPG compressed mode but clips are all captured in full HDV, which makes it impossible to edit in RT… I have no idea of what is going on…
    2. Offline RT (DV)
    - Using i-link downconvert mode to capture in OfflineRT mode
    - Everything seems OK until I finally try to batch capture in HDV. I then systematically get error messages and only a small part of the clips are captured.
    3. HDV capture and transfer to OfflineRT HD via Media Manager (recompress)
    - Everything works fine (capture, recompress and batch capture).
    - BUT: it seems that recompress with OfflineRT HD suppose that the original is letterbox so that when the original (as mine) is 16:9, the compressed output is strongly distorted.
    - I tried to use custom recompress procedures but they all seem to produce outputs which cannot be edited in RT…
    It has been two weeks now and I did not start editing yet… What should I do? Turn to PC and Adobe Premiere Pro 2.0?

    Welcome to the forum Jean-Claude.
    If you will provide your system specs, I'll bet that
    someone here will get you running smoothly and
    happily.
    Sorry for that...
    My spec are:
    FCP5
    Mac OSX
    2 HD (one external via firewire)
    G4 on PowerBook with 512M RAM
    I am capturing directly via Firewire from a Sony HVR-A1 PAL
    My main concern however is that my problem does not seem to come from hardware spec since I have no real problem in capturing in native HDV (although my computer is too slow to edit in native HDV or in Apple intermediate Codec). It seemed to me that OfflineRT HD was just the way it should work for me (I can find a proper computer to fine-tune the final work) but I have found nowhere successful reports of using this option...
    EDIT, just came across your other post... "Offline
    editing with FCP5 OfflineRT HD"...should try to keep
    only one thread active... keeps everyone from getting
    confused...
    Sorry for that too... I am going to close the other one right now...
    G4   Mac OS X (10.2.x)   PowerBook RAM:512M

  • Colour Management - who does what - Some thoughts now the smoke is clearing

    First up, thanks very much to everyone who contributed their ideas and expertise to my recent query here, when I was seeking help for a problem with colour management issues when printing a magazine I edit. I have a ton of suggestions  to work through and study but the smoke is slowly clearing and it raises some interesting points which I think are worth recounting.
    First of all, I have been editing short run magazines now for 25 years, at first part time and later on a professional contract basis.  I am not a trained graphic designer nor a trained printer. I did start out training as a graphic designer, many years ago but gave it up for a career in IT (as a networking specialist). That was full time until 10 years ago, although I did some freelance writing and editing in my spare time.
    And yes, I did start originally with scissors and cut and paste, and moved on through black and white with spot colour and Pagemaker software  to full colour and InDesign today. One thing which may be different about my experience to most of yours is that I am a PC user and always have been. All my editing and graphics work has always been done on a PC - Pagemaker was our DTP package of choice for a long time and we supplemented this with Corel-Draw (which has a range of graphics handling options). All my software is legal and I always register it and keep it up to date. I have used the same graphic designer for quite a few years now and whenever we upgrade our software he goes and gets trained on the latest release.
    Around 10 years ago I was offered the chance to edit a specialist short run magazine (not the current one). This was a chance I took and gave up the day job and became a full time freelance. Editing is not my main or only source of income. I am also  a freelance writer and photographer and heritage consultant and I have a specialist image library.   I sell my own sell my work - articles and pictures - to the national and local press. I also write books (non fiction) on commission. The magazine editing is really an extension of my interest in historic landscapes. I have never had any complaints, or problems, with the freelance work, photos and archived images I sell.  Clients include national newspapers here in the UK, national magazine groups and my books are available in national bookstore chains. I supply my work digitally, naturally, and it includes photos I have taken myself and items which I have scanned into my library of historical images and store on line. No reported colour management issues there.
    I have always enjoyed a good relationship with my publishers and printers because I seek to be as professional as possible, which means delivering my stuff on time, to the required standard so that minimum intervention is required from them. This does assume that I have a clear brief from them on what they need from me.
    Recently this approach has not been enough to avoid colour management issues with the short run magazine I currently edit. I have been wondering when  and where things went astray and date it back to the upgrade to InDesign two years ago. However it may have its roots in my earlier decision to use PCs not Macs for my work.
    Until 4 years ago I had used the same printers for magazine editing for many years. They were a well respected firm specialising in short run magazines. They were not far from where I live and work and if there was a problem I would go over and discuss it with them. They were happy, and competent, to handle Pagemaker files generated on a PC and convert my rgb images to cmyk if there was any concern about the colour balance. On a few occasions I paid them to scan a photo for me. However 4 years ago the owner decided to retire and shut up shop. I needed to find a new printers and it had to be someone who specialised in short run magazines and could meet the budget of the charity I edit for. Also someone who could handle copy generated using Pagemaker running on a PC. I chose a printers I had used briefly in the past  where I knew some of the staff and was promised PC based Pagemaker would not be a problem. I even got this in writing. I started to send them proofs generated using Pagemaker v7 on my PC.
    I soon found that although they had agreed they could handle Pagemaker on a PC in fact they had only a few PC based clients and were using a single ageing PC running Pagemaker to proof their work. In fact nearly all their jobs were Quark based. I was also told we had to supply CMYK images although not given any further requirement so I now did the conversions from rgb to CMYK using my PhotoPaint software. (There are quite a few settings in Corel for the conversion but there was no guidance  by the printer on which to use so to be honest it did not occur to me that it might be a problem).
    Now of course I understand that the drive to get customers to supply CMYK images was a Quark driven requirement back in the late 1990s. I did not and do not use Quark so knew nothing for this.  I did have some early colour problems and font incompatibilities with the new printers and was pressured by their senior Graphic Designer (who designed for their own contract clients) to upgrade to InDesign and provide them with a .pdf, which I was assured would solve all my problems. The .pdf would be the same as the final printed magazine because "it would not require any further intervention by the printers".
    I expect you are collectively throwing up your hands in horror at this point, but I think he was speaking genuinely. The creation of a .pdf  using InDesign, is widely promoted as the ultimate answer to all printing issues.   I have encountered it recently with a lot of printers' salesmen and my friend, who edits a learned journal, has just been told the same thing by her printers, to get her to upgrade to ID. Incidentally she also uses a PC.
    So we upgraded our design process in house to InDesign and our graphic designer went on a course, two courses in fact. When we came to produce our first .pdf using ID, the printers'  Senior Graphic designer came on the phone and talked our designer through the ID Export function. I think he may at that time have told him to create a preset profile with MPC and the defaults, but to be honest I don't recall. We were never sent anything in writing about what settings we needed to match theirs. I continued to have intermittant colour management problems but put this down to my photos. Things came to head with the most recent issue where the colours were badly out on the cover, supplied by a press agency and taken by a professional photographer. The printers seemed to have little or no idea about possible causes.
    Initially I thought that part of the underlying cause must lie in some mismatch between what I was sending the printers and what they expected to receive so I asked them to specify what I should send. All they said was use Profile preset as MPC setting and accept  the defaults which accompany it.
    So I came on here looking for a solution. A lot of people were keen to offer their own experience which I really appreciate. However the messages could be conflicting. Some of you suggested it was the underlying cover photo which was at fault, some that it was my monitor which needed better calibration.
    Many of you here said that part of the problem, if not the whole problem, was the way I was generating my CMYKs for the printer and I should use Photoshop to do this. You also mentioned a number of possible colour management settings which I should try.
    At times the advice seemed to change tack. There were suggestions that the colour management issues I had  were nothing to do with the printers, that it was up to me not them. Quite a lot of you said I needed to be better informed about Colour Management issues. I agree, but I had never had any previously (maybe good luck, maybe good support from my previous printer) so I was not even aware that I needed to be better informed.  Some of you mildly chastised me for not finding out more and doing more to manage my own colour management with the switch to ID. To which I can only say if I had needed to train up, I would have done. I did not realise I needed to.  Nor was my designer aware of the issues as colour management was not really covered on his ID courses which were about typesetting and design.
    Some of you even seemed to hint that unless I was prepared to use an expensive high end printer or effectively retrain as a print specialist or get my graphic designer to do so, then I probably shouldn't be in the magazine editing game at all. OK maybe that is a bit harsh but you get the drift.
    The fact is that printing is much more accessible these days to all sorts of people and in particular to people with PCs. My brother lives in a large village in an isolated area and produces a village magazine which has been a great success. It is in black and white with spot colour but he would like to move to an all colour issue. He is a bit nervous of the colour management issues as he has no experience of graphic design and is his own designer using a low end entry level design package. He too uses a PC. The printers reps all tell him the same thing they tell me, that all he needs to supply is a .pdf using InDesign.
    Somewhere I feel a black hole has developed, maybe back in the 1990s with Quark 4.11. A lot of printers standardised on that, and set up a work flow and prepress dependent on CMYK images as provided by the clients. They assumed the the clients would doing their own colour management. This approach also assumes everyone is using Quark on a Mac with the full range of Adobe software. When it became possible to generate .pdfs using InDesign, this was held out to users as the Holy Grail of magazine printing, even though their workflows and prepress were still based on Quark 4.11 principles. Any underlying colour management issues the clients now have to tackle themselves.
    So now we have the situation in which I find myself, having to learn from scratch a good deal about colour management issues so that I can tell the printers what is needed for my magazine. Meanwhile all the printing salesmen, the ones I encounter anyway, are still busy pushing the InDesign to .pdf as the "be all and end all" solution. Some re-education is needed for all parties I think.

    I am glad to see that the sun is peeping through the clouds.
    I apologise for my Aussie-style straight talk earlier, but as I said before it was not directed personally at you but in the direction of others whom you epitomize, repeating a conversation I have had many times over the last 10 years or so where respectable, well-meaning photographers, designers and other contributors refuse to accept that colour management is being thrust upon them.
    It is a simple fact of life, there is this 'new' thing that has butted into the very root of our trades and changed the most basic principles of printing and photography.  We expect that this kind of thing does not happen but the industry we now work in is not the same one we trained in twenty years ago.
    Many printers are still struggling with the same conflict, so many tradespeople cannot accept this change.
    This is exacerbated by the fact that colour management is so complicated to learn and implement and confounded by the fact that the default settings and a clumsy workflow often yield acceptable results with incorrect, generic settings, hence the old 'use InDesign and make a PDF and it will be ok' route.
    When the chain of colour management includes the photographer, the photographer's client, the designer, the other designer maybe, the prepress person, and the platemaker, and a single incorrect click by any one of those can kill the CM it is not surprising that in the end when someone is looking back to see where it fell over they usually never find out.....   They will meet someone who says ' I never touched it, I simply opened the file and scaled it and closed it'.  And that person will be a reputable photographer or designer (and CLIENT) who has no idea they just broke it.  So what do we do?  We go with the generic setting that seems to yield adequate results therefore avoiding the confrontation. 
    You need to understand the situation of the printer who took his business through the 'early' days of colour management, we had all kinds of very reputable sources supplying incorrect files, we did not have the expertise yet to be able to address the entire workflow, it would have meant training photographers and designers all through the best design houses and national institutions, because they blamed the printer.  Only in the last few years have I seen these people coming around to the fact that they bear responsibility for implementing their own cm and maintaining it through their own work.
    Sadly, many high end sources are still not there, and I mean HIGH end!  Probably the ones that don't even visit this forum because they want to keep blaming the printer... They tend to live with the poor quality reproductions and just pull up the worst ones and fiddle with those and try to avoid the 'elephant in the room'.
    I am sorry to say that it was not practical for a printer to reject mismanaged files for fear of losing clients who would happily accept less than perfect results in order to avoid the painful truth that was being told to them.  The best thing we could do was to gently make those clients aware that their workflow was imperfect and hope to show them how we could help...  Many print shops do not have someone knowledgeable enough or patient enough to do this, or the boss does not understand the issue either and tries to work around it to keep his jobs flowing in the expectation that all those experts in the chain will eventually tame the thing.
    The many experts on this holy forum are waaaaayyyy ahead of the printing industry in general and photographers and designers in general in their understanding of colour management workflow.  I have seen first hand how reputable local industry people and trainers alike are spreading misinformation and bad techniques, when I discovered these forums back in about 2002 I found that they opened up a whole new galaxy of knowledge and facts that actually worked and made sense, unlike what I had been told locally....  This forum taught me what the Adobe text books did not, the Tech' teachers did not, local 'experts' did not! 
    I tell all interested people to join these forums and learn to discriminate between the good and bad information.

  • Adobe Premiere Elements 0.9 project crash, HELP!

    This is the first time I am using these forums, so I hope I posted this in the right sektions.
    I need help and solutions for a Project which constantly crashes on my Adobe Premiere Elements 0.9. This program has been awesome and helped me create some projects and videos successfully, up until.... well for about 3 days ago when my latest project crashed when I had just antered and checking the storyboard etc, triggering a "Serious Error" message and then it shuts down. I try again and again, but everytime I try to put something (any sound or video etc) on the storyboard and start working etc the same damn "Serious Error" message and then allways shuts down. It's allways this same and only project (which has worked fine before) that crashes like this...
    In an attempt to first solve the problem myself I went through the Premiere Elements 9 files and deleted finnished projects and automatic saved process on projects etc, but still won't work even better... The funny thing is that when I open another project (a finnished project I left saved just in case) and go through the storyboard there and messes around a little and such, it won't crash nor trigger the same message as my latest project. And that program even has some effects on every footageclip on it too, but still it works fine. Haven't touched the program or the program until and since yesterday night to give it some rest but it still won't work, the project just keeps crashing like when and since it first started a few days ago.
    I have also read through and tried some things from this Help/Troubleshoot page:
    http://helpx.adobe.com/premiere-elements/kb/troubleshoot-damaged-projects-premiere-element s.html
    I have so far been doing 1 and 2 of the "Beginning Troubleshooting", otherwise I have been reading it all and such. I am also kinda afraid to do the 3 of the first quests because I worked so hard on this project and even tough it just keeps crushing, I'm afraid to lose it. Other, I have deleted audios and such from my filegallery on my Adobe Premiere Eements, stuff I don't need anymore because its projects are already done. After I did that I also tried to create a new project just for testing. The amazing this about this is that this the new created project I created works just fine, I could do all kinds of the stuff, effects and advanced editing which I did on the same project before it started crushing. Tough I didn't save that test-project since I didn't find a reason to since it worked so good. And so the thing is that I can start and create a new project and start working and do usual stuff on it with no problem, same when I open up another project and do stuff, it all works just fine! It is just this one and only project that keeps crushing with this "Serious Error" message, all the time... Does anybody else have, or has had the same problem? What could the problem and error be and how to fix it?
    This crushing project do has some effects on every footageclip/videoclip on it, to set the right mood for the musicvideo I'm making. I am making a musicvideo, and I haven't even done the half of the project/video. The song I am making this musicvideo with is about 00:07:32 in length, and (tough this detail may have no influence or meaning) the music is Symphonic Metal. The actual file of the song is 6,96 MB in size. This is also not the first time I've done such projects with such long songs on this same program either, one of my last videos I managed to successfully make and create a musicvideo with a song which was about 13 minutes and 30 seconds in length, and I also used effects on pretty much every videoclip on that project too.
    The current filesize so far on the actual project.prel-file of my project that keeps crushing is 9.73 MB.
    I am also using Adobe Premiere Elements and doing this troubleing, crashing project on a PC, a Fujitsu Windows (I believe Windows 7, or even updated to a newer version?). It has a regular ATI-card. The computer also has 2 modems and there's still some pretty GB amount free on them. The PC's main system also has a RAM in 6.00 GB and the operative system is the 64-bites.
    In short, the PC should just fine be able to handle Adobe Premiere Elements 0.9 and all its projects, just as it has handled it all before plus all my PC games at that. So it must be something with my Adobe Premiere Elements and that specific project which is the problem, but what is the problem and the serious error and how to fix it?
    Could it help to save and create the actual video in this crashing project, delete that project then start a new project, upload and put in the videofile of the crashing project in that new project and then continue from there?
    In either cases, I need help with this. Please, help!

    Thanks so much for your reply, Steve!
    Even tough I trust you guys enough here on the official Adobe site/forums to answer those questions as best I can, I am at the same time not very fond of giving away too much information because of safety. I understand I have to If I'm to recieve the accurate answers and solution, but as this is the internet you can never know. But again, I trust you guys enough on here and thus I'll try to answer those questions as best I can, even tough I am not very good with such stuff about computers. The PC I am using is also not only mine, it is the family computer also which me and my whole family uses.
    The operating system on my computer (according to the computer propotions etc) is a 64-bites operating system and the computer/PC is also a Windows 7 Home Premium.
    The processor the computer/PC have is a Intel(R) Core(TM) i5 CPU and the RAM is 6.00 GB. However, (and I hope I make this understandable because the computer/PC is in swedish)the subscore of RAM in the computer's Performance-Classification/Ranking is 7,5. The processor subscore is 7,3 per second. And the free space? Well, we have two modems, let's say a modem A and a modem B. Adobe Premiere Elements 0.9 is set to save all its stuff etc on modem B, while modem A is the main modem and spaces all main stuff and other things of the computer/PC. Modem A has about 314 GB of free space, while modem B has 207 GB of free space. Modem A's capacity is a total of 489 GB in which 175 GB has been used, the modems filesystem is a NTFS. Modem B is also a NTFS filesystem and its capacity is a total of 439 GB in which 232 GB has been used. And the Disk Cleanup? I believe my that latest ran it for about a few weeks ago. We also have a CCleaner also. But about the Disk Defragmenter, I have no idea. What exactly does a Disk Defragmenter do?
    You mean, entering my project that keeps crushing and simply rename it by using "Save As"? If that is what you mean, I dunnow If that actually worked. When I still tried to do stuff and edit the crashing project (tough as said, it hardly took any changes and process before it triggered that message) and then crashed and shut down, and I opened up the program again (trying to open the same project that way), it asked me If I wanted to re-create the missing process from the last crash of the same project. I tried it and it automaticly was renamed to a for example Project.copy. But when I tried to work with that it was to no futher success, the project kept crashing. I haven't renamed the project by "Save As" tough, but I doubt it'll work, I even tried to rename the actual project file in the Adobe Premiere Elements files but nope... the project keeps crashing. But also about the same question, "Save As" under a new name but in its own folder? You mean the actual project folder or Adobe Premiere Elements preview folder of the projects?
    My camcorder is pretty old by now, have had it since I turned 15, it has worked pretty good since then. Its model is a Sony Handycam, Carl Zeiss Vario-Tessar OPTICAL 20x. Even tough the last thing maybe doesn't say anything, this is all I know about my camcorder, except that it is a model no. DCR-HC17E PAL. But in that Project  which keeps crashing, there are only a few actual camcorder clips used as I am making a Game-MusicVideo and most of the footage of the Video-game (actually a PC game) I'm making a musicvideo of is downloaded from Youtube mostly from a guy I asked permission for to download his recorded footage of the game. I used a Youtube downloader called ClipConverter. As I don't have a SD card I cannot make this footage myself. But some footage I recorded on my camcorder, but If I can find high quality clips and get them, I will. The other footages is actual official trailers of the PC games which also was downloaded from the net. But I can give you the stuffs filetypes and hoping that may help. The downloaded footage which was downloaded by this ClipConverter, are MP4 files. The other stuff (which were official trailers) and most of them are also MP4 files, the others are QuickTime-film files. Many of these downloaded footages and trailers are also in HD quality, at least some of them I think.
    The actual filetype ofthe footage I myself recorded with my camcorder are, well.... it says Videoclip in the file. Maybe it is AVI?
    The project settings? You mean the settings you set at first when starting as a new project? The general settings are, in editingsettings it is AVCHD 270p square pixel. This is kinda hard for me to tell since everything is in swedish in my program. But these settings has worked perfectly before, same with all files, footages and videoclips I have been using, also all the soundfiles etc. Even the actual crashing project worked perfectly before it started crashing... So why does it so suddenly start crashing now?
    The audio is a song I copied directly from its album and CD into the computer/PC and it seems to be in WMA format in filetype.
    And lastly, no I haven't rendered the timeline of the project ever, not even on my other projects. What does the rendering do and is useful for? I have very little knowledge of it. Other, I keep the Timeline mode open all the time because I can edit my videos much better with it, but perhaps that editing method make little influence of the actual problem.
    Other, yesterday when writing the post and topic, I forgot to mention that I restarded my computer right after I created a new project, that testing project. When finnished with the testing I restarted the computer. Since then I haven't touched the crashing project since now tonight, when checking its settings for this post. I am also right now trying to create and save the actual videofile of it, saving it on my computer. I'll soon see If it's successful without any crashing interruptions, plus that the video itself works and is smooth when I'll play it on Windows Media Player like all the rest of my other videos. I do this just in case I must create a new project to be able to continue with my musicvideo, as the first part of it I worked very hard on.
    Other and again, I am still puzzled about why this is even happening, that this project which worked perfectly fine before, just suddenly starts triggering that "Serious Error" message and crashes. And in this program which worked so perfect before. Has this happened to anyone else before? Has anyone else experienced the same issue I have? Is this a knowledgable issue which has solutions and ways to fix it?... :/

  • Can't open Adobe Premiere Elements 9

    I've had some problems with Adobe Premiere Elements 9 recently, and right now I'm not able to use it. I'm not sure what the problem is really or how to fix it so I'll just write down what has happened here and hopefully someone knows what to do.
    A week or so ago my laptop started to crash repeatedly, but fortunately that was solved. But then I noticed that when I opened Adobe Premiere Elements, that's when it crashed and only then. It stopped crashing altogether except for when I opened this program (if it is of any importance I also tried opening Windows Movie Maker to edit there in the meantime but the same thing happened there, which seems strange and kinda random to me). I decided to get an antivirus software and install that and see if that took care of it, which I have now done. That didn't exactly take care of it though. The laptop did stop crashing when opening the Adobe software, but nothing happens once it's opened. The tabs on the top right are there but the whole program is just grey (where you would normally have the timeline on the bottom, video to the left, and the files etc. to the right) and nothing else comes up. I then tried to uninstall Adobe Premiere Elements 9 from my laptop altogether and then re-install it with the CD I still had from purchasing the laptop a couple of years ago. But after re-installing there is no change. Just a grey screen once again, except for the tabs and all that on the top. Now I'm not sure what else to try. It's frustrating as I need this program to work right about now. Does anyone know what to do? Thanks.

    From the Premiere Elements Information FAQ http://forums.adobe.com/thread/1042180
    •What version of Premiere Elements? Include the minor version number (e.g., Premiere Elements 12 with the 12.0.1 update).
    •What operating system? This should include specific minor version numbers, like "Mac OSX v10.6.8"---not just "Mac"
    •Has this ever worked before?  If so, do you recall any changes you made to Premiere Elements, such as adding Plug-ins, brushes, etc.?  Did you make any changes to your system, such as updating hardware, printers or drivers; or installing/uninstalling any programs?
    •Are you using an account with Administrator Privileges?
    Run as Administrator http://forums.adobe.com/thread/969395 (Encore + "All" Premiere)
    •Have you installed any recent program or OS updates? (If not, you should. They fix a lot of problems.)
    •What kind(s) of image file(s)? When talking about camera raw files, include the model of camera.
    •If you are getting error message(s), what is the full text of the error message(s)?
    •What were you doing when the problem occurred?
    •What other software are you running?
    •Tell us about your computer hardware. How much RAM is installed?  How much free space is on your system (C:) drive?
    And some other questions...
    •What are you editing, and does your video have a red line over it BEFORE you do any work?
    •Which version of Quicktime do you have installed?
    What is your exact brand/model graphics adapter (ATI or nVidia or ???)
    What is your exact graphics adapter driver version?
    Have you gone to the vendor web site to check for a newer driver?
    For Windows, do NOT rely on Windows Update to have current driver information
    -you need to go direct to the vendor web site and check updates for yourself
    ATI Driver Autodetect http://support.amd.com/en-us/download/auto-detect-tool
    nVidia Driver Downloads http://www.nvidia.com/Download/index.aspx?lang=en-us
    Some of the below is for Premiere Pro, but the idea is the same for Premiere Elements
    Dual video problems - Do you have dual graphics adapters?
    Go to the Windows Control Panel and select Hardware and Sound and then select Device Manager... In Device manager you click the + sign to the left of Display Adapters... and see if 2 are listed
    IF YES, read below
    -http://helpx.adobe.com/premiere-pro/kb/error---preludevideo-play-modules.html
    -http://forums.adobe.com/thread/1001579
    -Use BIOS http://forums.adobe.com/thread/1019004?tstart=0
    -link to why http://forums.adobe.com/message/4685328
    -http://www.anandtech.com/show/4839/mobile-gpu-faceoff-amd-dynamic-switchable-graphics-vs-n vidia-optimus-technology/2
    -HP Fingerprint/Password conflict http://forums.adobe.com/thread/911575

  • Premiere Elements 9 - "Sorry, a serious error has occurred that requires Adobe Premiere Elements..(2)

    Hi,
    I have the exact same problem as described here but the solution proposed here didn't work:
    Premiere Elements 9 - "Sorry, a serious error has occurred that requires Adobe Premiere Elements....
    I'm still getting the message "Sorry, a serious error has occured that requires Adobe Premiere Elements to shut down.  We will attempt to save your current project.".
    I uninstalled, reboot, installed, reboot a few times and it still doesn't work.
    Any suggestions?  I'm using Premiere Elements 9 and Windows 7, 64 bits.  It was working before.  It started after I had to reformat my harddrive and reinstall everything.
    Thanks,

    ...By the way, when you did that and deletion of the Adobe Premiere Elements Prefs deletion did not resolve the problem, did you then delete the whole folder in which the Adobe Premiere Elements Prefs file exists?
    [YH] Yes I did but it didn't work.
    1. When you did the uninstall/reinstall, did you include a ccleaner run through between the uninstall and the reinstall? Good idea to do that to remove any leftovers from incomplete uninstall reinstalls.
    [YH] Done but didn't work. I just ran the CCleaner free version.  I'm not sure if it's enough.
    2. Do you have the 9.0.1 Update installed.
    [YH] Done but didn't work.
    Do you have the latest version of QuickTime installed on your computer
    [YH] I didn't have QuickTime installed.  It is now but didn't do any difference.  I uninstalled Adobe Premiere Elements, ran CCleaner, reboot, installed APE, reboot... still doesn't work.
    3. Are you running your computer from a User Account with Administrative Privileges as well as Run As Administrator (from right click of program desktop icon and selection of Run As Administrator?
    [YH] Yes
    4. Is your video card/graphics card up to date according to the web site of the manufacturer of the card?
    [YH] I'm assuming yes because it was working before.
    5. Does the problem exist with and without the antivirus program disabled?
    [YH] I haven't tried yet but see item number 6 below.
    6. Go to Computer/Manage/Services and Applications/Services and assure that FLEXnet Licensing Service is started.
    [YH] I don't see any FLEXnet.  I don't remember installing this on any computer.  I googled it but I'm not sure I understand what and from where to install it.  I checked at work on another computer running Adobe Premiere Elements and FLEXnet is running on that computer. So this might be the source of the problem.
    7. The following is a version 12 remedy, let us see if this will work for 9.0/9.0.1
    As described in the link below, rename the SLCache Folder and the SLStore Folder.
    http://www.atr935.blogspot.com/2014/04/pe12-premiere-elements-12-editor-will.html
    [YH] Haven't tried it yet.

Maybe you are looking for