Jump to content

Promidi

Members
  • Posts

    2,983
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Promidi

  1. Yeah, but we are dealing with Cakewalk developers. Let me know what happens if you ever need to contact Cakewalk support and you disclose to them that you're still on an unsupported OS. Ok, they will probably still accommodate you (because that's how I think they roll) , but you’ll probably still get the lecture....
  2. Well the benefits of Windows 10 do outweigh the issues. Besides, what do you think Microsoft will tell the Cakewalk developers if the Cakewalk developers needed support from Microsoft for an unsupported operating system. This is why the Cakewalk developers say that, even though Cakewalk by Bandlab will technically run on Windows 7 and 8, Cakewalk by Bandlab is no longer supported on anything less than Windows 10. Something to consider if you are still run on an unsupported operating system.
  3. The last time I had an issue with a Windows 10 update was back in 2016 with a modified PCR-800 driver. And that was easily fixed by reinstalling said modified driver. I am on 20H2 (I have not been offered 21H1 as yet) All other times, for me, Windows 10 updates (feature and quality) have gone smoothly....
  4. Can you post the KB number of the specific update that you believed caused the issue?
  5. Probably going to need more information. Are you using the latest BBC symphony orchestra? Which version of Cakewalk? (Numerically) What are your PC specs? OS, Audio interface, Sample Rate, Bit Depth, Buffer Size?
  6. I wonder if this is because the feature update reinstalled a generic display driver. Did you try reinstalling your display drivers prior to rolling back to 20H2 (or whatever you had before)? Remember, feature updates ignore the group policy settings to tell Microsoft to ignore drivers. I am sure other users have updated to 21H1 where this has not happened.
  7. I've noticed that when one opens a project and that project opens further along in the timeline (say at measure 100), tempo inspector is still displaying the changes starting from the first tempo change (at measure 1). Also, scrolling along the timeline in your project does not move the tempo inspector to match. Is it possible we can have a setting to enable the tempo inspector to optionally follow the scrolling in the project track view. Also, it is possible for the tempo inspector to highlight (using a lighter grey or a colour) the current tempo change (which would also move through the tempo changed upon playback).
  8. Personally, I would just write a CAL script to do this...
  9. More your Now to where you want your starting point to be. I think opening a MIDI file, this is at the start. Enable the following in the track view menu: Options “On stop, Rewind to Now Marker” “Stop at Project End”
  10. Yeah, I have reassigned many of my key bindings. The point is, that marker navigation can be assigned to any key combination.
  11. What I have done is created keybindings in the Area: Global for Previous Marker and Next Marker. My Keyboard shortcuts are Ctrl+Left and Ctrl+Right respectively. Of course, being in Area: Global, these will work on any screen.
  12. This is why I still use the Yamaha SW1000XG (in another PC connected via USB to MIDI)..... no VST can touch it (probably never will)...
  13. Yes. With the smart tool selected, right drag a rectangle around the notes you want to change, then do the Process | Length
  14. One way I can think is to selected the notes you wish to change, then go Process | Length, and reduce just the durations by 50%
  15. Promidi

    Moving only one track

    You wouldn’t have Ripple Edit enabled would you?
  16. Do you have KB5003214 installed by any chance? Windows Update history may not display the knowledge base number Start + Run > appwiz.cpl View installed updates > scroll down to “Microsoft Windows”
  17. There are many variants of MP4 files. Maybe this is just one of those variants that Cakewalk can’t deal with properly. One thing you might want to try is to use a video converter to recode the resultant MP4 file after the rip. Another possibility is that the MP4 might have a variable bit rate. If that's the case, try converting the MP4 to a constant bit rate rather than variable.
  18. Have you tried uninstalling and reinstalling Melodyne?
  19. Which version (numerically) and which iteration of Melodyne do you have?
  20. I believe you might get what you are asking by inserting an Cakewalk FX Velocity in the Effects Rack of the MIDI track that your midi keyboard is triggering. With this you can set the resultant velocity to any value. All notes sounded will be that value - regardless of actual velocity played. Of course there are many other things you can do with Cakewalk FX Velocity, but I'll leave you to explorer those.
  21. Sounds like your mouse might need replacing. Or maybe see if changing some settings in mouse properties might help Start + Run (or Winkey + “R”) > main.cpl As regards deleting the markers, this would have the net effect of deselecting everything. If you’re ok with this, then you could keybind a single key press to “Select None”. Personally, I have actually set “Q” as a key binding for this.
  22. What driver mode are you using? (ASIO is preferred). What is your buffer size?
  23. One issue I had with a previous version of UVI Workstation is it would not remember the last opened patch folder for Gospelmusician's Bluebeast. Now it does. I think this issue was resolved a few updates back. I am now on UVI Workstation 3.0.22. It would be nice if UVI told us which actual issues were introduced, and then subsequently resolved.
×
×
  • Create New...