Yeah, this is probably the problem. For some reason GUI objects seem to eat up a large amount of CPU usage. Once you've asserted just what input you're getting (Wiimote tends to come between 0 and 1) remove any number boxes, sliders, etc which are displaying your wiimote input. If you need this then you could display the data through GEM, which for some reason uses less processing power Andrew
Date: Fri, 28 May 2010 12:59:17 -0400 From: martin.peach@sympatico.ca To: scossar@telus.net CC: pd-list@iem.at Subject: Re: [PD] wii controller
Simon Cossar wrote:
Hello list - I'm trying to control pd (0.41.4) with a wiimote and nunchuk. I'm routing the wiimote through Osculator, then using [import mrpeach] [udpreceive 9000] [unpackOSC] and a series of routeOSC objects. With Osculator running, the graphics in the main pd window slow right down - it becomes difficult to create objects, make connections etc. There is a fairly long lag in the signal from the wiimote. Is there anything obvious that I'm doing wrong?
Probably the data is coming in too fast for Pd's GUI to keep up. I would find out how many messages are arriving per second and see if it needs to be that fast. Usually making the patch window as small as possible will reduce the amount of updating needed, also reducing the number and/or size of graphic elements that respond to incoming messages. Using [print] to display reams of incoming data will usually lock up the GUI, although you will eventually (many minutes later) regain control if you stop the source.
Martin
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
http://clk.atdmt.com/UKM/go/197222280/direct/01/ We want to hear all your funny, exciting and crazy Hotmail stories. Tell us now