It may turn out that interacting directly with that shell script is good
enough anyway, so I'd try that first. Depending on what the script is
doing, it may already be setting things up for you in a workable manner.
It's worth a try.

Dave

> Indeed you are correct.
>
> I'll have to look into it, because it is a fairly complex bash script (107
> lines).
>
> Thanks,
> Jon
>
>
> On Thu, Nov 19, 2015 at 11:39 AM, Peter Crowther <peter at ozzard.org> wrote:
>
>> On 19 November 2015 at 16:25, Jon Hylands <jon at huv.com> wrote:
>>
>>> pi at raspberrypi ~ $ ps -ef | grep omx
>>> pi        3182  3058  0 16:19 ?        00:00:00 /bin/bash
>>> /usr/bin/omxplayer -r --live --win 54 58 400 447
>>> http://localhost:10088/?action=stream
>>> pi        3190  3182  9 16:19 ?        00:00:19 /usr/bin/omxplayer.bin
>>> -r
>>> --live --win 54 58 400 447 http://localhost:10088/?action=stream
>>>
>>> Why is this happening, and how can I fix it?
>>>
>>>
>>> Bet you /usr/bin/omxplayer is a shell script - take a look.  If it is
>> (i.e. its first line starts with #!/bin/bash) then this is what you'll
>> get;
>> you might wish to invoke omxplayer.bin directly.
>>
>> - Peter
>>
>>
>>
>>
>
>