Big MP4 Problem

[pepegota]

I converted a 5.7K 360 video file to a MP4 file. The MP4 file was 5760 x 2880. So, I converted it using Virb editor to 720P, as no present NLE would accept such a file. The file was not accepted by VideoStudio 2018 but, was accepted by Cyberlink PD. VS only can change it to 480P. If you try to save it to AVCHD the program crashes. It does not crash to MPG. Not only is the need to accept 5.7K video directly needed but for now let us get, at least, the MP4 to AVCHD functional.

Why does PD do what VS cannot do? This must change with the 2019 version.

[Ken Berry]

Would it be possible for you to make a small sample of your 5.7K 360 video available on Dropbox or similar website. Pretty obviously more people are going to be facing the sort of problems you are experiencing, and it would thus be useful if we could experiment with a sample to see what difficulties VS has with such footage and to see if there are any work-arounds...

[pepegota]

Ken

You can get all the relevant files here: https://app.sugarsync.com/wf/D1814182_040_877085820
1. First I used this file: Insta360 Studio Editor ONE X (Beta)_Winx64_3.0.3 to edit the raw 360 *.insv file which I provided.
The only thing you can do with this incomplete Beta is to create an MP4 file of the same magnitude 5760X 2880 (no other editing capabilities yet-a work in progress.)
I provided that file too.
2. Next I used ther Virb Editor to change to 720P or 1080P, which ever I may need. Also, provided
I also provided DVD from VS that I made.
3. I Inserted the Virb MP4 into VS to use. I can transcode to mpg but, as soon as you use m2ts the program crashes. AVCHD is a no-no.
Cyberlink PD had no problem with the Virb file. I would like to make VS better and I hope this helps. Also, it would put VS ahead of the pack
if they could go directly from 5.7K to AVCHD. They need to know. I tried re-encoding with Hand Brake and MultiAVCHD but their files also failed in VS.
Now, you have everything and I look forward to your comments.

Joe

[Ken Berry]

Thanks for providing both samples and programs. They're downloading a bit slowly at the moment. But I look forward to playing around with them. Watch this space!

[asik1]

Thanks for providing both samples and programs. They're downloading a bit slowly at the moment. But I look forward to playing around with them. Watch this space!

Here at ~100K/s
Took 35 minutes to D/L, MP4 from Insta360 editor.mp4
Media info don't know what is it nor bitrate viewer.
Non of my players could run it,(LA, VLC, AMTP, zoom, )
Nor my latest XMedia Recode .

So why VS should bother...

[pepegota]

I get a little over half a Meg/second. 100k/s what can I say?

[weaver]

I have a similar problem, and also the solution. I do not know why, recently the videos generated by Google Earth Pro ( Movie Maker) are in MP4, the W7 plays them, but the VS X7 says the format is incompatibel.
I use the Prodrenalin to convert the mp4 file to mp4 ( of course without any correction) and the converted file works fine in VS.

[pepegota]

"So why bother." Power Director can play it. There is a 360 market and if VS cannot cope with it others can.
I would hate to change editors. Other 360 cameras most probably have the same problem. I would like to use HD instead of SD.
Virb files bomb. When Insta360 editor is up to speed, it will bomb too. Also, I downloaded the whole folder in 30 minutes.
The problem is converted files also bomb.
I tried Prodrenalin and no change the program bombed. This really needs fixing!
All my players can play the 5.7k mp4, Pot Player and VLC

[asik1]

my VLC 3.0.0 git dosen't play your file

[pepegota]

Try VLC version 3.0.4. You are way out of date. That version would not play it. Also, try Pot Player-excellent for 360 video.

[asik1]

Try VLC version 3.0.4. You are way out of date. That version would not play it. Also, try Pot Player-excellent for 360 video.

3.0.0 also should play 360, but 4 U I went for 3.0.4 and got

avcodec error: Could not open I:\downloads\MP4 from Insta360 editor.mp4: Unknown error
vobsub debug: this doesn't seem to be a vobsub file
ps warning: this does not look like an MPEG PS stream, continuing anyway
main debug: using demux module "ps"
main debug: looking for a subtitle file in I:\downloads\
main debug: looking for meta reader module matching "any": 2 candidates
lua debug: Trying Lua scripts in I:\downloads\VLCPortable\App\vlc\portable\lua\meta\reader
lua debug: Trying Lua scripts in I:\downloads\VLCPortable\App\vlc\lua\meta\reader
lua debug: Trying Lua playlist script I:\downloads\VLCPortable\App\vlc\lua\meta\reader\filename.luac
main debug: no meta reader modules matched
main debug: `file:///I:/downloads/MP4%20from%20Insta360%20editor.mp4' successfully opened
ps warning: garbage at input from 509, trying to resync...
main debug: EOF reached
main debug: removing module "ps"
main debug: removing module "record"
main debug: removing module "cache_read"
main debug: removing module "filesystem"
main debug: dead input
main debug: changing item without a request (current 0/1)
main debug: nothing to play
qt debug: IM: Deleting the input

[Ken Berry]

VS only can change it to 480P. If you try to save it to AVCHD the program crashes. It does not crash to MPG.

I played around a little with your files last night before going to bed. But I thought I would leave more work till this morning. I am, however, a little confused about the quoted statement above. I assume you mean that you actually got VS to convert the "MP4 from Insta360 Editor" to mpeg-2, but would appreciate your confirmation of how you did this.

That MP4 from Insta360 Editor file caused me a few problems. First, it only appeared in the Library as extended black and white lines (black in the top half, white below). Nothing would play, neither video nor audio, when I tried to play it in the Library, although there was no trouble getting it to show its Properties which all appeared normal apart from the 5760 x 2880 frame size. (I acknowledge of course that that frame size is correct for the type of video involved though it's obviously not something that VS is programmed to be able to see or play.)

Second, the clip was difficult to drag and drop from the Library into the timeline. It took over a minute before the thumbnail in the library became active when I clicked on it, and allowed itself to be dragged and dropped. It then seemed to be just the black and white lines again and VS appeared to be frozen. I used Task Manager to get out of it and repeated things, with the same result. But this time I gave it more time. After nearly two minutes the first three quarters of the clip in the timeline turned all white, with the remainder black. It went into Project mode and I could not get it into Clip mode -- that link remained unresponsive. And the video would not play in Project Mode. There was also no audio apparent.

So I went to Share -- again having to wait nearly two minutes before the Share page appeared. I tried to render it to MP4, AVCHD and SD mpeg-2 (your 480P) but in each case, after about 20 seconds each time, I got an error message saying "Frame 0 is unreadable".

So that is why I am interested to know how you managed to convert MP4 from Insta360 Editor to 480P in VS...

As for playing that clip in VLC (and I have version 3.0.4 too), the opening frame appears (of you, presumably, standing in the yard near your house with your smartphone). But no video plays after that, although the audio did. After a couple of seconds the video breaks up, then resumes (though frozen again) with you having moved off-screen over towards the fence. I didn't get those various errors that asik reports.

But here's the other funny thing. The screen view in VLC I get of MP4 from Insta360 Editor is not the full view and gives no impression of being a 360 clip. This is what I get (see following image). And I should add that this is what I also see in the VS preview window when I play your 480P mpeg-2. A lot of the width has gone and there is only the vaguest hint of bent distortion in the vertical lines of the house.

As you said at the outset, pepegota, Cyberlink Power Director 16 accepts and plays and indeed renders the MP4 from Insta360 Editor clip with no problems. The view there is clearly of a 360 video: see next screenshot.

I took this screenshot inside VS 2018, not only to show what it should look like, but also to make the point that I rendered the MP4 from Insta360 Editor clip in PD16 to mp4, avchd and 480P mpeg-2 with no problems and all very quickly and good final quality (with concessions for the SD nature of the mpeg-2). And all these clips played properly in VS and moreover had the proper 360 appearance unlike your own 480P clip. So again I could only wonder exactly how you got that 480P clip.

[pepegota]

Hi Ken
I got VS to make 480p video by taking the Virb mp4 and rendering it to mpg in VS. If I tried to render AVCHD it would crash.
This is what I did:
1. I used the Insta360 editor to make a 5760x2880, 360 mp4 from the insv video file
2. Since that is all that editor could do, I used Virb editor to convert to 720p mp4 (regular file-no 360.) See note below.
3. I took the Virb file into VS and converted it to a functional mpg. When I tried AVCHD it crashed
4. If you try "same as first clip" it makes a mp4 file that works.
My Pot Player and VLC can play the the mp4 file, created by the Insta360 editor, without issue.
Note: you can convert, using Virb editor, selecting Export/Hyperframe and then select either, 1080p, 720p or 480p
Nevertheless, it is a problem as Power Director has no issue with it.

I hope VS can get on board before the train leaves.
FYI: Pot Player is exceptional for 360 video. You can display in 360 or standard mode by clicking on 360 at the bottom.
P.S. The video is from a web site and that is not me. Dpreview.com, an excellent site for cameras, located in VR/Action camera forum.

[Ken Berry]

I've been playing around with this a little bit further. First off I installed the Insta360 Studio Editor so that I could produce my own version of your MP4 file. However, once installed I could not import nor drag and drop your raw file. I reinstalled the Editor, but it didn't work then either.

So I moved on and installed the Virb Editor to see what it could produce using your 5760 x 2880 MP4 from the Insta360 Editor. I found that the Virb Editor could output in several formats apart from the 720P one you chose. Apart from 5.7K, it can also output in 5K, 4K, something called 1760P as well as the 720P. Since I have a 4K computer and monitor, I chose that. Interestingly enough, instead of the usual 3840 x 2160, it produced a 3840 x 1920 video.

I then inserted this into VS 2018. After more than a minute, it appeared and became active, and I dragged it into the timeline. Another couple of minutes before it became active there, with the frames now showing. I noticed that Garmin had added a couple of seconds attribution of its Editor to the beginning.

I moved on to trying to render it to some format, retaining the 360 aspect. To do so, I right clicked the clip and went to "360 Video", where I chose "Insert as 360". A double screen appears and you go through the process there, then OK out. In the preview screen, I got the following, which I thought I was after. You'll notice that among the icons below the screen that 360 is highlighted in blue.

Anyway, I went to Share, and things sort of fell apart there. I tried Same As First Clip, MP4 and AVCHD -- adjusting the frame size of the latter two to 3840 x 2160. In each case, the rendering appeared to start a went for a couple of seconds, reaching 4% in all cases. Then the rendering box disappeared and nothing was produced. In other words, this appears to confirm our view that something is not working correctly in VS when set for 360 views.

So I went back to the Edit module and removed the Insert as 360 by using the Reset 360 button. I then went back to Share and successfully produced a new MP4 using Same As First Clip. This shows the 360 distortions, but you cannot manipulate the 360 views on screen while the new clip is playing in either Clip or Project mode. Interestingly enough, though, you *can* manipulate those views when you take the new clip back to the Virb Editor.

[pepegota]

So, Quo Vadis? Where do we go from here? I don't think VS is aware of the problem.