please add support for Insta360 native .insv file

ynp wrote on 4/9/2019, 10:40 AM

support for the Insta360 series of 360 cameras

premiere already has a plugin that supports the Insta360 .insv file.

since the insta360 studio (the only way to export the .instv file to mp4 so it can be used in vegas) usually exports at 5.7k native resolution it has to changed to 4k in order for vegas to be able to edit it. powerdirector 17 can edit the insta360 studio 5.7k file no problem

so vegas please add support for this growing in popularity camera

Comments

ynp wrote on 4/9/2019, 11:53 AM

and now premiere has support for the gopro reframe plugin so you can reframe 360 videos, brillant!

 

set wrote on 4/9/2019, 4:40 PM

So far I know, the Premiere Pro plug-in was developed by insta360 developers (or GoPro developers for GoPro cameras), and the request for Vegas Pro plug-in need to be sent to them.

 

Actually, the native .insv can be put directly to Vegas Pro timeline, but unfortunately the audio is lost, and there's a problem on stitching back and forth camera if done manually within Vegas Pro environment.

ynp wrote on 4/9/2019, 5:07 PM

yes i have tried the scene rotation but the 2 images do not line up perfectly and there are black nadir spots as vegas does not support 5.7k . that is why you have to export out of studio at 4096x2048 so that vegas can render properly

set wrote on 4/9/2019, 6:05 PM

I'm curious to experiment again with the workflow for 360...

Here's my screenrecord for the short-experiment:

In order to get rid of black bar on top and bottom (in case your output is to make it back to normal video) is to put the 5.7K MP4 in 4096x2048 project, save it, and then make new project, put the previous VEG Project file into the new project as nested project, and put FX Scene rotation and tiny planet as MediaFX.

Not a straightforward workflow but working...

In order to speed up the 4K VEG resolution, do Create Video Proxy on the veg file

(but make sure to delete .sfap0 and .sfvp0 files if you are updating that VEG project and recreate video proxy))

set wrote on 4/9/2019, 6:09 PM

The cons of having nesting project like in previous comment is the lost of resolution (5.7K to 4K limit).

 

*Haven't tried:

I think the other alternate way is to create 2160x1080 workflow project, make a temporary guide reference for 1920x1080 output, and later crop it after intermediate render.

*Still not a direct workflow - but I assumed this can work too

set wrote on 4/9/2019, 7:14 PM

I think the other alternate way is to create 2160x1080 workflow project, make a temporary guide reference for 1920x1080 output, and later crop it after intermediate render.

*Still not a direct workflow - but I assumed this can work too

Confirmed: quickly tried, and worked:

Make 1st project that follows the source's aspect ratio, in this case 2:1 - so it is 2160x1080, and then make guide for 1920x1080 if you want a precision output (or 1080x1080 if you plan to make it square). With this way, you can put Scene Rotation and Tiny planet FX as EventFX, and you can sync the timeline cursor between the FX page and main timeline page. Much easier to work rather than MediaFX.

After done the editing, hide the guide, Save this 1st project as 1st VEG.

Now make new project, put 1st VEG project file to new project, set to output 1920x1080 (or 1080x1080), do pan & crop to crop the side.

Render to your desired output.

AVsupport wrote on 5/26/2020, 11:36 PM

+1 for .insv support.

Surely this request better comes from the software developer if it needs to?

Just testing my new Insta360OneR, 5760x2880

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.