MIDI input to AutoTune?!?

VST, AU, AAX, CLAP, etc. Plugin Virtual Effects Discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

Can someone help me figure out how to feed target-note info via MIDI to the DX version of AutoTune 4 on PC in Cubase SX3?

I think I understand I can only do this with the VST version, but I'll be honest, the manual and the website are pretty shady about this, and seem to suggest it's possible to do it with the DX version "in some hosts" with a "multi-client MIDI driver" -- whatever THAT is...


Of course, BASICALLY I want to complain that they are releasing a freaking THROAT modeler before they finish the VST version of AutoTune for PC... I mean, a THROAT MODELER?!? LOL... :roll: Whatever -- maybe it will make some really cool sounds, right? But for cryin' out loud, sending target notes via MIDI would just be so helpful, and they've been saying the VST version for PC is "coming this year" for about 30 years...

(note: actual time might not have been 30 years)


:D


Anyway, if you can help me, THANKS...

Post

k i dont know how to do this put though id post to keep this thread alive beacause i would luv to know

u can do this easily in akai pitchright - its vst but its not as good as autotune

also im hoping anatres throat modeler will solve all my problems and make me rich and famous -my whole life has been leading to this plugin

:party:

Post

I don't own auto-tune but i do use software vocoders (vokator)in my music and they are very simple to use i presume you just hook up Auto-tune the same way.

Add Auto tune as an insert effect to the vocal.

then create a midi track , in the midi tracks input choose the name of your midi controller and in the output choose auto tune.

now you should be able to play in realtime.

Post

CANE CREEK wrote:I don't own auto-tune but i do use software vocoders (vokator)in my music and they are very simple to use i presume you just hook up Auto-tune the same way.
Yeah, you'd THINK it wouldn't be that big of a deal to make the VST version for PC where we could do that -- :? -- but I'm not a developer so I shouldn't rush to any judgements on that...


But in fact, on the PC, with the DX version (only DX and RTAS available on PC), you can NOT do this, it seems.

Oh, well.

But hey -- so what? I can't correct pitch as easily as I'd like, but I can model the throat of a Tuvan singer with their NEW plug-in! Now THAT's progress!!

( :roll: )


ANYWAY, does anyone know what they mean by "multi-client MIDI driver"? I'm willing to try it, if someone can tell me what that means...

Post

im led to believe multi-client driver were drivers that could be used by more than one program/device at once.

Example a multi-client driver will let you play your host whilst playing the windows media player and at the same time playing an editor like cool edit.

so i presume a 'multi-client MIDI drivers' will let you use several midi devices at once

Multi program/devices running with one driver = multi-client drivers. :wink:

Post

CANE CREEK wrote:im led to believe multi-client driver were drivers that could be used by more than one program/device at once.

Example a multi-client driver will let you play your host whilst playing the windows media player and at the same time playing an editor like cool edit.

so i presume a 'multi-client MIDI drivers' will let you use several midi devices at once

Multi program/devices running with one driver = multi-client drivers. :wink:
This is my thinking, as well...

But can anyone NAME a "multi-client MIDI driver"? THIS is what I'm getting at -- 'cause it doesn't help to know what it means until I actually FIND one of those suckers. :)

I'm not gonna act "mad" at Antares over this one, though anyone in my position might feel a bit put-off that the manual and website are both very, very vague about this whole thing. If it can't do it, then SAY "don't try this with Cubase on the PC" -- or if it CAN work with some third-party "multi-client MIDI driver", then SAY that, and give me some freaking examples I can try out, geez.

Obviously they don't make it TOO explicit because it might hurt sales, I guess. Saying "these great features won't work in the PC version of one of the most popular hosts in the world" isn't good for bidness.

I just hate that my last update (to AutoTune 4) was partly predicated on using this feature, which for whatever reason I did not find out it didn't work on PC until AFTER I'd "paid me ca$h"... And now I'm in "full investigation mode" and I STILL can't freaking figure out if it definitely will or won't work, and how...

:roll: :? :x :cry: :help:

.

Post

k heres a stop gap solution in Fruity Loops 5 - but this doesnt work on mix down so youd have to record stereo mix

crate a midi out channel use this to trigger an hardware synth den go from midi through of that back in to pc and use the select port in auto tune to pick it up

u have to turn off "midi in" in fruity loops though to avoid a feedback chain which sounds good sumtimes though

anyhoo maybe ders a way to do virtual daisy chains with
different programs - i tried usin fruity as a vst inside mini host and could get minihosts midi file player to
trigger autotune but its not synced

plz someone make a wrapper for this

heres want we need
a dx to vst wrapper dat has some thingy for sendin midi to auto tune or sumthin

dis would be kule and antares would be sorry for not releasing the vst straight away and would maybe release the throat sim quicker to make up for it!!!

i think apple are behind dis one -d slimy b**tards

i have a hangover

:party: :party: :party: :party: :party:

Post

just keep dis thread alive again

Post

You simply should have some more available MIDI ports on your DAW. That is a requirement for any professional use of AutoTune.

Then you exclude one of the inputs for locking by Cubase and you can use it with AutoTune. That's all.


By the Way: The good old YAMAHA Serial Port Drivers were for instance "shareble", that means "Multi Client Drivers". So I assume there are others too, providing that today.

But normally you should have many physically inputs and outputs for MIDI on your "top modern" DAW.


Tip: Most Mainboards today have an ONBOARD MPU. You can use that additionally to your soundcard MIDI ports. Then you actually have a new MIDI in.

(But probably you merely have one master keyboard ???).


.

Post

pustekuchen wrote:You simply should have some more available MIDI ports on your DAW. That is a requirement for any professional use of AutoTune.

Then you exclude one of the inputs for locking by Cubase and you can use it with AutoTune. That's all.


By the Way: The good old YAMAHA Serial Port Drivers were for instance "shareble", that means "Multi Client Drivers". So I assume there are others too, providing that today.

But normally you should have many physically inputs and outputs for MIDI on your "top modern" DAW.


Tip: Most Mainboards today have an ONBOARD MPU. You can use that additionally to your soundcard MIDI ports. Then you actually have a new MIDI in.

(But probably you merely have one master keyboard ???).
Have you actually tried doing this? On PC, in Cubase SX? You used the phrase "exclude one of the inputs for locking by Cubase" -- I'm sorry, I don't understand that, so if you have some specific "pointers" it would be GREATLY appreciated! THANKS!! :)

Again, the issue is getting this feature to work with the DX version of AutoTune on the PC in Cubase SX3. Unless you can show me otherwise, I do not believe it has ANYTHING to do with number of physical MIDI ports at all -- it's getting the DX version of AutoTune to SEE incoming MIDI ports, right?

markroom wrote:heres want we need
a dx to vst wrapper dat has some thingy for sendin midi to auto tune or sumthin
The notion of a DX to VST wrapper with this functionality sounds like a good idea -- but what do I know?!? :wink: I did actually look for one before I posted this thread, by the way, so we are thinking the same, markroom!

Anyway, it's a feature that Mac and TDM users of AutoTune have access to -- but for SOME reason they seem to have let the PC VST version remain unavailable for a LONG time.

I just keep wondering how many more seasons I'll see that "coming this year!" sign on their website. :?

Post

TokyoTain wrote:
pustekuchen wrote:You simply should have some more available MIDI ports on your DAW. That is a requirement for any professional use of AutoTune.

Then you exclude one of the inputs for locking by Cubase and you can use it with AutoTune. That's all.


By the Way: The good old YAMAHA Serial Port Drivers were for instance "shareble", that means "Multi Client Drivers". So I assume there are others too, providing that today.

But normally you should have many physically inputs and outputs for MIDI on your "top modern" DAW.


Tip: Most Mainboards today have an ONBOARD MPU. You can use that additionally to your soundcard MIDI ports. Then you actually have a new MIDI in.

(But probably you merely have one master keyboard ???).
Have you actually tried doing this? On PC, in Cubase SX? You used the phrase "exclude one of the inputs for locking by Cubase" -- I'm sorry, I don't understand that, so if you have some specific "pointers" it would be GREATLY appreciated! THANKS!! :)

Again, the issue is getting this feature to work with the DX version of AutoTune on the PC in Cubase SX3. Unless you can show me otherwise, I do not believe it has ANYTHING to do with number of physical MIDI ports at all -- it's getting the DX version of AutoTune to SEE incoming MIDI ports, right?

:?
What do you actually think, I do here all the time ? :x
I used it quite often with Cubase 5.1 (so it will be possible with SX too...)

Ones you have excluded the inport from locking by Cubase, it is assigneble to Autotune and IT WORKS!!!

(On Cubase 5.1 there is an MME Enabler, where you can exclude the MIDI ports from locking. I assume, there is something very similar on SX.)

As long the ports are locked by Cubase, you wouldn't be able to access those with AutoTune (except you have Multi Client Drivers installed).


Yes. Such as simple is that. :)

.

Post

pustekuchen wrote:What do you actually think, I do here all the time ? :x
Geez.

Anyway, thanks for your comments. I'll try it.

Post

I am VERY mad at Antares: I sent them an email 10 months ago asking them how to do MIDI-input in Sonar, and they told me that the VST version would fix all my problems "soon".

I have gotten it working by installing a MIDI loopback device, but that's a really bad hack that doesn't really work well for me (it introduces a bit of a perf-hit).


Anyway, Antares should stop promising this if it keeps moving. I don't care about the throat modeler.





-Ido

Post

I was having a somewhat similar problem with another plugin that would only have certain MIDI functions in Cubase.

http://tonewise.com/DirectiXer/

try that VST adapter it allows midi in and out for the plugins you make with it in most hosts (i use it for sonar)

I'm not saying you SHOULD do this but you can easily find a pirated version torrentspy.com usually OR by simply going to a crack site (freeserials.com) and cracking the demo. I don't usually support Piracy BUT if you have no idea if you can use it or not $100 is a lot of money to just waste.

Post

em it already is dx

i think ders away of doing it in midiox but will prob take me a few days to try it out


(freeserials.com)?

more like freespyware.com :-o :-o :-o

Post Reply

Return to “Effects”