- #Komplete audio 6 windows 10 driver driver#
- #Komplete audio 6 windows 10 driver pro#
- #Komplete audio 6 windows 10 driver software#
- #Komplete audio 6 windows 10 driver Pc#
#Komplete audio 6 windows 10 driver software#
I have a lot of experience building high performance gaming PCs but have never experienced a change of hardware render any software created project obsolete. Had I known that this could have even remotely been the cause, I would have mentioned it. The error message is accurate - a lack of information on what you were doing made it more difficult to nail down the cause. It would have been helpful to know you were opening an existing project, rather than just trying to start Sonar. You can either remain 'not impressed' with things, or you can educate yourself enough on the products you are using.
#Komplete audio 6 windows 10 driver pro#
As far as 'tricks to try', I would suggest you invest some time in reading the documentation, or working through some of the tutorials, buying one of the well-written books on Sonar, watching the numerous free videos, buying some of the pro videos, or at the very least hitting F1 to pull up context help documentation for whatever screen you have up and are struggling with. To change the record bit-depth, go to Edit>Preferences>File>Audio Data, and you will see it there. I do not know why they have the grayed out bit-depth displayed, but in any case that is not where it gets set/changed. Please note that these settings are reasonable for recording, but will you will need to bump up ASIO Buffer Size to possibly as much as 1024 when you begin mixing. I suggest the following settings: Sample Rate (both Sonar and interface must match) of either 44.1 k or 48 k, ASIO Buffer Size of 128, record bit-depth of 24 bits - try to get your Total Roundtrip Latency down to around 10 milliseconds or a tiny bit less. Your settings, or plugins, are what is causing the crackles you hear.
#Komplete audio 6 windows 10 driver driver#
Should these be different and why can't I change the "Audio Driver Bit Depth"? Tried both "64 bit double precision engine" on and off. How do these relate to the "Audio Driver Bit Depth" which is at 24 and grayed out (can't be changed)? The transport display shows 96/16. Any other tricks I should try? My "Record Bit Depth" is 16 and "Render Bit Depth" is 32. I am not impressed with this so called better audio interface. It's now gone during play but still there for the volume sliders and play marker moves. Had to move the sample rate up to 96000 Hz and buffers to 192 for the cracking to go away. My cheap internal Realtek sound card was cleaner than this it only buzzed every minute or so. Although it works now, I get crackling during live piano play with Ivory VSTI and also lots of crackling when I move the volume sliders on any of the tracks or when I jump the play marker.
#Komplete audio 6 windows 10 driver Pc#
The problem was that I was opening a project that had a recording with a higher sampling rate made previously with the internal card on my PC motherboard. Is it possible that the audio interface is plugged into a different USB port than the one it was in during the driver installation? Bob Bone This defaults to 32-bit, and I have never changed it, but did see a post where someone got your same error message when they had it set to 64-bits, and it went away when they changed it back to 32-bits. Just curious - what is your Render Bit Depth set to? (Edit>Preferences>File>Audio Data). I found some info on the Cakewalk web site that was referencing the Unable to Open Audio Device error message you posted this thread about. NOW, with regard to your reported issue: 1.
Sorry for any confusion the above may have caused. So, again, the above has nothing to do with the error you posted - it was just something else I happened to see. A sample rate of either 44.1 k or 48 k, record bit-depth of 24 bits, and an ASIO Buffer Size of 128 should get you down to somewhere between 9.3 and 10.5 milliseconds, and that should eliminate that audible 'lag' or any dropouts or crackles. You want to try to keep your total roundtrip latency down to around or just under 10 milliseconds. I just happened to notice from your listed settings that your total roundtrip latency was up over 15 milliseconds, and latency that high produces an audible lag between playing a note and hearing it play back through Sonar while recording. It does not, and is a completely separate issue. I am sorry if I inferred that the observation I made about your ASIO Buffer Size had anything to do with your error.
0 kommentar(er)
