Performance adjusted for best performance and best performance of Background services. So now it seems that the best investment of my time is to work on removing the spikes in the DPC latency, so I get my rock solid recording setup.īut before I'll just have to summarize my setup right now when it's still working: Sometimes Sequoia hangs and writes long messages in the crashlog. It seems like the most problems occour is when you switch samplerate in the project or change the ASIO buffer size.
MULTITOUCH BOOTCAMP DRIVER
But with 96 samples it's getting sensible to GUI interactions (20 errors because of some zooming and open/close mixer).But when I reduce the bandwidth to only analog 1-8 in the RME driver it's solid again and don't care if I touch mixer settings. (though inserting effects results in lost ASIO buffer)ġ6 tracks in 96KHz/24 bit with 128 samples buffer produces some recording errors (8 errors in 3 minutes).Ĩ tracks in 96KHZ/24bit with 128 samples seems fine. Also the Sequoia feature "record without playback" works fine, so I can sit and mix the material while recording and jump around in the project without affection the recording. Also writing the files in 32bit floating format works fine.Ĭan also do 6 stereo tracks at 192KHz/24 bit with 256 samples buffer (128 not ok) and recording to 32 bit float. Although the playbuffer reports a couple of errors it doesn't seem to influence the recording. Running 6 stereo tracks at 192KHz/24bit (1024 samples buffer)also seems fine. The MBP is showing a CPU usage of 25% and Sequoia is reporting a disk usage of 2%, so I guess I have to increase the load I'm just sitting wondering why I had problems doing the same thing or even less tracks yesterday. At this moment I'm testing Sequoia on my MBP with 8 stereotracks recording from a Fireface 800 in 96KHz/24bit resolution.
0 kommentar(er)
