Hey all,
I am trying to use GEM (on OSX), in particular pix_kaleidoscope, to manipulate an image in real time based on a wav file currently playing from an array. It is meant to be a very basic visualizer which needs to be "wound up", i.e. periodically the music runs out like a wind up music box and the user must rotate the mouse around the screen and click the screen for the visualizer to continue!
OK now here is the problem when i call pix_kaleidoscope and it starts manipulating the image it starts using up 50% of my processor and the music gets all jumpy and the image changes are not smooth at all. Is there a way around this or a simpler, less processor hungry, method of manipulating the image for the same visual effect?
I have uploaded my patch to the following address for your perusal:
http://www.thehappydude.net/audio5.pd
If anyone could lend me their experience here it would be much appreciated.
Thanks
R.
By the way I only started using PD in November so my knowledge is limited!
There was a glsl kaleidoscope sent out the list a few months ago, it should work a little faster. I usually use midi instead of audio to controle gem. You also might try resizing your image to 512x512 for better processor performance
On Jan 12, 2008 8:04 PM, Ross Mulcahy ross.mulcahy@gmail.com wrote:
Hey all,
I am trying to use GEM (on OSX), in particular pix_kaleidoscope, to manipulate an image in real time based on a wav file currently playing from an array. It is meant to be a very basic visualizer which needs to be "wound up", i.e. periodically the music runs out like a wind up music box and the user must rotate the mouse around the screen and click the screen for the visualizer to continue!
OK now here is the problem when i call pix_kaleidoscope and it starts manipulating the image it starts using up 50% of my processor and the music gets all jumpy and the image changes are not smooth at all. Is there a way around this or a simpler, less processor hungry, method of manipulating the image for the same visual effect?
I have uploaded my patch to the following address for your perusal:
http://www.thehappydude.net/audio5.pd
If anyone could lend me their experience here it would be much appreciated.
Thanks
R.
By the way I only started using PD in November so my knowledge is limited!
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hi Ross,
Running GEM and PD for audio in the same instance isn't such a good idea. Better to keep the threads separate. Normally, if I want to use both together I run two different instances of PD, and communicate between them with OSC. One for the GEM and one for the audio. On OSX, you may have to start each PD instance from the command line:
/Applications/Pd-extended.app/Contents/Resources/bin/pd --noaudio --open
<GEM patch>
/Applications/Pd-extended.app/Contents/Resources/bin/pd --nogui --open
<audio patch>
should do the trick for with PD-extended. You could use the --nogui if all the controls are in the GEM patch. You could even make a shell script which opens both instances at once, with their respective patches.
best, d.
Ross Mulcahy wrote:
Hey all,
I am trying to use GEM (on OSX), in particular pix_kaleidoscope, to manipulate an image in real time based on a wav file currently playing from an array. It is meant to be a very basic visualizer which needs to be "wound up", i.e. periodically the music runs out like a wind up music box and the user must rotate the mouse around the screen and click the screen for the visualizer to continue!
OK now here is the problem when i call pix_kaleidoscope and it starts manipulating the image it starts using up 50% of my processor and the music gets all jumpy and the image changes are not smooth at all. Is there a way around this or a simpler, less processor hungry, method of manipulating the image for the same visual effect?
-
beau -
Derek Holzer -
Ross Mulcahy