msmcleod

Keyboard shortcuts are focus sensitive - i.e. they only respond in the if they are bound in the currently focussed view. For example a shortcut that is meant only for the PRV isn't necessarily going to work in the main view (it might have an equivalent, but you may have to re-bind it yourself). If a shortcut isn't working, it's likely you've given focus to a different view. Some keyboard shortcuts are global - well actually, it's more accurate to say the target operation is global, so they can still be overridden in a child view if you set it up that way. So when binding any key, check other views to see if the key is being used there too.

@hanyinshan - did you try setting your workspace to "None" or "Advanced" ?

It's already here: ...and here ( Project->Insert Tempo Change)

The instrument track is different because there's actually two tracks involved. Basically what happens when you freeze an audio track, is that it takes a backup copy of the current audio clips and replaces it with the frozen audio. Any insert time operation is then performed on the frozen audio, but the backup copy remains intact. When you unfreeze, the backup copy is restored. Instrument tracks have two tracks - an audio track, and a MIDI track. When an instrument track isn't frozen, it has an empty audio track and you see the MIDI track part in the clips view. When you freeze a MIDI instrument, all it does is bounce it down, fill the audio track up with the frozen audio, and show the Audio track part in the clips view. When you unfreeze, the frozen audio is replaced by the original audio (i.e. nothing), and it goes back to showing the MIDI track part. As the MIDI part isn't a backup copy, it's still affected by insert time.

This is to be expected. Freeze track is meant to temporarily free up CPU resources, and any operations on the frozen clip will not be reflected in the unfrozen version. There are two ways to get around this: 1. Use Bounce to Clip(s) instead of freeze 2. Once you've frozen your clip, copy it to another track then unfreeze the original

I can confirm that scrub is indeed skipping articulations. This was an omission rather than by design. I can also confirm: Only audio data / video is scrubbed in the track view/clips view - not any MIDI data MIDI data is scrubbed in the PRV, but is limited to note events only. We'll see what we can do about scrubbing articulations in the PRV for the next release, however given its limitation to notes, it may not give a 100% accurate rendering compared to normal playback. Triggers shouldn't be a problem, but support for transforms may be limited. We'll need to investigate further.

Have you got any active region fx (e.g. Melodyne) ? Clip Gain / Pan automation isn't available while a region fx is still active.

lol - yup... those are the ones I used!

Check the .ins file to see that bank select for bank 0 is being properly sent. I've found a few .ins files in the past that don't send anything for bank 0, and just send the program change. This works when you first turn your device on, but if you've switched to a different bank, it doesn't switch back to bank 0.

If you're using MCU mode on a device which doesn't offer a Cakewalk or SONAR mode, make sure you check the "Disable Handshake" checkbox on Cakewalk's Mackie Control panel. That should get transport, faders & knobs working.

The HUI support was developed by using some documents I found on the internet, by someone who reverse engineered the protocol. I used this in conjunction with the MCU in HUI mode, and TouchDAW in HUI Mode on an android tablet. All it does, is attempt to map HUI commands to MCU commands and vice versa. Basic HUI functions work, but without the real HUI documentation or a real HUI device, it's very difficult to proceed further.

Maybe something like this? https://www.amazon.co.uk/TGI-TGFS2-Latching-Footswitch-Black/dp/B007WSTOCS/ I'm sure there are plenty of alternatives by different manufacturers. [Edit] - You could also call Yamaha UK themselves - they are awesome at providing parts.

That's great news about Thomann - I used to use them all the time. Obviously the shipping has gone up though, even if they're sorting the paperwork out, so I'd have to look at the overall cost. In the meantime, Gear4Music has been pretty awesome.

I've had to stop buying from all my usual EU suppliers - you'll definitely get stung on import duties, additional VAT, and possibly an admin charge. Your bank may charge you for converting to € too - mine did. If you can get it from a UK dealer, do so.

If you really want to use .ins files, this is how to do it. Note that this is pretty specific to the MDS-50 in that it needs a separate instrument definition for each channel:

@User 905133 - Seeing as the MDS-50 uses NRPN's rather than the standard bank select/program change, you may want to consider using articulation maps instead, e.g: So, basically: Create a separate Articulation Group for each organ section Create an articulation for each sound. In each articulation, set the Kind to CC 14b, Note/CC to 99 (NRPN) and Play At = Start Then set Channel / Vel/CC to the channel and NRPN number required for that sound Once you've created your articulation map, export it so it's then available for other projects. You can then draw the articulation in the PRV to get the desired sound: Attached is one I've started off for you. Allen MDS-50.artmap

Have you tried excluding your projects & global audio folder from your virus checker and any cloud sync apps?

I've just tried saving a track template with an audio track sending to an aux track, and it worked fine for me - although I did make sure the aux track was in the selection when saving the track template.

@Josh Barron - we've been getting a lot of these kind of reports lately, and it seems to be down to something installing an older or broken version of the Microsoft VC++ redistributables. For me, it was Melda v15 that caused the issues, but there could be some other cause. This may not be the cause your issue, but there's no harm in ensuring you're running the latest VC++ redists. The latest redists can be found here: https://docs.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-160 You'll want to install the x64 version of the redists for "Visual Studio 2012", "Visual Studio 2013" and "Visual Studio 2015, 2017, 2019, and 2022"

@Jim Kelley - I've got the latest version of Cakewalk ( 2021.09.145 ) running on my Windows 7 64 boot, with no issues. If you're having issues, I'd check the following: 1. Make sure Windows 7 is fully up to date with Windows updates 2. Ensure you've got the latest VC++ redists installed. The latest ones can be found here: https://docs.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-160 You'll want to install the x64 version of the redists for "Visual Studio 2012", "Visual Studio 2013" and "Visual Studio 2015, 2017, 2019, and 2022" 3. Ensure you've got TLS1.2 enabled as default for Cakewalk authorisation to work: https://support.microsoft.com/en-us/topic/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-winhttp-in-windows-c4bd73d2-31d7-761e-0178-11268bb10392 . Assuming you're up to date with Windows Updates, you can jump directly to the "Easy Fix" section on this page: https://support.microsoft.com/en-us/topic/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-winhttp-in-windows-c4bd73d2-31d7-761e-0178-11268bb10392#bkmk_easy

The Export Dialog is selection based, so: If you've nothing selected in your project, all sources will be available If you've got tracks and/or clips selected, sources will be limited based on the selected tracks/clips. The Tracks/Buses in project basically allows you to alter your project selection and the mute/solo status of tracks & buses, without having to exit the dialog. In most cases, you'd make your selection in the tracks view before you open the dialog, but if you're creating multiple export tasks it's convenient to use the "Tracks/Buses in Project" flyout to alter the selection to create additional tasks. It's also there to be able to alter your selection if you'd made a mistake in your original selection.

It's all to do with the active track. You can only edit articulations on the active track. If you're showing more than one track in the PRV, articulations from anything other than the active track will be greyed out. e.g.:

@Milton Sica - It's not clear what context you're referring to here. Is it incorrect when you first create an MP3 export, or are you referring to recalling a task? Every time you open the Export Dialog, it grabs the latest information from the notes browser. If you create a new mp3 export task, the mp3 dialog will show and allow you to customise this information. Anything you edit will be stored inside the task. Subsequent changes to the notes browser will NOT update the task. Additionally, any edits you made to the mp3 dialog will remain while you are still in the Export Dialog. Once you close and re-open the Export Dialog , it grabs the latest information from the notes browser.

I used to use the gain envelope method, but nowadays I just use an auto leveller plugin as I can get good results very quickly. One's to look at: Hornet AutoGain Pro: https://www.hornetplugins.com/plugins/hornet-autogain-pro/ Melda AutoVolume: https://www.meldaproduction.com/MAutoVolume Waves Vocal Rider: https://www.waves.com/plugins/vocal-rider The advantage of using the gain method or these plugins over compression, is it doesn't sound compressed. It just levels things out. That being said, I also generally use gentle compression on a vocal after doing any levelling.

You can get almost exactly the same results using something like Sitala on an instrument track and opening the Step Sequencer.