Musikmesse 2012: Propellerhead to share "exciting news"

[VitaminD]

Not having to program to windows vs mac, set up a store-front website, and a free SDK makes me want to make a few things I've been itching to have in Reason (mostly CV mangling in a more refined and easier way). Now I need to figure out how the hell to start a corporation and get a tax id. Wish that wasn't a requirement but I can understand the need for tax laws.

Yes it is tempting.. even if just to play with DSP.

Have you Considered a Limited Liability Company (LLC) ?

[justin3am]

i suppose i can use SW in another DAW via Rewire? (never used it)

Yeah, I think that would work. I'll have to give it a try tonight.

Reason is really fun to dick around with. I haven't tried to complete a project with it but it's very cool to send audio from Reason to my modular and then back into Reason for sampling and FX.
It's easy to use, quick to set up and I've always though it sounded good. It doesn't do everything I need but no one tool does. If I were you, I'd check out the demo, it's unlimited as far as I can tell, you just can't save anything.

[bmrzycki]

Not having to program to windows vs mac, set up a store-front website, and a free SDK makes me want to make a few things I've been itching to have in Reason (mostly CV mangling in a more refined and easier way). Now I need to figure out how the hell to start a corporation and get a tax id. Wish that wasn't a requirement but I can understand the need for tax laws.

Yes it is tempting.. even if just to play with DSP.

Have you Considered a Limited Liability Company (LLC) ?

I was going to investigate it after I did my taxes this year. Thanks for the tip.

[eXode]

That's pure masochism, man! I think I tried to get my Piston Honda to track over an octave using the Sequencer in Thor, for about 5 minutes. I gave up and and just used my Doepfer quantizer. :lol:

The best thing to do is to setup a Thor patch that acts like the MIDI to CV/GATE converter on it's own and then control that Thor synth with either another Thor, or the RPG-8, or Matrix pattern sequencer.

I've uploaded a zip to RapidShare with some Thor patches that I've used to setup for controlling oscillators melodically. Chances are that it won't work out of the box on your system but maybe it's a start for you to understand what you need to tweak to get fully melodic playing.

RapidShare - Thor Patches for ES3.zip

I hope they are of help! :)

[justin3am]

Hey, thanks man! I appreciate the amount of work this probably took, so I'll give it a try tonight.

[eXode]

Hey, thanks man! I appreciate the amount of work this probably took, so I'll give it a try tonight.

You are welcome. Oh and for the connections on the Thor:

Audio Output 1 = Note CV
Audio Output 2 = Gate CV
Audio Output 3 = Trigger CV

Audio Output 3 isn't needed, I used it to act as a trigger because I couldn't get my doepfer envelopes to retrigger properly otherwise. If you don't care about retriggering you don't need to connect Audio Output 3. :)

[xh3rv]

So this is theoretical then?
Or are you just stuck in your best Project Manager tone?

Yeah, it's fair to say it is theoretical. I've tried to make it clear I'm just BS'ing ultimately But I'll stand by my points as much as anyone can not having lived in a Reason-extended environment.

The one point that I'm completely confident in - your timeframes are way off for amount of work it takes to get things going in Reason. You say six years, which is really sort of off the charts. Urs says a little over six days, and I believe that's not spun. If the concept takes off it may be improved for years to come, which is a little different. If you agree with my point about a more integrated object model in Reason, apply that to developer effort - that's what it's all about, not more lines of code but better lines of code which then transitions into orders of magnitude less code. Everything Propellerheads is tackling with RE is a known quantity - Reason's engine and interface, DSP plugging, and SDK design. Not saying it couldn't be screwed up but the idea is really realistically achievable.

I realize I'm coming at this with no baggage from being a Propellerhead customer so on that point, I get what you're saying.

I'm a bit of a u-he sockpuppet as well - tossed out a Uhbik preset collection THRAKosaurus less than a month ago which I'm tempted to rename THRAK-extensions - I did have the idea of stacking, at least somewhat modularly as far as VSTs allow, in mind with that. So this seems like about the perfect way to realize some ideas I've personally invested an amount of effort into. (BTW Props & u-he, if you're looking for presets or combinator-stuff ... I will shamelessly promote that project or stacked variations on what's in there as one of the best of it's kind. Also the one of the only .)

[Urs]

(I just hope they let us put patch points on the front plate and tell us where the cords originate... think ACE interpatchable with other REs... normal operation if patched within itself, streaming audio and control signals in/out if patched from elsewhere)

[bmrzycki]

(I just hope they let us put patch points on the front plate and tell us where the cords originate... think ACE interpatchable with other REs... normal operation if patched within itself, streaming audio and control signals in/out if patched from elsewhere)

I have no idea how you're going to mix audio and control rate cables in ReAce unless Re changes patching rules that have been there since Reason 1. Maybe you can put a CV and an audio plug next to each other for each patch point? And we'll have to use spiders to do many to one or one to many. And boy are you gonna have your work cut out for you with the mod devices.

And for what it's worth, I don't mind having to flip it around to change the routings of ACE. It would make the default front much smaller and simpler I think.

[eXode]

@ Urs and bmrzycki:

There's two major issues with using Reason's "conventional" CV for something like ACE (at the current state) which makes it not suitable for ACE style patching. First of all, CV signals in Reason are always monophonic, and secondly, they only run at a 16th (or something like that) of the actual audio rate.

I and some users with me have pestered props for quite some time to redeem this but perhaps if several RE developers push for it as well it might sway them more. We've asked them for to get both support for polyphonic CV and the option to run CV at full audio rate.

Anyway Urs, regarding the ACE problem. I don't know if that's a viable option for you but if the whole "front cables" layout of ACE is not possible to do in Reason a second option would be a Mod Bus Routing System a'la Thor. In Thor with the MBRS you CAN actually run LFO's etc internally in audio rate. I know it's not the same thing and perhaps it's too much trouble but an option at least.

[Crackbaby]

I wouldn't mind flippin' either Oh man, this is like a wet dream coming true

[justin3am]

There's two major issues with using Reason's "conventional" CV for something like ACE (at the current state) which makes it not suitable for ACE style patching. First of all, CV signals in Reason are always monophonic, and secondly, they only run at a 16th (or something like that) of the actual audio rate.

I wonder if it would be against the RE guidelines to use audio inputs and outputs as serial data pipes to get around these limitations. I mean it's all data within the Reason Rack, right. Who's to say you can't send data as audio from one device to another.
Well, I guess Propellerhead could say you can't do that.

@exode: check your PMs

[eXode]

I wonder if it would be against the RE guidelines to use audio inputs and outputs as serial data pipes to get around these limitations. I mean it's all data within the Reason Rack, right. Who's to say you can't send data as audio from one device to another. :hihi:
Well, I guess Propellerhead could say you can't do that. :lol:

@exode: check your PMs

I'm only speculating here but I doubt that it would be against any guidelines. Props did it themselves when I think about it. They added audio inputs for AM and FM in the pulveriser beside the regular CV's to be able to do full audio rate modulation from an external source.

Still, would be nice if they added support for running CV's att full audio rate. :)

[xh3rv]

Still, would be nice if they added support for running CV's att full audio rate.

RE-cursion (like that? ) would be a non-trivial issue, not sure a completely engineered solution for it is practical but designing around it is already done a bit in ACE (example - the ports on the bottom of ACE aside from white noise are all control-rate, pretty cleanly understood as such as well) [e: rebutted below ]

[e] Also just occurs to me, CV->Audio is sort of an interesting way to look at any plug-in now, but but Audio->CV modules with interesting functions could be pretty nuts too. A simple example would be an envelope follower, but maybe it would extend out - a quickly accessible sampler for example with some off-line sort of capability for pushing out analytically derived CVs on dynamics or spectrum or whatever for example.

[Urs]

ACE is mostly unaware of any control rate like in CV-sockets. It has to be all audio rate

From what I understood they wouldn't mind us abusing audio cords for control signals. I'm just not sure if we can place them on the front side.

And of course we need to know if it's an "in-ACE-cable" or a "external cable". That's because there's a difference in hvaing an audio stream or an in-voice connection between two modules. Audio streams are mono, in voice streams are polyphonic and handled internally.