Pd-list June 2010

pd-list@lists.iem.at

144 participants
304 discussions

[PD-announce] GridFlow 9.9
by Mathieu Bouchard 16 Aug '10

16 Aug '10

GridFlow 9.9 available now !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | `---> at http://gridflow.ca/ ChangeLog version 9.9 (2010.05.05): * added class [gridflow] for reporting version number of gridflow * [print]: pointer: write "0x" and not "0x0x" * added examples supercycloid.pd, simple_mask.pd, tictactoe.pd * renamed example blob.pd to shadebob.pd * reviewed and updated a lot of examples. * support GEM 91, 92 and 93 all at once, with runtime autodetection (NOT compile-time!) * fixed bug about [#to_pix] when created after [gemwin] was last activated * [#to_pix] and [#from_pix]: when in colorspace rgba, preserve alpha instead of setting to 0 * [#to_pix]: when in colorspace rgb, alpha defaults to 255 instead of 0 * [#to_pix]: correct GL_RGBA vs GL_BGRA on OSX * added [gf/string_length] [doc_link] [doc_accolade] [#lop_space] * added even more missing helpfiles... * [#io.quicktimecamera]: added brightness, contrast, hue and colour (saturation) control * [#io.x11]: setcursor: support 77 cursors instead of 64; and reject out-of-range values * [#color]: runs faster * [#io.videodev]: added colorspace rgba, with alpha=255. * [#io.videodev]: added conversion from RGB to colorspace "magic" * [#camera]: added colorspace rgba * [#io.quartz]: added support for keypress and keyrelease * [#io.quartz]: added 'menubar' method (show/hide system menubar on OSX) * [#io.quartz]: added hidecursor and setcursor * [#io.quicktimecamera]: colorspace rgba's alpha=255 now. * [#io.quicktimecamera] [#io.quicktimeapple]: added colorspaces y, yuv, rgb, and added method "cast". * [#io.videodev] and [#camera]: removed attribute 'transfer' * fixed bug in nested-list processing (which affected [print] and [display] and use of symbols that look like floats) * [#io.videodev]: add support for libv4l1 * [#camera]: added method "api", added autodetection of camera modules * [#io.quicktimehw]: show real error messages * added class [#to~], for converting grids to signals. * [gf/canvas_...] and [gf/find_file]: add default arg * [args]: fixed crash when using comma when there is no [inlet] at all. * [#out quartz]: major speedup ! * [#store]: put_at: fixed two crashing bugs * [#in grid]: handle end-of-file and other errors properly (when reading) * quicktimeapple, quicktimecamera and gem pix : refixed colorspace on PPC * [#io.ppm]: rewritten without using libnetpbm (so that errors are handled properly); support reading P2 P3 P5 P6 and writing P5 P6 * added alias [pd/print] for pd's [print] * added alias [gf/range] for gf's [range] * [#mouse]: added method "/" to automatically scale coordinates * [#draw_rect]: fix outline mode * removed polygon_editor.pd and [#edit_polygon] * added [#out png] (in 1, 2, 3, 4 channels) * added 'cast' method to [#cast] (for changing number type) * [#for] supports floats such as [#for (f #) (f # 10) (f # 1)] * [#out sdl]: fixed mouse button support so that [#mouse] is useful * added class [gemdead], for using pix-objects without a [gemwin]. * OSX: show proper camera error messages * added [#out quartz 0]: make a borderless OSX window * OSX package: enable OpenCV support * Ubuntu package: enable libv4l1 support _ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801 _______________________________________________ Pd-announce mailing list Pd-announce(a)iem.at http://lists.puredata.info/listinfo/pd-announce

10 21

Gigs with Pd
by Pierre Massat 01 Aug '10

01 Aug '10

Hello everyone! There was a discussion not too long ago about suitability of Pd in a live context (off the "smoother audio" thread i think). I just wanted to say that i use Pd everytime i play a gig with my band as a super multi effects. I have never experienced any crash in Pd, and the sound is just excellent, and everybody keeps asking me what the hell are these pedals and this software and how the eff do i make all these sounds, and well, i just think this is the future. I m just hoping that sometime soon we'll have a piece of hardware that's small and powerful enough to run Pd in realtime and I'll have the perfect gear (perfect for me). Just wanted to share this. Cheers! Pierre

13 20

Guitar Pitch tracking in pd
by Marco Donnarumma 30 Jul '10

30 Jul '10

Hi, you might be interested in try out C::ntr::l at http://cntrl.sourceforge.net/ There is also a preset for guitar. Pitch tracking is technically a bit rough though, but I think it could be a good basis, maybe you can modify it as you prefer (i.e. extract only the pitch tracking subpatches and try to make it more precise). If you intend to do so, please write me off-list and I'll be glad to help you surfing the guts, patching style is not that clean.. I made that last year.. M > Message: 7 > Date: Tue, 18 May 2010 12:18:37 -0400 > From: "Pagano, Patrick" <pat(a)digitalworlds.ufl.edu> > Subject: [PD] Guitar Pitch tracking in pd > To: "pd-list(a)iem.at" <pd-list(a)iem.at> > Message-ID: > < > 4102DA2A6DF4394B83D6F9EFC2AD12F73B062FE7C2(a)UFEXCH-MBXCL01.ad.ufl.edu> > Content-Type: text/plain; charset="us-ascii" > > > Hi > > I have a project proposal that wants to track pitches from a guitar > [non-midi] and then translate them into tablature that is readable by > players. I was looking at fiddle and wondering perhaps if processingmight be > of a help but I am posting her to hopefully get some pd feedback and perhaps > a few ideas for implementing this project. Has anyone tried this kind of > pitch tracking in pure data? > > Thanks in advance > > pp >

2 2

Re: [PD] readanysf~ error
by Derek Holzer 22 Jul '10

22 Jul '10

Hi August, thanks for your quick reply and sorry for my slow one ;-) The short answer is that cleaning up the headers of the soundfiles by re-encoding with sndfile-convert did the trick. Celine, the student I am working with, promised to write you a bit later with more details. Best! Derek On 6/15/10 5:31 PM, august wrote: > > Derek, > > Are you using MacOS X? What version of readanysf~? What version > of gavl and gmerlin_avdec are packaged with it/used with it? > > I don't suspect it is the soundfile itself, but just in case, can you > put an example online for me. This is going to be a tough bug to > find, unless you see some sort of regularity in how the sound turns > to noise for you and can report that to me? > > can you make a simple patch that isolates the bug? > > Also, when the sound goes to noise, is it just that one particular > soundfile that is used in readanysf or is it PD's entire output. In > other words, when you hear noise, can you also hear the other > readanysf's playing....or can you also make a simple osc~ and hear it > play correctly? > > The "Current file is either invalid or an unsupported codec." warning > can also come if you send "play" to the readanysf object without it > having a file loaded. I assume this is what is happening. > > -a. > >> Hello August, list.... >> >> I'm helping a student's installation, and we have created a patch which >> uses 24 instances of readanysf~ to read from 24 different soundfiles >> between 15min and one hour in length. All sound files are mono, 16 bit, >> 44.1KHz WAV_PCM format. >> >> The problem is that, after a length of time, the readanysf~ objects >> output noise rather than the soundfile. It is not the result of any >> single soundfile, and many or all of the readanysf~ objects can be >> affected by this simultaneously. >> >> I have attached the abstraction in question. The object is instantiated >> as [readanysf~ 1], in other words the block size and and buffer size are >> defaults. >> >> Sample terminal output is as follows while the patch is running: >> >> Created new readanysf~ with 1 channels and internal buffer of 24 * 64 = 1536 >> Current file is either invalid or an unsupported codec. >> Current file is either invalid or an unsupported codec. >> Current file is either invalid or an unsupported codec. >> Current file is either invalid or an unsupported codec. >> Current file is either invalid or an unsupported codec. >> Current file is either invalid or an unsupported codec. >> Current file is either invalid or an unsupported codec. >> >> Opening each soundfile individually with readanysf~ and sending "play" >> and "pause" messages reports no errors whatsoever, however. >> >> I have sndfile-info data for all of the soundfiles. The only >> irregularity I see in this is one file which reports: >> >> Unknown chunk marker at position 6087587. Resynching. >> >> Besides that, most of the files report something like this: >> >> File : F_DOK6.wav >> Length : 146725772 >> RIFF : 146725764 >> WAVE >> bext : 602 >> fmt : 16 >> Format : 0x1 => WAVE_FORMAT_PCM >> Channels : 1 >> Sample Rate : 44100 >> Block Align : 2 >> Bit Width : 16 >> Bytes/sec : 88200 >> *** minf : 16 (unknown marker) >> *** elm1 : 7506 (unknown marker) >> data : 140114520 >> *** regn : 92 (unknown marker) >> *** umid : 24 (unknown marker) >> *** DGDA : 6602919 (unknown marker) >> End >> >> ---------------------------------------- >> Sample Rate : 44100 >> Frames : 70057260 >> Channels : 1 >> Format : 0x00010002 >> Sections : 1 >> Seekable : TRUE >> Duration : 00:26:28.600 >> Signal Max : 11627 (-9.00 dB) >> >> Someone suggested the noisy output may be the result of a buffer >> problem, but I am not sure who I could verify or correct this. >> >> I checked with "top" while the noise was happening and saw no evidence >> that Pd was using any more memory than usual, and the CPU meter reported >> 30%. >> >> Hardware is an Intel Mac Mini, software is Pd-Extended 0.41.4. >> >> Any suggestions or other diagnostics I could run are appreciated. >> >> Best! >> Derek >> -- >> ::: derek holzer ::: http://macumbista.net ::: >> ---Oblique Strategy # 136: >> "Remove specifics and convert to ambiguities" >> > > > -- ::: derek holzer ::: http://macumbista.net ::: ---Oblique Strategy # 6: "Abandon normal instruments"

7 15

crash Pd-Extended 0.42.5 rc 4
by Mitchell Turner 15 Jul '10

15 Jul '10

Dear all, I hope it is ok to post this on the pd-list. If there is another place I should post, please let me know. I am trying to open the file "simple.pd" which can be found on the TouchOSC site. http://hexler.net/mint/pepper/orderedlist/downloads/download.php?file=http%… Each time I open it, Pd-Extended 0.42.5 rc4 crashes. I have included the log below. The file opens and works properly with Pd-Extended 0.41.4. I'm using Pd-Extended 0.42.5 rc 4. I downloaded this file Pd-0.42.5- extended-rc4-macosx104-i386.dmg. I am using a MacBook Pro with OS 10.5.8. Any help would be appreciated, Mitch Process: pdextended [1737] Path: /Applications/Pd-extended.app/Contents/Resources/ Scripts/../bin/pdextended Identifier: pdextended Version: ??? (???) Code Type: X86 (Native) Parent Process: Pd-extended [1736] Interval Since Last Report: 125 sec Crashes Since Last Report: 5 Per-App Interval Since Last Report: 0 sec Per-App Crashes Since Last Report: 5 Date/Time: 2010-06-25 15:20:58.916 -0400 OS Version: Mac OS X 10.5.8 (9L30) Report Version: 6 Anonymous UUID: 6B2A64E8-CDDE-480E-8495-DECBA5F3F043 Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x000000000000000c Crashed Thread: 0 Thread 0 Crashed: 0 pd 0x0001e00d rtext_new + 53 (g_rtext.c:57) 1 grid.pd_darwin 0x154d3413 0x154d2000 + 5139 2 grid.pd_darwin 0x154d41af 0x154d2000 + 8623 3 pd 0x00018f0a graph_vis + 3455 (g_graph.c:853) 4 pd 0x00013361 canvas_map + 100 (g_canvas.c:656) 5 pd 0x00054e55 pd_typedmess + 1141 (m_class.c:792) 6 pd 0x00054d1b pd_typedmess + 827 (m_class.c:818) 7 pd 0x00058fa8 binbuf_eval + 1224 (m_binbuf.c:726) 8 pd 0x00063170 socketreceiver_read + 1734 (s_inter.c:558) 9 pd 0x00061d30 sys_domicrosleep + 381 (s_inter.c:196) 10 pd 0x00062870 sys_pollgui + 26 (s_inter.c:845) 11 pd 0x0005ef78 m_mainloop + 814 (m_sched.c:493) 12 pd 0x00061a5f sys_main + 2909 (s_main.c:304) 13 pd 0x000027e2 _start + 216 14 pd 0x00002709 start + 41 Thread 1: 0 libSystem.B.dylib 0x95834266 mach_msg_trap + 10 1 libSystem.B.dylib 0x9583ba5c mach_msg + 72 2 com.apple.CoreFoundation 0x93545e7e CFRunLoopRunSpecific + 1790 3 com.apple.CoreFoundation 0x93546aa8 CFRunLoopRunInMode + 88 4 com.apple.audio.CoreAudio 0x944ad5f8 HALRunLoop::OwnThread(void*) + 160 5 com.apple.audio.CoreAudio 0x944ad480 CAPThread::Entry(CAPThread*) + 96 6 libSystem.B.dylib 0x95865155 _pthread_start + 321 7 libSystem.B.dylib 0x95865012 thread_start + 34 Thread 2: 0 libSystem.B.dylib 0x958342c6 semaphore_timedwait_signal_trap + 10 1 libSystem.B.dylib 0x958662af _pthread_cond_wait + 1244 2 libSystem.B.dylib 0x95867b33 pthread_cond_timedwait_relative_np + 47 3 com.apple.audio.CoreAudio 0x944bcbdf CAGuard::WaitFor(unsigned long long) + 213 4 com.apple.audio.CoreAudio 0x944be79a CAGuard::WaitUntil(unsigned long long) + 70 5 com.apple.audio.CoreAudio 0x944bcf3f HP_IOThread::WorkLoop() + 759 6 com.apple.audio.CoreAudio 0x944bcc43 HP_IOThread::ThreadEntry(HP_IOThread*) + 17 7 com.apple.audio.CoreAudio 0x944ad480 CAPThread::Entry(CAPThread*) + 96 8 libSystem.B.dylib 0x95865155 _pthread_start + 321 9 libSystem.B.dylib 0x95865012 thread_start + 34 Thread 3: 0 libSystem.B.dylib 0x958342c6 semaphore_timedwait_signal_trap + 10 1 libSystem.B.dylib 0x958662af _pthread_cond_wait + 1244 2 libSystem.B.dylib 0x95867b33 pthread_cond_timedwait_relative_np + 47 3 com.apple.audio.CoreAudio 0x944bcbdf CAGuard::WaitFor(unsigned long long) + 213 4 com.apple.audio.CoreAudio 0x944be79a CAGuard::WaitUntil(unsigned long long) + 70 5 com.apple.audio.CoreAudio 0x944bcf3f HP_IOThread::WorkLoop() + 759 6 com.apple.audio.CoreAudio 0x944bcc43 HP_IOThread::ThreadEntry(HP_IOThread*) + 17 7 com.apple.audio.CoreAudio 0x944ad480 CAPThread::Entry(CAPThread*) + 96 8 libSystem.B.dylib 0x95865155 _pthread_start + 321 9 libSystem.B.dylib 0x95865012 thread_start + 34 Thread 4: 0 libSystem.B.dylib 0x9583b44e __semwait_signal + 10 1 libSystem.B.dylib 0x95865dcd pthread_cond_wait $UNIX2003 + 73 2 libGLProgrammability.dylib 0x95bc0b32 glvmDoWork + 162 3 libSystem.B.dylib 0x95865155 _pthread_start + 321 4 libSystem.B.dylib 0x95865012 thread_start + 34 Thread 5: 0 libSystem.B.dylib 0x958342ae semaphore_wait_signal_trap + 10 1 libSystem.B.dylib 0x958662c6 _pthread_cond_wait + 1267 2 libSystem.B.dylib 0x958ab539 pthread_cond_wait + 48 3 pdp.pd_darwin 0x143214c0 pdp_procqueue_thread + 89 Thread 0 crashed with X86 Thread State (32-bit): eax: 0x00000000 ebx: 0x0001dfe6 ecx: 0x00000000 edx: 0x00000000 edi: 0x007e0c30 esi: 0x007eba80 ebp: 0xbfffda08 esp: 0xbfffd9e0 ss: 0x0000001f efl: 0x00010282 eip: 0x0001e00d cs: 0x00000017 ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 cr2: 0x0000000c Binary Images:

2 3

Synaptics touchpad input not working
by James Dunn 12 Jul '10

12 Jul '10

I've tried using [hid] and [linuxmouse] and both objects can open the device but no data is output from either object. [MouseState] and [cursor] both work but I was hoping to get relative values. Is this a driver issue? I'm using Ubuntu 8.04 and Pd version 0.42.5-extended-rc3. Here's the console output: [hid] 0.7, written by Hans-Christoph Steiner <hans(a)eds.org> compiled on Jun 13 2010 at 11:45:43 Device 0: 'Macintosh mouse button emulation' on '/dev/input/event0' Device 1: 'AT Translated Set 2 keyboard' on '/dev/input/event1' Device 2: 'PC Speaker' on '/dev/input/event2' Device 3: 'Power Button (FF)' on '/dev/input/event3' Device 4: 'Sleep Button (CM)' on '/dev/input/event4' Device 5: 'Lid Switch' on '/dev/input/event5' Device 6: 'SynPS/2 Synaptics TouchPad' on '/dev/input/event6' Device 7: 'Video Bus' on '/dev/input/event7' Device 8: 'PS/2 Generic Mouse' on '/dev/input/event8' Supported events: Detected: [hid] opened device 6 (/dev/input/event6): SynPS/2 Synaptics TouchPad print: open 1 print: device 6 Also my xorg.conf has this info: Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "SendCoreEvents" "true" Option "Device" "/dev/psaux" Option "Protocol" "auto-dev" Option "HorizEdgeScroll" "FALSE" Option "VertEdgeScroll" "FALSE" Option "SHMconfig" "on" Option "VertTwoFingerScroll" "TRUE" Option "HorizTwoFingerScroll" "TRUE" EndSection Any ideas? thanks, James

7 19

Tracking color with GEM+Pdp
by Olivier Baudu 11 Jul '10

11 Jul '10

Hi, I would like to track different colors at the same time with my web cam so I've try different way. I begun in GEM with [pix_movement] and/or [pix_alpha] and/or [pix_background]. It was quite good until I wanted only one tracking. With two, it begun more complicate to configure [pix_alpha] in RGBA to dissociate the spots. So, I've tried [pdp_ctrack] which is very powerful but in some situations it would be better to process only with moving pixel. I thought [pix_2pdp] would be the solution to use [pix_movement] before [pdp_ctrack] but it seem not to work with [pix_video] in RGBA colorspace, and in YUV I loose the color information after the [pix_movement] process... (By the way, I can't have simultaneously my webcam in GEM and in Pdp with [pix_2pdp], but, maybe, it's normal) What can I do ? Is there a [pix_movement] for Pdp I didn't find yet ? Is there a way to chose precisely the color to configure [pix_alpha] ? (maybe by converting the colorspace with [pix_rgb2hsv] but what to do after ?). Of course, if you have a solution for tracking color without answering my questions, I'm still interested. :-p Thanks. 01ivier

9 20

Floats and negative numbers over OSC
by PSPunch 07 Jul '10

07 Jul '10

Hi, Can someone advise me on the current state of receiving floats and negative numbers over OSC? (on Windows) It seems like both [dumpOSC] and [routeOSC] treats the 4 byte input as an integer, ignoring the format. I've looked through the log but found only similar voices and no solution.. Thanks in advance. -- David Shimamoto

5 10

software license for pd general patch?
by João Pais 07 Jul '10

07 Jul '10

Hello all, I'm doing last touches in a Pd patch that is a general tool to make click tracks. That can (and hopefully will) be used by any musicians, such as instrumentalists, conductors, composers, ... The patch is/will be available free of charge, only paypal donations are accepted (or suggested). But I'm considering using a different license than the general BSD license I usually ship my abstractions with. Since it's a rather complex patch (and if I get any grants to continue to work on it, it might get even more complex), I would prefer for people not to edit it too much - although most of the people using it won't be able even to open the gop. Another aspect is to prevent anyone to grab the code and do a commercial version of it. Not that it will happen anytime soon, but it might be a possibility. I was thinking of instead the BSD to use a CC license, the "Attribution No Derivatives" one - http://creativecommons.org/about/licenses/. Basically something that allows people to disseminate the program (even though is available online), but without them changing it (or not without my consent/knowledge). Does anyone of you has any experience with this, or can suggest a more efficient way of thinking about this? Best, JoÃ£o Pais -- Friedenstr. 58 10249 Berlin (Deutschland) Tel +49 30 42020091 | Mob +49 162 6843570 Studio +49 30 69509190 jmmmpais(a)googlemail.com | skype: jmmmpjmmmp

10 47

readanysf~ error
by Pierre Cage 06 Jul '10

06 Jul '10

> Hi Mathieu, > > > Le 22 juin 2010 à 22:30, Mathieu Bouchard a écrit : > >> On Tue, 22 Jun 2010, pierre cage wrote: >> >>> On my system (osx 10.6, Pd-Ext 0.42.5-RC2, hcs' readanysf intel binary), and no matter the format and the size of the files, 240 successive openings lead to: "Invalid file or unsupported codec. Current file is either invalid or an unsupported codec" >> >> Looks like this error message is wrong and the correct message is the one reported by Pd, isn't it ? > > > I guess so. > > >> >>> Then Pd refuses to save and reports : >>> "error: /Users/me/Documents/PD/stress.pd: Too many open files" >>> I join a simple "stress patch" that tries to isolate the error. >> >> I can't try the patch at this point, but can you try whether sending "pause" before re-sending "open" makes any difference, and whether sending "stop" before re-sending "open" makes any difference. this would be a useful hint to know, for people who want to try solving the problem. > > > > I've tried all (prior "pause", "stop" and straight "open") and haven't noticed any change.

4 13

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Pd-list June 2010