CODEWITHSUNDEEP
node.jslinuxraspberry-piomxplayer
Jason Small
Jason Small

Reputation: 1054

Pass : (Colon) into child_process SPAWN arg

I have a command

omxplayer /home/pi/videos/9886a3n2545r7i505rzz.mp4 -o alsa:sysdefault

It runs fine from the command line, but if I translate that command to a spawn command:

let omxProcess = spawn('omxplayer', ['/home/pi/videos/9886a3n2545r7i505rzz.mp4', '-o', 'alsa:sysdefault'])

The command fails (without any error).

But if I run the following removing the :sysdefault it runs (But without the :sysdefault, the command is not the same and I need to run it with :sysdefault

  let omxProcess = spawn('omxplayer', ['/home/pi/videos/9886a3n2545r7i505rzz.mp4', '-o', 'alsa'])

I'm thinking it has to do with having an ":" in the arg.

Any thoughts?

Upvotes: 0

Views: 174

Answers (1)

Robert Kawecki
Robert Kawecki

Reputation: 2458

Since you're not using the shell: true flag, it's almost certainly not caused by the : in the command. You can always verify this, just to be on the safe side.

An easy way to check if the environment is messing with your arguments is calling another binary, for example echo, instead of omxplayer. Does it echo back your arguments? Is the colon still there?

The binary is probably exitting with some error code (and possibly an error message). To capture them, be sure to register handlers on the output streams, as well as an exit handler that should tell you the exit code. This is outlined in the child_process docs, right below spawn(). Adapted for your case:

omxProcess.stdout.on('data', (data) => {
  console.log(`stdout: ${data}`);
});

omxProcess.stderr.on('data', (data) => {
  console.error(`stderr: ${data}`);
});

omxProcess.on('close', (code) => {
  console.log(`child process exited with code ${code}`);
});

Based on the output and the exit code, you should be able to debug the issue.

Upvotes: 0

Related Questions