All Activity

You'll find Modules Manager in C:\Program Files\IK Multimedia\T-RackS 6. Run it and you'll likely be delighted to see what it does. Background/tl/dr: I had read the blurb about T-RackS 6 before I Bumble Hundled it that mentioned that they had added the ability to only install the modules you own (or wish to install). The spamming of unowned modules is a longtime complaint about T-RackS. By default, they dump every module in the line into your VST3 folder, which causes them to show up in your hosts' plug-in lists with no indication as to whether you own licenses for them or not. So two types of clutter, both hard drive and visual. In the past I solved this by creating a "bullpen" folder where I would move unowned modules until such time as I acquired licenses for them. I expected this ability to be part of the installer or built into IK Product Manager, but it's not. Weeks later I was doing some cleaning work on my C drive and poked around in IK Multimedia's programs folder. That's when I discovered Modules Manager. Modules Manager allows you to see what licenses you own and choose to only install those modules. IK seem to be still into the idea that you (or they) want to dump the unlicensed modules onto your system, and some of the design of this tool reflects that. So you need to be careful when using it. When you first run it, select "Show All" in the left column. Then you can look over on the right and see the ones you own and the ones that are only available as trials. Toggle the button as appropriate for each one. Then click "Apply Changes" down at the bottom. This will remove unwanted modules. What to watch out for is that the next time you run it you may get a message about how your installation doesn't match your preferences. Do NOT click yes to this dialog. If you do, it will reinstall all of the modules you previously excluded. It's a useful tool, you just have to keep an eye on it.

Hey Carl, I have to say of the 3 versions you posted for me it's- 1. SSL- exactly the type of interface I enjoy! 2. Brainworx- not as elegant as the SSL but still has good seperation and legibility. 3. Softube- the type of interface I tolerate....a huge black background with a little grey here and there and some small white lettering and invisible sideway faders for manipulation. When it gets past 3, you know full on circus peanuts and spongebob I'm out!

Wow, $129 for a refurbished 4i4 is a great price. I like refurbished gear. It often means that it was either an open box return or a warranty return due to whatever factory defect (defects happen) that has been recertified (and repaired if necessary). So what? Well, whereas final QA on the manufacturing line is performed by people who just connect it to the test rig and push a button. Go or no go. And these days, often/usually done in China. Returns are usually processed by higher level technicians who know how to make repairs and adjustments. And depending on the company and the individual unit, it might be done in the US office. So such units can end up being very well gone over.

Here's a tip for anyone using MeldaProduction plug-ins: when you go into Settings/Style and select a style, there's a selection of color presets, and you can download color presets from the Online Preset Exchange. I've uploaded a couple for my favorite style, Argon. Mostly I turn the background darkest black and use aquamarine text with burnt orange highlights. I highly recommend fiddling with Styles and colors with MeldaProduction's plug-ins. I agree with those who say that the stock style and colors are....plain? Fugly? Whatever, their basic UI is purely functional, designed for high visibility over sexiness, and I find that it increases my enjoyment of using them if I can give them a color makeover. I like the darker styles like Argon, Titanium, and Uranium Dark. I'd love to dig deeper into Styles and even Devices, but it's pretty complicated and has the traditional MeldaProduction minimal documentation.

I can't find an upgrade price but it is currently on sale for $38 Orbitron If you're new to UP, use the code UP0599432 for 20% off (I'm not sure if it will apply to sale items but worth a shot). This is a referral code.

The only difference between a Simple Instrument Track and a Split Instrument Track is that the Simple Instrument track is shown as one track in the UI. A Simple Instrument Track is in fact still two tracks, it's just that in the Track View, the header part shows the audio track, and the clips view shows the midi track. The reason they're called "Simple" instrument tracks, is that they're generally created with a stereo only output, and the MIDI track part is sent to the synth on all MIDI channels. That, and the fact they only use up one track space in the UI. Up until the introduction of Per-Output Instrument Tracks, using split instrument tracks was the only way to properly leverage multi-timbral synths. Now you can use either for multi-timbral synths - it's really down to preference, and whatever you're used to in your workflow. As a rule, we try our best not to introduce anything that would require users to change their existing workflow - and obviously there's the backwards compatibility thing with older projects, so both options still exist. FYI: Per-output instrument tracks are really just Simple Instrument Tracks where: 1. The synth is set to have more then one stereo output 2. The audio track is set to receive audio from the synth on a specific audio output 3. The MIDI track is set to output on a specific MIDI channel. ... and those audio output channels / MIDI output channels are incremented each time you "append" a new per-output track for that synth.

So, much has developed since my initial post, and still hoping for some feedback... 1) All of my Midi Devices (controllers, drum pads) work going into my Win 11 All-In-One via USB-A in Cakewalk Next, and Audacity. AND, any/all of them work on my Gen 3 iPad, which is mounted in my Behringer iStudio/Is202 docking station using Cubasis, Garage Band and my Midi Apps. AND, the IS202 USB is recognized by my Win 11, All-In-One when plugged in with a USB-B out of the iStudio to the USB-A of the computer. BUT...none of the midi devices trigger voices or tracks in any PC program, through the iStudio like the devices do directly. Thoughts? Still a routing in/out issue of the iStudio or iPad?

I’m thinking this one may be free someday.

Agree with positive comments above on Melda. Purchased and instaled the ridiculously cheap MTurboAmp. I really like the at least 2 of the 5 bass amps that come in the package. I do see an issue with the inconsistent bass amp selection screen as shown below for 2 instances of the plugin. Melda support has been slow to respond.

Hey all, Check out the Fredenstein 6-Slot 500-Series Chassis for only $359.00 ============== Key Features Universal Power Supply Increased Output Currents Modules can be Daisy-Chained Compressor Modules can be Linked Multilayer Backplane Signal Integrity Ground-Lift Switch The Fredenstein Bento 6S is a high performance module carrier for Fredenstein Series 600 modules or API-500 compatible plug-in cards. The unit can accept a maximum of 6 modules.The Bento 6 features several important upgrades compared with third party products: Universal power supply: accepting mains voltages from 90V AC to 240V AC, 50 to 60 Hz. Increased output currents: +-16V DC 3.2A and +48V DC 0.3A The Bento 6S power supply is also designed for extremely low noise largely due to state of the art switching regulators that operate above 200 kHz, which is typically higher in frequency than most conventional switching regulators. They also follow “green” guidelines that minimize power consumption to only what is needed. Auxiliary Audio Inputs and Outputs Built-in Audio Routing: Modules can be daisy-chained by simply flipping switches on the back-panel. Compressor buss linking: Compressor modules can be linked by engaging switches on the back-panel as well. Multi-Layer Backplane: Increased signal integrity and lower noise floor. Ground-lift switch: In case of ground loops, the audio ground and the protective ground can be disconnected. Please use only if absolutely necessary. Check out the Fredenstein Bento 6S <~~~~ Here Cakewalk, I have no affiliation with this company

I've got 21 and after validating online, I've never had to redo anything. Obviously.updates need internet access, but that's all.

While it isn't really the same as what's being talked about here, but it is in the same vein in that it's about making a tool for an artist to create the thing they ahve a specific vision for, I am trying to create this tool for visual art here https://endless-sphere.com/sphere/threads/adrs-artist-directed-reality-synthesis-a-tool-to-help-artists-create.129368/ If there are any interested coders / scripters / artists, I would appreciate any input there that you can provide.

Maybe use a ForEachEvent Loop do delete just CC12 events. (forEachEvent (if (&& (== Event.Kind CONTROL) (== Control.Num 12)) (delete))) For the whole fade out thing, I just use a script I have written that creates a fade out by progressively reducing the controller values of selected controllers while keeping the relative dynamics. This effects all selected controller and aftertouch event though, but I am sure it can be modified to just effect CC11 events. I think the lines you would need to change is: (if (|| (|| (== Event.Kind CONTROL) (== Event.Kind CHANAFT)) (== Event.Kind KEYAFT)) to (if (&& (== Event.Kind CONTROL) (== Control.Num 11)) You could probably think of ways to trim this script even further. Fade Out Controllers.CAL

Thank you Bjorn - next time around I will fix that kick.

Thanks for listening Nigel! Merry Christmas!

Hi Wookiee- that was @kiwichrys on Bandlab. Chrissalynn Calder in New Zealand.

I'll claim here that there's a difference between "easy-to-use" and "easy-to-learn." There's also a difference between (what used to be called "shrink wrap") software like Sonar or Vegas where there are a zillion features, some of which may be touched by the user only once over a matter of weeks or months, or even never, and software designed for a more specific task like data entry or point of sale. In the second type of software, the user is expected to be given intensive hands-on training and then probably at least at first, operate it with an experienced user close at hand, ready to answer any questions and give useful advice. In the former type, the user will have nowhere to turn to except documentation and Reddit /YouTube/forum (if the program has a large enough user base to have a useful Reddit/YouTube/forum community). With these two types of software, there's a big difference in the importance of how easy features are to figure out. In the case of DAW or NLE software, the user could go long enough between using a certain feature that they don't remember how to access and use it the first few times they need it. In the case of DAW software, it's important for the export/render features to be easy to figure out because of how infrequently a user may actually get a project to the point where it's suitable for rendering.😒 Deciding which features, options and operations should be the more "front-facing" vs. buried behind menus is important. Case in point: MeldaProduction's MDynamics vs. MCompressor, MModernCompressor and MLimiterX. MDynamics is the flagship and wins hands down in the "will it do what I want it to do" category, but I have used it on exactly zero projects despite having access to every MeldaProduction processor (and instrument). On the other hand, I use MCompressor and MLimiterX all the time, and even use MModernCompressor (MeldaProduction's Edsel) occasionally. Why, when MDynamics will do any dynamics processing task you'd ever want to do? Its feature set eclipses the other three. The answer is that MCompressor and MLimiterX are easy to learn and easy to use, and MModernCompressor has one important feature front-facing (this would be the ability to select different types of detection algorithm, including "psychoacoustic," which is buried 3 configuration screens deep in MDynamics). It saves me time and loss of flow to be able to set up the less capable processors so quickly and easily vs. the more complex and capable one. Of course, if my task were to do nothing but set up dynamics all day long, and I had to choose only one of them, MDynamics would win hands down because once you get good at it, you can do everything with it that the other three do, and probably just as quickly if it were the only choice. Despite having to negotiate multiple menus to do the same thing, I could get good at it to the point where it wouldn't matter. Much of MeldaProduction's product line has been revolutionized by the addition of "devices" that present subsets of the products' features in a variety of simplified formats with more skeuomorphic UI's. You can still ignore those and use the products in their "under the hood" mode, but I am sure that the devices have helped sell a lot of plug-ins and have helped a lot of existing users make more use of them. So software isn't always just software, design philosophies and objectives can vary depending on the intended audience and function of the program.

Anyone know what the upgrade price to full Orbitron is?

You wouldn't have needed them if you didn't have to brake so hard after the speedbumpjump landings.

I've been reading a CAL guide, and it seems CAL is very similar to LISP, a language I hated and have since purged from my memory 😜 That being said, I went through the script and rewrote it in a C-like language so I could process what was happening. I have now commented out this line ;(= Control.Num TARGET_CONTROLLER) which stops the added in #12 controllers from being converted to #11 controllers. The section that follows then still sets the existing #11 controllers to the correct values, thereby eliminating all of the extra overlapping controllers added with the script. Now I have a bunch of leftover #12 controllers, and need to delete them at the end of the script. I was looking at (EditCut [<from> <thru> <events> <filt> <tempos> <meters> <markers> <hole>]) but if I understand correctly, this can not be restricted to a specific controller? Unless there is some way to assign #12 to the active filters? Every parameter after "<thru>" is a boolean, so <filt> is either TRUE or FALSE to use filters.

The hard part about that is the landing past the part of the road that curved away while you were still in the air.

My only Black Friday purchase was a new set of tire... Yay. 🙄

I find that if I hit the first speed bump at 100 mph that I fly right over the next one! 😁

I love that idea, but.... They';ll never do that here. It costs money to build and maintain and it doesn't cause enough problems for those not doing the thing they're there to prevent. It's much easier to dump a few pounds of asphalt or concrete in an inappropriate place with plenty of warnings to let speeders slow down just before they hit it but speed back up right afterward. There are various places around here where speeding in neighborhoods is a real problem, but instead of emphasizing the speed limits and the problems they can cause, with all the signage leading up to the speed bump, there are just signs warning that there is a speed bump ahead, usually several. There may nto even *be* a speed limit sign anywhere around, or a warning of why (like "caution: kids playing" or whatever).

I would still say my best value mic was an mxl r77 ribbon. Love that thing.