4K editing

[pepegota]

4k editing has not arrived yet to VS or PD. They both have problems. However, using a combination of the two, I was finally able to get a clean 4k video.
I rendered a 4k video in VS which went to completion. However, the playback could only display half the video. I was able to go from 4k to 1280x720p without
issue The programs are too mecurial for practical use as of now.

[tletter]

4k editing has not arrived yet to VS or PD ... The programs are too mecurial for practical use as of now.

In my experience both X10 and VS2018 can produce 4K videos and have for years. Perhaps you are doing something unusual.

tletter
https://www.youtube.com/user/tletter

[Ken Berry]

I can only agree with tletter. I have never had any difficulty producing 4K video. Mind you, the longest one I have produced is just under 15 minutes long -- though I rarely produce anything much longer than 20 minutes in any format. My computer and monitor are also 4K capable.

[pepegota]

Gentlemen, I can only say that an i7 8700 computer should do the job. I have no unusual inputs, jpg, mp4 3840x 2160 4k video, and wav files.
I could not render correctly a 20 minute 3840x2160 file. I am doing nothing unusual and I am not a novice to video editing. These 4k video
files were from a Panny FZ 2500-there should be no problem but, there is and very real. Sometimes it would render and other times not. It
is too mecurial for practical use so, I will have to go back to AVCHD.

The facts: 21 minute perfect 4k 3840x2160 video, no problems playing on VLS or Pot Player, was rerendered by VS and PD.
It was rendered without any additions. Results: The VS render could only play half the video and then reverted to the beginning and started to play over again.
The PD render completed without issue. Tell me there is no problem. Try making a 4k video, of the above dimension, and add titles, sound, extra
video clips and see what happens-disaster. The VS however, was able to convert the 3840x2160 video to AVCHD without issue.

[tletter]

I could not render correctly a 20 minute 3840x2160 file ... I will have to go back to AVCHD.

AVCHD is not a particular video resolution, e.g. it can be HD, FHD, UHD, etc.

These 4k video files were from a Panny FZ 2500-there should be no problem

Isn't this the same problem that you complained about at viewtopic.php?f=1&t=65470 and viewtopic.php?f=1&t=64222 ? Perhaps you should address this problem. BTW did you ever open a ticket with Corel per search.php?keywords=ticket&t=65470&sf=msgonly ?

tletter
https://www.youtube.com/user/tletter

[Davidk]

The camera may be part of the problem. I have seen and reported issues from a Panasonic FZ-2500.

[asik1]

here a sample file
http://download.dpreview.com/panasonic_ ... 500-4K.mov
I'm D/L it now, but it's QT so ..

*Sorry, it's not original it's edited.

and this?
http://www.aktiv-verlag.com/~webvideos/ ... FZ2000.MP4

https://www.imaging-resource.com/PRODS/ ... d-test.htm
scroll down for samples

[tletter]

https://www.imaging-resource.com/PRODS/ ... d-test.htm

The Panasonic FZ2500 4K video samples render fine in VS2018 as 4K MP4 output files.

tletter
https://www.youtube.com/user/tletter

[pepegota]

I will try VS 2018 and see what happens. The referral to AVCHD was to indicate m2ts video. Sorry for the duplication. Cell phones cannot compare to a computer.

[pepegota]

Davidk you gave me an idea. I re encoded the Panasonic mp4 videos which resulted in a smaller file size. I used these mp4's in VS 2019 and the result was success. It looks like those Panny files are not what VS expected. VS 2018 also, no problem. The size of the Panny clips are much larger than the re encoded clips. Perhaps, too much for VS to handle.
Having to re encode is not very pleasant but, the only way to make it work for now.
Thanks Mate!

[JWolters]

Hi Pepegota,
Sorry, I do not agree with that. I am not a VS cutter but I know something about it.

4k editing has not arrived yet to VS (...) However, using a combination of the two, I was finally able to get a clean 4k video.
I rendered a 4k video in VS which went to completion. However, the playback could only display half the video. I was able to go from 4k to 1280x720p without
issue The programs are too mecurial for practical use as of now.

Yes it did . I do not know your FZ2500 (2000) preset. I'm using Lumix FZ2000 (2500) as well as the GH5L. My preset for both is roughly 4K/MP4(also MOV)/10(8) bit color depth/picture style CineD or even VLog. With all imports makes VS2019 no problems. Yes since 2019 VS can also do it with LUTs. So I want to say, I do not know your problem and can not retrace it.

I wish you lots of fun and a definitive solution to your problem.

[pepegota]

On my Fz 2500 I shot at 38740x2160, MP4, 100Mbps 30P. The program is not consistent, too many crashes while editing and rendering is a Hail Mary.
After transcoding-no problem so there! I just split a perfect playing video, of 21 minutes length, into 7 or 8 clips. When rendered only 3/4 of the video played, the rest was
black screen-mecurial to be sure. Unreliable is the word. Shooting 4K with VS is a crap shoot. I will have to be content with 1080p.

[pepegota]

I just tried to create a two clip short video with title, music and applied Mercalli. The clips where from a Panny LX 100 camera at (3840x2160.)
VS 2019 could not do the job-crashed, incomplete. I then re encoded to 3840x2160 with my encoder. I used this result in VS 2019 and with success.
However, the resulting video was (3840x1920) not 3840x2160. They need to fix this because transcoding is not a desirable experience when clips are many.

[Davidk]

Working from memory re FZ2500 - the problem may be that the camera is just too capable for VS. I recall issues with a 100fps clip, which in some hardware configurations (really fast cpu and lots of RAM) did not seem to cause the owner any issues, but when that same clip was played on a slower computer, there were green bars at the bottom of the preview window, see topic here (search topic FZ-2500, get more than a few hits)
viewtopic.php?f=1&t=64331&p=361398&hili ... 00#p361398
and they went away with a re-code to more common frame rates. Which is what you are describing.

This is actually the other end of frame rate issues more commonly reported, where the rates are much too low - 12-21fps - from smart phone devices.

[pepegota]

I Just ran a 3840x2160 mp4 in VS 2019 and it only produced about 3/4 of the video. I ran it it PD and it was successful, also faster. Corel has a problem .
The PD encoder is faster and far less buggy. Corel support is useless.