Pr CC sequences not compatible with Encore CS6

Dear Adobe,
Could you please consider doing one of the following:
1. Make a CC version of Encore
or
2. Release an update that will make Pr CC sequences compatible with Encore CS6
... I really miss being able to drag Premiere Pro sequences directly into Encore.
Thanks!
-Stefan
P.S.
I really like your products!

Both 1 and 2 are NOT going to happen... CS6 is the final Encore http://www.adobe.com/products/encore/faq.html
There is a link at the bottom of http://helpx.adobe.com/encore/kb/encore-cs6-installed-cc.html to a video tutorial on using EncoreCS6 with PProCC

Similar Messages

Bridge CC cache not compatible with bridge CS6

Starting the Photoshop CC adventure. First install was Bridge. First test was to see if the Bridge CC cache is compatible with Bridge CS6 cache. First result is NO.
Test method:
1. Set the Bridge CC cache location to the same folder I use for CS6, which contains 10+ gigs of thumbs for my library.
2. Navigated Bridge CC to a sub-folder with about 30 images, see Bridge CC re-do the thumb extractions.
3. Close Bridge CC, launch Bridge CS6, navigate to the same sub-folder, see Bridge CS6 re-do the thumb extractions.
4. Close Bridge CS6, launch Bridge CC, still pointing to the same sub-folder, see it re-do thumb extractions again.
5. Repeat steps 3&4, always with same result, a redundant re-generation of thumbs.
Conclusion:
The actual thumbnail files in the cache are the same. But something happens in the index files (data/store) to make each version think it does not have thumbnails, so it re-generates them. IOW, when Bridge CC looks at the cache last used by Bridge CS6 it says "I have not been here, must re-cache", and visa-versa.
Solution:
Must let Bridge CC have its own separate cache, so the two versions don't walk over each other. Must let Bridge CC re-cache everything, which for me (and most users I assume) will be a long and time consuming process.
Not much surprise here. The same was true for CS5 vs. CS6.

Not much surprise here. The same was true for CS5 vs. CS6.
Then it also should not be a surprise for you that this behavior already started in the Filebrowser (Bridge predecessor that came with CS1 and by far the most stable and fast cache ever in the history of Bridge) and has not changed since. Nor is it likely it will chance in the future.
Hence my advice to not use Bridge for long term DAM because you need to recache the lot every new version...

Nikon D7100 Not Compatible with Adobe CS6

I recently purchased a new Nikon D7100 DSLR camera and was quite surprised to find out that it is not compatible with my Adobe CS5 Standard Edition Suite software.
From the little bit of info I found online, it appears that non-upgradable changes to the Camera Raw component between versions CS5 and CS6 have made my software incompatible with my new camera. This means that with my CS5 Standard Suite I cannot open RAW image files in Bridge or Photoshop.
The only two options I have found so far are:
[1] Upgrade my software to CS6 or CC: For me this is cost prohibitive.
[2] Use Adobe's RAW to DNG converter and then open the image files as DNGs in Bridge and Photoshop: It appears that the DBG converter is reducing the file size and this I assume (rightly to wrongly) that it might also be reducing the image quality. To facilitate maximum options in image post production, I want to maintain the extreme detail that RAW provides. I am not sure if DNG will retail the exact same level of detail and quality. Can anyone shed additional light on this?
[3] Are there any other option that I have missed that would allow me to upgrade the Camera Raw component of CS5 so that it is compatible with newer DSLRs like the Nikon D7100?
Thanks in advance.
Regards
irwin

You have not missed any options for CS5 opening the raw data, directly. The D7100 requires at least CS6/ACR 7.4 or DNGC 7.4 that will make DNGs that will open in older ACR versions.
DNGs may different in size from the NEFs due to differences in lossless compression or a different-sized embedded preview image or even missing Nikon-only metadata in the DNG. In other words, the photosite values for the sensor data should be preserved but the packaging of, or the other data around, the sensor data may be different.
The cheapest option to make PS work with the native raw files is likely PS-CC for $10/month as part of the Photography Plan.
Another option is to purchase (serial number version) or rent (CC Photography Plan version) Lightroom and use it to do what you’d normally do in Bridge and ACR, and then use Edit In Photoshop w/in LR to do finishing touches in your older PS. This option renders a TIF or PSD to disk with all your raw-file adjustments and then passes this file to PS for further editing. The one caveat with buying the serial-number LR is that a new version of LR is probably about ready to come out and waiting until that new version is available would save money.
One thing to consider is that the PS-CS6/ACR 7.x has a new toning model which is an improvement for most images and you don’t have access to that if you’re not using at least CS6.
The reason Adobe doesn’t add new camera support to CS5 (and CS4 and CS3 and CS2 and CS and 7, 6, 5, 4, 3, 2, 1) forever is because they want to be paid for their work, and if every camera update was free forever people would only buy PS, once, and would keep using that without paying anything more until maybe the OS on their computer wasn’t compatible, anymore. This is one reason Adobe went with CC, so people would pay a little continuously and this constant cashflow would better match Adobe paying their employees continuously, instead of having to budget for the future based on how many new customers might buy an upgrade every 1.5 years or so.

New MacBook Pros not compatible with Adobe CS6

I am having constant crashes with inDesign cs6 on new MacBook Pro. Lost a lot of the functionality of my printer—NO LONGER DUPLEXES! That was the purpose of that printer. Anyone with similar experiences. Shame on Apple for not coordinating efforts with Adobe before release!!!

Shame on Adobe. Have you posted in their support forum?

I downloaded CS6 and am having issues with my print driver. It is not compatible with the HP 2600n and have tried to download drivers given to me by adobe ( (Jupiter 3) but it is not working. after a few days. Its a temporary fix and is still looking for

I downloaded CS6 and am having issues with my print driver. It is not compatible with the HP 2600n and have tried to download drivers given to me by adobe ( (Jupiter 3) but it is not working. after a few days. Its a temporary fix and is still looking for the HP driver when i boot up. It also will not save in any print or postscript format. Does anyone know how to fix?
Currently use a Mac with the latest Mavericks 10.9.4

Oh boy! Acting kind of weird seems to be an understatement, aquaequus!
What type of troubleshooting were we able to do with you? I want to make sure that we can get some sort of resolution for this problem.
It is quite possible the battery door may get your phone in working order again. I'm not sure if the store has it in stock, but it is available in our warehouse for $14.99 which can be ordered via customer service.
Tamara H.
Follow us on Twitter @VZWSupport

CS6 file "not compatible with this version of Photoshop"

We are using Adobe Creative Suit 6. Yesterday i've created a file, and today i cannot open it with any software. (Bridge shows the thumbnail but the file is corrupted.) I get the "Could not complete your request because the file is not compatible with this version of Photoshop" error. The file contains multiple layers, without any masks. Originally it was a NEF file (Nikon raw). I used vanishing point, because its an interior photo. (it doesnt relevant for the problem) I have an earlier version, where the vanishing points are defined, but the textures are missing. Main question is, how this can be??? I worked on that version for more than 2 hours. The file size is small, it's only 133.579.959 bytes (133 Mb). The image is 4288 x 2848 px, 240 DPI, RGB 8-Bit, Fogra39 ICC profile. The computer is up to date, nor the hw or the softwares are corrupted. The file saved locally, so it's not a network problem. I saved the document, and left the machine for about 15 minutes, then i went back, so the save had to be complete. (on SSD it took about a couple of secs) The biggest problem is, i have to work with a large amount of photos in Photoshop. But after this i have some bad feelings about this job. We have to create these PSD files both for ourselves and for our client for further use. (It's a huge furniture factory) The hardware has 16 gigs of RAM with an Intel i5 operating system Windows 8.1. Any ideas? (ps.: i didnt' find PSErrorlog.txt file) Oh i almost forgot. After installing CS6 my Adobe Acrobat Pro stopped working in about 2 weeks... So. The job is waiting, but we cannot wait for a long time, we gonna loose our biggest client because of a sw error?

You write this is not compatible with this version. Did you install all updates and did you update the camera raw too?

The file is not compatible with this version of photoshop / CS2 error -- Same File : CS6 no error / CS2 error , I need trouble shooting method, Please

the file is not compatible with this version of photoshop / CS2 error -- Same File : CS6 no error / CS2 error , I need trouble shooting method, Please

Save with Maximize Compatibility in CS6.
Choose Edit > Preferences > File Handling (Windows) or Photoshop > Preferences > File Handling (Mac OS).
From the Maximize PSD and PSB File Compatibility menu, choose any of the following:
Always
Then re-save your file so it can open in CS2

CS6 not compatible with mac retina display

I recently purchased the Adobe CS6 Design and Web Premium at school. (It's not the creative cloud)
Upon installing, I noticed that all of the programs are blurry. After a quick google search, it says that when a program is blurry it's not compatible with retina display.
I did an update on all the programs, and it seems like only photoshop and illustrator were updated to have retina display. The only other program I really need to be retina compatible is InDesign. I don't care about dreamweaver and such.
Anyone knows if there is an update for coming for that? Any work arounds, or who I need to contact to see what they can do? I spent a ton of money on this, and was not aware that there was a retina display issue, and my software is obviously now non-returnable.

There is nothing more to do. CS6 is now 3 years old and there simply won't be any further updates, be it just for simple technical reasons.
Mylenium

Encore CS4 not compatible with Windows 7 [32] ?!

just reinstalled Windows 7 [32 - ultimate] and Adobe CS4 Master Collection and I get this error message each time I try to start Encore: "Encore is not compatible with this version of Windows" I had it installed before, worked perfect, till now. when I force it to start it goes only till Import as asset, then it freezes, shows a blue screen, then the computer restarts. any suggestions?

Hi,
As you mentioned that you are using Encore CS4 on win 7. There was an issue with Encore CS4 being used on win 7.
There might be the case that the pxhelp is not compatible with win 7 (64 bit)
Install latest pxhelp from -
http://kb.roxio.com/search.aspx?URL=/content/kb/General%20Information/ 000070GN&PARAMS=
This has solved the problem of lot of people. I hope it works for you also.
Let me know if it solves your problem.
En CS5 and 5.1 are shipped with the correct version of pxhelp engine.
Thanks,
Ramesh.

" This version of CS6 Photoshop and Illustrator not compatible with my computer"

CS6 Photoshop and Illustrator are not compatible with my computer. Is there a downloadable version of CS6 Photoshop and Illustrator that is? I downloaded in both the CS6 Design and Web Premium and individually, neither worked. I have a Mac OS X Version 10.6.8

No. if that message comes up, you are running on an old first generation Core Duo processor on an iMac/MacBook/ Mac mini and it simply is not compatible, no matter what version of OSX. It lacks specific chip components required for the code.
Mylenium

Media pending with Encore CS6

Hello,
I have a very large project built with Premiere Pro CC.
The project has 5 "sequences" which are "rendered" before export to Media Encoder CC.
The "transcode" (max quality) runs very well but is very slow (Media Encoder does not use GPU even the "Playback Mercury Engine" is activated), this is worst without Playback Mercury Engine.
The transcoded files are imported within Encore CS6 (no dynamic link between Encore CS6 ane PP CC and no Encore CC version, Adobe decided this but with very bad reasons).
The Encore project has 5 "montages" and one "diffusion list", the menu has "animated" buttons and need to be rendered before creating the final disk (blu-ray).
But when I try the menus before creating the blu-ray disk I obtain :
- media pending message : the audio track is there but the video track appears lated and is not smooth,
- the animated button of menus are very curious : some are correct but others flash in red or green.
- the software Encore freeze with a white screen, then the job may be resume,
- the "complete title" begins normally then the video disappears but not the audio, after 10 seconds the video appears but seems to be frozen.
I checked the links of chapters and buttons, all works normally. The project checking give no error.
I never encountered this with Premiere Pro CS6 and Encore CS6 (dynamic link works).
How can I fix this strange situation without discarding PP CC and migrate to FCPX ?

Hello,
Many thanks for your very long reply and your interest in my problems.
I shall try to answer you :
- 1) OS : Windows 7 64 bits Pro SP1, french,
                 Version : 6.1.7601.18247 (Win7RTM)
                 Framework.NET : 4.0.30319.18408 built by : FX451RTMGREL)
                 DirectX : 11.0,
                 OpenGL : 6.1.7600.16385 (Win7_rtm.090713-1255).
- 2) Yes the media pending goes away but after a couple of minutes (one
year ago I was using PP CS6 and Encore CS6, I never had this problem
even with very long files),
- 3) Yes my GPU driver is updated (Nvidia GeForce 332.21 dated 12/19/2014).
I never had thiese problems with PP CS6 + Encore CS6 and my projects
built with these PP ans Encore version were with the same structure and
length (in PP CS6 : sequences up to 45 minutes, in Encore CS6 chapters
up to the same time).
The difference between are in my hardware :
- the RAM was upgraded from 12 GB to 24 GB,
- the CPU was overclocked from 3,2 GHz (default) to 3,88 GHz).
- 4) I shall try up to the disk burn to check if the problem is just due
to display of "animated buttons".
I hope my answer will be usefull for you.
Regards,
Jacques Gourier.
Le 11/02/2014 19:53, Stan Jones a écrit :
>
      Re: Media pending with Encore CS6
created by Stan Jones <http://forums.adobe.com/people/Stan+Jones> in
/Encore/ - View the full discussion
<http://forums.adobe.com/message/6110278#6110278

The saved printer information is not compatible with this version of Photoshop

Hello,
I hope somebody can help us. I am a IT Technician in a school, we have approx 500 Windows 7 64bit machines with about 600/700 users - 200 machines have the CS5.5 Master Collection installed on them. We have an intermittent issue with printing from Photoshop (both the 32bit and 64bit versions). Our printers are mostly HP LaserJet printers (all modern), but we have an Epson B-510DN Inkjet and some Xerox copiers too. The drivers are all installed on a central print server running Server 2008 R2 and shared via Group Policy to client machines.
In rooms where Photoshop is installed, intermittently when a student goes to print we will recieve the following error:
The saved printer information is not compatible with this version of Photoshop, or the saved printer is no longer available. You will need to check your printer settings before printing.
Photoshop will then grey out the 'Print' button and won't let the user print again. The odd thing is that we can still print from other software such as Microsoft Word or even non Microsoft software - even Illustrator will print. It just seems to be Photoshop thats has any issues.
This happens when printing to any printer on site, 90% of which are HP's. As a general rule we configure all of our HP printers with HP's PCL6 Universal Print Driver as it makes management of various printer models easy, and we haven't found it to limit us atall yet. We are aware the Adobe software is 'preferential' to Postscript drivers but our printers arn't, being HP's PCL is their native language. We have tried changing a printer to the Postscript UPD driver to test it but it made no improvement. We have also seen the issue quite indepth with our Epson B-510DN which is configured with Epson's latest model specific driver as our photography department use it. Since we are seeing it with different printers I don't believe the printer drivers are to blame - unless somebody want's to prove me wrong.
Like I say the problem is intermittent, and we are having trouble tracing it down to a user, computer or a software problem as it is so intermittent. Has anybody else seen this and managed to overcome it? Since it's only happening in Photoshop is it a bug that Adobe have recognosed and fixed in CS6? The only workaround we have found for it is to go into printers, chnage the defualt printer from one to another and back again - this seems to shut Photoshop up.
Thanks, Dave.

Chris,
Apologies for my slow reply - we have been busy here the past few weeks.
We are using a standard Microsoft provided JPG image (Tulips.jpg) so we have ruled out it being an issue with the image; perhaps if we were using a PSD, maybe so.
We have now found out what the issue is, and what the workaround for this bug is. All of our printers across our site are named in a specific format, usually [Location name] [Room number] [Mono or Colour] resulting in printer names such as Photography A11 Colour, Art A2B Colour and Design Technology A14 Colour. All of these names contain numbers. We have tried reimaging machines, reinstalling Photoshop, upgrading to CS6, deleting and reconfiguring printers with the same name. Finally the only solution that worked was to take the numbers out of the name, either by renaming or deleting and reconfiguring the printers. The Photography printer is an Epson B-510DN using a model specific driver and the other two use the HP PCL6 UPD driver, so I don't believe the drivers are to blame and since renaming the printers work I don't believe it's a configuration issue either. Remember that these printers are shared from a print server and deployed via Group Policy (using the Print Management method).
I hope this provides you Chris, and others searching Google, a useful explanation of the problem and what the fix is. As much as Adobe won't admit it's a problem/bug, I and many others across the internet believe that it is and that it should be fixed in future versions of Photoshop.
Thanks, Dave.

Photoshop CS5. Saved printer information is not compatible with this version of Photoshop

I am hoping someone has experienced this problem. I am working at a clients
office which has a large Konica Printer. When I first started using Photoshop at this office I
could print directly from PS to thier printers. Then a printer driver change or something I cannot pinpoint changed and I began getting the Error Message: The saved printer information is not compatible with this version of Photoshop, or the saved printer is no longer available. You will need to check your printer settings before printing. I click OK and the second Error Message appears: There was an error opening your printer. Printing functions will not be available until you have selected a priner and reopened any documents. The radio button has the single response word "Cancel". After clicking that button the printing is grayed out and until I go into Color Settings and change the setting drop down box to something else, close PS and reopen the, or any file and the same thing occurs. Ihad the IT department down here and after an hour he clicked on settings and tinkered around until all of a sudden the printing was enabled. It worked until the printer driver was updated. Once again the IT guy was down here and didn't remember what he did, tinkered around and after changing the color settings to: Monitor Color, it printed. Here we go again, printer settings were randomly changed so we reinstalled the printer driver and again PS is not printing.
Is there anyone who has experienced this issue who can help me make sense of this insanity. Is there a sequence of setting changes, opening of the program and file that is allowing the color management to stop interferring with my printing other than Gremlins in this machine? I have not found anything Googling on this issue. Please help me . . . Annette

I don't think I have an answer for you about exactly what went wrong, but one thing that can help with understanding the messages (and maybe can help you and your IT people figure it out) is this:
Photoshop saves the information about the last printer the document was printed to as metadata in the document file. So if you make a print then save the PSD, the printer info is in the PSD.
If recently you opened an image that had previously been printed at another place (and which didn't have an exact match to the printer available in your current location), then you can start to imagine these error messages making a bit more sense. Things like "The saved printer information" begin to have meaning.
Hope this helps.
-Noel

Cannot publish Webpart - "Invalid SPlistItem. The SPListItem provided is not compatible with a Publishing Page"

Hello All,
I have seen this error message discussed in other posts on the forums here but the solution of deactivating and reactivating server publishing/infrastructure are not working for me. In fact I encountered additional errors when reactivating publishing at
the site level. Powershell was necessary to reactivate site level server publishing.
Here is detail of the error I get when attempting to publish:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 18/11/2014 08:59:05
Event time (UTC): 18/11/2014 08:59:05
Event ID: e2e43649e2164e399fe0aa85892a002c
Event sequence: 165799
Event occurrence: 17
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1827921427/ROOT-1-130607489469090399
Trust level: WSS_Custom
Application Virtual Path: /
Application Path: C:\inetpub\wwwroot\wss\VirtualDirectories\portal.cooperstc.com443\
Machine name: CTCSP2
Process information:
Process ID: 7392
Process name: w3wp.exe
Account name: COOPERS\svcSPPortalAppPool
Exception information:
Exception type: ArgumentException
Exception message: Invalid SPListItem. The SPListItem provided is not compatible with a Publishing Page.
Request information:
Request URL: https://portal.cooperstc.com:443/CLG/Student/Videos/Pages/Test101.aspx
Request path: /CLG/Student/Videos/Pages/Test101.aspx
User host address: 10.33.50.119
User: COOPERS\yangro
Is authenticated: True
Authentication Type: Negotiate
Thread account name: COOPERS\svcSPPortalAppPool
Thread information:
Thread ID: 41
Thread account name: COOPERS\svcSPPortalAppPool
Is impersonating: False
Stack trace: at Microsoft.SharePoint.Publishing.PublishingPage.GetPublishingPage(SPListItem sourceListItem)
at Microsoft.SharePoint.Publishing.Internal.WebControls.PublishingPageStateControl.RaisePostBackEventForPageRouting(String eventArgument, SPRibbonCommandHandler control, RaisePostBackEventDelegate raisePostBackEventDelegate)
at Microsoft.SharePoint.Publishing.Internal.WebControls.PublishingPageSaveAndStopEditHandler.RaisePostBackEvent(String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

DeActive and then ReActivate Sharepoint Site Publishing Infrastructure feature at both Site And Web level Scope.
To Deactivate at web level, Open SharePoint Site. Click on Site Actions -> Site Settings, then click on Manage site features and then Deactivate Publishing Infrastructure feature.
Similarly you can deactivate at site level, Open SharePoint Site. Click on Site Actions -> Site Settings, then Site collection administration and then go to Site collection features. there deactivate Publishing Infrastructure feature.
To Reactivate again the feature, follow the above steps.
http://www.c-sharpcorner.com/Blogs/15338/invalid-splistitem-the-splistitem-provided-is-not-compatibl.aspx
1.The simple thing is to try deactivate and reactive the publishing features both at site collection and site level.
2. If the above doesn't work then proceed to below PowerShell script.
$site = Get-SPSite "http://www.mysites/ "
$web = $site.openweb()
$correctId = $web.Lists["Pages"].ID $web.AllProperties["__PagesListId"] = $correctId.ToString()
$Web.AllProperties["__PublishingFeatureActivated"]="True"
$web.Update()
3. The key point is PublishingFeatureActivated bag which has to be true .
http://webcache.googleusercontent.com/search?q=cache:5xpx-C9kKgsJ:nagendra-gunaga.blogspot.com/2013/11/the-splistitem-provided-is-not.html+&cd=4&hl=en&ct=clnk&gl=in
If this helped you resolve your issue, please mark it Answered. You can reach me through http://itfreesupport.com/

Print Studio Pro plugin is not compatible with Photoshop Elements 12 Editor for Mac

It appears that the latest version of Print Studio Pro PlugIn is not compatible with the Editor version of Photoshop Elements 12 for Mac as available on the App store. The install gives an error saying that it did not find a supported version of Photoshop Elements. This error has been reported before for Elements version 12 but was reportedly fixed in the latest version of Print Studio Pro. Now it appears that this version may support Elements 12 for Mac but not the Editor only version from the app store. Any suggestions for work-around on this?

"Any suggestions for work-around on this?"
No!
Not untill Mac and Adobe and Canon get their collective acts together. Mac (Apple) has the bad habit of upgrading their stuff and not being forthcoming with the particulars given to 3rd party companies like Canon and Adobe.
Besides the cost difference of Mac's the compatibility issues are it's worst features.
EOS 1Ds Mk III, EOS 1D Mk IV EF 50mm f1.2 L, EF 24-70mm f2.8 L,
EF 70-200mm f2.8 L IS II, Sigma 120-300mm f2.8 EX APO
Photoshop CS6, ACR 8.7, Lightroom 5.7

Pr CC sequences not compatible with Encore CS6

Similar Messages

Maybe you are looking for