New to Usine, am I doing something wrong?

[Andromida]

Hi everyone...I am a big fan of modular hosts, started with eXT and since my upgrade to an AMD dual core, I was advised to try Usine.
So, I downloaded the latest demo version, set up the asio, midi-in/out, ...etc. I am running an M-Audio audiophile 2496 with native ASIO driver installed with 512 samples buffer that yield a 5ms in/out latency. My PC is an AMD dual core 3800+ with 1GB Ram, runnning XP PRO SP2. My MIDI controller is a Yamaha SY77 synth, that I have been using for almost a year now with eXT 1.4 with no problems.
I was able to run a few VSTs with no problems whatsoever, until:

(1) I got MIDI stuck notes + huge MIDI latency:
I experienced this with a few VSTs, and I can repeat it every time. To be specific I got it with Zebra CM, and Angular Momentum AM MAX-EQ
The problem occurs when I am trying to tweak the VST by turning a knob or a slider with the mouse while playing a fast repeated one note on the controller. Suddenly the sound goes off and Usine becomes too slow, and if you hit any keys, you get to hear them like 20-30 seconds later. So, what is wrong here? Any ideas?

(2) I tried to use eXT 1.4 from within Usine by using the VST demo version, it worked for a few VSTs but with noticable latency. Some VSTs refuse to launch giving me an exception error. Oh, and everytime I do something within Usine, eventhough eXT is not loaded, the eXT pop-up demo reminder appears and it's quite annoying.

Any help or feedback would be great. I like Usin and I think it's a monster, but having these problems renders it useless for me.
Thanks.

[martignasse]

hi andromida,

Well, seem's like you'r soundcard drivers doesn't like usine...
I'm not experienced with the audiophile 2496, but can give you some things to try.

Before all, did you check the dual core optimization in the usine setup, has you have a dual core processor.

Did you try with more latency, to see if the problem evolve or die ?

You can try with the Asio4All driver, to see if the problem is specificly related to you'r soundcard driver.

And don't hesitate to give you'r complete config (motherboard, schipset, OS..) it can help other to remind problems already known.


And for the eXT demo popup, i'm afraid that the only way seem's to run the plain version.

Just my two cents, hope it help

[Vincent]

1)
I got MIDI stuck notes + huge MIDI latency
2)
a. I tried to use eXT 1.4 from within Usine by using the VST demo version, it worked for a few VSTs but with noticable latency.
b. Oh, and everytime I do something within Usine, eventhough eXT is not loaded, the eXT pop-up demo reminder appears and it's quite annoying.

Hello Andromida,

1)
Well, I have no time for now to check with your VST, but I can now just tell you one or two small things.
I gave up tweaking VST while playing, except if I did a patch interface: connect switches or faders to the right pin of your VST and tweak the switches or the faders. Since I have a very crappy computer, I always close VST windows (I only use their GUI when patching). I just use them as "super-modules".
Maybe could you also automate this tweaking with the sequencer curves or a sequencer module?

2)
a. I've tried eXT before to choose Usine, so not in Usine. Maybe should you attempt Martignasse's suggestions?
Why do you want to plug eXT? Is there any possibility to do the same with Usine? Or, maybe is it only a lack of tracks?
My fantasy would be to host Usine in Usine, or (I mean, and) to run two instances of Usine in standalone to be able to overlap my music pieces.

b. The pop-up. I think it would be the same in V-STack or Cubase. The hosts check all the VST stored in your VST folder when they start or rescan the folder; the more VST you store, the longer it will take. And if some VST have a pop-up to throw, they do it! I had the case with some ugly synth demo from I-don't-remember-who. I deleted it! Arghhh!

I hope we'll solve all your pb!

[Andromida]

Thank you guys for the suggestions. I'm out of town at the moment, and I'll try your suggestions when I get back.

Best.

[Dog]

Hi everyone. I'm a new user also. So far, so good. This looks like a really great bit of software. My problem. Every minute or so, I am hearing a short (approx 1kH) tone. I cannot see where this is coming from. have I missed something about this?

Also, as regards using existing audio to trigger VSTi modules and thereby create a new sound - like adding an organ sound, for example. Is there a standard way of connecting to the VSTi modules or does it vary from module to module?

Thanks in advance!
Dof

[senso]

hello dog,
Welcome on this forum.
I don't think it comes from Usine.
There is no such protection in the free version.
Take a look on other demo VST(i) you have loaded in your patches(??)

[Dog]

Thanks. Now I know that for sure it isn't usine I will check elsewhere...
Dog

[Vincent]

Hi dog.

Also, as regards using existing audio to trigger VSTi modules and thereby create a new sound - like adding an organ sound, for example.

Do you mean that you would like an organ to follow your guitar?
That is, to turn audio flow into midi flow... Well, I think that can be complex and hazardous!
Sound must be analyzed in different ways to do that.

Is there a standard way of connecting to the VSTi modules or does it vary from module to module?

I would say: both. VSTi patching is a simple and common task but, from one VSTi to another, things might be quite different. Example: the program inlet does not work exactly the same with eg. NI Absynth 4, Moog Modular V and Tascam GVI...
Maybe we could answer to more precise questions. Sure we would like to!

Rgds

[Dog]

Thanks Vincent:

I was trying to patch in a VSTi instrument that would react to the looped/played audio source to add an extra sound to the track. When I loaded in the VSTi, though, the inoput connections didn't seem obvious..

[Vincent]

When I loaded in the VSTi, though, the inoput connections didn't seem obvious..

...you mean you did not see them?
It's because your VSTi has no audio out!
Arf!
Hm, no kidding, sorry...
On some VST with a lot of In- and Outlets, when the screen resolution is not very high, you cannot see them all. It's the same with very big patches. But you can scroll them: look at the two small light gray triangles on the top of the VST parameters panel (just on the right of the patch edit window), click on them.

a VSTi instrument that would react to the looped/played audio source

React in which way, that's all the question.
If you really want that VSTi to do beautifully things, I mean play notes, you have to detect the pitch and the envelope of the audio source (supposed to be monophonic, because to detect the pitch of a chord, well...), then to send those data in a MIDI language to your VSTi. AFAIK, there are some interesting stuffs like that in the add-ons.
This is not easy patching!

[bsork]

Hi there, I'd like to add to what Vincent has already said, that you can find a couple of Pitch2Midi patches with the Analysis modules. The Pitch Tracker module still mentioned in the manual is superseded by the new patches.

I haven't tried them myself, and as Vincent has already pointed out detecting the right is no mean feat, but the patching should be relatively straight forward. Patches stored together with the modules default to be sub-patches, so pick one of them and connect the audio in to the relevant input of the sub-patch, and the midi out to the midi in of the VST iof your choice. Round of with ctrl-dragging from the audio out(s) of the VSTi to get the sound out.

[Vincent]

Hi dog.

As you can see, nothing is really impossible.
Just come back here when you'll be ready to patch your "organ follow" and we'll give you more precise advices.
I'm interested too in that kind of patch. I'd like to make it play some nice pads on vocals or eBass (audio AND midi processing!).

[waverider]

all cool I have a newbie question to post too....