![]() The last probe to succeed is for 96 kHz at 14:22:13.850, but then the next probe for 176.4 kHz at 14:22:13.880 fails with AUDCLNT_E_DEVICE_INVALIDATED. ![]() Strangely, this error starts being returned earlier, during canSampleRate() probes. The audio endpoint device has been unplugged, or the audio hardware or associated hardware resources have been reconfigured, disabled, removed, or otherwise made unavailable for use. According to the relevant docs this means: Again that's the first time I see this error code. Most likely PortAudio ends up in a messed up state and that's what's making the process crash.ĪUDCLNT_E_DEVICE_INVALIDATED is being returned from IAudioClient::Start(). I've never seen PortAudio fail on start() before and it looks like there's an error handling bug on the PortAudio side where the error doesn't percolate through to FlexASIO. WASAPI ERROR HRESULT: 0x88890004 : AUDCLNT_E_DEVICE_INVALIDATEDįILE: C:\Users\edechamps\Documents\FlexASIO\src\portaudio\src\hostapi\wasapi\pa_win_wasapi.c ] Do you know why? And why I should install 64 bit Max instead.Starting PortAudio stream 00000000070946F0 I probably won´t be able to use the one or other □ I guess bouncing stuff as you said is the solution, especially for current projects (some work to do though).Ībleton 64 bit seems to run fine with the 32 bit version of MAX installed. Seems great so far…, but I will get problems with lots of (user/3rd party) MAX devices. I tested it with jbridge, bought it and checked some larger projects with 32 bit and 64 bit and noticed that 64 bit loaded much faster and projects seem run smoother. It is obvious I need(ed) the 64 bit version. My memory shows 4 gb with my personal default project and uses almost 8 gb on a test project with a similar setup I often use most of the time (but still less vsts, effects, etc. However, after working with it for many months, it has proved it’s ability to be super fast. When Ableton 64 bit first came out we didn’t see much additional benefit. The best/most stable current now seems to be running a 64bit OS, with a 64bit DAW. 64 bit Ableton seems really smooth compared to 32 bit for sampling. Most computers will easily allow 16gb nowadays, which is a huge speed improvement for Ableton 64.Ģ) SAMPLERS – If you’re sampling a lot of sounds, and using huge amounts of Clips, also expect your Ableton 32 to slow down, or even crash. Since moving to 64 bit Ableton, we’ve noticed this crash virtually never happens, due to the ability to access more than 4gb of RAM. If you’re finding that you manage large sets with lots of tracks/devices/vst’s and you’re getting the mysterious “serious error occurred” in Live, then you are most likely running out of RAM. There is a solution: Jbridge can enable 64 bit VST’s on a 32 bit host! It’s a good solution, but it would be so much better if Ableton built their own bridge Pros:ġ) RAM – There’s so much more RAM available in Ableton 圆4 bit. However, those little VST’s that sometime give the most unique sounds and workflow may not. The most popular ones are likely to be updated very quickly. Most of the developers who build these objects are building them for free, so expect it to take some time before the majority of them are updated.Ģ) VST’s – Many 32 bit VST’s will not work with a 64 bit host. ![]() Cons:ġ) MAX FOR LIVE – Some max for live devices will not work (32 bit object used inside max will need to be updated to work with 64 bit). We’ve put together this post to try and dispel some of the myths around the move to 64 bit architecture. Pros and Cons of moving to 64 bit Ableton:Ī lot of people have been asking about 32 vs 64 bit versions of Ableton Live. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |