# Issue: PulseAudio command working with console but not in Exec node

**URL:** <https://discourse.nodered.org/t/issue-pulseaudio-command-working-with-console-but-not-in-exec-node/46716>\
**Category:** General\
**Created:** [5 June 2021 06:22 UTC](https://discourse.nodered.org/t/issue-pulseaudio-command-working-with-console-but-not-in-exec-node/46716 "2021-06-05T06:22:08Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![janedoe123](https://avatars.discourse-cdn.com/v4/letter/j/b19c9b/32.png) [@janedoe123](https://discourse.nodered.org/u/janedoe123)\
**Post date:** [5 June 2021 10:30 UTC](https://discourse.nodered.org/t/issue-pulseaudio-command-working-with-console-but-not-in-exec-node/46716/13 "2021-06-05T10:30:55Z")

</div>

Ok so I have tried something else.

In the console, I am executing the below comand:

`pi@raspberrypi:~ $ pactl load-module module-loopback latency_msec=1 source=1 sink=0 | multimon-ng -a DTMF /dev/stdin`

It is successfully working:

```auto
multimon-ng 1.1.8
  (C) 1996/1997 by Tom Sailer HB9JNX/AE4WA
  (C) 2012-2019 by Elias Oenal
Available demodulators: POCSAG512 POCSAG1200 POCSAG2400 FLEX EAS UFSK1200 CLIPFSK FMSFSK AFSK1200 AFSK2400 AFSK2400_2 AFSK2400_3 HAPN4800 FSK9600 DTMF ZVEI1 ZVEI2 ZVEI3 DZVEI PZVEI EEA EIA CCIR MORSE_CW DUMPCSV X10 SCOPE
Enabled demodulators: DTMF

```

If I try to launch the very same command using Node-RED and having a look at the logs, I am getting the below error message:

```auto
Failed to parse module arguments
Failed to load module "module-loopback" (argument: "latency_msec=1 source=1 sink=0 | multimon-ng -a DTMF /dev/stdin"): initialization failed.
^C

```

I also found a similar thread here: [Exec Node and Terminal Problem ( Alsa)](https://discourse.nodered.org/t/exec-node-and-terminal-problem-alsa/24980)  
Not sure it is related to the same issue...

I am really clueless... Why would it work with the console, and not node-Red ?

---

_[View the full topic](https://discourse.nodered.org/t/issue-pulseaudio-command-working-with-console-but-not-in-exec-node/46716)._