Maarten Baert's website

Game Maker / C++ projects
Home Model Creator ExtremePhysics Game Maker DLLs SimpleScreenRecorder AlterPCB Quadcopters   Recent comments Search
Navigation

• Main page

Log in

No account yet? Register!

Valid HTML 4.01 Transitional

Valid CSS!

Recent comments

Showing last 30 comments, most recent first.

In SimpleScreenRecorder / Recording for YouTube:

Maarten Baert

Administrator

Comment #1: Mon, 30 Mar 2020, 0:25 (GMT+1, DST)

Quote

Quote: Fred

Geachte Maarten,
Where can I offer you a drink?
Your job's good and I totally want to donate!
Is it possible via Paypal?
Thanks!
Frédéric

I'm glad you appreciate my work. I don't take donations though, but thanks for the offer :).

In SimpleScreenRecorder / Recording for YouTube:

Fred

Comment #2: Sat, 28 Mar 2020, 16:30 (GMT+1, DST)

Quote

Geachte Maarten,
Where can I offer you a drink?
Your job's good and I totally want to donate!
Is it possible via Paypal?
Thanks!
Frédéric

In SimpleScreenRecorder / Recording for YouTube:

Maarten Baert

Administrator

Comment #3: Fri, 27 Mar 2020, 15:35 (GMT+1, DST)

Quote

Quote: Oh-kay-pee
Quote: Maarten Baert
Quote: Oh-kay-pee

I've been recording some educational videos for my students during this period of school closures. I like how simple SSR is to use. I want to improve my quality.

I record in SSR, upload to Youtube, and share the links. Sometimes I edit the videos in kdenlive, it just depends on if I have to do anything post-production.

The latest comments are years old so I wanted to ask a few questions to see if things are still the same.

I read that we should use either 720p 1280 X 720 or 1080p 1920 X 1080.

Does that mean our window size or our monitor resolution?

My monitor resolution is 1920 x 1080 so if I put it in full screen, will that get me the best quality?

Does a blurry screen result from putting my window size for Firefox to 1280 x 720 but my resolution is 1080p? I don't understand.

Also, some of the settings I have questions about.

I choose the Youtube setting from the Profile area, but what does that do? Does this somehow optimize the recording for YT?

What should I choose as the container? I've done it with MKV and MP4. When I've used MKV, I put it into kdenlive to edit, then exported it MP4. When I do MP4, I get an MP4 and I can upload directly into YT.

What's the difference in using these containers?

I used to get the error message about Flipping, and I have NVIDIA, but whether I turn it on or off in OpenGL settings, I am not getting the message anymore.

Does that mean this issue was fixed? I have a new custom built desktop and want to take advantage of hardware acceleration so I want the setting to be right for when I'm editing video elsewhere.

Assuming your monitor resolution is 1920x1080, and you are presenting in full screen, you will get the best quality if you let SSR record the entire screen with the resolution set to 1920x1080. But note that as a result of the higher-than-normal internet usage due to the Corona pandemic, Youtube has temporarily reduced the default video quality in order to reduce the overall network load. So you may not be seeing the full quality of your video unless you manually set the video player to 1080p when you view the video.

The Youtube setting will pick settings that are reasonable for uploading to Youtube with decent quality. Youtube will re-encode videos anyway so you won't see much improvement if you try to further increase the quality in SSR.

I do not recommend using MP4 in SSR because if your recording is interrupted for any reason, the MP4 file will become corrupted and you will have to restart from the beginning. WIth MKV you don't have this problem, you can always open the file and read it up to the point where it crashed. But you can export to MP4 from kdenlive if you want, since there's no risk of losing data in that case.

Regarding the NVidia message, if you are not seeing any glitches or flashes in your recordings then it's probably not an issue. In any case, if the dialog doesn't appear it's probably because you selected 'yes, always' or 'no, never'. To change it, open ~/.ssr/settings.conf and find the following line:

nvidia_disable_flipping=yes

Set it to 'ask' instead of 'yes' or 'no' and you will get the dialog again.

Thanks for the reply. I fixed the NVIDIA issue.

If I understand correctly, I should record in full screen, my monitor is 1080p. Should I scale it or not?

I guess for videos that I don't need to do any editing on, I was hoping to use MP4 so I don't have to import it into kdenlive just to export it as an MP4, but I understand why now.

Do I use the Youtube container or no? Are you saying it will or won't be useful for Youtube uploads?

You don't need to scale it.
Youtube will accept MKV as well, there is no need to convert it to MP4.
I would recommend using the Youtube preset if you want to upload to youtube. If you want to improve the quality you could lower the 'constant rate factor' from 23 to 20, but it won't make a huge difference since youtube re-encodes the video anyway.

In SimpleScreenRecorder / Recording for YouTube:

Oh-kay-pee

Comment #4: Fri, 27 Mar 2020, 1:41 (GMT+1, DST)

Quote

Quote: Maarten Baert
Quote: Oh-kay-pee

I've been recording some educational videos for my students during this period of school closures. I like how simple SSR is to use. I want to improve my quality.

I record in SSR, upload to Youtube, and share the links. Sometimes I edit the videos in kdenlive, it just depends on if I have to do anything post-production.

The latest comments are years old so I wanted to ask a few questions to see if things are still the same.

I read that we should use either 720p 1280 X 720 or 1080p 1920 X 1080.

Does that mean our window size or our monitor resolution?

My monitor resolution is 1920 x 1080 so if I put it in full screen, will that get me the best quality?

Does a blurry screen result from putting my window size for Firefox to 1280 x 720 but my resolution is 1080p? I don't understand.

Also, some of the settings I have questions about.

I choose the Youtube setting from the Profile area, but what does that do? Does this somehow optimize the recording for YT?

What should I choose as the container? I've done it with MKV and MP4. When I've used MKV, I put it into kdenlive to edit, then exported it MP4. When I do MP4, I get an MP4 and I can upload directly into YT.

What's the difference in using these containers?

I used to get the error message about Flipping, and I have NVIDIA, but whether I turn it on or off in OpenGL settings, I am not getting the message anymore.

Does that mean this issue was fixed? I have a new custom built desktop and want to take advantage of hardware acceleration so I want the setting to be right for when I'm editing video elsewhere.

Assuming your monitor resolution is 1920x1080, and you are presenting in full screen, you will get the best quality if you let SSR record the entire screen with the resolution set to 1920x1080. But note that as a result of the higher-than-normal internet usage due to the Corona pandemic, Youtube has temporarily reduced the default video quality in order to reduce the overall network load. So you may not be seeing the full quality of your video unless you manually set the video player to 1080p when you view the video.

The Youtube setting will pick settings that are reasonable for uploading to Youtube with decent quality. Youtube will re-encode videos anyway so you won't see much improvement if you try to further increase the quality in SSR.

I do not recommend using MP4 in SSR because if your recording is interrupted for any reason, the MP4 file will become corrupted and you will have to restart from the beginning. WIth MKV you don't have this problem, you can always open the file and read it up to the point where it crashed. But you can export to MP4 from kdenlive if you want, since there's no risk of losing data in that case.

Regarding the NVidia message, if you are not seeing any glitches or flashes in your recordings then it's probably not an issue. In any case, if the dialog doesn't appear it's probably because you selected 'yes, always' or 'no, never'. To change it, open ~/.ssr/settings.conf and find the following line:

nvidia_disable_flipping=yes

Set it to 'ask' instead of 'yes' or 'no' and you will get the dialog again.

Thanks for the reply. I fixed the NVIDIA issue.

If I understand correctly, I should record in full screen, my monitor is 1080p. Should I scale it or not?

I guess for videos that I don't need to do any editing on, I was hoping to use MP4 so I don't have to import it into kdenlive just to export it as an MP4, but I understand why now.

Do I use the Youtube container or no? Are you saying it will or won't be useful for Youtube uploads?

In SimpleScreenRecorder / Recording for YouTube:

Maarten Baert

Administrator

Comment #5: Thu, 26 Mar 2020, 22:47 (GMT+1, DST)

Quote

Quote: Oh-kay-pee

I've been recording some educational videos for my students during this period of school closures. I like how simple SSR is to use. I want to improve my quality.

I record in SSR, upload to Youtube, and share the links. Sometimes I edit the videos in kdenlive, it just depends on if I have to do anything post-production.

The latest comments are years old so I wanted to ask a few questions to see if things are still the same.

I read that we should use either 720p 1280 X 720 or 1080p 1920 X 1080.

Does that mean our window size or our monitor resolution?

My monitor resolution is 1920 x 1080 so if I put it in full screen, will that get me the best quality?

Does a blurry screen result from putting my window size for Firefox to 1280 x 720 but my resolution is 1080p? I don't understand.

Also, some of the settings I have questions about.

I choose the Youtube setting from the Profile area, but what does that do? Does this somehow optimize the recording for YT?

What should I choose as the container? I've done it with MKV and MP4. When I've used MKV, I put it into kdenlive to edit, then exported it MP4. When I do MP4, I get an MP4 and I can upload directly into YT.

What's the difference in using these containers?

I used to get the error message about Flipping, and I have NVIDIA, but whether I turn it on or off in OpenGL settings, I am not getting the message anymore.

Does that mean this issue was fixed? I have a new custom built desktop and want to take advantage of hardware acceleration so I want the setting to be right for when I'm editing video elsewhere.

Assuming your monitor resolution is 1920x1080, and you are presenting in full screen, you will get the best quality if you let SSR record the entire screen with the resolution set to 1920x1080. But note that as a result of the higher-than-normal internet usage due to the Corona pandemic, Youtube has temporarily reduced the default video quality in order to reduce the overall network load. So you may not be seeing the full quality of your video unless you manually set the video player to 1080p when you view the video.

The Youtube setting will pick settings that are reasonable for uploading to Youtube with decent quality. Youtube will re-encode videos anyway so you won't see much improvement if you try to further increase the quality in SSR.

I do not recommend using MP4 in SSR because if your recording is interrupted for any reason, the MP4 file will become corrupted and you will have to restart from the beginning. WIth MKV you don't have this problem, you can always open the file and read it up to the point where it crashed. But you can export to MP4 from kdenlive if you want, since there's no risk of losing data in that case.

Regarding the NVidia message, if you are not seeing any glitches or flashes in your recordings then it's probably not an issue. In any case, if the dialog doesn't appear it's probably because you selected 'yes, always' or 'no, never'. To change it, open ~/.ssr/settings.conf and find the following line:

nvidia_disable_flipping=yes

Set it to 'ask' instead of 'yes' or 'no' and you will get the dialog again.

Last modified: Thu, 26 Mar 2020, 22:51 (GMT+1, DST)

In SimpleScreenRecorder / Recording for YouTube:

Oh-kay-pee

Comment #6: Thu, 26 Mar 2020, 0:42 (GMT+1, DST)

Quote

I've been recording some educational videos for my students during this period of school closures. I like how simple SSR is to use. I want to improve my quality.

I record in SSR, upload to Youtube, and share the links. Sometimes I edit the videos in kdenlive, it just depends on if I have to do anything post-production.

The latest comments are years old so I wanted to ask a few questions to see if things are still the same.

I read that we should use either 720p 1280 X 720 or 1080p 1920 X 1080.

Does that mean our window size or our monitor resolution?

My monitor resolution is 1920 x 1080 so if I put it in full screen, will that get me the best quality?

Does a blurry screen result from putting my window size for Firefox to 1280 x 720 but my resolution is 1080p? I don't understand.

Also, some of the settings I have questions about.

I choose the Youtube setting from the Profile area, but what does that do? Does this somehow optimize the recording for YT?

What should I choose as the container? I've done it with MKV and MP4. When I've used MKV, I put it into kdenlive to edit, then exported it MP4. When I do MP4, I get an MP4 and I can upload directly into YT.

What's the difference in using these containers?

I used to get the error message about Flipping, and I have NVIDIA, but whether I turn it on or off in OpenGL settings, I am not getting the message anymore.

Does that mean this issue was fixed? I have a new custom built desktop and want to take advantage of hardware acceleration so I want the setting to be right for when I'm editing video elsewhere.

In SimpleScreenRecorder / Troubleshooting:

Maarten Baert

Administrator

Comment #7: Mon, 23 Mar 2020, 12:52 (GMT+1, DST)

Quote

Quote: Goldiev

Generally it works well, but the result is a zoomed-in (scaled up?) view of the upper left-hand portion of the recorded rectangle/window/screen (depending on setting). In other words the lower and right -hand side parts are cut off. It may have something to do with screen resolution. My laptop is set for 3200:1800, but the only choice I'm given for Record the entire screen is 1600:900. I suppose I might work around this problem by setting the display to that resolution, but I'd rather not.

This was already fixed in the SSR git repository but the fix hasn't been released yet. If you can't compile from source, try running SSR with:

QT_SCREEN_SCALE_FACTORS="" simplescreenrecorder

More info here.

In Model Creator / The model menu:

Maarten Baert

Administrator

Comment #8: Mon, 23 Mar 2020, 12:49 (GMT+1, DST)

Quote

Quote: Dave21

hello, I'm not able to open models or save in this program, errors always appear like: "Failed to create the file" or "Failed to open the file. Make sure you have read access to the folder". What I do?

Try going into the properties of the Model Creator executable and run it in Windows 7 compatibility mode.

Quote: Luc

Hi Maarten,

Just want to thank you! I'm a Flemish person, living in Brazil. I have a language school here. Here the Covid 19 crisis is starting and schools are closed. We give classes online now. I've downloaded simplescreenrecorder to record my classes, so I can share them with students who weren't able to follow the class. Works perfectlyi! Thanks again!

You're welcome :).

In SimpleScreenRecorder / Troubleshooting:

Goldiev

Comment #9: Mon, 23 Mar 2020, 1:50 (GMT+1, DST)

Quote

Generally it works well, but the result is a zoomed-in (scaled up?) view of the upper left-hand portion of the recorded rectangle/window/screen (depending on setting). In other words the lower and right -hand side parts are cut off. It may have something to do with screen resolution. My laptop is set for 3200:1800, but the only choice I'm given for Record the entire screen is 1600:900. I suppose I might work around this problem by setting the display to that resolution, but I'd rather not.

In Model Creator / The model menu:

Luc

Comment #10: Sun, 22 Mar 2020, 16:49 (GMT+1, DST)

Quote

Hi Maarten,

Just want to thank you! I'm a Flemish person, living in Brazil. I have a language school here. Here the Covid 19 crisis is starting and schools are closed. We give classes online now. I've downloaded simplescreenrecorder to record my classes, so I can share them with students who weren't able to follow the class. Works perfectlyi! Thanks again!

In Model Creator / The model menu:

Dave21

Comment #11: Sun, 22 Mar 2020, 0:25 (GMT+1, DST)

Quote

hello, I'm not able to open models or save in this program, errors always appear like: "Failed to create the file" or "Failed to open the file. Make sure you have read access to the folder". What I do?

In SimpleScreenRecorder / Recording Steam games:

Maarten Baert

Administrator

Comment #12: Thu, 27 Feb 2020, 11:56 (GMT+1, DST)

Quote

Quote: Linuxoed

Well, if I understood correctly, I won’t get a VAC ban if I follow this instruction. I want to record CS: GO.
P.S. Sorry for my broken English, this is not a oh native language.

I cannot guarantee this, but it is unlikely that you will have any issues. Back in 2017 there was one SSR user that got VAC banned, but he was unbanned again fairly quickly once he contacted Valve:
https://github.com/ValveSoftware/csgo-osx-linux/issues/1454

In SimpleScreenRecorder / Recording Steam games:

Linuxoed

Comment #13: Mon, 24 Feb 2020, 11:07 (GMT+1, DST)

Quote

Well, if I understood correctly, I won’t get a VAC ban if I follow this instruction. I want to record CS: GO.
P.S. Sorry for my broken English, this is not a oh native language.

In Quadcopters / Pagoda antenna:

Maarten Baert

Administrator

Comment #14: Sun, 19 Jan 2020, 1:34 (GMT+1, DST)

Quote

Quote: Quadcorei8085

Running the script on Windows python 3.8 64bit results in error:

Quote

D:\_tmp_\pagoda2-design-files\scripts>python pcb_pagoda_2.py
Traceback (most recent call last):
File "pcb_pagoda_2.py", line 23, in <module>
close("all")
NameError: name 'close' is not defined

If "close" is removed.

Quote

D:\_tmp_\pagoda2-design-files\scripts>python pcb_pagoda_2.py
Traceback (most recent call last):
File "pcb_pagoda_2.py", line 84, in <module>
oshw_x = array([
NameError: name 'array' is not defined

It seems that functions of modules are not properly prefixed.
(import numpy as np then np.array is used or matplot.array).

Those prefixes should not be necessary since I'm importing pylab into the main namespace. Which version of matplotlib are you using?

Last modified: Sun, 19 Jan 2020, 1:35 (GMT+1, DST)

In Quadcopters / Pagoda antenna:

Quadcorei8085

Comment #15: Tue, 14 Jan 2020, 11:13 (GMT+1, DST)

Quote

Running the script on Windows python 3.8 64bit results in error:

Quote

D:\_tmp_\pagoda2-design-files\scripts>python pcb_pagoda_2.py
Traceback (most recent call last):
File "pcb_pagoda_2.py", line 23, in <module>
close("all")
NameError: name 'close' is not defined

If "close" is removed.

Quote

D:\_tmp_\pagoda2-design-files\scripts>python pcb_pagoda_2.py
Traceback (most recent call last):
File "pcb_pagoda_2.py", line 84, in <module>
oshw_x = array([
NameError: name 'array' is not defined

It seems that functions of modules are not properly prefixed.
(import numpy as np then np.array is used or matplot.array).

Last modified: Tue, 14 Jan 2020, 11:15 (GMT+1, DST)

In SimpleScreenRecorder / Troubleshooting:

Maarten Baert

Administrator

Comment #16: Sun, 29 Dec 2019, 14:40 (GMT+1, DST)

Quote

Quote: Vanarie

Hello. I really like the screen recorder and was happy that I found it. I do have one problem with the audio. I'm hearing a very high pitch tone in the background on playback. I don't believe it's related to my mic because I've recorded with other recorder apps and the audio track doesn't have this tone. It's not really loud, but you can hear it and sounds similar to tinnitus (ringing in ears).

I've tested WebM and MP4, and they both have this high pitch tone. I'm recording from a headset mic. It's not a deal-breaker, but it's a shame I can hear it because the test of the app is great.

Do you have any advice on how to fix?

System is Intel PC/Arch linux desktop, mic going through onboard sound card via PulseAudio backend.

I'm not sure what could be causing this. Do you have the same problem if you use the ALSA backend and configure it to record from the sound card directly (i.e. hw:0,0)?

Can you send me a recording with SSR that shows the issue, and also an audio recording from the same mic with different software (e.g. Audacity) that doesn't show the issue?

Last modified: Sun, 29 Dec 2019, 14:40 (GMT+1, DST)

In SimpleScreenRecorder / Troubleshooting:

Vanarie

Comment #17: Sat, 28 Dec 2019, 20:38 (GMT+1, DST)

Quote

Hello. I really like the screen recorder and was happy that I found it. I do have one problem with the audio. I'm hearing a very high pitch tone in the background on playback. I don't believe it's related to my mic because I've recorded with other recorder apps and the audio track doesn't have this tone. It's not really loud, but you can hear it and sounds similar to tinnitus (ringing in ears).

I've tested WebM and MP4, and they both have this high pitch tone. I'm recording from a headset mic. It's not a deal-breaker, but it's a shame I can hear it because the test of the app is great.

Do you have any advice on how to fix?

System is Intel PC/Arch linux desktop, mic going through onboard sound card via PulseAudio backend.

In SimpleScreenRecorder / Troubleshooting:

Maarten Baert

Administrator

Comment #18: Tue, 26 Nov 2019, 23:48 (GMT+1, DST)

Quote

Quote: Veid

Hi there. At first - I very like this application, thank you author very much for it.
My question is - what codec should I use for gif container? I've tried about a half of them and I had "Can't write header" error for each.

This isn't supported, see:
https://github.com/MaartenBaert/ssr/issues/196

In SimpleScreenRecorder / Troubleshooting:

Veid

Comment #19: Mon, 25 Nov 2019, 11:45 (GMT+1, DST)

Quote

Hi there. At first - I very like this application, thank you author very much for it.
My question is - what codec should I use for gif container? I've tried about a half of them and I had "Can't write header" error for each.

In SimpleScreenRecorder / Custom codec options:

Mika

Comment #20: Fri, 15 Nov 2019, 8:33 (GMT+1, DST)

Quote

no, unfortunately, there is not. but you are free to test for yourselves and prove me wrong.

Last modified: Fri, 15 Nov 2019, 8:33 (GMT+1, DST)

In Quadcopters / Aomway Whip:

Maarten Baert

Administrator

Comment #21: Wed, 11 Sep 2019, 11:25 (GMT+1, DST)

Quote

Quote: Michiganbroadband

I imagine any lossy materials used in the connector or coax that change the Q may cause these to be a little broader.

And 5.8GHz do you actually see the impedance bump from the connectors?

Have you ever popped a few adapters inline to see how it changes?

Yes the connectors definitely do have an effect, especially the cheaper ones. Typically the reflected signal changes by a few percent when adding an adapter.

In Quadcopters / Aomway Patch ANT007B:

Maarten Baert

Administrator

Comment #22: Wed, 11 Sep 2019, 11:20 (GMT+1, DST)

Quote

Quote: Michiganbroadband

I'm curious about the total dropout below -30 on the one antenna.
Is that real?
And why would the other antenna not have a similar dropout?

It is real but it's coincidental. Due to constructive and destructive interference it is possible that at some point, all reflections cancel each other out, and the total reflected signal will be almost zero. But since this is at -30dB we're talking about a difference of 0.1%, which is not significant. Basically it's noise, it will be different for every unit due to manufacturing tolerances.

In SimpleScreenRecorder / Custom codec options:

Maarten Baert

Administrator

Comment #23: Wed, 11 Sep 2019, 10:52 (GMT+1, DST)

Quote

Quote: Mika

thanks for clarifying.

actually, crf value was a typo, was 0 already.

zooming in and comparing the 2 pngs (lossless crf:0 vs lossy crf:20), the latter is definitely the winner - though it makes no sense to me?

regarding the keyinterval, what would be the drawback of leaving this at a default value of 1? this way, accurate cuts of at least 1sec intervals would be possible, after all.

Are you sure there are no other differences between the files? crf=0 should definitely look better.

keyint is expressed in frames, not seconds. keyint=1 means every frame is a keyframe. If you want a keyframe every second at, say, 30 fps, you would use keyint=30. Note that the actual keyframes may not be exactly 30 frames apart though, since the encoder tries to align keyframes with scene changes whenever possible. So you can't really rely on this. The default keyframe interval is something like 250 frames I believe, which isn't very good for editing.

In Quadcopters / Aomway Whip:

Michiganbroadband

Comment #24: Fri, 30 Aug 2019, 18:54 (GMT+1, DST)

Quote

I imagine any lossy materials used in the connector or coax that change the Q may cause these to be a little broader.

And 5.8GHz do you actually see the impedance bump from the connectors?

Have you ever popped a few adapters inline to see how it changes?

In Quadcopters / Aomway Whip:

Michiganbroadband

Comment #25: Fri, 30 Aug 2019, 18:40 (GMT+1, DST)

Quote

Wish I had some nice test equipment for this stuff.
I have an old thing that only goes up to 1GHz.

Have you ever pulled off the plastic radomes just to see if it changes much?
I will sometimes pop a radome itself in the microwave for a few seconds.
If it gets warm or hot it's not good material for 2.4Ghz+

In Quadcopters / Aomway Patch ANT007B:

Michiganbroadband

Comment #26: Fri, 30 Aug 2019, 18:33 (GMT+1, DST)

Quote

I'm curious about the total dropout below -30 on the one antenna.
Is that real?
And why would the other antenna not have a similar dropout?

In Quadcopters / Aomway Patch ANT005:

Michiganbroadband

Comment #27: Fri, 30 Aug 2019, 18:27 (GMT+1, DST)

Quote

And all of this said and tested.
At the end of the day it works very poorly.
In all of my tests comparing this antenna to a simple dipole the dipole has always
captured much more signal at a distance over the same test range.

In SimpleScreenRecorder / Custom codec options:

Mika

Comment #28: Sun, 28 Jul 2019, 20:05 (GMT+1, DST)

Quote

thanks for clarifying.

actually, crf value was a typo, was 0 already.

zooming in and comparing the 2 pngs (lossless crf:0 vs lossy crf:20), the latter is definitely the winner - though it makes no sense to me?

regarding the keyinterval, what would be the drawback of leaving this at a default value of 1? this way, accurate cuts of at least 1sec intervals would be possible, after all.

Last modified: Sun, 28 Jul 2019, 20:06 (GMT+1, DST)

In SimpleScreenRecorder / Custom codec options:

Maarten Baert

Administrator

Comment #29: Sun, 28 Jul 2019, 17:51 (GMT+1, DST)

Quote

Quote: Mika

hi maarten,

there you go, i've only ever used avidemux with my h.264 screencasts (ssr default settings + crf 20) and cutting (without errors) is only possible on i-frame base in this mode. i wished accurate cutting was also possible with these final encodes.

now, i noticed something strange when recording losslessly (codec:other, libx264, bitrate:0, preset=veryfast,crf=15,keyint=1). i took stills of a scene from a lossless screencast vs lossy sc (h.264, crf 20, preset veryfast) and i could clearly spot artefacts in the lossless picture. the lossy one looks far superior. how is that possible after all?

apart from crf, bitrate and the keyinterval, the settings should be identical, i guess.

What you describe:

codec:other, libx264, bitrate:0, preset=veryfast,crf=15,keyint=1

... isn't lossless. If you want actual lossless, try:

codec:other, libx264, bitrate:0, preset=veryfast,crf=0,keyint=1,pixelformat=yuv444

or if your editing software supports H.264 RGB:

codec:other, libx264rgb, bitrate:0, preset=veryfast,crf=0,keyint=1

The option crf=0 is what makes it lossless. keyint=1 turns every frame into a keyframe to make editing easier.

Last modified: Sun, 28 Jul 2019, 17:52 (GMT+1, DST)

In SimpleScreenRecorder / Custom codec options:

Mika

Comment #30: Wed, 24 Jul 2019, 13:13 (GMT+1, DST)

Quote

hi maarten,

there you go, i've only ever used avidemux with my h.264 screencasts (ssr default settings + crf 20) and cutting (without errors) is only possible on i-frame base in this mode. i wished accurate cutting was also possible with these final encodes.

now, i noticed something strange when recording losslessly (codec:other, libx264, bitrate:0, preset=veryfast,crf=15,keyint=1). i took stills of a scene from a lossless screencast vs lossy sc (h.264, crf 20, preset veryfast) and i could clearly spot artefacts in the lossless picture. the lossy one looks far superior. how is that possible after all?

apart from crf, bitrate and the keyinterval, the settings should be identical, i guess.

Copyright 2009-2020 Maarten Baert