projectM-sdl-win-x64 v3.1.3 hanging on Win10

[chaosophy]

Hi, just recently found this project and thought I'd give it a go but it just hangs for me.

It opens up the 'projectM Visualizer' window with a black screen and the 'M' logo in the middle but immediately goes to not responding.

The CMD window that opens just shows this...

INFO: GL_VERSION: 3.2.13596 Core Profile Context 20.5.1 27.20.1017.1011 INFO: GL_SHADING_LANGUAGE_VERSION: 4.60 INFO: GL_VENDOR: ATI Technologies Inc. INFO: Using data directory: /usr/local/share/projectM INFO: Looking for configuration file in data dir: /usr/local/share/projectM. INFO: Config file not found, using built-in settings. Data directory=D:\projectM-sdl\Release\ [PresetFactory] url is idle://Geiss & Sperl - Feedback (projectM idle HDR mix).milk fps: 60

I had a look but can't find any kind of config file or log file to check, also searched the web but can't really find any documentation or help for the windows version, so posting here hoping someone can help.

I've tried 3.1.3 and 3.1.2 from the release downloads, running it as admin, running it from an admin cmd.

Resource monitor shows it opens a load of handles, both registry and file handles, including files in AppData\Local\AMD\GLCache\ so at least seems to be getting that far.

Am I missing something obvious/doing something dumb? Any way to get logs out of it to look at?

Let me know if you need any more info, h/w setup s/w versions etc.

Thanks.

[chaosophy]

Hi, seems to be working ok now, not entirely sure why but think it might be related to having my VR headset plugged in.
Need to test it out more.

Though now it does crash when cycling through audio devices.

Are there docs any where for setting up a config file?

Thanks.

[milkdropper]

Did it crash immediately when you changed audio devices or when you changed 5++ times? I saw this bug in Windows when I cycled too many times projectM-visualizer/projectm#365 (comment)

The bug is fixed and will be in future releases.

[chaosophy]

It's on the third change. Had a quick look at the issue you linked and could be the same thing. WASPAPI.

INFO: Opened audio capture device index=1 devId=2: Wave (ASUS Essence STX II Audio Device)
INFO: Samples: 2048, frequency: 44100, channels: 2, format: 33056
INFO: Opened audio capture device index=2 devId=3: Line In (ASUS Essence STX II Audio Device)
INFO: Samples: 2048, frequency: 44100, channels: 2, format: 33056
CRITICAL: Failed to open audio capture device: WASAPI can't initialize audio client: 栰⢽Ȝ
INFO: Opened audio capture device index=3 devId=0: (null)
INFO: Samples: 2048, frequency: 44100, channels: 2, format: 33056

main vis window closes and the cmd window carries on cycling through the presets.

also, sorry to ask again but is there any docs on, or sample file of, the config file?

thanks.

[milkdropper]

It must be the CRITICAL error.

In the current release it will exit the SDL application if it encounters an exception like that but in the upcoming version it will not.

[kblaschke]

The next projectM SDL release will feature a completely rewritten app, and also contain a lot of bugfixes in the underlying projectM visualizer. If the next release (in the new repo here) still exposes the described behaviour, please open a new issue.