Re: [PD] pidip camera settings high fps
Hello list, everything works, now I wondered if it was possible to change the size of the catch, I have a camera that captures from 640 to 1024, but low fps, I would like to capture at 30 fps and 640, if the capture is small I can run at 30 fps, you can adjust the dimensions? with pdp_scale suffice? Best José > > -- > http://arselectronicachile.blogspot.com > http://comunicacionnativa.blogspot.com/ > http://www.myspace.com/santorcuato > -- http://arselectronicachile.blogspot.com http://comunicacionnativa.blogspot.com/ http://www.myspace.com/santorcuato ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
[PD] pidip camera settings high fps
Hello list, everything works, now I wondered if it was possible to change the size of the catch, I have a camera that captures from 640 to 1024, but low fps, I would like to capture at 30 fps and 640, catch smaller setear possible dimensions? with pdp_scale suffice? Best regards José -- http://arselectronicachile.blogspot.com http://comunicacionnativa.blogspot.com/ http://www.myspace.com/santorcuato ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] [PD-dev] PD L2Ork 20101229 snapshot now available
Ah ok. Then don't bother-- I just already had an older "Burrito" version installed and was trying to just quickly test some of the changes. -Jonathan --- On Thu, 12/30/10, Ivica Ico Bukvic wrote: > From: Ivica Ico Bukvic > Subject: RE: [PD-dev] PD L2Ork 20101229 snapshot now available > To: "'Jonathan Wilkes'" , pd-list@iem.at > Date: Thursday, December 30, 2010, 3:00 AM > If you are trying to run the app > without installing, then copy pd.tk from pd/src/ dir into > pd/bin/ dir. I forgot to add this as it is actually not a > part of the actual install. I will reupload another version > that includes this but please understand this is not the > "default" way of things. You will likely have a much better > experience with doing actually make install and now that > pd-l2ork exists in a separate path from the pd-vanilla and > extended, it should happily coexist next to them. > > HTH, > > Best wishes, > > Ico > > > -Original Message- > > From: Jonathan Wilkes [mailto:jancs...@yahoo.com] > > Sent: Wednesday, December 29, 2010 6:05 PM > > To: pd-list@iem.at; > Ivica Ico Bukvic > > Subject: Re: [PD-dev] PD L2Ork 20101229 snapshot now > available > > > > I tried running the non-supreme burrito version by > running ./pd-l2ork > > from the console and got an empty tk window with the > following errors > > to the terminal window: > > tcl: /home/dude/Desktop/libmobiledevice/pd/bin/pd.tk: > can't open > > script > > invalid command name "pdtk_post" > > invalid command name "pdtk_post" > > invalid command name "pdtk_post" > > invalid command name "pdtk_pd_startup" > > invalid command name "pdtk_post" > > invalid command name "pdtk_post" > > invalid command name "pdtk_post" > > invalid command name "pdtk_post" > > invalid command name "pdtk_post" > > > > -Jonathan > > > > --- On Wed, 12/29/10, Ivica Ico Bukvic wrote: > > > > > From: Ivica Ico Bukvic > > > Subject: [PD-dev] PD L2Ork 20101229 snapshot now > available > > > To: linux-audio-annou...@lists.linuxaudio.org, > l...@lists.linuxaudio.org, > > l...@lists.linuxaudio.org, > pd-list@iem.at, pd-...@iem.at, > l2ork- > > d...@disis.music.vt.edu, > u...@disis.music.vt.edu, > pik...@piksel.no > > > Date: Wednesday, December 29, 2010, 9:57 PM > > > Please excuse cross-posting. > > > > > > Dear friends and fellow FOSS enthusiasts, > > > > > > It is my great pleasure to share with the > community a > > > belated Holiday > > > present :-) in a form of latest snapshot of L2Ork > iteration > > > of > > > Pure-Data. Better than ever, the latest version > comes with > > > the following > > > improvements: > > > > > > *implemented apply undo for array properties and > partially > > > implemented > > > apply undo for graph-on-parent object properties > (does not > > > apply to > > > abstractions or top-level windows currently until > I figure > > > out how to > > > address the indexing of toplevel windows inside > the glist > > > as well as how > > > to address to which window such an undo > belongs). > > > *properties are disabled when right-clicking on > an > > > abstraction as > > > modifying its settings externally does not make > sense when > > > one does not > > > see the actual contents inside it. So, to edit > the > > > properties of an > > > abstraction, one has to open the actual > abstraction. > > > *fixed how new arrays are created so that they > always fit > > > within the > > > specified boundaries. Please note arrays that > have been > > > already created > > > in prior patches remain untouched in terms of > graph > > > auto-resizing > > > (legacy code is provided in g_editor.c canvas_vis > that > > > deals with this > > > if anyone wishes to convert their arrays but is > incomplete > > > in that it > > > assumes all arrays require resizing--this is > however > > > unnecessary as > > > simple recreation of said arrays or manual > readjustment of > > > their > > > settings ought to do the trick. > > > -This feature needs further > > > testing--feedback is most appreciated. > > > *fixed how arrays deal with moving array points > via mouse
Re: [PD] [PD-dev] PD L2Ork 20101229 snapshot now available
> If you are trying to run the app without installing, then copy pd.tk from > pd/src/ dir into pd/bin/ dir. I forgot to add this as it is actually not a > part > of the actual install. I will reupload another version that includes this but > please understand this is not the "default" way of things. You will likely > have a much better experience with doing actually make install and > now that pd-l2ork exists in a separate path from the pd-vanilla and > extended, it should happily coexist next to them. Actually, I stand corrected. Because pd-l2ork is now looking for pd.tk in a specific folder (namely due to the way binaries were configured in /usr/local/lib/pd-l2ork/bin), you will not be able to run pd-l2ork any more without installing. HTH Best wishes, Ico ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] [PD-dev] PD L2Ork 20101229 snapshot now available
Ah, ok. --- On Thu, 12/30/10, Ivica Ico Bukvic wrote: > From: Ivica Ico Bukvic > Subject: RE: [PD-dev] PD L2Ork 20101229 snapshot now available > To: "'Jonathan Wilkes'" , pd-list@iem.at > Date: Thursday, December 30, 2010, 3:00 AM > If you are trying to run the app > without installing, then copy pd.tk from pd/src/ dir into > pd/bin/ dir. I forgot to add this as it is actually not a > part of the actual install. I will reupload another version > that includes this but please understand this is not the > "default" way of things. You will likely have a much better > experience with doing actually make install and now that > pd-l2ork exists in a separate path from the pd-vanilla and > extended, it should happily coexist next to them. > > HTH, > > Best wishes, > > Ico > > > -Original Message- > > From: Jonathan Wilkes [mailto:jancs...@yahoo.com] > > Sent: Wednesday, December 29, 2010 6:05 PM > > To: pd-list@iem.at; > Ivica Ico Bukvic > > Subject: Re: [PD-dev] PD L2Ork 20101229 snapshot now > available > > > > I tried running the non-supreme burrito version by > running ./pd-l2ork > > from the console and got an empty tk window with the > following errors > > to the terminal window: > > tcl: /home/dude/Desktop/libmobiledevice/pd/bin/pd.tk: > can't open > > script > > invalid command name "pdtk_post" > > invalid command name "pdtk_post" > > invalid command name "pdtk_post" > > invalid command name "pdtk_pd_startup" > > invalid command name "pdtk_post" > > invalid command name "pdtk_post" > > invalid command name "pdtk_post" > > invalid command name "pdtk_post" > > invalid command name "pdtk_post" > > > > -Jonathan > > > > --- On Wed, 12/29/10, Ivica Ico Bukvic wrote: > > > > > From: Ivica Ico Bukvic > > > Subject: [PD-dev] PD L2Ork 20101229 snapshot now > available > > > To: linux-audio-annou...@lists.linuxaudio.org, > l...@lists.linuxaudio.org, > > l...@lists.linuxaudio.org, > pd-list@iem.at, pd-...@iem.at, > l2ork- > > d...@disis.music.vt.edu, > u...@disis.music.vt.edu, > pik...@piksel.no > > > Date: Wednesday, December 29, 2010, 9:57 PM > > > Please excuse cross-posting. > > > > > > Dear friends and fellow FOSS enthusiasts, > > > > > > It is my great pleasure to share with the > community a > > > belated Holiday > > > present :-) in a form of latest snapshot of L2Ork > iteration > > > of > > > Pure-Data. Better than ever, the latest version > comes with > > > the following > > > improvements: > > > > > > *implemented apply undo for array properties and > partially > > > implemented > > > apply undo for graph-on-parent object properties > (does not > > > apply to > > > abstractions or top-level windows currently until > I figure > > > out how to > > > address the indexing of toplevel windows inside > the glist > > > as well as how > > > to address to which window such an undo > belongs). > > > *properties are disabled when right-clicking on > an > > > abstraction as > > > modifying its settings externally does not make > sense when > > > one does not > > > see the actual contents inside it. So, to edit > the > > > properties of an > > > abstraction, one has to open the actual > abstraction. > > > *fixed how new arrays are created so that they > always fit > > > within the > > > specified boundaries. Please note arrays that > have been > > > already created > > > in prior patches remain untouched in terms of > graph > > > auto-resizing > > > (legacy code is provided in g_editor.c canvas_vis > that > > > deals with this > > > if anyone wishes to convert their arrays but is > incomplete > > > in that it > > > assumes all arrays require resizing--this is > however > > > unnecessary as > > > simple recreation of said arrays or manual > readjustment of > > > their > > > settings ought to do the trick. > > > -This feature needs further > > > testing--feedback is most appreciated. > > > *fixed how arrays deal with moving array points > via mouse > > > by restricting > > > them within the array bounds--this should work > for all > > > gui-driven array > > > operations, while
Re: [PD] [PD-dev] PD L2Ork 20101229 snapshot now available
If you are trying to run the app without installing, then copy pd.tk from pd/src/ dir into pd/bin/ dir. I forgot to add this as it is actually not a part of the actual install. I will reupload another version that includes this but please understand this is not the "default" way of things. You will likely have a much better experience with doing actually make install and now that pd-l2ork exists in a separate path from the pd-vanilla and extended, it should happily coexist next to them. HTH, Best wishes, Ico > -Original Message- > From: Jonathan Wilkes [mailto:jancs...@yahoo.com] > Sent: Wednesday, December 29, 2010 6:05 PM > To: pd-list@iem.at; Ivica Ico Bukvic > Subject: Re: [PD-dev] PD L2Ork 20101229 snapshot now available > > I tried running the non-supreme burrito version by running ./pd-l2ork > from the console and got an empty tk window with the following errors > to the terminal window: > tcl: /home/dude/Desktop/libmobiledevice/pd/bin/pd.tk: can't open > script > invalid command name "pdtk_post" > invalid command name "pdtk_post" > invalid command name "pdtk_post" > invalid command name "pdtk_pd_startup" > invalid command name "pdtk_post" > invalid command name "pdtk_post" > invalid command name "pdtk_post" > invalid command name "pdtk_post" > invalid command name "pdtk_post" > > -Jonathan > > --- On Wed, 12/29/10, Ivica Ico Bukvic wrote: > > > From: Ivica Ico Bukvic > > Subject: [PD-dev] PD L2Ork 20101229 snapshot now available > > To: linux-audio-annou...@lists.linuxaudio.org, l...@lists.linuxaudio.org, > l...@lists.linuxaudio.org, pd-list@iem.at, pd-...@iem.at, l2ork- > d...@disis.music.vt.edu, u...@disis.music.vt.edu, pik...@piksel.no > > Date: Wednesday, December 29, 2010, 9:57 PM > > Please excuse cross-posting. > > > > Dear friends and fellow FOSS enthusiasts, > > > > It is my great pleasure to share with the community a > > belated Holiday > > present :-) in a form of latest snapshot of L2Ork iteration > > of > > Pure-Data. Better than ever, the latest version comes with > > the following > > improvements: > > > > *implemented apply undo for array properties and partially > > implemented > > apply undo for graph-on-parent object properties (does not > > apply to > > abstractions or top-level windows currently until I figure > > out how to > > address the indexing of toplevel windows inside the glist > > as well as how > > to address to which window such an undo belongs). > > *properties are disabled when right-clicking on an > > abstraction as > > modifying its settings externally does not make sense when > > one does not > > see the actual contents inside it. So, to edit the > > properties of an > > abstraction, one has to open the actual abstraction. > > *fixed how new arrays are created so that they always fit > > within the > > specified boundaries. Please note arrays that have been > > already created > > in prior patches remain untouched in terms of graph > > auto-resizing > > (legacy code is provided in g_editor.c canvas_vis that > > deals with this > > if anyone wishes to convert their arrays but is incomplete > > in that it > > assumes all arrays require resizing--this is however > > unnecessary as > > simple recreation of said arrays or manual readjustment of > > their > > settings ought to do the trick. > > -This feature needs further > > testing--feedback is most appreciated. > > *fixed how arrays deal with moving array points via mouse > > by restricting > > them within the array bounds--this should work for all > > gui-driven array > > operations, while array alterations via snapshots and other > > external > > ways of manipulating arrays remain unbound so as to allow > > for > > traditional data-flow debugging--this may change down the > > road in part > > due to introduction of the magicGlass option and in part > > due to belief > > that data monitoring should only report ranges specified by > > the graph. > > -This feature needs further > > testing--feedback is most appreciated. > > *added new feature for arrays where they report a bang > > through the > > _changed send (if one is provided) > > whenever they have been > > altered by a mouse click'n'drag--this in conjunction with > > array graph > > auto-resizing makes arrays formidable alternatives for > > multisliders. > > -This feature needs further > &g
Re: [PD] pidip error color mode
Hi, thanks, I solved the web camera connection, but has a considerable latency, the features are: ubuntu lucid 10.04, pentium 4 at 2.66 and 2 gb ram, NVIDIA GeForce 6200, goes slow, very slow, the system takes 5 minutes to start, and the latency of the camera is obvious, what camera you recommend?, the previous problem was that the camera was not supported. I can speed up the fps? ... Regards José 2010/12/29 Bastiaan van den Berg : > On Wed, Dec 29, 2010 at 14:11, Jose Luis Santorcuato > wrote: >> >> Hi all, I am working with the library PiDiP, I have previously worked >> with osx and linux ubuntu, had worked with the netbook acer and had no >> problems, but now I get the following error when trying to open the >> video window (i want to show a live video from webcam, easy in olds >> projects): >> >> pdp_v4l2: unsupported color model: 1497715271 >> >> also pdp_v4l2: unsupported color model: 1195724874 > > You could try starting pd like this : > > LD_PRELOAD=/usr/lib/libv4l/v4l2convert.so pd > > This will put the convert library of libv4l between pd and v4l, and it will > convert colormodels (and mjpeg for example) into a format that should be > supported. > > Let me know if it works :) > > -- > Regards, > buZz > -- http://arselectronicachile.blogspot.com http://comunicacionnativa.blogspot.com/ http://www.myspace.com/santorcuato ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
[PD] understanding fexpr~ example
Hi Dear list, i was experimenting with the lorenz example that comes with the fexpr~ help file. Can anybody explain me how that example internally works? how is fexpr~ generating the waveform in this case? thanks in advance R. ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] [PD-dev] PD L2Ork 20101229 snapshot now available
I tried running the non-supreme burrito version by running ./pd-l2ork from the console and got an empty tk window with the following errors to the terminal window: tcl: /home/dude/Desktop/libmobiledevice/pd/bin/pd.tk: can't open script invalid command name "pdtk_post" invalid command name "pdtk_post" invalid command name "pdtk_post" invalid command name "pdtk_pd_startup" invalid command name "pdtk_post" invalid command name "pdtk_post" invalid command name "pdtk_post" invalid command name "pdtk_post" invalid command name "pdtk_post" -Jonathan --- On Wed, 12/29/10, Ivica Ico Bukvic wrote: > From: Ivica Ico Bukvic > Subject: [PD-dev] PD L2Ork 20101229 snapshot now available > To: linux-audio-annou...@lists.linuxaudio.org, l...@lists.linuxaudio.org, > l...@lists.linuxaudio.org, pd-list@iem.at, pd-...@iem.at, > l2ork-...@disis.music.vt.edu, u...@disis.music.vt.edu, pik...@piksel.no > Date: Wednesday, December 29, 2010, 9:57 PM > Please excuse cross-posting. > > Dear friends and fellow FOSS enthusiasts, > > It is my great pleasure to share with the community a > belated Holiday > present :-) in a form of latest snapshot of L2Ork iteration > of > Pure-Data. Better than ever, the latest version comes with > the following > improvements: > > *implemented apply undo for array properties and partially > implemented > apply undo for graph-on-parent object properties (does not > apply to > abstractions or top-level windows currently until I figure > out how to > address the indexing of toplevel windows inside the glist > as well as how > to address to which window such an undo belongs). > *properties are disabled when right-clicking on an > abstraction as > modifying its settings externally does not make sense when > one does not > see the actual contents inside it. So, to edit the > properties of an > abstraction, one has to open the actual abstraction. > *fixed how new arrays are created so that they always fit > within the > specified boundaries. Please note arrays that have been > already created > in prior patches remain untouched in terms of graph > auto-resizing > (legacy code is provided in g_editor.c canvas_vis that > deals with this > if anyone wishes to convert their arrays but is incomplete > in that it > assumes all arrays require resizing--this is however > unnecessary as > simple recreation of said arrays or manual readjustment of > their > settings ought to do the trick. > -This feature needs further > testing--feedback is most appreciated. > *fixed how arrays deal with moving array points via mouse > by restricting > them within the array bounds--this should work for all > gui-driven array > operations, while array alterations via snapshots and other > external > ways of manipulating arrays remain unbound so as to allow > for > traditional data-flow debugging--this may change down the > road in part > due to introduction of the magicGlass option and in part > due to belief > that data monitoring should only report ranges specified by > the graph. > -This feature needs further > testing--feedback is most appreciated. > *added new feature for arrays where they report a bang > through the > _changed send (if one is provided) > whenever they have been > altered by a mouse click'n'drag--this in conjunction with > array graph > auto-resizing makes arrays formidable alternatives for > multisliders. > -This feature needs further > testing--feedback is most appreciated. > *when an array subpatch is opened and resized, the array > automatically > now resizes to properly fill the window. > -This feature needs further > testing--feedback is most appreciated. > *fixed where array was not visible after reopening the > patch if any of > its points touched upon y graph limits. > *fixed couple of segfaults caused by gridflow > incompatibility--more > problems remain with gridflow library compatibility, likely > due to > widgetbehavior and possibly also magicGlass > incompatibility. Further > investigation is necessary. > *fixed memory leak in the disis_phasor~ external where the > destructor > was never properly called and updated its documentation > (available in > the l2ork_addons package). > *fixed highlighting of signal nlets where nlet would revert > to > non-signal appearance after being highlighted/connected. > *reintroduced array listview (this was a regression in > respect to > pd-extended). > *improved appearance of the array listview. > *fixed a few broken links in the pddp documentation and > added new > l2ork-specific array features to
[PD] PD L2Ork 20101229 snapshot now available
Please excuse cross-posting. Dear friends and fellow FOSS enthusiasts, It is my great pleasure to share with the community a belated Holiday present :-) in a form of latest snapshot of L2Ork iteration of Pure-Data. Better than ever, the latest version comes with the following improvements: *implemented apply undo for array properties and partially implemented apply undo for graph-on-parent object properties (does not apply to abstractions or top-level windows currently until I figure out how to address the indexing of toplevel windows inside the glist as well as how to address to which window such an undo belongs). *properties are disabled when right-clicking on an abstraction as modifying its settings externally does not make sense when one does not see the actual contents inside it. So, to edit the properties of an abstraction, one has to open the actual abstraction. *fixed how new arrays are created so that they always fit within the specified boundaries. Please note arrays that have been already created in prior patches remain untouched in terms of graph auto-resizing (legacy code is provided in g_editor.c canvas_vis that deals with this if anyone wishes to convert their arrays but is incomplete in that it assumes all arrays require resizing--this is however unnecessary as simple recreation of said arrays or manual readjustment of their settings ought to do the trick. -This feature needs further testing--feedback is most appreciated. *fixed how arrays deal with moving array points via mouse by restricting them within the array bounds--this should work for all gui-driven array operations, while array alterations via snapshots and other external ways of manipulating arrays remain unbound so as to allow for traditional data-flow debugging--this may change down the road in part due to introduction of the magicGlass option and in part due to belief that data monitoring should only report ranges specified by the graph. -This feature needs further testing--feedback is most appreciated. *added new feature for arrays where they report a bang through the _changed send (if one is provided) whenever they have been altered by a mouse click'n'drag--this in conjunction with array graph auto-resizing makes arrays formidable alternatives for multisliders. -This feature needs further testing--feedback is most appreciated. *when an array subpatch is opened and resized, the array automatically now resizes to properly fill the window. -This feature needs further testing--feedback is most appreciated. *fixed where array was not visible after reopening the patch if any of its points touched upon y graph limits. *fixed couple of segfaults caused by gridflow incompatibility--more problems remain with gridflow library compatibility, likely due to widgetbehavior and possibly also magicGlass incompatibility. Further investigation is necessary. *fixed memory leak in the disis_phasor~ external where the destructor was never properly called and updated its documentation (available in the l2ork_addons package). *fixed highlighting of signal nlets where nlet would revert to non-signal appearance after being highlighted/connected. *reintroduced array listview (this was a regression in respect to pd-extended). *improved appearance of the array listview. *fixed a few broken links in the pddp documentation and added new l2ork-specific array features to the pddp documentation. Latest snapshot is available from the usual place: http://l2ork.music.vt.edu/main/?page_id=56 Complete changelog since 11/25/2010 is available here: http://l2ork.music.vt.edu/data/pd/Changelog Happy belated Holidays! Best wishes, Ico ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] libraries in Pd-extended 0.43
--- On Sun, 12/19/10, Mathieu Bouchard wrote: > From: Mathieu Bouchard > Subject: Re: [PD] libraries in Pd-extended 0.43 > To: "Jonathan Wilkes" > Cc: "PD List" , "Hans-Christoph Steiner" > Date: Sunday, December 19, 2010, 1:54 AM > On Tue, 14 Dec 2010, Jonathan Wilkes > wrote: > > > Yeah, so currently I have links inside canvas-help.pd > to table-help.pd, pd-help.pd, graph-help.pd, and a special > note about "Put" menu arrays with a link to > array-help.pd. array-help.pd is necessary to have > there because triggering the help patch for the "Put" menu > array is so obscure (I wonder if anyone here even knows what > to click to get it.) > > I don't know how you can possibly not get it. That's probably because you've never gotten it. Clicking on the graph that contains the array opens up 'canvas-help.pd'. But you can open a help patch named 'array-help.pd' when you: a) right-click on the "Put" menu array and choose "Open", b) mouse-over an array element until the arrow cursor changes directions, c) right-click and choose help. Then you will receive enlightenment from Pd's generous help docs: sorry, couldn't find help patch for "array.pd" Though it's certainly to the point, I thought a user might want a tad bit more information than that, so I made an array-help.pd patch, and linked to it in canvas-help.pd for those few boring users who choose not to click random spots within a patch until something helpful and relevant happens. -Jonathan > Do you expect > that you can get it by right-clicking the array's label ? > Because, it doesn't work for any other label (IEMGUI...), > so, why would it work for Array's label ? > > > That's true, but just because it's possible to do that > doesn't mean that [inlet] and [outlet] are relevant enough > to show in the help patch for [table], any more than showing > [list] in the help patch for [metro]. > > Also, it doesn't work the other way around-- > [tabread], [tabwrite], etc. are not relevant to [pd]. > > Actually, when you have a [table], you don't have one > object, you have two of them. Three of them. There's also a graph within the table. > When you have [table foo], > receive-symbol "pd-foo" sends to a canvas, whereas > receive-symbol "foo" sends to the internal t_array object, > which has all of the array-specific methods. This has to be > made clear, because it's not like an inheritance-like > pattern. > > An inheritance-like pattern (or interface pattern) would > be, for example, to have one single help-patch for most of > the common methods in iemguis, those that have exactly the > same behaviour, to emphasise that they are one single family > (even though inheritance in pd is mostly in our > imagination). It's a matter of documenting things in a > non-repetitive, synthetic manner, and with a mindset that > encourages consistency. How do you make that system of documentation consistent across libraries? (And show links across libraries?) > > When you have one class that seemingly would include one > complete other helpfile's content but not the other way > around, that would usually be an inheritance pattern, but > it's not here, because instead, it's mostly that a canvas > has a t_array tacked onto it, vs not. > > It can't be called delegation pattern either, because in a > delegation pattern, you have two objects, of which you only > send to one, which will forward the message to the other one > whenever appropriate. This is not the case here, because you > can send to two different receive-symbols, and you have to > send to the correct one. > > I could have said a lot less, but I just thought I'd give > you some more doc ideas. > > > ___ > | Mathieu Bouchard tél: +1.514.383.3801 > Villeray, Montréal, QC ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] pidip error color mode
Yes, i used that...maybe i dont considered v4l2ill try and comment... Thanks José 2010/12/29 Bastiaan van den Berg : > On Wed, Dec 29, 2010 at 14:11, Jose Luis Santorcuato > wrote: >> >> Hi all, I am working with the library PiDiP, I have previously worked >> with osx and linux ubuntu, had worked with the netbook acer and had no >> problems, but now I get the following error when trying to open the >> video window (i want to show a live video from webcam, easy in olds >> projects): >> >> pdp_v4l2: unsupported color model: 1497715271 >> >> also pdp_v4l2: unsupported color model: 1195724874 > > You could try starting pd like this : > > LD_PRELOAD=/usr/lib/libv4l/v4l2convert.so pd > > This will put the convert library of libv4l between pd and v4l, and it will > convert colormodels (and mjpeg for example) into a format that should be > supported. > > Let me know if it works :) > > -- > Regards, > buZz > -- http://arselectronicachile.blogspot.com http://comunicacionnativa.blogspot.com/ http://www.myspace.com/santorcuato ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] pidip error color mode
On Wed, Dec 29, 2010 at 14:11, Jose Luis Santorcuato < santorcuat...@gmail.com> wrote: > Hi all, I am working with the library PiDiP, I have previously worked > with osx and linux ubuntu, had worked with the netbook acer and had no > problems, but now I get the following error when trying to open the > video window (i want to show a live video from webcam, easy in olds > projects): > > pdp_v4l2: unsupported color model: 1497715271 > > also pdp_v4l2: unsupported color model: 1195724874 > You could try starting pd like this : LD_PRELOAD=/usr/lib/libv4l/v4l2convert.so pd This will put the convert library of libv4l between pd and v4l, and it will convert colormodels (and mjpeg for example) into a format that should be supported. Let me know if it works :) -- Regards, buZz ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
[PD] pidip error color mode
Hi all, I am working with the library PiDiP, I have previously worked with osx and linux ubuntu, had worked with the netbook acer and had no problems, but now I get the following error when trying to open the video window (i want to show a live video from webcam, easy in olds projects): pdp_v4l2: unsupported color model: 1497715271 also pdp_v4l2: unsupported color model: 1195724874 What is it? Greetings Josè -- http://arselectronicachile.blogspot.com http://comunicacionnativa.blogspot.com/ http://www.myspace.com/santorcuato ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
