Question about MediaPlayerFileLoadComplete hook

[BobPhoenix]

OK here is what I've seen and maybe this is normal - don't know. This was on a 5.0.4 Server and Client.

When Client is first opened and a video is selected from the library the MediaPlayerFileLoadComplete hook is apparently only called once on the first file to play - FullyLoaded is true so evidentally this is suppose to be the second call. All other video playback requests after that before exiting the Client appear to call the MediaPlayerFileLoadComplete hook 2 times like I would expect. Is this normal?

Now to the really weird:
Occasionally it is never called or at least not with FullyLoaded as true or false anyway. This can't be normal can it? I added another DebugLog out side of the 'If FullyLoaded' (see below) to see if it was executed with FullyLoaded equal to neither true or false but no luck yet - it always takes the true branch so far.

FYI: The IF I had looked similar to this (but I also included a graphic of the code as well):

DebugLog("Always Executed")   <---This is what was added after weirdness above.
If FullyLoaded
   true
      DebugLog("FullyLoaded=true")
   false
      DebugLog("FullyLoaded=false")

Edit: Opps should have specified which hook I'm using since there is one at the root level as well as in the MediaPlayer OSD menu. I was using the MediaPlayer OSD menu one. Also I just tried an experiment and copied the code to the root level one and now it appears to be working as expected except for one thing when I do that the code in the MediaPlayer OSD menu isn't executed at all now. (included a graphic of that code now as well)

[GKusnick]

A hook in a menu fires only if that menu is active. If the active menu does not have a hook of the right type, it falls through to the root-level hook of that type (if any). So you can't just put code in the OSD menu hook and expect it to catch all cases. You need to cover the fall-through case as well, for when some other menu is displayed.

[BobPhoenix]

Thank you. That's what I thought especially after I realized that the media player load process is started before the MediaPlayer OSD menu is launched. This explains why the hook sometimes only gets called on the second call or not at all - it's already been through the process before the menu is displayed.

BobP.

[alon24]

Is that true for a listener too?
I need to listen to the Custom2 event, from the second the application starts(in order to do forcedEpgUpdate).

Where should I place my event listener?

[Opus4]

The processing chain of events for a listener is described on p. 30 of the v5 Studio PDF manual; depending on the code, one or more listeners may be fired for a command. If you don't already have that document, it can be found in the stickies of this forum section. As it says there, you'll want to use a theme named "Global" (also see p. 51), but if the listener is also handled elsewhere in some menu, that Global listener may never be reached -- again, depending on the code in the listener's child widget tree.

- Andy

[BobPhoenix]

Originally Posted by Opus4

The processing chain of events for a listener is described on p. 30 of the v5 Studio PDF manual; depending on the code, one or more listeners may be fired for a command. If you don't already have that document, it can be found in the stickies of this forum section. As it says there, you'll want to use a theme named "Global" (also see p. 51), but if the listener is also handled elsewhere in some menu, that Global listener may never be reached -- again, depending on the code in the listener's child widget tree.

- Andy

This leads me to ask this question then and maybe it is in the manual but I don't remember it. Which would get executed first the listener loaded directly under the menu or the listener in the menu's theme - the Album theme for instance? I suspect it is the listener directly loaded in the menu.

BobP.

[Opus4]

The best way to see if one or both of the listeners would be called in such a situation would be to make sure they both use PassiveListen() at some point, then put a debugging breakpoint under both listeners. Afer passing the first breakpoint, use Resume & see if it stops at the next one.

- Andy

[BobPhoenix]

Originally Posted by Opus4

The best way to see if one or both of the listeners would be called in such a situation would be to make sure they both use PassiveListen() at some point, then put a debugging breakpoint under both listeners. Afer passing the first breakpoint, use Resume & see if it stops at the next one.

- Andy

I'll try that next time I get a chance.

Thanks.
BobP.