Hi all,

maybe someone knows how to get around this:
SimpleScreenRecorder can only write video files in matroska format, but
any other selection makes it refuse to write the header.

Selecting MP4 as output for instance, always leads to "H.264 (not
installed)".
I already installed all the "264" stuff, but the error still persists.

Did I miss something?

Thanks!

Best regards,

Markus

--
Please reply to group only.
For private email please use http://www.dipl-ing-kessler.de/email.htm

On Wed, 13 Sep 2023 16:44:46 -0000 (UTC) Markus Robert Kessler wrote:

> Hi all,
>
> maybe someone knows how to get around this:
> SimpleScreenRecorder can only write video files in matroska format, but
> any other selection makes it refuse to write the header.
>
> Selecting MP4 as output for instance, always leads to "H.264 (not
> installed)".
> I already installed all the "264" stuff, but the error still persists.

Kdenlive also refuses to render based on H.264, though

lib64x264_164-0.164-0.20220222.2.mga9.tainted
lib64x264-devel-0.164-0.20220222.2.mga9.tainted

is installed and the symlink

/usr/lib64/libx264.so -> libx264.so.164

is there.

Does this work on any other machine?

Best regards,

Markus

--
Please reply to group only.
For private email please use http://www.dipl-ing-kessler.de/email.htm

On Wed, 13 Sep 2023 15:14:49 -0400, Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:

> On Wed, 13 Sep 2023 16:44:46 -0000 (UTC) Markus Robert Kessler wrote:
>
>> Hi all,
>>
>> maybe someone knows how to get around this:
>> SimpleScreenRecorder can only write video files in matroska format, but
>> any other selection makes it refuse to write the header.
>>
>> Selecting MP4 as output for instance, always leads to "H.264 (not
>> installed)".
>> I already installed all the "264" stuff, but the error still persists.
>
> Kdenlive also refuses to render based on H.264, though
>
> lib64x264_164-0.164-0.20220222.2.mga9.tainted
> lib64x264-devel-0.164-0.20220222.2.mga9.tainted
>
> is installed and the symlink
>
> /usr/lib64/libx264.so -> libx264.so.164
>
> is there.
>
> Does this work on any other machine?

Just tried it and it's working here. Make sure you have the tainted version of
ffmpeg installed.

Regards, Dave Hodgins

On Mon, 18 Sep 2023 18:16:37 -0400, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:

> On Wed, 13 Sep 2023 15:14:49 -0400, Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
>
>> On Wed, 13 Sep 2023 16:44:46 -0000 (UTC) Markus Robert Kessler wrote:
>>
>>> Hi all,
>>>
>>> maybe someone knows how to get around this:
>>> SimpleScreenRecorder can only write video files in matroska format, but
>>> any other selection makes it refuse to write the header.
>>>
>>> Selecting MP4 as output for instance, always leads to "H.264 (not
>>> installed)".
>>> I already installed all the "264" stuff, but the error still persists.
>>
>> Kdenlive also refuses to render based on H.264, though
>>
>> lib64x264_164-0.164-0.20220222.2.mga9.tainted
>> lib64x264-devel-0.164-0.20220222.2.mga9.tainted
>>
>> is installed and the symlink
>>
>> /usr/lib64/libx264.so -> libx264.so.164
>>
>> is there.
>>
>> Does this work on any other machine?
>
> Just tried it and it's working here. Make sure you have the tainted version of
> ffmpeg installed.

I should have clarified. I tried simplescreenrecorder on m9, not kdenlive.

Regards, Dave Hodgins

On Mon, 18 Sep 2023 18:16:37 -0400 David W. Hodgins wrote:

> On Wed, 13 Sep 2023 15:14:49 -0400, Markus Robert Kessler
> <no_reply@dipl-ing-kessler.de> wrote:
>
>> On Wed, 13 Sep 2023 16:44:46 -0000 (UTC) Markus Robert Kessler wrote:
>>
>>> Hi all,
>>>
>>> maybe someone knows how to get around this:
>>> SimpleScreenRecorder can only write video files in matroska format,
>>> but any other selection makes it refuse to write the header.
>>>
>>> Selecting MP4 as output for instance, always leads to "H.264 (not
>>> installed)".
>>> I already installed all the "264" stuff, but the error still persists.
>>
>> Kdenlive also refuses to render based on H.264, though
>>
>> lib64x264_164-0.164-0.20220222.2.mga9.tainted
>> lib64x264-devel-0.164-0.20220222.2.mga9.tainted
>>
>> is installed and the symlink
>>
>> /usr/lib64/libx264.so -> libx264.so.164
>>
>> is there.
>>
>> Does this work on any other machine?
>
> Just tried it and it's working here. Make sure you have the tainted
> version of ffmpeg installed.
>
> Regards, Dave Hodgins

Hi,

yes, that was the point:
During base install of the OS I was able to select Kdenlive which got
installed then along with the necessary codecs. Unfortunately, at this
time the "tainted" repos are usually not yet activated.

So, the "non-tainted" ones are installed and due to very similar names it
looked as if everything was fine, but it did not work.

I had to go through "rpm -qa --last | less" to see what happened and had
to manually de-install the useless packages. After that, and after
activating "tainted" repos, a urpmi kdenlive as well as
simplescreenrecorder was successful.

I will keep in mind that such software should not be selected during base
install, but I don't know how this could be solved generically. Maybe
such software should not be selectable at that point, and should be only
visible when the correct repos and hence the needed codecs are availbale?

Thanks,
best regards,

Markus

--
Please reply to group only.
For private email please use http://www.dipl-ing-kessler.de/email.htm

On Wed, 20 Sep 2023 03:26:28 -0400, Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
> yes, that was the point:
> During base install of the OS I was able to select Kdenlive which got
> installed then along with the necessary codecs. Unfortunately, at this
> time the "tainted" repos are usually not yet activated.
>
> So, the "non-tainted" ones are installed and due to very similar names it
> looked as if everything was fine, but it did not work.
>
> I had to go through "rpm -qa --last | less" to see what happened and had
> to manually de-install the useless packages. After that, and after
> activating "tainted" repos, a urpmi kdenlive as well as
> simplescreenrecorder was successful.
>
> I will keep in mind that such software should not be selected during base
> install, but I don't know how this could be solved generically. Maybe
> such software should not be selectable at that point, and should be only
> visible when the correct repos and hence the needed codecs are availbale?

Enabling the tainted repos (release and updates) for each of the arches you
have for the core repos (x86_64 and/or i586) enabled, and then running
"urpmi --auto-update" would replace the core packages with the tainted ones.

# urpmq -i ffmpeg|grep ^Source|sort -uV
Source RPM : ffmpeg-5.1.3-3.mga9.src.rpm
Source RPM : ffmpeg-5.1.3-3.mga9.tainted.src.rpm

The way urpmi works when looking for updates is to look for packages with
a greater value when sorted. The tainted version package name sorts as
greater then the core version when the release/version numbers are the
same.

It won't show/select those updates when using mgaapplet as it passes the
"--update" option to urpmi. With the "--update" option urpmi doesn't look for
updates in the release repos. mgaapplet does that in order to keep the check for
updates quick. Using "urpmi --auto-update" only has to be done once after
enabling a new release repo (tainted or nonfree or i586 on an x86_64 install).

I don't remember off hand if running rpmdrake directly also uses the "--update"
option or not when using it to check for updates.

Regards, Dave Hodgins

On Wed, 20 Sep 2023 10:00:45 -0400, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:

> On Wed, 20 Sep 2023 03:26:28 -0400, Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
>> yes, that was the point:
>> During base install of the OS I was able to select Kdenlive which got
>> installed then along with the necessary codecs. Unfortunately, at this
>> time the "tainted" repos are usually not yet activated.
>>
>> So, the "non-tainted" ones are installed and due to very similar names it
>> looked as if everything was fine, but it did not work.
>>
>> I had to go through "rpm -qa --last | less" to see what happened and had
>> to manually de-install the useless packages. After that, and after
>> activating "tainted" repos, a urpmi kdenlive as well as
>> simplescreenrecorder was successful.
>>
>> I will keep in mind that such software should not be selected during base
>> install, but I don't know how this could be solved generically. Maybe
>> such software should not be selectable at that point, and should be only
>> visible when the correct repos and hence the needed codecs are availbale?
>
> Enabling the tainted repos (release and updates) for each of the arches you
> have for the core repos (x86_64 and/or i586) enabled, and then running
> "urpmi --auto-update" would replace the core packages with the tainted ones.
>
> # urpmq -i ffmpeg|grep ^Source|sort -uV
> Source RPM : ffmpeg-5.1.3-3.mga9.src.rpm
> Source RPM : ffmpeg-5.1.3-3.mga9.tainted.src.rpm
>
> The way urpmi works when looking for updates is to look for packages with
> a greater value when sorted. The tainted version package name sorts as
> greater then the core version when the release/version numbers are the
> same.
>
> It won't show/select those updates when using mgaapplet as it passes the
> "--update" option to urpmi. With the "--update" option urpmi doesn't look for
> updates in the release repos. mgaapplet does that in order to keep the check for
> updates quick. Using "urpmi --auto-update" only has to be done once after
> enabling a new release repo (tainted or nonfree or i586 on an x86_64 install).
>
> I don't remember off hand if running rpmdrake directly also uses the "--update"
> option or not when using it to check for updates.

Forgot to add. You can check which is installed using the rpm command ...
# rpm -q ffmpeg
ffmpeg-5.1.3-3.mga9.tainted

Regards, Dave Hodgins

On 2023-09-20, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:
> On Wed, 20 Sep 2023 10:00:45 -0400, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:
>
>> On Wed, 20 Sep 2023 03:26:28 -0400, Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
>>> yes, that was the point:
>>> During base install of the OS I was able to select Kdenlive which got
>>> installed then along with the necessary codecs. Unfortunately, at this
>>> time the "tainted" repos are usually not yet activated.
>>>
>>> So, the "non-tainted" ones are installed and due to very similar names it
>>> looked as if everything was fine, but it did not work.
>>>
>>> I had to go through "rpm -qa --last | less" to see what happened and had
>>> to manually de-install the useless packages. After that, and after
>>> activating "tainted" repos, a urpmi kdenlive as well as
>>> simplescreenrecorder was successful.
>>>
>>> I will keep in mind that such software should not be selected during base
>>> install, but I don't know how this could be solved generically. Maybe
>>> such software should not be selectable at that point, and should be only
>>> visible when the correct repos and hence the needed codecs are availbale?
>>
>> Enabling the tainted repos (release and updates) for each of the arches you
>> have for the core repos (x86_64 and/or i586) enabled, and then running
>> "urpmi --auto-update" would replace the core packages with the tainted ones.
>>
>> # urpmq -i ffmpeg|grep ^Source|sort -uV
>> Source RPM : ffmpeg-5.1.3-3.mga9.src.rpm
>> Source RPM : ffmpeg-5.1.3-3.mga9.tainted.src.rpm
>>
>> The way urpmi works when looking for updates is to look for packages with
>> a greater value when sorted. The tainted version package name sorts as
>> greater then the core version when the release/version numbers are the
>> same.
>>
>> It won't show/select those updates when using mgaapplet as it passes the
>> "--update" option to urpmi. With the "--update" option urpmi doesn't look for
>> updates in the release repos. mgaapplet does that in order to keep the check for
>> updates quick. Using "urpmi --auto-update" only has to be done once after
>> enabling a new release repo (tainted or nonfree or i586 on an x86_64 install).
>>
>> I don't remember off hand if running rpmdrake directly also uses the "--update"
>> option or not when using it to check for updates.
>
> Forgot to add. You can check which is installed using the rpm command ...
> # rpm -q ffmpeg
> ffmpeg-5.1.3-3.mga9.tainted

Or if you are not quite sure of the name
rpm -qa|grep ffmpeg
This can be useful when the names contain "random" numbers-- eg lib64udev1 or lib64x264_157

rpm -q lib64x264
package lib64x264 is not installed
>
> Regards, Dave Hodgins