help

Hi, ive just updated to the latest maintenance version, i am recording from a keyboard into my interface and each time i record, half way through i get the message “Recording error : Audio drop-out detected” this stops the recording, i have never had this issue since buying CB8, i did however reset cubase to default 2 days ago, but as far as i know it has always been default? is this a CB issue or can someone guide me in the right direction please

the interface is Steinberg CI1, asio driver is Yamaha Steinberg, windows 7, korg pa600

again i stress i have never had this issue until the update today ??

Hi,

Are you recording MIDI or Audio? Try to change you Buffer Size, or ASIO Guard settings. Make sure, your HDD is Fast enough, and there is enough free space.

Hi Martin, i’m recording mono audio, , i’ll check what you have just said thank you… but what sizes should i be looking for?

this is what i have
ScreenHunter_11 Sep. 13 13.36.jpg

Hi

I was also getting these audio dropout error messages. Never happened with Cubase 7.5

Try the ASIO Guard with High setting.
It solved the audio dropouts for me.

hi, this is getting worse and worse, i’m getting drop outs whilst playing my Impact lx 49… ? this is getting to much… once again i stress this never happened until the last update… it’s becoming so frustrating playing live, almost complete and boom… dropout…
please help

Hi,

Do you have the latest drivers of your sound card, please? Could you try to disable (or trash) Preferences?

What about your HDD space? Is it more than 10% free?

Could you try to use LatencyMon, to find, if there is any system issue?

Hi Martin, i’m using the steinberg/yamaha driver that came with the Ci1, i did reset the preferences and i un-installed some trial vst i thought maybe causing the issue, but to no avail… even when not recording and just playing live i am getting a huge quick type of buzz then a drop out for a second or 2 and then it’s back in???

edit

500gb ssd 90% free

I don’t know, which driver version is currently shipped with CI1. Download and install the latest version, please.

Also try the MonLatency, please.

hi, i just ran latencymon, it said the system was unsuitable, i then followed a guide on latency drop outs which suggested i alter some settings in power management which i did and now latency mon reports that the system is still unsuitable, i’ll check for the driver

installed driver same report from laencymon?

What is the report, please?

You could try to enable the:
Activate Steinberg Audio Power Scheme
In the Device settings.

hi, lattency report attached

__
cant attach file?


CONCLUSION


Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 0:01:09 (h:mm:ss) on processor 1.

\


SYSTEM INFORMATION


Computer name: SWAN-PC
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: Inspiron N5050, Dell Inc., 01HXXJ
CPU: GenuineIntel Intel® Core™ i3-2370M CPU @ 2.40GHz
Logical processors: 4
Processor groups: 1
RAM: 8100 MB total

\


CPU SPEED


Reported CPU speed: 2394 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): 2380.589918
Average measured interrupt to process latency (µs): 4.834279

Highest measured interrupt to DPC latency (µs): 133.419086
Average measured interrupt to DPC latency (µs): 1.688818

\


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): 0.0
Driver with highest ISR routine execution time:

Highest reported total ISR routine time (%): 0.0
Driver with highest ISR total time:

Total time spent in ISRs (%) 0.0

ISR count (execution time <250 µs): 0
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µ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): 47.854637
Driver with highest DPC routine execution time: tcpip.sys - TCP/IP Driver, Microsoft Corporation

Highest reported total DPC routine time (%): 0.000463
Driver with highest DPC total execution time: tcpip.sys - TCP/IP Driver, Microsoft Corporation

Total time spent in DPCs (%) 0.000682

DPC count (execution time <250 µs): 226
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 0
DPC count (execution time 1000-1999 µs): 0
DPC count (execution time 2000-3999 µ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: msmpeng.exe

Total number of hard pagefaults 3
Hard pagefault count of hardest hit process: 3
Highest hard pagefault resolution time (µs): 4484.706767
Total time spent in hard pagefaults (%): 0.001755
Number of processes hit: 1

\


PER CPU DATA


CPU 1 Interrupt cycle time (s): 0.217862
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): 47.854637
CPU 1 DPC total execution time (s): 0.001885
CPU 1 DPC count: 226