User 905133

Is it safe to assume you are referring to the admiral's attempts to measure "MIDI Jitter" in different DAWS?

Just last night, I uninstalled ST3 (and all my other IK Instruments/Tools) but for a different reason. (ST3 plays different ranges of the keyboard with different levels of loudness. Syntronik and MP2 didn't have this issue.) So, although, I have no opinion on your issue, I'd be very interested in suggestions for removing all the sounds and the sound packs/expansions. (Apologies if this if off-topic, but I did think it was related because if you remove IK GBs, I'd be interested in knowing the best way(s) to do it.)

Looks somewhat interesting. I was intrigued by the role of the microprocessor (represented by an Arduino in the image). It reminded me of MIDI responsiveness tests using different baud rates [serial communication rates] going into a joystick port using a standard joystick interface cable (IIRC) from a Mega 256 and driving a software synth [E-Mu]. I was pleasantly surprised that I could pump the data out at 11520 baud and the PC / soft synth handled it at that speed.. I just took a quick look at the links and didn't see anything that talked about the serial communication rate, although that might be negligible in terms of measuring total "jitter." At the time I used a standalone soft synth. It might be fun to dig out the Mega 256 and see if I can pump MIDI out that fast to the DAW. (Not sure it would be possible.) Anyhow, thanks for the links. ADDENDUM (after I read John's comments) -- from the video linked above:

I believe it. Stuff like that happens!!!!

Is the CC for the pedal configurable? If it previously also output 0x41, were you using a map to change it to 0x40? Maybe a map got changed? Also: how is the pedal getting into your PC [i.e., what gear]? Maybe that's where the mapping was done and somehow it got changed?

I don't. I use the in-app updater. Menu Bar > Help > Check for Updates.

From Bat Out of Hell to his infamous flap with Gary Busey Meat Loaf shared with us amazing moments from his life with unforgettable passion. RIP.

So tempting to post Zappa's "Broken Hearts are for _____ ________." Not sure that will get past the decency filter. ?

I did this several hours ago (5 3/4 hours ago) and forgot about it. When I looked, it still said "updating." Surprise, surprise. AHA!!!! The full executable seems to have been downloaded and is in a sub-folder called "pending." No hidden pop-ups telling me to do something to complete the installation. I will try (1) running it and if that doesn't work (2) rebooting my PC. UPDATE: I tried (1) and (2) and then a number of other steps. BLA Beta is not a top priority for me, so I just manually downloaded and manually installed the most recent BLA (10.2.0). I'll let others try the Beta (10.2.1). On the positive side, although I couldn't find any Genre Pack MIDI files, I did give the automatic get-started idea generator a roll of the dice. Also, I found some Bandlab MIDI files I downloaded in 2019.

Their genre packs used to have midi files, but the last several times I only found the audio files. Does anyone know if they still have the midi files available somewhere?

Completely Irrelevant. It says ALL T-RACKS USERS...not "select" or "Group Buy Participants Excluded"! It shouldn't matter if I have 500 Licenses....ALL T-Racks users means "ALL" I agree it shouldn't matter in terms of the stated rules. I was interested in what excuse they would give. Same here.

Did you buy TS MAX 3.5 after GB25? If so, try telling them that you should have been entitled to the promotional EQ-81 based on that purchase, not based on the prior GB25 "freebie" selection.

YUP!!!!!! But the OP seemed to be interested in the deep structure of MIDI:

The short answer: No. The high bit in the program number being 0 is intentionally used to identify the number as data. The long answer: When you asked "Is the high bit of the program number simply unused, reserved for future use?" I assumed you understood the structure of midi commands [midi status bytes and midi data]. Evidently I assumed too much. Sec while I look at the link. 1100 in binary = 0xC nnnn is the channel number (0x00 to 0x0F) corresponding to human numbers 1 to 16 1100nnnn represents 0xCn, aka the Program Change Command in MIDI 0ppppppp represents the Program Change Value. --------------------------------- This is a two-byte MIDI command. The first byte is the status byte. Since the highest bit is set [1100 nnnn] it says, "Hey, this is a midi command." Since the first half [nybble] is 1100 [0xC], it says, "Hey, this midi command is supposed to do a program change." nnnn says, "Hey, do this patch change on MIDI channel nnnn [1-16, where nnnn goes from 0000 to 1111]. The second byte is the MIDI data. Since the highest bit is clear [0ppp pppp], it says, "Hey, I'm MIDI data [not a MIDI Command]." Since MIDI data is 7 bits long, it goes from 0000 1111 to 0111 1111 (or, 0x00 to 0x7F; or 0 to 127) In the status byte, the highest bit is set. That tells any program/routine that is processing midi, that it is a midi command as opposed to midi data. If you are using software that handles MIDI for you, you shouldn't have to worry about trying to set the highest bit in the data byte. If you are writing your own code, it would make a difference. Bank Select / Bank Switching (where implemented) is included in the MIDI Spec so gear and users can switch banks of 128 programs/patches/presets. Pages 12-13 of the document you found show the Continuous Controller MIDI data bytes for selecting banks. Control Change commands are 3-bytes: status, CC number, data value.

The high bit in 8-bit midi is a midi command flag. So data [the bytes that follow the command in 2-byte and 3-byte MIDI command formats] use the lower 7-bits. Example 1: 0x90 0x4F 0x7F, where 0x90 is a note on command for midi channel 1, 0x4F is the note number [runs from 0x00 to 0x7F] and 0x7F is the velocity [0x00 to 0x7F]. Example 2: 0xCF 0x7F, where 0xCF is a program change command for midi channel 16 and 0x7F is "patch" 128 on a 1 to 128 scale, or 127 on a zero to 127 scale.

Based on this and GB25 I finally figured out IK's modus operandi: Give customers free duplicate (and triplicate and quadruplicate and . . . ) licenses so they feel good about getting so many "freebies" and then spend more money to get a few things they don't have bundled together with many things they already have. ? Larry, same here I'm not getting a pop up. I already have it, I'm just greedy. Because I already have it is probably why it's not popping. Seriously though, I will not pretend to understand the complexities of IK's website and product software utilities (i.e., authorizer, manager, custom shop, etc.), their product pricings, their promotions, etc., but I can tell you that I was able to get an extra / free license for this. I know I clicked on some popup somewhere for the EQ-81 when it showed up and now I have a specific license for it as opposed to it being included as a piece of "gear" within in a product variant within a bundled product I "own." Disclosure: I have been told that there are reasons for having multiple licenses and acquired many additional licenses I didn't think I needed as "freebies" in GB25. Not sure I will ever use them, but hey . . . they're free, so why not? Helps me feel good that I got something free. ?

Thanks for the question and the replies. I have used several plug-ins which have multiple outputs and this discussion confirms what I have done and expands some interests I have. I don't have/use Kontakt, but I have used TTS-1 and Proteus X/Emulator X which (1) is multi-timbral [in a single instance] and (2) can be instantiated with a set number of outputs based on a pre-instantiated setting [from 1 to 39 outputs]. Fascinating that there are plug-ins which can dynamically create outputs!!!

Bandlab v. Cakewalk by Bandlab

D & D!!! ? Not only is it a duplicate, but its also deceptive (both here and in the original thread from 10 hours ago). It looks like its a video, but its not. Its a static image of a youtube video!!!

two

Pong.

The Inspector-based Arpeggiator in Cakewalk. The MIDI Remote Control bug makes it unusable for my purposes. If not for that, I would gladly use it. Alternative third party software with arpeggiator functionality is not necessarily better on the whole, but if it allows for MIDI Remote Control, it can do things that Cakewalk can't.

Until yesterday, I never thought of this as an issue. If I could replay all of the times I used versions of SONAR/Cakewalk that had the track widget buttons, maybe I'd find that I consistently click on the down arrow, or maybe I just do what John does and it happens so fast (eye-hand automatic pilot) I don't notice it. I'll never know since I don't have a time machine. ? Seriously though, I checked the earliest version of SONAR/Cakewalk I have installed on my main PC--SONAR 8.5.3.282 (pre-Skylight UI). There are track widget button hot spot inconsistencies there, too. So, I assume its baked in. Probably safest to just click on the down arrow.

I am sorry, but while the hot spot is inconsistent, calling it "extremely counterintuitive" is 100% hyperbole. Clarification: Pressing a down arrow to trigger a dropdown menu is consistent across many pieces of software. Pressing an up arrow to trigger a dropdown menu would seem to be "counterintuitive" to use your term. The fact that there are extra hotspots to trigger the dropdown menu for some of the track control widgets but not others is inconsistent UI behavior. Bonus hotspots are not really "extremely counterintuitive." Anyone who presses on the down arrows will find the UI behavior consistent.

Suggestion: If you use a factory Workspace and tweak it, also tweak the name (that is, don't simply resave it as "Advanced").