Jump to content

Colin Nicholls

  • Content Count

  • Joined

  • Last visited

Community Reputation

249 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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!
  2. What happens if you zoom in? The blog is an approx/average but the peak indicator might be correct.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. I've updated the theme to 1.3 Includes I/O menu icons; and the Markers view marker lock indicator icon
  8. 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.
  9. 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.
  10. 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.
  11. 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?
  12. Now, if I only had an idea for a new theme, I could create it in half the time 😉
  13. 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.
  14. 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.
  • Create New...