-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feedback: Explain GStreamer and options #138
Comments
Thanks for the feedback I'll check if I can improve that in the next release |
Is GStreamer even still needed with crossover 23.5? my understanding is they now include it themselves. |
re7 doesn't work, so it's missing something, the gstreamer patch for cxpatcher is better |
As GStreamer is a hard requirement it can’t be optional, as for an explanation “GStreamer is used for multimedia decoding”
Could probably shorten this to
After applying CXPatcher it implements things that stock CrossOver doesn’t and this can cause bugs in the users bottles. Having completely separate bottles avoids these issues. The original intention was to allow a user to have stock CrossOver-23.0.1 plus CrossOver-22.1.1 that had CXPatcher applied. |
@italomandara along the same lines, because I don't want to open a new issue for a very similar thing, it would be nice if you had some little info buttons for the new features too such as disabling fast math and enabling msync.. I have no idea what those are and why they shouldn't be enabled at all times.. |
After the gstreamer integration release I'll have a more time to do this kid of things. |
This is just some general feedback that I think could help make things a bit clearer for first time users.
A little button next to GStreamer that explains why you need this, why you should install it (why I need foundations libraries)
And same thing next to "use separate bottles path". I can of get it from reading the issues about it but it's still unclear. Like.. will my existing bottles benefit from CXPatcher now that I've chosen this option?
Thanks!
The text was updated successfully, but these errors were encountered: