User 905133

"Soon" is a bit like "Tomorrow." Both terms are futuristic; neither really gets here. "Now" and "Today" are situated in "The Present." "Forthcoming" is like "Soon" but doesn't imply a generalized time frame. I suspect even people who like to nit-pick, argue, etc. would probably agree that "Soon" implies a short period of time. Carry on, but I really think this "debate" should be done in The Coffee House.

If your web browser is zoomed in/magnified too much, you might not be seeing the Search Box in the upper right corner of the web page. Here's a link to a search I just did for "activation" with the forum's scope set to Everywhere (as opposed to This Topic). Here's a link to a search for "offline activation" (in quotation marks so the search engine looks for the phrase, not both words individually). If you are using a small form factor for your search (i.e., a cell phone), maybe you need to zoom out to see the Search Box?

Thanks for the relevant but generalized comments re: *.vst3 plugins being placed in folders named with a vst3 suffix. It prompted me to set up two new searches: "*.vst3" for files and "vst3 Folders" for folders that have the vst3 suffix.

ADDENDUM: After looking through the online NI documentation, maybe there are some Kontakt users in the forum that can address things unique to using Kontakt within CbB.

Assuming each midi track is routed to a single sound-producing midi device on one and only one midi channel, have you made sure that the midi outputs of those devices are not being introduced into the data flow? Sometimes this can happen with software synths if plugins have their midi outputs enabled.

Wish I had seen this post before the other one. See the replies in the other thread. BTW, I started with Cakewalk for MS-DOS (with hardware), skipped Pro Audio (except for trials), and then did a number of updates starting with SONAR 3. If you used sysex with Pro Audio, the CbB documentation should get you caught up. Also, you can search the forum. There are many discussions of using System Exclusive data dumps and commands using CbB.

(1) By bandlab do you mean Cakewalk by Bandlab (CbB) or the mobile device/web-based app? (2) What do you want to do with sysex (e.g, to control parameters, to save and restore bulk data dumps, etc.)? Assuming you mean CbB, you can access sysex banks and commands from the Sysx View in the menu bar. If you don't see it there check your Workspace--some factory Workspaces exclude the Sysex View (such as "Basic"). If that's the case, enable the Sysx View in your current Workspace, or either choose "none" or another Workspaces (such as "Advanced"). (3) Here's a link to the index page in the online documentation. See also: https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=SYSX.01.html#1177298 https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=SYSX.03.html#1113134

I had something similar recently. So you don't have to read the full post, I posted the solution that worked for me. (See quote below.) Others might have different solutions; no guarantee mine will work for others.

This makes sense from an "intuitive/non-intuitive" perspective. Nowadays, most drop down menus in the world seem to prevent users from typing choices. Classic example: having to scroll through a long list of locations (such as US States) in a web-form instead of being able to type a 2 letter abbreviation.

Thanks for the clarification. You had my hopes up, but just about 1/8 of an inch. ?

USB? Parallel Port? If the latter, how? The last time I called MOTU, tech support had no idea that they used to make parallel port interfaces and they certainly didn't have any documentation I could use to try to make it work under Windows 10. They do have a download page for the "MIDI Express XT original" but the driver download for Windows 10 still requires a USB version. So far as I know, the original did not have USB nor can it be upgraded; nor is there an upgrade path to any USB versions of any era. The last time any of my MOTU MIDI interfaces worked with a computer as intended, it was under Windows XP.

Will he still be doing videos for the public?

Hmmm. I didn't get an e-mail. Not sure if its because I already picked up CV-2 a few months ago (probably when I picked up the end-of-the year freebie) and there's nothing new for me. At the website, when I use the custom link, I only get an offer for non-Multiphonics Sound Packs. @Brian LawlerThanks for the clarification and for the link. Your post came in exactly at the same time as I figured it out from the website. UPDATE: I didn't get an e-mail from AAS, because the offer is not from them. Its what Plugin Boutique is offering. Owners of Multiphonics CV-1 thinking about upgrading to CV-2 might want to see if AAS has/will be having a deal. It looks like I chose a new CV-2 Sound Pack as my free gift in December and then (based on what I heard) I went for the Black Friday/Winter AAS Custom CV-2 Upgrade for $39.

Asking for clarification of this ^^^^. Are you saying that 25 new modules were added to CV-1 but only 6 of those are new to CV-2?

https://www.crackle.com/watch/8ff12fe0-faa6-49b0-8ce5-5196171984a5/the-big-interview-with-dan-rather/dickey-betts

Never mind

This statement reminds of several times throughout my life when some individuals told me they were choosing to believe what they wanted to believe about what others said I did regardless of the truth. Nowadays, sometimes I respond when this kind of thing happens, but many times I remain silent. Your claim "Silence is consent" in my opinion is generally untrue. JMO: This statement was included as an insult. You can choose to believe what you want without regard to the truth, but IMO you should not lob insults.

According to this SONAR Professional dates to the era of SONAR Platinum, which came after the SONAR X1 product.

If you have the free version Analog Lab Play, you could try exploring the Tribute expansion packs (use the search term "tribute" here before your purchase (possibly on one of the 50% off sales) to see if they would meet your needs.

(1) I cannot speak for others. (2) If you are trying to claim this is my position, I highly recommend you rethink this in the context of my posts in this thread as well as in other related threads. (3) To be clear, I never thought (or said) that a "complete overhaul . . . ." was required. (4) As regards the issue of adding additional methods/workflow options to delete markers, so far as I can see, I never opposed that. For example, see the "JMO" sections here:

Thanks for starting the discussion and for your very thoughtful replies. I would agree that anthropomorphizing the software to be saying "Read My Mind and if you can't you are rather Dumb" could be considered as a bit of a stretched exaggeration. For what it's worth, yesterday I wrote up the following and decided not to post it. It was in my edit buffer, and after seeing all the new comments thought it might be good to include: I can easily imagine that changing the current procedures (described above), so that a marker can be deleted without having to select the marker (by holding the left click button down to delete) might accidentally introduce what could be called a "regression bug." To be clear, what you call my "defense of the status quo" was not merely for the sake of just keeping the status quo. In my view things should not be kept, changed, or removed simply for their own sake independent of consequences, functionality, etc.