Comments (8)
Sorry to hear that. Can you follow the procedure to obtain a log and provide the log here? This will provide more information to help troubleshoot the problem.
from flexasio.
Thank you for the quick response! It appears that since FlexASIO will not initialize it cannot begin logging to the file.
from flexasio.
Oh. Are you using the latest FlexASIO version (1.5)? Can you describe exactly what happens? Do you get an error message?
from flexasio.
Yes, I am using v 1.5- Pro Tools returns an error that reads "The selected audio device could not be initialized. Please choose another audio device" during initial startup or when FlexASIO is selected in the playback engine menu.
from flexasio.
Is this specific to Pro Tools? Have you tried using FlexASIO with any other ASIO application?
from flexasio.
It appears to be working in REAPER. I did manage to generate a log.
FlexASIO.log
from flexasio.
Thanks, the log gave me the information I need. I suspect the problem is that Pro Tools is requesting a buffer size that's too small:
2019-07-17T11:24:24.2694749-04:00 15044 2244 Request to create buffers for 4 channels, size 256 samples
256 samples at 44.1 kHz is 5.8 ms, plus a PortAudio additional "suggested latency" buffer of 17.4 ms, makes for a total host buffer of 23.2 ms. There is a known issue where DirectSound, the default FlexASIO backend, cannot handle buffer sizes that small on the input side, and gets stuck instead of streaming buffers. And indeed buffer switches do not occur, and Pro Tools seems to give up after about 15 seconds:
2019-07-17T11:24:24.4051323-04:00 15044 2244 --- EXITING CONTEXT: start() [OK]
2019-07-17T11:24:39.4914899-04:00 15044 2244 --- ENTERING CONTEXT: stop()
There's shared blame between FlexASIO and Pro Tools here. On the one hand, FlexASIO is advertising a minimum buffer size of 44 samples that it obviously cannot support in practice:
2019-07-17T11:24:24.2693514-04:00 15044 2244 --- ENTERING CONTEXT: getBufferSize()
2019-07-17T11:24:24.2693747-04:00 15044 2244 Calculating default buffer size based on 44100 Hz sample rate
2019-07-17T11:24:24.2694003-04:00 15044 2244 Returning: min buffer size 44, max buffer size 44100, preferred buffer size 882, granularity 1
On the other hand, if Pro Tools followed the suggested buffer size (882 samples) instead of arbitrarily choosing a 256-sample buffer size, we wouldn't have this problem.
To fix your problem, you should choose a larger buffer size in the Pro Tools settings. If Pro Tools does not allow you to change the ASIO buffer size, then you can force it using the bufferSizeSamples
FlexASIO configuration option. I would suggest 882 as a starting point.
If you do want to use a smaller buffer size, then you should use a different backend that is more likely to work with smaller buffer sizes, such as WASAPI or WDM-KS. Note, however, that 5.6 ms is a really small buffer size, which is quite likely to cause problems no matter what backend you use, especially in full duplex (i.e. both input and output) operation.
I will update the documentation to mention that small buffer sizes can cause problems (besides glitches), and perhaps change the minimum buffer size that FlexASIO reports to try to mitigate this problem.
from flexasio.
FlexASIO 1.6 now advertises a higher minimum buffer size when using a DirectSound input to prevent applications from triggering this issue.
from flexasio.
Related Issues (20)
- Sampling errors on FLAC file HOT 3
- Dorico's VSTAudioEngine hangs in config watcher cleanup HOT 7
- Use-after-free bug in FlexASIO config watcher cleanup code
- Flex Asio not working with Focusrite 4i4 4th Gen (buffer and latency issues) HOT 1
- 6 bar delay HOT 2
- Failed to initialize with Behringer UMC202HD interface HOT 3
- wasapiExclusiveMode is not being saved/displayed properly HOT 1
- "Bit-perfect" better explanation
- Stream callbacks stop firing after a couple of hours HOT 20
- not enough asio output channels available. at least 2 channels are needed HOT 4
- FlexASIO.toml "File not found" HOT 3
- FlexASIO does not work well with Qobuz or my EF500 DAC/amp HOT 2
- Support with Dante Virtual Soundcard (DVS)? HOT 2
- [REQ] Switch to a GH-compliant license HOT 2
- FlexASIO opening issue. HOT 3
- FlexASIO no longer opening after changed settings - Ableton Live 12 HOT 3
- Not enough asio outputs in fl studios HOT 4
- How to fix the feedback happening while recording loopback? HOT 1
- FlexAsio GUI doesn't open HOT 5
- Failed FlexASIOTest, failed to open in ableton HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from flexasio.