Robert Cameron wrote:
> The post about a typo and 3 slashes is incorrect. For using the
pipe://
protocol, the command to be executed follows
pipe://@. If the command is in your @$PATH
then the initial slash—and therefore, the full path—is not necessary. However, if it is not, or to ensure that a particular binary is used, then you would specify the full path, including the initial "third" slash.
>
> So, you will either have
pipe://ffmpeg
or
pipe:///usr/bin/ffmpeg
(assuming your
ffmpeg
binary is in
/usr/bin@. @pipe://usr/bin/ffmpeg
will only work if there is a
ffmpeg
binary in a
usr/bin
subdirectory of whatever the current directory of the Tvheadend process is. If for some reason that current directory is
/@, then the command will work. But most likely it will cause an error.
>
> From the documentation at http://docs.tvheadend.org/webui/config_muxes/ :
> > *pipe://*: Read standard output from an external program. If the program name does not have a forward slash (@/@) as the first character, the PATH environment variable is used to find the program name in all directories specified by PATH. Additional arguments may be separated using spaces.
You're right. I'm not a Linux expert, so sometimes I get a little confused. I have removed that incorrect post, and fixed my post above it (again), just in case anyone else discovers this thread. On my system, ffmpeg is in my path, so I just use the @pipe://ffmpeg...
syntax.
I was just telling you what worked for me, and it was based on something someone else had posted quite some time back, and generally if something works I'm happy and don't go asking too many questions about why. In your case it's obviously not working, and I cannot tell you why. I do recall in the dim recesses of my memory that at one time one of the distributions had started providing avconf (I think it was called, don't quote me on that) rather than ffmpeg, but they either renamed it to ffmpeg or provided some kind of shim program that just passed the call on to avconf. I do recall that you had to make sure that you were using genuine ffmpeg, and that this would not work with the "avconf relabeled as ffmpeg" version. I would be a little surprised if that is your issue, but it's probably worth checking. It's also possible that something about the CPU in the RPi3 is not allowing it to work as shown; I have only ever run TVHeadend on an Intel-based machine.
You can certainly try leaving out the -strict option, or using other values, but I'd be really surprised if that turns out to be the issue.
I wish I could be of more help, but since it works for me I'm kind of out of ideas. Sorry about that. I hope you can get it working.
