OSC remote for VST don't work for Hiden VST ?!

[cybercharles]

Hello

is it normal that the OSC remote is not working when the VST is hiden even if the patch is active ?

I'm using a lemur for the remote. I use the "add-ons" patch for programming a bidirectionnal OSC remote: PC to lemure and lemure to PC.

Thanks

Charles

[senso]

absolutely not!
which vst is it?

[cybercharles]

Is MODE "Mono" from cycling 74:

http://www.cycling74.com/products/mode

[senso]

the pb will be probably solved in the next beta.

[cybercharles]

I’m still working with USINE 3.68f ...

Olivier I’m a little bit angry today ! !

Up to me upgrading as quickly as you do the USINE software could be a problem to ! even if the new features are cool ! Because users spend lot of time to patch under an X version and the patch run well. After upgrading in version Y the same patch will not running as well. I did personally this experience … It seems that new beta version create other problems. In consequence you have to answer to the new bugs … and the old ones are not solved in the same time…

Still continue this marvelous software. I will support you however that may be.

Charles

[senso]

Up to me upgrading as quickly as you do the USINE software could be a problem to ! even if the new features are cool ! Because users spend lot of time to patch under an X version and the patch run well. After upgrading in version Y the same patch will not running as well. I did personally this experience … It seems that new beta version create other problems. In consequence you have to answer to the new bugs … and the old ones are not solved in the same time…

I'm like you I'm still using reaktor 4.0...

Since I'm alone it's hard to maintain several version of Usine. But don't worry the Usine 4.0 version will stay in place for a long time.

[cybercharles]

Hi olivier

this problem is still not solved in Usine 4 beta 13.

Charles

[senso]

ok!
definitively solved in the next version: V4.01

[Vincent]

I'm like you I'm still using reaktor 4.0...

No bugs in Reaktor 4.0. No bugs in Reaktor 5.0. And AFAIK Reaktor 4 ensembles work fine in Reaktor 5.
You're still using Reaktor 4 because you don't deadly need Reaktor 5!
But we need Usine, Olivier, we really deadly need it as much as you. And much, much more than Reaktor, as you can imagine.

I’m still working with USINE 3.68f ...

You beat me. I'm still on 3.66d!

upgrading as quickly as you do the USINE software could be a problem to ! even if the new features are cool !

Sooo cooool!
+1

After upgrading in version 'Y' the same patch will not run as well. I did personally this experience …

+1
+1

In consequence you have to answer to the new bugs … and the old ones are not solved in the same time…

+1
+1
+1

Still continue this marvelous software. I will support you however that may be.

+1
+1
+1
+1

And I would +++ this: why to suggest improvements, and why to spend 40 or 60 hours to track bugs in a truly great beta 4 if some killing buggy stuffs of 3.00 (and 2.00, and...) are still there? Why to update? What can we think about that?
That's not funny for us, usiners, specialy earlier ones (do you remember 0.8?! Hmmm, was that in the end of 2004?).
But when I think to Olivier's job on that soft...
Isn't that crazy?
I just get vertigo.
So...

[SylvainT]

Hello,

Interresting, interresting...
But what is the solution?
I'm a new usiner since three months, very amazed by this stuff.
Olivier make improvments all the time and alone on Usine, but he needs some betatesters. If you're Ok with that, like I am at that time, (I haven't 150 patches in my laptop for now) download each new version. If you don't want, keep you're old version in the corner but try the newest. To go fast Olivier needs some people to test the things everytime. And unfortunately, we are, less or more, all betatester.
Improvment vs bugs vs betatester vs users vs time vs.... and just Olivier. This is not Ableton or Digidesign
Ouaouh that's difficult, but so powerfull.....

Regards

Sylvain

[Vincent]

You're right!

I use 3.66 and I did some beta test on 4 (and on other realses) before it's out. I feel I have to do it, what else could I do?
I could also seriuosly update the Quick Start, for a release I don't realy know and I can't use.
That's OK, you know.
But there is something else: I am a musicien, just like you and certainly all of us here. Just that.
So I check for my time: more than 50% of it to patch and repatch... that's not music anymore.

In fact, the situation here is very unusual!
1. Olivier works quite alone to develop a genious and very powerfull (and, let's say it, a mandatory) soft
2. He uses it in its own way but creates the ability to do anything else with it
3. He realy tries to implement all what we suggest, and much more...
4. 50€, it's just a joke. We used to say "donativo" on the Camino in Spain!
5. We are fighting (and sometimes scaring, because live doesn't give a shit to bugs): is it a bug or is it stupid meeee?! That was working yesterday, why doesn't it work any more?!!!

...well, I'm not used to this. Sorry. Sometimes it makes me anger.
I don't have any solution, of course, just keep on. You say: "Improvment vs bugs vs betatester vs users vs time vs.... and just Olivier"... Well, all is in Olivier's hands.
But can we talk about it, or not?

BTW, I have hundreds and hundreds of patches on my computer; I was talking about a workspace with more than 150 patches (not including subpatches)! Quite different!

Rgds

[woodslanding]

Just want to say--there are bugs in reaktor 5!! Midi values are not range checked--they crash the program. There is some pitch bend routing bug (I forget which) that forced me to convert pb to a cc in plogue before it goes into reaktor, and then back to pb afterwards. These are just the first two off the top of my head.....

Absynth turns off 'respond to program changes' every time you start it up in a host. Kontakt puts your bank in 'omni' mode every time you add a patch to it.

And no chance of NI fixing anything (or even responding in the forums) until the next major revision, which will cost you several hundred dollars on top of your many hundreds of dollar investment

Thats software!!

Oliver is doing amazing work! --and this is a beta, after all.

I do hope by the time I get my setup put together, Oliver will have had time (and the beta test input) to get it running smoothly

cheers!
-e

[Vincent]

And no chance of NI fixing anything (or even responding in the forums) until the next major revision, which will cost you several hundred dollars on top of your many hundreds of dollar investment

That's true, woodslanding. An also certainly true with Reaktor 4 bugs, since I didn't use it for a long time. But I did not noticed the midi bugs in R5 you're talking about, whereas I manly use it for Midi manipulations and synths (neither Absynth's one, I use it all the time!). I'll check!
Anyway, you're right and that's why I said that all is in Olivier's hands.
He's doing great job and he's close to Usiners.

I do hope by the time I get my setup put together, Oliver will have had time (and the beta test input) to get it running smoothly

I do hope so too. Usine 4 is a major-major release!!!
Meanwhile, to get my setup put together, I must continue with Usine 3.66... sigh.

Rgds

[cybercharles]

The problem is solved in USINE 4.01 !!!!!

let's music !

thanks Olivier.

Charles "will support you however that may be"