Michael Nielsen
Forum Replies Created
-
What happens if you change folder name in mxf folder from 1 to 2 and try to relink the files from the folder? I have experienced the same thing when doing an aaf export from avid and import into after effects. Everything sits in order, but none of the videos show up, although – if I do the same thing inside of premiere pro, batch-relink and then drag the sequence to ae, no problem.
Im wondering if some metadata inside the aaf is telling the other software that codecs or whatever are a mismatch?
-
Thanks for the thoughts. Trashing prefs did not resolve the issue.
I am running a Windows 7, i7 2600K hyperthreaded, tho I dont use multiprocessing for internal renders, 32gb ram and an array of nas, local drives and ssd´s. Dual gtx670 cards, but the preview is not rendered with raytracing enabled. Latest CC-update.
The issue is more of an output than an input based one. Everything I import, ranging from .ai, psd and jpg-files to camera and output based .mxf, .mov, .mp4, etc. has presented this issue, but only if the ram render output is an .avi container. Mp4, mxf, mp2 and image sequences fly just fine, but some are of course sorely missing in depth and so on.
I just want a complete lossless translation of the ram-preview and I want it in .avi. But the issue persists. Is it possible that the .avi becomes so big that its choking my pipeline?
-
Thanks for the input. The odd thing is, if I use another codec, say h.264, for the preview render, it flies just fine. I only have this issue with .avi.
-
There is a project management option that allows you to collect and condense projects using only content present in sequences, handy for both archiving and moving large projects between systems. You can even decide for using handles or not, although that does put a strain on re-export.
-
If your banding persists, usually in darker areas, in the codec and container conversion from prores to h264, you can tick use maximum render quality in export settings to avoid that issue. Dpx is nice but very large, you should be able to export prores from davinci just fine without those issues.
-
While your problem may end up having to do with 3rd party issues, before actually creating your sequence, you should be able to define a custom codec for preview rendering in the new sequence splash. There are three tabs in the splash, presets, tracks and settings. Inside of settings before creating the sequence you can select which codec to use for preview rendering, and only then. Not sure if it helps tho.
-
If you can open media encoder by itself, try importing your .ppro-file and choose the sequence you want to export through the dynamic link server. Maybe specify a different disc than the one, you have tried exporting to? Sequence settings may mismatch altho it should be identical. Could have something to do with the settings. Can you provide some insight on your native material, res, framerate etc.
-
Seen it too.
That problem has forced me to have both programs run side by side, it eases importing and the dynamic link responds without stuttering.
Question is – do you have your edit open i PP before opening your AE comp?
-
IF youre not afraid of some trial and error time, you might be able to maintain large portion of quality in an .mp4 (h.264) compression using a bitrate below 4.0, say 3.0 in SD, for upload.
If youre able – not through the quicktime codec, but straight .mp4 – it should land you around 12mb/minute = roughly 540mb for the 45min, but it very much depends on the amount and change of colors in your video.
Good luck.