SpeedGrade CC (2014) corrupting .psd files sent as clips from Prem Pro CC(2014)

I have embedded a Photoshop CC file (.psd) in a Prem Pro CC sequence. Each time I link the sequence to SpeedGrade, making sure I don't interfere with the .psd clip, the clip is returned to Prem Pro corrupted and have to restruscture and reinstall each time.
Is there something that I can do to prevent this or is this a bug?
Thanks in advance.
Paul

Similar Messages

My Office Print Pro 8600 Plus will not print pdf files sent to it from an iPad using ePrint.

My Office Print Pro 8600 Plus will not print pdf files sent to it from an iPad using ePrint. I just get an error message when I go to the HP Eprint centre. It does print the cover e-mail but nothing else. The attachment is not secure as far as I can see. I have tried sending an attachment from my Mac and that worked fine.
This question was solved.
View Solution.

Hello krnkln3.
Are you trying to send the PDF as an attachment in an e-mail sent to the ePrint e-mail address of the printer or are you trying to print using the ePrint app?
Try sending the same PDF document to the printer's ePrint e-mail address and let us know if that works. If this works but using the ePrint app is not working, maybe the ePrint app is not working fine with this PDF document (it could be due to it's size or something else). Remember that you can always use the e-mail ePrint address of the printer to send PDF documents as the processing is happening at the HP servers and not in your iPad as when you try to send it using the ePrint app.
Cheers!
Wixma.
I am an HP employee.
Say thanks by clicking the Kudos star in the post.
If my reply resolved your problem, please mark it as as Accepted Solution so that it can be found easier by other people.

DirectLink from Premier Pro CC 2014 to Encore - no longer there

Trying to get a Premier Pro CC 2014 sequence into Encore CS6 - and it won't happen.
The DirectLink from Premier Pro CC 2014 to Encore - is no longer there and I've tried simply dragging the required sequences over from the PP CC window into the timeline bin in Encore - it won't do it.
I've tried importing sequences and after clicking on the project to open and select the sequences from it just sits there with a portion of yellow progress bar about 5mm long - doesn't move on.
I am now trying to build the DVD project by putting all materials on one sequence, with chapter markers on it and pushing out a media encoder file in H.264 first. Maybe this will import to Encore.
Hating the fact these two sister programs no longer talk or work together - losing Encore is a major headache.

Thanks Stan,
Interesting you say "Dynamic link only works between like versions. So the only DL for Premiere with Encore CS6 is Premiere CS6" and then show me a video where the guy's first screen pops up with "Using Premiere Pro CC & Encore CS6".
This is the latterday workaround to cover the issue of the removal of the directlink from PP CC 2014 to Encore - which does cover my issue - however I find it strange that Adobe choose to make great play of the DirectLink facility - now employed between programs such as PP CC 2014 and SpeedGrade - yet have deliberately destroyed a great working relationship in the same manner between PP CC 2014 and Encore.
I find this "dictatorial" deduction a real nause...

Why remove .flv export from Premiere Pro CC 2014? And what's a good workaround?

Why remove .flv export from Premiere Pro CC 2014? And what's a good workaround?

OK, so you want to put it on your own web page. That's fine as long as you know how to create a web page.
The next thing you have to decide is how big do you want the video to appear on the web page. Many people just post on YouTube and then embed the video into their web page. That way, the video can take advantage of all of the various sizes that YouTube provides.
In any case, I suggest that you use H.264. But the data rate depends on the size of the file. If you are going to display it in HD, then you probably want to start at about 20Mb/s and go up or down from there. The required data rate depends on what you find acceptable, and that depends on the amount of movement in the video. For example, a talking head next to a white board explaining something requires a lot less bits to represent the image because less changes are taking place from frame to frame. If you use 10Mb/s for that, you might find 20Mb/s or more is required to make you happy if you shot a football game from the sidelines.
I generally use settings that look like this image. If you have any questions as to why I choose these settings, feel free to ask.

Is there a way to recover corrupted psd. files?

I recently transferred all my work from a work computer to my mac at home. i am unable to access my work computer until October as we are having a 'break'. However, I have a deadline for September 15th and I need all my files.
Some older files open perfectly fine but I fear there was a problem in downloading-perhaps due to my haste to leave and enjoy the beautiful weather!
I tried downloading a Remo Repair software but unfortunately this was unable to launch. Is there program out there that you would recommend in this instance for me to recover my psd files-which are of great importance!
Any help would be appreciated
Basic notes:
Created on Windows computer cs5
Trying to open on Mac cs5
Sd card used to transfer-couldn't eject, this may be the problem

It is most difficult to recover a corrupted file. Many have tried but almost all end up in failure. Try opening in another program. IF you can then "save as" and you can probably open in PS.
Do you have a backup? Do you still have original files on Win computer? These are your best bets. It is too late for these files, but I think you can see the necessity of having a backup on a separate HD or even on a disk.

PSD files sent over FTP given 1kb file size, archived, and have .bin appended to extension

I'm trying to deliver PSD files to someone over our server's FTP. If the FTP shared folder is accessed via a browser (like safari which is the main thing I've been testing on), the files in are listed as being only 1kb in size when each is approximately 60MB and all have had .bin appended to the .psd file extension. When the file is downloaded it's still 1kb and when opened it is associated with the archive utility which attempts to unarchive it and produces and identically named and extensioned file of 4kb size which cannot be opened by preview or text edit or photoshop.
Changing the extension does not help as suggested here http://forums.appleinsider.com/archive/index.php/t-25119.html . Also if the file is downloaded via 3rd party FTP software like cyber duck, though the file size is listed as 1kb, the correct size file is downloaded though still has the .bin extension. When this full sized .bin file is opened, archive utility instead of unarchiving attempts to archive it and produces a file roughly half the size which too cannot be opened. Speaking with apple care resulted in the suggestion that I use terminal command line to force the client to use binary mode when downloading the file which also downloads a file of correct size but with the .bin extension and that can not be opened.
Is this a known issue with PSD files? I've not come accross this before, the server is configured correctly and different file types are successfully downloading with no changes to size or extension and then opening as they should upon receipt at the client side.

Hi and thanks,
that was my next port of call but I stumbled across a more permanent fix. Mac OSX server automatically converts files sent over FTP to something called MacBinary on the fly and it seems this process doesn't agree with PSD files. Someone else encountered this problem back in 2003 and found this solution
http://forums.appleinsider.com/archive/index.php/t-25119.html
speaking to apple care they also sent a link for the official mac instructions for achieving the same thing here
http://support.apple.com/kb/TA20996
and here
http://support.apple.com/kb/TA20645?viewlocale=en_US
in the second explanation it's important to note for anyone attempting to follow this that if you're fixing the problem on MacOsX server rather than just MacOSX it isn't necessary to enable the root account as it is automatically enabled by default. Simply log out and log back in as root and use the same password as the first administrator account you set up when the server was first configured.

Photoshop CS4 11.0.1 crash upon save, leaves small sized corrupt PSD file

Hi!
I've just updated our retouchers Photoshop CS4 to 11.0.1 but one of the issues we had with 11.0.0 remains. The problem doesn't happen that often, but since the result is an unusable .PSD file it's pretty nasty...
Sometimes when saving Photoshop crashes and the .PSD that was to be saved becomes a small (68 KB in the last example) and unusable.
The hardware/software we have:
Mac Pro 2.66 GHz (some with 5 GB RAM and some with 9 GB RAM)
Mac OS X 10.5.6
Photoshop CS4 Standard (updated to 11.0.1)
People work on server volumes shared via AFP. I've heard saving over the network isn't supported, but there's no other way, plus this issue never happened in CS3 so...
Any ideas on what can be done?
Below is the latest crash log:
Process: Adobe Photoshop CS4 [41265]
Path: /Applications/Adobe Photoshop CS4/Adobe Photoshop CS4.app/Contents/MacOS/Adobe Photoshop CS4
Identifier: com.adobe.Photoshop
Version: 11.0.1 (11.0.1x20090216 [20090216.r.522 2009/02/16:17:00:00 cutoff; r branch]) (11.0.1)
Code Type: X86 (Native)
Parent Process: launchd [84]
Date/Time: 2009-03-24 11:04:07.914 +0100
OS Version: Mac OS X 10.5.6 (9G55)
Report Version: 6
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000008
Crashed Thread: 0
Thread 0 Crashed:
0 com.adobe.Photoshop 0x00748248 0x1000 + 7631432
1 com.adobe.Photoshop 0x004d962d 0x1000 + 5080621
2 com.adobe.Photoshop 0x004dda2f 0x1000 + 5098031
3 com.adobe.Photoshop 0x004dedba 0x1000 + 5103034
4 com.adobe.Photoshop 0x004a6a58 0x1000 + 4872792
5 com.adobe.Photoshop 0x000821ad 0x1000 + 528813
6 com.adobe.Photoshop 0x00082bdb 0x1000 + 531419
7 com.adobe.Photoshop 0x00acb564 0x1000 + 11314532
8 com.adobe.Photoshop 0x004a5f6e 0x1000 + 4869998
9 com.adobe.Photoshop 0x00077f9e 0x1000 + 487326
10 com.adobe.Photoshop 0x0006b9ed 0x1000 + 436717
11 com.adobe.Photoshop 0x00069906 0x1000 + 428294
12 com.adobe.Photoshop 0x00063d65 0x1000 + 404837
13 com.adobe.Photoshop 0x00063ed3 0x1000 + 405203
14 com.adobe.Photoshop 0x0006222f 0x1000 + 397871
15 com.adobe.Photoshop 0x002206aa 0x1000 + 2225834
16 com.adobe.Photoshop 0x00220736 0x1000 + 2225974
17 com.adobe.Photoshop 0x00003912 0x1000 + 10514
18 com.adobe.Photoshop 0x00003839 0x1000 + 10297
Thread 1:
0 libSystem.B.dylib 0x92893906 kevent + 10
1 libSystem.B.dylib 0x92894095 _pthread_start + 321
2 libSystem.B.dylib 0x92893f52 thread_start + 34
Thread 2:
0 libSystem.B.dylib 0x9286320e semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x92895206 _pthread_cond_wait + 1267
2 libSystem.B.dylib 0x928da539 pthread_cond_wait + 48
3 com.adobe.amt.services 0x04da4552 AMTConditionLock::LockWhenCondition(int) + 46
4 com.adobe.amt.services 0x04d9f995 _AMTThreadedPCDService::PCDThreadWorker(_AMTThreadedPCDService*) + 115
5 com.adobe.amt.services 0x04da45b0 AMTThread::Worker(void*) + 20
6 libSystem.B.dylib 0x92894095 _pthread_start + 321
7 libSystem.B.dylib 0x92893f52 thread_start + 34
Thread 3:
0 libSystem.B.dylib 0x9286a3ae __semwait_signal + 10
1 libSystem.B.dylib 0x92894d0d pthread_cond_wait$UNIX2003 + 73
2 libGLProgrammability.dylib 0x95affb32 glvmDoWork + 162
3 libSystem.B.dylib 0x92894095 _pthread_start + 321
4 libSystem.B.dylib 0x92893f52 thread_start + 34
Thread 4:
0 libSystem.B.dylib 0x9286321a semaphore_timedwait_trap + 10
1 ...ple.CoreServices.CarbonCore 0x9237449b MPWaitOnSemaphore + 125
2 MultiProcessor Support 0x1

This is the boilerplate text I use in connection to saving to a network (please NOTE the part where it explains that
normally, it does work
, but that it is impossible to troubleshoot someone else's network remotely, and that's why it's not supported by Adobe):
If you are opening files over a network or saving them to a network server, please
cease and desist immediately
in the event you are currently experiencing problems with one or more files.
Working across a network is not supported.
See:
http://www.adobe.com/support/techdocs/322391.html
Copy the
CLOSED file from your server to your local hard disk, work on it, save it again to your local hard disk, close it, and copy the closed file back to the server.
Of course, the fact that Adobe does not support working across a network does not necessarily mean it won't work. It should.
Adobe's position is that there are too many variables in a network environment for them to guarantee that everything will work correctly in every network, especially given the fact that if something does
not work properly, it's probably the network's fault, and Adobe has no way of troubleshooting your network.
If you can't work locally, you are on your own, and if something happens, you're on your own. If you must work from a server, make sure your network administrator is a competent professional.
When problems arise, a lot of valuable work can be lost.

How do I recover a corrupt PSD file?

My last save of a 1.5GB PSD file went without a hitch. Routine save, as I always do before closing Photoshop (using CTRL-S). The save was not interrupted in any way, nor did it behave differently than it did the previous 100 times I saved this particular file.
However, upon reloading, now the progress bar stalls at appx. 30% before the thing gives me a disk error.
I have 600GB and 700GB free on both of my hard drives, so disk space is not the problem.
I tried loading the file with both Photoshop CS4 and Photoshop CS4 64-bit Edition. Both produce the same results. Disk error.
Rebooting did not change anything.
I tried copying the file to another location, but I get a "Cannot read from source disk" error.
But it's there, seemingly full size, with two weeks worth of work in it.
I ran a Google search for PSD recovery tools, and there are several commercial products claiming to be able to help. But I wanted to know if Adobe provided one first, then if anyone ever tried any of the other tools out there and saw it actually work.
Thanks!

function(){return A.apply(null,[this].concat($A(arguments)))}
mjyeager wrote:
I'd really feel more comfortable using Windows 7 repair tools at this juncture, before anything else.
I mean, these are all "Bad Block" disk errors. What's the worst that can happen?
What non-Windows repair tools have I advised you to use? I suggested a full System Image backup, using Windows Backup.
It's not a software problem, it's a confirmed hardware failure. Software repair tools will not fix it. This is experience talking.
The worst that can happen is that the drive will fail completely and you will lose all your data. And yes, even Caviar Black drives do fail.
If something under the hood of your car goes boom and you lose power, do you just floor it to maintain speed so that you can keep driving? No. You stop immediately, to take the stress off your engine so that you don't compound the problem. Something like a CHKDSK /R would exercise heck out of your drive - the very thing that's failing. Is that really what you want?
-Noel

PSD files will not print from Photoshop CS4 (previously posted in Acrobat printing and prepress)

My questions are: Does the PSD file have the printer information encoded?
Also why has this just started to show up? My wife has work successfully under the same conditions, files moved and printed on different printers, with no problems in the past.
I (we) have been struggling with a recent problem trying to print PSD files from Photoshop CS4. (Vista 32 bit, Epson 3880 networked) When trying to print certain, but not all, PSD files I get the message: "Before you can perform printer-related tasks such as page setup or printing a document, you need to install a printer." I have been in contact with Adobe support about the issue but with little in the way of positive results. I was referred to a kb link: http://kb2.adobe.com/cps/409/kb409119.html Tried all that to no avail. (The first suggestion is absurd to the point of making me wonder what process is used to construct the kbs. You cannot open the print menu when you get this message so....?)
Other solutions are not acceptable for the work my wife is doing, editing high quality photographs for an exhibition with test prints and so on. We are under intense time pressue with four shows coming up in a very short time. The final solution offered is that CS5 has solved all of this. Hum? interesting. No comment except new program, new problems so not a real solution for us.
In searching the web about this problem I have come across many other people with the same problem working from different platforms and even different Adobe products. I noticed that the MAC OS seemed to cause the same problem and that there was a problem with Reader and Acrobat. In every case the problem is never solved by Adobe or anyone else and users find some "workaround". I too have found what we hope is a workaround in our contiued travels on the blogosphere, on flickr http://www.flickr.com/groups/wellington/discuss/72157621548183001/ as "...a nasty, nasty solution" but we skipped the flatten part and the GIMP part and resave the PSD under a different name.
Adobe does seem supportive but not that interested (CS4 right) but I would like to find a real solution and I think many people would benefit from it.
Anyway what I have found is that the PSD files that will not print have been printed on another printer at some time in the past. In my case the Printer was an Epson Artisan A50. The printer we are using now is the Epson Stylus Pro 3880. Even when trying to print wirelessly to the 3880 from the laptop (Was Vista, now Windows 7) that was used to edit and print with the A50, (USB connection) we saw the same error. So it seems that the printer information is somehow embedded in the PSD file (also mentioned in a Blog) and is keeping PS from seeing the printer because the same printer is not there.
Has anybody already found the fix?
I know this is a long post but I have been working on this problem and have heard all of the pat and frankly useless answers and workarounds. Can we find a solution and fix the problem?

Just a few examples, since you ask:
Dr Craig wrote:
…The first suggestion is absurd to the point of making me wonder what process is used to construct the kbs…
…Other solutions are not acceptable…
…The final solution offered is that CS5 has solved all of this. Hum? interesting. No comment except new program, new problems so not a real solution for us…
…In every case the problem is never solved by Adobe or anyone else and users find some "workaround"…
"...a nasty, nasty solution"…
…Adobe does seem supportive but not that interested (CS4 right)… b
…I have been working on this problem and have heard all of the pat and frankly useless answers and workarounds…
That attitude, Dr. Craig. Plus the verbosity you unconscionably inflicted on your fellow forum users.
Cheers.
Wo Tai Lao Le
我太老了       (Not posting as a scientist here
                           but as a Photoshop user
                           so I'll forego listing any unrelated academic titles.)

How can I open psd files into Potoshop CC from bridge

PSD files will not open into Photoshop CC from Bridge CC. I get this error message...“Windows cannot find, C:\program files\adobe\adobe photoshop CS5 (64 Bit)\photoshop.exe.” I can open jpeg, tiff and raw. I'm using Windows 7. I do not have CS5 on my computer. Help...

You must have uninstalled CS5 after you installed CC. Your registry is fouled up. You can either uninstall CC, run the Script Cleaner and reinstall, or fix registry as below.
After looking at a new user's registry HKEY_CURRENT_USER and comparing it to the one on the original user, I found a registry value which was not changed, and should have been.
I found a key:
HKEY_CURRENT_USER\Software\Classes\Applications\Photoshop.exe\shell\op en\command
This key was set to the path for Photoshop CS6 when it should have been set to Photoshop CC.
In other words, in my case, it was set to:
"C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Photoshop.exe" "%1"
When I changed the CS6 to a CC, in other words, so the whole key reads:
"C:\Program Files\Adobe\Adobe Photoshop CC (64 Bit)\Photoshop.exe" "%1"

Bring in another .psd file with the clipping path

Okay, this client has a very odd request. They want a collage of images put together in one file and they want the clipping paths to be attached. Then it's to be saved as an eps file. I'd like to do this in InDesign and am going to be posting this same question there as well. I like that in InDesign, the clipping path stays attached to the image when you move it. However, is there a way to do this in Photoshop? I don't know how to bring .psd files into Photoshop along with their clipping paths. If there is a way to do this, is there a way to link the clipping path to the layer so that when I move the individual layers, the clipping path moves with it?
Help would be greatly appreciated! Thank you!

In Photoshop "Clipping Path" is a special kind of Path and limited to one per image and not linked to one Layer.
A work-around to combine multiple images with individual Clipping Paths into one psd file with a combined Clipping Path could be
• applying the Clipping Paths as Vector Masks to the images (flattened to one Layer or converted to a Smart Object each),
• combining them and after positioning/transforming/…
• copy/pasting the individual Vector Masks into one new Clipping Path.

Bring in .psd file along with clipping path

Okay, this client has a very odd request. They want a collage of images put together in one file and they want the clipping paths to be attached. Then it's to be saved as an eps file. I'd like to do this in InDesign rather than Photoshop because the clipping path stays with the image in InDesign when you move it. However, I don't know how to save the file as an .eps file with the clipping paths attached. I open the .eps files in Photoshop and there are no clipping paths present.
Help would be greatly appreciated! Thank you!

My suggestion is to compose the entire collage in Photoshop. And if you need to preserve the clipping paths of each image of the finished collage, then convert the clipping path to a vector mask. Then you can drag a layer (that will include image and path) into one photoshop file to make collage.
Here are the instructions from previous post to convert a path into a vector mask.
To create a vector mask in PS, select the path in the Path Panel, then under Layer menu > Vector Mask > Current Path.

Exporting from Premiere Pro CC 2014

Hello there,
Every time that I am willing to export my project my Premiere Pro CC 2014 stop responding all together. I tried the short cut (Commend+M) or going through the Manu bar. the result is the same, Premiere Pro CC 2014 just freezes and does not respond to anything till I force quit it and restart it allover again. I tried exporting from Premiere Pro it self, without using Media Encoder, but the problem remains the same.
I am using the new Mac Pro. I heard Adobe Premiere Pro is experiencing problems with the New Mac Pro. Is that true? Or is there other issue?
Thank you and looking forward to hear back,
Maruf

Hi Maruf,
Maruf Noyoft wrote:
Kevin,
I reset as you suggested and it took care of it.
Great!
Maruf Noyoft wrote:
So, if you don't mind explaining me the cause of the problem that I had? Or
an article about it. It is just for me for getting to know better the program and the system.
Thank you very much and appreciate your help enormously.
Since preference files get touched by the application frequently, there is always the possibility of their corruption. When this happens, you start to see what we call "unexpected behaviors" from Premiere Pro. This problem happens infrequently, but it is a good first troubleshooting step to try on your own. This is the case with most every non-linear editing application I have used over the years (Final Cut Pro, Avid, Media 100, etc.).
Thanks,
Kevin

I'm having problem with exporting video from premiere pro cc 2014

I'm using Adobe Premiere Pro CC 2014 and I'm having problem with exporting video.
When I click Export and media, the window for exporting appears and it starts exporting video.
But after a few minutes, it looks like it has completed exporting video and says there's a bug in exporting.
It literally says it has a problem with compiling, but I don't know what the real problem is.
I tried many things like restarting computer and Premire Pro but it's no use.
But it works when I use Adobe Media Encoder CC 2014 for exporting video.
If anyone knows any possibilities about why this problem happens, please let me know.

I'm having a similar issue. When I go to export my project, I add it to the render queue, set it up with the h.264 settings that I've used with countless past versions of the program, and then hit render. Randomly, at some point in the process, the render just stops and the ETA just keeps climbing. I actually had to save an XMF file of the CC 2014 project and bring it into the previous CC version of Premiere just to finish it. Even a clean re-install of CC 2014 doesn't work.

Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP

My recent update to Adobe CC 2014 apps has been an unmitigated disaster. Was running the 2013 version until last week and everything was just dandy. Very good performance and excellent render/encode times even for stuff with lots of filters and fx.
Since update 1-2 min videos with no fx or filters (or even transitions) have gone from exporting in under two minutes to well over 25 minutes. These exports are with the same presets I regularly use (Vimeo 720HD H.264).
I've been poking around the forums here for two days looking for answers and can't find anything that works. Tried the whole "App Nap" toggle as well as a few other tips. Didn't do squat. Looking for any hints/answers. Thanks.
Mac Pro Mid 2012
2 x 2.4 GHz 6-Core Intel Xeon
32 GB 1333 MHz DDR3 ECC
ATI Radeon HD 5870 1024 MB
OS X 10.9.5 (13F34)
System SSD 500GB
Cache SSD 500GB
Media HD 1TB

Hi MXSw,
MXSw wrote:
All right. More experimentation has been done. Seems like the renaming of Adobe folders fix prescribed in the link below might have helped a bit.
Premiere Pro CC 2014 renders are painfully slow.
You can rename folders, but I prefer to do it this way: Premiere Pro CC freezing on startup or crashing while working (Mac OS X 10.9, and later)
MXSw wrote:
Kicked out a 1 minute edit with some color/fx in under 10 minutes. Not as fast as in the past but at least the CPU seemed to be cranking at 500% and above per Activity Monitor. Its barely gone over 250% in previous attempts.
That sounds a lot better.
MXSw wrote:
Same 1 minute edit took 35 minutes however when I exported from a PP timeline using MXF clips instead of QTs. I assumed the QTs would speed up the process but in the past I've gotten great performance on big old RED raw files so still a bit of mystery why I can't approach the speeds I had prior to most recent CC update.
Maybe updating your project file has something to do with it. I'll keep my eye on this issue. Thanks for reporting.
Regards,
Kevin

SpeedGrade CC (2014) corrupting .psd files sent as clips from Prem Pro CC(2014)

Similar Messages

Maybe you are looking for