2008-11-12, 02:07
Ok, I tried it.
First, the autoswitch to 60Hz is still happening and when Zoom Player gets called the refresh stays at 60Hz. It's only when XBMC exits that I go back to my desktop refresh.
Second, this works fine for local content but network shares give me an error: Unable to play [//ASHLAR/My Videos/HD Content/Whatever.mkv]
This may be due to a corrupt file, missing filters, filter conflicts, or hardware related issues.
This happens only for networked stuff. Local content does not have problems (the Windows taskbar stays visible for a fraction of a second, but no big deal).
I'm now gonna try with MPC-HC to see if the problem with networked material remains.
Edit: yup, MPC-HC reports "Failed to render the file" with networked material. And I confirm that it refuses to start in fullscreen, both with the /fullscreen option and the same setting in the internal options of the player.
Regarding the networked stuff, I feel the problem is maybe related to how the path is presented to Windows? Because if I try to open the same file from inside the external player, everything works correctly.
First, the autoswitch to 60Hz is still happening and when Zoom Player gets called the refresh stays at 60Hz. It's only when XBMC exits that I go back to my desktop refresh.
Second, this works fine for local content but network shares give me an error: Unable to play [//ASHLAR/My Videos/HD Content/Whatever.mkv]
This may be due to a corrupt file, missing filters, filter conflicts, or hardware related issues.
This happens only for networked stuff. Local content does not have problems (the Windows taskbar stays visible for a fraction of a second, but no big deal).
I'm now gonna try with MPC-HC to see if the problem with networked material remains.
Edit: yup, MPC-HC reports "Failed to render the file" with networked material. And I confirm that it refuses to start in fullscreen, both with the /fullscreen option and the same setting in the internal options of the player.
Regarding the networked stuff, I feel the problem is maybe related to how the path is presented to Windows? Because if I try to open the same file from inside the external player, everything works correctly.