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

Score v1.0.0b41 (windows) crashes on startup #734

Closed
tohox opened this Issue Apr 27, 2018 · 14 comments

Comments

Projects
None yet
4 participants
@tohox
Copy link

tohox commented Apr 27, 2018

Running Win10 Pro 64 (quad Xeon 3.5, 16GB, with nVidia Quadro FX4600). Score crashes soon after splash screen appears.

Is there a crash report saved somewhere?

Thanks,

@avilleret

This comment has been minimized.

Copy link
Contributor

avilleret commented Apr 27, 2018

which version of Jack are you running ?
could you try to start it from a cmd prompt ? and send here the message that appear in the console ?

@tohox

This comment has been minimized.

Copy link
Author

tohox commented Apr 27, 2018

Didn't realize Jack was required as the last time I installed Score it ran out of the box.

Will install it and report back.

Thanks,

@tohox

This comment has been minimized.

Copy link
Author

tohox commented Apr 27, 2018

Installed Jack 1.9.11 64bits on a different computer with the same result. Score still crashes right after the splash screen appears. Should I simply install Jack for Windows or are some additional run time libraries or path arguments required for Score to run?

When started from CLI no additional information is displayed.

Don't know if this has any incidence on the problem but both computers use the French Canadian locale.

Thanks,

@tohox

This comment has been minimized.

Copy link
Author

tohox commented Apr 27, 2018

Installing 1.0.0b40 on the same Windows machines works out of the box.

@bltzr

This comment has been minimized.

Copy link
Member

bltzr commented Apr 28, 2018

Installing 1.0.0b40 on the same Windows machines works out of the box.

yes, that's because a lot (and I mean a lot) has changed under the hood between v1b40 and v1b41, which should thus (and will) be renamed v2a1

@avilleret

This comment has been minimized.

Copy link
Contributor

avilleret commented Apr 28, 2018

Score v2a1 (aka 1.0.0b41) introduce audio support, hence Jack should be started before score.
If not, it crashes.
This is a kwon limitation (reported on the release note), in the future, I hope there will be a dialog to ask to start jack when launching Score (like the one Ardour provide at startup).
Let us know if it works after starting jack.

@jcelerier

This comment has been minimized.

Copy link
Member

jcelerier commented Apr 28, 2018

This is a kwon limitation (reported on the release note), in the future, I hope there will be a dialog to ask to start jack when launching Score (like the one Ardour provide at startup).

it should be fixed in the latest commits though, it will now try to use portaudio instead if jack is not here

@tohox

This comment has been minimized.

Copy link
Author

tohox commented Apr 28, 2018

Understood. I installed Jack 1.9.11 and tried starting both JACK Audio Connection Kit and Jack PortAudio before starting Score v2a1 and it still crashes. I tried both 32bits and 64bits versions of Jack. Am not familiar with Jack so might not be starting the right component...

I don't need audio so I'll wait for the next release and use 1.0.0b40 in the meantime.

Thanks

@avilleret

This comment has been minimized.

Copy link
Contributor

avilleret commented Apr 28, 2018

Hum... to fix your crash in the next release we need more details :-)
First of all, the component to use to start jack is QJackCtl, the name might not be exactly the same on Windows (I can't remember right now) but the interface looks the same :
image
Once you've got this, try to start the audio server by pressing green arrow.
I really doubt that will works on the first try :-) but it's worth a try.
If it doesn't, open the preference panel and choose your driver/soundcard according to your setup.
You don't need special hardware, I setup an old Gigabyte Brix 2 weeks ago with Score.
If Jack fails to start, then Score will fails too.
So jack is the really first step to use Score >= 2.0.0

@jcelerier

This comment has been minimized.

Copy link
Member

jcelerier commented Apr 29, 2018

@tohox if you have the time, the latest release shouldn't require jack anymore (this was a bug) : https://github.com/OSSIA/score/releases ; if it still crashes it's certainly something else... I'll try in a clean virtual machine.

@tohox

This comment has been minimized.

Copy link
Author

tohox commented Apr 29, 2018

@avilleret This is what I did the first time around. Started the JackAudioConnection Kit and started the server which did so without complaining with the default parameters. Then I tried starting Score 2 both from the desktop shortcut and from the cli. Is there any kind of argument I can add to get debug info?
@jcelerier Just tried release 2.0.0-a3 with the same result (both with and without Jack running).

@tohox

This comment has been minimized.

Copy link
Author

tohox commented May 1, 2018

Hi, a quick followup. I just tried build 2.0.0-a3 on a third Windows 10 computer and it also crashed on startup.

@jcelerier

This comment has been minimized.

Copy link
Member

jcelerier commented Jun 15, 2018

hi! could you try a4 if you have a spare moment ? If it still does not work, I'm at loss :|

@tohox

This comment has been minimized.

Copy link
Author

tohox commented Jun 17, 2018

@jcelerier YESSSSsss!
Thanks! :)

@tohox tohox closed this Jun 17, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.