Synapse The Legend HZ

[Steedus]

Just got an email offer from Reason for an extra 25% off the intro price as I own the original Legend. It’s a helluva lot cheaper than a Moog Muse.

I have Legend... I received no email for this sale or the last sale on reason 13....
I have been a user since reason 2.5 and rebirth. I am on their subscription list.
I just resubscribed after contacting them about this.

If you can't remember ever receiving emails, try another email address. For some reason, Reason emails never came through to my main email address, so I changed to an alternate one, and started getting their emails from then on. Don't know why..

[Loque]

Are the controls of the backside automatically?

[turn2on]

I’m wonder if yes, by SDK all controls at rear panel can’t be automated

[Loque]

I’m wonder if yes, by SDK all controls at rear panel can’t be automated

Why not? A few devices allow this and many devices have automatable parameters which are not available on the UI.

[Loque]

Contact him.

I did that and heard back and came here to report. They confirmed that more CPU usage is expected, but not 2x and they said they will look into it

Maybe it is related to the polyphonic compressor?

[Mattvank]

This comes unexpected. Above all it shows a active and alive platform. Thx to all Developers!

[TritoneAddiction]

So I take it this HZ version is a seperate instrument from the original Legend? It's not an upgrade, meaning my old Legend won't disappear once I buy and install this right? I'm hoping the two can coexist in the rack.
I'm talking specifically rack extensions here, not VSTs.

[turn2on]

Why not?

- All automation/MIDI/Remote controlled properties must have a representation on the front panel
- widgets on the back panel not possible to automate or remote
May be something changed, and I skipped this, but usually its rules for widgets at rear panel.

A few devices allow this and many devices have automatable parameters which are not available on the UI.

This is possible to not create widget for the property at the front panel, but you ask (as I understand) about properties widgets at rear panel. They cant be automatable or remote. In other words - all properties controls (widgets) at rear panel - non automatable

[deeplink]

Why not?

- All automation/MIDI/Remote controlled properties must have a representation on the front panel
- widgets on the back panel not possible to automate or remote
May be something changed, and I skipped this, but usually its rules for widgets at rear panel.

A few devices allow this and many devices have automatable parameters which are not available on the UI.

This is possible to not create widget for the property at the front panel, but you ask (as I understand) about properties widgets at rear panel. They cant be automatable or remote.

To get ability to "automate" the back of rack, stick in a combinator

[joeyluck]

I did that and heard back and came here to report. They confirmed that more CPU usage is expected, but not 2x and they said they will look into it

Maybe it is related to the polyphonic compressor?

It's not engaged on the 'legacy' patches.

[turn2on]

To get ability to "automate" the back of rack, stick in a combinator

Yes)) Good addition.
This is always working trick) But out of the RE

[joeyluck]

So I take it this HZ version is a seperate instrument from the original Legend? It's not an upgrade, meaning my old Legend won't disappear once I buy and install this right? I'm hoping the two can coexist in the rack.
I'm talking specifically rack extensions here, not VSTs.

Yes, it is separate and will install alongside the original and not replace it.

[Loque]

- All automation/MIDI/Remote controlled properties must have a representation on the front panel
- widgets on the back panel not possible to automate or remote
May be something changed, and I skipped this, but usually its rules for widgets at rear panel.


This is possible to not create widget for the property at the front panel, but you ask (as I understand) about properties widgets at rear panel. They cant be automatable or remote.

To get ability to "automate" the back of rack, stick in a combinator

Exactly this requires automatable controls or values.

[Loque]

To get ability to "automate" the back of rack, stick in a combinator

Yes)) Good addition.
This is always working trick) But out of the RE

No, this is not a workaround. This requires access to the values, which means they must be automatable.

[Loque]

Why not?

- All automation/MIDI/Remote controlled properties must have a representation on the front panel
- widgets on the back panel not possible to automate or remote
May be something changed, and I skipped this, but usually its rules for widgets at rear panel.

A few devices allow this and many devices have automatable parameters which are not available on the UI.

This is possible to not create widget for the property at the front panel, but you ask (as I understand) about properties widgets at rear panel. They cant be automatable or remote. In other words - all properties controls (widgets) at rear panel - non automatable

I speculate it is possible to have a automatically value and redirect it's change to the back control, even if the back control cannot be automated directly.

[Steedus]

whoa, that's a lot of knobs on the rear!

[TritoneAddiction]

So I take it this HZ version is a seperate instrument from the original Legend? It's not an upgrade, meaning my old Legend won't disappear once I buy and install this right? I'm hoping the two can coexist in the rack.
I'm talking specifically rack extensions here, not VSTs.

Yes, it is separate and will install alongside the original and not replace it.

Good. Thanks Joey!

[joeyluck]

ABL3 achieves automatable controls on the back by mirroring them on the front. Option-clicking also works on the controls on the back of ABL3.

I suppose if your design choice is to have a series of knobs only accessible from the back panel, someone could try this—create an inaccessible front page with all the knobs mirrored there, with no way for the user to navigate to them (by leaving off whatever button or switch to get to them). But tie them to the knobs on the back, making the back panel the only place to control them. Not sure if that would pass acceptance, but technically I think that would work.

[selig]

ABL3 achieves automatable controls on the back by mirroring them on the front. Option-clicking also works on the controls on the back of ABL3.

I suppose if your design choice is to have a series of knobs only accessible from the back panel, someone could try this—create an inaccessible front page with all the knobs mirrored there, with no way for the user to navigate to them (by leaving off whatever button or switch to get to them). But tie them to the knobs on the back, making the back panel the only place to control them. Not sure if that would pass acceptance, but technically I think that would work.

Pretty sure that won’t pass acceptance or otherwise why not just allow automation on rear panel controls?
An option would be to have an alternate front panel that has all the back panel controls and IS accessible, something that’s been possible to do since ‘tabs’ were added.
Also not sure you can have a “tab to nowhere” so to speak, so that’s two possible strikes against your suggestion. I assume this would have been done by now if it’s possible but who knows…

[joeyluck]

ABL3 achieves automatable controls on the back by mirroring them on the front. Option-clicking also works on the controls on the back of ABL3.

I suppose if your design choice is to have a series of knobs only accessible from the back panel, someone could try this—create an inaccessible front page with all the knobs mirrored there, with no way for the user to navigate to them (by leaving off whatever button or switch to get to them). But tie them to the knobs on the back, making the back panel the only place to control them. Not sure if that would pass acceptance, but technically I think that would work.

Pretty sure that won’t pass acceptance or otherwise why not just allow automation on rear panel controls?
An option would be to have an alternate front panel that has all the back panel controls and IS accessible, something that’s been possible to do since ‘tabs’ were added.
Also not sure you can have a “tab to nowhere” so to speak, so that’s two possible strikes against your suggestion. I assume this would have been done by now if it’s possible but who knows…

My suggestion wouldn't include a tab to nowhere, like I had said it would include no tab. I agree that a solution if wanting to automate the controls on the back would be to just have a separate page on the front with the controls mirrored there, but I'm just offering an idea while considering a dev's decision to not use a page on the front panel in the first place.

And of course you can't just move them from the back panel to the front because then you have compatibility issues. I think mirroring as many controls as The Legend HZ has with an accessible front panel page would just feel like a bit much...like why have a back panel that busy if there's a front panel page you can use? ABL3 only has a few controls mirrored.

I think Murf's Valley Plateau has the best implementation of mirrored controls because it feels planned and not like an afterthought. The controls are not only mirrored for their settings, but their placements are mirrored as well. I remember people saying what audiorealism did wasn't possible, until it was done. I remember offering the suggestion for switchable skins as soon as the switchable panels were possible in the SDK and people told me it wouldn't work...and then turned out it did. Who knows what they will accept or fail. Don't know until you try

This is all hypothetical. I don't know if Synapse is even interested in making it possible to automate the back panel controls.

[joeyluck]

Reason Studios interview with sound designer, Kevin Schroeder:
https://www.reasonstudios.com/news/post ... -legend-hz

Very cool to learn about the process and the patches that have been used, such as "The Stone" which was used in Wonder Woman 1984. Would love to learn about what other patches have been used and in what films.

[moneykube]

I have Legend... I received no email for this sale or the last sale on reason 13....
I have been a user since reason 2.5 and rebirth. I am on their subscription list.
I just resubscribed after contacting them about this.

If you can't remember ever receiving emails, try another email address. For some reason, Reason emails never came through to my main email address, so I changed to an alternate one, and started getting their emails from then on. Don't know why..

they got back to me immediately and told me I had unsubscribed, but since I resubscribed yesterday both offers are now valid... I don't remember unsubscribing, but I guess it is possible.

[Despondo]

New interview with Kevin Schroeder on Reason Studios site:

https://www.reasonstudios.com/news/post ... -legend-hz

[joeyluck]

New interview with Kevin Schroeder on Reason Studios site:

https://www.reasonstudios.com/news/post ... -legend-hz

I shared that above
But nice to share the picture!

[RobBarnett]

I already had the Legend RE and synapse gave me the crossgrade to the VTS version for free, last night I bought the upgrade to the VST version of Legend HZ for £69 as I want the mpe capabilities