{"author_name":"barblewarble","cat":"October Challenge 2011","comments":[],"epoch":1318412160,"likes":0,"metadata":{"p_key":"63410","p_author":"barblewarble","p_authorkey":"509633","p_urlkey":"99188","p_title":"Sound Problems fixed!","p_cat":"October Challenge 2011","p_event":"LD21","p_time":"1318412160","p_likes":"0","p_comments":"0","p_status":"UPD5","us_key":"509633","us_name":"barblewarble","us_username":"barblewarble","event_start":"1313712000","event_key":"7","event_name":"LD21"},"text":"<p>So it turns out ffts on the fly is no problem, a quick check with timeit suggests I should be able to do around 1500 a second of the size I&#8217;m trying to do and I only need to do two per frame ie about 120 if we&#8217;re locked to vsync. The problem was that pyglet seems to take sound data twice as often as it &#8220;schedules&#8221; things if you set them up using pyglet.clock.schedule so I was giving two different data chunks for the same start time.<\/p>","time":"October 12th, 2011 4:36 am","title":"Sound Problems fixed!"}