I get no input signal in Ableton from my guitar. What's wrong?

[motorboyxx]

This is my configuration file:

backend = "Windows WASAPI"
bufferSizeSamples = 256

[input]
device = "Microphone (iRig HD 2)"
suggestedLatencySeconds = 0.0
wasapiExclusiveMode = false
wasapiAutoConvert = false

[output]
device = "Headphones (High Definition Audio Device)"
suggestedLatencySeconds = 0.0
wasapiExclusiveMode = false
wasapiAutoConvert = true

[dechamps]

By "no signal", do you mean that you can start a recording, but only get silence?

Does playback work?

Can you provide a log while the issue is happening?

[motorboyxx]

First question: yes, second question: no.

[dechamps]

Okay. Please provide a log so that I can investigate further.

[motorboyxx]

My log file is 60 MB (I opened an already existing project in Ableton and switched from MME driver to FlexASIO), which lines from it do you want to see?

[dechamps]

That's a pretty big logfile. That shouldn't happen unless you've let it stream for quite some time (but then that would mean it's working, so I'm confused as to why you wouldn't get any sound) or there is some kind of infinite loop happening somewhere. Maybe that's the problem…

Can you try deleting the log, re-creating it as an empty file, and then capture a new log with just how long it takes to reproduce the issue? Just letting it run for a couple of seconds should be enough. Otherwise, the first 10000 lines or so are usually sufficient to get an idea of what's going on.

Also, it would be useful to know what happens if you just use the default FlexASIO configuration (i.e. no configuration file at all, and setting "Microphone (iRig HD 2)" as your default Windows input and "Headphones (High Definition Audio Device)" as your default Windows output). Does it work then?

[motorboyxx]

OK, so I tried to reproduce the issue.
With no configuration file I do actually hear my own guitar, although the overall latency is 116 ms (at buffer size 1024 samples) which obviously is hard to play to.
With a configuration file the program crashes at launch if I try to launch with FlexASIO (to make the log file smaller). I can bypass this by launching with another driver and then switch to FlexASIO. This gives the log file down below (this time much smaller for some reason).
FlexASIO.log

[dechamps]

Okay, so the problem does not happen with the default config. And the logfile does not show any problems - it looks just like normal operation, and everything seems to be fine as far as streaming is concerned. (I did spot an instance of #66 but that's likely unrelated as it wouldn't explain these symptoms.) So I'm afraid I still have no idea what's going on here :(

Since you can get the default configuration to work, what I would suggest at this point is to enable/disable various options and see which one is causing the problem. I would start by removing the bufferSizeSamples and suggestedLatencySeconds options - they look the most suspicious to me as you're aggressively requesting a very small buffer size, and that's prone to issues depending on combinations of application/backend/hardware. It might work if you set the buffer size to something less extreme, e.g. 480 instead of 256.

With a configuration file the program crashes at launch if I try to launch with FlexASIO (to make the log file smaller).

Would you mind filing a separate issue about that? That's definitely not supposed to happen, although it's likely unrelated to the present issue of not getting any sound. Does FlexASIO still generate a log while Ableton crashes at startup?

[motorboyxx]

Keeping or deleting bufferSizeSamples makes no difference, neither does decreasing or increasing the buffer size - no sound from the guitar. I've tested deleting suggestedLatencySeconds as well but that made no difference either...
A log file is created when Ableton crashes at startup. See below.
FlexASIO.log

[dechamps]

Sorry to hear that, I'm all out of ideas :( My best guess is that there is something unusual about your software or hardware configuration that is messing things up somehow.

The other issue you filed about the startup crash (#86) is also very strange in its own way. I can't say for sure, but it could be that both issues ultimately have the same root cause, but are surfacing in different ways. #86 seems easier to diagnose and troubleshoot since it produces a more useful log, so I'd suggest we try to fix #86 first and see if that also fixes your "no sound" issue.

[motorboyxx]

Thank you very much for your patience!

[dechamps]

@motorboyxx In #86 you mentioned that uninstalling ASIO4ALL fixes the startup crash. Does it also get rid of the present issue of not getting any sound?

[dechamps]

Closing due to inactivity.