[Alius Sato]

thanks, @ht davis. you actually know your stuff! i’ve spent 3 hours this morning to figure out the best upscaling methods – as common as the task is, the web is full of ignorance and outright misinformation.

yes, ae detail preserving does OK for me – as did instant HD advanced in the past (discontinued, even if its algorithm had something others don’t – pick add’l resolution from the neighboring frames).

for image sequence, maybe alien skin blow up will do – and it automates some of the steps so you don’t end up in computing limbo. trying it now.

[Alius Sato]

“Can you not flatten the Timeline to a single Track before you Export the EDL.”

yes, i can flatten it. or export two EDL’s where the handles for dissolves are taken on.

but i still think that manual “force reconform” should work – after all the mistake, if any, would be mine, not resolve’s.

however, i’m currently making some headway on recreating the sequence from the render files in premiere BEFORE export. if that succeeds, it’ll be the better way of dealing with this.

[Alius Sato]

[Brent Marginet] “Although this could be a good idea it’s basically not possible unless you want to recut with the render files.
“

well, recutting with the render files is ok, if i don’t have to do it manually shot-by-shot.

i’m actually making some inroads here. if i re-import the render files to the project, i can make a new sequence in the chronological order of the original sequence in-TC. this would work perfectly if i throw out old renders and re-render, otherwise the resulting timeline will contain old versions of the render files as well.

is there a way in premiere to discard renders not in use in a given sequence? this would sort out my problem.

[Alius Sato]

[Glenn Sakatch] “just output an uncompressed quicktime, and use that as your source in Resolve. Output an edl, and use that to cutup the quicktime in Resolve.
“

yeah – great idea. it will still cause me gray hair when there’s a dissolve in the footage, but that’s only a handful of spots to tinker with. and by adjusting the cut / choosing the right tracks in premiere, i’ll be able to ex-/import a 2nd edl for dissolves only – containing the necessary handles.

a sample name for a premiere render file:
Rendered – 794ab695-05f9-48fd-8f7a-fb49bea4017b.mxf
with a corresponding metadata file:
Rendered – 794ab695-05f9-48fd-8f7a-fb49bea4017b.mxf.xmp

and yes, the metadata doesn’t seem to contain a reference to the original file name, just to a cryptic internal name that premiere has given it.

[Alius Sato]

bump. anyone?

[Alius Sato]

just to chip in to an old thread to save someone some time.

this problem exist also on avid 23.976 projects, where the content exported to QT from the timeline is longer than the TC tells you it is.

and the conversion factor is 30/29.97 – which can then be used as a base of adjusting timings of subtitles. which basically means that the TC IS drop frame-adjusted.

i’m not sure where this comes from, but suspect there’s some legacy 30i problematic going on. quite a bit of extra work results – not to mention the time wasted figuring out what actually IS going on when durations don’t match.

[Alius Sato]

it’s red.

edit / preferences / export – has various fields settings, they’re all set to “none.” and my feeling is that these don’t get used when working off of an NLE timeline.

render out of the red to an intermediary file does get me progressive frames – and i DO get the field order, or none, choices on the render menu, i just tried it. but then i’m into the export/import loop that i’m trying to avoid…

[Alius Sato]

see, i’m running red off of the timeline of mc 5 – and therefore i’m never seeing that menu.

i guess for kicks i’ll try to render outside of the avid and see if that would help. though of course my love of boris is entirely based on it working from within the NLE.

[Alius Sato]

i’d love to do that – but have not found such a setting. have you?

[Alius Sato]

played around quite a bit with those.

my “render farm” is an i5 / 6Gb RAM box. seems “render multiple frames simultaneously” slows it down. not quite sure what the ideal memory settings would be.