User 905133

Thanks for the heads up. I hope the new version solves a number of issues with the previous version without introducing new issues. Minor issue: The new version still fails to report information correctly. For example, On the opening page, I am told I have 4 Updates. But, once I press Manage my Products, there is only one product allegedly needing an update. (Not a "regression error" so far as I can tell; the previous version did the same thing consistently.)

The free, CS versions of their products give you a handful of gear plug-ins for free, and you can purchase additional gear, collections through the Custom Shop application (as well as from the IK Website, third-party vendors, etc.). There are also promotions where you can get gear--group buys, promotional freebies, etc. There are lots of people in the forum that know a whole lot about IK's products and promotions. You can learn a lot be reading some of the older threads related to IK.

I was looking for a comparison of Audio Lunacy's Cube Mini and Cube and found this. Thought others might be interested in the comparison: They look interesting.

Fun, funky song, but to me Falafel will always be food. https://www.tarazifoods.com/shop/falafel-25-lbs/

https://www.belgianstyleales.com/product/order-lindemans-kriek-cherry-lambic-25oz/shop-belgian-beers-sorted-by-name If I were to celebrate the release of a Cherry Audio Synth, I'd go for a Cherry Lambic. ? Not sure if I can find one of those near me, so I might have to go for Cherry Wheat. https://www.samueladams.com/our-beers/brewmasters-collection/ale/cherry-wheat ?

Thanks. I saw a couple of Syba FW pci-cards at NewEgg. SYBA SY-PEX30016 3 Port IEEE 1394 Firewire 2x 1394B & 1x 1394A PCIe 1.1 x1 Card TI XIO2213B Chipset was $25.00. There were others at various price points, too. SYBA Low Profile PCI-Express 1394B/A Firewire Card Model SD-PEX30009 is $38.00. Seem to have some differences. Will have to compare.

Thanks for the additional comments. I actually managed to get your Control Surface installed and showing up in Cakewalk. I will make time to explore it more thoroughly. Interestingly enough, I found Tom's FW-1884 documentation a number of year before I joined the forum. So when I saw him here, I took the opportunity to thank him for putting together and for maintaining his excellent repository. Footnote: I actually have it running off the FW port on my E-Mu Digital Audio Station card. Over the years, several upgrades to Windows 10 gradually killed the use of the other E-Mu driver functions (audio, then clock), but fortunately the FW port still works (knock on wood).

Translation per Google translate.

I also always have a floating Control Bar as soon as Cakewalk starts. Here's how I did it: I floated it in some of my Workspaces and those are the workspaces I use almost all of the time. One of the floating Control Bar Workspaces is always in effect for me. Wait a sec. Let me do an experiment. Switch to My First Lens (which has a top-docked Control Bar). Close Cakewalk. Restart Cakewalk. Its docked on the top when Cakewalk starts. Maybe your Workspace got changed or corrupted? Not sure if the Control Bar right-click context menu or if screensets will so something similar.

It is a standard for tuned pitch forks. ?

So glad its 440 and not 432! ?

I learned something new: I'll file this under totally useless knowledge. But it did make me laugh.

First of thanks, but I am not sure I am one of those 3 or 4 very special people. I use mine as an audio/MIDI interface / monitor mixer. I think of it as a control surface in a very generic sense, but in terms of integration with Cakewalk, I am not using it as a Control Surface (as in controlling the Cakewalk UI / Functions from the FW-1884). However, all your effort here has inspired me to at least put it on my to-do list to try. It does look very cool. If I can install it and get it working, having the FW-1884 in an interactive a window might open up some new workflows. Out of curiosity, what sub-forum was this in before it got moved? QUESTIONS: Do I need to install the original plug-in? ( I have the v1.22 SONAR x64 installer if I need to install that.) Since I don't use it as an official Control Surface, it won't be intuitive to me. Is the SONAR 2 (Windows) Notes - sonar_note_1_00 pdf a good document to help get me up to speed in understanding the integration with Cakewalk? A while ago, I did use MIDI-OX to see what data the buttons, knobs, and sliders send, so I understand how the communication protocol works. I just never got around to using them with SONAR (except with a basic test once or twice to watch the faders move and to test some possibilities to control soft synths). Thanks.

I looked and found a number of older threads that address transposition, key signature, etc. However, none of them directly address the issue you raised. The short answer is: (a) transposing notes up 2 half-steps in a song to change their pitches is one thing; (b) transposing to and from instruments that read music in different keys (e.g., a C instrument and a Bb) is different.

Does "dedicated MIDI I/O" mean 5-pin DIN connectors (female)? If so, you can use standard 5-pin DIN cables (male-to-male). Are the file *.syx files? UPDATE: I just looked at an image of the Focusrite 18i20. On the back there is a pair of 5-pin DIN connectors. Cakewalk still has a sysex module / view. Load the file(s) into a bank; send them one at a time. As for configuration / settings, if the D-50 shows that the data is being sent too fast, Cakewalk settings (but you might not need them). I have also uses MIDI-OX, but I prefer SONAR/Cakewalk. I have used it for years to back up presets for different sound modules. I have sent sysex to some Roland gear, but not in a while. I don't think they had hardware switches to enable/disable the receipt of sysex data. Also, other gear I had required software parameters to be set correctly to successfully receive sysex commands. I d not recall the older Roland gear having that. If the sysex data/commands were properly formed, they should work. UPDATE: From the D-50 manual: "The Bulk Dump and Bulk Load processes function whether the exclusive switch in MIDI Functions is ON or OFF." Roland sysex uses a checksum byte, but that only has to be calculated if you have hand assembled the sysex commands. If you are restoring factory data, or a download previously sent from the Roland, you would not have to recalculate the checksum.

I am a big fan of echo/delay--sometimes synchronized, but often fractionally random. So in terms of musical preference, random midi latencies of the miniscule variety (jitter) is often OK. On the other hand, a few days ago, I tried to synchronize a software sequencer in a particular soft synth with a BPM hardware sequencer. I have had no problems synching hardware across a span of 15 feet via MIDI. I would go crazy with all sorts of pitch wheel, pitch bend, and CC data, even testing the setup by wildly changing from 0 BPM to 300 BPM from the hardware sequencer to all the gear. Those modules never lost any clock bytes!!!!! However, with the BPM sequencer and the PC both within arms distance, the software got totally messed up with some very basic BPM changes--like from 120 to 78 over the span of several seconds. Since the hardware could handle extreme changing in timing but the software couldn't, I don't think it was a problem with MIDI but with how MIDI was implemented. Yup!!!! I have spent over 2 years trying to see if I can make a move to software synths. After the attempt to sync my BPM sequencer to a PC based soft synth less than a week ago, I am now wondering if even basic MIDI synchronization can be done much less eliminating miniscule latencies. Maybe time-stamping all midi data in MIDI 2.0 will work with PC based tools music-making. Great discussion!! Thanks for raising the subject.

Thread Chronology: Q &A sub forum : Feedback forum (this one): Q &A sub forum: Feedback sub forum (this one):

Which category do you think the Elka-X falls into--more like generic trash or more like GX-80 quality? Personally, I have been enjoying it more than a couple of the other recent original instruments. As for the GX-80, I think they went all out to assemble an amazing team of sound designers. Do you think that helps make it a quality instrument?

The transpose function and the key signature are separate things. Key signature relates to which notes are sharp and flat. Transpose relates to note pitches and how they look on a staff. There are threads where this is discussed complete with screen shots if I recall correctly. Unfortunately, it is too late in the day for me to look. Transposing notes in a song to change the pitches regardless of the instrument is different than transposing notes so instruments of different keys will sound the same. Sorry. It is late and I know that explanation is not as good as it can be, but I hope it points you in the right direction.

I don't currently have a full-featured multitimbral soft synth that I can use to test, but I used to do this with hardware and a now-legacy multitimbral soft synth. I am not sure how it would work with TX16Wx, but assuming you have multiple midi tracks each having data on a single track, here are some steps to try: Using the Track Widget Control set to "All" point each midi track to the same synth [O = Output Track Widget] point each midi track to a different channel [C = Destination Channel Widget] I don't have TX16Wx, so it might need some other set-up steps and it might not work with that synth. When you say Cakewalk only sends data to MIDI channel 1 to a multitimbral synth, it sounds to me like a setup issue. The last time I looked, Cakewalk still sends midi data to different midi channels. CONFIRMED! If those steps don't help, maybe post an image of the track header containing the widget settings to show the routings of each midi track. PS: I am installing TX16Wx now to give it a try. I downloaded and installed TX16Wx and rescanned my plug-ins. UPDATE: Conclusion: Try the steps. I don't have the time to look for samples to load up, but Cakewalk definitely sends midi data to different slots. Here's what I did: Created an Instrument track with TX16Wx. Created three MIDI tracks by recording random midi keypresses on each of three midi tracks. NOTE: I did not record midi data on the instrument track. (Its simpler that way, but it could be done if you record the data on different midi channels.) Pointed each of the three midi tracks to the TX16Wx (using the Output Track Widget). Pointed each of the three midi tracks to a different midi channel (using the Destination Channel Widget). I can tell by the virtual LEDs on each of the TX16Wx Slots, the different midi tracks were sending data to different slots. Thanks for mentioning the TX16Wx. Looks cool. ?

Friendly suggestion--wait until everyone has upgraded their systems (including all gear) to MIDI 2.0. As you know MIDI is serial communication. I haven't read the 2.0 docs in a couple of years, but as I see it, when all software and gear uses all the extra data in the expanded formats, there will be a period of what Thomas Kuhn called a paradigm shift which will result in chaos until the "normal science" of MIDI communication settles in into something a tutorial can safely talk about with any accuracy, reliability, and practical value (usefulness). PS: As a hobbyist, several years ago I gave some thought to how I might use a microprocessor to create a MIDI data converter to actually do something with the extra data. But I decided that manufacturing teams were also probably working on it and they could devote more resources to it than I could. From what I've seen of a few videos over the past few years that document midi latency and what some call jitter, with widespread marketing of MIDI to MIDI 2.0 converters, routers, handlers, or whatever they will be called, all the current video documentation will be out of date. JMO: Good to do the research to keep track of what people are saying, but postpone your judgments and have a very probative stance in any videos. Maybe a series on "What we know now" that take snapshots of current ideas where subsequent videos do a recap ("The last time we discussed _____________, _____________________." + an update to add new information, changes, etc.) Trying to be helpful so you don't have to keep on revising videos. More of a historical approach, than a how-to-use-it approach.