winkpain

Yup, Steve. I do like the way CS lets you map your articulations any which way, and that is how I make it work for now (I use the cc mappings set in CS) I do prefer the velocity mappings, however, and since velocity was mentioned in the new CbB Articulations Map instructions as a viable method for articulations, I wondered if it really is working there at the moment.

...And I confirm crashes on editing CC lanes with EA2 as well.

I love the new Articulations Map function! I am not finding a way to define an articulation in the Editor by velocity. It is mentioned in the .pdf as one of the methods alongside keyswitches, control changes, and patch changes. However, when I go to edit an articulation Midi event "kind", the pull down does not offer Velocity as a "kind". Many of my instruments in Kontakt (specifically CineSamples string instruments) use note velocity to vary the patches called upon for various articulations (as well as in combination with note duration, pedal, keyswitches, mod wheel changes, etc.) to get a very complex and live playing like, extended technique response in the performance. I have, of course, grown accustomed to authoring these with MIDI changes in the automation lanes and such. BUT I would love to work completely in the new Articulations pane! Is there a way yet to map velocity to these new articulation "clips"?? And I look forward to the possibility of integrating Key Bindings to all Articulation Map functions, including to individual custom articulations (although I'll bet this would be difficult, no?)

In troubleshooting what I thought was a Melodyne problem (a simple drag and drop a small audio clip to MIDI track for conversion brought up the dialog box for conversion, but nothing happens after clicking "OK"), I uninstalled Melodyne from "Add/remove programs" in Windows as suggested in the Bandlab Assitant Add-ons dialog. I also uninstalled the Melodyne Runtime as Administrator. I then went back to Bandlab Assistant in hopes of re-installing Melodyne from the "Install add-ons" window there. However, Melodyne remains greyed out and unavailable to install. Is the included version of Melodyne available for re-installation or does it cease working and cease to be available in any way if not upgraded/licensed/paid for? I am currently running the Early Release version of CW on a Windows 10 machine.

...Yes, those articles, although a little old, do help refresh my memory on using ReWire. I had gotten Sibelius to work with ReWire/Cakewalk in the past and could not now figure out why it no longer worked. One important thing to remember, and what caught me off guard this time, is that you must untick the setting in Preferences/Audio/Playback and Recording that is called "Suspend Audio Engine When Cakewalk Is Not in Focus" This is a newly worded setting that used to be "Share Drivers with Other Programs" and is still mentioned as such in the CW Knowledge Base article for setting up ReWire. I had been looking for what I remembered as the "Share drivers..." version of the setting and took me a bit to figure out (because I kept overlooking it) that "Suspend Audio..." is just another way of saying the same thing. Anyway, that is what did it for me! I am recording this here in case anyone else stumbles on this thread looking to get ReWire working. This combined with using loopMIDI virtual cables really ups the game for me. Sibelius can then be used as the "Staff view"/Notation page where I can compose in my preferred Sibelius which then drives those MIDI notes into CW where I then assign the sounds and can have MIDI changes and automation and such controlled in the familiar way within CW. The best of both worlds!

Where are these articles by Craig about Cakewalk and ReWire?? I too have been trying to get CbB to work with ReWire and Sibelius (Ultimate) and am having no luck...

Yup. I got all that and that's how I've been doing it, and I'm familiar with workarounds with temporary group changes to ensure all tracks have the same settings after the fact, etc. I was just hoping for a way to have the default be exactly how I wanted it (with preferred module states - specifically the Console module) from the outset whether Inserting new track or drag/drop adding tracks so as to have a "set-and-forget" scenario. No worries, tho. The setting default arrangement from PC context menu got me much closer. Thanks again!

That's it. Thanks! This does not, however, preserve the chosen status of the modules. For example, if I want to have the default Console Emulator always load as an A Type with Tolerance set to On, nor does it preserve the On/Off state of the modules. Is it possible, then, to choose a particular PC preset that will load by default when doing this??

I cannot seem to remember: How do we save our preferred version of the default track template? I'm well familiar with exporting/creating and using my own named templates as described in the User Manual on page 328 (in the downloaded pdf). Here I'm talking about the unnamed default that defines the setup of a (in this case audio) track with an arrangement of chosen ProChannel modules and is the one used for a simple Insert Audio Track or with a drag and drop of an audio file(s) and without having to choose "Insert from Track Template" and then choosing the template. Anyone know? This question was asked a year and a half ago with no answer....

I continue to score to video in CbB. It still continues to work with the basic functionality it has always had through the Sonar versions, 'tho with some quirks. Some discussion of those issues and the inherent problems related to them as explained by Noel are discussed in a thread here. Although I agree that the OP's issue is most likely the video view being "blocked" by the Workspaces set-up as mentioned above. It's almost always the cause of view problems. When I can't find my glasses in the morning, I go to Workspaces, choose None, and boom! there's my glasses. 😉

Agreed, agreed. Happy to join in the conciliatory mood here. Yes, we all continue to agree that Staff View is what it is and isn't what it isn't, 'tho tweaks and fixes would be appreciated.

Agreed. CW, nor any other DAW, is the right tool for the particular job of writing (certainly not publishing) music notation properly, and I don't expect it to be. That's why I shared my Rewire/Sibelius "workaround". It provides the best of both worlds in a way. However, I also agree that it will be a grand day if/when the fantastic folks at CbB have the time to upgrade the Staff View, since there are certainly enough of us who like to work with notation in DAW composition (as this and other threads bear out), or at least like to have it as a viable, full-functioning option. I am deeply and continually impressed over this last year with CbB's staff and their unflagging attention to this product and its broad base of constituent users, and I know you can't please everyone, but I highly doubt it is true that, as I read elsewhere here by someone seeming to say "why bother" fixing Staff View when they said there are "easily 100 or more" times as many people who don't use Staff View as those who do. I wonder where they got their data from! And since it remains as part of the program, it seems worthy as any of the other tools for upgrade consideration. As this is the Feedback Loop, that is my feedback. But as I say, I'm quite happy working with the Rewire option when needed.

Staff View is hardly even a nod to composers who are accustomed to and prefer working in traditional notation and/or need to provided printed sheets for instrumentalists. Cakewalk is simply not the place to attempt it. But chiming in here with the note for Sibelius users (like myself) who want to also have the ability to work with all the wonderful CW tools and workflows: Remember, it can be Rewired into a Cakewalk project fairly functionally. I do this whenever working on scores (much, much preferable to work in Sib. for composing in "dot and line") with soundtracks/sound design that want to include synchronized audio elements worked on in CW. I just think of the Rewired Sibelius instance as my Staff editor in this case, and of the audio output of Sib. as a 2-track mix within CW . Of course, you do not get to edit the sounds of the instrument tracks (staves) individually in CW with any of the controls or tools available in the box there, but if happy working completely in Sibelius for those tracks and then working with additional audio extensively in CW, it keeps everything synced up and is great for the work-in-progress part of your workflow.

Interesting! It is definitely a new thing for me and my set-up which has remained unchanged for years, besides updates of course. But thanks again for chiming in on it. It's always a relief to know an issue is in capable hands.

Nice to know this is in your sights. Strange, tho, that it should be an "all of a sudden" issue, no? Does this mean it's crept in with these latest updates?

Are you suggesting that deleting TTSSEQ.ini and re-enabling the MIDI device every time you open Cakewalk is just the way it is? Surely that indicates, as does mine and all the other instances of the problem here in this thread, that something is wrong. I, too, can get it working with that procedure and have done so, or by disabling the device, re-opening CW and re-enabling the device, which I guess in effect is the same thing. Either method being necessary every time I open CW surely is not the way it should be.

I would sacrifice a chicken at this point to get this fixed! Is there a post about the proper procedure you can point us to?? I wouldn't want to mess up the juju! 😉

This is the same with me with both my Novation and M-Audio keyboards, both continuing to work fine in all other, non-Cakewalk instances.

Yup. this is exactly my issue. Still no answers here.

I agree with you - should be set and forget. Fortunately, if you have set it and saved all those projects with it set, you're good. I do believe this is the way it's been for a while. I wish it would be changed as well.

I have noticed this issue as well and brought it up, specifically with the snap to zero crossings setting which I prefer to have always set on (its default is off). Yes, these Snap settings do seem to be a per-project setting even tho it is not called out as such. A "work-around" I have done is to re-save all my templates, especially the "Empty" template with my chosen Snap settings so as to have them at my preferred defaults. But still, opening new projects not from a template, or existing projects without snap settings having been set to preferred before saving will revert those settings.

This would be great! I know of no way to customize mouse wheel settings. The wheel is not available in the Key Bindings preferences. I don't know of anywhere else it would be besides [Track view] Options > Mouse Wheel Zoom Options, which only offers those aspects of its Fast Zoom functions, no options for choosing the modifier keys. But it would be nice to be able to customize it !

You have it bound already? Meaning that it is available in the EA release? Or is it just on your own, pre-release copy? I cannot find any available bindings for "Rename" anything in Track view window of the bindings or any of the others.... (I'm on the EA release)

Thanks scook! That looked promising, and it did get me to get rid of some undesired, previously installed MIDI devices in my Device Manager. But I didn't have anywhere near 10 devices installed, nor were there any hidden devices. I even uninstalled my desired devices and re-installed them and their drivers. In any case, the problem persists. Perhaps it is worth re-iterating that I have no issues with other applications (stand alone synths, other DAW, etc.) with any of my MIDI devices. Only CW has this issue and it only began a week and a half ago, first intermittently and then consistently... 😕

I'd love some advice on this. I'm really in the dark here. No MIDI device will function, either with USB connection or MIDI cable through audio interface without first disabling (un-checking) it in Preferences, exiting CW with no devices enabled, re-opening CW and then re-enabling the device in Preferences. I must repeat this process every time I start CW. Deleting/renaming TTSSEQ does not help. I see in my MIDI devices window in Preferences that every MIDI connection I have ever made is in the list whether enabled or not. Is there a way to clear this ? Maybe this would help CW start with a "clean slate" so as to re-establish the MIDI settings for these devices somehow? Really flummoxed as to how this came about all of a sudden....