Hi, I’m having a problem since the last Dorico update, until now I had my sound card buffer at 256 and I had no crash problems or any noise and I could record in real time quite well, suddenly I started to receive noises and I had to increase my card buffer to an outrageous 2048 to be able to hear the sound without cracks, I use Note Performer with different libraries bbc, vsl, iconic, nucleus and several vst3; I attach a diagnostic report to see if you can find out where the problem is, my computer is .
windows 10,Rme Raydat,I7 6300,128
You submitted your post before your diagnostics had been fully uploaded. Please try attaching them again, and wait until the upload has completed before you post the message.
Dorico Diagnostics.zip (3.3 MB)
It’s a total guess (and maybe @Ulf might have more ideas) but you could try disabling ASIO-Guard in the Advanced Options section of the Play page of Preferences, then restart Dorico and see if that helps.
Well, unfortunately I can’t find any evidence in the log files that the audio engine would be in distress, i.e. not being able to deliver the proper audio stream to the audio device. Therefore, other than Daniel’s suggestion with the advanced option I have nothing to add at this moment.
Well, not true, there is one more thing: Please download the free utility LatencyMon, run that and post here the result. Let’s see if that reveals something.
prueba.dorico (2.2 MB)
clear
115 / 5.000
Resultados de traducción
Resultado de traducción
I am attaching a short project where in measure 6 the cut and noise of the program becomes evident, in case it is helpful.
CONCLUSION
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:03:40 (h:mm:ss) on all processors.
SYSTEM INFORMATION
Computer name: PC-1670667679
OS version: Windows 10, 10.0, version 2009, build: 19045 (x64)
Hardware:
BIOS: 1801
CPU: GenuineIntel Intel(R) Core™ i7-6800K CPU @ 3.40GHz
Logical processors: 12
Processor groups: 1
Processor group size: 12
RAM: 130982 MB total
CPU SPEED
Reported CPU speed (WMI): 3401 MHz
Reported CPU speed (registry): 3398 MHz
Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.
MEASURED INTERRUPT TO USER PROCESS LATENCIES
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution
of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.
Highest measured interrupt to process latency (µs): 851,0
Average measured interrupt to process latency (µs): 4,667183
Highest measured interrupt to DPC latency (µs): 848,40
Average measured interrupt to DPC latency (µs): 1,604015
REPORTED ISRs
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.
Highest ISR routine execution time (µs): 67,455268
Driver with highest ISR routine execution time: portcls.sys - Port Class (Class Driver for Port/Miniport Devices), Microsoft Corporation
Highest reported total ISR routine time (%): 0,005807
Driver with highest ISR total time: portcls.sys - Port Class (Class Driver for Port/Miniport Devices), Microsoft Corporation
Total time spent in ISRs (%) 0,006364
ISR count (execution time <250 µs): 28493
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 0
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µs): 0
ISR count (execution time >=4000 µs): 0
REPORTED DPCs
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.
Highest DPC routine execution time (µs): 344,017952
Driver with highest DPC routine execution time: tcpip.sys - Controlador TCP/IP, Microsoft Corporation
Highest reported total DPC routine time (%): 0,019316
Driver with highest DPC total execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in DPCs (%) 0,058150
DPC count (execution time <250 µs): 320951
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 8
DPC count (execution time 1000-2000 µs): 0
DPC count (execution time 2000-4000 µs): 0
DPC count (execution time >=4000 µs): 0
REPORTED HARD PAGEFAULTS
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk
while the process is interrupted and blocked from execution.
NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.
Process with highest pagefault count: avp.exe
Total number of hard pagefaults 669
Hard pagefault count of hardest hit process: 300
Number of processes hit: 17
PER CPU DATA
CPU 0 Interrupt cycle time (s): 4,187913
CPU 0 ISR highest execution time (µs): 67,455268
CPU 0 ISR total execution time (s): 0,163053
CPU 0 ISR count: 22634
CPU 0 DPC highest execution time (µs): 316,358446
CPU 0 DPC total execution time (s): 0,822354
CPU 0 DPC count: 141663
CPU 1 Interrupt cycle time (s): 0,789949
CPU 1 ISR highest execution time (µs): 0,0
CPU 1 ISR total execution time (s): 0,0
CPU 1 ISR count: 0
CPU 1 DPC highest execution time (µs): 329,155386
CPU 1 DPC total execution time (s): 0,043725
CPU 1 DPC count: 11999
CPU 2 Interrupt cycle time (s): 0,987458
CPU 2 ISR highest execution time (µs): 0,0
CPU 2 ISR total execution time (s): 0,0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 329,117128
CPU 2 DPC total execution time (s): 0,077133
CPU 2 DPC count: 19329
CPU 3 Interrupt cycle time (s): 0,944153
CPU 3 ISR highest execution time (µs): 0,0
CPU 3 ISR total execution time (s): 0,0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 119,527369
CPU 3 DPC total execution time (s): 0,050289
CPU 3 DPC count: 12592
CPU 4 Interrupt cycle time (s): 1,161422
CPU 4 ISR highest execution time (µs): 0,0
CPU 4 ISR total execution time (s): 0,0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 328,147440
CPU 4 DPC total execution time (s): 0,086441
CPU 4 DPC count: 22448
CPU 5 Interrupt cycle time (s): 0,984668
CPU 5 ISR highest execution time (µs): 0,0
CPU 5 ISR total execution time (s): 0,0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 105,807828
CPU 5 DPC total execution time (s): 0,018924
CPU 5 DPC count: 5539
CPU 6 Interrupt cycle time (s): 2,840954
CPU 6 ISR highest execution time (µs): 0,0
CPU 6 ISR total execution time (s): 0,0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 344,017952
CPU 6 DPC total execution time (s): 0,217916
CPU 6 DPC count: 60274
CPU 7 Interrupt cycle time (s): 0,941063
CPU 7 ISR highest execution time (µs): 0,0
CPU 7 ISR total execution time (s): 0,0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 105,070041
CPU 7 DPC total execution time (s): 0,011294
CPU 7 DPC count: 3414
CPU 8 Interrupt cycle time (s): 1,144227
CPU 8 ISR highest execution time (µs): 0,0
CPU 8 ISR total execution time (s): 0,0
CPU 8 ISR count: 0
CPU 8 DPC highest execution time (µs): 120,954679
CPU 8 DPC total execution time (s): 0,070051
CPU 8 DPC count: 17055
CPU 9 Interrupt cycle time (s): 1,022336
CPU 9 ISR highest execution time (µs): 0,0
CPU 9 ISR total execution time (s): 0,0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 115,962625
CPU 9 DPC total execution time (s): 0,020903
CPU 9 DPC count: 5256
CPU 10 Interrupt cycle time (s): 1,243880
CPU 10 ISR highest execution time (µs): 4,027958
CPU 10 ISR total execution time (s): 0,005079
CPU 10 ISR count: 5859
CPU 10 DPC highest execution time (µs): 108,962331
CPU 10 DPC total execution time (s): 0,066510
CPU 10 DPC count: 14135
CPU 11 Interrupt cycle time (s): 1,077622
CPU 11 ISR highest execution time (µs): 0,0
CPU 11 ISR total execution time (s): 0,0
CPU 11 ISR count: 0
CPU 11 DPC highest execution time (µs): 111,025309
CPU 11 DPC total execution time (s): 0,050696
CPU 11 DPC count: 7255
?Would it be possible that the file of the song I’m writing is corrupted, as has happened to me in Cubase, because I’m reviewing songs I’ve made previously and I don’t have these problems with noise and cuts.
?If this is the case, what would be the possible solution?
You could try making a copy of your project and re-applying the playback template to the copy, but I’d be surprised if it makes any difference.
That prueba projects contains 28 instances of VSTinstruments. NotePerformer alone already 10 instances. So with applying the default project template, yes, I do expect an improvement. Please do like Daniel suggests and report back on your experience. Thanks
Hello, after countless tests and as you suggested, I tried the default Note template and I was able to lower the buffer to 68 without noise. Once I did this, I started adding different vsts like Halion, Kontakt and a woodwind synchron until I got to the saxophones and that’s when I had the problem, which makes me think that I have a limit of extra VSTs that I can’t use.
It’s a shame because I’ve spent a lot of money to be able to enjoy the sound when I’m writing music, but as we say in Spain (this is what there is).
At the same time, I find it quite strange that in the previous projects with a buffer of 128 everything worked fine and there are some projects with much more music and more VSTs than in this one? It’s strange, isn’t it? Thank you for your patience and I will continue investigating a solution.
See, in the VST and VSTi world things are not allways as simple as 1 + 1 is 2, but could also be anything else. In theory you have unlimited amount of instruments in Dorico, but it all boils down to how much memory and horse power your computer has. But also on the setup of the VSTinstruments. HALion and HALion Sonic have an option page, where you can configure e.g. the multi processing, i.e. how the plug-in will use several cores in parallel rather than just using a single core. So with this load balancing you get much better results. I don’t know with NotePerformer, it seems it does not have any options in this regards. Also some Vienna plug-ins are known for using just one core. So you could end up in situations where one core is used 100% and you are getting drop outs, while at the same time 7 other cores are just idling doing nothing. So you now see that there is no simple answer to the question of what is the maximum amount of instruments you can use.
1 Like