Articles on this Page
- 01/11/19--06:29: _Re: .srt import and...
- 01/11/19--06:30: _Re: Open Captions w...
- 01/11/19--06:36: _Re: Converting mast...
- 01/11/19--06:39: _Re: Converting mast...
- 01/11/19--06:40: _Re: Why did they re...
- 01/11/19--07:03: _Re: MOGRT - Text Pr...
- 01/11/19--07:07: _Re: Premiere Pro CC...
- 01/11/19--07:09: _Re: Premiere Pro fr...
- 01/11/19--07:11: _Re: Poor Performanc...
- 01/11/19--07:13: _Re: Major disappoin...
- 01/11/19--07:24: _Re: Scaling only pl...
- 01/11/19--07:30: _Re: Green and Pink ...
- 01/11/19--07:31: _Re: Photoshop image...
- 01/11/19--07:41: _Re: MOGRT - Text Pr...
- 01/11/19--07:46: _Re: Open Captions w...
- 01/11/19--07:48: _Re: .srt import and...
- 01/11/19--08:00: _Re: MOGRT - Text Pr...
- 01/11/19--07:59: _AS-11 Vidchecker Fa...
- 01/11/19--08:15: _Re: Adobe Premiere ...
- 01/11/19--08:10: _Obsolete Audio Filt...
- 01/11/19--06:29: Re: .srt import and editing not working in Premiere CC 2019
- 01/11/19--06:30: Re: Open Captions won't update changes
- 01/11/19--06:36: Re: Converting master video from NTSC to PAL
- 01/11/19--06:39: Re: Converting master video from NTSC to PAL
- 01/11/19--07:03: Re: MOGRT - Text Properties Don't Work
- 01/11/19--07:09: Re: Premiere Pro freezing on "Save as" and "Save a copy"
- 01/11/19--07:11: Re: Poor Performance in V13 Compared to 12
- 01/11/19--07:13: Re: Major disappointment in Premiere Pro 2019
- 01/11/19--07:30: Re: Green and Pink Video in Premiere Pro 12.0.1 (Build 69)
- 01/11/19--07:31: Re: Photoshop images don't fit?
- 01/11/19--07:41: Re: MOGRT - Text Properties Don't Work
- 01/11/19--07:46: Re: Open Captions won't update changes
- 01/11/19--07:48: Re: .srt import and editing not working in Premiere CC 2019
- 01/11/19--08:00: Re: MOGRT - Text Properties Don't Work
- 01/11/19--07:59: AS-11 Vidchecker Fail due to structural problems/picture essence
- 01/11/19--08:15: Re: Adobe Premiere CC 2018 Video Issue
- 01/11/19--08:10: Obsolete Audio Filters and Lables
Thank you for your feedback !!!! After some tests I finally find out how to make .srt works in Premiere, but.... for me that is a bug !
1 - Start Adobe Premiere CC 2019.
2 - Load the video on the timeline.3 - Import .srt files and add it to the timeline. From now I can't edit the .srt layout (only have the preview in the Captions tab).
4 - SAVE AS the project
5 - Close Adobe Premiere CC 2019, start the software again.
6 - Load the project and now you can edit captions layout.
If you import other .srt, edit won't be possible until you save the project and restart the app....
To sum up.... when you import .srt you have to save the project before any edit of the captions layout..... (sic)....
What does burning in mean?
This is taken from the BBC delivery spec pdf.
1.6.3.Frame Rate Conversion
To prevent image degradation, Motion Compensation standards conversion sometimes known as Motion Predictive or Motion Vector Conversion should normally be used.
Speed change is the preferred method of converting from 24fps (including 23.976fps) to 25fps. Due attention must be given to the audio. Software standards conversion packages should also use Motion Compensation processing. It is not permitted to use simple “timeline” conversion. Contact the broadcaster for more information.
I'll have two simple question.
Have you tried to do it in Premiere with your footages?
What is your export format ?
You can keep multiple versions of an app. You can't keep multiple dot versions of a single version (e.g. only one from 2018, not multiple). Both of those have been true for a long time. Two "new" things happened here: 1) they changed the installer to a default of "remove all old" and made it a preference you can pick (or reject) and 2) they immediately removed all versions of 2018 (to install/reinstall) except for the final dot release. So if you uninstall 2018.1.1 (intentionally, unintentionally, hard drive failure, whatever), you can only install 2018.1.2.
My answer is post 5 is all I have heard: older versions, dolby was a major issue. Recent, e.g. 2018, no reason I can see.
That worked.... enabling all 3 options let me change the font size. I'll file a bug report. Thanks!!!
Either one of your files is corrupted, or the Cache of that files is corrupted.
Delete all the caches AND the preview files associated with that project and report back
Here in 2019 with same problem, I've got the newest version too. It's never done this before, I've only been using for a couple of months now though, but I save my projects multiple times while working on them in case of something like this but have never actually had something happen.
Are you opening a brand new project with PP 13? Or are you opening a Project that you already started with PP 12?
Also, by Updating your setting might have been reset, including the cache folder location and the Renderer acceleration might have reverted back to software only.
Did you try a new project with the new PP or are you attempting to open a project that you already worked on using PP12?
Please try to switch the Renderer to Mercury Playback Engine Software Only and check if it's working properly.
Let us know if it helps.
Just had same issue. Intel updated graphics driver last night. I updated Intel Graphics 530 driver again (version 22.214.171.12423) and got Premier running with rendering and playback settings with GPU Acceleration. Timeline playing back fine on 1080, full resolution. Check dates on Intel graphic updates, that might coincide with Premier issues. Good Luck.
Your image from Photoshop has a pixel aspect ratio of 1:
It needs to be 1.2121 to match the sequence you want to use.
Post a link to the bug report (in uservoice) so we can upvote it.
Open Captions (compared to Closed Captions) have only 2 options when exporting the sequence: None (ignore) or "Burn in" (include the captions in the actual video stream). You can also export an Open Caption stream from the Project Panel as a srt or stl file.
Alternatively, when exporting from the sequence, Closed Captions can be burned in, ignored, embedded, or exported as a sidecar.
You must know you final goal(s) when deciding the caption type to use in your project and how it is going to be exported from PR.
Glad you found a way. I do not have to take those steps to get a caption stream to edit. BUT, when I do occasionally get this bug, it is steps like yours that may get it working again.
I think I did... I reported it at some Adobe report bug page.
I’ve recently had a video fail on multiple occasions going through the Vidchecker.
The file is an AS11 for broadcast, and uses the same template project as the last 40 or so exports which have passed Vidchecker with no issue.
The main error to come up is:
Found 3 structural - problems with AS-11
UK DPP conformance:
- Picture Essence
Descriptor item 'Black Ref Level' must be 64 (when present) but was 0. - Picture Essence Descriptor item 'White Ref Level' must be 940 (when present) but was 1023. - Picture Essence Descriptor item 'Color Range' must be 897 (when present) but was 1023.
This is something the techs themselves have not seen before.
It has occurred to me that this may be related to what I have on the timeline - I have two colour mattes over the top of everything - a black and a white, with their blend modes set to lighten and darken. This is to prevent any stray pixels from going above or below legal luma levels. A technique learned in “The Cool Stuff in Premiere Pro” by Jarle Leirpoll et al.
My question is, does anybody else use this method for broadcast safe levels, and if so have they encountered any errors recently with their videos going through Vidchecker?
If anybody uses other methods to ensure Broadcast safe levels would they care to share them? I personally find the video limiter effect on its own to be less effective.
It is also worth noting that during these passes through the Vidchecker, it at one point indicated the colour bars were not at 100, when they definitely were. It also flagged a title sequence for harmful flashing, when the title sequence has remained untouched in 35 weeks of broadcast with no issue.
Could this just be a error with a new Vidchecker update? If so how best to proceed and avoid such issues again as there are many more TXs to deliver.
All help appreciated.
I have deleted all media caches and preview files, recreated both of them. I've also tried uninstalling and reinstalling premiere pro and media encoder. Still no luck. I'm really not sure what the problem could be, but what I do know is that with all the work put into what I have created currently, I definitely cannot just recreate it.
I used a "deprecated filter" which appears opening the project as such:
Audio Filter obsolete: Adaptive Noise Reduction
I changed and used the RX7 Voice denoise from iZotope, which works better
As this message appears opening the project I might have left this obsolete filter in one or more clips As they are thousands, is there a "fast" way to locate these filters, OR if I was able to remove it everywhere I used it does it appear for some mysterious reasons in project file no matter if it is in use or not?
I selected one by one A1, A2 ecc audio files attempting to remove the AUDIO filters Property butI never saw the Obsolete Adaptive Noise Reduction in the list to Remove.
In my Effects window iZotope RX7 Voice denoise (and all others from iZotope) appear 3 or four times ... how can I just keep one in my list? I placed them in the system Library not int he Users library ... so I don't understand what to do-
I unlinked every "linked Video-Audio files" in my editing I occasionally need to move the audio as off screen voice, using a different section of the VIDEO part as a reaction shot with no audio.
As I have 8 different Audio tracks as Dialogue, Dialogue 2, Voice Over, Music, Foley, Other sounds, Atmosphere and so on, I hope to colour each label according to my editing needs.
Still if an AUDIO clip comes from a MOV file, no matter if I unlink it, attempting to assign it a different colour label also the corresponding VIDEO file colour label changes.
Is there a way to avoid this, so my various AUDIO files keep their own label as I assign it, without also changing the colour in the VIDEO file?
Thanks a lot to anyone who care to answer