Colin Nicholls

Okay, I didn't realize this was a thing. Interesting. I'll play with that. I'll let my enhancement request stand, though, if you would be so kind ? Thanks Mark

@Will_Kaydo, no, that's not really what I'm looking for. I understand what you're saying.

Yeah this is pretty much what I was thinking. I was hoping there was a viable limited enhancement that got us 80% of the way there, hence my simplified request. I was wondering if we could avoid overloading Arranger Track sections with additional metadata. This does make sense, though. I LOVE Studio One's project page but there is nothing that couldn't be achieved in Cakewalk with a bit of additional work.

Option 1. I would expect that each exported file would be named after the Section only, and not incorporate the Track name. In my use-case, the tracks are irrelevant (except for applying specific processing to specific parts of the project. EDIT: I realize I shot myself in the foot in my screenshot by naming each section "Track 1", "Track 2", etc without realizing the confusion that would lead to with Cakewalk's project tracks. I'll update my screenshot in the first post.

I use Studio One for album mastering but I'd love to be able to stay in Cakewalk. One feature that seems like a no-brainer now that we have the Arranger lane is multi-track export. I would love to see the EXPORT module allow me to save a project out as a series of named FLAC files (or even burn to CD!) using the sections defined in the Arrangement: The goal is to export a stereo mix out to a series of separate files, named after the Section that defined their Start/Duration times. I would not expect the file names to include the Cakewalk Track name in this use-case. The actual tracks are not important here (other than hosting the raw audio and for applying specific processing to specific parts of the project). For example, in this image above, I have recorded a tape cassette that I am restoring for a friend, and I have defined the song/track breaks using the Arranger Track; set up stereo adjustment on each recording run; I have mastering effects in the Master bus (not shown), and at this point I have done everything I need to the audio. I just need to GET IT OUT of the project, as separate files in MP3, FLAC, or WAV, or similar format. Or even straight burn to CD. (Cakewalk has CD Burning ability but it requires mixed and rendered WAV files on disk and, dammit, everything I need is right here in the project. Including album/artist information in the Project Info dialogs...) Being able to set up an alternative track sequence (using Arrangements) and burn a test mix to CD to listen in the car would be cool. Please consider adding this feature to the development hopper.

Well... um... okay then. I'll alter the top post. I'm sorry about the confusion regarding "updated for 2020.09" but I just meant that the latest version of the theme was updated at that time, not that it necessarily accommodated additional changes in Cakewalk 2020.09.

Arghh, don't make me definitively list the eight standard changes I do in each theme because I'm bound to forget some and also I'm not consistent. But one of theme is definitely swapping the Instrument and Synth Track/Header icons, for the reasons you cited. Another is to alter the Pre/Post buttons so that they SAY "Pre" and "Post" but i stole that from Steve C in the original Polar Blue.

Would you like to rephrase your question?

Link now points to v.1.4 Includes Control Bar module value text backgrounds, and transport text color

I am having this exact problem, although it has nothing to do with MIDI in my case. Just random pop-ups with identical wording. Usually I see it when I come back to my computer after a period of time and wiggle the mouse to reactivate the screen. I will update this message with my findings. Update: Pretty consistent. If I walk away from my computer and it goes into screen save mode, when I get back to it, this dialog is on the screen: It seems to be coming from Cakewalk, but Cakewalk shouldn't care two hoots about any other audio device other than the ASIO driver/device that I've told it to have exclusive use of. So, why is Cakewalk telling me about this? For what it's worth, choosing either YES or NO seems to have no difference. Cakewalk continues to work normally. So it is an annoyance rather than big issue.

I've been playing around with the $49 Discover edition of Spitfire's BBC Symphony Orchestra plug-in. At $49 (or free after 14 days) I am not complaining, but there seem to be some important limitations here. 1. It's not multitimbral You can select which orchestra section you want to use (say, Cellos) and you can set the MIDI channel. But the orchestra section behaves like a "patch" on a typical synth plug-in. If you change patch, the MIDI channel remains the one you selected. In other words, if you actually want to create a project with many orchestra sections (and lets face it, that's probably the whole point) then you'll need multiple instances of BBCSO in separate tracks. They can all be on MIDI channel 1 if you want because you'll be addressing each instance with it's own dedicated MIDI track. 2. Articulation switching is not obvious There are MIDI notes to switch between articulations but it is really not obvious what they are (C-1 ? That's off the left end of my 88-key board). 3. You can customize the keyswitch position but it doesn't save with the patch! This has GOT to be a bug. If I drag the little keyboard icon to pull the keyswitch position back into frame on my 88-keyboard (but outside the play range of the chosen section, of course), then i can play a performance including switching between articulations. But that keyswitch position doesn't appear to stick with the patch. It defaults right back to C-1 (or wherever). If anyone else has experience or thoughts using Spitfire BBCSO Discover, feel free to join the discussion!

What happens if you zoom in? The blog is an approx/average but the peak indicator might be correct.

I'm not convinced there isn't still a bug here, in 2020.09. We shouldn't be required to edit/save the LOCK icon in order to have it show up in a brand newly-created theme. And yet: Open Theme Editor Create new theme based on Mercury Make some trivial unrelated change in order to enable the SAVE button SAVE the theme as "test" Open Cakewalk; Change theme to "test" Open test project with existing locked markers, or create a new project with marker and lock it Observe: You don't see the lock indicator against the marker row. However, this works as expected if you use TUNGSTEN as a base theme. I've submitted a bug report.

Updated theme to include the Markers view Lock Indicator icon, missing since 2020.04. The link is now a URL to a zip hosted on my own site.

Updated for 2020.09, to include the missing Markers view Lock indicator icon, which hasn't worked since the 2020.04 bug fix. Sorry about that. The link in the top post is now a URL to a ZIP on my own site.

I've updated the link in the top post to point to the latest ZIP. This version includes the Markers view lock indicator icon, which wasn't visible since 2020.04 bug fix. Now it should be good. It's the only change.

I've updated the theme to 1.3 Includes I/O menu icons; and the Markers view marker lock indicator icon

I literally just edited and saved the element without changes. The Theme Editor picked up the file stamp change (as it does) and loaded the image as a custom Theme Element. After saving the theme, and opening Cakewalk, I could now see the lock status.

[deleted]

The 2020.04 release included this bug fix: User @fonolit discovered that, when he/she used the "Blue Aston" theme, the lock indicator was NOT displaying in the Markers view, and that this was a change post-2020.04. I have verified that my own custom themes that were created prior to 2020.04 also no longer show the locked status in the Markers view, in 2020.09. Note that the themes do NOT supply a customized lock image - they rely on the original theme default (which presumably came from a pre-2020.04 version of the original theme). The solution/work-around appears to be to provide a custom image in the theme, even if it is just a copy of the original default. After saving that change, the Lk symbol image now shows up in the application (with the theme selected of course). UPDATE: Okay I see that this WAS included in Morten's original post about 2020.04, but at the time I completely missed the subtlety about the Marker Lock status. I'm gonna let this post stand in case there is anyone else out there as dense as me. SECOND UPDATE: Some folks have reported that their themes are okay without additional tweaking. Bottom line is, I guess, test first. But i have reported a bug regarding new themes being created based on Mercury in 2020.09 having invisible Marker Lock indicators, so I don't think this story is over yet.

Huh. I just checked one of my custom themes, and the Lock symbol isn't showing up there either! I've checked the theme in the editor and there is no obvious reason why the lock image wouldn't be visible. My theme does not have a custom image overriding the default. If I edit my theme so that it does supply a custom image, and save the theme, the lock symbol now shows up in Cakewalk. Now I have a theory that custom themes that were created prior to the 2020.04 update; and that did not specify a custom image for the lock symbol; will demonstrate the same issue.... I happen to have another custom theme that meets this criteria, and, yes, it exhibits the same issue. UPDATE We can't say we weren't warned - Morten posted about changes in 2020.04 and it included the Markers view change, and somehow I completely missed that specific thing. SECOND UPDATE The bug fix in 2020.04 has created a related issue in that themes created from Mercury no longer show the marker lock indicator (unless a custom image has been provided for it). I have submitted a bug report about this.

Transport behavior has been changed slightly in 2019.09 (refer to the manual) but not in this respect. I just tested this out, and if I press the STOP button in the transport (or press SPACEBAR), the playback position returns to the NOW TIME marker. If during playback, I press the PLAY button, then playback halts (or pauses) and the playback position stops at the current location. Pressing PLAY a second time resumes playback from that position. I don't think it is possible to re-map the SPACEBAR to a different function. Can you clarify how you are starting and stopping the transport? Are you using a Control Surface?

Now, if I only had an idea for a new theme, I could create it in half the time ?

Technical note: I am using LibreOffice Writer to create the document. I had the cross-reference (section C) working great with internal hyperlinks on all the section references to allow the user to look at a Theme element and then zip to a corresponding feature where it was used - and the generated PDF didn't recognize them as hyperlinks! They were blue text with an underline, but not active. I had to re-do all the section titles as "cross-reference" elements, instead, which work great in the rendered PDF except that they don't look like hyperlinks at all. They do work, though. Bottom line: In case it isn't obvious, Section C Cross-reference elements to features are click-able. If you open the PDF URL in a modern browser, BACKSPACE or ALT-LEFT will work to return you to your original location.

I was going to add a revision list to the YLIP document, but then it turned into a full-on refactoring and the revision list idea fell by the wayside.