msmcleod

Take a look at the Bright Electric Guitar by SONiVOX: https://www.pluginboutique.com/product/1-Instruments/64-Virtual-Instrument/2010-Bright-Electric-Guitar It's not the best sounding guitar by any means, but it's much better sounding than TTS-1 and for £4 you can't really go wrong. Their other instruments (Classic Bass, Taylor Acoustic and Orchestral Companion series) are also worth a look and are at the same price at the moment.

The TX16Wx is quite popular, which based on the Yamaha TX16W. There's a free & paid for version: https://www.tx16wx.com/

We fixed a number of issues with clip healing in the 2019.11 release: In the Bug Fixes section, see last two items under UI , and first item under Tools:

This sounds very similar to the issue with the Realtek ASIO drivers, which make the keyboard & mouse unresponsive due to memory leak issues. Does the same thing happen if you change to WASAPI?

For small sysex events (e.g. switching to XG mode or setting input volume / effects on external in's on an XG device), having them in the track should be fine, but for larger one's you're better off using sysex banks. When I used hardware MIDI devices, I had a 16K block of sysex with my custom patches in it on my basic template. As they were saved as sysex blocks, I'd get prompted to send on project load. That way I could get them sent once, and use them for the rest of my session. If you really need to send them out every time, you can insert a sysex bank event in your MIDI track using the event list. As Cakewalk sees this as one event, it will be sent in one go rather than interleaving it.

It was very useful when struggling to sing those odd high notes!

As long as the automation time base is set to absolute, then tempo changes won't affect them. As fades are tied to the clips, you need to make sure the clip's time base is set to absolute to make them immune to tempo changes:

@Pascal Auger - sorry, just realised what your issue is here. You're saying that the times for your automation has changed, because your tempo has? The way to get around this is to set your automation time base to absolute on your audio tracks: Note: This needs to be done before you change your tempo.

There should be no changes in audio quality at all - the audio should be exactly as it was. It just looks zoomed out if the tempo is set to a slower amount.

It's not clear from the video exactly what the issue is, but I've tried out a few scenarios of changing project tempo / inserting tempo changes in projects and everything is working as expected for me. Unless you've got stretch to tempo enabled, then the audio clips will look different when you change tempo. This is because the audio hasn't changed, but the time line for everything else has. For example, 4 bars of audio at 120bpm is exactly 8 seconds long. Changing the tempo to 60bpm, means the time at the start of bar 5 is now 16 seconds, however the audio remains unchanged at 8 seconds, so it appears as if it's changed. In fact, the audio hasn't changed (i.e. it's still 8 seconds long) - it's everything else that has :

Can you post a screen shot of your options (ALT + PrtScrn) within the MackieControl dialog? e.g.:

Fire up RegEdit and open this key: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Tools Menu You'll see a list of everything that has been added to the tools menu, e.g.: Just right click and delete the one you added by mistake.

The USB license requirement is one of my major gripes with Revalver. I love the software, especially the guitar modelling (great for mixing VST guitars & real guitars and making them sound like the same instrument), but it does mean I've got this USB key constantly having to be moved around between PC's. Because of this, I can't think of any project where Revalver has stayed in a project for more than the time its taken to apply the effect and bounce to clip(s). Oh, and the other thing - unless the new owners have made some changes, you can't change the USB device it's authorised to without a call to support.

@Riccardo66 - This sounds like it could be your ASIO buffer size is set too low. Try it at 256 first, the try lowering it to 128 and maybe 64. If you're running the latest cakewalk, you can do this with the slider, otherwise click the ASIO panel button. How high this buffer should be set is dependent on how much work your laptop is doing - if you've got plugins that require a lot of CPU, then a higher value will be required. The downside to higher values is a higher latency: in other words a slight delay between pressing a key on your keyboard and the note sounding. The Focusrite's should go down as low as 16, but expect crackles at anything but the most basic project. I tend to stick to 64 for tracking, occasionally going to 128 or 256 during mixing.

Well spotted @Noel Borthwick - I've updated the screenshot.