[mythtv-users] frontend network control port

[Raymond Wagner]

On 12/11/2010 11:37, Richard Morton wrote:
> On 11 December 2010 16:30, John Pilkington<J.Pilk at tesco.net>  wrote:
>> On 11/12/10 16:20, Raymond Wagner wrote:
>>> On 12/11/2010 10:50, Richard Morton wrote:
>>>> On 11 December 2010 15:34, Richard Morton<richard.e.morton at gmail.com>
>>>> wrote:
>>>>> Hi,
>>>>> (0.23 here still)
>>>>> If I play a file through mythvideo and then use the network control
>>>>> port to query location I get the following response
>>>>>
>>>>> # query location
>>>>> Playback Video 00:00:04 1x myth://Videos@192.168.0.2:6543/films/James
>>>>> Bond/17 GoldenEye.mkv 117 25
>>>>>
>>>>> If I do help play :
>>>>> # help play
>>>>> <snip />
>>>>> play file FILENAME - Play FILENAME (FILENAME may be a file or a
>>>>> myth:// URL)
>>>>> <snip />
>>>>>
>>>>> but if I do:
>>>>> # play file myth://Videos@192.168.0.2:6543/films/James Bond/17
>>>>> GoldenEye.mkv
>>>>> or
>>>>> # play file "myth://Videos@192.168.0.2:6543/films/James Bond/17
>>>>> GoldenEye.mkv"
>>>>> or
>>>>> # play file myth://Videos@192.168.0.2:6543/films/James Bond/"17
>>>>> GoldenEye.mkv"
>>>>>
>>>>> it doesnt work...
>>>>>
>>>>> any ideas?
>>>>>
>>>>> thanks
>>>>>
>>>>> R
>>>>>
>>>> The above does try to initiate playback and indicates "Ok" through the
>>>> network control port, but it fails...
>>>>
>>>> This does work however:
>>>> # query location
>>>> Playback Recorded 00:00:14 of 01:08:57 1x 11211 2010-12-11T08:53:00
>>>> 369 myth://192.168.0.2:6543/11211_20101211085300.mpg 25
>>>> # play file myth://192.168.0.2:6543/11211_20101211085300.mpg
>>>> OK
>>>   From the frontend logs, it seems to be ignoring the '@' character.
>> US/UK keyboard?
>>
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>> UK keyboard
> Raymond,
> ok, are you stating it is ignoring the @, or have you reproduced this?
> Have you reproduced this on 0.24? Should this be logged as a bug?

If you watch the frontend logs as you run that command, it reports 
receiving the string minus the '@' character.