Skip to content
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

Closed
theguitarplayer opened this issue Mar 13, 2014 · 13 comments
Closed

LMMS is not responding on Windows 8 #451

theguitarplayer opened this issue Mar 13, 2014 · 13 comments

Comments

@theguitarplayer
Copy link

When I try to load the program this pops up:

the application has requested the run time to terminate it in an unusual way.

@Sti2nd
Copy link
Contributor

Sti2nd commented Mar 13, 2014

@theguitarplayer
Copy link
Author

Thanks! that worked!

@Sti2nd
Copy link
Contributor

Sti2nd commented Mar 15, 2014

So the old portaudio (the one in LMMS) seems to be in conflict with Win8.

@tobydox
Copy link
Member

tobydox commented Mar 16, 2014

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.

@tobydox
Copy link
Member

tobydox commented Mar 16, 2014

@theguitarplayer
Copy link
Author

It's actually fixed now. But thanks anyway!

On Sun, Mar 16, 2014 at 6:24 PM, Tobias Doerffel
notifications@github.comwrote:

Please try

http://www-user.tu-chemnitz.de/~doto/lmms/pa/32bit/libportaudio-2.dll

or

http://www-user.tu-chemnitz.de/~doto/lmms/pa/64bit/libportaudio-2.dll

Reply to this email directly or view it on GitHubhttps://github.com//issues/451#issuecomment-37773385
.

@Sti2nd
Copy link
Contributor

Sti2nd commented Mar 17, 2014

@theguitarplayer yeah, but would you mind trying with one of the files in the links for testing purposes? It might help others 👍

@theguitarplayer
Copy link
Author

not sure what you mean, but if you want to, go ahead.

On Mon, Mar 17, 2014 at 5:09 PM, Stian Jørgensrud
notifications@github.comwrote:

@theguitarplayer https://github.com/theguitarplayer yeah, but would you
mind try with one of the files in the links for testing purposes?

Reply to this email directly or view it on GitHubhttps://github.com//issues/451#issuecomment-37870507
.

@Sti2nd
Copy link
Contributor

Sti2nd commented Mar 21, 2014

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.

@tresf
Copy link
Member

tresf commented Mar 29, 2014

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.

@tobydox
Copy link
Member

tobydox commented Mar 29, 2014

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).

@tobydox tobydox closed this as completed Mar 29, 2014
@theguitarplayer
Copy link
Author

So what do you want me to do?

On Fri, Mar 28, 2014 at 10:21 PM, Tres Finocchiaro <notifications@github.com

wrote:

Like I said in #512 #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 https://github.com/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 fig the OPs
problem, but it won't likely make it into the official release. A
work-around is not a solution. It circumvents the problem instead of
resolving it. The community needs to take some responsibility for the
freedoms that they enjoy and pay it forward. It can only remain free if our
community understands the philosophy around "free" in terms of public
domain software. :)

Reply to this email directly or view it on GitHubhttps://github.com//issues/451#issuecomment-38984248
.

@theguitarplayer
Copy link
Author

I think you have the wrong person.

On Sun, Mar 30, 2014 at 5:37 PM, Gordon White teamecstaticgdw@gmail.comwrote:

So what do you want me to do?

On Fri, Mar 28, 2014 at 10:21 PM, Tres Finocchiaro <
notifications@github.com> wrote:

Like I said in #512 #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 https://github.com/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 fig the OPs
problem, but it won't likely make it into the official release. A
work-around is not a solution. It circumvents the problem instead of
resolving it. The community needs to take some responsibility for the
freedoms that they enjoy and pay it forward. It can only remain free if our
community understands the philosophy around "free" in terms of public
domain software. :)

Reply to this email directly or view it on GitHubhttps://github.com//issues/451#issuecomment-38984248
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants