Gswitz

https://www.sweetwater.com/store/detail/RNDR6--rupert-neve-designs-r6-six-space-500-series-rack This mitigates but does not solve? The idea of more kit to carry is not at all appealing.

I'm sorry for your loss.

Ty for the smile.

I'm standing in a brewery watching someone else on stage thinking being ON the stage might help me a little. All the best Mudgel. Compassion, sympathy, blessings.

Awesome afternoon.

Sounds like a plugin in demo mode to me. Did you recently install a plugin you chose not to buy? Try an empty project our disable all plugins with E key to begin to isolate the impact.

And restart cakewalk after fixing it. This whole troubleshoot had me running in all the wrong directions. I was considering buying a new interface to fix it! Not my best troubleshooting effort.

I know, I know... stop posting! But I learned something! Ok > so earlier after I got it working I added my controller back. Later I unplugged my controller and all was well. After a couple of restarts tho, midi channel 1 stopped working. It was assigned to the unplugged controller in preferences so I couldn't use it for something else. I think this is really the heart of my problem. I use the controller. I get the controller working. I unplug the controller b/c I'm not using it but I don't remove it in preferences. Now midi channel 1 (never used for the controller) gets assigned to the controller and stops being available.

OMG I love playing guitar!!

This morning, I unchecked the devices and deleted the Control Surface reference (which was set to the inputs for the midi 1 track). I clicked Apply and Ok. I re-opened preferences and selected (checked) the midi devices. Apply > Ok. It was not working. I closed and re-opened Cakewalk and it worked!! ? Yay! I went back in added the AlphaTrack and assigned Midi1 to it and it still works fine. All I can tell you is it was definitely messed up before. Seems fine now. There's a bug in there somewhere. ?

For my first year or so with cakewalk I did not use an interface. It is possible. The folks on this forum are mostly interface users because, well, it's better if you can afford it. I think you can sort out your issue but it might take some fiddling. Read Craig's post. I agree with him that you might have some routing situation that is causing two out of sync versions of the same sound to get routed to your outputs.

@synkrotron Exactly. My only problem is using concurrent midi devices in Cakewalk. It seems I can only use one at a time. In other DAWs including Sonar, all three work simultaneously. I think Noel used to use an rme ufx. @Noel Borthwick, do both of those midi inputs work at the same time for you?

I still have old sonar installed. Have you considered trying to open the project with that? -assuming maybe you have that too.

Thanks @synkrotron This gives me hope. Now I super curious how I've messed it up. Do you use a controller device ever? I wonder if that is my problem. I have an alpha track i sometimes like to use. I'll go mess with those settings.

I've been struggling for a time with Cakewalk by Bandlab midi. All of the devices are in the midi list in Cakewalk and checked. I have 2 RME Midi inputs and outputs and a Roland UM One. Strangely, I can only get one to work at a time in CbB but in Mixbus 32c they all work at the same time. Puzzle. It's working properly in Sonar Platinum (just tested). In trouble shooting this, I didn't immediately try another daw. I figured the RME was busted from hauling it all over town all the time. I even ordered a new RME Breakout Cable and then the UM One to try to make it so I could use my FCB 1010 and my GR20 together. I rolled back my rme drivers to prior versions. I messed with USB settings in Windows device manager. I tried resetting the config file to defaults in CbB. Feeling kinda stupid now. ? Could one of you good folks out there who uses multiple midi devices at once in CbB chime in and tell me it works wonderfully for you? Based on this post... https://www.forum.rme-audio.de/viewtopic.php?pid=138451#p138451 it looks like I had become frustrated enough to start spending money by October 11, 2018. Maybe it broke in the September release?

I think yes. Noel has indicated that when it should not be used it will not be used. Which one to use is a tricky question. I default to triangular except for final export. Then powr3 for final export.

For all us regular humans, USB 2 carries enough data to support all our tracks. So is usb c faster? What is the benefit? Just having it work on a USB c port isn't worth it to me.

Jim doesn't deserve the patronizing. (Doesn't need my defense, just thought I'd tell you tho). All of the old-schoolers around here use real-time monitoring when appropriate, but there are cases for through DAW monitoring. If you use your imagination a little, you could think of a few. ? Many of the things you said are true. - Real-Time monitoring is cheap and easy and incredibly effective for lots of things. - Inexpensive interfaces can include fx processing like verb, eq and compression (I have made videos on how to do real-time parallel compression with an RME UCX). - Lots of other equipment matters like Mics, pre-amps and instruments. - Musicianship matters and when the musicians can hear themselves sounding great they'll perform better. None of this discounts the huge value of a good low-latency interface. There are just tons of great things you can do with computers and it is possible to have a reasonably priced computer and interface that makes it all possible. Jim knows more than most about how to make this fun happy world a reality for many people who were not able to achieve this on their own. It sucks to be the old guy who's mad at his computer for ... So much better to be the old guy whose computer enables wild new adventures.

Because they need admin privs to truly know the genius that is Bapu. He's been holding back and they were afraid they might be missing stuff.

After reading this thread days ago I bumped my samples to 192 and my buffer to 48. Then I decided I didn't care and went on with life. Today, I was bouncing a video while listening to playback and I was scratching my head why I heard crackling... duh lol 48 samples while exporting video didn't work. The point is, I hadn't heard it in so long I started trouble-shooting rather than just bumping up the buffer. lol

Sitting in my chair now, I have more latency between me and my amp than 5 ms. Super low latency is cool though. I appreciate it. For me, I love using synths and using tons of voices with low latency drives the processor hard b/c the voices all show up on one core.

Sounds like a scroll wheel spin with control key pressed and no tracks selected with your focus on the quad curve of a track? Lots of times inadvertent moves where the user thinks the scroll just didn't work actually changed an effect parameter value. I could be wrong. Honestly, being able to impact lots of tracks at once is a feature lots of us take good advantage of. What am i saying?... The behavior you see may not be random. Be deliberate as you move through your project. Errant key strokes can really cost you time. One of the most famous ones was hitting the O key instead of the I. O enabled offset mode at one time while I toggled the inspector. Once on, offset mode would totally confuse you. .. Offset mode has been unmapped from the O key now.

Gone gigging?

Quantization is something i avoid.