abacab

It also has little to do with the DAW. MIDI Bank/Program changes are already available.

LOL! Sorry bro! ?

I bought the SampleTank 4 MAX crossgrade at the pre-sale price, which was excellent! But I was not prepared disk space wise for the enormous downloads. So I never got around to downloading many of the sound expansions that I was entitled to. So recently I did a disk drive upgrade on my system that ran about $200. When I looked at what I was missing from ST4 MAX, I was surprised to learn that the downloads had expired. So I paid the $10 for another 180 days. The way I look at it is that $10 spent now was a lot cheaper than $200 that I couldn't afford for a drive upgrade at the time. But I wish that they would change their current policy, as it is stupid.

The only thing that really interests me is the Hammond. But nothing else does as far as the potential freebies. I think I'd like to see IK offer equivalent JamPoints for the Group Buy as an alternative to claiming freebies...

Yep, I believe that is how it works now, unless you are filtering that MIDI data from the recording. But that patch number would only be useful in the context of the same VSTi loaded with the exact same bank anytime you played back that MIDI track with those changes. But your VSTi would still have to be coded to recognize MIDI bank/patch changes, else they would be ignored. Some do, and some don't.

I think ASIO is mostly trouble free if you only have ONE version installed. ASIO4ALL works great on my laptop which just uses on-board audio. I also ran into a similar issue a few years ago when a Steinberg demo decided to install its own low latency driver unannounced.

Yes I agree, but I just wanted to share how it has already been done. Coming from a MIDI hardware only background, to an in-the-box VSTi only setup, I no longer have use for bank/program changes. I believe using multiple instances on different tracks is more effective, especially if you are using samplers. The load times could be problematic if you are loading large samples when changing instrument programs on the fly. In the old days, the sample ROM was relatively small in hardware ROMplers.

Just wanted to post this here as a heads-up to anyone who installs the Sound Forge Audio Studio 13. It comes with a little hidden bonus in the form of a Magix Low Latency ASIO driver named "mgxasio4_x64.dll". ? If you are only using Windows Audio, you might be OK. But I have audio hardware and a dedicated ASIO driver for that purpose, and an apparent conflict. I began having issues starting Cakewalk, and a few other programs, that would hang for several minutes attempting to use the Magix ASIO, even though they were set up to use my real ASIO driver. Unfortunately, MAGIX didn't even ask permission to install, or bother to include an uninstaller for this driver. So I uninstalled Sound Forge Audio Studio 13, and that took care of it. Apparently you can alternatively hack it away by removing these: Go into the Registry... HKEY_LOCAL_MACHINE\SOFTWARE\ASIO - delete the Magix Low Latency ASIO driver entry HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ASIO - delete the Magix Low Latency ASIO driver entry And then remove this file... c:\Program Files\Common Files\Magix Services\System\mgxasio4_x64.dll

Interesting proposal. But I believe that this issue, and the solution for bank and patch numbers in virtual instruments lies in the MIDI standard and the VST instrument coding. Cakewalk and other DAWs are already capable of sending standard bank and patch change messages. But the VSTi's must be capable of knowing what to do with the message. VSTi's can support standard .fxb and .fxp files, with 128 patches per bank, but only if the developer has incorporated that feature, in addition to whatever proprietary internal patch bank/browser system that was implemented. Sometimes these internal banks can hold thousands of patches, so there is no way to have a one-for-one map to cross reference to .fxb banks. And each developer usually has a different internal method, as they are virtually free from being bound to the the old MIDI standard for this aspect of patch handling. The solution is to save your 128 favorite patches as ".fxp" to a custom ".fxb" bank stored in a folder that the plugin dev has accounted for. The dev also has to code the plugin to accept bank and patch changes. I initially struggled with this concept as I transitioned from years of using external MIDI instruments, external MIDI ports and cables, instrument definitions, MIDI SysEx transfers, etc. Here is an example based on the SynthMaster One User Guide.

You are correct, and I think that one is my favorite! ?

I like the restriction! It keeps me away from needlessly tweaking knobs all day. Sound designers may disagree of course, but the macro knobs are usually enough to play the instrument expressively. Now THAT would be nice!

I have the full Syntronik collection, but that is my chief complaint. Click on preset... wait ... load... The loading time for the samples is not the greatest, and I have them all on SSD now. However the sound quality is great! But, I also have the Arturia Analog Lab, and I am finding that auditioning presets in much more enjoyable in that product. Click. Load. Click. Load. I think that is the difference between sampling vs. modeling.

I would assume from your comments that you will need to dig into the MIDI file yourself and analyze what is happening. Or else you may want to post an example of the file where the community can have a look at it... without that we are only guessing. It is most likely channel assignments or controllers.

I have collected the entire iZotope "Elements" series one by one either for really cheap, or free. Maybe someday I will see the need to follow an upgrade path, then they will "own" me.

Yes grab it! I ran a couple of virtual basses through it, and it definitely adds some character! Comes with tons of SVX presets! Had big fun running my Ample Metal Ray 5 through it, and then thumping on the B string, with the amp cranked up to 11. ? But is there any way to enlarge the UI? Auditioning presets is one thing, but imagine I would go blind trying to spend any time tweaking things. Just saying, that thing is freaking tiny!

Good catch there scook. Back when I was assembling the spreadsheet for Sonar plugins and what was included in each release I was only attempting to captured the top of the line bundles. But now I do recall that it was included in the Sonar Home Studio that was even given away as a freebie a few years ago. [Edit] I corrected my earlier post about Rapture Session to cover the broader release in all Sonar editions.

I got it to work in Firefox by turning off "enhanced tracking protection" for that site. That feature is now enabled for all sites by default in the latest versions of Firefox. Some sites break when this is active. I know, dumb. But... Click on the shield icon next to the padlock on the left side of the address bar for a dropdown menu. Move the slider to the left to disable it for that site.

Grabbed a 2nd license to use on laptop.

I think I would try to get them working in Dimension Pro, or maybe even Rapture Session (which can import the Dim Pro library as a player). You should have a Dim Pro license in your old Cakewalk account if you had ever registered Sonar Producer 8 to X3, or Sonar Platinum. [Edit] Rapture Session was included with Platinum as well the entry level and up Sonar editions of that time, such as Sonar Home Studio, Artist, and Professional.

I think the movie studio line is intended for casual users. For serious audio, one could always move up to Vegas Pro, or move to a DAW for the final audio mixing task. Vegas Pro 14 User Manual (older version): PCM audio Sample Rate / Bit Depth / Channels / Compression 48,000 Hz 16, 20, or 24 bit Stereo Uncompressed 96,000 Hz 16, 20, or 24 bit Stereo Uncompressed

I agree that is probably time to avoid SONiVOX plugins. I have their Premier Collection, and there has not been a single patch or bug fix in several years. And computer operating systems and DAWs keep marching on with development and modernization. The gap keeps widening. Let the buyer beware. Sometime the price is too good to be true. In this case I believe it is, IMHO. But with all due respect, I don't believe that Vocalizer Pro specifically has ever had crashing problems for me. But it can be a bear to set up correctly in your DAW of choice.

Good rundown. Been a fan of Humble for a while now, and scored some great deals with it! Have Vegas Pro 14 as a result, and have managed to use it on a few small projects. Was really wondering about the Video Pro X thing and Movie Studio Platinum 16. But my point and shoot camera and smartphone have video record mode, so...

It looks like the AAS Player in the example above is directly hosted in Cakewalk. If that is the case, then the issue is not likely to be only with KK. Pics are great, but I wonder if they can give step by step actions to reproduce the issue, starting with a new blank project, then exactly how the instrument is inserted, and any track settings are adjusted, etc. I cannot reproduce the issue here based on what has been discussed so far.

Ahem! We will be needing the link for the free beach pad! ?

Which sample format (Cakewalk?) and what virtual instrument were you using to play them with?