Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by scook

  1. It is not clear what the envelopes are automated Here is the signal flow diagram http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Mixing.07.html maybe it can help with where the FX racks exist in the tracks and buses
  2. is global FX bypass enabled in the mix module?
  3. FWIW, the large export module shows the duration of the entire project and the current selection.
  4. Check the MIDI driver mode. Some devices only work with MME and will not show when running UWP
  5. Like most Windows uninstallers, registry entries and user files are not removed. The clean install instructions are here
  6. In this part of the forum, it is handy, when a question is answered, to select the best answer by clicking the check next to the reply It let's everyone know there is a solution posted to the question. I checked this one for you thanks
  7. For now it's folders Select the tracks Move the tracks to a folder Move the folder Delete the folder, answering No to "Delete all Tracks within this folder too?"
  8. Add the plug-in path used by "Reaper and other DAW" If they are scanning the PC path, then copy the SaturationKnob.dll to a different folder in the scan path outside of the PC path.
  9. I am not sure if the bundled plug-in is a dual VST/PC dll but the plug-in is available for free from Softube While the plug-in is free, it requires an iLok account and license manager for activation.
  10. When using hardware pads to send MIDI data to a DAW, there are basically two ways to map the pads to MIDI notes in the hardware - most devices have an editor that come with the hardware in the DAW - there are a couple of ways to map incoming MIDI notes to different values, the Transpose MFX and Drum maps The SI-Drum documentation contains all the information about the notes used by the plug-in. To access the documentation, open the plug-in and press the F1 key. Here is a post about creating a drum map for the MPK mini
  11. Everything under Audio in Cakewalk preferences. If you capture images of the pages when driver mode is set to MME and ASIO4All (the two modes you had working) the changes should stand out. The critical bits are Devices, the input and output selections Driver Settings, the timing masters Playback and Recording, the driver mode Sync and Caching, the Record Latency Adjustment device Maybe the Cakewalk Tutorial videos linked in John's .sig above will help.
  12. ASIO4All was originally designed for use with Windows software that only worked with ASIO. ASIO4All is not a driver, it is a wrapper that presents WDM drivers as ASIO to ASIO hosts. In addition to ASIO, Cakewalk also works with MME, WDM and WASAPI drivers directly, no wrappers required. Usually audio interfaces with a manufacturer supplied ASIO driver perform better using their ASIO driver. The RealTek audio chip is an exception. It's ASIO driver is not very good. When running Win10 the WASAPI driver is the best choice. When switching driver modes, review the rest of the audio preferences and make sure they reflect the change. Some find it easier to validate their audio setup using an audio clip in a project before moving on to MIDI and soft synths.
  13. Bet there is information in the TS-64 documentation about this. Click the F1 key when the plug-in UI is open and has focus to read the TS-64 help file.
  14. If audio is disabled on the Export menu, it means there is no audio selected to export. MIDI data routed to external hardware, including the MS GS Wavetable synth, must be recorded into the DAW as audio before it can be exported as audio from the DAW.
  15. One more option available today for volume control is the free Blue Cat Gain Suite part of the Blue Cat's Freeware Plug-ins Pack II These plug-ins have 9 built in groups. Drop one of the plug-in in the FX rack or PC, set the Group A through I and all the BC gain plug-ins in the same group are linked together. Automate one, and all the others in the group follow the automation.
  16. It's certainly easier to use the fader for group edits but it is possible to lasso nodes across tracks and edit them all at once too. Here is another way using remote control, MIDI tracks and a virtual MIDI cable to control automation. This video shows: Track 1 through 3 with volume faders setup using remote control listening to MIDI channel 1 CC7 from MIDI track 7 Track 4 through 6 have volume faders setup using remote control listening to MIDI channel 2 CC7 from MIDI track 8 The MIDI tracks are sending their output to LoopBe1. After recording CC7 automation on both MIDI tracks, the CC data is edited affecting the volume on both groups of audio tracks.
  17. For now create a group for the Automation buttons to match the fader group.
  18. If you really want to use the MS GS Wavetable synth don't use instrument tracks. Instrument tracks are designed for soft synths like TTS-1. Use MIDI tracks and set the channel and patch name using drop downs in the track header or inspector to initialize the track. All MIDI channels except 10 default to the first patch - a piano.
  19. I based the comments about synth audio recording on the image. This image shows the audio+MIDI track pair setup to record audio only. The record button is not enabled on the MIDI track. I am not a fan of Always Echo Current MIDI Track being enabled (as shown by the "A" in the input echo button) because of the effect input echo has on track input settings. The auto-echo setting along with hiding the track input drop down seems like an opportunity for problems.
  20. If you were trying to record audio directly from the synth, it cannot be done with an instrument track. An instrument track can only record MIDI data. Soft synth audio recording requires, as you have discovered, separate audio and MIDI tracks.
  21. Not sure exactly what the question is but I suspect the Track 2 input setting (not shown in the image) may provide a clue. If the sound being produced is not expected chances are the input is set to Omni or one of the other synths in the project with "Enable MIDI Output" turned on.
  22. To find which audio files are used in a track, select the track right-click in the clips pane of the selected track select "Associated Audio Files" from the bottom of the context menu For all the audio files referenced in a project use Project > Audio Files from the main menu
  23. The interface and the project must be set to the same sample rate. Project sample rate is determined by the audio in the project. All the audio in a project must be the same sample rate. When a project has no audio clips, the sample rate is read from preferences If the interface is set to a different sample rate than the project, the DAW will record the audio at the interface sample rate but it will write the project sample rate in the file headers. Playback in the DAW uses the sample rate in the file header resulting in the audio having a different speed and pitch. This may be fixed by correcting the sample rate in the file headers. Because the clips are not at the project sample rate and there are other clips in the project, it may be necessary to import the fixed clips into the project. Changing clip sample rates inside a project can cause the clips to be misaligned on the timeline. That said, I have not experimented with this particular scenario. If I encountered this situation, to repair the clips I would - Copy the clips from the project audio folder. Correct the sample rate in the file headers. There are a few tools that can perform this task. Sox is one of them. I describe how to use sox in this post Import the new clips into a new track Delete the original clips from the project
  24. CbB is running in ASIO driver mode. This is the preferred setting when using an audio interface with a manufacturer supplied ASIO driver. ASIO supports one I/O driver at a time. If there were other ASIO drivers installed they would show up on the preference screen above. Unfortunately, the RealTek ASIO driver is not very good. And even if it was a good driver, it is not possible to select the Focurite ASIO driver for input and a different driver for output. As a rule, ASIO drivers do not support mixing hardware from different manufacturers. Only a few manufacturers supply ASIO drivers that support using multiple interfaces at a time. You can try changing the driver mode to WASAPI shared or WDM. The internal sound chip should be one of the devices available and these driver modes allow multiple different devices, however; there are performance trade-offs using these modes instead of the ASIO driver designed for the interface. From a performance and reliability standpoint, this using the Focusrite ASIO driver is your best solution.
  25. Excluding plug-ins prevents them from showing up in plug-in lists but does not prevent projects that reference the excluded plug-ins from trying to load them. This or renaming the plug-in binaries will prevent the DAW from loading the plug-ins. As far as the DAW is concerned the plug-ins will not exist. Projects that reference the plug-ins, when opened, will display a plug-in missing dialog.
  • Create New...