[RELEASE] XBMCFlix-o-mate

Thank You for the new version. I removed the previous version, laid down the new version and rebooted. I see you have auto fullscreen according to the documentation. The video still does not go full screen. Do I need to configure something?

Here is the debug output:


AutoITdebug: Script Variables:
AutoITdebug: $ScriptsDir: C:\script
AutoITdebug: $SikuliDir:
AutoITdebug: $JavaDir:
AutoITdebug: $netFlixTogglePlayHotKey: {SPACE}
AutoITdebug: $netFlixFF: >
AutoITdebug: $netFlixRewind: <
AutoITdebug: $netFlixTerminate: Q
AutoITdebug: $XBMCFlixomateExit: X
AutoITdebug: $netFlixLaunchHotKey: O
AutoITdebug: Java location gathered from registry: C:\Program Files\Java\jre6\bi
n
AutoITdebug: Java file found at registry location!
AutoITdebug: $SikuliDir c:\Program Files\Sikuli X
AutoITdebug: Sikuli file found at above location!
AutoITdebug: run("C:\Program Files\Java\jre6\bin\Java.exe" -jar sikuli-ide.jar -
r"C:\script\XBMCFlix-o-mate.sikuli" --args debug,c:\Program Files\Sikuli X)
[info] Sikuli vision engine loaded.
[info] Windows utilities loaded.
[info] VDictProxy loaded.
Sikuli debug: ControlBarRegion defined as: 0,614,1024,154
[log] toggle highlight Region[0,614 1024x154]@Screen(0)[0,0 1024x768] E:Y, T:3.0
E:Y, T:3.0: true
Sikuli debug: NextEpisodeRegion defined as: 307,230,410,308
[log] toggle highlight Region[307,230 410x308]@Screen(0)[0,0 1024x768] E:Y, T:3.
0 E:Y, T:3.0: true
Sikuli debug: TestEpisodeRegion defined as: 512,384,62,85
[log] toggle highlight Region[512,384 62x85]@Screen(0)[0,0 1024x768] E:Y, T:3.0
E:Y, T:3.0: true
[info] add hotkey: CTRL+ALT+SHIFT O
[info] add hotkey: CTRL+ALT+SHIFT F
[info] add hotkey: CTRL+ALT+SHIFT N
[info] add hotkey: CTRL+ALT+SHIFT B
[info] add hotkey: CTRL+ALT+SHIFT T
[info] add hotkey: CTRL+ALT+SHIFT J
[info] add hotkey: CTRL+ALT+SHIFT H
[info] add hotkey: CTRL+ALT+SHIFT K
[info] add hotkey: CTRL+ALT+SHIFT A
[info] add hotkey: CTRL+ALT+SHIFT Q
[info] add hotkey: CTRL+ALT+SHIFT X
Sikuli debug: in netFlixLaunch (O+11)
AutoITdebug: keys sent: C+A+S+O
AutoITdebug: newNFLaunchFlag set to: 0
Sikuli debug: loading movie
Sikuli debug: loaded movie
Sikuli debug: in goNextEpisode (N+11)
[log] CLICK on (512,384)
[log] CLICK on (164,713)
Sikuli debug: Click Skip Episode result: 1
Sikuli debug: in netFlixLaunch (O+11)
Sikuli debug: loading movie
Sikuli debug: loaded movie
Sikuli debug: in toggleNetFlixFullScreen (F+11)
[log] CLICK on (512,384)
[log] CLICK on (883,677)
Sikuli debug: Click Full Screen result (manual toggle): 1
Sikuli debug: in toggleNetFlixFullScreen (F+11)
[log] CLICK on (512,384)
[log] CLICK on (958,747)
Sikuli debug: Click Full Screen result (manual toggle): 1
AutoITdebug: Received C+A+S+Q for Netflix termination
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: newNFLaunchFlag set to: 1


After the video started playing I did:

ctrl+alt+shift+n for next video(Skipped to next video, but still no full screen).

ctrl+alt+shift+f for fullscreen(This worked).

ctrl+alt+shift+f to exit fullscreen(This worked).

ctrl+alt+shift+q to quit(This worked).

(2012-05-13 03:17)kevev Wrote:  Thank You for the new version. I removed the previous version, laid down the new version and rebooted. I see you have auto fullscreen according to the documentation. The video still does not go full screen. Do I need to configure something?

Here is the debug output:
....
Sikuli debug: in toggleNetFlixFullScreen (F+11)
[log] CLICK on (512,384)
[log] CLICK on (958,747)
Sikuli debug: Click Full Screen result (manual toggle): 1
....

After the video started playing I did:

ctrl+alt+shift+n for next video(Skipped to next video, but still no full screen).

ctrl+alt+shift+f for fullscreen(This worked).

ctrl+alt+shift+f to exit fullscreen(This worked).

ctrl+alt+shift+q to quit(This worked).

Ok...so I took a look at this again. I had some issues with certain resolutions. I had done a lot of my testing outside of XBMC (just launching Netflix in IE) and had not always remembered to put my IE in Kiosk/Full screen mode (F11), which is how XBMC launches it. Because of this, some of the scan regions were off at certain resolutions.

However your tests are not entirely accurate. It is not possible that CTRL+ALT+SHIFT+F worked for you to GO INTO full screen, because the button would not be in the scan region. You can see this in your output above where it says:

Sikuli debug: in toggleNetFlixFullScreen (F+11)
[log] CLICK on (512,384)

That shows that although you tried to toggle full screen, nothing happened. Now, it is possible that the way you were hitting the keys you also then just hit the "F" key by itself which is Netflix's built in Full Screen key... Once in Full Screen the Full Screen button would have been visible in the scan region...so when you see in your log:

[log] CLICK on (958,747)
Sikuli debug: Click Full Screen result (manual toggle): 1

That shows that it clicked near the corner of your screen and the result (1) was a success. The lack of a second "Sikuli debug: in toggleNetFlixFullScreen (F+11)" may have indicated you were doing things too fast as well. Normal circumstances wouldn't have you changing these things within a second or two of each other (no reason to keep toggling full screen unless testing...). So, when doing testing you should always wait about 5-10 seconds in between giving it commands. In reality (and non-debug mode) you can usually go very quickly, but not for testing's sake...

In any event, I have upped a new 1.5b version which should fix the scan regions on the 1024x768 resolution as well as with some other minor things I found.

Let me know how it works out.

I tested the new version. Still no auto fullscreen.

Here is some debug output:


AutoITdebug: Script Variables:
AutoITdebug: $ScriptsDir: C:\script
AutoITdebug: $SikuliDir:
AutoITdebug: $JavaDir:
AutoITdebug: $netFlixTogglePlayHotKey: {SPACE}
AutoITdebug: $netFlixFF: >
AutoITdebug: $netFlixRewind: <
AutoITdebug: $netFlixTerminate: Q
AutoITdebug: $XBMCFlixomateExit: X
AutoITdebug: $netFlixLaunchHotKey: O
AutoITdebug: Java location gathered from registry: C:\Program Files\Java\jre6\bi
n
AutoITdebug: Java file found at registry location!
AutoITdebug: $SikuliDir c:\Program Files\Sikuli X
AutoITdebug: Sikuli file found at above location!
AutoITdebug: run("C:\Program Files\Java\jre6\bin\Java.exe" -jar sikuli-ide.jar -
r"C:\script\XBMCFlix-o-mate.sikuli" --args debug,c:\Program Files\Sikuli X)
[info] Sikuli vision engine loaded.
[info] Windows utilities loaded.
[info] VDictProxy loaded.
Sikuli debug: ControlBarRegion defined as: 0,568,1024,200
Sikuli debug: NetflixLogoRegion defined as: 358,192,308,231
Sikuli debug: NextEpisodeRegion defined as: 512,337,62,132
[log] toggle highlight Region[0,568 1024x200]@Screen(0)[0,0 1024x768] E:Y, T:3.0
E:Y, T:3.0: true
[log] toggle highlight Region[358,192 308x231]@Screen(0)[0,0 1024x768] E:Y, T:3.
0 E:Y, T:3.0: true
[log] toggle highlight Region[512,337 62x132]@Screen(0)[0,0 1024x768] E:Y, T:3.0
E:Y, T:3.0: true
[info] add hotkey: CTRL+ALT+SHIFT O
[info] add hotkey: CTRL+ALT+SHIFT F
[info] add hotkey: CTRL+ALT+SHIFT N
[info] add hotkey: CTRL+ALT+SHIFT B
[info] add hotkey: CTRL+ALT+SHIFT T
[info] add hotkey: CTRL+ALT+SHIFT J
[info] add hotkey: CTRL+ALT+SHIFT H
[info] add hotkey: CTRL+ALT+SHIFT K
[info] add hotkey: CTRL+ALT+SHIFT A
[info] add hotkey: CTRL+ALT+SHIFT Q
[info] add hotkey: CTRL+ALT+SHIFT X
Sikuli debug: in netFlixLaunch (O+11)
AutoITdebug: keys sent: C+A+S+O
AutoITdebug: newNFLaunchFlag set to: 0
Sikuli debug: loading movie
Sikuli debug: loaded movie
Sikuli debug: in goNextEpisode (N+11)
[log] CLICK on (512,384)
[log] CLICK on (164,713)
Sikuli debug: Click Next Episode result (Skip): 1
Sikuli debug: in netFlixLaunch (O+11)
Sikuli debug: loading movie
Sikuli debug: loaded movie
Sikuli debug: in toggleNetFlixFullScreen (F+11)
[log] CLICK on (512,384)
[log] CLICK on (883,677)
Sikuli debug: Click Full Screen result (manual toggle): 1
Sikuli debug: in goNextEpisode (N+11)
[log] CLICK on (512,384)
[log] CLICK on (958,747)
Sikuli debug: Click Exit Full Screen result: 1
[log] CLICK on (164,713)
Sikuli debug: Click Skip Episode result: 1
Sikuli debug: in netFlixLaunch (O+11)
Sikuli debug: loading movie
Sikuli debug: loaded movie
AutoITdebug: Received C+A+S+Q for Netflix termination
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: closed iexplore.exe
AutoITdebug: newNFLaunchFlag set to: 1


I did:

ctrl+alt+shift+n

ctrl+alt+shift+f

ctrl+alt+shift+n

ctrl+alt+shift+q

All with about 15 seconds between. The mount pointer will automatically go to the next button and click it, then return to the center of the screen. It never goes to click on full screen. When I do the ctrl+alt+shift+F it will go to the fullscreen button and click on it. I have a feeling we are getting close.

(2012-05-16 08:23)kevev Wrote:  All with about 15 seconds between. The mount pointer will automatically go to the next button and click it, then return to the center of the screen. It never goes to click on full screen. When I do the ctrl+alt+shift+F it will go to the fullscreen button and click on it. I have a feeling we are getting close.

Can you take a full screen screen shot (prt-screen) of your screen directly after the next episode starts (and you say the full screen isn't working)? Upload it somewhere in full size somewhere for me.

Also, try running Netflix in IE outside of XBMC. When running in debug mode you will see several red rectangles outlining the scan areas. These will only show when you are not in full screen (because Silverlight goes fully to the foreground). I want to know if the bottom rectangle covers your full screen button. If you can take a screen shot of the rectangles and post that too would be good.

thanks.

(2012-05-16 14:45)bengalih Wrote:  

(2012-05-16 08:23)kevev Wrote:  All with about 15 seconds between. The mount pointer will automatically go to the next button and click it, then return to the center of the screen. It never goes to click on full screen. When I do the ctrl+alt+shift+F it will go to the fullscreen button and click on it. I have a feeling we are getting close.

Can you take a full screen screen shot (prt-screen) of your screen directly after the next episode starts (and you say the full screen isn't working)? Upload it somewhere in full size somewhere for me.

Also, try running Netflix in IE outside of XBMC. When running in debug mode you will see several red rectangles outlining the scan areas. These will only show when you are not in full screen (because Silverlight goes fully to the foreground). I want to know if the bottom rectangle covers your full screen button. If you can take a screen shot of the rectangles and post that too would be good.

thanks.

The bottom rectangle does surround the fullscreen button. I will get the screen shot for you tonight and test via IE.

I've been looking over your log some more and there is one part that I'm just not sure about.

When i set my screen res to 1024x768 I get pretty much the same results that you get, with the exception that my Auto Full Screen works, so I have some additional data in my logs that reflects this. But, that aside, there is this bit of mystery. Let's compare logs:

Yours:


Mine


So, first, let's explain whats going on here.... This is CTRL+ALT+SHIFT+N to go to a new episode. It really doesn't matter if you run this from within Full Screen or not, since in order to show the next episode button, Netflix needs to be taken out of full screen...so after that things would continue the same. So let me comment on each line:

Sikuli debug: in goNextEpisode (N+11)
Basically shows that we received the hotkey command to advance the episode
[log] CLICK on (512,384)
Does a mouse click at the center of the screen (1024/2, 768/2). This is to bring the menu at the bottom of the screen up.
[log] CLICK on (958,747)
Does a mouse click on the Exit Full Screen Button. This is to put Netflix in non Full Screen so we can make the skip button visible. Since this shows in both our logs I can deduce that we were both in Full Screen mode when pressing the hotkey.
Sikuli debug: Click Exit Full Screen result: 1
Shows that the click is successful (as it will almost always be assuming the line above shows a click).
[log] CLICK on (97,628)
This is where it clicks on the skip button (little triangle) to advance an episode (more on this below...)
Sikuli debug: Click Skip Episode result: 1
Says that clicking the button was successful (again it should always be if the above Click line was present)
Sikuli debug: in netFlixLaunch (O+11)
This tells us that the netFlixLaunch routine was entered. Technically the "O" hotkey is not being sent by us, but automatically being sent by XBMCFoM because we advanced an episode, so it is telling itself a new episode was launched.
Sikuli debug: loading movie
This means it found the NETFLIX logo on the screen
Sikuli debug: loaded movie
This means the NETFLIX logo has disappeared (in other words, the movie is done loading)
[log] CLICK on (950,592)
Sikuli debug: Click Full Screen result (new launch): 1
These last two lines (which you are missing) shows that there was a click around the bottom right of the screen - which means that the Full Screen button was found and clicked on. Following the click is the confirmation of success.

So, obviously it would appear that your Full Screen Button isn't found. What I don't understand is your coordinates look off, and I don't understand why/how this can be if we are running at the same resolution. So I need your help to track it down. For example, when XBMCFoM clicks on the skip button, I get:

[log] CLICK on (97,628)

but you get...

[log] CLICK on (164,713)

Below is a screen shot of what this means. The red dot indicates where my triangle is (and where the click happens), the yellow dot indicates yours:



Additionally if you look at what we get when doing a manual fullscreen (CTRL+ALT+SHIFT+F), I get this:


You get:


Here is another pic to reflect that:



So it appears that your buttons are well below and inset from where mine are. Now they would appear to still fall within the red rectangle of the control bar zone, so I would think it would still be clicked...but something is definitely strange with this. I need to know why your buttons are appearing in different places as running with the same browser with the same resolution I would expect them to be in the same place. As I said, even out of place I still think they should be clicked as they are in the zone)....but this might help us track down a better clue.

If you have another machine to try this on, I would also suggest that (you can set it on 1024x768 to test). I will be trying it on another system of mine with 1024x768 as a double check. I also will try to post a video of my experience so you can compare it to yours in terms of button placement, etc...

UPDATE: Hmmm well ok, so I went back in the thread and grabbed a pick you posted and compared the two:


I think this has something to do with the fact that you must be using a 4:3 monitor and I am using a 16:9.
When I set my resolution to 1024x768 I get two big black bars on both sides of my screen to simulate a 4:3 ratio....

UPDATE: Never mind the last thing...I figured that out...it is because Sponge Bob is only streaming in 4:3 and all my tests have been with HD shows (like American Pickers in my examples above). I tested with Sponge Bob and i get the same view you do....so pretty much everything I said above about your coordinates being off should not matter.

I posted a video of me watching SpongeBob and using XBMCFoM. Everything works for me. In the video the only time I am moving the mouse on my own is to move the little recorder bar and then also to advance the video quickly to the end to test next episode.

At this point I really have no idea why this wouldn't be working for you....so I will need you to review all of the above data and make sure you understand how we are working and then think about anything you might have running or configured that could change any of this.

As I type this I am thinking that there may be one other possible reason and that is some sort of delay in checking for the Full Screen button. I timeout pretty quickly as it is CPU intensive to keep scanning for the buttons, but I'm wondering if this is your issue. Let me look at the logs and code again and if I think this may work I will adjust the timeouts and post a test version.

OK - so I suppose the timeout is a possible cause. I have created a test version for you to try.

Download here. All that is enclosed is the XBMCFlix-o-mate.sikuli folder, so just delete the existing one and replace with this.

I have added a new setting in the user variables called Settings.myButtonTimeout.
It is currently defaulting to 3 seconds, which should be more than enough (previously the value was one second).

If this doesn't do it, I really am at a bit of an impasse as to what it could be...

UPDATE: BTW I noticed that even in non-debug mode the mouse cursor is moving (as opposed to quickly jumping) to its click points. This will be fixed in the next release (hopefully tonight/tomorrow).

ThankYou for the quick response. I will test all of this tonight. I am using my 42" 720p TV. It supports 1024x768 as its native resolution according to its EDID.

(2012-05-16 19:45)kevev Wrote:  It supports 1024x768 as its native resolution.

ick

Hopefully you got that many years ago or on a real good deal. Not sure why anyone who wants to use a system primarily for video doesn't go with native 720 or 1080...but that's just me.

In any event, I can't see that in itself as an issue. Obviously the Full Screen image is able to be found (as is evident by the fact that manual CTRL+ALT+SHIFT+F works)...let's hope it is just the timing issue and the above tweak fixes it.

Ha! Ya, it was a clearanced display model. Got the warranty and already used it once. What can I say, I'm a cheap skate.