When doing time lapse, my workflow has been to import the stills, create a sequence, then usually, convert it to HQX in the bin. I'm working with 16-bit Photoshop graded files. Up until now, I've been working at BT 709. I just discovered that when I import the 16 bit Photoshop stills into the bin- I've also tried it with 16-bit TIFF- even though my project settings are set to 2020, under properties, they will show as BT.709. So, I'm really not sure whether the files are being bitrate neutered on import, or what might be happening. The other HUGE workflow problem, is that if I select an image in the bin, I can go into properties and change the 709 color space to 2020, but besides not knowing if the origional bitrate was preserved in the first place, I'm not able to make this change on more then one image at a time. If I select several images in the bin and change the properties, the change will only be applied to the first one. And, when dealing with a 450 image time lapse, this is not a pleasant thought. Furthermore, since my usual workflow would be to put all the stills in sequence anyway while in the bin, I tried doing this first, going to properties on the sequence, and applying the color change there. Well, the properties for the sequence, will not allow any color changes to be made to it and shows 709 by default. Not good!! So, if I then do a bin conversion of the sequence to GV HQX, I can then change the color in properties to whatever I want on the interim coded sequence, but again, I have no idea if I have lost all the extra color data during the origional import. I realize that I won't be working with 16-bit, but 10 bit, but I sure don't want to be working with 16-bit down converted to 8-bit, and then upconverted to 10-bit.
Any thoughts on what is going on here?
Also I should add that working with these 16-bit TIFF, or Photoshop images, in Resolve is impossible. Resolve imports them as a corrupted sequence, while Edius does the sequencing just fine.
UPDATE:
While I'd still very much like to know what might be happening in Edius, I tried the multi image import and sequencing of the 16-bit images in DaVinci Resolve. I haven't tried this since the failed attempts about a year, but Resolve has had a few updates to 16 since then. It now works fine and shows that the sequence is 16-bit. Hopefully, this issue can be resolved with Edius. I'm using Edius X.
Any thoughts on what is going on here?
Also I should add that working with these 16-bit TIFF, or Photoshop images, in Resolve is impossible. Resolve imports them as a corrupted sequence, while Edius does the sequencing just fine.
UPDATE:
While I'd still very much like to know what might be happening in Edius, I tried the multi image import and sequencing of the 16-bit images in DaVinci Resolve. I haven't tried this since the failed attempts about a year, but Resolve has had a few updates to 16 since then. It now works fine and shows that the sequence is 16-bit. Hopefully, this issue can be resolved with Edius. I'm using Edius X.
Comment