Bug 29982 - obs studio cannot find an encoder in the auto configuration wizard
Summary: obs studio cannot find an encoder in the auto configuration wizard
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Rémi Verschelde
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 29990
Blocks:
  Show dependency treegraph
 
Reported: 2022-02-01 11:31 CET by Nikolay Sabelnikov
Modified: 2022-02-04 10:36 CET (History)
2 users (show)

See Also:
Source RPM: obs-studio-26.1.2-1.mga8.src.rpm
CVE:
Status comment:


Attachments
Screenshot of 4 OBS-studio Auto-config windows, no error (143.08 KB, image/png)
2022-02-01 21:04 CET, Lewis Smith
Details
screenshot with steps to reproduce the problem (674.63 KB, image/jpeg)
2022-02-02 06:45 CET, Nikolay Sabelnikov
Details
screenshot with steps to reproduce the problem(eng) (590.96 KB, image/jpeg)
2022-02-03 13:20 CET, Nikolay Sabelnikov
Details

Description Nikolay Sabelnikov 2022-02-01 11:31:11 CET
Description of problem:
The essence of the problem: the encoder cannot start at the initial start.

Version-Release number of selected component (if applicable):
nikolanp@localhost ~> rpm -qa | grep obs
obs-studio-26.1.2-1.mga8
nikolanp@localhost ~> 

How reproducible:
you need to run the automatic configuration wizard

Steps to Reproduce:
1. Launch the obs-studio program
2. Launch the Automatic Configuration wizard
3. Select "optimize for recording only" and click next
4. Once again next.
5. and on the final results I see this error.
Nikolay Sabelnikov 2022-02-01 11:31:17 CET

CC: (none) => 79625490833

Comment 1 Lewis Smith 2022-02-01 21:04:08 CET
Created attachment 13111 [details]
Screenshot of 4 OBS-studio Auto-config windows, no error

Thank you for the report.

I installed the program and found the 'Automatic Configuration Wizard' in the 'Tools' menu. Following your instructions, it went to end without error. I attach a screenshot of the 4 Wizard windows.

Can you please:
1.
> 5. and on the final results I see this error
post the exact error message.

2. Attach (a) similar screenshot(s) - the 4  stages.

CC: (none) => lewyssmith

Comment 2 Nikolay Sabelnikov 2022-02-02 06:45:08 CET
Created attachment 13112 [details]
screenshot with steps to reproduce the problem

Mistake: failed to start the encoder
Comment 3 sturmvogel 2022-02-02 11:24:00 CET
Could you please follow the rules for creating a bug report:
https://wiki.mageia.org/en/How_to_report_a_bug_properly#Principles

The common used language for a bug report is english. You can eiter change your locale or use the recommended way from the wiki article.

We can't read the stuff from your screenshot.
Comment 4 sturmvogel 2022-02-02 11:41:21 CET
The problem with error "Failed to start encoder" only occurs with  obs-studio-26.1.2-1.mga8.x86_64.rpm

With the tainted package obs-studio-26.1.2-1.mga8.tainted.x86_64.rpm this problem don't occur.
Comment 5 Nikolay Sabelnikov 2022-02-02 16:08:58 CET
Я вам для это и перевёл саму ошибку.(In reply to sturmvogel from comment #3)
> Could you please follow the rules for creating a bug report:
> https://wiki.mageia.org/en/How_to_report_a_bug_properly#Principles
> 
> The common used language for a bug report is english. You can eiter change
> your locale or use the recommended way from the wiki article.
> 
> We can't read the stuff from your screenshot.

To do this, I manually translated the error to you.
Nikolay Sabelnikov 2022-02-03 06:29:53 CET

Depends on: (none) => 29990

Nikolay Sabelnikov 2022-02-03 06:30:46 CET

Depends on: 29990 => (none)

Nikolay Sabelnikov 2022-02-03 06:31:07 CET

Depends on: (none) => 29990

Comment 6 Morgan Leijström 2022-02-03 09:53:32 CET
(In reply to Nikolay Sabelnikov from comment #5)
> I manually translated the error to you.

We did not benefit much from the screenshot. Could as well have been in my own mother tongue.

It is usually easy to get it in English, per the link sturmvogel gave: 

"

Please always prefix calls to programs with LC_ALL=C so that error messages or other output will be shown in English, for example
Don't run urpmi somepackage, but LC_ALL=C urpmi somepackage

Some applications will not start in English when using LC_ALL=C. In that case, try LC_ALL=en_US.UTF-8 or LANGUAGE=C

  "

CC: (none) => fri

Comment 7 Nikolay Sabelnikov 2022-02-03 13:20:19 CET
Created attachment 13114 [details]
screenshot with steps to reproduce the problem(eng)

I am sending it in English

Attachment 13112 is obsolete: 0 => 1

Comment 8 Nikolay Sabelnikov 2022-02-03 13:23:04 CET
(In reply to sturmvogel from comment #4)
> The problem with error "Failed to start encoder" only occurs with 
> obs-studio-26.1.2-1.mga8.x86_64.rpm
> 
> With the tainted package obs-studio-26.1.2-1.mga8.tainted.x86_64.rpm this
> problem don't occur.

how do I install this version?
Comment 9 sturmvogel 2022-02-03 14:30:17 CET
You have to enable the Mageia tainted repositories.
https://wiki.mageia.org/en/Install_media_in_Mageia_for_beginners
Comment 10 Lewis Smith 2022-02-03 21:37:11 CET
@Nikolay
For all multi-media applications, enabling Tainted is more or less necessary. It could be an installation option (like Nonfree is). At present, you should enable Tainted ASAP after installation; following which system update will replace standard packages with Tainted ones where appropriate.

The indicated wiki page (above) is clear; thanks sturmvogel for the URL.

But there is a real (if academic) problem:
(In reply to sturmvogel from comment #4)
> The problem with error "Failed to start encoder" only occurs with 
> obs-studio-26.1.2-1.mga8.x86_64.rpm
> With the tainted package obs-studio-26.1.2-1.mga8.tainted.x86_64.rpm this
> problem don't occur.
Assigning to Rémi whose package this is.

Source RPM: obs-studio => obs-studio-26.1.2-1.mga8.src.rpm
Assignee: bugsquad => rverschelde
CC: lewyssmith => (none)

Rémi Verschelde 2022-02-03 22:48:21 CET

Summary: [bug]: obs studio does not start the encoder during the initial setup => [bug]: obs studio cannot find an encoder in the auto configuration wizard

Rémi Verschelde 2022-02-03 22:48:30 CET

Summary: [bug]: obs studio cannot find an encoder in the auto configuration wizard => obs studio cannot find an encoder in the auto configuration wizard

Comment 11 Rémi Verschelde 2022-02-03 22:50:15 CET
I can reproduce the issue, which is indeed specific to the Core Release package which does not have support for the x264 encoder (patent encumbered, tainted only).

That's not something we can fix in Mageia, unless we decide to drop the Core version of the package. I'll report it upstream to see if they want to fix it (either by outright disabling the auto-configuration wizard when x264 is missing, or falling back to another encoder).
Comment 12 Morgan Leijström 2022-02-03 23:03:29 CET
Thank you Rémi
upstream then, awaiting response

Also, this is not a major class bug, but by design.
- workaround is to use tainted version

Keywords: (none) => UPSTREAM
Severity: major => normal

Comment 13 Rémi Verschelde 2022-02-03 23:20:53 CET
So after looking at it, it seems upstream doesn't provide any option to disable the x264 plugin, that's our own patch which adds it.

And as such, the whole software is based around the idea that x264 is available, and that's the only software encoder available. So basically our Core package is useless.

So I'll drop the Core version and obs-studio is going to become a Tainted only package.
Comment 14 Rémi Verschelde 2022-02-03 23:47:20 CET
"Fixed" with obs-studio-27.1.3-1.mga9 which from now on will only be built in tainted.

This can't be fixed in Mageia 8 as we can't remove the package present in Core Release.

Removing the UPSTREAM keyword as in the end it was indeed a packaging error, we were patching x264 out without checking if it's supported - it isn't.

Resolution: (none) => FIXED
Keywords: UPSTREAM => (none)
Version: 8 => Cauldron
Status: NEW => RESOLVED

Comment 15 Morgan Leijström 2022-02-04 00:46:47 CET
I agree.
Thank you for the quick resolution!
Comment 16 Nikolay Sabelnikov 2022-02-04 06:58:34 CET
(In reply to Rémi Verschelde from comment #14)
> "Fixed" with obs-studio-27.1.3-1.mga9 which from now on will only be built
> in tainted.
> 
> This can't be fixed in Mageia 8 as we can't remove the package present in
> Core Release.
> 
> Removing the UPSTREAM keyword as in the end it was indeed a packaging error,
> we were patching x264 out without checking if it's supported - it isn't.

When I was covering on opensuse, I also did not make a separation. And nowhere have I seen such a division, as in mageia.
It was amazing for me. I just suggest that non-free encoders be sent to a certain turnip, if possible. So, at least, they did in opensuse.
Comment 17 Nikolay Sabelnikov 2022-02-04 06:59:51 CET
Don't forget to add me when testing, I'll check.
Comment 18 Morgan Leijström 2022-02-04 10:36:10 CET
non-free encoders are in tainted.

We try to have some applications in both tainted and other repos so users that choose to not use tainted can use some of the applications anyway, with various limitations. Usually that only means less encoders (or with limitations) to choose from.  For obs-studio it seem impossible / too much work.

27.1.3-1 is already built in cauldron tainted/release,
http://pkgsubmit.mageia.org/
heading to your mirror if not already there.
https://mirrors.mageia.org/status
(note: this latter page show how long time since last a indication file was updated - if there no updates it erroneously looks like all mirrors are behind)

We usually do not utilise testing repos in Cauldron, unless it is something that have extra risk of breaking the system, such as a big group of related packages for i.e a desktop environment.

Cauldron as a whole is "testing" for next Mageia release.

Note You need to log in before you can comment on or make changes to this bug.