-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
LMMS is not responding on Windows 8 #451
Comments
Thanks! that worked! |
So the old portaudio (the one in LMMS) seems to be in conflict with Win8. |
The PortAudio DLL in LMMS isn't that old. Actually it's from June 2013 and since then no changes to the Windows backend drivers (wasapi, wdmks, wmme, DirectSound) have happened in their SVN repository. Of course it's possible that someone else's binaries work better if they include things like ASIO support (requiring a proprietary SDK to compile). All I can try is to rebuild PortAudio with latest GCC and MinGW64 runtime. |
It's actually fixed now. But thanks anyway! On Sun, Mar 16, 2014 at 6:24 PM, Tobias Doerffel
|
@theguitarplayer yeah, but would you mind trying with one of the files in the links for testing purposes? It might help others 👍 |
not sure what you mean, but if you want to, go ahead. On Mon, Mar 17, 2014 at 5:09 PM, Stian Jørgensrud
|
I meant that you do the exact same process of replacing the .dll but use the file from the links tobydox posted. This way we can find out if it is something "wrong" with the portaudio LMMS ships with. |
Like I said in #512, for me this was clearly a compatibility issue with a specific sound driver. This is the third bug report since 1.0.0 was released so whatever this is, it isn't uncommmon. What @tobydox is suggesting is important because he compiles and bundles the Windows version and the team doesn't use proprietary libraries to do so, so this ASIO4ALL fix might temporarily fix the OPs problem, but it won't likely make it into the official release and therefor won't fix it for others. To be a bit more pragmatic, a work-around is not a solution as it circumvents the problem instead of resolving it. Bug reports aren't support forums, and now we have a bug that we'd like to fix but likely will close as "won't fix" . Because of this we hope each bug reporter can take a bit of onus toward testing the proposed fixes. This will come off as a bit of a lecture, but the community needs to take some responsibility for the freedoms that they enjoy and pay them forward. It can only remain free if our community understands the philosophy around the tight-knit relationship between the users and the developers public domain software. :) @Sti2nd, perhaps we should do diligence too and try to reduce the amount of proprietary solutions we propose. and use the links to proprietary solutions as a last resort. On a side note, I've never had any luck with ASIO4ALL. I've heard it has tremendous performance benefits over the Windows Sound Driver. It is unfortunate that it requires proprietary libraries to build. |
That's why we default to SDL since 1.0.0. There's nothing more we can do here except dropping PortAudio at all (which on the other side works perfectly and better than SDL in many setups). |
So what do you want me to do? On Fri, Mar 28, 2014 at 10:21 PM, Tres Finocchiaro <notifications@github.com
|
I think you have the wrong person. On Sun, Mar 30, 2014 at 5:37 PM, Gordon White teamecstaticgdw@gmail.comwrote:
|
When I try to load the program this pops up:
the application has requested the run time to terminate it in an unusual way.
The text was updated successfully, but these errors were encountered: