Mistake... Link between audio and video parameters

4 views
Skip to first unread message

sylvaink...@gmail.com

unread,
Mar 28, 2019, 10:21:40 AM3/28/19
to PraxisLIVE software discussion group
Hello,

I want to send the value from [audio]:input -> level to [video]:any parameter (like x-rotate e.g.)
but the value received from a send box is still 0,0.

Same problem with frequency received from fft audio analysis object.

How can I do please ?

Thanks,
@skunt

Neil C Smith

unread,
Mar 28, 2019, 11:37:31 AM3/28/19
to Praxis LIVE software discussion group
Hi

Is the out connected to the audio output, and no gain set to 0 in between? 

Best wishes, 

Neil

sylvaink...@gmail.com

unread,
Mar 28, 2019, 4:11:30 PM3/28/19
to PraxisLIVE software discussion group
Thank you for your reply.

Yes, fft out is connected to audio ouput.
I have this message in the console :

WARNING : /audio/send-1
org.praxislive.core.ValueFormatException@360a29f4

The send box is connected to a  /video/player.zoom

Where I'm wrong ?

sylvaink...@gmail.com

unread,
Mar 28, 2019, 4:21:42 PM3/28/19
to PraxisLIVE software discussion group
For information, at the start of the project (when I build it), I have this message :

WARNING : /audio/fft
[34:17] setup() in org.praxislive.audio.code.AudioCodeDelegate has been deprecated (compiler.warn.has.been.deprecated)
WARNING : /audio/fft
[71:32] redundant cast to int (compiler.warn.redundant.cast)

Neil C Smith

unread,
Mar 28, 2019, 5:16:09 PM3/28/19
to Praxis LIVE software discussion group


On Thu, 28 Mar 2019, 20:11 , <sylvaink...@gmail.com> wrote:
Thank you for your reply.

Yes, fft out is connected to audio ouput.
I have this message in the console :

WARNING : /audio/send-1
org.praxislive.core.ValueFormatException@360a29f4

The send box is connected to a  /video/player.zoom

Where I'm wrong ?

If this is the fft component from the examples make sure that the receiving end is a float[] property. What is zoom? Maybe take the receiving component from one of the examples as a template. 

The other warning messages are just because of changes between v3 and v4.

Best wishes, 

Neil


Reply all
Reply to author
Forward
0 new messages