Pd-list February 2013

pd-list@lists.iem.at

106 participants
200 discussions

pdgst + Gem + pix_pix2gst yuv , pb streaming a webcam to an icecast server
by Benjamin ~ 01xy 05 Feb '13

05 Feb '13

Hello, I'm trying to stream a webcam to an icecast server with pdgst and Gem with the attached patch I managed to stream to icecast using [v4l2src] object, so without pix_pix2gst pix2gst.pd example works I managed to stream to icecast out of Pd using this command : # gst-launch v4l2src ! video/x-raw-yuv,width=320,height=240 ! ffmpegcolorspace ! theoraenc quality=16 ! oggmux ! shout2send ip=labomedia.org port=8000 password=**** mount=live.ogv but I can't create [video/x-raw-yuv] ("video/x-raw-yuv ... couldn't create) and [audio/x-raw-float channels=2] neither and when I try without it with the attached patch, no error but no stream tried with PD-extended 0.43.4, GEM: ver: 0.93.3 compiled: Jan 28 2013, Gstreamer 0.10.36-1 on linux mint debian (wheezy) Does pix_pix2gst only works to "Loads in a movie with the videoIO framework" as written in the source code or with the pix_snap object ? I also tried to stream the webcam using Pix_snap to feed pix_pix2gst with no success. Did anybody already managed to use pdgst for video streaming ? thanks for any tips ++Benjamin PS : I can give the pwd of the icecast server in a private e-mail so as to prevent this pwd to be archived with the mailing list == Pd log (4) == setting property 'ip' setting property 'port' setting property 'password' setting property 'mount' info:theora: __gst connect theoraenc1 info:ogg: __gst connect oggmux1 info:shout2send: __gst connect shout2send1 info:vorbis: __gst connect vorbisenc1 info:ogg: __gst connect oggmux1 info:shout2send: __gst connect shout2send1 info:ogg: __gst connect oggmux1 info:shout2send: __gst connect shout2send1 GEM: Only using 8 color bits GEM: Direct Rendering enabled! GEM: GLEW version 1.5.4 GEM: Start rendering info: proplist numread 11 .... v4l2: GEM: pix_video: Opened video connection 0x16 info:theora: __gst connect theoraenc1 info:ogg: __gst connect oggmux1 info:shout2send: __gst connect shout2send1 info:vorbis: __gst connect vorbisenc1 info:ogg: __gst connect oggmux1 info:shout2send: __gst connect shout2send1 info:ogg: __gst connect oggmux1 info:shout2send: __gst connect shout2send1 info:pix2gst: stream_status 0 audiotestsrc1 info:pix2gst: stream_status 1 audiotestsrc1 info:pix2gst: stream_status 0 appsrc0 info:pix2gst: stream_status 1 appsrc0

1 1

Re: [PD] pidip
by Pagano, Patrick 04 Feb '13

04 Feb '13

Hello FWIW. I used the pdp-0.12-6 sources and the pd43 sources to build pidip from CVS Then I created paths for pidip/modules, pidip/patches and pidip/morphology Then created a startup -lib/home/xxxx/pidip/pidip And it mostly all works Only thing I could not get working was pdp_freenect Everything else seems to play nice. I will check the pdp_opencv stuff today Just to be clear I AM NOT using pidip for repressive, military or commercial use. pp

1 1

Re: [PD] file format for GEM
by Thomas Mayer 04 Feb '13

04 Feb '13

Hi, please respond to the list, as others may help in answering your follow-up questions, and / or may benefit from the conversation.0 On 03.02.2013 21:49, Stephan Elliot Perez wrote: > Thanks. I have no idea what a bash script is or what to do with it, but I > will read through the thread... If you use Linux or Mac OS X, bash is usually installed on your system. It is a command line interface and can be used for scripting. (http://en.wikipedia.org/wiki/Bash_%28Unix_shell%29) This particular script is nothing fancy, and I have made it mostly to remind the parameters for mencoder. > Also, I selected JPEG-Photo using the program "MPEGStreamclip" at %100 > quality and it produces quite a large file. With "auto", the CPU goes over > 90, but if I drag up or down on the framerate's number box, it stays at > around 30-40... I assume JPEG-Photo is MJPEG: The video file gets so large, because you store a JPEG for each frame instead of full image for keyframes only and then changes for subsequent frames as do other video codecs (rough explanation). [pix_film] can then read each frame as a JPEG and does not need to find the last keyframe and apply the changes to it, so playback should be possible with lower CPU usage. Please tell us some information about your system, i.e. CPU, graphic card, operating system etc., maybe someone with a similar setup can respond with further advice for optimisation. Hth, Thomas -- "Chaney was aware that anything, however small, can get the eye of the media if it's repulsive enough." (Robert Anton Wilson - The Universe Next Door) http://www.residuum.org/

4 4

closing Pd -nogui plus disabling Greek as main language
by Alexandros Drymonitis 04 Feb '13

04 Feb '13

I've checked the flags to open Pd with some custom settings, but I've no idea how to close it if I open it -nogui. Haven't tried to do, to be honest, but I'd like to be sure about how to close it before I go on playing with it -nogui. The other question is this, which has been address already, but I'm not sure about the answer. I'm running a Pd basics workshop and one of the students has Pd running in Greek by default. I checked Hans's video about how to open Pd in any language, so we did that and Pd opened in English, but as soon as he open a patch we made the week before, Pd turned to Greek again... So, is it something in the Contents/Resources/po directory, or something I should run in Terminal? I don't want to disable the Greek translation, I just don't want it to be the default one..

4 10

pdp-0.12-6 compilation problem
by Pagano, Patrick 04 Feb '13

04 Feb '13

How does one fix the "--export dynamic" unrecognized option when compiling dynamic libraries? If I remove this flag pdp-0.12-6 compiles but fails to link properly I assume And I get /usr/lib/libgsl.so.0: undefined symbol: cblas_dasum When running pd -lib pdp pp -----Original Message----- From: pd-list-bounces(a)iem.at [mailto:pd-list-bounces@iem.at] On Behalf Of Pagano, Patrick Sent: Sunday, February 03, 2013 9:11 PM To: Pd List Subject: [PD] pidip i notice that pidip is not in the new pdextended is there a way we can reconcile this without huge tantrums and bullshit? pp _______________________________________________ Pd-list(a)iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

1 0

now that we don't have user-settable global search paths in Pd-E 0.43
by katja 04 Feb '13

04 Feb '13

Hello, Since a few years I've been using Pd-extended 0.43 incidentally, and since a few months I use it intensively. The discontinuation of user-settable global search paths made me hopping around between alternative solutions, finding out their pro's and cons by (sometimes painful) experience. Don't get me wrong - I think the discontinuation of user-settable global search paths was a good decision. Once you get the best way to work around, it's much easier to share complex patches including dependencies. Initially I preferred the 'namespaces approach'; organize abstractions in folders and instantiate them like you can instantiate objects as [cyclone/svf~], [zexy/limiter~] etc. Sometimes however I felt the need to reorganize folders with abstractions or homebrew externals. Such reorganization forces the namespaces in patches to be refactored. Not good! Then I tried [import] and [declare] instead. I settled on [declare] because it is vanilla Pd, the most flexible approach for all sorts of situations. Fortunately, [declare] doesn't report an error if a path is non-existent, so you can give several options to cover various situations if so desired. I include my home brew binaries and abstractions in subdirs of a project dir, and point to them from the main project patch with [declare -path bin], [declare -path abstractions] and so on. But ow!... with all the namespaces removed I suddenly recalled what makes namespaces so useful. Some classes exist in more than one library. A notable example is [pow~]. There's one in vanilla / Pd core and one in cyclone. Both used to have their exponent and mantissa inlets swapped as compared to [pow]. Somewhere in the Pd 0.43 series, vanilla's [pow~] was refactored to have it's inlets matching the [pow] format. So it became incompatible with Pd 0.42, while [cyclone/pow~] was still compatible with Pd 0.42 and 0.43. Namespaces are also very useful if you have collections of abstractions which you never share but only use for development purposes. For example, I have collections of oscilloscope abstractions and small math utilities. They are stored in their appropriate subdirs on one of the default location as mentioned here: http://puredata.info/docs/faq/how-do-i-install-externals-and-help-files So I can instantiate something like [scopes/scope2~] to quickly check two signal waveforms without including the path in the patch itself, and the object must be removed before the patch is shared. After struggling with Pd search paths for many years, I'm finally starting to get a grip on it. Thanks to / forced by discontinuation of user-settable global paths. No matter how, I guess this will remain tough matter for Pd beginners. Katja

3 3

GOP-GUI-dynamic patching weirdness
by Pierre-Olivier Boulant 03 Feb '13

03 Feb '13

Hello, I've been trying to make a copy of the Max object called "multislider". From what I gathered it's a set of sliders that resizes itself according to the length of the list of values it receives. It was a request posted here: http://codelab.fr/3980 Sounds like something doable with dynamic patching! I had to build some pack-like and unpack-like objects that I could create with a variable number of in/out-lets respectively. That bit seems ok. But there is some weirdness on my system. (Win 7, 64bit with Pd-extended 0.43.4 win32). - First when I start the example patch I have no problem as long as I play with the sliders. But when I start to change the values of any of the numboxes, that's when things start to look ugly. See the screen shot. - I have patch cords supposed to be hidden that show through outside of the GOP. I can live with that. - More concerning I can't see the cursors moving at all. I have to open the abstraction to have them drawn in the subpatch of the abstraction. And then once I close the abstraction, the cursors are properly drawn in the example patch. I can play with them or with the set of numboxes that corresponds to the current number of sliders. Once I change set and the abstractions is resized the cursors are set to zero and won't move. In any case the values are still flowing through the abstractions fine, but, you just can't see the cursors of the sliders. Maybe mixing GOP/GUI and dynamic patching isn't such a swell idea... ;) Anything worth reporting in the bug tracker? Cheers pob

2 2

Plugin auto install feature to Pure data
by fls＠rendera.com.br 03 Feb '13

03 Feb '13

Hi list I would like to write before but unfortunately I couldn't. Some weeks ago people started to talk about the development of some auto install mechanism to Pure Data, like the apt-get. It is an amazing idea. I researched and developed some thing like it to my master degree and I would like to contrib with my 3 cents. I studied the plugin structure of Netbeans, Eclipse, Fire Fox, deb and rpm and my contribution is about it. Sorry if I am a little bit prolix. The first thing is to create a plugin package. A a single file to group a lot of files. It can be a zip package, tar, gzip or anything that already has some C open source API to pack / unpack. This way we can upload / download a single file and extract it localy. I will call it the package. Inside the package is necessary to have a package descriptor. It can be a XML file, CSV, txt, JSON or any kind of structured file to describe the content of the package. This file should have the information about the plugin like the author, version, website, license, OS, dependencies, compatibility with PD "flavors" (vanilla, extended, Lork ....), pre-installation script, post-installation script, uninstall script, key words, ... Pre and post installation script are used to create SQL tables, files or other things. Maybe it is not useful in PD. Uninstall script should clean the mess if you want to remove a plugin. Dependencies is a complex problem because it should care about libraries and circular dependencies. Maybe it is the hardest problem to solve. These two things will define the PD plugin: The package file and the plugin descriptor inside the package. The package structure should be defined as a standard. So we should agree, for example, about the name of the descriptor, the folder where the plugin will be and the name of the package file. Probably a package file can be the name of the external.version.something.pd_pkg. In PD we should have a list of installed plugins. It can be a directory with all the plugin descriptors. The user might be able to install new plugins manually. It means a local file in my machine that I choose. PD will open the package, copy the content to the correct folders and copy the descriptor the the correct folder. The uninstall option will do the oposite, delete the plugin descriptor and delete the plugin files. To update from the web, a plugin repository need to be defined. The client should have a list of repositories address. (It is good because different flavors can have their own plugin repositories and the users can choose which one they want to use.) The plugin server can be implemented with a HTTP server. It will publish the list of available plugins on the server. This list can be the list of package descriptors in a tar / zip file. Locally, PD will keep these lists, one for each server, and it will be used to look for new plugins. Add a new server means add the server to the repositories list and download the plugin list of the new server. Since PD has a list of local installed plugins, if you want to check for updates PD compares the servers plugin lists with your local list. Easy task. Different versions should can be shown and the user would be able to choose what to update. These descriptors can be useful also to search for plugins by author, version, key words, versions, ... Update a plugin means to create a list of update, download the packages to a temp directory and install them locally. Just to step foward, the server can have a web interface with some PHP programming, for instance, that automatically update a package, extract the descriptor, put it in the correct folder and put the plugins in the correct folder. Just to be easier to maintenance. Another tool can help developers to pack. Since I did a new plugin I can select the folder, fill a form with the meta-data and the tool will create the package automatically. That's it. Sorry if I wrote too much. cheers f schiavoni

1 0

Apply missing
by Max 03 Feb '13

03 Feb '13

hi list, hans, i noticed that in the current autobuilds of Pd-extended the property dialogs for the gui-objects are missing the Apply-Button. Is that a bug or a feature? IMHO this is a bug - if you want to adjust for instance a canvas to be the same size as another object of unknown size you can do that with a few clicks and the help of the Apply button. If you have to click OK and then go to context menu->Properties, set the size, OK repeately to do that it's simply annoying. m.

7 19

[PD-announce] LAC 2013: the Linux Audio Conference - Deadline Extension
by IOhannes m zmoelnig - LAC 2013 Organizing Team 02 Feb '13

02 Feb '13

sorry for >< please >> << Hi all, [sorry for the previous empty mail; let me try again...] The Linux Audio Conference submissions deadline has been extended! It is now February 17th, 2013 (23:59 HAST) So, if you were considering to submit a paper but couldn't make up your mind yet, here is your chance to become active! Never forget that this conference lives through the people participating in it. FEBRUARY 17th is the new deadline for all submission types: papers, music, installations, workshop proposals. Check out the link below more info: http://lac.linuxaudio.org/2013/participation Please spread this information to anyone who might be interested. If you have any questions, drop us a line at lac(a)linuxaudio.org We are looking forward to seeing you in Graz in May! Thanks and happy last-minute music-and-paper-submissions, on behalf of the LAC2013 organization team, IOhannes m zmoelnig --- LAC 2013: the Linux Audio Conference May 9-12, 2013 @ IEM, Graz/Austria lac(a)linuxaudio.org http://lac.iem.at _______________________________________________ Pd-announce mailing list Pd-announce(a)iem.at http://lists.puredata.info/listinfo/pd-announce

1 0

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 February 2013