Jump to content

Recommended Posts

Posted

I posted this question on the Resolve forum and only got so far. I don't expect any Resolve experts here, but the problem is pointing to something in the way I"m exporting an image to a TIF file. The relationship between my use of Affinity and Resolve is this: you can produce a series of TIF files, numbered sequentially (tif.01, tif.02, tif.03, etc) and select them all and drag them into Resolve and it magically transforms the series into a viewable movie sequence. I'm doing this for a series of drawn, animated frames.

So.....

I have this little character that I've been playing around with the color, using Affinity. These end up being a TIF sequence in Resolve. The first picture shows what I created in Affinity and saved as a TIF (or as Affinity likes to call it, TIFF), WITH NO LAYERS.

Bumper#6-01test2.tiff

In AFFINITY he had a green nose at first and when I brought him into Resolve and keyed out the green background, the nose disappeared so I went back to Affinity and selected the nose and changed it to the chartreuse color to match the eyes.

Then I brought him with his chartreuse nose into Resolve and oddly, when i placed the single TIF file into the timeline (it automatically creates a five second clip) and played it, the nose started as the original green and then popped into chartreuse and then back to green again. In another part of the program called Fusion, it flickered wildly from green to chartreuse back and forth repeatedly. Either way, the point is that even though the single tiff file had a charteuse nose, in some frames it was the original green! Going something like GREEN (12 frames) chartreuse (36 frames) GREEN again ( 12 frames).

I tried the same thing but exported the chartreuse nose version as a JPG file and it worked fine.

I tried the same thing but exported with a blue nose and it worked fine.

And most importantly, with the original problem file, I took that into Photoshop 6 (yes I still use that) and re-saved it as a TIF file. And it worked fine.

So...either Resolve doesn't like the charteuse that Affinity exports. OR Affinity is including some vestige, some ghost, of the original file.

I'm going to include the saved AFPHOTO file, where you can see the color correction I've done to go from the original to the chartreuse nose.

Bumper#6-01.afphoto

 

  • Staff
Posted

Hi AndyV,

I can see from your post on the black magic forums that you since have re-opened the file in Davinci and it seems to be working correctly. Is this issue still present?

Thanks
C

Please tag me using @ in your reply so I can be sure to respond ASAP.

Posted

Oooh, surveillance at its very best. 😄

As you might have seen, the problem I had one day, disappeared the next day. So in the sense that I still have a problem, no I don't. But in the sense of whether I figured out what the problem was, no I didn't.

I have no idea what originally caused this to happen, nor why it suddenly disappeared. I have since imported about six different TIFF sequences that I made in Affinity AFTER that one problem and they all worked perfectly well. They were all exported in Affinity in the same way that problematic one was.

I guess I'll just call this an example of "the ghost in the machine" and hope it doesn't happen again.

But if you're asking this in order to delete this thread, be my guest.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.