- Davinci resolve lite max resoltuion mp4#
- Davinci resolve lite max resoltuion install#
- Davinci resolve lite max resoltuion full#
- Davinci resolve lite max resoltuion pro#
I can open it with lightworks as standard videofile, I can open it with davinci resolve as a 360 file (but in both apps - 360 video - useless ).
Davinci resolve lite max resoltuion full#
What I ve tried so far - full export 5,2 K from gopro fusion studio as well as the commandline export of 5,7 K material. Import as mov at maximum possible quality is unable to import into PD - reason unsupported format.
Davinci resolve lite max resoltuion mp4#
Only if export from gopro fusion studio is set to MP4 it works. When you can download the gopro fusion studio, I can uplad for you the original unstitched material from both cams as well if you want.Ĭlip in max size and MOV format does correctly import into PD. It is huge file, and today I´m in foreign on worktrip, but I´ll try after I come back. Where does the benefit of VirtualDub2 and MagicYUY comes into place?Ĭan you upload the clip to a cloud folder and paste the link to it here? I can download the GoPro app and maybe if you shared the original clip from your Fusion and the converted version we can figure out where the problem came from.ĮDIT: Just to confirm: If you don't convert to MagicYUV, does the clip import into PD as 360 when it comes straight from GoPro When I render the files from INSV into MP4, I just throw them into PD17 and everything works fine.
Davinci resolve lite max resoltuion pro#
Any edits you want to make will have to be done in Notepad, but it's OK to check that the settings are correct as shown above.ĭS365 | Win10 Pro | Ryzen 9 3950X | RTX 2070 | 32GB RAM | 10TB SSDs | 5K+4K HDR monitorsĬanon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360° I changed the and lines to the correct values and saved the file, then I reopened PD and confirmed that everything is set correctly:įor your second finding, you shouldn't use the built-in profile editor for this since it's beyond what PD will allow you to work with. I then closed PD and opened profile.ini in Notepad. I didn't leave any "custom profile" words in there. In the other post that you linked to above, I had created a 5.2k profile and shared it, and just now I created a new 5.7k profile from scratch and changed the name to "Insta360" and typed my own comments. Thanks very much for doing all of the setup and outlining your workflow!Īs for the 2 findings you mentioned, I wonder if you'd solve the first one if you tried doing things a bit differently. Here included are 2 custom profiles, 1x with about 50Mbps and 1x with about 150Mbps enjoy & have fun:Ĭustom Profile -1 5760x2880 29_97Fps 50MbpsĬustom Profile -1 5760x2880 29_97Fps 50MbsĬustom Profile -2 5760x2880 29_97Fps 150Mbps Here is the content of my modified profile.ini which works for OUTPUT of 5.7k, if you need higher quality increase the 50Mbps setting to a much higher level (careful bigger files & faster hardware & faster network necessary). Use your custom profile for exporting in 5.7k
Import finished file into Power Director 17 Ultra or UltimateĮdit as you like. Save as losless AVI with the Video Comprssion set to MagicYUV - YUV 4:2:0īe very patient & have a huge storage disk
Davinci resolve lite max resoltuion install#
Install Virtualdub2 and the latest version of MagicYUVĮxport your video file at full res out of Insta360 Desktop app To do this you need:Ī fast computer & lots of storage space & this additional software: (and in VLC or file properties) the properties say though that itsĥ.7k INPUT works also fine. Under proprties in the Profile Name Tab of Quality Profile Setup It still claims to be of 1280圆40 resolution when you change to the When you edit the new custom output profile under the produce tab, If you create a custom profile the words Custom Profile -1 (orĢ,3,4.n) needs to be kept. Two things turned out to be important when doing that. I created a new profile ini which works for 5.7k output. I think I have the 360 5.7K IN & OUTput working from PD17 and think this warrants a new thread.
0 kommentar(er)
