Cannot work with 4K video file. Why?

[jungleexplorer]

So I got a new 4K action camera. Problem is, the files from it completely freezes up VS10. Any idea as to why?

Here are some of the video specs.

VLC Specs

VS10 Specs

[lata]

Hi

Make sure that you are using Smart Proxy and that the proxy file shave been created

The properties you show seem a little unusual with the VS showing the audio using Mono and VLC shows as Stereo
I would have thought stereo being the norm nowadays.
Are you able to provide a sample of your video, use your to camera to record a short sample.

[jungleexplorer]

Hi

Make sure that you are using Smart Proxy and that the proxy file shave been created

The properties you show seem a little unusual with the VS showing the audio using Mono and VLC shows as Stereo
I would have thought stereo being the norm nowadays.
Are you able to provide a sample of your video, use your to camera to record a short sample.

[jungleexplorer]

Hi

Make sure that you are using Smart Proxy and that the proxy file shave been created

The properties you show seem a little unusual with the VS showing the audio using Mono and VLC shows as Stereo
I would have thought stereo being the norm nowadays.
Are you able to provide a sample of your video, use your to camera to record a short sample.

Oops, the video file did not go through because it was too large. I uploaded to my Google Drive. Here is a link: https://drive.google.com/open?id=1ssbOx ... UwSMgNc99B

[pepegota]

I have no problems with 4k, 3840x2160 files in VS from Rylo and Insta360 X.

[Ken Berry]

There's definitely something a little strange about that sample. It inserted OK in VS X10, and I got the question asking if I wanted the Project Properties to match, which I accepted. It also played smoothly in both Clip and Project mode -- though there was no audio to judge whether it was mono as indicated in the VS Properties for the file.

Apart from the mono, the other slightly strange thing about it is that VS says its frame rate is 30.07 fps -- which suggests that it has come from a camera with variable frame rates. So what was it taken on? As you may be aware, VS does not like video with variable frame rates, and we usually advise people to put such video through a converter using the same properties but make the frame rate a normal one e.g. 29.87 or 30 fps.

I then tried to render the sample using Same As Project Settings. It took a few seconds for the rendering to start, then it got to 4% and appeared to stop. I decided to wait for a while to see what might happen. After about 30 seconds it moved to 5%; another 30 seconds and it got to 6%. And then X10 simply closed with the generic msg that the program had encountered a problem and closed.

I started again, and this time chose to render the sample to mp4, with a frame rate set at the standard 30 fps, the bitrate lowered to 15 Mbps and audio at 16 bit stereo. Much the same thing happened: it quickly got to 4%, then took well over a minute to get to 7%, when rendering stopped. This time, though, X10 remained open and I got a msg saying frame 14 was unreadable. I tried to expand the timeline so I could look at every frame. This proved difficult. X10 seemed to freeze for over a minute, but then it expanded to frame by frame view. However, the last frame to show anything was frame 12 with 13 not showing fully, and everything after that being plain black. So indeed there does appear to be something wrong around frame 14.

I also tried it in VS 2018 and had a different, though not totally dissimilar, set of problems. When I tried to insert the clip into the library window, nothing happened for over 40 seconds. Then it appeared. But when I tried to drag and drop it into the timeline, I had to wait another 30 - 40 seconds for this to happen. It took nearly a minute for the message asking to match the Project Properties to appear, though at least it did. And it took similar amounts of time before it would play, though it did finally play in both Clip and Project mode. Attempts to render it, though, had the same results as in X10, though in both cases VS 2018 simply closed without any messages.

I then tried to put it through Handbrake using a frame rate set at constant and 29.97 fps. The process started and took only a few seconds, but no new file was produced. I tried a couple of other variations in the Handbrake settings, with the same result.

[Ken Berry]

I have no problems with 4k, 3840x2160 files in VS from Rylo.

Can you confirm that you used X10 for the test? And did you try rendering it, and also have no problem? As you will see above, I had no trouble inserting and playing it in X10. The trouble only started when I tried rendering.

[jungleexplorer]

I have no problems with 4k, 3840x2160 files in VS from Rylo.

Can you confirm that you used X10 for the test? And did you try rendering it, and also have no problem? As you will see above, I had no trouble inserting and playing it in X10. The trouble only started when I tried rendering.

Yes. I am using VS10. I get the same "Frame 14 missing" Error after about 10 minutes of trying to render. But the real problem occurs when you add the video file to the time line and try to edit it in anyway. On both my Asus laptop with an i7 2.8 Ghz processor and on my new Desktop (see specs on the right), trying to make any edits in the timeline will result in a freeze up for several minutes.

This is a cheap chinese action camera that I am just testing out to see if their claim of 4K is true. I am doing a side by side comparison with a another higher quality 4K action camera. I have no problem working with the other 4K files, which are much higher quality, just the files from this cheap camera.

While I was waiting for a reply here, I downloaded the free Shotcut video editor and tried to load the file in it. Shotcut would not load the file. It said that the file was "Not in an editable format". It offered to convert the file, which I accepted. It converted the file to a MOV format file. The converted file ended up being 10.1 GB in size. The original file that was converted was only 464 MB. But VS10 cannot open the MOV file that was converted by Shotcut, although Shotcut has not problem with it.

I find it funny how a free program can detect what is wrong and offer a solution and VS cannot. This is nothing new. I have had a lot of problems in the past with VS struggling to work with files that other programs can handle. The engineers really need to get their act together.

I am going to email the camera seller and let them know of the problems and see if what they say about these problem and that strange audio settings. Maybe the camera is defective.

[Ken Berry]

jungleexplorer: Does the cheap camera have a name and model number?

Incidentally, the questions in my last post were directed at pepegota and not at you...

[lata]

Hi
Very similar problems as described, program runs very slow, long time to refresh.
Switching to Sound Mixer was particularly slow but did show the mono track although volume level showed as high was static when played with no sound.
Playing seemed ok but stalled VS at end of play, again long time to recover?

I did not bother trying to render this file.

[pepegota]

Same result with VS 10-no problems rendering with mp4's from Rylo and Insta360 One X cameras. Cheap 360 cameras are a waste of time and money, as the good ones produce marginal results when transferred to large screen viewing. If you are into 360, get a Rylo or an Insta360 one X. I prefer Rylo for ease of use, as quality is about equal with both cameras and Rylo's custom service is second to none-best on the web.

[lata]

Hi pepegota
We misunderstood your reply and assumed you had tested jungleexplorer video sample
The topic is discussing problems with the video provided by jungleexplorer, it is that video which is giving problems
I have a Sony that records to MP4, no problems, but that does not help jungleexplorer

[jungleexplorer]

jungleexplorer: Does the cheap camera have a name and model number?

Incidentally, the questions in my last post were directed at pepegota and not at you...

No model number that I can find, it is my by Tec.Bean. Here is a link to the product page. https://amzn.to/2BdFC8p. Either this camera is a piece of junk or it is defective. Either way, I have notified the seller about the problems and am waiting a response, which I will not get until Monday, if at all. Since I am doing a review on the camera, it will be in their best interest to work with me to solve the issues.

[RobertOZ]

How can you possibly expect anything of reasonable quality for $45.99, surly that's what you would call a disposable camera, throw away after use.
Not only is it supposed to be 4K, it is also waterproof as well, who's kidding who

[jungleexplorer]

How can you possibly expect anything of reasonable quality for $45.99, surly that's what you would call a disposable camera, throw away after use.
Not only is it supposed to be 4K, it is also waterproof as well, who's kidding who

The camera was sent to me by the seller to do a video review of. But as far as the $45.99 goes, that is irrelevant. I have actually bought some very good stuff for insanely low prices. Take for example the Plantronics Voyager Bluetooth headset that cost $60 on amazon.

51sc6e37-DL._SL1200_.jpg (12.96 KiB) Viewed 2966 times

For years I used Plantronics headsets because I thought they were the best, but everyone of them had serious problems. One actually melted on my ear and nearly cause me a server burn. Then I bought this one off of Wish.com and it smoked anything I had ever used made by Plantronics. Been using it for almost two years and it is the best bluetooth headset I have ever used hands down.

cheap headset.jpg (28.65 KiB) Viewed 2966 times

Want to take a guess how much it cost?.......... It cost just $6. No, I did not forget to add the 0.

I have several action cameras that are under $50. Some of them are not bad at all. I have one that cost $200 and although it produces superb video, it has tons of other technical problems. I think my most negative product review I ever made was on that camera. Not only because of all the problems with it, but because the manufacturer knows about all the problems and is still selling this defective camera and then turning a deaf ear to the consumer's cries for help.


The Bottom line is this. Don't make false claim and expect me to give you a pass just because the price is low. If it is not true, do claim it. But here is the thing about this $45 camera. I am not complaining about the quality of the video it produces. It is not that great, but what do you expect for $45? The issue is not the quality of the 4K video. The issue is that no editor can work with the video files this camera produces. Either this is an engineering flaw, a software flaw, or the camera I received is defective. I don't know which it is. But I am going to find out.