Thank you very much Igor. These are the settings I've been looking for. It is a great help to me. :-) Sam On 08.04.19 21:53, Igor BEGHETTO wrote:

Hi Sam, usually I use this proxy settings (for  source at 1080p):     - Scale Factor: 1/4     - Use Scaler: unchecked     - File Format: FFMPEG - mpeg     - Video Preset:         - Compression: mpeg.mpeg         - Bitrate: 1800000         - Quality: -1         - Pixels: yuv420p

For some videos, with strange variable bit rate, made with a smartphone I had problems, like you, with the settings above; then I changed it to MOV and it works fine :     - File Format: FFMPEG - mov     - Video Preset:         - Compression: mov.mov         - Bitrate: 1800000         - Quality: -1         - Pixels: yuv420p

I don't know if it can help you.

IgorBeg

Il 08/04/2019 18.57, Sam ha scritto:

...

Hi guys,

I recorded a sports event this weekend and created very large files. To be able to edit the video files I have to create proxy files. I use FFmepg m2ts format. Most of the files are created, but for the video files with a frame rate of 120 FPS the proxy creation is aborted with the error message.

check_frame_rate failed /home/sam/YI023601.proxy2-MP4.m2ts failed=1 canceled=0 int ProxyRender::create_needed_proxies(int): Error making proxy.

 Does anyone have a hint for me to also handle video files with 120 FPS and higher.

I have added this information to the manual in the Proxy section for future reference. *BUT...* On 08.04.19 21:53, Igor BEGHETTO wrote:

...

Hi Sam, usually I use this proxy settings (for source at 1080p): - Scale Factor: 1/4 - Use Scaler: unchecked - File Format: FFMPEG - mpeg - Video Preset: - Compression: mpeg.mpeg - Bitrate: 1800000 - Quality: -1 - Pixels: yuv420p

For some videos, with strange variable bit rate, made with a smartphone I had problems, like you, with the settings above; then I changed it to MOV and it works fine : - File Format: FFMPEG - mov - Video Preset: - Compression: mov.mov - Bitrate: 1800000 - Quality: -1 - Pixels: yuv420p

-------------------------------------

...

...

int ProxyRender::create_needed_proxies(int): Error making proxy.

Does anyone have a hint for me to also handle video files with 120 FPS and higher.

We can not reproduce the above error on a sample 120fps mp4 file when using m2ts, but would like to see if it can be fixed. The sample we used is at:

https://streamable.com/ot7nz Does this sample fail for anyone else? Or is there a small sample that fails for sure? Perhaps other settings have been changed that create the error? and I could try those? gg/phyllis

Later we will boot OpenSuse and see if we can get it to fail there. It still works here and I carefully compared what you did and even set the bitrate = 0. Working demo: https://streamable.com/u7hgi On Thu, Apr 11, 2019 at 2:59 PM Sam <[email protected]> wrote:

I have used your file and get the same error message.

Here is the video: https://streamable.com/vkav1

In the console I also get the following error message:

int FFMPEG::open_encoder(const char*, const char*): check_frame_rate failed /home/spc/cin-test/test.proxy2-mp4.m2ts failed=1 canceled=0 int ProxyRender::create_needed_proxies(int): Error making proxy.

Igor, you're absolutely right. The video is rendered down to 61 FPS. Well observed! The project format is set to 25 FPS. Sam On 12.04.19 11:03, Igor BEGHETTO wrote:

GG/Phyllis, thanks for the ub16 built. 1) I downloaded the ot7nz.mp4 file from "streamable.com" and I checked this file with ffprobe command. FFprobe says to me: 61fps 3601kbps 1280x720. So, I think, streamable changes your video compression format even if I saw Sam's video with others parameters for the same video. Booh! 2) However I loaded ot7nz.mp4 video in Cinelerra-gg and I have got the same issue like Sam, also with .mov and .mpeg. If I change the bitrate of the file in Media (and in Settings-Format) from 61 to 60 then it works.

Could you give me the original video file 120fps.mp4 uploading it to datafilehost or other, please? @Sam: your video source was to 120 fps but what is the Project's format? Thanks.

IgorBeg

Il 12/04/2019 0.35, Phyllis Smith ha scritto:

...

Later we will boot OpenSuse and see if we can get it to fail there.  It still works here and I carefully compared what you did and even set the bitrate = 0.  Working demo:

https://streamable.com/u7hgi

On Thu, Apr 11, 2019 at 2:59 PM Sam <[email protected] <mailto:[email protected]>> wrote:

    I have used your file and get the same error message.

    Here is the video: https://streamable.com/vkav1

    In the console I also get the following error message:     int FFMPEG::open_encoder(const char*, const char*):     check_frame_rate failed /home/spc/cin-test/test.proxy2-mp4.m2ts     failed=1 canceled=0     int ProxyRender::create_needed_proxies(int):     Error making proxy.

I have different frame rates. The event I recorded was mostly recorded at 25 & 50 FPS. The recordings with 25 & 50 FPS are converted into proxy files without any problems. Only the sports close-ups were recorded with 120 FPS. These cause the error. I will send you a file via your private e-mail address, then you can test it. Let's see if you get other results. Sam On 12.04.19 15:40, Phyllis Smith wrote:

On Fri, Apr 12, 2019 at 3:25 AM Sam <[email protected] <mailto:[email protected]>> wrote:

Igor, you're absolutely right. The video is rendered down to 61 FPS. Well observed! The project format is set to 25 FPS.

Sam / Igor:

Well I am very surprised!  Streamable took my 120fps and made it 61fps !!!  So I was continuously testing the original file that I had uploaded and you were testing the file that was downloaded and made into 61.

So now I downloaded the multilated 120fps.mp4 which was 61fps and it failed.

Thanks to both of you as this was driving GG crazy all day long. He says it is up to the codec as to whether or not it accepts a certain frame rate for encoding.  And we just discovered yesterday, no matter what you Set Format fps to, the proxy uses the original media fps always.

Sam, please check your large original camera files to see what its original fps is -- it must not really be 120fps or it should have worked?

Do either of you have a suggestion for a workaround in Proxy to be able to use a different fps?  Something like "Override frame rate ? "  gg/Phyllis

You're right, it's actually 119.88 FPS. My camera shows me 120 FPS, apparently it rounds up automatically. Sam On 12.04.19 16:26, Phyllis Smith wrote:

Sam, thank you !! It is 119.88 fps which is not 120.  I can not believe this but I am glad to get to the bottom of this. Eagle Eyes Igor with the 61 fps discovery.  I was trying all kinds of things yesterday and getting absolutely no where. gg/phyllis

On Fri, Apr 12, 2019 at 8:16 AM Sam <[email protected] <mailto:[email protected]>> wrote:

I have different frame rates. The event I recorded was mostly recorded at 25 & 50 FPS. The recordings with 25 & 50 FPS are converted into proxy files without any problems. Only the sports close-ups were recorded with 120 FPS. These cause the error. I will send you a file via your private e-mail address, then you can test it. Let's see if you get other results.

On 12.04.19 19:08, Igor BEGHETTO wrote:

GG/Phyllis quotes: Do either of you have a suggestion for a workaround in Proxy to be able to use a different fps? Something else "Override frame rate?"

For me is better don't touch it. It help to undestand if rendering will have any problem.

Same here.

Usually, the professional mode is ... 1) to convert the source video with a external program, like Eyeframe (unfortunately only for Windows program) or ffmpeg, to a friendy fps (and change GOP, GroupOfPictures). 2) "to convert" the fps inside Cinelerra-gg, like I have done with your 61 fps video: in Resources->Media, select the video, RMB on that video, choose "Info" option and change video's framerate.

In a old post/thread/issue (I don't remember) I had written that would be useful to have in Media, near the name of the video/audio some fields with the informations: fps, size, (codec?). It would be useful because you could see the info without open another window (Info window) for every file. I understand that it is not easy to implement that feature.

I agree with you Igor. If I had seen that it wasn't 120 FPS but 119.88 FPS, then I would have come to the cause of the problem myself.

GG/Phyllis: "Eagle Eyes Igor" My sister call me Ygor. Take a look at https://www.youtube.com/watch?v=nxxSIX3fmmo Great movie (...and No Comment, please). =)

Hahaha :-) I had to laugh very much about the video. Nice :)

IgorBeg

On 12.04.19 21:47, Phyllis Smith wrote:

For me is better don't touch it. It help to undestand if rendering will have any problem.

Y-GOR or E-GOR or I-GOR: OK, will not touch it.  I will change the manual to say what to look at for check_frame_rate error.

2) "to convert" the fps inside Cinelerra-gg, like I have done with your 61 fps video: in Resources->Media, select the video, RMB on that video, choose "Info" option and change video's framerate.

I did not know you can do this -- I kept changing via Set Format menu. BTW:  I could not get either the 61fps or the 119.88fps files to proxy even with MOV.  Is that correct?

Right, with 61 FPS and 119.88 FPS it doesn't work either. I just found out how it works. As soon as I right-click on a video file in the Media tab and then go to Info in the context menu and change the FPS from 119.88 to 120 FPS, the m2ts and mpeg proxy creation works. By the way, the m2ts format creates extremely small files with high image quality. I could reduce a 1 GB file to 50 MB with scale 1/2. This format is optimal for Proxy. I only have the problem that I have to manually change the many 119.88 FPS files to 120 FPS. It will take me some time. Now that I think about it, an overwrite function would be very useful. Maybe it would be a solution for the future to select multiple files in the media tab, and change the FPS for them, otherwise you always have to adjust every single file of many.

In a old post/thread/issue (I don't remember) I had written that would be useful to have in Media, near the name of the video/audio some fields with the informations: fps, size, (codec?). It would be useful because you could see the info without open another window (Info window) for every file. I understand that it is not easy to implement that feature.

I do not think this would be difficult to do in the code BUT to add this to the comment field, you have to actually open the file to obtain that information.  Which means that when you load a lot of files, it is going to slow down.

By the way, in Resolve and PP the FPS for each file is always displayed. I would appreciate it if Cin could also display it, even if this reduces the loading time.

GG/Phyllis: "Eagle Eyes Igor" My sister call me Ygor. Take a look at https://www.youtube.com/watch?v=nxxSIX3fmmo Great movie (...and No Comment, please). =)

Had to laugh at this video.  Gene Wilder was in some funny movies -- I liked Blazing Saddles best!

Me: "2) to convert the fps inside Cinelerra-gg, like I have done with your 61 fps video: in Resources->Media, select the video, RMB on that video, choose "Info" option and change video's framerate." (I think, you always know) Keep in mind that if you change the fps there, only video fps is changed, not audio. Then you lose the A/V sync. Phyllis: "In the Resources window comment field the addition of fps and codec have been added. This has been checked into GIT and is in the latest ubuntu16 build in the usual place." Thanks for all. Could you also add the size WxH information, please? For example [email protected]. And add the info for the Audio, if possible. Now it is empty. I guess you can't create a new field for every single info. Sorry for all these requests. IgorBeg