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

Crash bug opening current windows build #1526

Open
geoffeep opened this issue Jan 14, 2024 · 11 comments
Open

Crash bug opening current windows build #1526

geoffeep opened this issue Jan 14, 2024 · 11 comments
Labels

Comments

@geoffeep
Copy link
Contributor

When I run Bespoke, it opens, stays open for about a second, and then crashes.
I don't have enough time to click on the ? unfortunately, so not entirely sure what version it is sorry!

No useful information in the Windows Event Viewer either.
Can't imagine it is helpful, but I'll paste it anyway:

Fault bucket 1743911573119277303, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: BespokeSynth.exe
P2: 1.2.1.0
P3: 65060d15
P4: BespokeSynth.exe
P5: 1.2.1.0
P6: 65060d15
P7: c0000005
P8: 0000000000456461

@geoffeep geoffeep added the bug label Jan 14, 2024
@geoffeep
Copy link
Contributor Author

geoffeep commented Jan 14, 2024

Sorry forgot the crash log!

crash_2024-01-14_12-28.txt

@NoxyNixie
Copy link
Collaborator

Have you tried removing your Documents\BespokeSynth\userprefs.json file?

@geoffeep
Copy link
Contributor Author

Gave it a shot, but still instant crash!
I think I'll have a go at compiling from source and see if I can catch it, has got to be a really weird edge case if no one else is getting it

@geoffeep
Copy link
Contributor Author

Ok building from source and getting somewhere!
The assert is in ModularSynth::GetOutputBuffer.

Channel is 1 going into that function, and the output buffer array only has one element in it.
Still trying to work out what that means, but I'll keep poking it.

image

@geoffeep
Copy link
Contributor Author

It is from this function call:

image

image

@geoffeep
Copy link
Contributor Author

Figured it out :)
Arctis 7 Chat setting as a playback device is insta crash!

image

@KottV
Copy link
Collaborator

KottV commented Jan 28, 2024

Hi. What if build Bespoke with the latest JUCE? It should compile.
There is an option -DBESPOKE_JUCE_LOCATION= which can be pointed to the JUCE source tree.

@geoffeep
Copy link
Contributor Author

I'll give that a try at some point, but I'm pretty ok with using the "Game" mode on the headset for now, I think it is probably the better setting anyway :)

@awwbees
Copy link
Collaborator

awwbees commented Feb 2, 2024

my surface-level guess is that bespoke doesn't handle things properly when your audio device just has a mono output, it always assumes you have at least 2 output channels. your headphones' "chat" setting is probably just a single channel, which is breaking that assumption. should be a pretty easy fix, although I should figure out how to get (or simulate) a single-channel audio device to properly test it. I might be able to do it with vb-cable.

@geoffeep
Copy link
Contributor Author

geoffeep commented Feb 2, 2024

Ah ok yeah, that makes sense.
If you want me to test some code out locally I can do that if it helps!

@geoffeep
Copy link
Contributor Author

geoffeep commented Mar 23, 2024

I might try to look at this one myself, if you're ok with that?

As a side thing, I wanted to do a really hacky multi channel output for VST plugins just to see if it was even worth a feature request, and I noticed this comment:
* Until we support multi output we end up with this requirement that
* the output is at most stereo.

So I am going down the rabbithole of trying to understand input and output channels and busses already anyway :)

So regardless how I go on the output channel hackery, handling Mono output might be something I can work out!
I managed to get the code setup, and vaguely understand github, so I'll see how I go :)

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

No branches or pull requests

4 participants