msmcleod

I take it they have no interest in customers in any of the 27 EU countries then, cos GDPR rules state they must give a valid reason for wanting every bit of personal information, and specify exactly why they need it and what they use it for. Not being based in the EU isn't an excuse. If they want to do business with EU customers they have to follow the EU rules. FWIW the same applies for non-US site selling to the US - they have to follow certain US rules if they want to sell to US customers ( can't think of them all right now, but certainly at one point an import/export declaration was needed for selling anything using encryption, which normally requires a munitions licence in the US).

@Leroy Casterline - FWIW, In the past I've had nothing but problems with USB to MIDI cables and SYSEX. The issue is that a lot of these cables have a IC in them with an extremely small buffer size. They receive data from Cakewalk at full USB speed (480 Mbps), but are unable to send the data out at MIDI speed (32.125 Kbps) fast enough before their small internal buffer overflows. There're two ways to remedy this: 1. Find a way of slowing the data down. IIRC MIDIOX can do this, but in Cakewalk, you need to split the data up into much smaller chunks with delays in between. This normally means not using SYSEX banks, but instead recording the MIDI directly from the device into a normal MIDI track so it can be sent back out at the speed it was received. This may not always work if the device insists on sending the data out as one big chunk of SYSEX. 2. Use a better MIDI interface (e.g. M-Audio MIDISport series, MidiTech MIDIFace series, or if you've a MIDI interface on an external audio interface that will usually work too)

The default settings for TAB and SHIFT+TAB is to navigate through transient markers on the selected clip. I'm assuming you've rebound these to Next Marker and Previous Marker respectively? In which case, you need to check your Landmark settings (right click on "Marks" on the snap module) and make sure arranger start and/or arranger end is checked.

WARNING... for anyone installing this on Windows 7 (either 64 bit or 32 bit). I found after installing this, CbB became unstable on Win 7 64 bit, and SPLAT unstable on 32 bit. Cakewalk Command Center refused to run at all on 32 bit. The solution is to re-install the Visual C++ redistributables. The VC++ 2015-2019 package and the VC++ 2013 package can be downloaded from here: https://support.microsoft.com/en-us/topic/the-latest-supported-visual-c-downloads-2647da03-1eea-4433-9aff-95f26a218cc0 VC++ Redist 2012 Update 4 can be downloaded here: https://www.microsoft.com/en-gb/download/details.aspx?id=30679 Once I'd installed these, everything was working again.

This one isn't even battery powered. You just twist it in your ear, pull it out and clean it. I use it 2 - 3 times day, especially after using headphones for a while. The silence and clarity in my hearing afterwards is surprising.

Oh, this does look nice...

@Matthew Marsolek - It sounds like it's trying to position the dialog offscreen. The last used size & position of the dialog is stored in the registry under this key: Computer\HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\Cakewalk\Core\Dialogs\File Export Dialog If you delete the File Export Dialog key from Computer\HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\Cakewalk\Core\Dialogs\ , this will cause the dialog to go back to its defaults.

Yeah, I've got it on my laptop... didn't really want it on my desktop though. I'll give it a try. I guess I can live with it on my dev partition.

This is a great deal... pity it requires Steam to be installed though...

For a few years I had terrible tinnitus, to the extent where I went a whole year getting no more than 3 hours sleep a night. I gave one of these a try, and it's totally cured it for me: https://www.amazon.co.uk/dp/B09G5VYBKL

You may not have noticed, but there's also a custom date builder in the filename tags popup, so you can have any date format you want:

You could draw a section using the arranger, then press play on that section in the arranger inspector:

+1 to this. Look at Andrew Scheps - he does some mixes in a hotel room, with his headphones plugged into his macbook using it's onboard device. If you're just mixing, and not recording anything, there's absolutely no reason why you can't use an onboard Realtek device. If you just use VSTi's to make music then there's no reason why you can't use an onboard Realtek device. In theory, there's shouldn't be anything stopping you recording audio with a Realtek device either... it's just that most motherboard manufacturers have done absolutely nothing to shield the audio signal path from the input to the Realtek chip, meaning you get loads of interference. This is not Realtek's fault - it's the fault of the motherboard manufacturer.

Cakewalk already supports surround panning if the track is sent to a surround bus:

You can use the Channel Tools plugin for this.

I've got SONAR 8.5 installed on a 64 bit machine, alongside 64 bit versions of X1, X3, Platinum and CbB. I've not had any issues, but I would recommend installing them starting with the oldest SONAR version first to avoid potential issues with common components. You shouldn't see any issues with VST plugins, but you may well get issues with DX plugins. 32 bit DX plugins / DXi synths will not load in a 64 bit program. You'll need to replace these with their 64 bit counterparts manually.

Can't you just set the filename to something other than {projectname} ? You can set the filename to anything you like. There's nothing forcing you use the tags, and actually with the workflow you've described, they won't help you ( unless of course, you're updating the browser notes, in which case you could use {notesname} instead). Also, you can use the "..." button next to the filename to specify both the filename an path at the same time. It will remember the path for the remainder of your session.

@Steven Lewis - if you really need to use ASIO4ALL, just hit No at the warning prompt and it'll use it and not bother you again. ASIO4ALL was being used by new users despite having a native ASIO driver installed. As ASIO4ALL is simply a wrapper for the WDM drivers, this was leading to sub-optimal performance. In most cases WASAPI will perform far better, or better still, use the native ASIO driver if there is one. If you've a very old audio interface, or you're using an advanced configuration for streaming, there might be a legitimate reason for using ASIO4ALL. In this case, just hit No at the warning prompt.

There could be various reasons for this: 1. A fault in your keyboard ( FWIW, I recently had to replace my Korg microKEY2 61 with exactly this problem on several keys) 2. The velocity curve configuration in your keyboard ( if it allows you to modify this ) 3. The VSTi instrument itself, e.g: - Some VSTi's have their own configuration for velocity curves. Check to see if you can change this. - Some sample based VSTi's have a limited number of samples, maybe as small as 4 samples per key. It may be that the VSTi just doesn't have a quieter sound for that velocity ( you can check this by editing the notes directly in the PRV to see if you can lower the velocity there) - Some VSTi's don't respond to velocity at all ( e.g. organs ). I would start by trying to do a factory reset of your keyboard. Most keyboards have some key combination you have to press when powering it up to reset it. Consult your keyboard's user guide, the manufacturer's website, and/or do a Google/YouTube search. Once you've done this, start recording some quiet MIDI notes in Cakewalk, and view them in the Events View and check the velocity of the notes recorded. Cakewalk doesn't modify velocity information as it comes in, so if it's stuck at a certain level, it's likely a hardware issue with your controller. If the lower velocities are showing up in the Events View, then the problem lies with the VSTi.

There are two differences: 1. CA2A is a VST that can be used in any DAW, whereas PC2A is pro-channel only 2. CA2A has a sidechain input, PC2A doesn't.

@gmp - You could try this: 1. SHIFT + double click the clip to zoom the track to full screen 2. ALT + Z to return to the previous view In fact you can use ALT + Z to work your way back through the history of all your zoom steps, SHIFT + ALT + Z will go forward through your history of zoom steps.

You can add text events using the Events View.

I've not delved into this deeply, but I suspect if this is a groove clip, and you've set beat 1 to the first transient in the waveform then what it is doing is aligning beat 1's transient to the grid rather than the edge of the clip. Which makes sense if you think about it.

You've copied the clips as linked clips. That's why they're outlined.

Looks like you've got a snap offset set on the clip. You can tell by the small corner on the bottom left of the clip. Check the clip properties: