Juce 3.0 - no sidechain, no proper multiout configuration support?


#1

As far as I see Juce 3 upgrade is not free, and in that case I probably can ask for more attention to that functionality?

Can we please get any real estimates?


#2

Sorry, I don't do estimates! But I do have some side-chain code here (donated by andy simper) which I've begun to integrate.

Unfortunately at the moment because of tight tracktion deadlines, I have to give a higher priority to hosting than plugins, but I'm on the case with this whenever I get chance!


#3

It’s a bit unrealistix to expect a whole different architecture of plugins to magically just work over night, is it?
Give it some time, I’m sure jules is doing everything he can to make this stuff work to satisfaction, but it’s a huge task and not an easy one at that.


#4

lucem

There is already completely working solution proposed - http://www.juce.com/forum/topic/now-available-vst3-wrapper-sidechains-and-aux/out-rtas-aax-au

At the moment I'm forced to support custom code changes to plugin wrappers (because with JUCE,  it is impossible to create virtual instrument with fixed multiout configuration, lie 8 stereo + 8 mono outs for rtas\au\aax plugins)

it is lasting a few years as far as I remember.

It's very uncomfortable to merge in custom changes every time after JUCE version update. And taking in account that I have a commercial license and I only use plugin wrappers and some very basic UI functionality in JUCE, I think it is not a crime to ask for some essential futures.

"It's a bit unrealistix to expect a whole different architecture of plugins to magically just work over night, is it? " - adding sidechain \ multiout support is not related to " whole different architecture" in any way. And the code is floating here for about two (or three?) years. 

jules does the code from Andrew have support for multiout configuration for virtual instruments?

 


#5

I do see your point, really. However, the code you cited is also very limited in its capability to fully support VST3; and, as far as I remember, jules integration of VST3 started off exactly from the achievements of this piece of code (which by the way, is not 2-3 years old, but more in the cope of half a year).
Regarding your trouble of merging into every new release; a sensible business decision would be to wait until the new feature is ripe for use, instead of relying on it. jules made it pretty clear that VST3 support in the codebase is incomplete and at the moment still a work in progress. It’s called development, cause these things stretch out over time and don’t magically appear in one huge blob. A lot of people anxiously wait for this to happen, and to properly work and support all of the VST3 features; however, the current state of things is a small first step into the direction of fulfilling that goal, but it just doesn’t go all the way - YET. But maybe a clear roadmap, not in terms of time, but order, of things that are to be expected in the near future from jules might help ease a lot of peoples mind on the matter? Something like a public .plan file to access and see where things actually are at, and what it is that is being worked upon right now. That’d be nice. Don’t you agree?


#6

It looks like you are not reading my message.

I'm NOT talking about VST3

I'm asking for these futures for AU\RTAS (and now AAX) for about 2 years.


#7

I just checked my private messages, and found that sidechain \ multiout code was already available in 2010.

 


#8

And, if I may add, your initial post does not read as a request for essential features - it more reads like a complaint that this first release of VST3 integration doesn’t do justice to your requirements. As I said, I can relate to it, but the truth of the matter is, the more people complain about “feature X missing”, the more potential development and testing time is bound and unavailable for productive work, which in fact slows down the whole process even more. Do you want to be a well-behaved customer, or someone who just complains? Why don’t you at least propose on how to integrate your essentials, and where, to give it a productive start and help jules in actually getting things done faster?


#9

lucem

Please, carefully read my request.

There is no any questions about VST3


#10

Okay, point taken. However, you did not specify any target on that, so the assumption was natural that it was VST3. Sorry for that. However, as I see it it’s interrelated; and I think I remember reading an answer to that problem that went into technical difficulties making multiout reliable across all supported standards, but I might be wrong about that.


#11

No need to yell, see post above.


#12

Sorry, I don't see any point in that discussion.

I'm asking for same two features several times per year for about 3 and half YEARS.

That's all.

PS I've paid for JUCE and I'll gladly pay for an upgrade, so It seems that I'm not a bad customer.


#13

Ok, calm down everyone!

But maybe a clear roadmap, not in terms of time, but order, of things that are to be expected in the near future from jules might help ease a lot of peoples mind on the matter? Something like a public .plan file to access and see where things actually are at, and what it is that is being worked upon right now. That'd be nice. Don't you agree?

All I can really tell you is that my current schedule is:

- frantically work on getting Tracktion 5 ready for release in January

- then relax a bit and spend some time on the plugin-side work to keep you lot happy. And maybe grab a few minutes here and there to do this before january too, where possible.

 


#14

Jules, if possible, please make multiouts first. As far as I understand that will not take a lot of changes to wrapper.

Thanks!

 


#15

+1 for multi-outs!

JUCE is amazing and working very well for me but the multi-out config for AU is a stumbling block at the moment. Would love to have an 'official' update from Jules rather than mess with it myself.

Also, thanks for all your hard work, Jules! It's MUCH appreciated and NOT taken for granted even on a commercial license.

 


#16

Thanks! I do have some side-channel code that has been contributed, but merging it will be a complicated job and I've not had chance yet.


#17

Any news?

 


#18

Sorry, I've been too busy to do it yet myself.. It'll be top of the list of tasks we give to our new juce developer when we finally find the person for that role!


#19

any update?


#20

Nothing to tell you - we'll make it known when we do it.