User 905133

Cakewalk - Cakewalk Documentation - Freeze tracks and synths

This is the best price I can remember, too. I have also used VM in the FX bin as an FX Rack for CbB. Works for me. I can't test Nucleus either. Usually when resellers have VM bundles like this on sale there's a sale going on at Cherry Audio.** The JRRShop deal is better than $33 at CA. For those who might not know, Cherry Audio has changed to a NFR policy. So if you buy this and you don't like it from everything I've read, you will not be able to sell it (or transfer it) to anyone else (such as your heirs). For that reason, JMO: people might want to get a demo of a module or two first and if you like it, buy the bundle while on sale at the third party reseller that gives you the best perks. **From what I can see, there isn't a general sale going on at CA/VM.

Results: [ S ] and [ M ] buttons on both track and console work as expected. Simple Test # 1: Set up Proteus 2500 sound module [always in multitimbral mode (up to 32 midi channels)]. Record super simple 8 bar patterns (C01A = drums, C02A = bass, C03A = piano chords) one at a time. Tested Solo and Mute buttons. ADDENDUM: Since I never paid much attention to greyed out tracks before, I looked at this. There are different levels of grey. Selected track grey is different than soloed and muted greys. With all, some, and no tracks selected, [ M ] and [ S ] lightened relevant tracks appropriately. tested on both track and console. Note: Simple Test # 1 only has 3 midi tracks; each is forced to a specific midi channel through the [ C ] widget.

When this happened with APD (MODO DRUM, IIRC), I seem to recall some users reporting APD was kind enough to issue a refund. I am not sure if IK honored the sale as a qualifying event for anyone. JMO: It is unfortunate that loyal consumers need to find the snags in any company's marketing and promotion schemes. I don't think there was any malintent on anyone's part (IK, resellers, or consumers). Minimally it does, however, point to a flaw in communication. By that I mean specifically, that if a manufacturer will be running a promotion, (1) they should get the word out to resellers early enough for the resellers to update their websites, (2) they should send out timely reminders to resellers, and (3) they should take the initiative to check the sites of resellers. If all this was done (as it might have), the process needs to be fine tuned. That being said, I think this SNAFU was covered more quickly. So maybe next time no consumers will be affected. In addition, it might be a good idea for IK to give a free promotion entry to the first 25 loyal customers who alert them to SNAFUs like this and bonus jam points in the amount of the purchase to the first 100 loyal customers before the websites were changed.

This was my thought, too, esp. since I am more into synths/sound content than FX/Processing Tools. I passed on the TS4 MAX upgrade and even the ST4 MAX upgrade in hopes they would have a GB to fill in with new sound content. I really don't need duplicate / triplicate / quadruplicate licenses for products I have already licensed.

If I didn't already have MixBox and almost everything that would get me if the Group Buy goes to the max, I'd give it a try.

Sorry. I couldn't find what I was looking for. It might have been in a different forum. Maybe someone else has seen this before or has some ideas on how to solve it.

Something like this came up before, IIRC. I think it was within the past several months. Not sure if it was the exact same issue. If not, the solution might be different. I will look.

Hmmm. I will have to hook up an external sound module to see if soloing midi tracks works with CbB.

IIRC in the past IK has extended deals to recent purchasers. Maybe Peter is doing some IK interdepartmental stuff to try to make it happen.

I assume you mean the program installers (specifically the old AT, TR5, etc. installers) as opposed to any Sound Content installers--unless people don't mind paying extra to re-download the sound content installers when needed.

LOLOLOL. At last now I get more of an answer to the question about the difference between AT5 MAX and AT5 MAX v2. I suspected something was up with the previous answer that was not really an answer and my request for clarification which was met with deafening silence. ? After TS 2 MAX --> TS 3.5 MAX, I'm glad I didn't get TS 4 MAX. I saved a boatload of money!!! Looking forward to saving even more. ? Caveat Emptor!!! Consumers of the World, UNITE!!! ?

Yeah. Sometimes the final release is not the same as the last beta.

If this is going to be changed in the last CbB update, I would prefer either a preference check box that says, "OK to screw up my track names" with off / unchecked as the default or maybe a check box in the right-click context menu next to the Replace Synth selection options. As for changing user assigned track names, I really feel that is rather intrusive. Not sure why people can't just use the button or the Synth Rack if they get confused. Also, is there any possibility (1) undo/history might not be able to track all the name changes/replacements and/or (2) replace all tracks with this synth might get messed up? And if it any of this gets anything messed up, does that mean CbB will forever not work the way it has worked for the past several years?

Interesting. I never noticed this because I use mostly Instrument Tracks (usually combined) with some occasional MIDI Tracks either pointed to a synth in a combined Instrument Track or sometimes a split Instrument/synth only track. But I just tried. I get what seem to be inconsistent darkening or lightening depending on which track is soloed and what track the midi track is pointed to. I only did a very quick test because I never noticed this before, but something is going on when an Instrument track is soloed and an additional midi track is unsoloed. The unsoloed midi track does lighten up while the Instrument Track stays dark. Since it has been announced that there will be only one more update to CbB, I worry that if this is changed, what happens if there are regression errors. BTW, normally I also often use Instrument Tracks and additional MIDI Tracks in the same folder. That might be part of why I never noticed the darkening/lightening before. But, its really wild if you have a folder with an Instrument track and several midi tracks inside pointed to different synths and one synth is in a track outside the folder! Soloing the track folder soloes all of the relevant instrument tracks, but unsoloing the track folder does not unsolo the Instrument Track outside the folder! Hmmm. Trying to resolve all this for the last CbB update worries me that some new issues will be added in trying to resolve this. ?

For people who name tracks by function/purpose in the context of the music/composition, who might include an abbreviated or shortened synth name, and/or who might include other useful information in the track name, having the original name of the track wiped out by an automatic process just to have the name of the replacement synth in the track name field seems like it would cause an awful lot of unnecessary work. Since the Synth Rack and reflects the name of the replacement synth, if someone doesn't want to click on the track button to see what synth is there, they can keep an eye on the Synth Rack. If Replacement Synth is set up to change the name of the track automatically, the user designated track name would have to be written down, put into the Notes Browser, restored manually, etc. every time a different synth is swapped in. I can't be the only one who uses my own choice of names for tracks. On second thought, maybe I am and most people just leave the name of the synth for the track name instead of having a more purposeful name.

Thanks for confirming you were talking about default [automatically assigned] track names. I do remember sometime within the past year (possibly before that), there was an issue with track names when they were moved and that the issue was ultimately fixed. IIRC, (1) it had to do with maintaining the order of tracks and (2) there was a difference between the user's order and the creation order. Unfortunately, I don't recall if there was a difference between automatically named tracks and user named tracks.

With the unprecedented 65% off sale and the ridiculously low prices people were discussing as possible glitches in the "Melda 15th Anniversary Sale - 65% off bundles" thread, I also wondered. But I thought that maybe it was just a change of who had set up sale price calculation mechanics--that is, a technical change, not a "money grab." For more discussion of the sale to Image Line, see the KVR > MeldaProduction thread that begins sometime in February. There is at least one post from Image Line confirming their recent acquisitions.* As many know, a few months ago Cherry Audio also announced a "Not For Resale" purchase policy (going forward license owners would no longer be able to sell/transfer their purchases). I couldn't help but wonder what was going on with that, too, including the possibility that Acoustica was trying to make the Cherry Audio product line more desirable to purchase (among other possible reasons). With all that's been happening my concern has been that there is only Melda's good faith word backing up the "lifetime updates." We have no idea what the terms of the sale were. When I posted my comment on 6/19/2023, I didn't want to be alarmist. I still want to maintain a positive / hopeful attitude (all will be OK). But with Benn's Op-Ed- style Commentary, and mettelus' concern, I might as well share some of my worries, too. Some people say "You can't change City Hall," but as we know when it comes to the practices of Corporations, all rules, terms, policies, etc. are subject to change at any time. Caveat Emptor! *ADDENDUM: The comment about Image Line's recent acquisitions including Melda is in a thread entitled "Image Line Acquires UVI." From the Image-Line post: From Vojtech:

I assume you are referring to the case where people don't name their own tracks. I would be horrified if the Replace Synth... changed the names of my tracks. To me it would be a serious bug if the software changed the names of my tracks. I suppose if each track name has a flag set for cases when the name was assigned by the software (or vice versa), user-named and auto-named tracks could be treated differently by the Replace Synth... function. I have no idea if there is such a flag.

Let's get some more traffic headed his way!!

I have one of those usb floppy drives and even thought of mentioning that as an option, but I didn't think that 1992 laptops had usb ports. In fact I looked up usb and the internet said "USB (Universal Serial Bus) was originally developed and introduced in 1996 as a way of setting up communication between a computer and peripheral devices by replacing many varieties of serial and parallel ports." Never mind I had no idea laptops had 3.5" drives in 1992.

I previously asked if Workspaces will be retained. The answer was yes. But I assume if the Cakewalk Sonar UI doesn't have certain features (for example custom themes), certain UI changes will be meaningless. However, if initially theme-switching is excluded from the early releases, maybe it will be included in a later release in some modified form. I would assume if this is the case, the team would choose to keep the parameter in the *.lns file (maybe with a warning plus a check box to ignore this warning in the future or maybe a timed out notice) and switch all the UI elements that do work with the new UI system. However, with a new UI system, this might not be practical. This is 100% speculation + 100% optimism on my part. I have no standing with Cakewalk except as a user. Theming capabilities will change and there may be little to no customization in the first release of Sonar. That said, a tremendous amount of thought and effort have gone into this rework and we hope that the need for theming will be greatly diminished moving forward. The way that theming works in CbB is tortuous, so we're moving to a simpler, more elegant presentation idiom. The core customization capabilities that are needed most will likely be introduced in the future, but in a far more user friendly way than what's available in the current theme editor. Based on this I think its safe to assume that if custom-themes based on the way they are under CbB are a big part of your reason for switching Workspaces, that will be different. I am also open to the possibility that the Workspaces management system might be improved. I'm taking a wait and see attitude. (We will find out when we find out.)

LOLOL. Its been a good couple of years since you've given me shit. I was due!!!!

Background reading: https://www.digitalsoundfactory.com/wp-content/uploads/Proteus-Legacy-Library-User-Manual.pdf https://www.digitalsoundfactory.com/wp-content/uploads/E-MU-Proteus-Rack-Library-User-Manual.pdf Keep in mind, these only make use of the repackaged samples/sounds for the romplers. Evidently, there was enough interest a year or so ago for NI and DSF to work together. If they continue in this vein and do the same kind of thing for the sampler portion of the Emulator X, who can say that there would be no interest for it because its ancient? I had mentioned this as a potential opportunity for Bandlab long before NI did the romplers. Considering all the user demands for Cakewalk to have built-in sampling abilities over the years as well, it seemed to me that a strategic partnership be tween Bandlab and DSF might have benefitted consumers. Addendum: https://www.airmusictech.com/expansions/planet-earth.html https://www.airmusictech.com/expansions/proteus-2000.html https://www.airmusictech.com/expansions/vintage-pro.html https://www.airmusictech.com/expansions/xtreme-lead-1.html https://www.airmusictech.com/expansions/virtuoso.html https://www.airmusictech.com/expansions/mo-phatt.html https://www.airmusictech.com/expansions/ensoniq-asr.html