msmcleod

I took a look at this earlier on - it is a bug. While its true that in Windows there isn't any way of truly distinguishing between hardware MIDI ports (although Cakewalk does try its best to get around this by also using the device name), this is not what is happening in this case. The issue is that it's losing the internal MIDI device ID of the soft synth when loading the template. It then gets that mixed up with the real hardware device ID. Disabling the MIDI output of synths that you don't need MIDI output for will go some way to mitigate this issue.

Quick groups work on visible items (so you don't end up changing something you can't see and are unaware it's been changed), so this is expected.

You cannot buy SONAR anymore. In fact you can't buy anything anymore. Cakewalk by BandLab is what SONAR Platinum was, but now it's free with loads of new features and well over 1000 bug fixes (maybe even 2000 by now).

You can find an old comparison chart between SONAR & Cakewalk by BandLab here: https://docs.google.com/spreadsheets/d/1AwrivrPMMqFyAnbRfV03U2ki00VwOJNHeFXolbyyzKA/edit#gid=0 The current (2021.04) release, also includes the following: Cakewalk Classic Effects Suite: Alias Factor, Compressor/Gate, HF Exciter, Modfilter, Multivoice Chorus/Flanger, Para-Q, Tempo Delay ... and also Channel Tools and the PC2A pro channel module.

The iCon devices don't officially support Cakewalk or SONAR, so there's bound to be areas that don't work properly (especially the button mapping). You should be able to get basic Mackie faders/transport working however. Any device that doesn't officially support Cakewalk/SONAR should have "Disable Handshake" checked within the Mackie Control Surface Panel (accessed from the Utilities menu): Also, make sure Master fader is set to Bus 1:

Yes, this is correct - apologies for the ambiguity in my first statement.

Tempo Track settings definitely do get saved in Workspaces as well as screensets. What I said at the time was, you need to re-save your workspaces/screensets in 2021.04 for them to save those settings, as obviously 2021.01 versions of the them have no knowledge of the tempo track.

This is partially a bug, and partially not... Since 2021.01, arranger section operations use the "Arranger Section Overlap Threshold" setting (under the Track View MIDI menu). When this threshold is set, any notes that overlap the section boundaries will be treated as part of the section when deleting/copying/cutting etc if they fall within the threshold. If set to a low value, it can help to include unquantized notes that start just before the section boundary or end just after. Higher values can be used for pads that are played early because they have a slow attack. So the "not a bug" part is that notes outside the section boundaries may be deleted if they fall within the threshold. The bug is that it's picking up non-MIDI data such as tempos, markers & meter/keys and incorrectly deleting more than it should due to the tempos/markers/meters internally extending the selection. This bug has been fixed for the main release ( due to be released immanently ). In the meantime, setting the threshold to "None" will get around the issue.

No this isn't possible. Have you considered using articulation maps? They're far easier to use than using the PRV to enter key switches.

Just use the tempo inspector. It essentially gives you the same functionality as the old tempo view. FWIW - the old Tempo Map is exactly the same as it was behind the scenes. All the tempo inspector / tempo track, is give you a different way of editing it.

If you set the following within Preferences->File->Initialization File: TempoImportErrorThreshold=0 ... the tempo will be imported exactly as it was in the old project and won't try to fit an envelope shape to the map.

Reaper's ReaStream plugin will stream over the network (although it's meant for a LAN rather than a WAN)... but it might work. It's just a standard VST2, so it should work in Cakewalk: https://www.reaper.fm/reaplugs/ If it doesn't support WAN streaming directly, you'll definitely be able to use Reastream to stream to OBS, then get OBS to do the streaming over the internet.

@Mauricio Ramirez - Thanks for sending the cwp file. We've found the cause of the issue a fix will be in the next update. For the meantime, either use Cut instead of Delete, or set the "Arranger Section Event Overlap Threshold" to off.

Ok, I've worked out what's going on, and it's behaving as expected. Firstly, as you've pointed out, the track/console states in sync box is not ticked. When you use a keyboard shortcut to bring up the Track Manager, it brings up the Track View's version of that dialog. This is why it makes no difference to your console strips. If the sync box is not ticked, you need to select Track Manager from the Strips menu on the console to affect the console tracks. Secondly, the visible tracks are stored per screenset. So hiding tracks in screenset 1 will not hide them from screenset 2.

If the project is loading ok, you can do a "Save As" to a new location - that should only bring the audio that is actually being used with it.

@Justin Ursua - I can't reproduce this. Can you send a copy of your cwp file to @Jonathan Sasor , along with the steps you took to save the MIDI file so we can try to reproduce?

@Mauricio Ramirez - can you PM @Jonathan Sasor a copy of your project so we can try to work out what is going on here? Thanks.

@Psychotronic - we got a cwp file from you, but not the audio... so there's not much we can do investigation wise. Best thing to do is zip up your project directory and sent it to Jon.

@Marcello - one thing I forgot to mention... If your delay pedal is designed for a guitar's input, it may be expecting a Hi-Z level impedance input rather than the line level impedance your audio interface will be sending out. Your pedal might accept a line level, in which case you're fine - check your pedal's user guide. If it doesn't accept a line level, you might get away with turning the send level down, but really you need to match the impedance otherwise you'll get sub-standard quality. This can be done with a re-amp pedal (they're pretty easy to build if you want to save money):

That might suggest the sample rate in Windows and the sample rate in Cakewalk are different (e.g. 48Khz in Windows, 44.1Khz in Cakewalk).

Using MIDI won't help you at all. All the MIDI is used for is to remotely control the pedal (or perhaps for matching delay to tempo) - it carries no audio signal at all. If you just want to use the pedal as an effect, record your guitar dry as normal (i.e. plug the guitar directly into a Hi-Z input on your audio interface), then use a spare output on your audio interface to connect to the input of your pedal. The output of your pedal should go to a spare input on your audio interface. Then use the "External Insert" plugin on your recorded guitar track to send the audio out to the pedal.

The re-activation process within Cakewalk itself uses the Microsoft Edge WebView component. If your Windows 7 has all the latest updates, this should work fine (I've tried it on my Windows 7 boot, and this definitely works). I believe The Edge browser was included in the penultimate Windows 7 update. Failing that, you can use BandLab assistant to re-activate.

Do a VST scan from within preferences - this should pick it up.

You can use external effects using an External Insert... ...however, you may find that it increases latency too much as its having to make two round trips. What I normally do is record 2 tracks for my guitar: one mono track with the dry guitar signal, and a stereo track coming out of my guitar effects. You could do a similar thing using an ABY pedal or DI box: So your guitar goes into the Y input, output A goes directly to your audio interface; output B goes to your effects pedals and then on to your audio interface. If you like what you've recorded, then you're good to go. If you need to change things, unplug your effects from output B of your ABY and connect it to one of your audio outputs, insert an External Insert effect on the dry track, tweak the effects and then either re-record on to another track... or just leave it as an external insert on your original dry track.

Sounds like you've got Ripple Edit switched on: