INTERACT FORUM
More => Old Versions => JRiver Media Center 24 for Windows => Topic started by: johanossason on April 26, 2018, 08:57:11 am
-
Does not work in 24. Works with 23. I'm using win 7. Noticed another user remarked on this so you're probably working with this issue.
-
Please try the build just posted.
-
Same here. Running JRiver 24 with Windows 10. When I try to open Theater View, it come up with this error:
Error starting open GLengine (open GL 2.1 or newer required (1.10 found))
JRiver 23 on the same computer works fine.
I have uninstalled and reinstalled it 2 times but still comes up with same error, when trying to open Theater View.
-
You would get that error if you graphics card is not supported. The most likely case is that your graphics card is not fully compatible with Windows 10.
-
I'd recommend reading this topic: https://yabb.jriver.com/interact/index.php/topic,115454.0.html
-
Same here. Running JRiver 24 with Windows 10. When I try to open Theater View, it come up with this error:
Error starting open GLengine (open GL 2.1 or newer required (1.10 found))
JRiver 23 on the same computer works fine.
I have uninstalled and reinstalled it 2 times but still comes up with same error, when trying to open Theater View.
In MC23 "Theater View" uses Direct3D (and there is an option in Tools>Options>TheaterView>Advanced to switch to "OpenGL (experimental)" as the developers were starting to write the programming to switch MC to OpenGL.
Now in MC24 "Theater View" uses OpenGL (and there is an option at Tools>Options>TheaterView>Advanced to switch to legacy Direct3D". But this option is going to removed in the near future according to developers. Most of what I just said is in the other post, linked to above.
-
Just installed 19. No change, ie, Theater view does not work
-
You said it worked with MC23. Why did you install 19? Just go back to 23.
But if Theater View is not working in any version, then something else is going on with your machine. Could you be in "Audio Only" mode (View>Audio Only)?
-
He probably meant Build 19.
-
Just installed 19. No change, ie, Theater view does not work
Try Tools>Options>Theater View>Advanced> "Use legacy Direct3D"
He probably meant Build 19.
Yes. I get that now.
-
Just installed 19. No change, ie, Theater view does not work
And honestly, it won't if you're using a Sandy Bridge-era CPU (with HD 2000/3000 onboard graphics) on Windows 10. This is a Intel issue for never releasing Windows 10 drivers for the Sandy Bridge CPU's onboard graphics. There's really nothing JRiver/Hendrik can do about this.
Using the legacy Direct3D option is just a temporary measure, JRiver/Hendrik has already said it's going to removed eventually, so I would not recommend using this as a solution, because it isn't one.
To anyone encountering this issue, I'd highly start consider either a) upgrading CPU/motherboard/hardware to something that's a little more "modern" and is supported on Windows 10, b) consider adding a dedicated GPU to the system if possible or c) downgrading from Windows 10 to Windows 8.1 where OpenGL 2.1 will work. Honestly though, if you're still running a Sandy Bridge/Ivy Bridge-era CPU and hardware, I'd HIGHLY consider upgrading anyways because older hardware like this isn't going to be supported forever.
Hendrik, is it possible to change what the GLengine error says? At least informing the user their hardware/CPU/onboard graphics isn't supported on Windows 10 if they're using Sandy Bridge or older.
-
b) consider adding a dedicated GPU to the system if possible
And, assuming it is a desktop PC with a slot, and not a laptop, this will be your most cost effective and simple option, naturally. Pretty much any current-gen AMD or nvidia add in GPU is going to have the OpenGL support needed. This is not a new, latest-and-greatest version of OpenGL required or anything. Intel's drivers are just broken, and rather than fix them, they discontinued support for the product.
You can enable D3D mode until then, of course.
-
Try Tools>Options>Theater View>Advanced> "Use legacy Direct3D"
Yes. I get that now.
Followed your advice, and, it worked. Was a bit reluctant because it says "not recommended"
-
Followed your advice, and, it worked. Was a bit reluctant because it says "not recommended"
Yeah, it'll be removed at some point, so it's not really a solution/fix.