Helos Bonos

Did you try bypassing all plugins? Can you post a clip of the distorted audio?

I just discovered you can adjust the zoom amount for smoother zooming with the scroll wheel but requires more spinning of the wheel: Track menu item>Options>Mouse Wheel Zoom Options...>Zoom Factor>Horizontal But it doesn't fix the PRV zoom. Apparently there's no connection between the two operations.

I am the OP on the subject (as of late at least), as you may already know. This doesn't solve anything but just to put it out there, I have used another DAW called Waveform 10 and the timeline zoom vs the PRV zooms are actually both completely different operations (which is even more frustrating than different zoom levels for each). So maybe it's just inherent in DAWs that these two seemingly related operations are completely separate.

@MediaGary @bitflipper Thank you guys for reminding me about LatencyMon. I ran it and I'm sure it will point me to the direction to solve all my problems. Problem is, I'm not that great with computer stuff so I don't quite understand everything in the results. I'll paste the text here and hopefully you can decipher it for me. FYI, I was not doing music during this monitor. Not sure how big a difference that makes. If you want I can do it again while recording. But I think this shows that I have an existing problem recording or not since the interrupt and DPC routine meters are maxed out to the red. But maybe it's from running for almost 2 hours? Anyway, thanks. _________________________________________________________________________________________________________ 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 or more DPC routines that belong to a driver running in your system appear to be executing for too long. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. 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 1:37:27 (h:mm:ss) on all processors. _________________________________________________________________________________________________________ SYSTEM INFORMATION _________________________________________________________________________________________________________ Computer name: ROY-PC OS version: Windows 10 , 10.0, build: 18363 (x64) Hardware: HP Compaq Elite 8300 CMT, Hewlett-Packard, 3396 CPU: GenuineIntel Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz Logical processors: 8 Processor groups: 1 RAM: 16258 MB total _________________________________________________________________________________________________________ CPU SPEED _________________________________________________________________________________________________________ Reported CPU speed: 3392 MHz Measured CPU speed: 10 MHz (approx.) 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. WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature. _________________________________________________________________________________________________________ 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): 48161.70 Average measured interrupt to process latency (µs): 4.266973 Highest measured interrupt to DPC latency (µs): 48141.30 Average measured interrupt to DPC latency (µs): 1.145050 _________________________________________________________________________________________________________ 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): 171.545401 Driver with highest ISR routine execution time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation Highest reported total ISR routine time (%): 0.013799 Driver with highest ISR total time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation Total time spent in ISRs (%) 0.023949 ISR count (execution time <250 µs): 1747633 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): 27799.683373 Driver with highest DPC routine execution time: tcpip.sys - TCP/IP Driver, Microsoft Corporation Highest reported total DPC routine time (%): 0.219153 Driver with highest DPC total execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation Total time spent in DPCs (%) 0.359287 DPC count (execution time <250 µs): 134956854 DPC count (execution time 250-500 µs): 0 DPC count (execution time 500-999 µs): 881 DPC count (execution time 1000-1999 µs): 12 DPC count (execution time 2000-3999 µs): 2 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. Process with highest pagefault count: none Total number of hard pagefaults 0 Hard pagefault count of hardest hit process: 0 Highest hard pagefault resolution time (µs): 0.0 Total time spent in hard pagefaults (%): 0.0 Number of processes hit: 0 _________________________________________________________________________________________________________ PER CPU DATA _________________________________________________________________________________________________________ CPU 0 Interrupt cycle time (s): 226.896236 CPU 0 ISR highest execution time (µs): 171.545401 CPU 0 ISR total execution time (s): 11.159355 CPU 0 ISR count: 1741371 CPU 0 DPC highest execution time (µs): 3409.998821 CPU 0 DPC total execution time (s): 65.697154 CPU 0 DPC count: 31090621 _________________________________________________________________________________________________________ CPU 1 Interrupt cycle time (s): 121.861007 CPU 1 ISR highest execution time (µs): 90.525649 CPU 1 ISR total execution time (s): 0.041368 CPU 1 ISR count: 5999 CPU 1 DPC highest execution time (µs): 435.723762 CPU 1 DPC total execution time (s): 10.734181 CPU 1 DPC count: 10730147 _________________________________________________________________________________________________________ CPU 2 Interrupt cycle time (s): 152.916420 CPU 2 ISR highest execution time (µs): 32.415979 CPU 2 ISR total execution time (s): 0.001424 CPU 2 ISR count: 233 CPU 2 DPC highest execution time (µs): 1417.358196 CPU 2 DPC total execution time (s): 21.144566 CPU 2 DPC count: 21806312 _________________________________________________________________________________________________________ CPU 3 Interrupt cycle time (s): 135.026555 CPU 3 ISR highest execution time (µs): 9.152123 CPU 3 ISR total execution time (s): 0.000148 CPU 3 ISR count: 30 CPU 3 DPC highest execution time (µs): 27799.683373 CPU 3 DPC total execution time (s): 12.141802 CPU 3 DPC count: 12096678 _________________________________________________________________________________________________________ CPU 4 Interrupt cycle time (s): 123.335584 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): 419.904481 CPU 4 DPC total execution time (s): 16.663639 CPU 4 DPC count: 16989204 _________________________________________________________________________________________________________ CPU 5 Interrupt cycle time (s): 122.607718 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): 420.136203 CPU 5 DPC total execution time (s): 11.833393 CPU 5 DPC count: 11667294 _________________________________________________________________________________________________________ CPU 6 Interrupt cycle time (s): 117.999810 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): 432.916274 CPU 6 DPC total execution time (s): 16.407517 CPU 6 DPC count: 16761656 _________________________________________________________________________________________________________ CPU 7 Interrupt cycle time (s): 117.095633 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): 433.693396 CPU 7 DPC total execution time (s): 13.438076 CPU 7 DPC count: 13815838 _________________________________________________________________________________________________________

@winkpain Well, you just solved that problem! But you know, why wouldn't CbB just give you a PRACTICAL color combination by default and let you muck it up if you choose rather than giving it to you mucked up so you have to fix it??? I notice a lot of defaults are like this and this is not only a CbB issue. Reaper is guiltily of this as well.

So I did finally get the legacy driver installed but my issues remain. Latency (even when buffer size is at 64), audio dropouts, horrible random glitch noises on my audio clips that seem to be embedded in the clip (I move the clip around on the timeline and turn effects on and off).

@Jon White Good idea but na.

A bit off topic, I might create a post in the feedback section but I find it very annoying that the muted notes in PRV are almost invisible. Like they couldn't just grey out the notes? It's just a very light grey outline with 100% transparent note. Find the muted notes:

@MediaGary Someone else also suggested that Latency Monitor program on another post of mine for a different (related?) problem. I forgot I actually have it on my PC. I'll run it and see if I can get some clues. @bitflipper This seems to be a new problem. I havne't touched the mic or any cables. Actually, I have maxed out the buffer size to 1024 and still hear it in places. I don't think this is a coincidence but I notice the noise at transitions of my song. Chorus to verse to example. Right around the transition. Here's anothing thing I noticed by accident: I opened up my preferences to check on my buffer size, didn't change anything (buffer at 64), hit Ok. Now the latency is gone (5.6ms at least). But after a few seconds, it creeps back. So I'm still getting latency even at a 64 buffer. And here is another problem that I'm sure is related but I was going to do a separate post on it. And this is not a CbB issue. I've had this problem for a long time even with Reaper: The audio will go silent (during playback or recording) and there will be a high pitch "peep" sound around 10k for a second or two, then resume playing or recording. This has been plaguing me for a very long time and I've not been able to figure it but I'm sure all my latency, audio dropouts and this glitch noise are all interrelated. There has to be one culprit causing all of this. I need to get it figured out soon as I'll be tracking a client when this quarantine thing cools down.

Yeah, I'm sure that's what it is too. Hearing protection failsafe. I don't think I was doing anything out of the ordinary. I was just going through a bunch of different vocal tracks to align them and couldn't get any sound out of this one track. I actually have this latency monitor software! I have to run it and see if it gives me any clues. That was a good video, thanks. I"ll have to go through my device manager to see if there are any power sucking processes going on.

I think this might be related to my latency issue. Or my audio drop out issue. Or maybe everything is related. I don't know if it's even Cakewalk, my computer, or my MOTU audio interface. When I record audio (my horrible singing) there is a crunchy glitch that shows up in pretty much the same spots on my timeline. I've always thought it was just the crunchiness that comes with recording at too low of a buffer size (64) trying to avoid latency. But it seems to be embedded in the audio clip. It's at the same spot even if I move the clip up or down the timeline. And the noise is there with or without effects. I tried bouncing a short selection to mp3 to no avail. Once I got an error message, the second try, I it bounced to a silent mp3 file. So I ended up recording it from my Voice recording app built in to Windows 10 in m4a format. I'm attaching it here. Recording Glitch.m4a

I think I remembered the real problem I was having with zooming. It's zooming on the piano roll. I go from this view: To this view: In ONE tick of my scroll wheel. That MIDI controller looks like a nice toy but since I'm limited on desk space and on monetary funds, I think that $200 might be better spent toward a Presonus license. It's looking better and better with every session.

I don't think so. It was just a regular vocal track; same as the adjacent tracks that were not giving me any problems.

Wow. I can't seem to get through one session without issues. One of my vocal tracks went silent. It's the same stuff/settings/audio/plugins as my other vocal track but this one track won't output any sound; shows -136dB on the meter; the Global Input Meter shows Red and the clipping LED on the EQ and on the Tube modules in the Prochannel. Weird thing (actually nothing is weird anymore) when I try to screenshot the red LEDs, as soon as I click my screenshot software, the red lights go out. Also, if I click one module on or off, I hear a lout clicking sound. Also, the meter on that track is maxed out so there is some loud (inaudible) noise that is causing the clipping and it must be so loud that it is muting the track somehow. On Reaper if something gets beyond a threshold of loudness, the track mutes but with the mute button so I can unmute it after I figure out what the problem is i.e. a delay feedback gone rogue. I was wrestling with this issue for a while until I just gave up and closed the session and reopened it. Now it seems to be working. Why do I keep having these interruptions in my flow. If I had a client here, it would have ruined the session.

I'm not a hardware guy but I'm digging this. I might get one. Thanks. But wait. Can it control the full timeline with audio and MIDI or just the MIDI window?

I might have to get into this habit.

Oh, yeah, that is very smooth zooming and scrolling. Mine seems to jump from level to level rather than a smooth graduation. Another thing I forgot to mention are the microscopic scroll handles! I'm zoomed out all the way and the handle is still tiny. WHY??? On every other program (I'm not talking DAW, I mean every other type of program) , when you zoom out to see the entire project, the scroll handle lengthens so you don't have to mouse to the other side of the screen to grab it or to search for it with your eyes.

Thank you for this. This seems unnecessarily confusing. CbB shouldn't assume everything is stereo. Why can't it just be all mono inputs and if I have a stereo pair, just connect to 7 & 8 as I normally would anyway?

Jonathan, how can I change the names to friendly names if CbB doesn't show all the inputs? I really hate having to figure out which physical input goes to which discretely named input labeled by CbB. I.e. If I want to record something from input 6, I don't want to have to think is it Analog 5 right? Analog 5 stereo? Analog 7 left? Odd? Even? Whut? I just want to see the number that matches with my input channel and get on with making music. I don't have this problem in Reaper or Waveform 10. I'm sorry. I don't know why it's double pasting my images. When I tried deleting it, it messed up my post.

I'm deeply focused on my editing which requires a lot of zooming in and zooming out which I also use to slowly move my way across the timeline by zooming in on one side and zooming out on the other. When I have to look at my keyboard to make sure I'm hitting the Alt key and not my Ctrl, Windows key, or space bar which I do half the time, it takes my sight off of the clip I am editing. Then I have to find my place again. And sometimes if I hit the alt key instead of the space bar, then the menu drops down on top so I have to get rid of the menu in order to continue to play. It's maddening, distracting, and time wasting. Is there a way to horizontal zoom with scroll button only?

AWESOME!!!! THANK YOU!!

I've been complaining and ranting a lot on here with every problem I encounter but while there are many good things I like about Cakewalk, one thing I would like to mention is how great this support forum is!!! Man, it is so nice to know that when you post a problem, there are answers and great help not long after. Thank you guys!

Is there a setting so that whenever I create a new track the output will default to my MASTER BUS that I've created rather than my stereo outputs? I have to manually do that every time and sometimes I forget and notice it later.

Does it have to be in like a smile position? Or a grimace? Kissy face? 😄😄

This post has nothing to do with the software; it's about the forum notifications. When I click on the notification bell, I have a number of bolded notification that are unread. I'd like to read all of them but after I read the first one I clicked on and go back to the bell, all the other notifications are unbolded so I don't know which one I've already read and which ones I've not read yet. Am I doing something wrong? Again. Is there a setting to fix this?