Blue Cat Audio: new product and new year prices

[Blue Cat Audio]

We are happy to announce Blue Cat's Remote Control, a 3 plug-ins set with special MIDI I/O capabilities: either as a MIDI remote control, remote monitor, MIDI CC mapper or automation transformer, this virtual control surface declined in 16/32/64 parameters versions offers advanced skinning capabilities to let you customize the way you control your Digital Audio Workstation (DAW) and MIDI hardware. Several step by step tutorials are available to learn how to use this unique product.



Like many other products, Blue Cat's Remote Control is available for a special new year price until the end of January: check the new year discounts!

Main features:
- Virtual MIDI control surface and monitoring tool.
- Control or monitor in real time any MIDI-controllable plug-in or external MIDI device.
- Customize the controls response curve with advanced settings.
- Create your own Digital Workstation controller thanks to Blue Cat's Skinning Language.
- MIDI learn.
- Full automation support.
- DirectX and VST formats.

Price (Special introduction & new year price):
33.15 EUR (instead of 39), or USD 39.8 (instead of USD 46.8 )

Happy new year!

[aMUSEd]

This looks useful. Could I use it to control my Yamaha VL70 for example and can it change patches too? (even better does it support patchname lists?)

[Blue Cat Audio]

can it change patches too? (even better does it support patchname lists?)

Today it exclusively works with MIDI CC (it's a parameter-oriented controller) but other MIDI capabilities might be integrated in the future.

[Jake Jackson]

Patch changes are part of the midi specififcation:
cc 145. Does this product support that parameter?

[Blue Cat Audio]

145? Aren't MIDI CC numbers supposed to be in the 0.127 range? As far as I remember the Patch Change messages are different from Control Change messages (the only ones implemented today in the Remote Control).

If you use the CC0 and CC32 bank select controls, maybe it would work (it depends on the MIDI hardawre you are trying to control). Like all our plugins you can affect any channel/CC Number to any parameter. Maybe a custom skin would be necessary (today skins are parameter-oriented and thus display a percentage). That's something that could be customized quite easily.

[Angelo]

This application is very useful as it is. But I think that many of us are working with external midi devices too. I have a DTXtreme IIs drum module that is not supported by any commercial editor/librarian. It would be great to have on the same screen the VSTI parameters and patches together with the same information for the external modules. Probably this would require an implementation at the system exclusive level but the product possibilities would be largely extended. It could be transformed in an universal VST editor/librarian where each hardware instrument interface could be programmed by midi learning or manually editing system exclusive and CC messages.
Any possibility to see this implemented in a near future ?
Best Regards
Happy New Year
Angelo

[Blue Cat Audio]

This application is very useful as it is. But I think that many of us are working with external midi devices too. I have a DTXtreme IIs drum module that is not supported by any commercial editor/librarian. It would be great to have on the same screen the VSTI parameters and patches together with the same information for the external modules. Probably this would require an implementation at the system exclusive level but the product possibilities would be largely extended. It could be transformed in an universal VST editor/librarian where each hardware instrument interface could be programmed by midi learning or manually editing system exclusive and CC messages.
Any possibility to see this implemented in a near future ?

It would be possible to add at least Program Change support to change MIDI hardware patches quite fast. For sysex functionalities, it might be a bit more complicated to use (it really depends on your scenarios), but feasible. Do you have sysex commands examples that your hardware uses?