-
Posts
102 -
Joined
-
Last visited
Posts posted by Klaus
-
-
Hallo!
Falls du die Ausschläge der Pegelanzeige der MIDI-Spuren meinst, diese zeigen nicht die Lautstärke/Volume an,
sondern die Anschlagstärke/Velocity der MIDI Noten.
-
You are right, HOOK!
It indeed only works when Auto-Crossfade is disabled.
My bad!
Damn... 😔
-
23 hours ago, HOOK said:
Hi Mark. Indeed, it works that way. The problem I have with the auto-fade function is that it snips the clip at a point prior to and after the desired grid line and fades into or out of your intended split point. If you do that to a group of tracks and then drag that group of waveforms over a few beats, now EVERYTHING is off by that much because it snaps to the cut where the fade starts. That's no good.
If you guys change the S shortcut to do the same and I can't shut it off, it'll ruin me. I've been using S to split clips for a couple decades man....don't do that to me! 🥺
If you disable "Snap to Nearest Audio Zero Crossings", splitting Clips with ALT + Left Click will follow your Snap settings exactly.
Preferences > Customization > Snap to Grid (Advanced)
-
In Cakewalk's AUD.INI, is "ThreadSchedulingModel" set to "2"?
"1" is the default value, but "2" is recommended for multiprocessing systems with quad core or higher processors.
-
Yes, you can change them in the Inspector or use "Views" - "In/Out" in Console View.
Your tracks maybe already routet to the Master Bus (default), so you doubled the Volume by using the additional sends.
-
Route the Output of your tracks to Master and Bus B.
Then delete the Sends on these tracks.
-
VSTis are loaded into the "Synth Rack".
"Views" - "Synth Rack View" or shortcut Alt+9.
-
Right click on the tab (bottom) of the video and choose "Undock".
Now you can resize the video window.
To use different stretch options, right-click the video window to see the context menu.
- 1
-
WRT RME, another feature/tool I really like is their software DIGICheck.
It's been rarely mentioned here so I thought a post about it could be usefull.
Here's a link with info:
-
Using Notes
in Q&A
57 minutes ago, Bruno de Souza Lino said:Doesn't help that Ctrl+Enter does the same function as just Enter in other places, whilst Shift+Enter (which is the shortcut to add a line break in essentially everything else) is not mapped to anything.
Well, Ctrl+Enter certainly helps if you want to add a line break in Inspector and Take Lanes notes.
It's the only way to do it.
-
Using Notes
in Q&A
52 minutes ago, Bruno de Souza Lino said:If you need comprehensive notes for a track, the Melda MNotepad plugin is your best solution for that. The Inspector notes only allow you to write one continuous string of text without multiple lines and the same goes for the Take Notes as well. Don't expect a complete text editor experience from the plugin though. You also have to click on the right keyboard icon to type text into the plugin, as even clicking on "give all keystrokes to plugin" will still trigger keyboard shortcuts.
Use Ctrl+Enter to add another line.
- 1
-
3 hours ago, Daniel Rippe said:
After more extensive testing, I can now reliably reproduce this bug. It happens when exporting WAV and MP3 audio. I have not tested the other audio formats.
I have a simple project with one track and one clip. The FIRST time I export audio after opening the project, the Clip Gain is included. The SECOND time I export, the Clip Gain is ignored. I am doing nothing other than opening the project, then exporting the same audio twice.
If I move the clip forward or backward in time, the next export is fine, but the one after that, again, ignores the Clip Gain.
Bouncing to Clips and/or Flattening Comp sometimes resolves this, but not always. Even after bouncing or flattening the Clip Gain is sometimes ignored, but not always.
^^^
That would mean not only your exports don't work as they should but also the bounce process, which is a really important and fundamantal feature.
Bouncing has less routing possibilities and user interaction than exporting, so doing some tests only with the "Bounce to Clip(s)" command on one Clip (no additional Lanes) could be helpfull.
After right-clicking the Clip and selecting "Bounce to Clip(s)" you should immediately see the applied Clip Gain in the new waveform and peak levels.
-
Maybe the "Aim Assist enhancements" feature is what you're looking for:
Click the Edit menu and choose "Aim Assist > Show Aim Assist Time"
-
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).
🙂
- 2
-
To use this feature ("Speed comping"), start playback with Shift + Spacebar.
- 2
-
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".
-
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.
- 1
-
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.
-
Right click on the volume slider of the Kontakt instrument (the one which jumps).
Remove any MIDI CC automation you see there.
- 1
-
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
- 1
-
9 hours ago, Will. said:
I have reported this before, and workaround are often a pain to isolate the region to be worked on. When making cuts on the specific area the loop points do not go further than an 1/8th snap note on the grid, This means: If you had make cuts in a 128th of a snap - you're by yourself. Even with the snap off it does work, nor, by holding Ctrl, Shift or in a combination of these keys. The reason is to get a surgical and precise region on the playback to tame some transients and to do precise comping | or | to add some dynamics to it.
I can do cuts in samples/ticks and all that, but to get that precise area to work on, is a guessing game with the playback loop points not going smaller than an 1/8th snap note in the measure/bar.
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.
-
On 7/17/2022 at 1:23 AM, Mark MoreThan-Shaw said:
One thing that helped me learn to avoid that was the little mixcube, I spend a lot of the time working in mono which really highlights when parts are in the way of each other as well as being a great tool for balance.
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!
- 1
-
20 hours ago, Starship Krupa said:
Hmm, maybe I missed something....
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. 😉
-
Nice catch, thanks!
FWIW, my Waves plug-ins (VST3) do appear in this view, too.
- 1
Color Palette Favorites
in Q&A
Posted
After you've added your custom color to the first box in "Custom Color" via clicking the "Add to Custom Colors" button,
press the Tabulator key on your keyboard twice.
The first press will put the focus to the "Basic Color" palette, showing a black quadrat around one of the color boxes;
the next press will shift that quadrat to the "Custom Color" palette.
Now use the arrow keys on your keyboard to put the focus/quadrat to a different box where you want the next color added.