The latest version of the proposal:
Testcase Audio Recording (change proposal) Description
This test case tests whether sound can be recorded on Fedora.
Prerequisites
- Install any sound recording application you're familiar with. If
you've never worked with any, you can try the *Gnome Sound Recorder*
(the gnome-sound-recorder package), a very simplistic and lightweight
application. Alternatively, you can try other applications, such as
*Audacity* (the audacity package).
- Make sure the input sound device is correctly connected to your
computer, so that you can expect that sound will be recorded, i.e. you have
a microphone (or any sound producing device) connected to the input of your
sound adapter.
- Run *Settings* and navigate to the *Sound* tab. Check that your sound
device is correctly recognized by the system. In case you have more input
sound devices, make sure all of these devices are listed.
- Select a preferred device for input and set the input level using the
slider and the indicator below to avoid over-excitation of the signal and
sound distortion.
How to test
- Start a sound recording application.
- Record a sound clip of about 10 seconds using the microphone (or
another sound producing device).
- Play back the recorded sound.
Expected Results
- The recorded sound clip is *correctly* recorded and can be played
back. Note that the quality of the recording depends on many factors, such
as the quality of the sound adapter, the microphone, the wires used, etc.
Therefore the sound quality should not be considered a test failing
criterion unless it is much worse than expected.
On Fri, Jan 22, 2021 at 3:33 PM Neal Gompa <ngompa13(a)gmail.com> wrote:
On Fri, Jan 22, 2021 at 9:19 AM Kamil Paral <kparal(a)redhat.com>
wrote:
>
> On Fri, Jan 22, 2021 at 3:01 PM Neal Gompa <ngompa13(a)gmail.com> wrote:
>>
>> On Fri, Jan 22, 2021 at 2:01 AM Kamil Paral <kparal(a)redhat.com> wrote:
>> >
>> > On Thu, Jan 21, 2021 at 12:30 PM Neal Gompa <ngompa13(a)gmail.com>
wrote:
>> >>
>> >> GNOME applications pull in most of the GNOME desktop as dependencies.
>> >> Properly developed KDE applications will pull in the KF5 libraries
and
>> >> occasionally some Plasma libraries. That's just how it goes. It is
>> >> also unrealistic to expect GNOME applications to work fully "to
spec"
>> >> on KDE because KDE does not provide all the D-Bus interfaces and
>> >> services that GNOME does. We can and do have quirks when applications
>> >> are transplanted from one desktop environment to another, if the
>> >> underlying frameworks don't handle this well. While most of the
KDE
>> >> frameworks adapt well to a non-KDE environment, it's rare that
GNOME
>> >> applications fully do, especially ones that depend on things like
>> >> gnome-settings-daemon, gnome-shell, or gnome-control-center. In the
>> >> case of gnome-sound-recorder, it'll be fine as it's quite
simple. But
>> >> if you were using something like the GNOME screencast app, that would
>> >> fail in KDE. Note that I'm specifically saying "GNOME
applications".
>> >> Plain GTK applications are generally fine on Plasma.
>> >
>> >
>> > Neal, you're doing a great job in Fedora, but this made me somewhat
angry. Because I *did* spend the time yesterday, installed KDE in a VM from
scratch, and tested gnome-sound-recorder, audacity and kwave in it. And
sounds like you haven't. Gnome-sound-recorder only pulls in gjs and
libhand1, and that's *all*. It's the most minimal application I could find.
I also tested its functionality, it worked without issues. I stand by my
opinion that this is the best sound recorder to recommend. Your reaction is
the tribalism I was talking about, negatively reacting to anything that has
"GNOME" or "K" in the name.
>> >
>>
>> I specifically said that GNOME Sound Recorder is fine because it's
>> simple,
>
>
> I must admit I missed that particular sentence in the middle, sorry.
>
>>
>> but the majority of GNOME applications are *not*. But I was
>> responding *specifically* to your comment about tribalism, because you
>> suggested that all desktop applications for each desktop work fine on
>> other desktops.
>
>
> Ugh... I didn't say that. And I re-read my emails again, just to be sure.
>
> I do feel that the common advice of "install app X if you're on GNOME,
or app Y if you're on KDE" (just because X uses GTK and Y uses QT, or a
similar reason) harms the whole ecosystem. That's why I said I want to
avoid this style of instructions, find a tool that works best everywhere,
and recommend it universally (and then we don't even need to name the
desktops, which might feel like we're looking down on the other ones).
Quote:
> "If one tool works well on all desktops, recommend that one, regardless
of its name or library toolkit used. Of course ideally such a tool
shouldn't pull half of some desktop with it as dependencies (as KWave
does), and should have a reasonably newcomer friendly UI. It would also
make the instructions sound better, currently it seems like we only care
about GNOME and KDE."
>
Hmm, that's more fair than I read it as originally. I'm mostly annoyed
because I've had people complain to me why X GNOME app doesn't work on
KDE (e.g. GNOME screen recording app on Plasma Wayland). It's
frustrating how we've regressed on inter-desktop interoperability over
the past few years...
--
真実はいつも一つ!/ Always, there's only one truth!
_______________________________________________
test mailing list -- test(a)lists.fedoraproject.org
To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
--
Lukáš Růžička
FEDORA QE, RHCE
Red Hat
<
https://www.redhat.com>
Purkyňova 115
612 45 Brno - Královo Pole
lruzicka(a)redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <
https://redhat.com/trusted>