Blackmagic Forum

Hi,

I am about to get an Insta360 One X 360degree camera for our offices.
There is a so called no stitch workflow based on a similar called Adobe Premiere Plug-in around which makes post processing of tge large files much easier.

How are tge chances to see a similar workflow and Plug-in for DaVinci anytime soon?

Are there chances that you will support the large resolution (5.7k) footage from 360 degree cameras any time soon in one of the upcoming releases?

I'd really appreciate it if this can be made to happen, as I would not want to be forced to go over to the "Dark Side" =Adobe)

Thanks for any info on this,

Very best regards,

Fran

Anyone?

Will there any spherical image support anytime soon?

Time for some feedback on this from myself.

At least for 4K here is a workflow:

What one does need to do (and I did previously wrong!) is to set the exact resolution in the project settings BEFORE importing. The resolution of the mp4 exported from the Insta360 desktop app is the one to use.
I did that now sucessfully by setting the project resolution & importing & exporting with custom 4k 3840x1920 resolution. Of course you can also use optimized media in this workflow. You can even save that as custom project profile (also in the deliver tab).

After export reinject metadata as spherical. Result has minute distortion at nadir.

5.7k @ 5760x2880 does not work in DaVinci. Can't even set that as import setting.
DaVinci does not support MagicYUV.

Hopefully both will change with future releases.

On the free version the maximum render resolution is 3840x2160. 5760x2880 works fine in the Studio version.

I wouldn't count on MagicYUV being supported now that there are many other good options.

Thanks Roger,

very interesting. I'm looking into getting either Power Director 17 Ultimate or DaVinci studio.
As I am primarely doing 360 I lean towards PD as its offers an option to add title images in an undistorted way. Still the drawback it seems not to be able to support more than 4k out of the box - the latter is big plus for DV Studio..

Will investigate both further.

Fran

I have the Insta 360 One X, unfortunately Resolve 15.x atm has not a 360° editing workflow.
You can do some tweaking with Fusion but the Resolve embedded version doesn't support Oculus Rift or HTC Vive realtime stereoscopic playback.
Wait for Nab 2019, I bet Blackmagic will release a new beast.

I just crossed the line, here is my summary.

https://forum.cyberlink.com/forum/posts/list/78558.page

It's working in Power Director, and its not hugely expensive either....

Hey guys!
I have a problem with Davinci Resolve 16 Studio and insta 360 one x footage. On the timeline some of the clips appear to be "media offline". But they are not offline, as all of them are In-to-Out portions of the same video file from the Media pool. Some of the clips are offline, but their audio plays well. Other clips are displayed ane played back normally. All of them are the parts of one huge file, which is stored in the Media pool, so Davinci Resolve is clearly aware of where the footage is located

pavelsuchkov wrote:Hey guys!
I have a problem with Davinci Resolve 16 Studio and insta 360 one x footage. On the timeline some of the clips appear to be "media offline". But they are not offline, as all of them are In-to-Out portions of the same video file from the Media pool. Some of the clips are offline, but their audio plays well. Other clips are displayed ane played back normally. All of them are the parts of one huge file, which is stored in the Media pool, so Davinci Resolve is clearly aware of where the footage is located

Hello, I found the same. I dropped the bit rate when exporting from insta360 studio in h.265.

Whereas h.264 defaults to 120Mbps the H.265 allows it to drop to 80Mbps and it handles it really well

Found this thread coincidentally having the same problem with my Insta360 EVO footage.

I was able to fix this by deactivating Intel Quick Sync support for H.264 decoding under 'Preferences...':


Nvidia support still works fine for my Quadro RTX 4000 with 8GB.

I just moved from 16.2.0.055 to 16.2.1.017 and retested: Same behavior