Chris Wright
1
Audio Coin
1
COW Coin
Forum Replies Created
-
if its 8 bit or 10bit depends. You can go super quality visually lossless DNxHR 444, DNxHR HQX or completely lossless with 8 bit full uncompressed png quicktime or 16 bit EXR full math lossless.
-
you render out the whole thing as 23.976. not individual clips. you don’t import 23.976 footage onto a 24 fps timeline, you interpret framerate to 24, then place that 24fps into a 24fps sequence. there are no gaps because you have a whole movie with no cuts.
-
export the 23.976 out in a 23.976 timeline, then re-import in and interpret footage as 24 into a 24 timeline. this will change both the duration and audio without making spaces.
-
you have to render it out so its all one video so it all changes at the same time.
-
XAVC? that will be cpu bottleneck. I wouldn’t buy anything that much unless I perused pugetsystems’s detailed breakdown of what footage needs what RAM. in what program.
-
how are you comparing them? each program has its own particular flavor of color management. do they match if you import then into the same program window? are you using an external monitor? what is your monitor calibrated to?
-
have you tried creating the EXR with adobe only products? I feel fusion is the wildcard here. At least you’d be able to isolate the variable of EXR render output with assigned profiles.
I made an EXR from AE 32bpc and its luma matches, although the active window will be a little off so the pixels will be shifted a little bit. In Resolve, settings for levels should be set to auto so you don’t export video levels(which might be your issue hiding in fusion)
There is also the free AE plugin opencolorio used by ACES for color management as well if you want to get complicated with ACES workflow in AE.
-
29.97i? or P? you can get smooth motion with ‘i’ with low data rates compared to 59.94 p. Both should look the same on an interlaced display. Your final destination will decide how you record. web likes progressive.
-
isolate the variables first. try a new project with jpegs, TIFF, PNG, then quicktime, then check crash logs, update video driver, check read/write permissions(adobe has a page on this). try .wave, then mp3, then variable h.264 (ran through handbrake first.)
-
1394 is firewire. do you even have firewire on your motherboard? I’d try using a virtual machine operating system and install an older OS for something like this. Step 1 in windows 10 was to delete all legacy hardware support. You might need an old hardware machine as well. There might be some 3rd party products that have 1394 for the year 2019, but from what I can remember, 1394 was almost direct IRQ input(lower level than directx)