Jump to content

Will.

Members
  • Posts

    2,617
  • Joined

  • Last visited

Posts posted by Will.

  1. On 10/8/2020 at 10:05 AM, Simon Wilkinson said:

    I posted this issue here about problems when write automating envelopes using a control surface and getting a smooth envelope:
     


    It would be great to have the option to select a default envelope node style when recording write automation (e.g. jump/linear/fast curve/slow curve). Or at least to be able to highlight multiple envelope nodes and bulk change them all to a certain type.

    At present it's almost not worth using a control surface for this sort of thing and would make workflow so much easier!

    It also seems to show there's a bug when you right click to drag select a bunch of nodes and then press delete on the keyboard. It doesn't delete all the nodes you've highlighted and leaves a few behind that you have to right click select again and press delete a 2nd time.

    Isn't there a setting under control surfaces in preferences for this? I think cakewalk sets this to default for "surgical" writing purposes. 

    Will have to look into this when I'm at studio again. I don't have a control surface at home. 

  2.  

    On 10/11/2020 at 6:26 PM, FRESH BEE said:

    could you add a mic fader  i know people use usb mics and just getting to music recording and cant afford a interface.

    it would be a great feature for the daw

     

    The "mic fader" you're looking for (assuming you're using a USB mic as described in your post,) is in your windows sound tab. 

    Look it up. 

    Get a volume that you like and keep it there. 14% should be enough if you're on windows 7. Have no idea if windows 10 fixed their issue and it's compatibility with those usb mics. 

  3. On 10/11/2020 at 11:33 PM, Dav said:

    I have also found a bug wherein you can't open cakewalk after closing it and putting the system to sleep, or at least I believe these are the circumstances which cause this bug. Cakewalk won't open from a shortcut, a pined taskbar shortcut or from the start/search bar. So I used the last resort option to open it with the (sigh) bandlab assistant. This time I got an error message (see attached image below).

    Another problem I have is that often projects wont open and will just freeze up cakewalk and crash, this is really annoying because I have most of time (I'd guess around 80% of the time) I have to open my projects in 'safe mode' and just say  "yes to all", re-save the project without changing anything and reopen the project in regular mode. Idk why this is happening but this is also irritating.

    BandlabBUG.PNG.68763a6f1194740b2960ff20b9eb5b06.PNG

     

    This is purely a windows issue. I have a friend with basically the same specs (just two gen lower.) Normally what happens is, for some reason when the DAW does crash (which is often caused by a free or old 3rd party plugins) windows keep a copy open. 

    To get rid of this.

    Ctrl+Alt+Del will bring the task menu, where you'll find Cakewalk to still be open under the progams tab. 

    On 10/11/2020 at 11:33 PM, Dav said:

    Cakewalk does not run at smooth fps (I think it only runs at 30fps), most DAWs runs at (at least) 60fps or more.

    Automation of parameters are not smooth at fast tempos and it IS audible. They are smooth at slow tempos, but on fast tempos (more than 150bpm) you can see knobs instead of of moving smoothly, follow a S&H of the automation curve and often misses quick changes in the automation. This is the worst thing about cakewalk and (along with these bugs/problems) is the major reason why I am considering changing my DAW.

    Make sure your playback and hardware buffer size are sync'd with that of your interface. By default cakewalk sets this to 256ms  both playback and hardware. 

    Lastly: Make sure windows is up to date. Follow steps below.

    Follow step 2 and 4 - especially if you're running Windows 10 build 2004 (Which is also the latest version.) It helps a lot. 

  4. 8 hours ago, Glenn Stanton said:

    may use the surround features? i like to use a 2.1 surround setup where the LFE is ignored. this way all tracks and busses going into a surround buss can have their width, depth, etc positioned. for example - i have a mono or stereo track feeding into a stereo buss, the separate busses feed into a surround "instruments". i could simple for from the track to the instruments buss to directly position it or add another buss (if say i have a pairs of acoustic guitars left and right comped which also need positioning in the surround space). tweaking the HF to changes it's apparent vertical position...

    image.thumb.png.56d7600c7789fbdec76e37a529b6d844.png

    Totally hear you Glen. My concern with this is (as I've said in a previous thread on this,) that it does not project the image the same for all forms of devices when using a surround bus in that sense. I've experiment with it before, gave it to a client and certain elements didn't come through on a device she was listen on. 

    That's my issue with using a surround bus, with this idea. Most clients get's their tracks played on radio. Plus, i don't have a surround setup to hear the image in - so i'm a bit cautious and staying away from that buss, after one incident. 😅

  5. I'm going to take another approach on this idea - maybe it'll generate some kind of positive conversation on it. 

    Imagine being able to change the stereo image manually to your desired liking from mono to stereo throughout the entire image field on an Aux or Bus track without the use of a "width/widening" plugin.  

    The ability to move an effect/file source straight on the track itself (mainly effects) from mono to 10% all the way 100% Stereo or "VICE VERSA" in the stereo field - especially on reverbs that don't have a "stereo" function, such as waves Rverb; H-Reverb and free reverbs like, Cloud Seed and the Leslie Sandford Reverb

    The channel tool is awesome, so is the Sonitus phase plugin, but I think this will help a lot of producers with processing issues, as the use of these plugins won't be a need if it gets implemented in the DAW self. 

     

  6. It all comes down to one thing everyone is saying ~ "comfortability." Where do you feel most comfortable -- at home right? If you don't feel comfortable with the DAW you're using, it will never become "The Best" DAW. The rest will be second nature. 

    Like Mr @Craig Anderton said, it's like a car.  If you over-rev your car, you will damage the piston and valvetrain, and if you don't know how to read your gas/petrol gauge, you will stuck on that freeway, (Being "limited" in your DAW of choice) and telling yourself the product you're using lacks certain qualities.

    So just like your brand new car, once you've become accustomed to it's features and abilities, certain qualities you haven't noticed upon it's purchased, starts to make their appearances and become enjoyable - even with that slight over steer it possesses, which can easily be controlled and handled, once you get use to it. 

  7. 1 hour ago, Jim Fogle said:

    Will,

    Thanks for the video.  I'm looking forward to seeing additional videos as you re-start your channel.

    I like using the typing versus narration.  For a video that's demonstrating one idea typing makes for a concise video.  Aldo there are many people that read English better than they can speak or listen so the potential is there to gain a bigger audience.

    Thanks Jim.

    I'll try to narrate and add text to the video next time. There's a lot of content coming soon so stay tuned. 

    Thanks for the support. 

    • Like 1
  8. All I know is, I'm not changing back to Mac ever again, I'm loving my microsoft surface 3 laptop for personal use too much. I've also been sitting heavily on the idea to upgrade my studio machine to the Surface studio 3 - with one main monitor against the wall, when microsoft launch it soon. 

    • Like 1
  9. 41 minutes ago, msmcleod said:

    definitely uninstall ASIO4ALL, and any other "generic" ASIO drivers such as Steinberg's or Reaper's.

    ASIOLink normally requires your existing ASIO driver to be there in order for it to use ASIO for your primary interface. All other interfaces are then connected via WDM.

    Yeah. That makes more sense. Like I said, I'm not using this, so I'm not familiar with it - just happen to over heard another team figuring this out, on a visit to a friends label and newly build studio. 

    Perhaps @MediaGary can try this again with one Primary Interface Asio Drivers?

  10. 10 hours ago, MediaGary said:

    Wow, thanks for that tip!  

    Because my test machine had been used for *many* tests along the way, I had to un-install the ASIO drivers for the Klark-Teknik KT-USB, Midas MR18, Dante Via, and the Echo Pre8 before starting to get some forward momentum. 

    Glad it could help in some way.

    Try to clear your machine's "registry" from all Asio files too -- including Asio4All. Make sure there's no traces of them and reinstall ODeus Asio link - perhaps that will create some sort of improvement (Usually the case.)  

    I'm curious to know what affect the network speed might have on this? Different locations, different signal. My city had heavy thunder and lighting rain storms 3 days ago, and it interfered with my 5G connection - slowing it down a bit. One of the reasons I'm hesitant trying this out. 

  11. Pleading request to highlight only the tracks from which you double click on to the last track/bus. 

    The drag and highlight tracks or bus to mute or solo together is cool and been great for years - double click on any track is even better, and became a favourite in my workflow as it select every track instantly - cool way for easy mute and solo with Ctrl (but the downside is, it selects every track.) 

    So it got me thinking, what if you have 64 tracks, but only want to solo or mute  every track from track 12 to 64 - wouldn't it be great to just double click on track 12 to select every track from 12 up to 64 by holding down Ctrl without having to move the window to select ever track/bus and leave every track from 11 down track 1 not selected? That would be a simple but awesome feature to have too. 

  12. 2 hours ago, M_Casey said:

    118 GB SSD hard drive for OS

     

     

    This right here could be your problem. Everything you install from your second drive get's installed on your OS drive and in return taking space - therefore causing your SSD to run slower/block, when reading your second drive to grab the samples on playback, causing the dropouts (assuming the 1TB is not an SSD as you didn't mention if it is.)  

    My dropouts disappeared since I've copied all my samples on the same drive - keeping the originals on my external. My projects get saved every 1min automatically on my OS driver, but do the necessary manual Ctrl+S to save it on my second drive. I also only increase sample rates when I bounce/render/export the final product on both plugs and CbB. 

    In return NO DROPOUTS for me on 60 + tracks. 

     

  13. On 10/6/2020 at 6:24 AM, Charley Rich said:

    I just purchased an SSL 2+.  Are there any special settings I should use with Cakewalk for this interface?

    I went into driver settings in Cakewalk  and it showed latency of 10ms for 44k hz stereo.  That seems quite slow.  I am using a PC with an Intel i7  9700 3.6 ghz  CPU which should be quite fast.  

    Am I doing something wrong or is this what I should expect to see?

    --Charley

    1: Choose the interface Asio driver.

    2:Than click on the Asio box at the bottom. 

    3: Set to desired latency. 

     

    10ms for 44.1K is the default option that  Cakewalk choose self for latency. 

     

  14. 10 hours ago, Terry Kelley said:

    Thanks Will, but that's not what I am looking for.

    You sure? Cause the prochannel clip indicator is really that good. If a plugin clips and I mean any plugin (not only the channel modules,) the indicator on the pro channel lights up red. 

×
×
  • Create New...