|
|
Search
You searched for the word(s):
Showing page 3 of 1,680 (16,799 total posts)
< 1 second(s)
-
The issue could be that your recordings are in the HEVC format, but your computer doesn't have the hardware for PS to work with HEVC.
-
I'm not really clear about what you are trying to do, but I'll just mention that you can also use the Corrections editor to put internal markers on the the clips, and this might be of help to you.
The Text format EDL was lost when they brough out NGStudio, so the timecodes aren't accessible to the user, but I'm sure it is something that could be ...
-
The intended workflow for this function is NOT to do your clip spltting on the timeline, but to pre-trim the clips you want in the source viewer using the Mark In and Mark Out callipers and then putting that on the timeline (yes, I know it sounds more work, but that's the way many professional ediors behave). The clip trims are retained with the ...
-
Could you have some sort of keyboard or mouse fault? Something resting on the edge of keyboard? It doesn't sound like an issue I've ever heard of.
-
A lot of people use a free program called Handbrake.
-
Sorry, do you mean ''Render'' as in create the Playback Optimisation Preview files (the brown/green bars), or render as in Export?
There is definitily something wrong with creating the PO files for Time Remapping (on Pinnacle's radar). I've not seen the issue with export, but I've not experimented with the reverse option.
-
Did they also take a huge amount of time to export?
-
If you have used the h.265 (HEVC) codec to record on the iPhone you won't be able to see them in PS 11 - the program is far too old to support that codec. Convert to h.264 and they should work.
-
This is typical of smartphone video that has used a variable frame rate to record. It's a good idea to convert to footage to a fixed rate before editing. Check the rate of the source before you take any other steps.
-
I concur.
This must have been fixed by Microsoft. It certainly wasn't anything that Alludo have done, as the problem still existed after the last patch to 26, and there haven't been any patches to earlier versions since before the release of 26.
3 ...
|
|
|