Blackmagic Forum

I have been using the Dust Buster.
It crashes every few frames of work done.
I am set to send reports automatically - do you need more?
I would like to use this tool but crashing so often it is becoming unviable.
My system should be able to cope, no?

The footage is Prores - would I improve my chances with a transcode to dpx?
W10 2004
DR 16.2.5
3950X
128 RAM
RTX 2080 TI
Nvidia 452.06 Studio

Does anyone have success with the Dust Buster tool?

Is it's node placement important?

Fortunately, I've not yet had need of it.

But if you want to share a short clip, I can test here.

Logs, and a project export .drp along with media, to attempt to repro the issue, could be helpful.

Thanks Dwaine.

well...

It's not that I am coy about sharing my logs n project but
I reflected on this problem further and realised that my test item is a timeline slo-mo.

I have nested it and I am now powering through the Dust Busting - no crashing. I plan to apply the slo-mo on the nest and anticipate that might cause issues again and push me to export a Dust Busted clip to re-import.

Maybe I spoke too soon.
I made some great progress but I have had 2 crashes since my previous post and I dont see any pattern.
DxDiag is not a zip - it is a forbidden txt

I realise that I have been having success with a clip that I transcoded to dpx. I will try with the original prores.

It is fantastic when it works!!!

Project file:
https://www.dropbox.com/s/fsv3w363faah3 ... d.drp?dl=0

The crashing is much less - I attribute to not doing it on slowed media.
The crashing that I am still getting is possibly from not allowing enough time between patching.

Both Optical Flow and Dust Buster are temporal processes and vey demanding on the GPU.
You could try to render one process into a visually lossless codec and import it.

Thanks Uli.

Which bit of you is in Indonesia?
We are almost neighbors!

Well, Braunschweig in Germany is a sister city to Bandung on Jawa island and we have a lot of university cooperation.
My wife just finished her PhD in Germany and very soon we are getting back to Indonesia.
If you come to Jawa, please tell us.

In Premiere Pro as well, often times an effect won't work as desired on a time adjusted clip. One has to apply the effect to the original, then the time adjustment to a Compound.

Thanks Jim.
I realise haven’t put the media up. It’s really long ProRes 422 HQ (I am pretty sure (at home now)).
If Dwaine really needs it....

Well I am not sure if Dwaine needs footage to test this but Prores 422/HQ doesnt vary much does it?
I think the manual might be better updated to suggest that the Dust Buster doesnt work on time adjusted media or on nested compound clips.

Workflow seems to need to be:

original media > Dust Bust > render out > import > add to timeline

I reckon for the effort:

Fusion clone brush > compound ...?

I am finding that, after having nested the media, the tools impact "disappears" until you go back in to Color and "wake it up"

EDIT_________

Maybe I was a bit hasty: I have got the Dust Buster to stick in the compound and it has been stable for a few plays through....

When the client is here for a run through it can not be relied on to deliver...

My hope is that I am misunderstanding the correct operation of this tool and some nice Forum trawler will set me straight.

Try this:

Original -> Dust Buster -> Compound -> Time Adjustments.

Hi Jim.

That is the workflow I have been following but it seems that unless I go in and "Remind" the compound to do the busting it doesnt work for me.

It seems that if you dust bust before stabilizing then the stabilize offsets all the dust busting.

Damn, dude!

Given all that you're doing to that poor clip, maybe a DNx copy immediately after Busting is a good idea.

I hope Dwaine managed to get the logs that I put up for him. If there is anything else I could supply to aide the analysis - it would be great to use this tool without crashing.

A windows System Information .NFO is generally more helpful than a dxdiag file for analyzing crashing issues. So I'd like to see that.

But I doubt that's really going to help in this scenario.

What would be most helpful is a project export .drp PLUS the media required to demonstrate the crash.

From the logs, it looks likely that it's not crashing to the desktop, but is hanging. Can you confirm?

The project file:
https://www.dropbox.com/s/fsv3w363faah3 ... d.drp?dl=0
The project is extremely convoluted. I will have to narrow it down for you but I think there are compounds labelled dust4something or something4dust

Yes, hanging. I have been patient and waited for it to become responsive - probably 10 mins but in the end terminated manually. It is obvious when it happens - freezes - hourglass cursor and the blemish to be patched doesn’t get patched despite the bounding box. Predictably when too quick to create a new patch after the last or when removing a patch and re-applying. A laboured pause between or doing a ctrl-save between each new one helps.

I will send a system nfo when I get to the studio...

Yeah...no.

That project is not going to be helpful.

Gonna need a simple single timeline project, with as few clips and other things happening as possible, that will reproduce the issue.

And media...

get the clip on a different timeline, dust them and export them.... that will be my workaround.

I did a project with dust (lots of time for cleanup), but they where DPX and no temporals...

As suggested above

Well today I looked harder and closer. I found that 1 of my compounds to quarantine the speed change still had the speed change! (I should just keep my mouth shut?) It was one of the clips I have been working on that has been causing problems. I removed the speed change and the stability has been fine - I dont think that one crashed at all or maybe just once. The node tree in my grades has noise reduct - both Blackmagic and Neat (not simultaneously). Buoyed by the stability that I had on the speed normal clip, I tried another non speed affected clip and it crashed after a few patches. I turned off the nodes with noise reduct and it seems to be stable.

I am holding back sending the media because it's not mine and I will probably have to get triplicate release approvals. It is 10 bit Prores 422 that originated from a Cintel scanner. There are others but all Prores - some 422HQ.

system nfo:
https://www.dropbox.com/s/p6s4ou24jc300 ... o.nfo?dl=0

Thank you for your continuing interest!

yes, I know, round trip it to pull back in. I hate the idea of double handling but it will get to the point that I will have to.

I have only 1 node: Dust Buster and the footage is prores. If I have +1/-1 mode selected and I draw a box left to right and the result is poor (because of my choice), I then remove that box with Alt click and immediately do a box right to left, it is almost sure to crash ....well, hang....forever.

When it is works it works well! That is why I persevere

Roen Davis wrote:I have only 1 node: Dust Buster and the footage is prores. If I have +1/-1 mode selected and I draw a box left to right and the result is poor (because of my choice), I then remove that box with Alt click and immediately do a box right to left, it is almost sure to crash ....well, hang....forever.

When it is works it works well! That is why I persevere

that's not good. I used single frames (DPX), it seems to work better than a stream file (like prores)

I have installed V17.9 and have been revisiting the dustbusting.
It's like a different program! It is smooth as silk, no crashes. Fantastic!

...but the Automatic Dirt Removal seems to be changing the grade I had to a much darker place. After finding that the motion estimation setting was changing the brightness, I have tried setting the system motion to Enhanced best or whatever it is and that seems to have fixed it...?

AMD 3950X
RTX 2080 TI
W10
128 gig RAM