[Jeff Coleman]

whats an OOC file?
And How do u know it looks fine?

[Jeff Coleman]

You are using Premiere Pro?
You are using version 15.3 or later?
You are following the instructions from Peter’s links above and you do not see the options for “Open Caption”?

If “yes” to all the above, then you may have some unusual problem like a corrupt software installation or something.
If “no” to any of the above then you may wish to provide us more detail about your
operating system,
software version and
project details.

[Jeff Coleman]

That works! Thanks Peter!

[Jeff Coleman]

Hey Peter!

Do you have a link/tutorial on how to do Open Captions in Premiere Pro 15.4? The links sent above don’t tell how to add captions or extend the captions clip in 2015.4 (like in 2017).

[Jeff Coleman]

Does MPEG Streamclip do the same? (can it handle TS files?)

[Jeff Coleman]

I’d go for the faster, brighter one with more contrast ratio. I wouldn’t use it either for critical color.

[Jeff Coleman]

I rarely have good luck with horizontal motion in QuickTime movies. But your shots behind the titles that are just zooms don’t seem smooth. What happens when your render the same clip with no titles?

[Jeff Coleman]

Holy Exasperation Batman! You must be completely brain fried by now.

I hope this is helpful and not off-topic. Have you tried opening those files in an earlier version of Premiere?

I noticed today importing Pan AF-100 AVCHD files that they read differently between CC2015.3 and CC 7.2.2

Ingesting via the Media Browser or Prelude the file comes into the project showing a framerate of 59.94 ndf. If I create a sequence from that .mts clip, the sequence is also 59.94 ndf. If I drop a timecode filter on to the clip in the sequence it displays 60 frames of timecode ndf. The next part is what’s different between the versions of Premiere:

In 2015.3 – the Source Viewer or the metadisplay timecode track display in the Program Viewer shows the clip as 29.97 ndf timecode. For every two frames I jog in the sequence the timecode of the source track/clip moves 1 frame. If I load the clip in the Viewer it only shows me 30 frames of timecode. So the timecode filter shows 60 frames but the metadisplay and the Viewer only show 30.

In CC7.2.2 – I get all 60 frames of timecode in the metadisplay and in the Viewer. So the timecode filter shows 60 frames and the metadisplay and the Viewer show 60.

Perhaps that’s an intended revision of the program, but strikes me as a bug. I should be able to load a 60frame clip into the Viewer and see all 60 frames of timecode. That strikes me as the later version of Premiere not handling the timecode of an AVCHD clip as well it did in a previous version. Seems something has changed under the hood.

[Jeff Coleman]

Exactly what it will look like kind of depends upon the footage. You may want to test a piece of footage of the type you’ll be shooting or shoot a piece of test footage and see how it looks.

To get 24p into a 30p timeline requires Premiere to repeat frames as those threads suggest. If you are watching something that is not moving or not moving much, I don’t think you are going to see much of a difference really, but it may have a subtle difference in feel. The more movement, the more observable the repeating frames will be, thus creating a kind of staccato feel. Some people actually like a bit of that look as it looks less real, less broadcast tv as if you could sense the realization that you are watching the cellulose instead of a live image—extraordinary, cinematic, etc. I’ve had projects that have done all the interviews in 24p and all the b-roll in 30p and dropped it into a 30p timeline. It makes the interviews look different while the b-roll doesn’t suffer from the artifacts of pulldown. For me, the more motion then the less I like it because it starts to feel like there’s something wrong. Perhaps shoot in 60p, 30p, and 24p a close up of a football pass from throw to completion and drop them into a 30p timeline and see what they look like to you. Try the same for an interview. Subjective mileage varies. Hope that helps.

Notice Mr. Williams comment here:
https://forums.creativecow.net/thread/8/1112879

“Re: Shooting in 24p, editing in 30p, easiest workflow?
by Bret Williams on Dec 3, 2010 at 12:23:31 am

24p at 30p simply duplicates every 4th frame. The worst cadence you could ask for. It’s not done anywhere I can think of. … 24p at 30p isn’t a very optimal or accepted practice. What happens when you add graphics or motion effects that are interacting on another timebase than the 24p footage? It would exaggerate the stutter.for example a logo flying across the screen would move at 30p, while the footage behind it would freeze frame momentarily while the graphic continues to move. This would occur on 20% of the frames.”

and Mr. Okey has a strong opinion on that thread as well:
“Don’t use 2:2:2:4 pulldown. Even a partially blind person can see its atrocious motion effects. Using 2:2:2:4 pulldown really is unprofessional. If you drop native 24p footage into a 30p sequence in FCP, 2:2:2:4 pulldown is what you’ll get. Just don’t do it.”

[Jeff Coleman]

[Duke Sweden] “No. If you open a new project, that project will have no bins until you create them.”
My bad. I didn’t mean “Open a New Project”.
I meant open a different project–not a new project. That is what Jay Cederholm referred to in his original post.

[Duke Sweden] “What’s happening is if I, for example, have 4 bins, “images”, “Sequences”, “Green screen clips”, and “Sound F/X”, and I want to get into Sound F/X to pull out an asset, I click on that bin, and 3 or 4 of the same bin opens. I do believe this is the problem the others are talking about.”
That is a different problem which I posted about today (08-06-16)
Open in New Tab Makes for Multiple Tabs of Same Bin
https://forums.creativecow.net/thread/3/989536
wherein (for me) when I click to Open in New Tab, I get multiple instances of the same bin and the instances of any bin opened with Open in New Tab increase the more bins I open. So when I click open my 10th bin in the project I have 10 instances/tabs of that bin. That is abnormal/a bug.

I tried to answer the first post in this thread:
“Once I close that particular project and then open a different project with only a few bins it seems to retain my bin/tab settings from the previous project.
It’s terribly annoying to find that I have 5 tabs of the same bin at the top of my window….having to close each tab.” That is normal/not a bug, at least for me in all the PProCC versions I can remember.
I believe my workflow suggestion for that problem might be helpful.