23.976 frame rate explained

This post was triggered from this this thread:
http://discussions.apple.com/thread.jspa?messageID=4741388#4741388
I just thought it best to start a new one
Okay iSchwartz, with the speed of a flying bullet, and with help from my fellow members of the IBS (Institute of Broadcast Sound - in the UK), I think I have some answers...
24P is indeed simply video at 24frames per second with the "P" meaning Progressive scan. Its a video format invented to be compatible with film. It also means that the footage will have more of a "film look" when its converted to TV frame rates for broadcast as it will have the same process applied to it as film footage.
As to where 23.976 fps comes in (with regards to Logic) is rather more vague!
(warning - the following contains some speculation!)
As all will know because film is shot at 24fps it needs a special conversion process to be shown on an NTSC TV of 29.97fps. The process could just speed the film up but it would look funny and so they sort of duplicate some of the film's frames instead, to get the frame rate increased. The process used would result in a frame rate of 30fps so to bring it in line with the (cumbersome) NTSC frame rate they have to slow the film down slightly (by 0.1%) before they "scan" in the film's frames to make video.
...and guess what a 0.1% speed reduction of 24fps results in? Yes - 23.976!
so...
23.976 is the frame rate of the telecine machine when playing film to transfer to NTSC tv. The process involves slowing the 24fps film by 0.1% to 23.976 and applying a 2:3 pulldown picture process, resulting in NTSC's frame rate of 29.97fps
Now the question is why would you want Logic to work in 23.976fps?
It is possible (I don't know for sure) that when you shoot with film (ie 24fps), destined for tv that the programme is edited at 23.976, ready for the telecine process, and so this is the frame rate used during the post production process - As it is the time reference used in the edit then we need logic to work at this rate too so we're all in time.
It is also possible that the latest HD video cameras provide a shooting frame rate of 23.976 fps so that the "slow down" process of the past is not required.
Having said that to view the 23.976 fps pictures on telly the video needs to be converted to 30fpsDrop - or you need a display that can work at this unusual frame rate. I am not sure what the implication of all this would be for the musician "working to picture".
One thing I would say, is that musicians are not alone in having much confusion with frame rates and time code, especially now Hi def has arrived. I would strongly advise double checking with "production", particularly the dubbing editor, if that frame rate requested ~really~ is the right one!
I hope I haven't confused the issue even more with all that! Don't take any of this as gospel as I am still learning too. I trust someone will provide corrections and additions.

Rohan,
I agree in so far as the musician should not have to worry about the technical aspects of picture, but the composer is working within a team of people who have to be able to communicate effectively. the composer is also part of the production's overall workflow and so the composer's work methods can be dependent on productions.
To answer you points individually...
- when the telecine is created, and then sent for offline editing, it is the offline edit that you receive with the BITC or the striped LTC (rare these days) that should be your guide. obviously in the states with the confusing NTSC format, it is important to be sure what format they have used in the offline process, but ultimately it is the production facility to ensure you have a video edit that you can work to
Your first sentence says it all. If the offline edit is in 23.976 then presumably this is what you'll get sent. I have no idea how this will get delivered as the format would not work on video tape, you wouldn't be able to view it on a standard TV either. You could view it as a quicktime movie. That is the only way I can think of.
I agree it should be up to production to provide you with what you can work with but how far must they accommodate? I doubt anyone would be too happy providing U-matic tapes these days. For my last job I wanted QT movies on a DVD-R but I had to settle for DV tapes and capture myself. Lets face it, as technology gets cheaper and more accessible we are increasingly expected to be able to handle all those advances!
- so the music you create can either sync to a master clock (which is rare other than word clock which is not for video syncing anyway) or simply to the QT or VHS that you have been provided with which should have standard frame rates. you simply compose your music based on that sync
I don't know what you mean by "master clock" in this context, and as you point out word clock has no timing information at all and is irrelevant in a timecode discussion. Yes you work to the movie you've been given, but what if its using 23.976fps? If it is, it wont be on VHS - and, you wont be able to sync properly to it in Logic as Logic doesn't work with 23.976
If production provides you with a "special copy" in say standard NTSC 29.97fps then the editors timecode will be different to yours. You wont be able to talk timecodes with them over the phone for example. For them to do this production will have to convert the footage specially for you using 3:2pulldown telecine process (so the film plays at the right speed) and I'm not sure they would pay for that!
- the issue is more critical in the dubb, but generally 1 second of music at whatever frame rate is still 1 second of music. when you send your music in it is almost never smpte locked unless you have delivered via a timecoded DAT something which is very rare these days. basically it simply measures the sample rate and then syncs within the DAW in the dub
1 second in NTSC's 29.97fps is 1second at 23.976fps which is 1 second in PAL's 25fps too;-) Its the number of frames within one second that has changed. The problem is the format of the movie. you can play it in QT but not on the telly and Logic doesn't have a time base to match with it. It is likely that logic will be able to follow the movie in QT (not sure of that), or "chase" it, but Logic's own smpte display will not match the movie's BITC. Indeed all of logic's time references will not match the movie's.
when you send your music in it is almost never smpte locked unless you have delivered via a timecoded DAT something which is very rare these days. basically it simply measures the sample rate and then syncs within the DAW in the dub
Ever heard of BWF? Bounce your finished music in logic as a WAV file and you actually get a timecode stamped "Broadcast WAV" file: a file that has the SMPTE time of where the music starts in the film. The timing info is embedded in the file. All the dub mixer has to do is press a key-command to place this file in the right place in the film. I worked this way on my last project. (Its also how logic can place any audio file into "its original recording position")
Without using timecode I'm wondering how you tell "the dub" where the music should go in the film? - I'm genuinely curious. In the past when delivering music without timecode I would still say, in a written note for eg, the track starts at some timecode point (as referenced to the BITC for eg). This is why the composers timecode needs to be the same as the dub/editor's!
- it is simply important for the people sending you their film to agree how many frames consitute their second. if you have a VHS playout from the offline, you should work to whatever format that VHS or DVD comes in; NTSC or PAL. it's not your job to worry about the film to offline telecine
A nice thought in theory:-)
It shouldn't be our job to worry about such things (bars, beats, keys and harmony are enough for me!) but we may not have the choice if we want the job!
Don't get me wrong here Rohan. I don't profess to understanding all this stuff properly and I have never been asked to work in 23.976fps. I went down this line of enquiry to see if I needed to know about it! Perhaps you are right and production will supply a special version for the composer - but I'd like to know if this is the case as I like to have a basic grasp of the overall production process. I'd love to know of anyone who has had to work in this frame rate and how typical it is becoming (if at all).

Similar Messages

  • Need 23.976 frame rate!

    I'm producing music for a television show at the new HD standard of 23.976. Moving back and forth between Pro Tools is a nightmare because Logic doesn't support the video frame rate.
    Any suggestions? (Besides ditching Logic altogether)
    Thanks,
    Nathaniel Reichman
    www.nathanielreichman.com
    G4 Dual 2.7Ghz   Mac OS X (10.4.8)  

    Hi Starcrash,
    I would strongly discourage the use of the term "24 drop" in reference to 23.976 (23.98) which happens to NOT be a drop-frame timecode. <<</div>
    Newer formats and all file-based workflows is getting confusing enough without screwing up the terminology. No offense intended, of course. Just wanted to point it out and not have the misinformation spread any further.<<</div>
    I couldn't agree more. But since you're new here, and also coming in on the tail end of a thread, the subject matter of which has been moved to and since clarified to great extent here...
    http://discussions.apple.com/thread.jspa?threadID=1000224&tstart=0
    ...let me suggest that no one here, let alone myself -- a stickler for nomenclature and correct use of terminology (but you wouldn't know that because you're new) -- was not intentionally or otherwise trying to spread misinformation. This was very much a "learning" thread. That should have been clear by my use of "AFAIK (and that ain't much)" and "would like to learn more".
    Having said that, what I wrote about the terminology being used interchangeably (albeit incorrectly) was based on recent experience dealing with editors on two different films, both of whom continued to refer to the film as "twenty-four frame". In fact, one of them didn't know if the right rate was 23.98 or 23.976 or 23.978 so perhaps he "defaulted" to using the term "24" and calling it a day. Who knows, eh?
    So, yes, slight offense taken. But I think your very cogent explanation of the nomenclature more than makes up for that  :-)  and I'm glad you posted it.
    Having gotten that off my chest, I'd like to welcome you to the forum.
    -=iS=-

  • 23.976 Frame Rate Workaround?

    Please help. im doing hte sound design for my friends film, which is at 23.976 fps. This is my first time doing this. i should add.
    is there a pardon the pun, logical way to do this? ive spent the last 2 nights worrying that my audio is not going to sync up and that its going to waste everyones time aside from me wanting to bash the crap out my computer.
    i just need some help here....ugh.

    well...what im going to test tonight is this.
    im going to sync the beginning and put a hard effect towards the end that is synced visually in logic. then, bounce my audio, and send it back to FCP. and see how much...if at all it is out of sync.
    all this stuff is very confusing. ive been writing music for years, but this is a whole realm of stuff that im not prepared for.
    but its a friends film, and i want to do due dilligence.

  • How do I output the smoothest video when changing or mixing frame rates from the original footage?

    I have been experimenting with various Media Encoder settings, and wondered if there was anything else I can try to get the smoothest video output possible, especially when changing frame rate and possibly resolution.  For clarification, let me start from the beginning and explain what I'm doing and what I've tried so far.  I'll try to be as brief as possible, but if I do go into too much detail, I apologize. 
    My original footage is AVCHD 1080p - 60fps.  (my camera only does 60fps...specifically 59.94fps)  We're not talking interlaced video here, I'm staying away from that.  This is definitely full frame, progressive video at 60 frames (not fields) per second.  My output will ultimately be for the web.  I have been keeping my output codec (H.264) and bit-rate (VBR 2-pass, relatively high-bitrate) consistent, and have been trying numerous output options and even sequence settings to see what would yield the best results.  I am using Premiere Pro CS5.5 along with Media Encoder.  Here's what I've done and the results I've observed:
    1.  I created a sequence with 1080p - 59.94fps settings to match my original footage.  I then output both 1080p and 720p versions at 59.94fps, and at 29.97fps.  The 59.94fps output files looked absolutely great, as would be expected.  Extremely smooth.  The 29.97fps output files were generally smooth, but not near as smooth as the 59.94fps.  This is expected since it's half the frame rate as my original footage.  However, my question is this:  What exactly is Media Encoder doing when "down converting" from 60p to 30p?  From a technical stand point, is it dropping every other frame?  I'm just curious to understand exactly what it does.  I tried the Frame Blending option as well, and that only yielded a bit more blur to the images which wasn't desirable for any of the output files. 
    2.  Just to see what would happen, I created a sequence with 1080p - 29.97 settings.  I then output both 1080p and 720p versions at 29.97fps.  The video was much more choppy in these cases, even with Frame Blending on.  Now, I know not matching my sequence settings with my original media isn't ideal, but I again just want to understand why this yields less smooth video than the 29.97fps options above.  Why does cutting the sequence settings frame rate in half from the original, then outputting the same frame rate as the sequence yield video that is not as smooth?
    3.  Next, I wanted to try mixing frame rates to see how Premiere and Media Encoder handled the footage and output files.  Premiere handled it great, no issues there.  However, I had some interesting things happen when I output the files.  Here's what I did:  I created a sequence with 1080p - 59.94fps to match my original footage.  Then I took the same exact footage that was in my sequence, copied it in my project panel and interpreted it at both 23.976 and 29.97 fps, yielding slow motion video.  The slow motion video looked great in Premiere, so I went ahead and just added it to my sequences, along with the original 59.94 footage.  I also created separate sequences for the 29.97 and 23.976 footage respectively, each with matching sequence settings, then added a nested sequence to another original footage sequence (with 59.94fps sequence settings) to see which yielded the best results.  Basically, I'm trying to output 59.94fps that match my original footage, but also throw in some slow motion footage at different framerates.  I'll explain my results in a moment as they are a bit convoluted, however, here is my question:  When mixing frame rates and trying to output the smoothest video, am I going about this the right way?  I would assume you would use your sequence settings that match the original footage (which is what the majority of the footage will be), then bring in a nested sequence for the slow motion (as oppose to just dropping the slow motion video directly into my main sequence), and then output to the same frame rate of the majority of the footage, in this case 59.94fps. Is there a better workflow for this?
    The results to #3 above were as follows.  Initially, it looked like it didn't matter if I nested the slow motion sequence into my main sequence, or simply dropped the actual slow motion video into my original 59.94fps sequence.  It seemed to produce smooth results either way.  Frame Blending blurred the video a bit, but didn't seem to make much difference, and quite honestly I like the footage without Frame Blending in general.  However, when I closed down Premiere, and opened the output files later (opening in Quicktime), the footage looked choppy.  In fact, it would go from choppy to smooth and back, almost like it had an irregular cadence (don't know if I'm using "cadence" in the right context here).  I would then open up Premiere again, import the output footage into my project panel, and play the footage in Premiere, and it would play back smooth again. Is this a Quicktime issue?  I was playing 1080p 59.94fps files when this happened, so maybe it's just because it's a large file.  Doesn't seem to have issues with the 720p files I created.  But it sure threw me off with my testing because I then started second guessing the settings I was using.  My iMac is the latest 2011 model with plenty of RAM, so I wouldn't think it's the computer.  Thoughts?
    4.  Next, I noticed on ALL my output files (again, using the H.264 codec from Media Encoder) that the color of my video seemed to flatten quite a bit.  It seems that the original footage has more contrast and saturation than the output files.  I figured maybe this was just how it was, but when I re-imported the output files back into Premiere, they looked IDENTICAL to the original footage.  And in Media Encoder's Source/Output windows, I don't see any difference there either. Is Quicktime again the culprit here, doing some odd things to the color of my videos?
    5.  Regarding Frame Blending, when is the best situation to enable this option in Media Encoder?  I've read it is when mixing frame rates, but I honestly didn't see too much of a change except for a bit more blur, which I didn't care for.
    6.  Lastly, my conclusion is that 60fps yields the smoothest video, which is an obvious conclusion.  However, I know that 60fps isn't the best or easiet frame rate for web delivery.  It seems 30p is more the standard.  Are there any integrated web players that would play 60fps?  Can you get 60fps video on YouTube/Vimeo?  If yes to any of these questions, can they do 720p and 1080p at 60fps? 
    Those are all my questions.  I hope I am clear enough without being overly wordy and hopefully I didn't put too many questions into one post.  Thanks in advance for any insight, I really appreciate it.

    Did you ever figure out which output worked the best? I have the same original footage; trying to determine the best output settings to make a dvd for tv.
    thanks!

  • Modified frame rate properties keep resetting

    Hi community.
    I have faithfully switched over to Premiere Pro CC and so far so good. One thing that just sucks is that if I modify the frame rate of a clip (or series of clips) in a project (like take gopro 60fps footage and modify it to playback at 23.976) if I move that project to another computer the original settings come back (60fps)
    To better explain, I have duplicate projects set up at home, and in my office. They are cloned projects, so every byte is the same (folder structure included). If I work at home, then take the premiere pro project into to work, and relink it to the media files there, all the modified clips revert back. Which is a pain because I have to go through all the footage and re-modify them.
    Any fix on the horizon?
    Thanks team!
    Rs

    They are just looking past this, Just make sure to modify all the clips so when your project moves and it resets you only need to modify all the clips at once. Only fix I can see right now.

  • Creating a Gif is different frame rate

    If I have an uncompressed .AVI file that I created in After Effects CS5.5 which is 23.976 fps, and load it in Adobe Media Encoder CS5.5, and tell it to create a .GIF of it, at an output fps of 23.976, when I load the created .GIF into Adobe After Effects it tells me the frame rate is 25 fps and there is a black frame padded on the end.  I want the frame rate of the GIF to be what I ask it to be, ie. 23.976, with no additional black frames.
    Here's what happened with screenshots:
    1. I load the uncompressed AVI file that was created in Adobe After Effects CS5.5 into Adobe Media Encoder CS5.5.  Note below that Adobe Media Encoder is saying that the source clip is 23.976 fps, and that the export settings are to create an animated GIF at 23.976 fps.
    2. After Adobe Media Encoder CS5.5 has said "done" (Encoding Completed Succesfully) for this export to a .GIF, if I take that .GIF file that Adobe Media Encoder has just created into Adobe After Effects CS5.5, this is what it says:
    As can be seen above, Adobe After Effects CS5.5 is saying the GIF file that Adobe Media Encoder CS5.5 has just encoded is actually 25 fps, not 23.976 fps like I told it to be exported as.  Also, the GIF Adobe Media Encoder has created is 10 frames long, whereas my original uncompressed AVI is 9 frames long.
    Edit: I've just been reading up on the GIF format and it seems it doesn't store a frame rate but instead stores a frame delay, which is in hundredths of a second.  If this is just an integer, is this the reason for the displayed frame rate discrepancy, ie. 1 frame at 23.976 fps  would be 4.1708 hundredths of a second I think, and 1 frame at 25 fps would be 4 hundredths of a second I think - both rounded to the nearest integer would be 4 hundredths of a second so would the frame delay be set to "4" for both 23.976 fps and 25 fps? (there is also the fact that some short time will be taken for the drawing of the frame)
    Though even with the above, it shouldn't be increasing the amount of output frames.  It converts it correctly (no additional frames) if I use VirtualDub to convert the AVI to GIF instead of Adobe Media Encoder CS5.5.

    Thanks.  Could you get them to also check other parts of the code too.  eg. when I had a work area set in Adobe After Effects CS5.5 and then loaded that project into Adobe Media Encoder (dynamic link etc.) and rendered just the work area I think it was about a frame out then too - I don't think it was a GIF in that case but another type (maybe AVI/H264).

  • When is new frame rate for HD projects?

    Cyberbretheren...
    Those working in film especially CGI stuff know that there's a new frame rate of 23.976. Any word on when Logic will add this option?
    Pro Tools already has, nudge nudge wink wink....
    A
    G5 dual 2.5   Mac OS X (10.3.9)   Stylus AND my original Minimoog. Lots of MOTU. No more Digi.

    Yeah, "24 drop frame". I asked the Logic reps at last years' NAMM show if this was going to be added to the next version of Logic, but I got the ol' blank stare -- they had never heard of it! Hopefully by now they have. I agree, this new frame rate needs to be added. Glad you brought this up!

  • FCP XML to Premiere Different Frame Rate

    Hello,
    I have imported an FCP 7 XML into Premiere 5.04. When my sequence was in FCP it was at a frame rate of 23.976 at 720P. When it came into Premiere, though, it had changed to 59.94 fps at 720P.
    I wonder how this has happened and if there is any way to change it back to 23.976 fps? Or should I just leave it as is?
    I tried copying all of the clips within the 59.94 fps sequence into a new sequence that was 23.976, but this resulted in partial frame gaps (like a quarter of a frame missing). Sometimes you wouldn't even notice this during playback, but other times you do. So I assume this is not the best way to change it back to 23.976.
    Thank you.

    Hi Colin,
    Here is the info:
    General
    Complete name                    : /Volumes/David Whillans 500GB/Ghana Documentary FCP/Final Cut Pro Documents/Capture Scratch/Day 2/A01_BusMirror_01.mov
    Format                           : MPEG-4
    Format_Commercial_IfAny          : DVCPRO HD
    Format profile                   : QuickTime
    Codec ID                         : qt 
    File size                        : 124 MiB
    Duration                         : 21s 188ms
    Overall bit rate                 : 49.2 Mbps
    Encoded date                     : UTC 2009-06-26 15:49:49
    Tagged date                      : UTC 2009-06-26 15:49:49
    Writing library                  : Apple QuickTime
    Original source medium           : Card A
    com.panasonic.professionalplugin : 2009-05-05 07:17:50 -0400
    org.smpte.mxf.identification.fil : 2009-05-05 11:17:50 +0000
    com.panasonic.professionalplugin : 2009-05-05 07:18:11 -0400
    com.panasonic.professionalplugin : Panasonic
    org.smpte.mxf.package.material.p : 2009-05-05 11:17:50 +0000
    com.panasonic.professionalplugin : B8TCA0255
    org.smpte.mxf.identification.app : P2
    com.panasonic.professionalplugin : AG-HVX200P
    org.smpte.mxf.identification.app : Panasonic
    org.smpte.mxf.package.material.c : 2009-05-05 11:17:50 +0000
    org.smpte.mxf.identification.app : 0x060E2B34040101090E0E010101000001
    com.panasonic.professionalplugin : 060A2B340101010501010D4313000000ECEA5B74564905F70080458228D2D24D
    org.smpte.mxf.package.material.p : 0x060A2B340101010501010D4313000000ECEA5B74564905F70080458228D2D24D
    org.smpte.mxf.package.material.p : 0021JO
    com.apple.proapps.reel           : Card A
    com.panasonic.professionalplugin : 2009-05-05 07:18:11 -0400
    com.panasonic.professionalplugin : 2009-05-05 07:17:50 -0400
    org.smpte.mxf.identification.app : 2.0
    com.apple.proapps.originalFormat : DVCPRO HD 720p60
    org.smpte.mxf.identification.gen : 0x9007CAD96EFF4741A0AF8763540BD0E6
    com.apple.proapps.clipID         : 060A2B340101010501010D4313000000ECEA5B74564905F70080458228D2D24D
    com.panasonic.professionalplugin : SHOOTING
    Media/UUID                       : 75369709-6DCB-4DC0-A504-1B84D8A45AC8
    Video
    ID                               : 1
    Format                           : DV
    Format_Commercial_IfAny          : DVCPRO HD
    Codec ID                         : dvhp
    Duration                         : 21s 188ms
    Bit rate mode                    : Variable
    Bit rate                         : 46.0 Mbps
    Maximum bit rate                 : 97.7 Mbps
    Width                            : 936 pixels
    Original width                   : 960 pixels
    Height                           : 702 pixels
    Original height                  : 720 pixels
    Display aspect ratio             : 16:9
    Frame rate mode                  : Constant
    Frame rate                       : 23.976 fps
    Original frame rate              : 29.970 fps
    Standard                         : NTSC
    Color space                      : YUV
    Chroma subsampling               : 4:2:2
    Bit depth                        : 10 bits
    Scan type                        : Progressive
    Compression mode                 : Lossy
    Bits/(Pixel*Frame)               : 2.922
    Stream size                      : 116 MiB (94%)
    Language                         : English
    Encoded date                     : UTC 2009-06-26 15:49:49
    Tagged date                      : UTC 2009-06-26 15:49:49
    Audio #1
    ID                               : 2
    Format                           : PCM
    Format settings, Endianness      : Little
    Format settings, Sign            : Signed
    Codec ID                         : sowt
    Duration                         : 21s 188ms
    Bit rate mode                    : Constant
    Bit rate                         : 768 Kbps
    Channel(s)                       : 1 channel
    Channel positions                : Front: C
    Sampling rate                    : 48.0 KHz
    Bit depth                        : 16 bits
    Stream size                      : 1.94 MiB (2%)
    Language                         : English
    Encoded date                     : UTC 2009-06-26 15:49:49
    Tagged date                      : UTC 2009-06-26 15:49:49
    Audio #2
    ID                               : 3
    Format                           : PCM
    Format settings, Endianness      : Little
    Format settings, Sign            : Signed
    Codec ID                         : sowt
    Duration                         : 21s 188ms
    Bit rate mode                    : Constant
    Bit rate                         : 768 Kbps
    Channel(s)                       : 1 channel
    Channel positions                : Front: C
    Sampling rate                    : 48.0 KHz
    Bit depth                        : 16 bits
    Stream size                      : 1.94 MiB (2%)
    Language                         : English
    Encoded date                     : UTC 2009-06-26 15:49:49
    Tagged date                      : UTC 2009-06-26 15:49:49
    Audio #3
    ID                               : 4
    Format                           : PCM
    Format settings, Endianness      : Little
    Format settings, Sign            : Signed
    Codec ID                         : sowt
    Duration                         : 21s 188ms
    Bit rate mode                    : Constant
    Bit rate                         : 768 Kbps
    Channel(s)                       : 1 channel
    Channel positions                : Front: C
    Sampling rate                    : 48.0 KHz
    Bit depth                        : 16 bits
    Stream size                      : 1.94 MiB (2%)
    Language                         : English
    Encoded date                     : UTC 2009-06-26 15:49:49
    Tagged date                      : UTC 2009-06-26 15:49:49
    Audio #4
    ID                               : 5
    Format                           : PCM
    Format settings, Endianness      : Little
    Format settings, Sign            : Signed
    Codec ID                         : sowt
    Duration                         : 21s 188ms
    Bit rate mode                    : Constant
    Bit rate                         : 768 Kbps
    Channel(s)                       : 1 channel
    Channel positions                : Front: C
    Sampling rate                    : 48.0 KHz
    Bit depth                        : 16 bits
    Stream size                      : 1.94 MiB (2%)
    Language                         : English
    Encoded date                     : UTC 2009-06-26 15:49:49
    Tagged date                      : UTC 2009-06-26 15:49:49
    Audio #5
    ID                               : 1-0
    Format                           : PCM
    Muxing mode                      : DV
    Muxing mode, more info           : Muxed in Video #1
    Duration                         : 21s 188ms
    Bit rate mode                    : Constant
    Bit rate                         : 768 Kbps
    Channel(s)                       : 1 channel
    Sampling rate                    : 48.0 KHz
    Bit depth                        : 16 bits
    Stream size                      : 0.00 Byte (0%)
    Audio #6
    ID                               : 1-1
    Format                           : PCM
    Muxing mode                      : DV
    Muxing mode, more info           : Muxed in Video #1
    Duration                         : 21s 188ms
    Bit rate mode                    : Constant
    Bit rate                         : 768 Kbps
    Channel(s)                       : 1 channel
    Sampling rate                    : 48.0 KHz
    Bit depth                        : 16 bits
    Stream size                      : 0.00 Byte (0%)
    Audio #7
    ID                               : 1-2
    Format                           : PCM
    Muxing mode                      : DV
    Muxing mode, more info           : Muxed in Video #1
    Duration                         : 21s 188ms
    Bit rate mode                    : Constant
    Bit rate                         : 768 Kbps
    Channel(s)                       : 1 channel
    Sampling rate                    : 48.0 KHz
    Bit depth                        : 16 bits
    Stream size                      : 0.00 Byte (0%)
    Audio #8
    ID                               : 1-3
    Format                           : PCM
    Muxing mode                      : DV
    Muxing mode, more info           : Muxed in Video #1
    Duration                         : 21s 188ms
    Bit rate mode                    : Constant
    Bit rate                         : 768 Kbps
    Channel(s)                       : 1 channel
    Sampling rate                    : 48.0 KHz
    Bit depth                        : 16 bits
    Stream size                      : 0.00 Byte (0%)
    Menu
    ID                               : 6
    Language                         : English
    Encoded date                     : UTC 2009-06-26 15:49:49
    Tagged date                      : UTC 2009-06-26 15:49:49

  • Importing EDL project frame rate is always 23.98

    Hi There,
    I'm importing a 24 frame EDL. All of the import settings are set to 24 fps. However on import, the project frame rate is always 23.98.
    I have added the number 24 to the defaulteframerate section of the preferences file, but no luck.
    Anyone found a solution to this?
    Thanks

    Just a wild guess since I don't normally work in 24 fps... all of us NTSC-biased types accept that 23.98 (more accurately, if not absolutely precisely expressed as 23.976) is the "pull-down" frame rate that results from a telecine transfer, and is the rate that is assumed, corresponding to 29.97 or 1000/1001.
    This framerate is emulated in a number of "Digital Cinema" electronic origin formats.
    Absolute 24.0000 fps is a bit rare in these parts and in reality probably would only come up if one were working with a dpx image sequence properly scanned, not telecined.
    Not saying that 24.000 does not exist -- I'd say that it is just as uncomfortable a fit in 25 fps-land as it is here! And Color / Final Touch has been notoriously bad with 25 fps.
    good luck and merry christmas....
    JPO

  • After Effects CC import "Sequence Footage" frame rate settings in "Import" preferences

    Just started using the new AE CC (v12 as Adobe will not refer to it as) I noticed one thing that seems to work differently from CS6 and that is in the preferences for import Sequence footage settings.  It doesn't seem to work normally, at least for me.  I don't know if this is an issue related to how AE CC works with the cloud but the dfault frame rate for sequence footage importing is 30fps.  I am trying to import footage that is natively 23.97 at 24 fps.  So like in CS6 I go to Preferences - Import - Sequence Footage - frame per second and change it from 30 to 24 frames per second.  Closed the software, opened it back up, checked the settings and saw that they took, it still says 24 frames per second like I told it.  But when I import a piece of 23.976 footage, it comes in at 23.976 as opposed to the 24 fps I set it as.  Same goes for 30 fps footage, it comes in at 30 fps and not 24.  User error is always my first assumption, I'm not proud i just want it to work, am I doing something wrong or just confused?  Thanks for any help.  p.s.  help is not someone responding with, "I don't know" or "I don't have AECC yet".  I know somebody is going to!

    Hi Tim,
    WOW!  Thanks for the super-fast reply!  As soon as I posted this I realised I should have mentioned that I am importing DPX files.  I do import quicktimes as well but know that the footage import does not apply to a single file, only a sequence of files.  But I still wonder if I may be either doing something wrong or am just a little confused.  I have been using After Effects since CS3 doing compositing for film and I always use DPX sequences.  I did a bunch of comparing and back and forth with AE CS6 and AECC while trying to figure this out.  I always set my preferences up when I upgrade before I start working and I always set them up the same.  I have been using CS6 since last July and it still works the same.  What I did is imported five or six different DPX sequences, some were rendered out as 24 fps, some at 30 and some at 23.976.  Assuming AE looks at the metadata to decide how to auto interpret, AE CC opened them all at their native frame rates of the just mentioned 24, 30 and 23.976 respectively, even though I told it to import at 24fps in the preferences.  I also imported the same files in AE CS6 and they all opened at 24 fps like always.  I know I can change the frame rate in the "Interpret footage" option, that is what I have been doing today so that I can work with footage in 24fps but since I have it set in the preferences to import image sequences at 24fps, I am perplexed as to why it does not do so, so I do not have to interpret the footage to my preferred frame rate, as is the case in AE CS6 as well as it was in CS 5.5 and CS 3.  Since I was lucky enough to have an Adobe employee chime in Tim, I would be curious to see what you may find if you recreated this scenario.  Would it be possible for you or someone at Adobe to set the sequence footage import frame rate to 24 fps in the preferences then try to open a piece of footage that is natively 23.976 fps in both AE CS6 and AE CC?  Like I said, I certainly beleive I may be doing something wrong but I would be very curious to see what you find on your side.  I would not be suprised if it imported at 24 fps in AE CS6 and 23.976 fps in AE CC.

  • FCP to PP Blackmagic frame rate settings question

    Hello everyone. FCP to PP editor here, and as I attempt to monitor my AVC-Intra 100 1080HD 23.976 footage on an external monitor via my Blackmagic Studio card, I seem to be missing a setting that was available in FCP 7.
    I'm hoping someone can help me either find the switch or confirm that it does not exist in PP.
    The video output menu in FCP7 (when used with Blackmagic cards anyway) has a handy 23.976 ->59.94 8 bit HD conversion output that allows me to monitor in a frame rate my consumer Samsung display can accept.
    In Premiere CS 5.5, I understand that I need to choose the Blackmagic sequence preset that matches my footage (I've chosen the Uncompressed preset at 1080HD/23.976 so I can also choose ProRes422 for my preview file codec). My external monitor can't display 23.976, so I'm hoping there's a way to tell my Blackmagic card to still do that conversion I'm so fond of in FCP7 (to 59.94)... Whether it's through a Blackmagic setting or a PP setting, I'd like to know if it's possible. I know the hardware can do it... just wondering if there's a way PP can acheive it.
    By the way, I did have the thought to use a 29.97 sequence/timeline, and it works great for monitoring, but playback continually stops, even when files have been rendered.
    Thanks so much for any input!
    Banks

    Richard,
    Thanks very much for the response. It's not there on my Mac. I do have 9.5 installed (did it last week).
    I'll give BMD a call. I have a Decklink Studio 2, which may not have the option at the card level. Strange, though, since I know the hardware can do it. Perhaps BMD has a way to flip the switch.
    Thanks,
    Banks

  • How does FCP Pro X handle mixed frame rate video clips?

    My camcorders are by Canon and both can shoot 50i or 25p. Normally I shoot 25p to avoid interlace artefacts. As I understand it, FCP Pro X conforms the clips to match the initial clip in the storyline. But what would be the outcome if I included clips from another camcorder that only offered 30p? Would those clips be converted to 25p if the initial clip was 25p. Or, would the 25p clips be converted to 30p if the initial clip was 30p?
    Assuming I made a movie entirely out 30p footage, would that be uploaded to You-Tube at that frame rate?  If my movie is 25p is that converted to 30p for You-Tube upload? Could I otherwise export a QT movie to my desktop at 30 fps or any other frame rate?
    It seems that the 25p setting on my camcorders still means that the recording is made as 50i but repackaged somehow. Can anyone explain please?
    Yes, I am in the UK in a PAL environment.
    AW.

    But what would be the outcome if I included clips from another camcorder that only offered 30p? Would those clips be converted to 25p if the initial clip was 25p. Or, would the 25p clips be converted to 30p if the initial clip was 30p?
    Subsequent clips will be converted to match the project settings created by the first clip into the timeline. I don't know how well FCP does this timebase conversion from NTSC to PAL frame rates or vice versa. Compressor would probably do a better job. There is also Standard Conversion software from Graeme Nattress that will do an excellent job.
    YouTube will take either. You would need to use Compressor to change the frame rate on export, though you don't want to do that unless you absolutely have to.
    Most consumer cameras do not actually shoot 25 separate frames when they're set to 25p. They shoot what's called segmented frames, two fields just as the 50i setting, only the two fields are supposed to be identical. That's the theory; in practice some cameras do this better than others.

  • Can't Change Frame Rate in Properties

    To change project properties in FCPX you click the wrench icon, which brings up a window to select 720p, 1080p, etc as well as frame rate. The problem is, there are no options in the dropdown for the frame rate in all of my projects, it chooses one automatically (seemingly arbitrarily) and you can't change it.
    I thought that when the progam says it would detect the properties of the first clip and adjust the project properties to match, it would actually do that (maybe I should have known better). So I imported my standard 1080p 29.97fps footage from my Canon 7D and then FCPX automatically set the project properties to...720p at 24fps. Curious, no? No problem, I thought, I'll just go to Project Properties and manually correct FCPX. But it was not to be, as FCPX had decided to give me only one  option in the frame rate selection: 24p. But no, I thought, I would very much like my properties to be 29.97 so as to match my footage. But FCPX did not agree with this, and would not change its mind.
    Has anyone found a solution to this?
    Do any pros still use Final Cut Pro?
    Thanks,
    Kurtis

    It may be possible that a .jpg was the first thing in the project, which may explain the seemingly random properties (why wouldn't they just make it default to a more common setting like 1080p 29.97?) but I digress.
    And it's a very stupid move to revoke the ability to change project properties while clips are in the project, that makes no sense.
    I'm begining to think that Apple has really failed with this new version of Final Cut; and I've been using Final Cut for years. I am debating switching to Premiere, but I will give FCP X a bit more time to redeem itself.
    Kurtis

  • Small frame rate variation between Motion output and reference video

    Hello all,
    Here's really wonky sort of question for all you Motion/post-production wizzes out there.
    I have a 1920x1080 lower thirds project that I am trying to synch up to a HD up-res of the same dimensions. The problem is that the up-res has a frame rate of 23.976 and Motion only allows for a frame rate of 23.98, so the output synchs up ok at the begining of each act (I have the projects split up into acts), but the further down the time line you go, the more it drifts.
    I've done the math and, for this particular project, the last title begins to appear at 00:20:09:11 in Motion, but appears in FCP at 00:20:09:07, a drift of 4 frames, 3 short of the 7 frames it is supposed to drift if you multiply the timecode in secconds by 23.976 and 23.98, but none the less, very annoying.
    Is there anything that can be done to remedy the situation besides going back after the final Motion output and resynching manually? A three or four frame drift isn't a huge deal, but the largest act I have is 32 minutes, which sounds like a 6 or 7 frame drift. Again not really a huge deal, but I do have several lower thirds that need to be frame accurate (and really, it would be nice if they were all that way).
    Thanks ahead of time.
    -G
    1.6 GHz G5 1.5GB RAM   Mac OS X (10.4.3)   Final Cut Studio

    Yeah. It kind of stinks when you have to swap platforms just to finish a project. AE is also a pain for longform, so I don't want to mislead you.
    I would imagine that Motion would be fine as long as you break the Project up in sections. My workflow is usually like this:
    Generate a matte or slug in a layer above the footage to fill the area where I need the Super or Composite. This should be fairly short (below 1 minute if possible) I may also have to RAZOR out the footage below the matte to match the matte timing. Select the Matte and footage below it if you wish to see the footage and sound in Motion.
    Select File/Send to/ Motion Project
    Create a new Motion Project. Name it for the section I'm editing.
    Add overlays and animations, filters, etc.
    Save project
    switch back to FCP and view/render from FCP.
    then move on to next section of timeline that needs overlays, repeat the procedure. Just copy paste the layers from one Motion project to another if you want to maintain certain layer continuity.
    This way, the Motion projects are managable size and you don't have to re-render the whole FCP project at once. The clips are not long enough for sync issues to appear. And Motion performs much better when the footage is short enough to load into RAM (sub 20seconds for most people).
    Also, to get the most out of Motion, you might want to turn off one of your monitors if you use 2 of them. Motion can use far more VRAM from your graphics card if only one monitor is active.

  • Export XML in right frame rate  for resolve?

    Hi!
    I'm in serious need for some help! When I import my exported XML sequence from premiere in to DaVinci Resolve 10 lite, I get an error message saying "The imported sequence frame rate (25) must be the same as the project frame rate (23,976)." All of my settings in Premiere that I can think of is set to 23,976fps, but if I understand the error message right, DaVinci claims the XML is 25fps... doesn't make any sense at all. I've tried for several hours now getting this to work, but it won't.
    I would really appreciate some help with this one, I'm in a hurry (as always, we're behind schedule). Worked with Davinci many times before, never had any problem with it.
    Regards
    /Patrik

    I am not a Resolve user, but could it be that Resolve has been set up for a 25fps project? And maybe the lite version restricts your frame size?
    Just curious.

Maybe you are looking for

  • Help needed in query friends

    Hi, I have a table with Data as follows countryname id - name - Date 1 - argentina - 11/28/2006 12:53:21 PM 2 - alabnia - 12/01/2006 10:00:21 PM 3 - us - 12/01/2006 05:00:21 PM 4 - france - 12/02/2006 04:00:21 PM 5 - canada - 12/03/2006 03:00:21 PM 6

  • How to put acents in pages app

    How I can correct the acents in pages app for Macbook?

  • Preview in Finder doesn't work. Doesn't preview movies or audio.

    When i used to preview files in finder such as movies or audio they would play in a preview window. now, instead, all that comes up is a picture of the application the file is opened in, i.e. quick time or itunes. help?

  • How to find the cause ofan error at runtime in forms (10g)

    hi can u please tell me how to find the cause ofan error at runtime. in forms 6i, the shortcut key is shift+f1 i needthe shotcut key in 10g forms. thanx

  • Disappearing folder

    Major Xsan troubles here, started last Friday. The Xsan has a dozen or so folders at the top level. When viewed from the Finder, one of those folders has no icon and reports a date sometime in 1904. When I try to select this folder (click on it), it