I am too lazy to be bothered looking for it again now.
Premiere Pro Reference
(.pdf 7 MB download)
I am too lazy to be bothered looking for it again now.
Premiere Pro Reference
(.pdf 7 MB download)
Hello,
I have been working on a few projects that use RED files for the source footage at 3840x2160 resolution, and when you create a new timeline based off of the source it will create a timeline that recognizes the source raw size and then use the I-Frame only preview codec at 1920x1080. So the source footage is being sized down in the timeline to accomodate the smaller size, but in the motion tab of the source footage Scale is represented at 100%. This is universal from what I can see like if using 1920x1080 source footage and the preview files are set at 720x480 the source is still shown as 100% scale. So when you scale up beyond 100% with source footage larger than the output size does Premiere still leverage the raw size and not result in a loss of quality? Or is it only an issue if you render it and use the preview files for the export? Some clarification on how the relationship between these elements work would be great.
As an aside to this topic, I used Pluraleyes 3 to sync footage through their app and export out an XML to import into Premiere, and instead of a typical sequence being made when using canon HDSLR footage at 1920x1080 i-Frame Only preview files, Pluraleyes made the sequences at 720x480 DV24P Preset for the preview files, and I didn't realize it at first and noticed the first export using one of those sequences did not look as good as it should have and I used the previews to create the export, so all of the synced sequences had to be moved to the usual sequence settings.
Did you read the WARNING here: Balanced Systems
DVCPRO HD on windows? Dude, That has never worked. There was a third party thing that cost about 300 bucks http://www.calibratedsoftware.com/products.asp to allow you to playback and export to DVCPROHD from quicktime on windows but that was during CS3 days.
Absolutely...now make it a sticky.
BTW its a 6.76 mb download according to my desktop file.
Hi All,
Vinay, thanks for the suggesttion, but that did not work.
Kevin - Yes, I'm using Quicktime Pro Version 7.
CC_Merchant - Yes I understand that, but I have used this 9800GT with CUDA accelleration for years with not a single issue. I'm certain that's not the cause of this problem.
JaysonM-Y - I believe since version 5 that you have been able to use DVCPRoHD within Premiere for playback (but not for authoring or playback in QT player)
Any other ideas?
Steve
What version of windows are you running on btw? I hear people get weird crashes and stuff running Windows 8 on specific laptops.
I'm running Windows 8 Standard (not pro) 64 bit. The laptop came with Win8. I haven't tried going back to Win 7 to be fair. I'm reluctant to do so as I quite like Win 8 (I know - weird!) and this laptop is touch screen although if I don't resolve this problem then the laptop has to go anyway, so everything is on the cards and I could try a Win 7 install.....
I'm going to try a full memory check tonight maybe that will shed some more light.
I've been running Premiere Pro, both CS6 and CC, on Windows 8 since summer of 2012 without any issues. It's more likely the new install, not the version of operating system, is what cleared up the issue.
Kevin, Thanks! Great info. Works perfectly. But I do not always have access to the SD cards. A lot of footage is given to me in the m2ts format. It sure would be sweet of Adobe to also import the m2ts metadata along with the file. Also the Sony app gives each clip a unique name which prevents inadvertently overwriting clips on the harddrive. I am no fan of the clunky Sony app but it is part of the workflow whether we like it or not.
Just came across the same problem, but for audio clips.
I'm getting into Premiere Pro and I'm getting mad drag-n-droppin' from 2 to 16 tracks of audio into my timelines.....
Any handy workaround to have my clips automatically stacked vertically ?
Thanks
Isn't that what I've just done?
No, you posted a new thread instead of searching for the two dozen or so others already on the same subject.
The extra .24 Mb reflects my level of effort.
Where exactly did the clip originate?