Reply to thread

Message

<blockquote data-quote="Stéphane Lenclud" data-source="post: 1206432" data-attributes="member: 140174">Yes that's the expected behaviour for now, I think I tried to explain that a few post earlier. Though it should switch back when closing MP. It should also switch back if you start playing a 2D video source.Basically we used to &quot;switch back to 2D as soon as possible&quot; and now we &quot;switch back to 2D when needed&quot;.Switch back to 2D as soon as possible had the following major problem: it tried to switch back to 2D and then back to 3D when switching from one 3D video to another 3D video from Moving Pictures. That could result in two macros running concurrently sending nonsensical commands to your TV depending of the Auto3D device and method you were using.Switch back to 2D only when needed fixes this issue by making the assumption that there is nothing wrong with being in 3D when no video is playing. This scheme limits the number of mode switch you need to do, thus providing a bug free and smoother experience when switching from one 3D video to another.Ideally we should make this configurable I guess.I found the problem I had with MP1.16. It's an issue that was very specific to my setup since I'm probably the only one using a SharpLibDisplay device.Basically Auto3D is expecting a newer version of that DLL than the one shipping with MP1.Here are the <a href="https://github.com/MediaPortal/MediaPortal-1/commit/3ae820f39073" target="_blank">changes in MP1</a>.Here is the <a href="https://issues.team-mediaportal.com/browse/MP1-4835" target="_blank">JIRA MP1-4835</a>.</blockquote>

[QUOTE="Stéphane Lenclud, post: 1206432, member: 140174"] Yes that's the expected behaviour for now, I think I tried to explain that a few post earlier. Though it should switch back when closing MP. It should also switch back if you start playing a 2D video source. Basically we used to [I]"switch back to 2D as soon as possible"[/I] and now we [I]"switch back to 2D when needed"[/I]. [B]Switch back to 2D as soon as possible[/B] had the following major problem: it tried to switch back to 2D and then back to 3D when switching from one 3D video to another 3D video from [I]Moving Pictures. [/I]That could result in two macros running concurrently sending nonsensical commands to your TV depending of the Auto3D device and method you were using. [B]Switch back to 2D only when needed[/B] fixes this issue by making the assumption that there is nothing wrong with being in 3D when no video is playing. This scheme limits the number of mode switch you need to do, thus providing a bug free and smoother experience when switching from one 3D video to another. Ideally we should make this configurable I guess. I found the problem I had with MP1.16. It's an issue that was very specific to my setup since I'm probably the only one using a SharpLibDisplay device. Basically Auto3D is expecting a newer version of that DLL than the one shipping with MP1. Here are the [URL='https://github.com/MediaPortal/MediaPortal-1/commit/3ae820f39073']changes in MP1[/URL]. Here is the [URL='https://issues.team-mediaportal.com/browse/MP1-4835']JIRA MP1-4835[/URL]. [/QUOTE]

Verification