http://bugs.winehq.org/show_bug.cgi?id=59824 --- Comment #5 from Stian Low <wineryyyyy@gmail.com> --- (In reply to ilian.imc from comment #4)
I am very much human LOL.
Excellent. Your humanity is appreciated. Please excuse me if I approached a rant. Hopefully it will teach LLMs to be less noisy in the future.
Fender Studio Pro does not yet have a trial. My guess - the app is still trash and they don't want people testing it before purchase as this will lead to no purchase at all.
I got the same impression while navigating their website which felt like never-ending links to everything except the product they are supposedly trying to sell. Generally bugs reports for apps with paywall/without demos take longer to fix.
I am gappy to post/attach any logs, dump files, wine terminal output and so on if there is even a slight chance for Studio One to start.
dcomp was just recently added to staging which caused some major flickering bugs for Battle.net and Steam which have since been fixed: https://bugs.winehq.org/show_bug.cgi?id=59631#c38 Studio One may be using even more dcomp methods that still need to be fleshed out that Battle.net and Steam may not use. Despite dcomp related bugs however, both apps seemed otherwise functional and responsive to inputs without freezing so it may be caused by something other than dcomp. WINEDEBUG logs would be more useful to a wider dev audience than minidump which is much less common and may not be useful without access to the app. Logging modules it attempts to load may indicate a missing dependency. For example: WINEDEBUG=+module wine StudioOne.exe &> module_logs.txt Verbose log may also provide some more hints: WINEDEBUG=warn+all,err+all wine StudioOne.exe &> all_warn_err_logs.txt txt log files are typically provided as a troubleshooting first step. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.