u-he

justin3am · Post by **justin3am** » Wed Mar 09, 2011 7:55 pm

Why not use the AU in Live? That's what i use most of the time.

justin3am · Post by **justin3am** » Wed Mar 09, 2011 8:04 pm

I meant to post this last night but I fell asleep.

Using feedback with the rectifiers can cause Bazille to freak out occasionally. I made a patch last night that will cause the whole oscilloscope to turn green and Bazille will not output sound until I eliminate the feedback routing and trigger another note.

I'll post the patch and a screen shot when I get home from work.

Echoes in the Attic · Post by **Echoes in the Attic** » Wed Mar 09, 2011 8:35 pm

justin3am wrote:Why not use the AU in Live? That's what i use most of the time.

I only enable my VST folder. I would be scanning my whole AU folder just for one plug-in if I did so - Bazille. VST have so many advantages over AU from a user point of view. Novation automap is much better and doesn't screw up the VSTs if you ever decide to remove it for example. I also like the preset system better. Many plug-ins I find the VST version works better, not to mention other things like midi out, so I stick with only VSTs in Live.

I was hoping the cut off gui would be something easy to fix, since it's happened to most of the u-he plug-ins so far in beta stages.

justin3am · Post by **justin3am** » Wed Mar 09, 2011 8:55 pm

Echoes in the Attic wrote:
justin3am wrote:Why not use the AU in Live? That's what i use most of the time.
I only enable my VST folder. I would be scanning my whole AU folder just for one plug-in if I did so - Bazille. VST have so many advantages over AU from a user point of view. Novation automap is much better and doesn't screw up the VSTs if you ever decide to remove it for example. I also like the preset system better. Many plug-ins I find the VST version works better, not to mention other things like midi out, so I stick with only VSTs in Live.

I was hoping the cut off gui would be something easy to fix, since it's happened to most of the u-he plug-ins so far in beta stages.

That's fair. I'm sure that once Bazille is actually in beta phase, issues like this will get addressed.

pdxindy · Post by **pdxindy** » Thu Mar 10, 2011 6:17 pm

Echoes in the Attic wrote:
justin3am wrote:Why not use the AU in Live? That's what i use most of the time.
I only enable my VST folder. I would be scanning my whole AU folder just for one plug-in if I did so - Bazille. VST have so many advantages over AU from a user point of view. Novation automap is much better and doesn't screw up the VSTs if you ever decide to remove it for example. I also like the preset system better. Many plug-ins I find the VST version works better, not to mention other things like midi out, so I stick with only VSTs in Live.

I was hoping the cut off gui would be something easy to fix, since it's happened to most of the u-he plug-ins so far in beta stages.

Huh... I use only AU's...

Echoes in the Attic · Post by **Echoes in the Attic** » Thu Mar 10, 2011 8:20 pm

pdxindy wrote:
Huh... I use only AU's...

Yeah I used to. Until I realized all the advantages of vsts. And that's not a developer perspective about the specs. I know urs says there are advantages to au's. But for general use, I could never go back in live. I hate that logic makes me use au.

ruud07 · Post by **ruud07** » Sun Mar 27, 2011 1:32 am

BuddhaMaster wrote:I have one request/idea: When we create a cable, make all possible inputs highlight themself in different colors- each color represents a output function OOO. (i.e. signal modulation, math-functions, addition/subtraction. Those are just some ideas, I'm sure someone else can name them better)
This would increase work flow oh, so much better! It would help unexperienced users to be 400% as successful!

Please, please, please make this!

+1

And is there an option to make the cables shine through, like in Reason? That would make the interface much more uncluttered while lots of cables are used.

In other words: could you make the cables and inputs react just like in Reason

R.A.W. · Post by **R.A.W.** » Sun Mar 27, 2011 2:03 am

ruud07 wrote:And is there an option to make the cables shine through, like in Reason? That would make the interface much more uncluttered while lots of cables are used.

In other words: could you make the cables and inputs react just like in Reason

just right-click on an input, where you got a cable.. in the menu scroll all the way down and you got options for the cables.

BuddhaMaster · Post by **BuddhaMaster** » Sun Mar 27, 2011 3:31 am

@ Urs
Have you noticed my post (page 49, with 2 agreements)
To add the feature to highlight each possible input function with a different color, when creating a new patch-cord?
(i.e. signal modulation, math-functions, addition/subtraction)

This would allow fluid work flow for beginners

gorecki · Post by **gorecki** » Sun Mar 27, 2011 3:42 am

Echoes in the Attic wrote:I was hoping the cut off gui would be something easy to fix, since it's happened to most of the u-he plug-ins so far in beta stages.

Just curious, have you tried right-clicking on the little u-he logo at the top to re-size the GUI? I get the same issue in Cubase 6 on Mac but re-sizing the GUI seems to the do the trick, albeit temporarily until the plug is closed/opened again.

ruud07 · Post by **ruud07** » Sun Mar 27, 2011 2:33 pm

R.A.W. wrote:
ruud07 wrote:And is there an option to make the cables shine through, like in Reason? That would make the interface much more uncluttered while lots of cables are used.

In other words: could you make the cables and inputs react just like in Reason
just right-click on an input, where you got a cable.. in the menu scroll all the way down and you got options for the cables.

Thanks for the information!

Howard · Post by **Howard** » Sun Mar 27, 2011 3:31 pm

BuddhaMaster wrote:I have one request/idea: When we create a cable, make all possible inputs highlight themself in different colors- each color represents a output function OOO. (i.e. signal modulation, math-functions, addition/subtraction. Those are just some ideas, I'm sure someone else can name them better). This would increase work flow oh, so much better! It would help unexperienced users to be 400% as successful!Please, please, please make this!

Sorry, I don't understand. ALL inputs are possible candidates for something useful. Could you explain the idea more precisely?

R.A.W. · Post by **R.A.W.** » Sun Mar 27, 2011 3:46 pm

Howard wrote:
BuddhaMaster wrote:I have one request/idea: When we create a cable, make all possible inputs highlight themself in different colors- each color represents a output function OOO. (i.e. signal modulation, math-functions, addition/subtraction. Those are just some ideas, I'm sure someone else can name them better). This would increase work flow oh, so much better! It would help unexperienced users to be 400% as successful!Please, please, please make this!
Sorry, I don't understand. ALL inputs are possible candidates for something useful. Could you explain the idea more precisely?

i think what he means is that when you drag a cable from an output that possible inputs are highlighted (and in different colors for different functions).. i'm not exactly sure if i'm with this idea.. part of the fun is trial and error until you get something cool.

well, highlighting the inputs could be helpfull, but i'm not sure about the color-coding. btw this feature is also available in the semi-modular ASM/ABL Pro by audiorealism.se , so it could be a helpful addition.

Howard · Post by **Howard** » Sun Mar 27, 2011 9:02 pm

R.A.W. wrote:
Howard wrote:Sorry, I don't understand. ALL inputs are possible candidates for something useful. Could you explain the idea more precisely?
i think what he means is that when you drag a cable from an output that possible inputs are highlighted (and in different colors for different functions).

I can't imagine how input "functions" could be categorized in a way that would be useful (the essence of modularity is that anything can be connected to anything). But maybe I'm still missing the point: any concrete suggetions for the colour-coding?

Urs · Post by **Urs** » Mon Mar 28, 2011 1:15 pm

BuddhaMaster wrote:@ Urs
Have you noticed my post (page 49, with 2 agreements)
To add the feature to highlight each possible input function with a different color, when creating a new patch-cord?
(i.e. signal modulation, math-functions, addition/subtraction)

This would allow fluid work flow for beginners

Yep, thought of it... but havn't had time to implement/try it yet

u-he

KVR Audio

Berlin Modular (ancient thread)