Jump to content

Search the Community

Showing results for tags 'static noise'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • News & Announcements
    • Product Release Info
    • Frequently Asked Questions
  • Cakewalk Products
    • Cakewalk by BandLab
    • Instruments & Effects
    • Feedback Loop
  • Community
    • Content
    • Tutorials
    • Songs
    • General Music Discussion

Product Groups

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 2 results

  1. Apologies for the length of this post, Its a complex knot and I've been at it a long time. The problem is sporadic and doesn't seem to follow any consistent logic. I'm writing here after several weeks of running the well-beaten trail of this problem with the usual suspects, (sound card and Microsoft support). I have not changed anything significant in the last year but suddenly encountered severe dropout and static about 3 months ago. The static is sometimes only heard and not recorded, the dropout sometimes so severe I get the blue screen ( blue screen report only says Windows stopped unexpectedly). The dropout records as an electric buzz. Here is a short synopsis of questions, a longer description follows: -Could 2 video cards ( both NVIDEA) using the same driver cause this -Could 4 monitors cause this, ( sometimes disconnecting a monitor or disabling one of the cards ( 2 monitors) seems to reduce the chance of dropout ( or red ink in latency monitor) -Could there be a physical electrical problem , (short circuits, overloaded power demands) -Is there an inherent Windows 10 problem with sound recording revolving around the ACPI Driver for NT routine? I am running windows 10 Pro up to date ( latest build) on a SSD drive, projects and VST banks on a separate SSD drive. Board is MSI Z390-A Pro with i7 3.6Ghz and 64 G of RAM. I have a Native instrument controller (USB powered) and a digital piano connected via separate midi cables to a Powered USB bar that is plugged to a USB 3.1 Gen 2 port. I have 2 sound cards ( not using simultaneous, just to say I've swapped them out and the problem persists) Focusrite scarlet 2i2 and EVO 8. I believe I have swapped out every component listed above including the computer. I do not experience this problem with the same sound card connected to my laptop running Windows 10 Home. Windows, sound card drivers, video card drivers and chipset drivers are up to date, ( and throttling is disabled). Power settings are specifically set for sound recording (including disabling USB suspected suspend). This problem persists after deactivating all other unrelated devices, (network card, Realtek onboard sound, wacom tablet, NVIDIA high definition audio) I am turning in circles because behavior is not repeatable. Running a test several times produces a consistent result one day and not another. At times I thought the problem could be electrical, because I often get shocks ( little sparks) in my headphones that cause the mic light to flash which means they are being recorded. But they don't correspond to moments of static while recording and the shocks aren't new. For a short period it seemed as I was getting a correlation between dropout and touching the keyboard or pedal of the piano, but that too was not consistent. Computer and 3 monitors are connected to one bar, midi controller, USB bar, piano and a fourth monitor are connected to a second bar, each bar to separate 3 prong outlets. USB bar has both MIDI USB cables and the NI controller power. Steps taken Starting with the sound card I explored the full range of buffer settings, and then ( with tech support) installed and ran latency monitor several times while recording. I ran the utility many times while experiencing dropout and static, Latency Monitor blames a large spectrum of services and devices on my computer rarely the same. ( dxgkrnl.sys direct X, nvlddmkm.sys - NVIDIA Window, ACPI.sys - ACPI Driver for NT. The ACPI driver is the current darling culprit for this problem on the Microsoft forum, because latency monitor frequently records that it is the highest DPC routine execution time. I am starting to ask the question what is causing the ACPI Driver for NT routine to overrun? On one occasion I tried swapping out Cakewalk ( I have the latest update but the problem has survived at least 2 updates) I ran latency monitor while recording a single audio track in Cakewalk and then in Audacity. Latency Monitor turned red within seconds during the Cakewalk recording which produced static all the way along and dropout that recorded as an electric buzz yet it remained green during the Audacity recording which produced no static or dropout. The latency monitor reports are very similar (expect one is red and one is green) both showing Direct X as the highest ISR Routine execution time and NVIDEA as the most DCP routine execution time with roughly the same numbers. However, these results, just like every other test I run are not consistent, immediately afterwards the cakewalk recording produced a green “suitable for audio” conclusion??? On another occasion it seemed to be the weight of playing back multiple VST banks. I open a new project file and record midi with no problem then add an audio track that produces static while recording but which is not recorded, then I open a full project with multiple tracks and I experience dropout and latency monitor flashes red. Any help with this problem would be greatly appreciated. Thanks
  2. Hi, I started getting crackling static noise during playback after the latest Cakewalk update. Even when only one track is loaded there is still static. Tried uninstalling and reinstalling but it doesn't work. I know it's in cakewalk because playback in sforzando and Kontakt Player is normal. EDIT: Solved it I was stupid and just had to choose MME 32 bit (I am new to this sorry) Edit again: Choosing MME 32 bit solved the issue
×
×
  • Create New...