Time to make Touch web Service less experimental

[mvallevand]

I thought I'd resurrect my python code for XBMC to connect to the touch service but I lost it and had to redo it, at least my python skills improved a little and this only took an hour or so. Here's a video with the problems I see http://youtu.be/lK-Czm5TAzE

- YouTube (beta) Trailer, I have to keep hitting a key for the progress bar to show, there is no async refresh method (not sure what to do with this)
- Video Library the meta data is for the wrong item, likely the caching is before the screen capture
- after Exit @2:30 using the &key interface loads a new session but at the default lower res, requires exit from client and a restart of the server to reinit
- hitting Esc to close a plugin (see recording at 3:10) most of the time doesn't land on the right menu item, it can be before or after.

I agree with Fred this is worth taking further. Speed is pretty good in my environment, I haven't tested on slow machine, I will wait for file urls to work

Also for an enhancement

- when a filename is returned it should be in an object indicating the media type and the resume location.
- new api calls method=recording.watched.set and method=recording.watched.clear need a filename option

Martin

[fred250]

I’d love to see this touch thing grow big. Most of the work has to be made server side so I guess “push it forward” really means trying to get sub to implement all terrific features that comes to mind .

/Fred

@Sub, I hope I didn’t offend you by my comment. I honestly had no intentions to.
Please bear with me since English is not my native language and I’ll probably do it again :o


/Fred

[fred250]

I thought I'd resurrect my python code for XBMC to connect to the touch service but I lost it and had to redo it, at least my python skills improved a little and this only took an hour or so.

An hour or so, impressive Martin!
I think this only shows the potential of this becoming a wide spread client platform.

- YouTube (beta) Trailer, I have to keep hitting a key for the progress bar to show, there is no async refresh method (not sure what to do with this)
- Video Library the meta data is for the wrong item, likely the caching is before the screen capture
- after Exit @2:30 using the &key interface loads a new session but at the default lower res, requires exit from client and a restart of the server to reinit
- hitting Esc to close a plugin (see recording at 3:10) most of the time doesn't land on the right menu item, it can be before or after.

I agree with Fred this is worth taking further. Speed is pretty good in my environment, I haven't tested on slow machine, I will wait for file urls to work

I also noticed that after hitting esc the screen isn’t always in sync. I suggest updating the screen on timer rather than on keypress would correct many errors. I suggested Motion Jpeg earlier.

Also for an enhancement

- when a filename is returned it should be in an object indicating the media type and the resume location.
- new api calls method=recording.watched.set and method=recording.watched.clear need a filename option

Martin

I agree on passing an object instead of just a filename. I would prefer a JSON object rather than XML (as sub indicates by the filename webclient.xml).
Filename, name of the show, description and resume position is what comes to my mind.

/Fred

[mvallevand]

I don't think we need mjpeg but a tag in the response

<META HTTP-EQUIV="REFRESH" CONTENT="15;URL=....">

would be useful.

Martin

[fred250]

I don't think we need mjpeg but a tag in the response

<META HTTP-EQUIV="REFRESH" CONTENT="15;URL=....">

would be useful.

Martin

Yes, if that would do the trick it's fine with me. It would be nice if the frequency was adjustable from the client though. There is always the option to make a periodic call in code from the client, but this would create some overhead of course.



I was thinking of experimenting a bit with timing.info. I usually don't have much trouble with accuracy in seeking but I've found a file that has a bad time line. Now I don't know where to find the timing.info – is it a separate file or inside the .ts?
Is there a setting or is it always generated?


/Fred

[sub]

I’d love to see this touch thing grow big. Most of the work has to be made server side so I guess “push it forward” really means trying to get sub to implement all terrific features that comes to mind .

/Fred

@Sub, I hope I didn’t offend you by my comment. I honestly had no intentions to.
Please bear with me since English is not my native language and I’ll probably do it again :o

No worries. I've sent you a PM on getting access to the pre-releases of the next build, so that I'm in a position to give you patches.

[sub]

Now I don't know where to find the timing.info – is it a separate file or inside the .ts?
Is there a setting or is it always generated?

It's always generated on recordings. It's usually embedded in an Alternate Data Stream on NTFS disks, but can write to a separate *.timing.info file on FAT32, or if you have a registry setting indicating you prefer to have a separate file.

[fred250]

No worries. I've sent you a PM on getting access to the pre-releases of the next build, so that I'm in a position to give you patches.

Thanks!

It's always generated on recordings. It's usually embedded in an Alternate Data Stream on NTFS disks, but can write to a separate *.timing.info file on FAT32, or if you have a registry setting indicating you prefer to have a separate file.

Yes, I eventually found I post showing how to get the information.
http://forums.nextpvr.com/showthread.php...iming.info

/Fred

[mvallevand]

Yes, if that would do the trick it's fine with me. It would be nice if the frequency was adjustable from the client though. There is always the option to make a periodic call in code from the client, but this would create some overhead of course.

What I do in my client is send the /size=1280x720 as kind of a NOP refresh every 10 seconds after keystroke.

Martin

[whurlston]

- YouTube (beta) Trailer, I have to keep hitting a key for the progress bar to show, there is no async refresh method (not sure what to do with this)

Are you talking about the progress bar on the new progress popup? I'll double check my NeedsRendering()