STVi Import: VideoOut Tools for the HD100/200

[razrsharpe]

This stvi plugin adds a popup menu to choose the new output resolution of the extender interactively (similar to the "Detailed Setup" > Multimedia > "Output Resolution" menu in the default STV). The menu is mapped to the "Video Out" remote button while in the media player. It also can display the current mediafile's resolution and the extenders output on the OSD (this can be disabled thru Video Tools Options).

It replaces the default behavior of the "Video Out" remote button while in the Media Player. In other portions of the UI the "Video Out" button is the default behavior (cycling through available resolutions).

To access Video Tools Options: press "Video Out" on the remote while in the media player and navigate to "Options".

Installation Instructions:
from the Sage V7 main menu on the server or extender go to Setup -> SageTV Plugins -> All Available Plugins -> UIMod -> VideoOut Tools for the HD100/200 -> Install Plugin

Note: This plugin is only really useful on an extender. (Yes you will still get the MediaFiles resolution on a PC Client).

This is a combination of 2 of my v6 STVi's (linked here only for reference to the previous work): VideoOut Popup (http://forums.sagetv.com/forums/downloads.php?do=file&id=294) and Display Resolution on the Timebar (http://forums.sagetv.com/forums/downloads.php?do=file&id=293)

Video Output Menu:
http://forums.sagetv.com/forums/attachment.php?attachmentid=10306&stc=1&d=1274493488

MediaFile Resolution:
http://forums.sagetv.com/forums/attachment.php?attachmentid=10307&stc=1&d=1274493488

Release Notes:
1.0.2
-updated razr-api min version to v0.1.2
-razr-api: fix resolution parsing and sorting algorithm to accept non integer (ie float/double) frame per second (FPS) values in the resolution description.
-razr-api: fix resolution parsing and sorting algorithm to accept and sort properly prepended text in the resolution description.

1.0.1
-Initial Release

[heffe2001]

I was just wondering if someone was going to do something like this, never can tell what I have my output set at (grandkids and sage remote don't mix, period, lol).

[razrsharpe]

:)

Eventually it will also do smart native output resolution switching by having a prioritized list of input resolutions (with ranges/wildcards) and what the output should be. I've started the framework for it but wanted to get the functionality that existed for v6 out there early on.

Oh and a BTW. Sage is now giving access to all the format properties (width, height, fps, i/p, container, video format, audio format, etc) through the extra metadata properties so this will actually be much more accurate in terms of the video resolution it supports

[CanadianEh]

This is awesome! Thanks for creating this.. it works great on my HD100!

[kmp14]

For some reason, I am not getting the output resolution choices. The menu pops up, but I don't get the list of selectable resolutions like I did in the 6x version. Any help would be appreciated!

[razrsharpe]

For some reason, I am not getting the output resolution choices. The menu pops up, but I don't get the list of selectable resolutions like I did in the 6x version. Any help would be appreciated!
Just to make sure some basic questions:
this is on a hd100/hd200?
if you navigate to Setup -> Detailed Setup -> Multimedia -> Output Resolution the list displays all the resolutions?

[Fuzzy]

so... any chance of making a PC client version that could launch an external command?

[stanger89]

Just curious, but does this disable the list/manual changes if Native Output Switching is enabled?

[razrsharpe]

so... any chance of making a PC client version that could launch an external command?
I've thought about that... and once (if/when) i build a client then the answer is in all probability yes... until then probably not because i don't really want to spend the time figuring out the intricacies of calling an external program, what to pass to it, how to generate the list of resolutions, etc0

Just curious, but does this disable the list/manual changes if Native Output Switching is enabled?
if i understand the question... No. I have native output switching enabled (to do most of the work)... but the list is still available and you can still change the resolution manually. My experience is that Native Output is only considered during playback start and stop, so any changes in the middle of playback are OK.

[kmp14]

Just to make sure some basic questions:
this is on a hd100/hd200?
if you navigate to Setup -> Detailed Setup -> Multimedia -> Output Resolution the list displays all the resolutions?

Yes, although I have a custom list. I was having some stutter problems, so sage gave me some custom resolutions to use, which solved the problem. Not sure if having custom choices is causing a problem? It worked fine in 6.x.

FYI- the name of one of the custom res starts with a letter, just in case that could be causing the problem?

[kmp14]

FYI- the name of one of the custom res starts with a letter, just in case that could be causing the problem?

I renamed the custom res so that it does not start with a letter, but still do not get the list. Here is what my custom res line looks like:

extender_resolution_extra_modes=1920x1080k@60|standard\=HDMI_1080i59;

[stanger89]

if i understand the question... No. I have native output switching enabled (to do most of the work)... but the list is still available and you can still change the resolution manually. My experience is that Native Output is only considered during playback start and stop, so any changes in the middle of playback are OK.

Oh, I know you can change it, I was just curious if you looked at that and didn't give the option to switch if it was enabled. Sounds like not, in which case, I think I have the same issue as kmp14.

[razrsharpe]

I renamed the custom res so that it does not start with a letter, but still do not get the list. Here is what my custom res line looks like:

extender_resolution_extra_modes=1920x1080k@60|standard\=HDMI_1080i59;
If you remove the custom res does it work?
Can you post a screen shot (from a camera) of the resolution options in detailed setup (with the custom res line) from the hd200?

k is a valid descriptor in that line? I thought only i and p were valid.

The resolution starting with a letter could be the problem... when i generate the list of resolutions i sort it with a custom comparator to make sure they are ordered correectly (ascending vertical resolution)... this is new in the v7 version... so perhaps that part is gagging... Can you enable debug logging on the hd200 and the server and then post (or email it to sagetve @ gmail . com) the sage_tv0.txt log file after starting the hd200 and displaying box? I assume/expect a specifically formatted resolution string so if it doesn't match the format i expect (WxH[ip]@FPS) then i can definitely see it gagging.

[kmp14]

Yeah, the K looks weird, but it is just the name, and works fine when selected via the multimedia res menu.

I completely removed the custom res line from the client properties file, but I still do not get any choices.



I must have something else weird going on.

Also, I can send a pic, but before I get a chance to that here is a description: THe dialog pops up, and is titled "Video Output Options", below that I see "Current Output:1920x1080i" and below that "Current Mediafile:720p@59.94", under that I have the Options and Close choices, but no list of resolutions.

Thanks for the help!

[kmp14]

Sorry, I have to do better at explaining, dont want to waste your time.

In regards the "k" instead of an i or p, if I name the custom res the same as a standard one (like 1920x1080i@60), the problem is that you will then see 2 with that name, the standard and custom, and there is no way to know which one is which. So I named it with a k instead of an i, just something to distinguish it. It does work fine when selected.

I have completely removed the custom res, but still do not get a list of choices. I will enable logging and get the log posted. Thanks again!

[razrsharpe]

Yeah, the K looks weird, but it is just the name, and works fine when selected via the multimedia res menu.
yup but i wonder if that is whats causing a problem because of my comparator that i use when i display the list... what happens if you change the k to a p?

I completely removed the custom res line from the client properties file, but I still do not get any choices.

Another weird thing, with the custom res line removed, when I go to Setup -> Detailed Setup -> Multimedia "Output Resolution" is NOT available as a choice.

I must have something else weird going on.
That's usually because it thinks there is only 1 valid output resolution... so therefore there is no reason to display the dialog box (since there isnt a choice)... you set up the resolution choices somewhere in standalone mode setup...


Also, I can send a pic, but before I get a chance to that here is a description: THe dialog pops up, and is titled "Video Output Options", below that I see "Current Output:1920x1080i" and below that "Current Mediafile:720p@59.94", under that I have the Options and Close choices, but no list of resolutions.
sorry i meant a pic of what the built in dialog looks like under detailed setup -> Multimedia -> Output resoltuion (with the custom resolution enabled)

[razrsharpe]

In regards the "k" instead of an i or p, if I name the custom res the same as a standard one (like 1920x1080i@60), the problem is that you will then see 2 with that name, the standard and custom, and there is no way to know which one is which.
can't you disable the standard one in standalone mode so its never a choice?

EDIT: assuming of course that you don't want it to be a choice

[razrsharpe]

one more thought:
if the built in dialog displays 1920x1080k@60 then that will definitely mess up the comparator because the string is not formatted like i expect... I do this string format checking because i thought it would be more robust when setting the resolution :) apparently that's not true :) so I need to rethink that piece of it to be able to still sort everything but handle non standard names.. and then probably just put the non standard names at the bottom of the list....

Stanger,
by chance do you have a custom output resolution that has a funky (non-standard) name?

[stanger89]

Not really, I think all I've got is a 480i and a 1080p24 defined, I'd have to look at my list and check my debug logs later.

[stanger89]

so... any chance of making a PC client version that could launch an external command?

FWIW, reclock can do that too.

[kmp14]

can't you disable the standard one in standalone mode so its never a choice?

EDIT: assuming of course that you don't want it to be a choice

Good idea. I will try that.

But, WITHOUT my custom, it is now working! Not sure why. I had to restart the Sage service to enable debugging, maybe that did it? Regardless, it works, so now I can start experimenting with the custom res. I will post what I find. Thanks!

[razrsharpe]

But, WITHOUT my custom, it is now working! Not sure why. I had to restart the Sage service to enable debugging, maybe that did it? Regardless, it works, so now I can start experimenting with the custom res. I will post what I find. Thanks!
ya restarting the service probably did it... even though you deleted the custom resolution it was probably still active if you you didnt do it with the service disabled... its the old you need to stop the service to modify property files nonsense :)

[kmp14]

So here is the latest.

I Shut down and unplugged the HD200
Shut down Sage service
Started hd200 and removed 1080i res as an option
Shutdown HD200 again and unplugged
Added custom res to clients file: extender_resolution_extra_modes=1920x1080i@60|standard\=HDMI_1080i59; Notice the "i" instead of "k" - looks ok to me.
Started sage service
started HD200
Played a recording, hit "Video Out" -- Did not work, did NOT get a list of resolutions. :(


Maybe the code is having a problem with custom res's in general? It seems that if I add a custom res at all, the pop-up does not give me a list.

Again, I can't say again how much I appreciate the help. You rock!

[razrsharpe]

Maybe the code is having a problem with custom res's in general? It seems that if I add a custom res at all, the pop-up does not give me a list.
I know it works with at least some custom resolutions... I have 1080p24 working so i know that works...

here is what my custom resolution line looks like
extender_resolution_extra_modes=1920x1080p@24|standard\=HDMI_1080p24

EDIT: What happens if you remove the trailing ; in the line... i just noticed that that is different between yours and mine... maybe its creating a "blank" resolution at that point (and my comparator fails)...

[kmp14]

You are right on - the trailing ; was causing a blank one. Now, all is good. The only thing I have not tried is adding the custom res with another letter in it so I can still have the original 1920x1080...but for now, we are good.

I am going to try the "other letter" option. I will let you know.

[kmp14]

Adding any character to the beginning of a custom res results in the plugin not showing any.

Adding a character other then the expected anywhere else in the custom res name results in the res being shown OK by the plugin, but when I select it, the HD200 hangs and the TV indicates nothing is connected, and I need to unplug the HD200.

So I guess with Sage7 the res names have to be standard. Probably more troubleshooting can be done, but for now, i have my custom res working and selectable from the plugin. Thanks again.

[razrsharpe]

:) glad its working (mostly :) )

what happens when you have letters in the name and use the built-in selector (in detailed setup)? That would tell us if it is sage's problem or something do with how i am presenting and setting the resolution... I pretty much just copied the built-in dialog when i first created this plugin (it's a little different now but the basics are the same) so i would expect that to fail too... Anyway if you want to do some more trouble shooting i would be curious how it works when using the built-in selector

[Fuzzy]

FWIW, reclock can do that too.

Yeah, I know.. and I used to use it.. however, for some reason, a couple of my local channels have pretty crappy flags, switching between film and video often, meaning ReClock is routinely switching between 24 and 60hz. so i had to disable that. I currently have a remote button configured to switch between 24 and 60, but would like to be able to do that onscreen.

[kmp14]

:) glad its working (mostly :) )

what happens when you have letters in the name and use the built-in selector (in detailed setup)? That would tell us if it is sage's problem or something do with how i am presenting and setting the resolution... I pretty much just copied the built-in dialog when i first created this plugin (it's a little different now but the basics are the same) so i would expect that to fail too... Anyway if you want to do some more trouble shooting i would be curious how it works when using the built-in selector

Razr,

Sorry for the delay in answering your question.

When selecting a "bad" custom res (like naming it with a "k" instead of an "i"), it crashes the HD200 even when using the built-in selector, so it is not your plugin causing the crash.

As far as naming a custom res with something at the beginning, like:

Test1920x1080i@60|standard=HDMI_1080i59;

As we have discovered, that results in the plugin not showing any resolutions.

I went through the emails I got from SageTV support, and found the one where they recommend a custom resolution for a problem I was having, and they specifically say to name it "Test1920x1080i@60|standard=HDMI_1080i59;", so hopefully you can get the plugin to handle res names like that, since it appears to be a SageTV sanctioned naming practice to prepend some text.

This is a bit off topic, but I have to vent: Here is the really bad news. The reason I use the custom res is because without it, I get "micro-stutter" when watching live or recorded TV. That custom res fixes it 100% in SageTV 6 with the current official firmware. Unfortunately, with Sage7 and the latest Beta firmware, the micro-stutter is back, even with the custom res selected. I don't know if it is the firmware or SageTV 7, but man, how disappointing! I spent WEEKS working with them on it, until finally they recommended the custom res. I otherwise loved SageTV 7, but that micro-stutter is unacceptable. I have reverted back SageTV 6. :(

Here is the really weird part about the micro-stutter - I get that stutter on 3 different HD200s on 3 different brands of TVs (Samsung, Sony, Panasonic) when not using the custom res. Why doesn't everyone have the micro-stutter???????? It is not the PC (I tried several), it is not the network (I tried several switches and routers), etc, etc, etc.....

[razrsharpe]

When selecting a "bad" custom res (like naming it with a "k" instead of an "i"), it crashes the HD200 even when using the built-in selector, so it is not your plugin causing the crash.
good to know :)


I went through the emails I got from SageTV support, and found the one where they recommend a custom resolution for a problem I was having, and they specifically say to name it "Test1920x1080i@60|standard=HDMI_1080i59;", so hopefully you can get the plugin to handle res names like that, since it appears to be a SageTV sanctioned naming practice to prepend some text.
and just to make sure i understand... a resolution with prepended text does work using the built-in selector?

I'll get the code modified to gracefully accept prepended text (but still require a "good" resolution descriptor after any text that exists).


This is a bit off topic, but I have to vent: Here is the really bad news. The reason I use the custom res is because without it, I get "micro-stutter" when watching live or recorded TV. That custom res fixes it 100% in SageTV 6 with the current official firmware. Unfortunately, with Sage7 and the latest Beta firmware, the micro-stutter is back, even with the custom res selected. I don't know if it is the firmware or SageTV 7, but man, how disappointing! I spent WEEKS working with them on it, until finally they recommended the custom res. I otherwise loved SageTV 7, but that micro-stutter is unacceptable. I have reverted back SageTV 6. :(

Here is the really weird part about the micro-stutter - I get that stutter on 3 different HD200s on 3 different brands of TVs (Samsung, Sony, Panasonic) when not using the custom res. Why doesn't everyone have the micro-stutter???????? It is not the PC (I tried several), it is not the network (I tried several switches and routers), etc, etc, etc.....
i get some microstutter here and there but have always been too lazy (and busy) to really spend any time with it and track it down.... have you brought up it behaving different in sage7 vs sage6 with support? I would think they should be the same because its the same firmware with both versions...and the firmware is responsible for playback.....

[kmp14]

and just to make sure i understand... a resolution with prepended text does work using the built-in selector?



Yes, works fine with the built in selector


i get some microstutter here and there but have always been too lazy (and busy) to really spend any time with it and track it down.... have you brought up it behaving different in sage7 vs sage6 with support? I would think they should be the same because its the same firmware with both versions...and the firmware is responsible for playback.....

I did let them know I was having the problem again. More testing needed....

[kmp14]

sorry to hijack this thread with stutter discussion, but since we have been discussing it here, just though I would post my latest discovery:


Some good news. it appears that with the latest BETA version of the HD200 firmware, when using SageTV 6 (NOT 7), I don't see any stutter with the HD200, and I DON'T even need to use a custom resolution!

Unfortunately, when using SageTV 7, I get micro-stutter REGARDLESS of which resolution I use. In other words, SageTV 7 seems to introduce micro-stutter into the HD200 that even a custom resolution could not fix it (even though it used to).

I sent SageTV support this info too. I really like v7, but I am really sensitive to the stutter (drives me nuts) so for now I am back to v6. Hopefully this is something they know how to fix, and get it fixed.

[adamwh]

I know it works with at least some custom resolutions... I have 1080p24 working so i know that works...

here is what my custom resolution line looks like
extender_resolution_extra_modes=1920x1080p@24|standard\=HDMI_1080p24



This used to work for me, but I use it rarely and at some point it stopped giving me a list of resolutions. I only use the same exact custom resolution above. If I remove it, I get a list, but nothing when I put it back. Switching to the custom resolution in the settings menu is fine (and cumbersome!). I'm on the latest beta software, firmware, and STV.

[razrsharpe]

This used to work for me, but I use it rarely and at some point it stopped giving me a list of resolutions. I only use the same exact custom resolution above. If I remove it, I get a list, but nothing when I put it back. Switching to the custom resolution in the settings menu is fine (and cumbersome!). I'm on the latest beta software, firmware, and STV.
ya i don't use it that often either and at some point recently i noticed it was broken for me as well... no list error... I just need to find some time and debug what the issue is and issue a fix for it... hopefully I'll have time sometime in the next week or so

[razrsharpe]

New version in the repository (v0.1.2)

fixes two critical bugs that completely broke this plugin. It should be working for all accepted resolution descriptors (that I'm aware). Sorry this has taken forever for me to fix... life has just been really busy lately. Let me know if you have any issues.

Release Notes:
1.0.2
-updated razr-api min version to v0.1.2
-razr-api: fix resolution parsing and sorting algorithm to accept non integer (ie float/double) frame per second (FPS) values in the resolution description.
-razr-api: fix resolution parsing and sorting algorithm to accept and sort properly prepended text in the resolution description.

[drewg]

Hi,

I was experimenting with Native output switching on my HD300. Before this, the video out tools always gave me a menu with resolutions to choose from.
As part of playing with Native output switching, I mapped 480i to 480p since my TV does not support 480i via HDMI. Eg:

extender_resolution_extra_modes=720x480i@60|standard\=HDMI_480p60


Native output switching proved to be too unstable, so I eventually disabled it. But after this, the video out tools no longer lets me choose resolutions. I think it is due to the line above. Is this expected, or a bug?

Thanks,

Drew

[razrsharpe]

[quote=drewg;516122Native output switching proved to be too unstable, so I eventually disabled it. But after this, the video out tools no longer lets me choose resolutions. I think it is due to the line above. Is this expected, or a bug?[/quote]
Pretty sure it's a bug and probably related to how i parse the resolution... but i thought i fixed the parsing problems with the last release... I'll need to dig up the old source code and see if i can see anything. It would also be helpful to see your sagetv debug log (enable debug logging, restart the service, connect the hdxxx, reproduce the problem and then post the log) to see what it is gagging on.

[drewg]

I had debug logging enabled last night when I was playing with it, but the logs are a bit huge. Can you give me an idea what you're looking for? Just looking in the logs for "VideoOut", I see the following scary stuff when re-loading the gui after re-installing the plugin:


Tue 9/20 23:51:23.411 [EventRouter-0023a5000235@17333cc] Processing STV import: /home/sagetv/server/STVs/SageTV7/VideoOutTools_v1.0.2.stvi
Tue 9/20 23:51:24.000 [AWTThreadWatcher-0023a5000235@f64d0f] EventThread-0023a5000235 Hang Detected - hang time = 4594
Tue 9/20 23:51:24.011 [EventRouter-0023a5000235@17333cc] Module processing STVImported Hook
Tue 9/20 23:51:24.011 [EventRouter-0023a5000235@17333cc] PATCH ERROR Missing Widget - Symbol=BASE-51092 "Video Out Options" could not add as child; parent symbol=MAZON-2202596 "MediaFileOptionsButtonTheme 3"
Tue 9/20 23:51:24.013 [EventRouter-0023a5000235@17333cc] PATCH ERROR Missing Widget - Symbol=BASE-86358 "OSDToolsMedWidthOptionsTheme" could not add as child; parent symbol=WABNM-50074 "BeforeMenuLoad"
Tue 9/20 23:51:24.013 [EventRouter-0023a5000235@17333cc] PATCH ERROR Missing Widget - Symbol=BASE-86359 "OSDToolsMedWidthOptionsTheme" could not add as child; parent symbol=WABNM-50074 "BeforeMenuUnload"
Tue 9/20 23:51:24.013 [EventRouter-0023a5000235@17333cc] PATCH ERROR Missing Widget - Symbol=OPUS4A-75 "OSDToolsMedWidthOptionsTheme" could not add as child; parent symbol=WABNM-50074 "AfterMenuLoad"
Tue 9/20 23:51:24.013 [EventRouter-0023a5000235@17333cc] PATCH ERROR Missing Widget - Symbol=BASE-47399 "DialogOpenAnimName = "OutpuResolutionPopupMenu"" could not add as child; parent symbol=MAZON-2202591 ""REM Animate the dialog opening, if should do so.""
Tue 9/20 23:51:24.013 [EventRouter-0023a5000235@17333cc] PATCH ERROR Missing Widget - Symbol=BASE-47408 "DialogCloseAnimName = "OutputResolutionPopupMenu"" could not add as child; parent symbol=MAZON-2202593 ""REM Animate the dialog closing, if should do so.""
Tue 9/20 23:51:24.013 [EventRouter-0023a5000235@17333cc] Auto-cleanup of STVImported hook is running...



Drew

[razrsharpe]

I had debug logging enabled last night when I was playing with it, but the logs are a bit huge. Can you give me an idea what you're looking for? Just looking in the logs for "VideoOut", I see the following scary stuff when re-loading the gui after re-installing the plugin:


Tue 9/20 23:51:23.411 [EventRouter-0023a5000235@17333cc] Processing STV import: /home/sagetv/server/STVs/SageTV7/VideoOutTools_v1.0.2.stvi
Tue 9/20 23:51:24.000 [AWTThreadWatcher-0023a5000235@f64d0f] EventThread-0023a5000235 Hang Detected - hang time = 4594
Tue 9/20 23:51:24.011 [EventRouter-0023a5000235@17333cc] Module processing STVImported Hook
Tue 9/20 23:51:24.011 [EventRouter-0023a5000235@17333cc] PATCH ERROR Missing Widget - Symbol=BASE-51092 "Video Out Options" could not add as child; parent symbol=MAZON-2202596 "MediaFileOptionsButtonTheme 3"
Tue 9/20 23:51:24.013 [EventRouter-0023a5000235@17333cc] PATCH ERROR Missing Widget - Symbol=BASE-86358 "OSDToolsMedWidthOptionsTheme" could not add as child; parent symbol=WABNM-50074 "BeforeMenuLoad"
Tue 9/20 23:51:24.013 [EventRouter-0023a5000235@17333cc] PATCH ERROR Missing Widget - Symbol=BASE-86359 "OSDToolsMedWidthOptionsTheme" could not add as child; parent symbol=WABNM-50074 "BeforeMenuUnload"
Tue 9/20 23:51:24.013 [EventRouter-0023a5000235@17333cc] PATCH ERROR Missing Widget - Symbol=OPUS4A-75 "OSDToolsMedWidthOptionsTheme" could not add as child; parent symbol=WABNM-50074 "AfterMenuLoad"
Tue 9/20 23:51:24.013 [EventRouter-0023a5000235@17333cc] PATCH ERROR Missing Widget - Symbol=BASE-47399 "DialogOpenAnimName = "OutpuResolutionPopupMenu"" could not add as child; parent symbol=MAZON-2202591 ""REM Animate the dialog opening, if should do so.""
Tue 9/20 23:51:24.013 [EventRouter-0023a5000235@17333cc] PATCH ERROR Missing Widget - Symbol=BASE-47408 "DialogCloseAnimName = "OutputResolutionPopupMenu"" could not add as child; parent symbol=MAZON-2202593 ""REM Animate the dialog closing, if should do so.""
Tue 9/20 23:51:24.013 [EventRouter-0023a5000235@17333cc] Auto-cleanup of STVImported hook is running...

Drew
Those refer to errors when the stvi is imported to the base stv at runtime. There should not be any patch errors, it means the stvi is not importing correctly into the base stv. this either comes from an incompatibility with the base stv (ie sage updated it since i updated videoouttools and a reference that videououttools uses is no longer there) or a plugin conflict creates the same type of reference error (ie diamond perhaps.. if you have that installed).

try searching the log for razr or razr_ too... that "should" (iirc) get you to the part where you try to display the list.

[drewg]

No, no Diamond (I'm a low-glitz kind of guy). When I search for razr, I see all kinds of stack traces, etc.


Tue 9/20 23:52:31.060 [AsyncWatch@1275229] EXCEPTION in getValueAsObject:sage.a.e: Error in method reflection of razr_mf_format_ResolutionFull of java.lang.reflect.InvocationTargetException for:razr_mf_format_ResolutionFull(mf)
Tue 9/20 23:52:31.060 [AsyncWatch@1275229] sage.a.e: Error in method reflection of razr_mf_format_ResolutionFull of java.lang.reflect.InvocationTargetException
Tue 9/20 23:52:31.060 [AsyncWatch@1275229] at sage.e$e.a(Unknown Source)
Tue 9/20 23:52:31.060 [AsyncWatch@1275229] at sage.a.m$b.a(Unknown Source)
Tue 9/20 23:52:31.060 [AsyncWatch@1275229] at sage.a.m.a(Unknown Source)
Tue 9/20 23:52:31.060 [AsyncWatch@1275229] at sage.e.a(Unknown Source)
Tue 9/20 23:52:31.060 [AsyncWatch@1275229] at sage.be.a(Unknown Source)
Tue 9/20 23:52:31.060 [AsyncWatch@1275229] at sage.be.do(Unknown Source)
Tue 9/20 23:52:31.060 [AsyncWatch@1275229] at sage.be.new(Unknown Source)
Tue 9/20 23:52:31.060 [AsyncWatch@1275229] at sage.be.int(Unknown Source)
Tue 9/20 23:52:31.060 [AsyncWatch@1275229] at sage.be.new(Unknown Source)
Tue 9/20 23:52:31.060 [AsyncWatch@1275229] at sage.be.int(Unknown Source)
Tue 9/20 23:52:31.060 [AsyncWatch@1275229] at sage.be.new(Unknown Source)
Tue 9/20 23:52:31.060 [AsyncWatch@1275229] at sage.be.int(Unknown Source)
Tue 9/20 23:52:31.061 [AsyncWatch@1275229] at sage.be.new(Unknown Source)
Tue 9/20 23:52:31.061 [AsyncWatch@1275229] at sage.be.int(Unknown Source)
Tue 9/20 23:52:31.061 [AsyncWatch@1275229] at sage.be.new(Unknown Source)
Tue 9/20 23:52:31.061 [AsyncWatch@1275229] at sage.be.int(Unknown Source)
Tue 9/20 23:52:31.061 [AsyncWatch@1275229] at sage.be.new(Unknown Source)
Tue 9/20 23:52:31.061 [AsyncWatch@1275229] at sage.be.int(Unknown Source)
Tue 9/20 23:52:31.061 [AsyncWatch@1275229] at sage.be.new(Unknown Source)
Tue 9/20 23:52:31.061 [AsyncWatch@1275229] at sage.be.int(Unknown Source)
Tue 9/20 23:52:31.061 [AsyncWatch@1275229] at sage.cb.ah(Unknown Source)
Tue 9/20 23:52:31.061 [AsyncWatch@1275229] at sage.UIManager.a(Unknown Source)
Tue 9/20 23:52:31.061 [AsyncWatch@1275229] at sage.UIManager.a(Unknown Source)
Tue 9/20 23:52:31.061 [AsyncWatch@1275229] at sage.UIManager.if(Unknown Source)
Tue 9/20 23:52:31.061 [AsyncWatch@1275229] at sage.be.a(Unknown Source)
Tue 9/20 23:52:31.061 [AsyncWatch@1275229] at sage.be.a(Unknown Source)
Tue 9/20 23:52:31.061 [AsyncWatch@1275229] at sage.e$c.a(Unknown Source)
Tue 9/20 23:52:31.061 [AsyncWatch@1275229] at sage.e.try(Unknown Source)
Tue 9/20 23:52:31.061 [AsyncWatch@1275229] at sage.d.s$23$1.run(Unknown Source)
Tue 9/20 23:52:31.061 [AsyncWatch@1275229] at sage.cz$a.run(Unknown Source)
Tue 9/20 23:52:31.063 [AsyncWatch@1275229] Caused by: java.lang.reflect.InvocationTargetException
Tue 9/20 23:52:31.063 [AsyncWatch@1275229] at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
Tue 9/20 23:52:31.063 [AsyncWatch@1275229] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
Tue 9/20 23:52:31.064 [AsyncWatch@1275229] at java.lang.reflect.Method.invoke(Unknown Source)
Tue 9/20 23:52:31.064 [AsyncWatch@1275229] ... 30 more
Tue 9/20 23:52:31.064 [AsyncWatch@1275229] Caused by: java.lang.NumberFormatException: empty String
Tue 9/20 23:52:31.064 [AsyncWatch@1275229] at sun.misc.FloatingDecimal.readJavaFormatString(Unknown Source)
Tue 9/20 23:52:31.064 [AsyncWatch@1275229] at java.lang.Double.valueOf(Unknown Source)
Tue 9/20 23:52:31.064 [AsyncWatch@1275229] at razr.mf.format.Fps(format.java:46)
Tue 9/20 23:52:31.064 [AsyncWatch@1275229] at razr.mf.format.ResolutionFull(format.java:20)
Tue 9/20 23:52:31.064 [AsyncWatch@1275229] ... 33 more
Tue 9/20 23:52:31.065 [AsyncWatch@1275229] java.lang.reflect.InvocationTargetException
Tue 9/20 23:52:31.065 [AsyncWatch@1275229] sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
Tue 9/20 23:52:31.065 [AsyncWatch@1275229] sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
Tue 9/20 23:52:31.065 [AsyncWatch@1275229] java.lang.reflect.Method.invoke(Unknown Source)
Tue 9/20 23:52:31.065 [AsyncWatch@1275229] sage.e$e.a(Unknown Source)
Tue 9/20 23:52:31.065 [AsyncWatch@1275229] sage.a.m$b.a(Unknown Source)
Tue 9/20 23:52:31.065 [AsyncWatch@1275229] sage.a.m.a(Unknown Source)
Tue 9/20 23:52:31.065 [AsyncWatch@1275229] sage.e.a(Unknown Source)
Tue 9/20 23:52:31.065 [AsyncWatch@1275229] sage.be.a(Unknown Source)
Tue 9/20 23:52:31.065 [AsyncWatch@1275229] sage.be.do(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.be.new(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.be.int(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.be.new(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.be.int(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.be.new(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.be.int(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.be.new(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.be.int(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.be.new(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.be.int(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.be.new(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.be.int(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.be.new(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.be.int(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.cb.ah(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.UIManager.a(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.UIManager.a(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.UIManager.if(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.be.a(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.be.a(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.e$c.a(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.e.try(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.d.s$23$1.run(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sage.cz$a.run(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] java.lang.NumberFormatException: empty String
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] sun.misc.FloatingDecimal.readJavaFormatString(Unknown Source)
Tue 9/20 23:52:31.066 [AsyncWatch@1275229] java.lang.Double.valueOf(Unknown Source)
Tue 9/20 23:52:31.067 [AsyncWatch@1275229] razr.mf.format.Fps(format.java:46)
Tue 9/20 23:52:31.067 [AsyncWatch@1275229] razr.mf.format.ResolutionFull(format.java:20)
Tue 9/20 23:52:31.067 [AsyncWatch@1275229] sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
Tue 9/20 23:52:31.067 [AsyncWatch@1275229] sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
Tue 9/20 23:52:31.067 [AsyncWatch@1275229] java.lang.reflect.Method.invoke(Unknown Source)
Tue 9/20 23:52:31.067 [AsyncWatch@1275229] sage.e$e.a(Unknown Source)
Tue 9/20 23:52:31.067 [AsyncWatch@1275229] sage.a.m$b.a(Unknown Source)
Tue 9/20 23:52:31.067 [AsyncWatch@1275229] sage.a.m.a(Unknown Source)
Tue 9/20 23:52:31.067 [AsyncWatch@1275229] sage.e.a(Unknown Source)
Tue 9/20 23:52:31.067 [AsyncWatch@1275229] sage.be.a(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.be.do(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.be.new(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.be.int(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.be.new(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.be.int(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.be.new(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.be.int(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.be.new(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.be.int(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.be.new(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.be.int(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.be.new(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.be.int(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.be.new(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.be.int(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.cb.ah(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.UIManager.a(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.UIManager.a(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.UIManager.if(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.be.a(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.be.a(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.e$c.a(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.e.try(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.d.s$23$1.run(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.cz$a.run(Unknown Source)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] EXCEPTION in getValueAsObject:sage.a.e: Error in method reflection of razr_mf_format_ResolutionFull of java.lang.reflect.InvocationTargetException for:razr_mf_format_ResolutionFull(mf)
Tue 9/20 23:52:31.068 [AsyncWatch@1275229] sage.a.e: Error in method reflection of razr_mf_format_ResolutionFull of java.lang.reflect.InvocationTargetException
<....>


Are you running 7.1.9 with the latest STV update applied?

Thanks,

Drew

[razrsharpe]

No, no Diamond (I'm a low-glitz kind of guy). When I search for razr, I see all kinds of stack traces, etc.


Tue 9/20 23:52:31.060 [AsyncWatch@1275229] EXCEPTION in getValueAsObject:sage.a.e: Error in method reflection of razr_mf_format_ResolutionFull of java.lang.reflect.InvocationTargetException for:razr_mf_format_ResolutionFull(mf)
<....>
Are you running 7.1.9 with the latest STV update applied?

Thanks,

Drew
yup that method does the parsing of the resolution... so it is gagging somewhere in that code. I will need to turn some internal logging on and take a look at it.

yes 7.1.9, no to the latest stv update, and i hardly ever use video out tools anymore so that's probably why I havent noticed it...

I'll make some time and dive back into this... its probably something simple that i am over looking... Can you post a screenshot of what the default list looks like for choosing the output resolution (accessible from detailed setup somewhere)?

[drewg]

I'll make some time and dive back into this... its probably something simple that i am over looking... Can you post a screenshot of what the default list looks like for choosing the output resolution (accessible from detailed setup somewhere)?

Thanks for looking at this. I'm sorry, but I don't have a camera handy.
There is a list like:
720x480p@59.94
1280x720p@59.94
1920x1080p@23.976
1920x1080i@29.94
1920x1080p@59.94
720x480i@60

I think the last one is the custom resolution mapping..

Drew

[razrsharpe]

Thanks for looking at this. I'm sorry, but I don't have a camera handy.
There is a list like:
720x480p@59.94
1280x720p@59.94
1920x1080p@23.976
1920x1080i@29.94
1920x1080p@59.94
720x480i@60

I think the last one is the custom resolution mapping..

Drew
no worries that's the info i wanted. Nothing looks amiss so not sure why its gagging but I'll dig into it and see if i can see anything. and it could be somehting with the custom resolution mapping to 480p that is messing up the logic somewhere.. I'll look into it

[drewg]

no worries that's the info i wanted. Nothing looks amiss so not sure why its gagging but I'll dig into it and see if i can see anything. and it could be somehting with the custom resolution mapping to 480p that is messing up the logic somewhere.. I'll look into it

So.. I think I figured it out. It wasn't the custom resolution. It was the fact that I upgraded to 7.1.9 without un-installing the IMDB plugin.

Last night, I was watching Fringe 45 minutes behind, and went to IMDB somebody. The sagetv extender froze, and after rebooting it, I realized that the server (java app) froze too. After I restarted it (and missed the critical bits of the show), I went to check for an update to IMDB, and I saw that it was marked as not compatible, so I removed it (and a few others that were marked as incompatible). Flash forward to tonight, and I realized that the video out options menu was back & working just fine. So my theory is that it was the "incompatible" IMDB extension that was the problem. I wish SageTV would have disabled or uninstalled incompatible extensions...

Sorry to waste your time!

Drew

[wildgoose]

I've been using the "VideoOut Tools for Extenders" on my Sage HD300 for a while now. Very useful to be able to explicitly select a resolution for a given video.

One persistent problem I've been having lately is, for some reason, the feature doesn't get triggered when I press the video-out button when playing back a video. I get the standard Sage menu for "close" and "option", not the menu from the Plugin where I get to select the output resolution.

I am running SageTV V7 on Windows 7. It was working fine for the last few month (I forgot how I made it working again last time, probably uninstall/re-install), but a few days ago after I restarted Sage on my PC, it no longer works.

It's interesting because for the few month that it did work, my computer's been restarted quite a few times, so a restart does not necessarily disable it.

Is this a known problem? Is there a workaround other than uninstall/reinstall?

Thanks!

[razrsharpe]

I've been using the "VideoOut Tools for Extenders" on my Sage HD300 for a while now. Very useful to be able to explicitly select a resolution for a given video.

One persistent problem I've been having lately is, for some reason, the feature doesn't get triggered when I press the video-out button when playing back a video. I get the standard Sage menu for "close" and "option", not the menu from the Plugin where I get to select the output resolution.

I am running SageTV V7 on Windows 7. It was working fine for the last few month (I forgot how I made it working again last time, probably uninstall/re-install), but a few days ago after I restarted Sage on my PC, it no longer works.

It's interesting because for the few month that it did work, my computer's been restarted quite a few times, so a restart does not necessarily disable it.

Is this a known problem? Is there a workaround other than uninstall/reinstall?

Thanks!
It is still working for me (I just checked with a BD and recorded tv episode). I'm using Diamond. Did you update/install any new plugins? Can you post a screenshot/picture of what the menu looks like? Are the different output resolutions available via the standard menu (Setup -> Detailed Setup -> Multimedia -> Output Resolution... going from memory...)?

EDIT: Can you also restart sage, connect an extender, reproduce the problem and then send me the sagetv_0.txt log from the server?

[wildgoose]

It is still working for me (I just checked with a BD and recorded tv episode). I'm using Diamond. Did you update/install any new plugins? Can you post a screenshot/picture of what the menu looks like? Are the different output resolutions available via the standard menu (Setup -> Detailed Setup -> Multimedia -> Output Resolution... going from memory...)?

EDIT: Can you also restart sage, connect an extender, reproduce the problem and then send me the sagetv_0.txt log from the server?

Oh great. I restarted my SageTV server, connected my extender, and now it works. All the resolution shows up. Not sure what happened.

VideoOut is the only plugin I've installed.

My "Installed Plugins" setting, under "All", show the following

* Google Weather (1.0.6)
* razr API (0.1.2 Beta)
* sagex-api (7.1.9.10)
* VideoOut Tools (1.0.2 Beta)

Where do I find this sagetv_0.txt file? In this dir, I have:

D:\Program Files (x86)\SageTV\SageTV


6/18/2012 11:11 0 ___A__________ DebugTrace.log
9/23/2012 22:45 0 ___A__________ sagetvmsgs.log
6/18/2012 12:02 53,929 ___A__________ StmDeMux.log
9/28/2012 21:56 1,282 ___A__________ tv.sage.mod.0.log

Thanks!

Edit: It just happened again after I needed to restart Sage server this evening. Here's the screenshot of what I get when I press video:

https://lh4.googleusercontent.com/-4GVtTgLLYMg/UGk5iIxSmWI/AAAAAAAAQCI/-1yVuq-Hhrs/s1024/20120930_223224_5596_iphone4.JPG

This is how it looks like when it was working yesterday before the restart:

https://lh4.googleusercontent.com/-zGG1zvoC1Dk/UGk5hjdsZCI/AAAAAAAAQCE/yFpwnnqua4Y/s1024/20120929_161249_0_galaxys3.jpg

Perhaps it was not able to query the list of supported resolution? I cannot find this sagetv_0.txt log on my Sage directory in my Windows machine.

[razrsharpe]

Enable Sagetv debugging (option under setup -> Detailed Setup -> Advanced, requires restart) to generate the sagetv_0.log file.

The screenshot of the empty menu (like you are showing) is what happens when it can't generate the list of available resolutions for some reason (I parse the available resolutions so that i can sort them correctly... perhaps this is failing and returning an empty array). My hope is there is an exception written out in the log and with that i should be able to tell you where and perhaps even why it is failing.

[wildgoose]

I enabled logging, but unfortunately unable to reproduce it this morning.

I restarted SageTV server several times, and restarted my HD300 several times as well. But the context menu shows up correctly with the video resolutions.

My theory is it might be related to the sequence of how various devices are powered on. My Sage is connected to my Denon HDMI receiver, which is connected to my Panasonic TV. If everything works as expected, when I power on the Sage, it is able to query the resolution data from the receiver/TV, and everything is fine.

But if for some reason, this information is not available when Sage is doing its query, then it'll be empty. Though I have yet to find a power on sequence that does this today. I tried the following

1) start sage tv server
2) turn on tv
3) turn on receiver
4) turn on sagetv HD300

This worked. Then I tried the following:

1) start sagetv server
2) start sage HD300

at this point, the HD300 should not be able to get any resolution info, since both the receiver/tv is off. I then

3) turn on the TV
4) turn on the receiver

but it also worked. So the theory is probably not sound. (there is one more sequence I'll try tonight, turn on the Sage while the receiver is in a different input mode, like DVD..)

The thing that puzzles me a bit is, when it is not working, it won't work even if I use the first power on sequence above (it's what I typically do, except SageTV server is already up so it's not restarted) So it feels like it won't work unless I go and restart the SageTV server (which I don't do very often). But why would that be the case? Whether the HD300 is able to get the resolution list from TV/receiver should not depend on what the state of the sagetv server is correct?

Debug logging is on now, so if it does happen again, I will have the corresponding logs. I hope the logging don't interfere with my recording.. It's a busy week with lots of shows I want to record. ;)

Q1: when does Sage HD300 query for the list of resolutions? on startup, or on demand as needed? When the problem does occur, would turn off/on the HD300 refresh this data?

q2: when I press the video button, does the plugin gets the cached resolution info? (from the SageTV server or from itself?) or does it query the TV at that point?

[razrsharpe]

My theory is it might be related to the sequence of how various devices are powered on.
I suppose that's possible but i doubt it. I believe the methods i use to generate the list of available resolutions (see below) is merely returning a combination of the resolutions that are enabled in the standalone setup mode plus any custom resolutions that are defined in the properties file for that extender... so i doubt it has anything to do with what order things are turned on.
Q1: when does Sage HD300 query for the list of resolutions? on startup, or on demand as needed? When the problem does occur, would turn off/on the HD300 refresh this data?I use the sage api methods GetDisplayResolutionOptions(), (http://download.sage.tv/api/sage/api/Global.html#GetDisplayResolutionOptions%28%29) GetDisplayResolution() (http://download.sage.tv/api/sage/api/Global.html#GetDisplayResolution%28%29) and SetDisplayResolution() (http://download.sage.tv/api/sage/api/Global.html#SetDisplayResolution%28java.lang.String%29) to generate the list, get the current resolution, and set the new resolution. See above but the short answer is i believe its just returning property items.

q2: when I press the video button, does the plugin gets the cached resolution info? (from the SageTV server or from itself?) or does it query the TV at that point?it just returns the list of available resolutions from the above methods (after some sorting).... i do not think those methods query the tv everytime.

It is entirely possible my sorting/parsing algorithm is messed up and barfing (hence why the debug log would be helpful)... It would also be helpful to see a picture of what the default output resolution menu displays (Detailed Setup > Multimedia > Output Resolution) when video out tools is empty.