| 1 |
On Thursday, 19 September 2019 03:45:59 BST Adam Carter wrote: |
| 2 |
> On Thu, Sep 19, 2019 at 9:58 AM Walter Dnes <waltdnes@××××××××.org> wrote: |
| 3 |
> > On Wed, Sep 18, 2019 at 09:14:44PM +0100, Mick wrote |
| 4 |
> > |
| 5 |
> > > Yes, you only have one card 0. The first device (default) is the |
| 6 |
> > |
| 7 |
> > analogue. |
| 8 |
> > |
| 9 |
> > > What does 'arecord -l' show? |
| 10 |
> > |
| 11 |
> > **** List of CAPTURE Hardware Devices **** |
| 12 |
> > card 0: PCH [HDA Intel PCH], device 0: CX20641 Analog [CX20641 Analog] |
| 13 |
> > |
| 14 |
> > Subdevices: 1/1 |
| 15 |
> > Subdevice #0: subdevice #0 |
| 16 |
> > |
| 17 |
> > card 0: PCH [HDA Intel PCH], device 2: CX20641 Alt Analog [CX20641 Alt |
| 18 |
> > Analog] |
| 19 |
> > |
| 20 |
> > Subdevices: 1/1 |
| 21 |
> > Subdevice #0: subdevice #0 |
| 22 |
> > |
| 23 |
> > I don't run "desktop environments"; I run useful applications |
| 24 |
> |
| 25 |
> I think for what you are trying to do, the capture devices/mic are not |
| 26 |
> relevant - there will be no signal on them. The playback device have the |
| 27 |
> signal, and ffmpeg needs to capture of those signals. |
| 28 |
> |
| 29 |
> > -i hw:0,1 |
| 30 |
> > |
| 31 |
> > or |
| 32 |
> > |
| 33 |
> > -i hw:0,0,1 |
| 34 |
> |
| 35 |
> Both fail with No such file or directory. |
| 36 |
> |
| 37 |
> FWIW audacity has a drop down list of the output devices, and on my system |
| 38 |
> they're all shown as hw:X,Y. There's no hw:X or hw:X,Y,Z. I also notice |
| 39 |
> that the same hw:X,Y is used for both an playback and capture device, so i |
| 40 |
> guess that means that '-i hw:0.1' is using the hw:0,1 capture device, which |
| 41 |
> for you has no signal, and therefore ffmpeg doesnt capture anything. |
| 42 |
> |
| 43 |
> Hopefully there's some way to capture the output digitally, but if not, a |
| 44 |
> cable connecting the analogue out to the analogue in should work. |
| 45 |
|
| 46 |
I'm sorry - I had misunderstood the original requirement! I thought Walter |
| 47 |
wanted to capture the whole desktop (not a single application window within |
| 48 |
it) and record voice along with it - not the sound of the application. The |
| 49 |
command shown does that - records a screencast of the desktop and voice from |
| 50 |
the microphone. |
| 51 |
|
| 52 |
Having read the first email to the list once more, I can confirm the ffmpeg |
| 53 |
command will work, but only with the audio loopback configured. |
| 54 |
|
| 55 |
It should also work nicely with jackd - which along with qjackctl would be my |
| 56 |
preference. |
| 57 |
|
| 58 |
https://qjackctl.sourceforge.io/qjackctl-index.html |
| 59 |
|
| 60 |
-- |
| 61 |
Regards, |
| 62 |
|
| 63 |
Mick |
Archives