Jump to content

Klaus

Members
  • Content Count

    89
  • Joined

  • Last visited

Community Reputation

55 Excellent

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Maybe the "Aim Assist enhancements" feature is what you're looking for: Click the Edit menu and choose "Aim Assist > Show Aim Assist Time"
  2. Ha! What a great idea! Spread the word and I see a new VSTi comming: "Finger Squeaks!": 50 GB Hi-Res samples, 5 microphone positions (requires full Kontakt). 🙂
  3. To use this feature ("Speed comping"), start playback with Shift + Spacebar.
  4. Use Shift + Spacebar to start playback for comping. The auditioned clips will then loop continuously while using the Up / Down Arrows. This feature is called "Speed comping".
  5. After reading your other thread about Intra-/Internet, my recent experience is maybe related: While trying to check for updates I had repeatable crashes after clicking the mentioned "Help" menu. And because I had problems that day with opening some websites, too, I looked at my network router settings and saw that the Internet IPv4 connection was lost (IPv6 and DSL were still running). After the reconnection to IPv4 Cakewalk didn't crash anymore when clicking the "Help" menu.
  6. I don't have a solution unfortunately but maybe another workaround: Cakewalk stores the MIDI device settings in the TTSSEQ.ini file under "C:\Users\...\AppData\Roaming\Cakewalk\Cakewalk Core". * The idea of the workaround would be to create two different TTSSEQ.ini files, one for each of your UC MIDI devices and then creating a batch script which will rename/copy the relevant TTSSEQ.ini file to the Cakewalk folder. So, at the end, you'd have to double click the batch file (and remember to do so) before you plug in the MIDI device UC-1 or UC-2. At least a bit faster than reinstalling the driver, I think. * Edit: The path for TTSSEQ.ini in Sonar 8.5 is different of course, but the name is the same, IIRC.
  7. Right click on the volume slider of the Kontakt instrument (the one which jumps). Remove any MIDI CC automation you see there.
  8. Normally, no markers will be added , but maybe those wave files have embedded cue markers. Try unchecking "Allow importing of WAV File Cue Markers" in Preferences > File > Audio Data > All Projects
  9. I can't reproduce this. When Snap to Grid is set to 1/128, Loop Markers will snap to that value. According to your pic, your Snap to Grid module is set to 1/8.
  10. Klaus

    TV Music

    Another single MixCube user here, and your tracks sound really great on it! True mono with only one speaker/driver reveals even the tiniest flaws in the (most) important midrange. Your mixes translate perfectly, very well done! Thanks for sharing!
  11. Waves' plug-ins are sorted just alphabetically in this view, they are not in a dedicated folder. Look at your "Berzerk Distortion" Mono / Stereo plug-ins. 😉
  12. Nice catch, thanks! FWIW, my Waves plug-ins (VST3) do appear in this view, too.
  13. Hi-hat foot controller for e-drums do usually send CC events to reflect the transitions between a closed and an open pedal. If you don't want to see those red lines in Track View, you could convert them to an envelope so they are only visible in the Automation Lanes area.
  14. I just tested the bx_rooMS VST3 plug-in and CbB crashed here, too, while clicking on the UI. Here's the link to the zipped MiniDump file: https://www.dropbox.com/s/n8fr4mfwk4dg663/Cakewalk.exe.7408.dmp.zip?dl=0 bx_rooMS: v1.8.3.0 VST3 CbB 2022.06 (build 028)
×
×
  • Create New...