Ezcap as Audio source no sound detected by audio-recorder app

Bug #1671931 reported by Bryan Castillo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Audio Recorder
Medium
moma

Bug Description

I am using the ezcap audio line-in for audio source. Pulse audio detects sound input by looking at the vu meter on pulse audio, audacity records audio, vlc plays audio to speakers.

Audio-recorder detects as sound source and can be selected as usb ezcap mic input but no sound is detected by audio-recorder as evidence by no vu meter activity and when clicking record, no sound is recorded.

Thank you

Revision history for this message
moma (osmoma) wrote : Re: [Bug 1671931] [NEW] Ezcap as Audio source no sound detected by audio-recorder app

Hello,
Would you like to test the recording in a terminal window (command line).
It is easy to do.

Goto [Additional settings], "Recording commands" and use the [Show cmd]
button to display the actual Gstreamer-pipeline that does the recording.
Then run the shown pipeline in a terminal window. This how you can easily
DEBUG and learn more about the recording formats and devices.

Take also listing of your audio devices. Then use correct device in the
recording command.
The [Show cmd] dialog gives you instructions about the "pactl list"
command.

Please see also (more instructions):
https://answers.launchpad.net/audio-recorder/+question/352293
and
https://answers.launchpad.net/audio-recorder/+question/273078

Please tell me about your findings.
  Osmo (Moma)
  Portugal

On Fri, Mar 10, 2017 at 8:56 PM, Bryan Castillo <email address hidden>
wrote:

> Public bug reported:
>
> I am using the ezcap audio line-in for audio source. Pulse audio detects
> sound input by looking at the vu meter on pulse audio, audacity records
> audio, vlc plays audio to speakers.
>
> Audio-recorder detects as sound source and can be selected as usb ezcap
> mic input but no sound is detected by audio-recorder as evidence by no
> vu meter activity and when clicking record, no sound is recorded.
>
>
> Thank you
>
> ** Affects: audio-recorder
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to Audio
> Recorder.
> https://bugs.launchpad.net/bugs/1671931
>
> Title:
> Ezcap as Audio source no sound detected by audio-recorder app
>
> Status in Audio Recorder:
> New
>
> Bug description:
> I am using the ezcap audio line-in for audio source. Pulse audio
> detects sound input by looking at the vu meter on pulse audio,
> audacity records audio, vlc plays audio to speakers.
>
> Audio-recorder detects as sound source and can be selected as usb
> ezcap mic input but no sound is detected by audio-recorder as evidence
> by no vu meter activity and when clicking record, no sound is
> recorded.
>
>
> Thank you
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/audio-recorder/+bug/1671931/+subscriptions
>

--
Sent from my PC, laptop or phone with Ubuntu-Linux.

Revision history for this message
moma (osmoma) wrote :

Please reply and copy/paste the device list (pactl list...) and Gstreamer-pipeline here.

moma (osmoma)
Changed in audio-recorder:
importance: Undecided → Medium
assignee: nobody → moma (osmoma)
Revision history for this message
Bryan Castillo (brycastillo) wrote : Re: [Bug 1671931] Re: Ezcap as Audio source no sound detected by audio-recorder app

pactl list | grep -A3 'Source #'Source #0
State: IDLE
Name: alsa_output.pci-0000_00_01.1.hdmi-surround.monitor
Description: Monitor of Built-in Audio Digital Surround 5.1 (HDMI)
--
Source #1
State: SUSPENDED
Name: alsa_input.pci-0000_00_12.2-usb-0_3.analog-stereo
Description: USBTV007 Video Grabber [EasyCAP] Analog Stereo
--
Source #2
State: SUSPENDED
Name: alsa_output.pci-0000_00_14.2.analog-stereo.monitor
Description: Monitor of Built-in Audio Analog Stereo
--
Source #3
State: SUSPENDED
Name: alsa_input.pci-0000_00_14.2.analog-stereo
Description: Built-in Audio Analog Stereo

On Fri, Mar 10, 2017 at 5:03 PM, moma <email address hidden> wrote:

> Please reply and copy/paste the device list (pactl list...) and
> Gstreamer-pipeline here.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1671931
>
> Title:
> Ezcap as Audio source no sound detected by audio-recorder app
>
> Status in Audio Recorder:
> New
>
> Bug description:
> I am using the ezcap audio line-in for audio source. Pulse audio
> detects sound input by looking at the vu meter on pulse audio,
> audacity records audio, vlc plays audio to speakers.
>
> Audio-recorder detects as sound source and can be selected as usb
> ezcap mic input but no sound is detected by audio-recorder as evidence
> by no vu meter activity and when clicking record, no sound is
> recorded.
>
>
> Thank you
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/audio-recorder/+bug/1671931/+subscriptions
>

Revision history for this message
Bryan Castillo (brycastillo) wrote :

gst-launch-1.0 -e pulsesrc
device=alsa_input.pci-0000_00_12.2-usb-0_3.analog-stereo ! queue !
audioresample ! audioconvert ! audio/x-raw,rate=44100,channels=2 !
lamemp3enc name=enc target=0 quality=2 ! xingmux ! id3mux ! filesink
location=test.mp3

On Fri, Mar 10, 2017 at 5:03 PM, moma <email address hidden> wrote:

> Please reply and copy/paste the device list (pactl list...) and
> Gstreamer-pipeline here.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1671931
>
> Title:
> Ezcap as Audio source no sound detected by audio-recorder app
>
> Status in Audio Recorder:
> New
>
> Bug description:
> I am using the ezcap audio line-in for audio source. Pulse audio
> detects sound input by looking at the vu meter on pulse audio,
> audacity records audio, vlc plays audio to speakers.
>
> Audio-recorder detects as sound source and can be selected as usb
> ezcap mic input but no sound is detected by audio-recorder as evidence
> by no vu meter activity and when clicking record, no sound is
> recorded.
>
>
> Thank you
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/audio-recorder/+bug/1671931/+subscriptions
>

Revision history for this message
moma (osmoma) wrote :
Download full text (4.5 KiB)

Hello,
Very good. Now you have the recording command. Let us test it in a
terminal window (command line).

0) Open a terminal window (for example, press: CNTR + ALT + t)

1) First, install gstreamer1.0-tools package. The gst-launch-1.0 command
comes from that package.
Run this command:
*sudo apt install gstreamer1.0-tools*

2) Now test the Gstreamer-pipeline.
Run your recording command (be careful not to break it. It is one, long
line).
Notice: the command will record to (output to)* test.mp3 *file.

*gst-launch-1.0 -e
pulsesrc device=alsa_input.pci-0000_00_12.2-usb-0_3.analog-stereo ! queue
! audioresample ! audioconvert ! audio/x-raw,rate=44100,channels=2
! lamemp3enc name=enc target=0 quality=2 ! xingmux ! id3mux !
filesink location=test.mp3*

Now check if the output test.mp3 has content. Re-play it. Play it in a
video player (totem).
*totem test.mp3*

Hope this will clarify if the recording works or not.
---

Looks like the devices (in the list) are found and are ok.
Looks like the Gstreamer pipeline (recording command() is ok.

You may also add a "*volume*" element to the pipeline. It increases or
decreases the volume/audio level (0.1 ... 10) of the recording.
Ref:
https://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-base-plugins/html/gst-plugins-base-plugins-volume.html
With the "volume" element, the command becomes:

*gst-launch-1.0 -e
pulsesrc device=alsa_input.pci-0000_00_12.2-usb-0_3.analog-stereo ! ** volume
volume=6 ! **queue ! audioresample ! audioconvert !
audio/x-raw,rate=44100,channels=2 ! lamemp3enc name=enc target=0 quality=2
! xingmux ! id3mux ! filesink location=test.mp3*

Again, replay the test3.mp3 file to check.

Check also the audio (input) settings.
Please see: http://bildr.no/view/QUhPa0Jh
Start it from the sound-menu (icon). Check the input level (is it muted or
low?)

There are also the "pacmd" and "pactl" commands that can do magical things.
I do not know`em well.
*pacmd --help*

*pactl --help*

Please report your findings.

On Sun, Mar 12, 2017 at 4:01 AM, Bryan Castillo <email address hidden>
wrote:

> pactl list | grep -A3 'Source #'Source #0
> State: IDLE
> Name: alsa_output.pci-0000_00_01.1.hdmi-surround.monitor
> Description: Monitor of Built-in Audio Digital Surround 5.1 (HDMI)
> --
> Source #1
> State: SUSPENDED
> Name: alsa_input.pci-0000_00_12.2-usb-0_3.analog-stereo
> Description: USBTV007 Video Grabber [EasyCAP] Analog Stereo
> --
> Source #2
> State: SUSPENDED
> Name: alsa_output.pci-0000_00_14.2.analog-stereo.monitor
> Description: Monitor of Built-in Audio Analog Stereo
> --
> Source #3
> State: SUSPENDED
> Name: alsa_input.pci-0000_00_14.2.analog-stereo
> Description: Built-in Audio Analog Stereo
>
> On Fri, Mar 10, 2017 at 5:03 PM, moma <email address hidden> wrote:
>
> > Please reply and copy/paste the device list (pactl list...) and
> > Gstreamer-pipeline here.
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1671931
> >
> > Title:
> > Ezcap as Audio source no sound detected by audio-recorder app
> >
> > Status in Audio Recorder:
> > New
> >
> > Bug description:
> > I am using the e...

Read more...

Revision history for this message
moma (osmoma) wrote :

Looks like the commands are surrounded by a *.
Please remove the * (from beginning and tail) before testing the commands.

Revision history for this message
moma (osmoma) wrote :

Launchpad.net also added some ** the other recording pipeline with the "volume" element. Please check the command carefully. Take an original copy from the audio-recorder program (as you did earlier).

Revision history for this message
moma (osmoma) wrote :

Sorry for double posting, but I am repeating the last reply without the `*`s.

Very good.
Now you have the recording command. Let us test it in a terminal window (command line).

0) Open a terminal window (for example, press: CNTR + ALT + t)

1) First, install gstreamer1.0-tools package. The gst-launch-1.0 command comes from that package. Run this command:
sudo apt install gstreamer1.0-tools

2) Now test the Gstreamer-pipeline.
Run your recording command (be careful not to break it. It is one, long line).
Notice: the command will record to (output to) test.mp3 file.

gst-launch-1.0 -e pulsesrc device=alsa_input.pci-0000_00_12.2-usb-0_3.analog-stereo ! queue ! audioresample ! audioconvert ! audio/x-raw,rate=44100,channels=2 ! lamemp3enc name=enc target=0 quality=2 ! xingmux ! id3mux ! filesink location=test.mp3

Now check if the output test.mp3 has content. Re-play it. Play it in the video player (totem).
totem test.mp3

Hope this will clarify if the recording works or not.
---

Looks like the devices (in the list) are found and ok.
Looks like the Gstreamer pipeline (recording command() is ok.

You may also add a "volume" element to the pipeline. It increases or decreases the volume/audio level (0.1 ... 10) of the recording.
Ref: https://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-base-plugins/html/gst-plugins-base-plugins-volume.html

With the "volume" element, the command becomes:

gst-launch-1.0 -e pulsesrc device=alsa_input.pci-0000_00_12.2-usb-0_3.analog-stereo ! volume volume=6 ! queue ! audioresample ! audioconvert ! audio/x-raw,rate=44100,channels=2 ! lamemp3enc name=enc target=0 quality=2 ! xingmux ! id3mux ! filesink location=test.mp3

Play or produce some sound/noise on the alsa_input.pci-0000_00_12.2-usb-0_3.analog-stereo device. Then record it with the above command.
Again, replay the test3.mp3 file to check the content. Change the volume= value (between 0.1 ... 10) and check again test.mp3. Ok?

Check also the audio (input) settings.
Please see: http://bildr.no/view/QUhPa0Jh
Start it from the sound-menu (icon). Check the input level (is it muted or low?)

There are also the "pacmd" and "pactl" commands that can do magical things. I do not know`em well.
pacmd --help
pactl --help

Please report your findings.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers