Jump to content

msmcleod

Staff
  • Posts

    6,905
  • Joined

  • Last visited

  • Days Won

    35

Everything posted by msmcleod

  1. Yes, adding per-output instruments ad-hoc is much easier now:
  2. Select Tempo from the top "Views" menu - you can then add tempo changes at the specified point (or even draw them in).
  3. If you're using Microsoft GS Wavetable Synth for your sound, this is treated by Cakewalk as an external MIDI device (in exactly the same way as an external hardware sound module). You have two choices: First record the output of the Microsoft GS Wavetable Synth on to an audio track, then do your export; or Do as @Kalle Rantaaho suggests and use TTS-1 as your synth instead of the Microsoft GS Wavetable Synth.
  4. What I meant was say you've got one instance of VSP, with all your tracks feeding into it. You could have 4 instances of VSP and have 16 of your tracks feeding the 1st instance, the next 16 tracks go to the second and so on... So in practical terms this means copying your current VSP instance in the synth rack 3 times (so you've got 4) - then ensuring each instance only has 16 (or 17) parts. However it sounds like the latest player is probably doing the core load balancing for you, so there's no need to go down this route.
  5. @MikeyT - what's your ThreadSchedulingModel set to within Preferences->Audio->Configuration File ?
  6. @Sean - FWIW I have a similar setup - 1st gen 6i6 + 3.4Ghz i5 3570. I can quite comfortably work on projects with a buffer size of 64 - sometimes even 32 without crackles or dropouts. @Anders Madsen is correct - first you should check you're running in high performance mode, so there's no reduction in CPU power. However even then, 65 Channels through a single sampler may be a bit much for a single VST, especially if it's only running on one core. Things to try: Try splitting up your sampler into 4 instances, so each instance is only dealing with 16/17 channels. This will allow each instance to run on its own CPU core. You've got 32GB of RAM, so if possible try to get the sampler to load more samples into RAM rather than relying on disk streaming - this will increase project load time, but should reduce CPU load during use. In Preferences->Audio->Configuration File Check you've NOT got the ThreadSchedulingModel set to 3 - it should be set to 1 or 2. [Edit] - Out of interest, what sampler are you using? Kontakt for instance can be configured to use multiple cores, which would negate the need to split your tracks up:
  7. I've been getting this on windows startup with my Focusrite Scarlett interfaces ever since I installed Win 10 1909. Microsoft have probably changed something in the driver initialisation process. Opening/Closing Cakewalk opens & closes the audio device drivers, so depending on what interface you have, you may get a similar effect.
  8. @scook - this is correct - Jon uses the VS-700 as his main interface, and he uses it at least 8 hours a day. @Mark Withers - I'm sure there are instructions somewhere on this forum to set up the VS-700 on Windows 10. IIRC it involves editing one of the setup files, and disabling driver enforcement for the installation - after that it's plain sailing. I'm sure if you reach out to Jon he'll be more than happy to walk you through the process.
  9. Check your Keyboard Shortcuts settings - there's an option to use MIDI CC as a shift key. Uncheck the "Enabled" checkbox if enabled, and consider changing the controller to something you don't use, e.g.:
  10. You can install it via BandLab assistant: Then check the Studio Instruments Suite:
  11. What you need is an ABY pedal - it basically splits your guitar signal into two, such as this: https://www.dv247.com/en_GB/GBP/Fender-2-Switch-ABY-Pedal-/art-GIT0031549-000?campaign=GShopping/UK&ProgramUUID=HADAqJarPzAAAAFlea9yjI.G&gclid=EAIaIQobChMIht3uoI3j6AIVb4BQBh3MwAy2EAQYAiABEgJsDPD_BwE Send one output to your amp (which is then connected to input 1 on your audio interface), then the other output to input 2 your audio interface. You then record both signals. You're now free to use your original amped version, or use the dry signal to add any VST effects to - you could even use both and blend the two.
  12. The sample is probably being recognised as a groove clip. When you open up the clip properties, you'll probably see one or more of these checked: Uncheck them all, and it should play as a standard wav file.
  13. I'm assuming you're using a Simple Instrument track? The easiest way is to just add a volume automation fade out: To be honest though, rather than fading out each individual track it may be better doing the above on the master bus - that way it will affect all the tracks at once.
  14. What is your ThreadSchedulingModel set to within Preferences->Audio->Configuration File ? I've found that setting it to 2 gives me the best results.
  15. Did a bit more research... this is a Windows error that comes up when two programs are trying to access the same file at the same time. Do you have a virus checker running, or a cloud backup service running (e.g. OneDrive) ? My hunch is that it's trying to access the file at the same time as something else. Make sure the following are excluded from any virus checkers or cloud sync programs: Your Cakewalk project & audio directories (i'd also exclude the Cakewalk program and %APPDATA%\Cakewalk\ directories too) Your VST directories Any VST sample content directories
  16. Something like this should do it: https://www.dv247.com/en_GB/GBP/Miditech-USB-MIDI-HOST/art-SYN0006178-000?campaign=GShopping/UK&ProgramUUID=HADAqJarPzAAAAFlea9yjI.G&gclid=EAIaIQobChMIt46bjPzg6AIVgevtCh2z4Q2wEAQYAyABEgI9LfD_BwE
  17. Give the latest EA a try - it should be fixed in that version: PS - there's a rollback facility for this version, so you can rollback to the current release if you get any issues.
  18. Those USB to MIDI "cables" are all based around an IC with a ridiculously small internal buffer size, and whats more the driver accepts MIDI data at full USB speed rather than blocking it to how fast it can send it out. So yeah, pitch bend is dodgy... sysex is a no-go. Personally I'd stay away from any MIDI interface that uses the generic Windows MIDI drivers - just in case they're using the same internal IC. The ones I know work with everything are: M-Audio MidiSport series Miditech MIDIface 8x8 Any MIDI interface that is part of an audio interface that doesn't use generic drivers (e.g. Focusrite Scarlett 6i6, 18i20 etc)
  19. This is almost certainly an issue in Addictive Drums 2 - can't say I've seen it myself though. Things to try: 1. Open the XLN Online Installer, and make sure everything is up to date 2. Check your firewall settings, and make sure it's not blocking access to either Cakewalk or XLN Online Installer. You may find that step 1 is all you need, as this will not only make sure everything is up to date, it will also ensure your license is refreshed so chances are it won't feel a need to connect to the XLN server. Note: Windows updates can change what XLN thinks is the "Computer ID", so it thinks you're running on a different machine. This is a known issue with XLN products. The only way around it is to remove authorisation for your "old" computer id, and re-authorise it.
  20. Please contact support regarding this: support@cakewalk.com
  21. This happened to me a while back when I upgraded my Focusrite drivers. It was down to conflicting settings in my AUD.INI. With cakewalk NOT running, delete AUD.INI from %APPDATA%\Cakewalk\Cakewalk Core , then start Cakewalk. Cakewalk will generate a fresh AUD.INI I'm running the 1st gen 2i2, 6i6 & 18i20 on three different machines, and although I normally use a buffer size of 64, I can get as low as 32 for tracking, or 16 for playback without effects. Tracking guitar without latency when only using VST effects can be tricky though. Typically I record both the dry & effected signal using hardware effects to avoid any VST latency, then add the VST effects afterwards. However if this isn't an option, make sure all other effects are bypassed apart from your guitar effects when tracking.
  22. Are you using a Workspace ? It may be that it's set up to be too "pervasive" in the workspace settings. Try setting it to none, close down Cakewalk, restart it and re-load your project.
  23. Personally, I'd recommend sticking them on ebay - its surprising how many people use/rely on legacy gear, and when something breaks, ebay is the only real source of a replacement. For example, I saw a YouTube video recently by Lewitt (the microphone guys), who were filming at a mastering studio in London. The studio had a range of PC's/Mac's dating back to the early 90's - just in case they needed to work on a session they worked on 25 years ago for a client. No doubt these machines get very little use, but if one of them breaks its a big deal. So not only might you be doing someone a huge favour in allowing them to keep their old gear working, you'll make a bit of money out of it too.
  24. If you're scan settings are set to manual, you'll need to re-scan to pick them up. 1. Go to Preferences->VST Settings 2. Make sure the location of the Waves plugins is in the VST path list 3. Click the Scan button.
  25. Are you using a workspace? Try setting it to None.
×
×
  • Create New...