|
|
Quote
Hi,
I think I have the 360 5.7K IN & OUTput working from PD17 and think this warrants a new thread.
Following these two threads:
https://forum.cyberlink.com/forum/posts/list/77316.page
&
https://forum.cyberlink.com/forum/posts/list/63881.page
I created a new profile ini which works for 5.7k output.
Two things turned out to be important when doing that.
1)
If you create a custom profile the words Custom Profile -1 (or
2,3,4.....n) needs to be kept. If this is directly replaced by the
profile name it does not work.
2)
When you edit the new custom output profile under the produce tab,
it still claims to be of 1280x640 resolution when you change to the
video tab.
Under proprties in the Profile Name Tab of Quality Profile Setup
(and in VLC or file properties) the properties say though that its
actually 5780 width by 2880 height=5.7k
5.7k INPUT works also fine. To do this you need:
A fast computer & lots of storage space & this additional software:
http://virtualdub2.com/
&
https://www.magicyuv.com/
WORKFLOW:
Step 01
Install Virtualdub2 and the latest version of MagicYUV
Step 02
Export your video file at full res out of Insta360 Desktop app
Step 03
Open it with Virtualdub2
Step 04
Save as losless AVI with the Video Comprssion set to MagicYUV - YUV 4:2:0
Step 05
Be very patient & have a huge storage disk
Step 06
Import finished file into Power Director 17 Ultra or Ultimate
Maybe a dumb question but,
Why do we need all of this preperations?
When I render the files from INSV into MP4, I just throw them into PD17 and everything works fine...
Where does the benefit of VirtualDub2 and MagicYUY comes into place?
Quote
struggling to get this to work: when converting the insta360 one x input, th evideo no longer shows as a 360 video. Thoughts?
You need to inject 360 metadata
https://support.google.com/jump/answer/7044297?hl=en
|
|
|
Render output with vp9/av1 codec.
It's royalty free and better in almost every way.
Why not use it?
Av1 is from 2015, we are now entering 2019.
4 years is enough waiting.
|
|
|
