Baz Leffler
Forum Replies Created
-
If you place a ‘transparency’ layer over the DV clip does that fix the clicking?
This will obviously give you a red bar indicating rendering required.
Baz
-
[Tim Mirande] “is there any way to effect a name change en masse in the main project file?”
What I do is open the .prproj file in notepad and do a ‘replace’ as per normal eg. replace “d/project/graphics” with “d/NEWproject/graphics” (all) etc. Word of warning… copy the original .prproj to a safe place in case you screw up.
Baz
-
My workaround is to apply a null filter to the incoming/outgoing DV clips to force render. I normally use ‘brightness/contrast’ set to zero.
Baz
-
A quick way is to…
1/ open a new DV project
2/ import your HDV project
3/ block select all clips in the timeline (ctlA)
4/ right click set “scale to frame size”But remember, as Steven suggests, you also have the ability to zoom up/reframe HDV in a DV project giving added versatility but remember you are zooming up mpeg artifacting as well.
Baz
-
George said:
——————————————
If I install the decklink card can I then just import a current DV-AVI project into a 10 bit ubcompressed project and get all the uncompressed benefits?
——————————————Once something is compressed it can not be ‘uncompressed’; it will always have any compression artifacting. Its like dubbing a VHS to digibetacam; it is still going to look like VHS when playing the digibetacam.
But…
If you just import your DV project into a Decklink project you get realtime playback as per normal with the added benefit of going directly out to a digibetacam via SDI (or Beta SP via component)
Baz
-
Seems you have the wrong project setting and deck selected as device control. Premiere thinks its exporting a HDV project.
You have to open a Decklink SD project and import your completed HDV project, select all the clips in the timeline and tell premiere to re-adjust frame size to project, then render and export via DL deck control.
Baz
-
Steven is correct; by “The panel menu” he could also mean the top right corner of the timeline window. (>)
I use the ‘sequence timecode start’ to set my timeline timecode to the exact timecode I am exporting to tape at. Most international program distributers like ‘picture start’ to be 10:00:00:00 so I set the timeline to 09:59:30:00 so my 30 sec clock can be the start (IN point) of my export to tape. This also helps when ever you need to revise a portion an need to re-insert it back into the tape. You can immediately refer the timeline to the tape timecode.
It is also valuable for checking export to tape accuracy and for drop frame detection over a long export. If a drop frame occurs on export then the later timecode numbers will no longer match between the timeline and the tape; then its just a matter of going back into the tape and comparing it with the timeline untill you find where the offset occurred and exporting from there (after you have determined what caused the drop)
As for doing source timecode dubbs I don’t find it too tedious to set the ‘timecode’ filter; hell! its only been there since PPro 2 and was almost impossible prior to that! The only thing I find strange about Adobes implementation of the timecode filter is that it defaults to ‘clip’ timecode (zero based) and not ‘media’ timecode which is in the most part what you want displayed in a pro environment. Once I set up the first clip its just a matter of cut/paste attributes across the lot; all done in about 5 secs.
My BIGGEST criticism of PPro’s timecode handling (and as I have mentioned before on these forums) is its inability to detect timecode breaks/jumps on capture which is more the fault of the avi wrapper format than Adobe’s. But as a work around they give you scene detect but leave the actual implementation of that feature to the capture card manufacturer who most deem ‘last on the list’ of their feature set. I have my work arounds but they certainly don’t suit everyone.
Baz
(been Premiere’n since V4.0) -
[Craig Howard] ”
Pg Dn to end of the clip then ALT “]””If you do this you get one frame of the next clip so you should frame bump back before you ALT “]”
-
The AVI format does not accomodate running timecode as such. The way the avi format works is to enter the timecode start info into the avi header and then does a frame count based on that… so if there are any timecode breaks it does not get detected (I have mentioned this elsewhere either here or at the adobe forums). You can thank Bill Gates for that one for not future proofing his products.
The only work around is to use a program that detects the changes and captures separate avi’e eg SCLive. Or use an Avid that captures Quicktime where running timecode is also entered into the data.