Canopus

You mean something like this? Nah, I don't think that can be done. No, but seriously, as I use Photoshop I would use the Wand tool with the option Contiguous selected and then Shift+Click select all three segments. Once all segments are selected I would create a Gradient with all those colours and apply to the selection.

H*ll yeah, could it be the “XLN-Audio-Shooting-Themselves-in-the-Foot-Day”!? Edit: No, thankfully it wasn't. I'm relieved that it wasn't just an April Fools' joke.

In space no one can hear you drum.

If it’s AD3 I agree that backward compatibility or otherwise a smooth upgrade path for the AD2 libraries is a must. But I really like the products from XLN Audio and I’ve got most of them, be it Addictive Drums, Keys or FX.

When a vector based font is rendered into a bitmap in a program like Photoshop, it normally uses anti-aliasing to make the contours smooth. Thus when the text blends with the background there’s more or less “smear” around it. Unless not only all the font attributes (size, weight, slant, spacing etc.) are identical with the Cakewalk original, but also text and background colours and perhaps most importantly rendering algorithm, there will be differences. In Photoshop CS6 (which is what I use) there are five different text rendering options which can be found at the bottom of the Font panel: None, Sharp, Crisp, Strong and Smooth. I think that newer Photoshop releases have a couple more. Depending on font attributes, the selected algorithm may have a huge impact on the rendered result. With all these different parameters I would say that it’s practically impossible to create text in a theme that matches Mercury and/or Tungsten perfectly. Unless, of course, BandLab would publish a theme font manual. But I can't really see that happen in the foreseeable future...

I don’t think that info has ever been made public. I'm using Arial Regular 10.6 points with 25% kerning which is pretty, pretty close and so far good enough for my needs, but if your requirements are very high (e.g. putting your own text over some existing text and you need an absolute perfect match) that might not be good enough.

I’ve also got a $99 offer but that’s probably because I already have the UVI Grand Piano Model D (bought as an unregistered copy for $9 over at KVR many moons ago). I like the dark tone of that one. I honestly never thought I’d be considering yet another piano library as I already have quite a few, but there were definitely some rare ones in this bundle. But will I ever use them? Guess I’ll have to watch and listen to that YouTube video again.

Both the Gran Vista Black & Blue and Carbon themes have now been updated to support GUI modifications in CbB 2019.03, i.e. the Arpeggiator Rate Lock button. Download the modified themes from the links supplied in the OP.

Should this be a precursor of putting ads in the Cakewalk GUI, then I’d definitely turn to Cubase or Studio One, both of which I bought when things were unclear. And this time I would most definitely never look back.

It is nice, but I think you’re in for a long wait. I’ve never seen UVI stuff go for Waves’ prices.

The problem is that the View > Fit MIDI Content command only works vertically (when it works, that is). I’ve said it before in the old forum and I’ll say it once again: I’d really love to see a command in the full PRV that’s similar to the Shift+F command in the Track View, showing the full length horizontally. And better yet: to have the same shortcut keys (F and Shift+F) performing the same operation in both Track View and Piano Roll View. Consistency is king. http://forum.cakewalk.com/FindPost/3493927 http://forum.cakewalk.com/FindPost/3758173

It’s called trial-and-error and anyone trying to create a theme has gone through it. I think the best approach is to first follow the browser structure. Most design elements have logical names and can most often be located by expanding the appropriate nodes. The possibility to filter Colors and/or Images under the View tab is also very useful when limiting the number of displayed elements. Design elements common to a whole group of underlying nodes are normally placed in the appropriate root node and if you can’t find it there, try one or two levels up. Also the search field located directly above the tree structure can be a real time saver, but it can also be a hit and miss as the Bakers may have called the element you’re looking for something completely different than what you would expect. Partial search strings normally work best. As to your specific question, when looking for the background color of the MIDI clips the element is definitely a Color and not an Image so enable the Colors filter button. They’re located in the track view so expand Track View > Track Pane and there you can see two elements that might be it: View Background (odd) and View Background (even). If you’re not sure if those are the elements you’re looking for, take a note of their current color and set them to a color that really stands out. Save, switch theme in CbB and see what happened. And hey presto, it worked. Buttons, knobs and faders are of course more complicated to change as they are images and not simple colors. After locating the correct buttons you might get by changing the color, hue or saturation in a program like Photoshop, but if you would like to give them your own look-and-feel you will have to dig deeper. Buttons and sliders can be done in a program like Photoshop. Knobs are more difficult but it's certainly doable (I’ve done so myself in my Gran Vista and Carbon themes using Adobe Illustrator and some simple math) but requires some knowledge of vector graphics and a lot of time as there’s a large number of different button sizes and knob ranges in CbB.

When you drag a beat from AD2 to a project it will match the project’s tempo. However, as you've noticed the right edge of the MIDI clip might not extend to the end of the measure or beat. That doesn’t have any negative impact other than visually, but to make the clip visually match the grid you may just grab the right edge of the MIDI clip and drag it to wherever you want to have it. This will also make it easier to later make multiple copies of that clip elsewhere. Also, you don’t seem to have vertical grid lines enabled. To see the grid better I would suggest that you from the Track View menu enable Display > Vertical Grid Lines > Behind Clips.

Seeing a couple of episodes of Outback Truckers I think that I can figure out the first part of your nom de guerre (i.e. “MUD”) and, yes, definitely in capital letters.

Of course I can only speculate, but my guess is that most of their customers only have a few AD Packs and that XLN Audio’s business model is based on the fact that it’s much more profitable to have a 50% sale once or twice a year and sell existing products already paid for, than to invest in creating more AD Packs.

Reading some recent messages in the XLN Audio Facebook group, there are indications that something might happen on Thursday 21st. If product related, it might indeed have something to do with this recent update. I guess we’ll just have to wait and see. https://www.facebook.com/xlnaudio.music

Una iniciativa muy buena. La comunidad hispanohablantes es muy grande pero a menudo no habla inglés. Esperamos que esto ayude a un gran grupo de personas interesadas en la música a aprender a usar Cakewalk. También sé la dificultad de aprender idiomas extranjeros. El inglés no es mi idioma nativo y actualmente estoy tratando de aprender español yo mismo. Pero es más difícil cuando ya no eres tan joven .

Yes, I get the same error but in my case regardless if I’m trying to insert a VST2 or VST3 version of Thorn 1.2. The reason why it says DS Audio in my image above is because I’m using my own Plug-in Menu Layout. That’s also why there are duplicates: I inserted both the VST2 and VST3 version side-by-side to be able to easily test both version’s crashing behaviour. But the exact same thing happens of course when I use the stock plug-in menu. I may add that I tested Thorn 1.2 not only in Cubase 9.5 but also in Studio One 3.5 (two remnants on my computer from the Great Panic of 2017). The plug-in worked without a problem in both DAWs, so my number one suspect must be Cakewalk. Sigh. Maybe I should start looking how to raise a support ticket with BandLab. Or simply re-install my old Thorn CM. It worked flawlessly.

Is anyone else having problems using Thorn 1.2 in Cakewalk? When I try to insert an instance of Thorn into a project I get a fatal error “Unhandled Exception, code c0000005” and Cakewalk crashes. This happens with both the VST2 and VST3 versions. The funny thing is when I try to insert the VST2 plugin the error message says that the failing module is “c:\program files\common files\vst3\DS Thorn.vst3”, so something is definitely wrong here. And have a look at the picture below and in particular the VST2 icon next to the selected instrument. Compare that with the text under the browser where it says “VST3”. Go figure. I have tried to re-install Thorn from the Plugin Alliance Installation Manager, this time running as administrator, and also doing a full reset before yet again running the plug-in manager. But all to no avail. So I started Cubase and tried to run Thorn 1.2 there. The Thorn GUI appeared and asked for activation. After activating the product it worked flawlessly. Returned to Cakewalk and tried again (thinking maybe it was the activation thingy that didn’t work well with Cakewalk) but no such luck. Don’t know what to do next. Send the dump file to Cakewalk support? Am I really the only one having these problems?

Yes, having both Vintage Vault and Vintage Vault 2 myself, I’ve noticed that exact same thing. Also, the current download speed isn’t that impressive. I’m currently updating OB Legacy and, sure, it’s a 16.7 GB download. But I’m connected to a 100 Mbps network so a download should have been a matter of minutes. Instead the download speed is currently 1.5 MB/s with an estimated total time of 2 hours. But I suspect I’m not the only one running updates through the UVI Portal right now. So there’s definitely room for improvements. But as one first step – great!

Maybe not a deal per se, but definitely a big deal to me (and most likely anyone who has a lot of UVI products). And besides, as there isn’t yet any Software sub-forum here, where else would it be posted? So, UVI has finally (as the last company like ever?) made a product portal where you can check for product updates. As the only way to detect updates previously has been to log in to your UVI account, check the last update date for each and every product you’ve got, and then manually download and install the updates, this will help a lot. https://www.uvi.net/uvi-portal And if this isn't such a big deal for you, well, it's free.

The problem with having a tag in front of the header is that you no longer get a straight left-aligned column with headers. That makes the subjects harder to read as it disturbs the natural movement of the eyes when used extensively. In my opinion it would have been better if the red tags had been placed after the header text and not before. Trailing tags are not a problem.

Lots of fun for $3.99.

In case anyone else is experiencing a problem with the Cakewalk audio engine being stopped when pressing the RANDOM button in any of the Audifier Randomisers series (Abstrung, Aerkord, or Vesper), I might mention that I managed to solve this problem on my system by increasing the DropoutMsec setting from the default 250 to 1500 in Preferences > Audio > Configuration File.

I usually don’t forget what I’ve bought, but I almost always have regrets for not using some of my recent purchases very much after the initial frantic preset playthrough. Although presets are not what the Randomisers series is all about. Having just bought Aerkord I now have all three in the Randomisers 1.2 series. The one problem I’ve found is that the randomize button quite often results in the Cakewalk audio engine unexpectedly being shut down. My DAW is quite powerful so that shouldn't be the problem. It probably comes down to me being impatient, not waiting for the previous sound to close the door when leaving.