msmcleod

Here's what I did when I upgraded: 1. Make sure your existing installation is up to date with Windows updates 2. When upgrading, on the first screen choose NOT to do updates right away 3. Do the upgrade 4. Once the upgrade has finished, run Windows update.

OK, had my first glitch with Windows 25H2... my Korg microKEY 2 wasn't showing up in Sonar, despite being plugged in. The way I fixed it: 1. Go to Windows Device Manager ( WinKey + X, then press M ) 2. Expand "Sound, video and game controllers" 3. Right click on microKEY2, and select "Uninstall device" 4. Unplug the microKEY 2 5. Plug it back in again

This is the best guide to CAL I've seen... the original site has gone, so you can get it here: Cakewalk Application Language Programming Guide.pdf

Click it to give it focus, then press F2.

Sound on Sound merges the new take with the existing one - whether you choose to record to a separate lane or not, it'll still end up with both the old and new take on the same track. Choose Overwrite mode if you want to overwrite the old data with new.

I was pretty shocked to see that despite doing regular updates, my dev boot was on Win11 24H2, yet my DAW boot was still stuck on Win11 23H2 - and they're on the same machine! But anyhow, I upgraded my machines to 25H2 yesterday. I've not done extensive testing, but my Mackie MCU & C4 are working fine, so no MIDI issues so far with the latest Windows 11. The Mackie's are connected via a MidiTech MidiFace 8, which uses the standard Windows class compliant driver. Also no issues with audio performance/latency, and none of my plugins needed re-authorising after the upgrade. MIDI devices that use a 3rd party driver may require the driver to be re-installed - I can't confirm this, but it's worth doing if you're seeing MIDI issues. FWIW, I'm using MME for MIDI (which will almost certainly not have any MIDI 2.0 support if it exists) - YMMV if you're using MIDI via UWP.

Personally, I'd put it in the vocal track's FX bin, as the first effect - however that does depend on (a) what I'm using in the Pro Channel, and (b) whether I'm using the Pro Channel pre or post FX bin. Typically I set my Pro Channel to be post (default is pre), as I tend to use the FX Bin for sound design and the Pro Channel for mixing. But basically, you want the pitch correction to come first in the chain, as you don't want it pitch-correcting any effects on top. It sounds like you want to use this as a real-time effect while recording though... real-time pitch based effects can be really off-putting for the singer, and may actually turn out worse. By all means try it, but I suspect you'll get a better vocal take from an emotional/expression point of view than recording through pitch correction - i.e. disable the plugin during recording, then enable it for playback. You may be able to tweak it using automation to bring it in/out at various points.

A few things to try: Is there a difference in ASIO buffer size between Sonar and Tracktion? A larger buffer size might explain the drift. If you disable PDC in Sonar does it make a difference? You can either disable PDC completely in the control bar using the PDC button, or disable it for the plugin only using plugin properties (you can get to plugin properties using the cog icon on the plugin UI's toolbar). Be careful with this though - as other plugins are added to your project, the main project audio will sound "later" than time-code. Another thing you could try would be to set it as a tempo-based effect in the plugin properties page. With this set, it stops being a synth and will need to be inserted as an effect on an audio track. If you're just using the SMPTE output, maybe try using an audio track with a WAV file of the SMPTE code on it. FWIW, using the trial version, I tried recording via an aux track at an ASIO buffer size of 1024, then at 64... the output was definitely different, as playing both together with one phase inverted didn't null completely.

Have you made certain there are zero effects (e.g. Pro Channel etc) or other processing (e.g. in the hardware path) on the output of the track hosting the TXLTimecode plugin? It could even be something as simple as the signal being too quiet or too loud.

I jumped on this deal... be aware though, that the current AWS outage is causing issues with Pulse (their download manager) registering the serial number. It'll no doubt be sorted in a few hours.

Yes, they are... but from what I gather it's several months away. Also, their priority is releasing a native driver for ARM64 - the reason being, that they want people to adopt the platform, and they realise that hardware manufacturers will need time to develop/test/release their own native drivers. So I wouldn't hold my breath waiting for Windows ASIO drivers on x64. Also bear in mind that good manufacturers will tweak their drivers to their specific hardware, whereas Microsoft will be focusing on something that will work reasonably well on all hardware.

I'll plus one @Amberwolf's suggestion - use the free version of Sonar rather than CbB. If you've literally done nothing to the waveforms, you can select all of the clips, then drag them to a folder in Windows Explorer. Be sure to extend the left hand of the clip to 1:01:000 before doing so however. If you've only got 4 inputs, for the 8 track I'd recommend doing it in 3 passes: Pass 1: Tracks 1-4 Pass 2: Tracks 4-7 Pass 3: Tracks 7 & 8 With two copies of track 4, you can select all of the clips in pass 2 and nudge them together so that the waveforms in both track 4's line up exactly. Same with the clips in pass 3 (using the two copies of track 7). You can then delete the duplicate track 4 / track 7.

If the native resolution is 3840 x 2160, you'll get better results keeping that resolution but decreasing the scaling - either 150% or 200% scaling will give you much better results.

The meter options are likely different. The "missing" bits you're seeing are the peak holds. There are a BUNCH of different metering options, and it looks like you've got the inspector / console view set to different settings (which is a perfectly normal thing to do). For example, here's the options for the playback meters within the Inspector: There are equivalent options in the Console View and Track View, for Record, Track, Bus and Hardware Output metering.

What screen resolution / display scaling are you using? Looks like you've gone beyond the minimum required resolution.