Isaac Brillant
Forum Replies Created
-
Isaac Brillant
January 18, 2017 at 12:47 pm in reply to: Syncing and replacing sound after finished editing? Is it possible?This is a real PITA workaround but you could try it:
Take every shot from your sequence one by one and put them into a new sequence where they are in the order you shot them.
sync them with the good audio.
cut off the head and tail of the audio to match the clip length.
Match the clips with the originals on the original sequence one by one. -
Isaac Brillant
March 13, 2016 at 2:43 pm in reply to: How can I import or convert single MTS files into Premiere ProOld post but–
Does this mean that you can open the AVCHD package, remove the individual MTS files from the stream folder, RENAME them, and then if you bring them into Prelude, Prelude will recreate a new folder structure that PPro can work with?
And what will happen with spanned clips in this scenario?
And if so, can you do this in CS6 or only CC versions?
thanks!
-
Isaac Brillant
February 2, 2016 at 2:36 pm in reply to: How can I import or convert single MTS files into Premiere ProOld post but– This “show package contents” method is OK for just viewing the MTS files, but if you import it directly from here, or delete any files from here, or move any files around, Premier will run into trouble reading the file. Especially if a clip spans 2 or more files. In some cases you will get duplicate files, and the audio will not be in sync. The best way is to import it through the Media Browser to avoid serious trouble later on.
-
Isaac Brillant
March 31, 2015 at 12:36 pm in reply to: Scaling 1080 DSLR footage down to 720, but screening in 1080.Hi,
OK, I ran a test yesterday. I exported the following (all in Prores422 unless otherwise noted):
1) 1080 sequence exported at 1080 (where punched-in shots are scaled up to 150%)
2) 720 sequence exported at 720. (where punched-in shots are at 100% ie 1080 and the original shots are in 66.67%) Enlarged in quicktime player to compare to the 1080 export.
3) 720 sequence (where punched-in shots are at 100% ie 1080) exported at 1080
4) 720 export (where punched-in shots were at 100% ie 1080 before exporting) re-transcoded to 1080
5) 720p sequence (where punched-in shots are at 100% ie 1080) nested into a 1080 sequence
6) 1080p sequence (where punched-in shots are scaled up to 150%) nested into a 720 sequenceI then compared them in quicktime viewer, at 150% view. Keeping in mind that my footage wasn’t crystal sharp to begin with, and I added a sharpening effect– I hardly noticed a difference in quality/sharpness between them all. There may have been a very very subtle difference but I had to look back and forth a few times to tell which one was better.
I also exported the 1080 sequence (#1 above) in ProResLT and didn’t notice a difference between that and ProRes422.
-
Isaac Brillant
March 31, 2015 at 12:19 pm in reply to: Scaling 1080 DSLR footage down to 720, but screening in 1080.Thanks for all of your feedback.
HT Davis–
I just want to clarify that when you write “Since you’ve already scaled the video to 720 (you will never see the original quality again), you are not blowing up to original quality.” that you are talking about taking a nested 720 sequence and dropping it into a 1080 sequence. As opposed to scaling up 1080 footage in a 720 sequence to its full 1080 size, to create a closeup.
BTW, when I refer to zoom, I really meant a punch-in, not a camera zoom.
Why do you transcode at 60fps rather than 30?
Thanks!
-
Isaac Brillant
March 25, 2015 at 12:55 pm in reply to: Scaling 1080 DSLR footage down to 720, but screening in 1080.anyone? 🙂
-
Isaac Brillant
February 22, 2015 at 8:45 pm in reply to: Mac Book Pro vs Mac Pro for daily PPro Editing.Thanks for the advice. Based on what you’ve said, I’ve decided to get the MBP. I posted some other Qs in another thread though, regarding internal vs external drives, that I’d love your input on.
thanks! -
Isaac Brillant
January 12, 2015 at 3:34 pm in reply to: Audio Disappears & Error code: [/cloudroom/releases/2014.09/shared/adobe/dvamediatypes/src/ticktime.cpp-290]I forgot to mention that I am running Mountain Lion and am editing on CC, but I also upgraded to CC2014 to see what would happen and I have the same problem there.
So far I tried:
Deleting the media caches
Deleting preview files
uninstalling and reinstalling PPro CC
uninstalling and reinstalling PPro CC2014
creating a new project and importing the old project into the new one.
exporting XMLs from the sequences without audio and reimporting them into CC2014.
Importing those same sequences directly from an earlier project, using Media Browser. -
Isaac Brillant
January 6, 2015 at 7:53 pm in reply to: Premiere Pro CC 2014 source and program monitor fail to refreshHi,
Did you ever find an answer to this question? I’m having the same problem, in CC (not CC 2014), and restarting (the project or the computer) doesn’t fix it.thanks
-
In my case, the files were synced in the project before they had been correctly named. Now that they’re named correctly, I want the names of the clips in the project to match.
thx