Blackmagic Forum

Thread starting here for Unexpected Behaviours to feed into the FUSION integrating team.

(also - I am reading the manual to learn FUSION and so it is highly probable that I might report something that that is not really a problem ... just a lack of understanding!).

B5_001) Creating a FUSION Database. : Lower Case not allowed?

ISSUE : I started trying to create a DB and got confused for a moment when I couldn't call the database '2018_FUSION_TEST' ... the cursor got stuck at '2018_'.
I started testing the Keyboard out .. and quickly realised that LOWER CASE letters are not allowed in DB names.

SUGGESTED FIX 1 : Why not accept upper case and change the case to lower rather than do nothing (if there is an internal limitation on accepting Upper case)? With no warning on the screen I just assumed there was Keyboard Hardware error...

SUGGESTED FIX 2 : Perhaps allow Upper case? (Might be more readable in the UI for those that like Upper Case).

002) MediaOut : Viewer out issues.

ISSUE : When MediaOut is point to Viewer 1 ... and then a node is updated to ALSO point to Viewer 1 .. the Tiny white dot in MediaOut is NOT Removed.

When you play around for a couple of minutes (choosing a node and pressing 1 or 2) .. eventually MediaOut output stops being sent to the viewer.

In the attachment .. you can see that MediaOut should be updating the LEFT Viewer ... but the viewer is BLANK.

RELOADING PROJECT : Fixed this bug.

AJ

003) Drop down Menu ON/OFF has THREE states.

Just a curiously .. why de the Drop down Arrows have three states?

If you press a drop down arrow:
1) (click on arrow) Drop down menu displayed
2) (click on arrow) Menu vanishes
3) (click on arrow) Arrow is HIGHLIGHTER.
4) (click on arrow) Drop down menu displayed

Suggestion - I can't see any benefit in step 3. It seems counterintuitive.

AJ

004) No Subview in 2D yet?

The manual mentions that 3D subviews are not yet ready.
I took this to mean that 2D should work (like Histogram / Metadata).

I managed to get an empty Grey bar appear in the top left of the Viewer - but no Subview for any of the options (tried them all).

AJ

hi,
001) Only lower case: yes
002) MediaOut: Viewer out issues: can not reproduce on windows 10. Everything works well



003) wait. is new.

Thanks for the input Jean.

'Sure is a nice microphone you have there

AJ

005) Duplicate of Timeline on FUSION tab -> New node tree not CENTRED

(I would add that when you open up an existing Fusion timeline .. the nodes are also LEFT justified. I can't seen any benefit in being LEFT justified? The fist action I ALWAYS have to do is to make the view the maximum magnification my screen do to the font size being too small on my 4K screen).

AJ

006) Quick Duplicate Project : Very very Slow Project RENAME

Steps
===
+) Ipad Clip -> CTra
+) Save project (approx 8 sec)
+) Duplicate Current Project (approx 5 sec)
+) Rename Current project (ie the Duplicated Project) : Approx 30 seconds.

Is there something wrong with Current project RENAME that causes it to consume (in this case) 8 time more processing that a PROJECT duplication?

MISC : Fusion Memory pressure (bot right of screen) looked unchanged during the Rename.

AJ

[ADDITIONAL INFO #1] There seems to be a correlation between the number of times THREADs 'hung' and the length of time Timeline_Duplicate or Project_Save takes.
In Attachment I noted Hangs increase about once every two seconds during Timeline_Rename.

007) FUSION CTra (Camera Tracker) : Progress reporting.

0% -> Pause 99% -> Solved

A time ESTIMATION would be useful - especially when trying to LEARN what parameters give an acceptable solve time.

AJ

** UPDATE ** : BRYAN advises below that this is not a BUG - but a FEATURE of FUSION9.

My interest on feedback of processing is partly due to the currently stability (ie not knowing if the App has hung), or also to understand if I have kicked off a Track that is beyond the capabilities of my machine in the available timeframe.

008) FUSION CTra (Camera Tracker) : PROMPT before Deleting TRACKs that could result in there being insufficient Tracks to Solve.

Suggest that this is a config check that defaults to CHECK.

AJ

009) FUSION SETTINGS : After selecting 'Path Map' - Beach Ball displayed in GUI for about 40sec (GUI unresponsive).

AJ

010) Camera Tracking : Thread Hangs - BM to review during FUSION integration.

Simple camera track of 720p material to see if there any tell-tale signs that somethings in not working during protracted computations. In this case Camera_tracing.

T=0 : Less 300 thread : SOLVE started
T=1 : Solving 0% : 3268 MB : 0 Hangs
T=17 min : Solving 99% : 0 Hangs
T=73 min : Solving 99% vanishes : Beach Ball on screen : Hangs Increasing roughy every 5 seconds :
T=74 min : Total number of threads 3535

- - - - This seems like quite a lot of threads - - -

T=79 min : GUI refreshes : Threads shoots down to 232 : Memory pressure 4349 MB
T=80 min : Solve Complete.

Looking at snapshots (samples) of processes when there were 3535 threads ... there were a lot of dependencies (mutex). As there did not seem like any memory pressure (64GB machine) .. is there a resource timeout?

AJ

011) Render Range - Right Click on Timeline -> Set Range not working.

TESTS:
+) Right Click on Timeline -> Set Range = Couldn't get it to work.
+) Setting DIRECTLY in rect rectangles = WORKS
+) Command clicking on Timeline = WORK

AJ

012) Composition last frame -> Takes you to the FRAME before the last frame (ie not the last Render Frame)

AJ

013) Playback stopping when LOOPING is switched off.

BUG : Stops ONE FRAME before the actual end of RENDER.

AJ

014) J K L

SUGGESTION 1
As the WHOLE timeline is on view - can I SUGGEST that.

Pressing in order
L : Play at x1
L : Play at x2
L : Play at x5 speed
L : Play at x10 speed
L : Play at x20 speed
K : Halt Playback

As this would speed up navigation for that want to.

SUGESSTION 2
+) Use an ICON next to the PLAY Icons that let you know what the PLAYBACK speed currently is.
(example attachment from another App)


AJ

015) Half Speed Playback : Keyboard shortcut suggestion.

SUGGESTED SHORTCUT :
HOLD DOWN K : Press L = PLAY FORWARD AT 0.5 x
HOLD DOWN K : Press J = PLAY BACKWARD AT 0.5 x

AJ

016) Half Speed Playback : FUSION errors

Errors as FUSION could not find HALF track errors.

AJ

017) Playback after Range has been been moved & no longer includes current frame.

Currently nothing happens.

SUGGESTION : When Play is pressed - relocate to First (or LAST) frame in Render Range - and then continue playing.

AJ

018) Deleting Camera Tracker 'selected tracks' -> After a solve can take ages.

Usually takes a few seconds.
This time ... more like 10 minutes.

It might have something to do with MacOs reporting thread hangs every 5 - 10 seconds.

AJ

Antony Newman wrote:007) FUSION CTra (Camera Tracker) : Progress reporting.

0% -> Pause 99% -> Solved

A time ESTIMATION would be useful - especially when trying to LEARN what parameters give an acceptable solve time.

AJ

This is a known issue with the CameraTracker in Fusion 9, also. The very first step of automatically calculating the seed frames takes forever, but it's really just one step from the perspective of the progress bar. If you set the seed frames by hand the solve will probably take less than a second.

Thankyou for your input Bryan.

As I am totally new to FUSION - and am calling out everything that I think is unintuitive or broken.

I will update this 'Bug' as a FEATURE in this thread.

AJ

lol. I'd still call it a bug. It's just not the bug you thought it was! I know the devs are aware of the problem because it almost wrecked one of the presentations at SIGGRAPH last year. They've apparently all been tasked with getting the integration into Resolve working, though, so I guess there hasn't been manpower available to address it.

016:
That is also not a bug, the 0.5 is not half speed playback its half a frame step. You know frome the days we had fields in video footage?!
If you set the timeline to increase by 0.5 frames it can not find the half frames because your footage is only full frames

Thanks for the input Michael.

When the BM manual suggest that many graphics are calculated mathematically - and that having key frames (I presume it was keyframes) that were not completely alligned with frames could be of creative benefit - I was anticipating expectation on this part to place the Playhead in between distinct frames.

If this is the case - then I would not expect an error to be created (this could be that I am a newbie)

I also note (although not uploaded to this thread) that I get similar errors even on whole frames when switching in and out of the Fusion tabs - usually only on the Current playhead position.

To be honest my use of playback at half speed was intended to allow me to confirm that a visual effect would work even under close scrutiny.

As FUSION & FARLIGHT & EDIT tab have slightly different ways of doing the same thing - I am hoping that the BM team (when they get a chance to sleep!) will unify the controls.

AJ

[b]B6_001)[/b].

Minor issue :

+) When editing Spline - it looks like the OLD and CURRENT graphics are displayed.

+) Switching Tabs (eg FUSION -> EDIT -> FUSION) does not clear the OLD spline information.
+) Restarting FUSION DOES clear the OLD spline information.

I am guessing this is a bug as I cannot think of a good reason to have the old data on the screen (unless this is useful to compare before and after?)

ATTACHMENTS:
1) After making a few change - you can see the OLD position the SPLINEs were in.
2) After a RESTART of Resolve -> ONLY the CURRENT position information is displayed.

AJ

Here's my experience finishing a VR project in Resolve 15.6_beta.

I was very excited to try the Panomap tool within the Fusion tab. Being able to rotate a VR latlong to adjust the 0 degree of a shot and color/finish/title all within Resolve is a dream come true for VR projects.

Is practice however, I was having random black frame renders on every shot I tried to use the Panomap. Issue duplicated on multiple systems pulling media via 10gb fiber to a 24 drive raid array. Eventually got the project out, but I wont be doing that again until this issue is fixed.

Project specs:
Timeline Res: 5760x5760
FPS: 59.94
Media: DPX 10bit

Workstation specs:
4 x 1080ti
2 x 2697v2 Xeon
256 GB 1867 DDR3 system ram

B6_002) CRASH

Crash adding tool bar nodes (first time adding them in FUSION).

AJ