Andres Medina

According to your image, it seems that there are no tempo nodes until measure 33, and it seems to be the same original 130 bpm tempo. Same for measure 34. That's why the left pane does not reflect your changes, as there are none? Measure 69 shows a tempo change to 125.02, but it's out of the range in your pic.

I have had the same issue. Mind that your BT headphones travels on a BT connection, that is carried from your Laptop tiny audio card. And CW is not at its best running in such configuration, as the above notes explain. However, your main audio card should be a proper audio card with proper drivers in order to take full advantage of CW - But such audio card is not a bluetooth device...! Provided that you got a proper audio card, one solution is to buy a Analog to BT converter, which allows you to transmit your analog audio via BT to your BT headphones. In this scenario, you can hear all the audio coming from the audio card, but as stated above, with a noticeable delay. In some stages of music production this is a major inconvenience, like when you are playing your keyboard or autidioting audio in real time. But for other stages I find it irrelevant: mixing i.e. , if you are not adjusting things in real time. I already work this way, and enjoy a very good pair of Noise Cancelling BT headphones, which completely isolate me from the external noise - with the above limitations.

I use google drive for all tasks that are CW related, and haven't encounter any uses, BUT the audio data is pointed to a drive that is outside Google Drive, meaning that the project file is cloud based, but the audio is not. I had the problem you mentioned, and at the time it was suggested that writing audio files in the cloud was a slow process, as the service has to synchronize them, and it takes time, so, eventually it leads to errors. I adjusted my workflow so that after each session I make a backup of the session - audio included - , in the cloud. So far, it works fine for me, but I guess everybody has its own preferred workflow.

Happy to help...! I had sort of a nightmare in my first attempts to run video in CW - not a CW fault by the way: video+audio is tricky at first. I troed Cubase for a while and was even worse. Never got the video to run at all. Look, I tried a number of codecs. Mp4 is a wrapper. The actual codec is very important. AVi is super heavy, but at least it made your video run...! After many many trials, I found H264 is a very good choice: it produces a small file and very good video resolution, with little load in your system. Just re-export your video file using any free video converter, and make sure you select H264 codec, keeping all other video settings the same. If you need more info, feel free to ask.

Sorry to hear that. I don't have more answers, but one more question: What type of video are you trying to run? I have no trouble at all working with video, but only if I use H264 video codec. Other formats were problematic inside CW. I usually re encode the video to H264 if I'm not able to ask to the video producers to export so beforehand.

I agree: in addition, try inserting the video in a blank project (no VST's), and see if starts immediately.

Although a little tricky, OMF files were designed to solve this problem. It's old but if handled properly it works just fine. Reaper must have the ability to export it's file as OMF anyway. Not sure if it does. Once exported, just open the OMF file in CW and you'll get all the tracks and its clips in their corresponding positions in your timeline. But basically you have to build up your session from this basic scratch . Here is the info in the documentation, if it helps: https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Exporting.11.html

I have used OMF's before, and it's tricky, but once you get it right is very convenient if you want to preserve different takes and clips and their corresponding places in your timeline. If your Protools session is comprised of only final takes, I guess the method OutrageProductions outline may be best. Tip: be sure to ask for the original tempo of the protools session, as you need to use the same in CW.

I guess it will be common practice in a few years, thanks to AI, but at the moment I have no notice of this kind of automated intelligent workflow. There are a few smart tools out there, but what you expect is way more complicated.

It means that your project had those 5 plugins loaded, but CW is unable to find them now. Why? you could have moved them to another location, or they were uninstalled, or your plugin manager menu is not including the path that contains those plugins... or other issues. You could rescan your VST's and make sure that you include the folders where those 5 plugins are installed. It usually solves the problem.

I know how frustrating is to get sucked into all this technical tangle... but, really, is very important that you get a proper audio card and it's native driver. This issue comes again and again in this and other forums.

No difference that I'm aware. Just different signal path. Regarding "sends": they are extremely useful if you understand the way they work. Worth checking the documentation!

I did have this same issue, but with Steinberg products. They install the generic ASIO driver mentioned, and is not that easy to find. CW finds this driver and assumes it's the right one to use. See this thread to erase any unwanted ASIO driver: https://helpcenter.steinberg.de/hc/en-us/articles/206633450-How-to-delete-old-ASIO-device-entries

As I understand, the PRV Snap only provides the option to configure a different snap resolution from the track view. Say in track view you set snap to measure, and in PRV sanap to quarter note. But the main Snap button must be engaged.

Right, not sure if CW ever dimmed the other tracks while soloing? I get the greyed out only when archiving tracks, on the archived track itself.

... but just noticed that if you move a note in PRV by clicking and then slowly moving the mouse, the snap to grid seems to be disabled temporarily. Not sure if this is intended behavior or not.

Working as expected here. Check this article included in the documentation: https://legacy.cakewalk.com/Documentation?product=SONAR&language=3&help=EditingMIDI.16.html

mmm, I don't get the greyed out audio tracks when soloing. Neither the midi tracks...

It seems to me that your buffer size is too low. In my system, any value under 128 click and pop. 256 is just fine, good balance between low latency and sound stability.

I have had that same problem. I got help to sort it out. One of the proposed solutions would work for you. See this thread:

Thanks! Very cool. A step ahead from our CW current Arranger Mode. I like it!

Yeah, I don't remember either! Hopefully it will be adressed at some point!

Good point. I wish I remember which DAW had it... I heard Hans Zimmer talking about it in a Master Class. I think it was Cubase but you are familiar with it and seems to lack this one.

Not quite... workspaces allows you to "filter out" modules, functions, etc to declutter the UI. This other function allows you to create different versions of your music inside the same file. Steinberg Dorico has it - but this is a notation software, not a production tool as CW -, and is really nice to work this way: each piece of music is independent from the others, you just "recall" it with one click. Someone mentioned "scratchpad": not familiar with, but sounds like the feature I'd like to get from CW.

Sorry to hear that! Yes, something is not working properly, and the way your system behaves is not normal. Hope this tests help the developers to understand what is going on, as it seems definitely to be a bug somewhere...