Can Muse give an update on 1.6?

[gizmostatic]

Yeah, I've been playing B4II on the Mac .. can't wait to get it out live. But also, FM8 (with the new arp. in it), Kontakt and Guitar Rig will be getting heavily used, and I'm sure I'll be exposing absynth, pro 53 and occasionally reaktor to our 'masses'. Of course we don't have another gig on the books until sept. Figures!

[Juancho]

Weeeeiiiiii!!!!!!
Downloading now!! and awaiting for release notes!!! Btw, what will happen with current installs?

THANK YOU MUSE!!!

/Juan

[Juancho]

ok, installed the update, but at first glance there doesnt seem to be much new except for the midi + programchange feature....better wait for the release notes....:-O

i'm happy anyway!!!! now i might be able to use The Receptor as a multieffect AND as a synth at the same time!!

yieeepieee!!

[thesoundsmith]

holy crap! I knew it would be released right before a major gig!

Yeah - I'm playing the Monterey Bay Blues Festival this weekend - all three days, all three stages (one a day.) Won't get a chance to even install it till Monday. But it's number one with a bullet on my To Do list.

Oh, the hell with it - I'm going to install it now. I don't get to use my rig this weekend anyway - B3s and RD600s everywher - but I love being able to show up for a gig with just a little pair of individual Anvil cases - for my hands...

But I'll get to try out the upgrade in the safety of my studio - this is going to be cool - not a big change, but cool

And Kim - yeah - do you have two manuals? I use the Axiom 61 on top and the Prokeys88sx below and get kick-ass bass when needed - if I could only find a reasonable answer to the pedals!

[Juancho]

Damn, i cant enable UniWire anymore, as soon as i activate it it is turned off...how am i supposed to use UniWire now???
And from what i've read, its was now possible to use windows installs on certain plugins, tried to copy one exe the usual way (Drop Installers Here) but it doesnt work...
Please advice, MUSE!

[Ben [KVR]]

The release notes aren't ready yet (hence no official announcement yet). But I can help answer these issues from what I have seen of them:

Uniwire change: The enable / disable state depends on if Receptor has a valid Uniwire plugin connection. In 1.6 Uniwire needs to find a connection before it can enable, if it cannot Uniwire disables. This is a new behavior but prevents the "no audio" problems at gigs.

I believe the windows installer feature was held back until the next release due to a further, major, underlying change that needs to take place for it to function reliably.

[Juancho]

Ok, i see, i suspected it was something like that...
Care to explain how the new programchange feature works?

/Juan

[ksiragusa]

and
Can you tell us if we can install Komplete 4?

Kim

[Ben [KVR]]

and
Can you tell us if we can install Komplete 4?

Kim

I can't comment on Komplete 4 until the official announcement (next week).

[Ben [KVR]]

Ok, i see, i suspected it was something like that...
Care to explain how the new programchange feature works?

/Juan

Cribbed from the draft release notes:

New Feature: Send MIDI Program Changes Directly to Plugins

Receptor will now allow you to send MIDI program changes directly to Source plugins, completely bypassing Receptor's own, internal patch management feature. This is particularly useful, for example, when you load a plugin that does not yet contain any "Receptorized" patches—only its own, internal "built in" patches. By using this feature, you can tell Receptor to pass the MIDI program change information directly to the plugin rather than using Receptor's own methodology for managing Multi, Single, and Plugin patches.

Route All Other Channels to Source Plugin

If, in the MIDI section of Receptor's Setup view, you set the Receptor Program Changes Channel to anything other than "All", the Route All Other Channels to Source Plugin option becomes available.

Prior to v1.6, if you told Receptor to use a specific MIDI channel for all its program change messages, it would simply "drop" the MIDI program change messages it received on the other channels. Now, if you check the Route All Other Channels to the Source Plugin option, Receptor does exactly that: It takes any Program Change message received on all MIDI channels not being used by Receptor's own program change channel, and routes them directly to the Source plugin of the corresponding patch channel.

NOTE 1: Not all plugins support changing their built-in patches using MIDI program change messages. If your plugin does not support this feature, having it enabled in Receptor will not have any effect.

NOTE 2: Some plugins, while they may support changing built-in patches via MIDI program change messages, do not actually update their graphical interfaces to reflect that a new patch is playing. This is a result of the way the plugin, itself, is programmed and is not something Receptor can remedy.

NOTE 3: If an Instrument Channel has its Source assigned to an audio input (rather than a plugin), then the program change messages are routed to the first instantiated FX plugin. For example, if an Instrument Channel uses an audio input as a source and has an effect assigned to FX A, then the program change messages will be sent to the plugin instantiated on FX A. If there is no plugin instantiated on FX A, then the program change messages are routed to the plugin instantiated on FX B, etc.

The option also appears on Receptor's front panel, and is accessed by pressing the SETUP button, then rotating the top display knob to select the Unused Pgm Chg Ch's parameter (which, of course, is a front panel-friendly abbreviation for Unused Program Change Channels).

Rotate the bottom display knob to select between the following two options:

• Go to Source plugin - turns on the feature (same as checking the box in Receptor's graphical interface)
• Are ignored - turns off the feature, making Receptor operate as it did prior to v1.6 (this has the same effect as un-checking the box in Receptor's graphical interface).

The release notes go into the background theory of this.



New Feature: Support for Plugins with Built-in Sequencers

Some plugins (such as Native Instruments' Reaktor) contain built-in "groove oriented" sequencers. On a computer, these built-in sequencers are designed to start and stop with the transport controls in your host sequencer, but Receptor doesn't have a transport control.

Prior to version 1.6, there was no way to remotely start or stop a plugin that contained an embedded sequencer (unless you were using UniWire). Now, as of version 1.6, plugins running on Receptor will respond to MIDI start, stop, and continue messages, meaning you can start, stop, and sync these groove oriented plugins over MIDI.

So, if Receptor's Tempo Source parameter (in the MIDI section of the Setup page) is set to either Internal or External-MIDI, then Receptor will receive MIDI start/stop/continue messages and pass those to plugins with built-in sequencers. If Receptor's Tempo Source parameter is set to External-UniWire, then any groove-oriented plugins are started and stopped using your host sequencer's transport controls.

[gizmostatic]

and
Can you tell us if we can install Komplete 4?

Kim

I can't comment on Komplete 4 until the official announcement (next week).

oh no!

/cue sinking feeling in stomach

well the responding to transport controls is pretty cool news. Wonder if setting BPM via 'tempo tap' might be something on the horizon?

[Juancho]

ahh, thank you very much Ben!

So if i have 2 midicontrollers that send programchange into receptor, i will be able to switch between Snapshots with one and with the other switch between presets on another plugin...?

/Juan

[tjodoin]

Ben, any hint on how to update Kontakt 2 to the latest version? Or is this the same issue as Komplete 4?

[jespero]

hi

I can't find it on muse homepage and plugorama

do you know where I can find it ????

jespero


have a nice day

[jespero]

where can you download receptor system software 1,6

jespero