Bouke Vahl
Forum Replies Created
-
Sure,
select the file in the bin, ahd do a re-import.
Note that the duration of the old and new has to be the same!Bouke
https://www.videotoolshed.com/
smart tools for video pros -
Bouke Vahl
July 2, 2012 at 3:06 pm in reply to: Workable Premiere Pro –> Davinci Resolve Workflow with DSLR?Well, the project file is a bit risky to toy around, but XML is human readable.
I’m very much willing to take some money from you, but since XML is editable with a normal text editor, a search / replace operation will do the trick just fine!hth,
Bouke
https://www.videotoolshed.com/
smart tools for video pros -
Bouke Vahl
July 2, 2012 at 2:03 pm in reply to: Workable Premiere Pro –> Davinci Resolve Workflow with DSLR?Not sure if it helps you, but i’ve found Premiere to have a ‘memory’ for files. If you alter a file that Premiere already knows, it assumes the data of the first moment it saw the file.
Changing the file name can reset this, but probably that causes more problems then it solves.If the Reelname change from QTchange prior to importing to Premiere does not work, there is really something funny going on.
If that’s the case, contact me directly.Bouke
https://www.videotoolshed.com/
smart tools for video pros -
My guess is that it has been standard converted to something,
as indeed (almost) every frame is interlaced. No way you can go back to 24 with this sample.But how come you have a beta SP and do a downconvert to 24 trough the HDcam?
This makes it close to impossible to guess what is going wrong where.
Can you provide a sample captured 29.97 from your source betaSP?Another question, are you going to deliver 24P?
If not, why bother?Bouke
https://www.videotoolshed.com/
smart tools for video pros -
You could try to trash the media databases, let Avid rebuild them and try again.
Bouke
https://www.videotoolshed.com/
smart tools for video pros -
Have a look at Sync and Link
https://assistedediting.intelligentassistance.com/Sync-N-Link/But as always, test before you commit yourself.
Can’t you just put the polyfiles in your rendered QT’s?
Bouke
https://www.videotoolshed.com/
smart tools for video pros -
Is there common timecode?
If not, you’re in for a lot of work….Otherwise there are several options, depending on what you have.
So could you be a bit more specific?Bouke
https://www.videotoolshed.com/
smart tools for video pros -
Not in my opinion.
AMA gives me clipping on both blacks and whites, where import with RGB source selected does not.
It might be a version issue.So i would suggest, pick the one that gives you the best levels to your liking.
Bouke
https://www.videotoolshed.com/
smart tools for video pros -
Perhaps a little late, but nevertheless:
If your transcodes have filenames that resemble the originals:
(Like original.mov –> original_transcoded.mov)
you can use QTchange. Open the folder with the originals and save the TC attributes.
Then put the attributes files in the transcoded folder, and open the transcodes with the ‘ use TC from saved attributes’ checkbox checked, and apply them. (delete old tc tracks if needed)(Shameless self promotion, as i’m the developer…)
Bouke
https://www.videotoolshed.com/
smart tools for video pros -
Wild guess:
Avid sees the offending files as movie files instead of still images.
No idea why that could happen, but Jpg and PNG are QT compatible, so that ‘could’ be the case.Try opening a good and bad one in Photoshop, see what the differences are (RGB / CMYK, resolution etc..)
Try a copy/paste of the offending image into a good one and save, that ‘should’ get rid of any anomalies in the files…Bouke
https://www.videotoolshed.com/
smart tools for video pros