-
-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Like "Export Disparity" but without rgb images #246
Comments
See #173 |
So right now I am doing export disparity, and using just the resulting depth PNGs along with the original video in Resolve and it works perfect every time. I never touch the rgb frames except to delete them. Unless the act of creating the rgb frames somehow changes the number or order of the depth PNGs it should work fine, no? |
Since iw3 always uses fixed(constant) FPS filter, the frame position may be shifted/skipped due to start duration, variable frame rate, changing frame rate etc. I am planning to add a checkbox for |
If you think it will definitely not work then that's ok. But if you think there is a chance, I will be happy to test it out! The only necessity is that the depth images come out in the correct order numbered the same way they are now. Edit: And good idea about the advanced settings checkbox |
When synchronization between depth and rgb frames is required: However, there are cases where only depth is required without need to synchronize with rgb frames, e.g. controlnet input. For this super logical reason I can add Export (Depth Only) feature. |
I'd like to give it a try and see what you are talking about if you don't mind |
seconding this, would be very helpful in multi-pass 3D renderings by saving storage space (and possibly processing power depending on how it was implemented) |
Hi nagadomi! Any chance we can get this option for those who use other methods for the final conversion? Not sure if it will give even a slight boost to speed, but the storage savings and less drive usage would be super helpful.
The text was updated successfully, but these errors were encountered: