
- Posts: 2
- Joined: Mon Sep 25, 2023 8:08 pm
- Real Name: Massimiliano Pecchiari
I have this problem on different workstations (Apple StudioUltra - AMD Threadripper), so I think it's a structural problem of fusion.
In any case, the characteristics of the PC with which I write and I captured the screenshots are as follows:
CPU AMD Ryzen9 7950X3D;
Motherboard Asus ProArt X670E-Creator ATX 128GB;
RAM 128GB GSkill Trident Z5 Neo (Mod.ExpoII);
Video Card ASUS NVIDIA GeForce RTX 4090 24 GB GDDR6X;
SSD Samsung 990PRO (4 on board to manage from different disk OS - working clips - chace disk - broll)
Windows 11 Pro 22H2 OS Build 22621.1992
- Before describing the problem, I explain the most inexplicable thing: once my node editor structure in Fusion is finished, I have a correct representation of the work (as it should be) on the Fusion MediaOut, but when I go back to the Edit Page the result instead is different and are being generated - error displayed.
- this error persists despite having done: erasing the chace, reloading the DRA, exporting video in different formats, installed up to the latest version of DR 18.6
- I've never considered the option of using saver - loader nodes, because I work in BRAW and RED RAW, so I MUST have to keep the advantages of RAW up to the Color. I purposely bought an Ursa 12K to have maximum compatibility in DaVinci...
- The problem persists even with only BRAW jobs with Ursa 12K and BMPC 6Kpro.
- Same problem regardless if I use BRAW or ProRes444 from Sony camera.
WORKING:
the problem generally occurs whenever I have a clip where a subject moves over a background and I need to retouch the background.
Obviously if the subject moves I must fragment the intervention on the background to use the parts not occluded at that moment, therefore I have to use a Time Strecher node to freeze the frame, so I correct on an area which will then be merged with another area with the same technique. To carry out this correction we will therefore mainly use the nodes of Time Strecher - Paint - Matte Control - Merge.
Then, now I must isolate the subject using a mask (Polyline or Bspline) which acts on a Matte Control (inverted Garbage input).
Finally the moving subject will go to the Foregroung of a merge node where the Background is the result of the background correction performed by merging the different areas managed by the TimeStrecher.
My background interventions can be simple uses of paint only as a PNG application, etc
THE PROBLEM:
When I finished the job I check the mediaout and it's all correct, everything works perfectly, but when I go back to the EditPage it's a completely different result with the subject swinging some frames forward and some backwards like ping-pong and then jumping at the end of the frame.
MY THING:
My thought is that there is an incompatibility between Fusion and Da Vinci Resolve, a non-integration. The Time Strecher node works fine in Fusion, but handles time data incompatible for the Edit Page and DaVinci Resolve, which fails to interpret this data correctly.
I've already had other types of problems of this type in the past (which I won't list now), but this is the most serious problem because this actions is the basis of all my compositing works.
In any case, the characteristics of the PC with which I write and I captured the screenshots are as follows:
CPU AMD Ryzen9 7950X3D;
Motherboard Asus ProArt X670E-Creator ATX 128GB;
RAM 128GB GSkill Trident Z5 Neo (Mod.ExpoII);
Video Card ASUS NVIDIA GeForce RTX 4090 24 GB GDDR6X;
SSD Samsung 990PRO (4 on board to manage from different disk OS - working clips - chace disk - broll)
Windows 11 Pro 22H2 OS Build 22621.1992
- Before describing the problem, I explain the most inexplicable thing: once my node editor structure in Fusion is finished, I have a correct representation of the work (as it should be) on the Fusion MediaOut, but when I go back to the Edit Page the result instead is different and are being generated - error displayed.
- this error persists despite having done: erasing the chace, reloading the DRA, exporting video in different formats, installed up to the latest version of DR 18.6
- I've never considered the option of using saver - loader nodes, because I work in BRAW and RED RAW, so I MUST have to keep the advantages of RAW up to the Color. I purposely bought an Ursa 12K to have maximum compatibility in DaVinci...
- The problem persists even with only BRAW jobs with Ursa 12K and BMPC 6Kpro.
- Same problem regardless if I use BRAW or ProRes444 from Sony camera.
WORKING:
the problem generally occurs whenever I have a clip where a subject moves over a background and I need to retouch the background.
Obviously if the subject moves I must fragment the intervention on the background to use the parts not occluded at that moment, therefore I have to use a Time Strecher node to freeze the frame, so I correct on an area which will then be merged with another area with the same technique. To carry out this correction we will therefore mainly use the nodes of Time Strecher - Paint - Matte Control - Merge.
Then, now I must isolate the subject using a mask (Polyline or Bspline) which acts on a Matte Control (inverted Garbage input).
Finally the moving subject will go to the Foregroung of a merge node where the Background is the result of the background correction performed by merging the different areas managed by the TimeStrecher.
My background interventions can be simple uses of paint only as a PNG application, etc
THE PROBLEM:
When I finished the job I check the mediaout and it's all correct, everything works perfectly, but when I go back to the EditPage it's a completely different result with the subject swinging some frames forward and some backwards like ping-pong and then jumping at the end of the frame.
MY THING:
My thought is that there is an incompatibility between Fusion and Da Vinci Resolve, a non-integration. The Time Strecher node works fine in Fusion, but handles time data incompatible for the Edit Page and DaVinci Resolve, which fails to interpret this data correctly.
I've already had other types of problems of this type in the past (which I won't list now), but this is the most serious problem because this actions is the basis of all my compositing works.