Insert Piz Here

insertpizhere · Post by **insertpizhere** » Sat Jan 08, 2011 11:02 pm

does two things:
- sends a continuous CC signal following the audio envelope using RMS averaging.
- sends a fixed CC when the audio level (peak value) passes a threshold.

http://thepiz.org/pizmidi/AudioToCC.zip

damstraversaz · Post by **damstraversaz** » Sun Jan 09, 2011 3:56 pm

great !! i will try it as soon as possible. That's probably the most advanced audio to midi cc plug !

thanks a lot

sinkmusic · Post by **sinkmusic** » Sun Jan 09, 2011 6:24 pm

Thanks a lot, Piz !

Lying Low · Post by **Lying Low** » Tue Jan 11, 2011 5:50 am

it works really nice! I like it

the possibilities with this one are endless

vata44 · Post by **vata44** » Tue Jan 11, 2011 6:21 am

Can you explain just a few basic/common uses for a tool like this? I am out of the loop in this area.

Thanks

Lying Low · Post by **Lying Low** » Tue Jan 11, 2011 7:08 am

vaisnava wrote:Can you explain just a few basic/common uses for a tool like this? I am out of the loop in this area. Thanks

Its fun for experimenting on unique ideas and obtaining surprising or even thrilling results.

A common use may be to give it some vocals for an imput, use the volume level of the vocals to modulate the wet level of a effect, so the louder the vocal is the more compression or reverb or EQ is applied.

wakax · Post by **wakax** » Tue Jan 11, 2011 7:35 am

thanks !:)
great plug.

fliffo · Post by **fliffo** » Tue Jan 11, 2011 11:03 am

I've been testing this plugin for a while under Ableton Live 8.2.1 (latest) and Windows 7.
The plugin is rock-stable, no crashes or glitches at all here, but I experienced something strange i want to share:
I tested AudiotoCC feeding it with really simple material: a 4/4 drumloop @ 120 bpm with just 4 *identical* kickdrums on the quarter-beats, and I recorded 8 bars of it with both audio and the automation curve obtained from the movements of a fader being automated by the plugin output.
What I noticed:
1) While recording, the automation curve was ever changing... I mean, the plugin listens always to the same kick, so it should output always the same sequence of CC values... or at least with minor variations...instead I noticed great variations while the audio material was just the same.
2) I also experienced a variable and random lag in the plugin response: sometimes the plugin reacts fast to the kick, outputting a peak CC value just a few ms after the kick attack... sometimes it reacts slowly (50 - 60 ms) and in an unpredictable manner.

I don't know if this is an host issue or a plugin issue.

insertpizhere · Post by **insertpizhere** » Tue Jan 11, 2011 9:25 pm

this is probably due at least in part to a limitation in the resolution of automation recording in Live... also, the direct host output of AudioToCC is close to sample-accurate, but sending it to a loopback port and then receiving it in Live again introduces some latency, and depends on how Live handles MIDI input.

i'll see if i can adjust anything to make it more consistent, but one thing you might be able to do to improve it is to use a smaller buffer size.

for the fastest response, also try setting Rate to 100, Attack and Inertia to 0 and Release to 30 or higher...

-PIKU- · Post by **-PIKU-** » Wed Jan 12, 2011 2:21 pm

could you make the gate mode velocity sensitive (sending midi notes)?

i'd like to have an affordable trigger to midi plugin..
i tried all the trigger-to-midi plugins available, but i found that they always introduce a small latency time.
i just compared the behaviour of an akai lpd8 usb midi controller, with the trigger-to-midi plugins (using a piezo microphone or an original roland drumpad connectrd with the audio-in of my audio interface) in energy xt1 and xt2..
the best plugin is KTdrumtrigger, but again, it's performance is worse than akai midi controller.. i don't understand why.

now i'll make the same comparison using this plugin and a cc2note converter.. i'll let you know the results

insertpizhere · Post by **insertpizhere** » Wed Jan 12, 2011 2:52 pm

small update, continuous CCs on right channel were being sent twice to the direct output.

http://thepiz.org/pizmidi/AudioToCC.zip

i can add note output... don't know how well i can reliably determine the velocity without latency, but i'll try it.

-PIKU- · Post by **-PIKU-** » Wed Jan 12, 2011 3:36 pm

insertpizhere wrote:small update, continuous CCs on right channel were being sent twice to the direct output.

http://thepiz.org/pizmidi/AudioToCC.zip

i can add note output... don't know how well i can reliably determine the velocity without latency, but i'll try it.

mmh.. you could add velocity as an option..

sinkmusic · Post by **sinkmusic** » Wed Jan 12, 2011 3:41 pm

My goal with Audio To CC is to use it as a synchroization tool, in order to send tap tempo message to my host (Reaper or Live) from an audio trigger to the host clock.
I managed to setup the proper routing, but in practice,the issue is that it sends tap tempo messages all the time, and so the tempo is changing all the time.
I was hoping to find proper settings so the tempo would have been "adjusted" only if needed, without luck.
Do you guys think of any workaround, or is it a "comdamned to fail" idea ?
Thank you !

insertpizhere · Post by **insertpizhere** » Wed Jan 12, 2011 4:31 pm

maybe you could automate the "MIDI to host" switch and turn it on when you want to tap tempo?

sinkmusic · Post by **sinkmusic** » Wed Jan 12, 2011 4:42 pm

Yes, but my dream would be to be able to play together in realtime with midi and pre-midi hardware gear, with the pre-midi drum machine sending an audio trigger to the host, which will send sequences to hardware synths, so i'd need an accurate synchronization for all this together...
I didn't think that Reaper tap tempo would be so sensitive