Photo Jpeg codec

Does any apple VP of software know if Final Cut Pro supports the photo jpeg codec?

From the responses I need to clarify. Is there anyone on this forum or at apple that has first hand knowledge that FCP 6 or 7 can edit clips that have the photo jpeg codec in a timeline correctly using simple transitions( dissolves, wipes)?
FCP 5 could do this with no problems. What changed? Is it operator error? I am willing to push the right keys to make it work.
Is it a legal issue over the photo jpeg codec? Is apple just not supporting it now that prores is here? Did the FCP dev team forget to carry the 1?
The only work around that converted or transcoded the clips without altering the clips values was an adobe product. Using a third party to correct the problem or staying with FCP 5 does not seem right.
Looking for someone to show us the way.

Similar Messages

QuickTime 7.1.5 photo-jpeg codec problem

After upgrading to version 7.1.5, all the movies with photo-jpeg codec play with jumps (aprox 5 frames)
If I check "play all frames" it plays smooth as always.
Any idea / solution?
Thank you.

Others have reported something similar. Can you go into System Preference, then QuickTime, Advanced, Mime Settings, and let us know what items are selected in the Miscellaneous part of the list? Flash Media should not be selected, but I want to know if it currently was for you.

I want to photo jpeg codec for render vdo in cs6 to do it. thank you.

I want to photo jpeg codec for render vdo in cs6 to do it. thank you.

Do you mean Premiere Pro CS6?
If yes, I will move your message to the Premiere Pro forum
Do you mean Motion JPEG?
MJPEG http://forums.adobe.com/thread/730396
Also, More information needed for someone to help... please click below and provide the requested information
-Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840

HT201066 Why does "New Screen Recording" record in Photo-JPEG codec?

Something's changed on me... Now when I use QuickTime to record (using "New Screen Recording"), it records the portion of the screen I've selected same as always but the resulting file is way fat.
Get Info says its recorded as: codec Photo-JPEG.
It used to record in H.264 but now it's a bloated file and this screwy wrong format.
Why?
How do I change it back to record screen as a H.264 file?
I see only options for Quality: Medium or High. (I choose Medium.)
I'm using latest Lion and QT.
Any ideas...? Thanks

Further research answered my question. Found my answer posted by QuickTimeKirk on a related topic:
"There are two options for quality in the screen recording set up (Medium and High). Medium uses Photo-JPEG codec and High uses H.264. Medium quality actually makes much higher file sizes."
My thanks to QuickTimeKirk. Since I haven't seen any of this extremely helpful info posted here or in a Google web search, I must assume I'm the only idiot on the block. However, let's get the word out.

Compressord crash, photo jpeg codec

Hi, having a rather severe issue here where several machines are experiencing problems with multiple photo-jpeg encoded files, .. trying to export to a variety of codecs (separately). All are G5's running fairly recent versions of Tiger.
A sample crashlog follows below (noncrashed threads omitted, binary images descriptions omitted.. Do you need them?)
Any help would be greatly appreciated.
-Xel
Host Name: (omit)
Date/Time: (omit)
OS Version: 10.4.5 (Build 8H14)
Report Version: 4
Command: compressord
Path: /Library/Frameworks/Compressor.framework/Resources/CompressorTranscoder.bundle/ Contents/MacOS/compressord
Parent: qmasterd [131]
Version: ??? (???)
PID: 4381
Thread: 6
Exception: EXCBADACCESS (0x0001)
Codes: KERNINVALIDADDRESS (0x0001) at 0x06082000
Thread 6 Crashed:
0 ...ickTimeComponents.component 0x02117b94 DecodeBlocks + 948
1 ...ickTimeComponents.component 0x02119228 getyuvMB + 300
2 ...ickTimeComponents.component 0x0211e920 jpegdecompress + 2560
3 ...ickTimeComponents.component 0x02106fd4 JPEG_DDrawBand + 1360
4 ...ple.CoreServices.CarbonCore 0x90b5bafc CallComponentFunctionCommon + 1044
5 ...ple.CoreServices.CarbonCore 0x90b5b684 CallComponent + 260
6 ...ickTimeComponents.component 0x0288a6e4 ImageCodecDrawBand + 40
7 ...ickTimeComponents.component 0x0210329c BaseCodec_DecompressWorkFunction + 1204
8 ...ple.CoreServices.CarbonCore 0x90b6e8f4 InvokeComponentMPWorkFunctionUPP + 24
9 ...ickTimeComponents.component 0x021017ec BaseCodecDecompressCallBackCommon + 2064
10 com.apple.QuickTime 0x8fadabc0 ExecuteCallBack_priv + 108
11 ...ickTimeComponents.component 0x020f5838 rescheduleTimeCallBack + 372
12 ...ickTimeComponents.component 0x020f58e0 CodecClockTimeChanged + 36
13 ...ple.CoreServices.CarbonCore 0x90b5bafc CallComponentFunctionCommon + 1044
14 ...ple.CoreServices.CarbonCore 0x90b5b684 CallComponent + 260
15 ...ickTimeComponents.component 0x02896ff0 ClockTimeChanged + 40
16 ...ickTimeComponents.component 0x020f54fc CodecClockSetTime + 116
17 ...ple.CoreServices.CarbonCore 0x90b5bafc CallComponentFunctionCommon + 1044
18 ...ple.CoreServices.CarbonCore 0x90b5b684 CallComponent + 260
19 com.apple.QuickTime 0x8fada96c QTCodecClockSetTime + 40
20 com.apple.QuickTime 0x8fcd20a8 SetDSequenceNonScheduledDisplayTime + 136
21 com.apple.QuickTime 0x8fcd4fe0 ICMDecompressionSessionSetNonScheduledDisplayTime + 88
22 ...ickTimeComponents.component 0x0226c170 NuOutputVideoPass + 2420
23 ...ickTimeComponents.component 0x0226c3d8 NuOutputVideo + 84
24 ...ickTimeComponents.component 0x0225ce3c SpitMovieFromProceduresToDataRef + 1832
25 ...ple.CoreServices.CarbonCore 0x90b5bb1c CallComponentFunctionCommon + 1076
26 ...ple.CoreServices.CarbonCore 0x90b5b684 CallComponent + 260
27 com.apple.QuickTime 0x8fc0ba98 MovieExportFromProceduresToDataRef + 44
28 ...pple.compressor.transcoding 0x7d73d6dc stomp::CQTSpitTranscoder::run() + 852
29 ...pple.compressor.transcoding 0x7d72dadc stomp::CStompTranscoder::_processRequest(swamp::IServiceRequestRef const&) + 3148
30 ...pple.qmaster.ServiceControl 0x7ee86028 swamp::CServiceControllerThread::runOnce() + 1120
31 com.apple.AECore 0x7f902c70 aecore::CThread::runThread() + 60
32 com.apple.AECore 0x7f900690 threadProc(void*) + 16
33 libSystem.B.dylib 0x9002b1e0 pthreadbody + 96
Thread 6 crashed with PPC Thread State 64:
srr0: 0x0000000002117b94 srr1: 0x100000000200d030 vrsave: 0x0000000000000000
cr: 0x48002244 xer: 0x0000000020000000 lr: 0x0000000000000006 ctr: 0x0000000000000019
r0: 0x0000000000000007 r1: 0x00000000f007d640 r2: 0x000000000000001e r3: 0x00000000000000ff
r4: 0x0000000000000001 r5: 0xffffffffffffffff r6: 0x0000000053b763ff r7: 0x0000000063ff0000
r8: 0x0000000006081fff r9: 0x00000000000000d9 r10: 0x0000000000000014 r11: 0x0000000006081fff
r12: 0x0000000000000024 r13: 0x0000000000000002 r14: 0x000000000034db20 r15: 0x0000000000000005
r16: 0x0000000000000009 r17: 0x0000000001863002 r18: 0x0000000001863000 r19: 0x0000000001863008
r20: 0x0000000000000000 r21: 0x0000000001863864 r22: 0x00000000f007d68e r23: 0x0000000001855a00
r24: 0x0000000000000014 r25: 0x0000000000000800 r26: 0x00000000028fc700 r27: 0x00000000f007d7b0
r28: 0x0000000001863970 r29: 0x000000000000000c r30: 0x000000000000002a r31: 0x00000000021177ec

From the responses I need to clarify. Is there anyone on this forum or at apple that has first hand knowledge that FCP 6 or 7 can edit clips that have the photo jpeg codec in a timeline correctly using simple transitions( dissolves, wipes)?
FCP 5 could do this with no problems. What changed? Is it operator error? I am willing to push the right keys to make it work.
Is it a legal issue over the photo jpeg codec? Is apple just not supporting it now that prores is here? Did the FCP dev team forget to carry the 1?
The only work around that converted or transcoded the clips without altering the clips values was an adobe product. Using a third party to correct the problem or staying with FCP 5 does not seem right.
Looking for someone to show us the way.

I am having problems exporting my time lapses from quick time pro i need to save my files as photo jpegs but the standard video compression window will not open fully,

i am having problems exporting my time lapses from quick time pro i need to save my files as photo jpegs but the standard video compression window will not open fully, it just keeps my mac (old 1.6Ghz 2.5 GB sdram G5 still good for most stuff i need) spinning for ever but i can see compression type H.264 selected and the other setting but i can not select any other options as it still thinking but never opens! why is this happening how do i get round it?
my work flow is: 300 images shot on a 5d mark II medium jpegs opened in Light Room cropped to 16:9 then exported and opened in quick time i can save a .mov H264 giving me files sizes of 14 mb for a 16 second time lapse, mp4 9 mb. the only way i can get large files is saving as a self contained movie then i get 300mb files.
i need to save my files 1920 x 1080 photo jpeg codec as i want HD quality.
i am sure there is a simple way round this?
thanks guys!

It is very difficult to offer troubleshooting suggestions when the "os version" you are using is unknown as each os has their own troubleshooting solutions.
How large is your hard drive and how much hard drive space do you have left?

Final Cut Pro 6.0.3 Problem with Photo JPG Codec ?

Hi everyone...
I have been working with music videos for several years using FCP 5.x and photo-jpeg codec, everything works fine. As time going by now I have updated my FCP using 6.0.3 with hopes to get better features. But unfortunately FCP 6 has problem with photo-jpeg codec. The problem is when I load a photo-jpeg video, the gamma will changes every time the playback head is start or stop. And I can't using video transition (standard cross-dissolve) anymore because the video gamma also change at the in transition and out transition. It also appear in my video monitor and output file ! I have searching all day to find out what is exactly the problem, but never get the solution. Should i come back to FCP 5.x ? Is it a BUGS or what ? What happen with Apple, why they let this happened ?
For information the video is in SD PAL & captured using Blackmagic Decklink card.
Please help,...Thanks.

Welcome to the discussions...
I believe this has to do with using YUV or RGB as the rendering method. RT is always RGB, but try changing the setting for your timeline to whatever it is not now...
post back,
Patrick

Adobe CS4 Media Encoder doesn´t encode Quicktime Photo-Jpeg

hi,
i´ve seen similar entries in that forum,but none fits to my problem.. so i hope to get some help. i´m working on a suitable vista-64bit machine with premiere pro cs4.1 and quicktime 7.6 (checked for updates today again).
i´ve got a 9min project in my timeline,i want to export it as a quicktime with the photo-jpeg-codec. the media encoder is loading the project,then it does nothing,no rendering at all. i wonder why,because the default setting for qt-dvpal works pretty well and fast(,but the quality is bad).
Now i´ve opened the project in aftereffects and used it to render,but it took about 40min.... this can´t be the solution. does anybody know better?

If memory serves, that option is currently broken through Premiere. AE may be the only way.

Color issue exporting Photo JPEG

Hello everyone,
I'm new to these forums, and somewhat new to using Adobe. I have used Adobe CS5 in the past and would like to start using Creative Cloud. Premiere Pro and After Effects in particular.
One of the things I need to do is create stock footage, particularly exporting in the Quicktime Photo JPEG codec. This has always gone without any hassle in CS5, but I ran into a color issue with the Creative Cloud version. After preparing a clip and exporting it, the colors differ substantially, the greens and blues in particular. I import these files to compare them inside Premiere, and the difference is very noticeable.
Here are two screenshots of the exported file and the original one, respectively.
I have spent a day trying to figure out what is going on, and can't find any real leads. I found some suggestions about the way Apple has coded their gamma color into Quicktime that wouldn't correspond with CC. However, this may be totally unrelated. I'm not a color expert, so I hope some of you can help me out.
Best regards,
Stef

I've just discovered this problem as well (thanks to your post elsewhere).
It's definitely a CC issue, and it's troublesome. It looks to me even more obvious than the sample you gave above. There seems to be a luminance increase in at least the green channel, and perhaps red or blue as well.

FCP 6 Gamma Photo jpeg

In FPC 6 the photo jpeg work flow has been changed. Gamma tags on photos can be set in FCP but not mov files. If you use photo jpeg codec , FPC6 can not render its transitions ( like dissolves, wipes ) with proper gamma levels. This also affects the new compressor. Photo jpeg gamma levels are changed. File footage libraries (Artbeats) that sell their clips using the photo jpeg codec must be re-rendered at the time of this post.
If anyone knows of a fix for Photo Jpeg RGB workflow in FCP 6 please let us know.
Thanks

I re-encoded my source material to find an alternative codec to get around this bug in FCP 6.
I found that Motion JPEG B at 100% quality gave similar file sizes to Photo JPEG and work with simple transitions in FCP 6.
I was also pleasantly surprised at how well my older dual 2.5 ghz G5 was able to process the lossless TIFF codec.
I subsequently found the following link regarding this codec:
http://www.siggraph.org/education/materials/HyperGraph/video/codecs/MJPEG.html
Mac OS X (10.4.9)

Interlacing for photo-jpeg movie

I originally posted this in the compressor forum. Forgive me for posting again here - I had no response at all on the compressor forum...
I'm encoding a DV movie into photo-jpeg. I chose this codec as I believe it provides more accurate frames, rather than the keyframe technology in stuff like h.264, or sorenson etc. I am writing music to picture and accurate sync is essential. (feel free to correct me if my format choice is wrong!). The movie needs to frame sync perfectly (if this is possible from a DV source?) with Logic Pro's timeline.
On export there is an option to "de-interlace source". As I'm viewing the footage on my computer monitor I checked this option in the belief a de-interlaced movie would produce better results. With the option checked the burned-in-timecode looks blurred. When paused the frame number looks like a combination of the current frame and the previous frame - so for eg if I pause the movie at the 18th frame the bitc display looks like a number 18 over the top of 17. Indeed the "weirdness" reminds me of the sort of effect one gets when viewing interlaced footage on a progressive scan screen.
If I render the movie ~without~ the option of "de-interlace source" checked, all looks sharp and as it should be.
I am currently encoding my movies without the option checked.
does anyone know what is going on here?
(I'm wondering if that option just needs to be checked when the source is already de-interlaced?)
TIA

Edit: Go ahead and read this, but it occurs to me that this is neither a Compressor nor an FCP question. This is what Logic people deal with every day. Ask on the Logic forum what works best for those purposes.
When I say DV I don't mean digital video. My video is
delivered on DV tapes from a TV production company.
(for some reason they wont provide any other format).
I use FCP to capture and then export the movie to use
in Logic to create sync music.
Are you only doing this to create a visual for music production? i.e. this video won't be used in the end product? If so it really doesn't matter what format you use, and it sounds as though there's no real place for FCP in this beyond capturing the video.
Are you sure DV is all keyframes?
I'm sure, and I'm pretty sure that Colin is sure.
What I do know is that DV is not the best of
formats where sound sync is absolutely crucial
DV has no inherent sync problems. There are sync problems that can some up with poor practices in capturing, but it DV is in sync when it starts out in FCP it will stay that way.
I'm working in PAL 25fps for the record - but of
course your info equally applies. In my case I
obviously can't stipulate the shooting formats used
(shot on digibeta for broadcast).
My main question though is just what does
"de-interlace source" check-option in the export pane
in QT for motion-jpeg codec mean? Do I check it when
my source footage is de-interlaced, or when I want to
produce a de-interlaced file?
You would use it to produce de-interlaced output, which is irrelevant in your situation and should be ignored. De-interlacing is only called for when moving to final distribution format, and when that format will only be seen on web or computer screens.
My problem is described in my original post regarding
the BITC frame numbers looking "doubled up". Its like
the previous frame gets superimposed on top of the
current one.
It's VITC - but DV doesn't use VITC.
In any case, it's relevant to know where your window burn came from. Is it burned into the tape you receive, or are you using TC Generator or Reader in FCP?
What it indicates is a time code offset by one field (half a frame). It may also indicate that there are fields which are not only in the wrong order but in the wrong frame. If your tape has hard cuts in it, park at one of those and see if you get half the lines of the outgoing shot and half of the incoming one. That would indicate such a problem.
Most likely it's just a problem with whatever device did the window burn. If it's a problem for your work, ask them to fix it.
If this is a reference tape, most likely there was an analog transfer from DBeta, with one or both of these issues introduced there.
Is there relevant DV timecode on the tape itself? If so you should probably use that and ignore the window burn.
I am wondering its a field order thing. There is a
de-interlace process going on and instead of
combining field 1 and field 2 of frame5 say, it
combines field 2 of frame 4 with field 1 of frame 5.
Another possibility is that there was a standards conversion in the chain, which would spread some source fields over two frames. Did the program originate in NTSC?
I can post examples of the issue if the problem needs
to be "seen". With "de-interlaced source" checked I
get a more blurred result with messed up BITC.
Don't do the deinterlacing, you'll confuse yourself more. At best you'll cover up a problem which may really be a problem. You don't need deinterlacing.
The Animation or None codec
create movie files that are too big and unwieldily.
This is why I've been using photo-jpeg. I'm not sure
how the Motion-jpeg A or B codecs you mention work -
any info would be useful.
You also likely have no use for any of these codecs. Most of them will actually degrade from DV somewhat. Don't fix what ain't broke. For your purposes DV is the native format you have to work with. Everything will work best if you keep it that way.
I need my movie to be as undemanding on CPU ~and~
disk as possible, while supplying true frames. Logic
needs every clock cycle and disk bandwidth it can
get! Picture quality is less important - I can always
look at the DV stuff if I need too.
Others with Logic experience will have other suggestions. If you need to see every field for timing you will need an interlaced signal and an interlaced display, which pretty much leaves you using standard PAL. Might as well be standard PAL DV. If the machine can't hack that there are other formats to consider including even MPEG-1 or -2.

Technical Photo-JPEG question

I am doing a project where a client has provided me with 400 Photo-JPEG files. (stock footage from Digital Juice). They load and playback just fine in a sequence that was created using the Make Sequence button.
I was informed by a knowledgeable person that I should not use Photo-JPEG and should have converted all the clips to a QT movie format (Prores or whatever).The only limitation I bumped into is that the clips wont accept metadata, but that is superfluous for this edit.
The time spent doing that seemed probibitive but I just wanted some technical experts from the forum to confirm or deny what I was told.

The only reason you would convert this to ProRes or an intermediate filetype is if you were having performance issues, i.g. slow playback, stuttering, excessive render times, etc...
Converting to ProRes or any other intermediate filetype introduces another conversion which degrades the original files with each conversion. Since Photo-JPEG is already a lossy format, you really don't want to compress those files again, unless you really have to. Anytime you can edit with the original format throughout a project it will give you a superior quality in the end. You have less time converting files. You lose less quality due to filetype conversions and multiple compressions. And generally the original file size is going to be substantially smaller than the intermediate codec.

QT- Photo Jpeg compression looks jerky

Hello guys,
I have converted my HDV 1080 i 60 clip to QT Uncompressed 10 bit with these settings:
video encoder tab - Compression Type: Photo Jpeg, frame rate: 29.97, compressor quality: Best,
Frame Controls tab - controls ON, resize filter: Better, Output fields: progressive, Deinterlace: Better
It is a video of waterfall and resulting clip is kind of jerky. The water looks like played frame by frame, not in fluid motion.
Thank you for any advise.

Thank you Brian so much for your response.
I am trying to find the best (most universal) format for my video stock footage. I am leaving the footage in native HDV 1080 i, but I would like to have another version for someone who doesn't have HDV codec on his computer.
I would love to try Motion Jpeg, but I can't find that codec anywhere within Compressor.

Quality loss when trimming photo-jpeg videos?

Hi all,
I want to do some basic editing with Quicktime Pro to videos made with my digital camera. They are photo-jpeg with stereo sound. With "basic editing" I mean trimming and joining clips, no further processing like color correction etc.
I wonder whether there is any loss of quality during this process... From my understanding photo-jpeg is much like mjpeg, so in theory there would be no need to re-encode the result (I save the stuff with "Save as...", not via export).
I made some tests, and for me it looks like there is no re-encoding. Does anyone know whether this is true?
Thanks,
Thomas

Only an "Export" would re-compress.
Save As merely puts your trimmed or joined files into a .mov container. The original codecs are used again.

Photo-JPEG / Compressor 4

How do I create 8-bit, Photo-JPEG QuickTime movie clips in Compressor 4? Does not seem to be among the built-in codec options.

Make a custom setting. Choose Quick Time Movie for Format. In Video, change the QT Settings which opens up the QT dialogue. In the Compressor drop-down, choose Photo JPEG.
Russ

Photo Jpeg codec

Similar Messages

Maybe you are looking for