Jump to content

Tim Flannagin

Members
  • Posts

    41
  • Joined

  • Last visited

Reputation

11 Good

About Tim Flannagin

  • Birthday June 10

Recent Profile Visitors

1,794 profile views
  1. Hello Heinz, This seems to be workable, however is a departure from what I'm used to. I will give it a try. Thank you for your effort!
  2. Can't wait to see what you've come up with. Danke!
  3. That would be fantastic! That is the missing piece for me.
  4. Obviously the best solution would be for Nektar to offer deep integration with CbB. In lieu of that however, I've had to build my own using a combination ot P6 Macros and AZ Controller.
  5. I have finally set up my Nektar P6 to run Cakewalk in a good way. However, there is one exception that would be immensely helpful for us ITB guys. I would like to see a shortcut (key binding, alt + key, don't care) to open the Instrument VST on a selected Instrument Track. It would really make the world a better place. Currently the only way I can find to do this is by clicking the mouse over the Instrument Icon. This means that it's one of the few things I can't assign to a controller function.
  6. I just wanted to thank the Bakers and Noel for all the hard work. About a year ago, I gave up on Cakewalk. After working with all the usual helpers on this forum including a great list of suggestions from Alexey, I was unable to get CW to run in a stable way. As happens about yearly (as far as I can tell) I got the urge to try CW again. I installed the latest version (2020.01 at that time) and without much trouble, I was able to begin working in a stable environment. I have updated as they became available and have been continually amazed at the quality and improvements being rolled out. I did notice on the latest update that it was necessary to tweak the buffer settings on my Delta 1010LT initially to stop the program from experiencing Audio Dropouts, but interestingly enough, returning it to the original settings later seemed to work as well. Not sure what was going on there. Bottom line is that CW is working well on a 2011 vintage Dell T5400 2 X Xeon Windows 10 system that couldn't run it reliably before. On another note, thanks for the Arranger function! This is very similar to the "Regions" functionality in Reaper and one of by favorite things to use. Keep up the good work and thanks again!
  7. Drivers for the V Studio 20 can be found here: https://www.roland.com/us/support/by_product/v-studio_20/updates_drivers/ How to hack the Windows 8 driver to work in Windows 10 http://forum.cakewalk.com/How-to-use-V700-win-8-driver-in-win-10-also-applies-to-some-other-Roland-drivers-m3206046.aspx I'm using mine with Cakewalk by Bandlab on a Windows 10 laptop, and it works great.
  8. +1 on this statement. There are so many configurations out there that one man's fix might be another's downfall. I agree with the "proceed with caution" sentiment. In my case, the DAW machine in question is a hodgepodge of parts accumulated over several years. Most are obsolete in one way or another. That's just how I roll. So to the noob, proceed with caution and most of all, make sure you understand what was said. Perception is a funny thing with reading these suggestions! Make sure you know what was being suggested, but perhaps even more than that, consider the context of the suggestion.
  9. Good thread. I wasn't aware of the Microsoft real time scanning thing. Changes shall be made this afternoon. While on the subject of Anti-Virus / Malware scanning programs, if you are running McAffee or Nortons, just get it off your machine NOW. You don't need it. These programs are worse on a DAW machine than an actual virus! I had issues all last year with audio dropouts and the machine bogging so badly that the screens would stop updating. I made 4 changes that completely changed the stability of my machine when running CW. Removed ALL McAffee products and started using the build in Windows anti-virus solution. Removed ALL Nvidia drivers from my machine and reverted to using the stock Windows display drivers. This includes removing that pesky high definition audio driver that Nvidia installs. I was running a wireless NIC in my machine because I was too lazy to run a hard wire to my building NIC. I removed the wireless card along with all of the drivers and reverted to using the built in NIC on a wired connection. I swapped out the system drive for an SSD and rearranged my files so that the CW audio has its on dedicated drive. Bottom line is that I never have an issue now. After swearing that I'd never go back to CW, here I am. My changes along with the improvements made to the program by the Bakers in the last year have completely changed my mind. My specs are in my signature and you can see that I'm not exactly running a state of the art rig, but it's back to being rock solid with these few changes.
  10. Guys, I appreciate all your help. I've either verified or implemented most of the changes you've suggested along with going through Alexey's recommendations. I've used Latency Mon and gotten validation that the machine is good enough to run as a Daw without dropouts. I've run a project with resource monitor up, and never reached over a 50% CPU load. The downside is that on the test project, I still have the issue with little improvement. So at this point I'll conclude my effort and carry on. Again, thanks for the help. I've learned a lot from you all this week.
  11. Thank you for the information Alexey. I will look over your list this weekend and see if there is anything I've missed. At this point, I suspect that it's related to the multi-cpu configuration I'm running. However, that is purely speculation after trying a multitude of other tweaks. I don't see my hardware configuration changing anytime soon, so the answer at the end may be that I stick with the DAW which can best take advantage of it.
  12. Thanks for the feedback Scook. I'll give these suggestions a go.
×
×
  • Create New...