I would have liked to see your demo at the SAT but I got held up at work. I am less interested in VJing lately, so the next version of V3 will mostly be oriented towards installation work on integration into other complete packages (like pixelTANGO). I would like to merge the projects because I do not wish to further the development of V3 but I do not want it go to waste ( I put a lot of math in there!).
The next version will only have 3 parts to it :
- a multiple video file player (in XP, gem crashes when you switch
videofiles, so I need to create a new instance of pix_movie for every video). 2) a "breakable" video surface that will be composed of a dynamic number of objects. I have also created a messaging system to give CUES to the 3d objects (like go to point A in 5 seconds then go to point B while rotating x degrees then scaling big in 1 second). 3) a gemwindow manager thingy.
What is done :
- video player (just need to add multiple video file support) with
many options (loop points and frame number and variable speed playback, etc) 2) I have made my own state saving mechanism : I never got memento to work for me. 3) The breakable window thingy is almost complete.
How I imagine it could connect to pixelTANGO :
v3 vidplayer (v3.vid)) -> pixelTANGO -> v3 breakable surface (v3.surface) -> geo
Off topic : does gemkeyboard and gemouse work in OS X?
Tom
On Wed, 16 Mar 2005 12:52:52 -0500, B. Bogart ben@ekran.org wrote:
Hey Tom,
I spoke to Patrick a bit at the SAT on thursday. We were talking about how it could be possible to merge V3 with pixelTANGO. Here are a few of the objectives of pixelTANGO:
- pixelTANGO (aka pt) is a set of abstractions and externals, for pd/GEM, that make using pd and GEM easier, faster and more satisfying.
- The purpose of pt is to balance usability and ease of learning with programmability, modularity and flexibility.
- This balance means that pt will always be playing catch-up to build easy to use interfaces to the ever growing and complex functionality of GEM.
- This means that often pixelTANGO will be used with "traditional" pd/Gem programming for and by artists to create performances as well as contribute more specialized pt modules back to the community.
- Make pd/Gem more accessible to artists by increasing the ease of use and making a more shallow learning curve
- Keep the modular nature of pd/Gem intact
- Ability to use full resolution DV videos, live, recorded and streamed over IP.
- Artist can work in 2D and 3D or both
- External control of pt through MIDI, OSC and custom hardware (Via AID*1)
- Community supported and developed
Exitsing features of pixelTANGO are:
- Easy two file drag and drop installation (on OSX)
- Complete documentation
- DV over firewire, network streams (QTL or SDP), still images and movie files as inputs.
- Number of layers only limited by available hardware
- Filters for layers with plug-in architecture
- OpenGL effects for layers (rotate/scale/translate etc..)
- Text & 3D model layers
- Configurable smooth interpolation on all parameters
- Preset (state) saving and preset animation
- Quick access to directories of files
What are the objectives/features of V3?
How do you see the projects connecting/merging?
Things like BPM sync etc.. have been requested for pixelTANGO but I have little personal interest in them. Also I think pixelTANGO has a more unified design that acts more like an application than a patch. For example there is a plugin system that dynamically generates an array of abstractions in the "fx/" folder and manages the seamless routing between them. V3 effects could be added to this perhaps. PDP too for that matter. (these are pix_ based effects) Also I want to build something similar for transitions that I think its a strong-point of V3.
What benifits do you think there are to merging the projects?
What do you think of things like PiDiP/PDP integration?
Did you see the Article in La Presse on friday the 11th on the TOT project?
Anyhow I'd love to hear your thoughts on the matter.
Oh and fwish looks pretty amazing, how did you get the alpha-channel working well? (multiimage, or alpha video? or? The OSX developers have broken pix_mask and don't see it being valuable! yuck!)
b>
Thomas Ouellet Fredericks wrote:
Here are videos (screen captures, not yet the actual installation) and part of the code of my Fwish (Bassin du destion) installation. One version has fish that do not collide, the other does not because I decided it is nicer when the fish overlap.
http://www.danslchamp.org/mrtof/code.htm
tom tom@danslchamp.org
On Tue, 15 Mar 2005 18:30:41 +0100, Frank Barknecht fbar@footils.org wrote:
Hallo Nicolas, Nicolas Montgermont hat gesagt: // Nicolas Montgermont wrote:
I've been experimenting pmpd with datastructure for a week now,
Wow! That's quite a patch for one week, wonderful!!
and I encounter a few problems that are all present in the attached patch:
- Computation speed! The simple model presented here (5 mass, 8
link) seems to charge all my CPU at a metro period of 100ms. The string patch designed by Frank Barknecht in the datastructure tutorial was much more faster. Does anybody see any "bad" programming in the patch?
I also get a very high load. I will need a bit time to take a deeper look, but generally the data structures are far from the efficiency that e.g. Gem has. However I don't think your model should be that slow.
- use the $0 variable to have mutiple instanciation, but I have to
use the external "sprintf" to build the "pd-$0-data" message. Is there a solution using only native pd objects to do that?
Yes, and it even works better here (maybe I have another sprintf, I get lots of errors like "sprintf: no method for float").
Anyway the solution is to replace every "sprintf" with "makefilename", you can keep the "pd-%d-data" part, it's the same for makefilename.
Ciao
Frank Barknecht _ ______footils.org__
_ __latest track: "scans" _ http://footils.org/cms/show/41
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://iem.at/cgi-bin/mailman/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://iem.at/cgi-bin/mailman/listinfo/pd-list
Ok. You did not have cylcone loaded so you were using another gate object, so I replaced it with demux (its better and from zexy). The new version (once I know in what format to convert the videos) should work, I am uploading it now.
www.danslchamp.org/mrtof/code.htm
Tom
On Wed, 16 Mar 2005 14:11:23 -0500, Thomas Ouellet Fredericks iamonthebeach@gmail.com wrote:
I would have liked to see your demo at the SAT but I got held up at work. I am less interested in VJing lately, so the next version of V3 will mostly be oriented towards installation work on integration into other complete packages (like pixelTANGO). I would like to merge the projects because I do not wish to further the development of V3 but I do not want it go to waste ( I put a lot of math in there!).
The next version will only have 3 parts to it :
- a multiple video file player (in XP, gem crashes when you switch
videofiles, so I need to create a new instance of pix_movie for every video). 2) a "breakable" video surface that will be composed of a dynamic number of objects. I have also created a messaging system to give CUES to the 3d objects (like go to point A in 5 seconds then go to point B while rotating x degrees then scaling big in 1 second). 3) a gemwindow manager thingy.
What is done :
- video player (just need to add multiple video file support) with
many options (loop points and frame number and variable speed playback, etc) 2) I have made my own state saving mechanism : I never got memento to work for me. 3) The breakable window thingy is almost complete.
How I imagine it could connect to pixelTANGO :
v3 vidplayer (v3.vid)) -> pixelTANGO -> v3 breakable surface (v3.surface) -> geo
Off topic : does gemkeyboard and gemouse work in OS X?
Tom
On Wed, 16 Mar 2005 12:52:52 -0500, B. Bogart ben@ekran.org wrote:
Hey Tom,
I spoke to Patrick a bit at the SAT on thursday. We were talking about how it could be possible to merge V3 with pixelTANGO. Here are a few of the objectives of pixelTANGO:
- pixelTANGO (aka pt) is a set of abstractions and externals, for pd/GEM, that make using pd and GEM easier, faster and more satisfying.
- The purpose of pt is to balance usability and ease of learning with programmability, modularity and flexibility.
- This balance means that pt will always be playing catch-up to build easy to use interfaces to the ever growing and complex functionality of GEM.
- This means that often pixelTANGO will be used with "traditional" pd/Gem programming for and by artists to create performances as well as contribute more specialized pt modules back to the community.
- Make pd/Gem more accessible to artists by increasing the ease of use and making a more shallow learning curve
- Keep the modular nature of pd/Gem intact
- Ability to use full resolution DV videos, live, recorded and streamed over IP.
- Artist can work in 2D and 3D or both
- External control of pt through MIDI, OSC and custom hardware (Via AID*1)
- Community supported and developed
Exitsing features of pixelTANGO are:
- Easy two file drag and drop installation (on OSX)
- Complete documentation
- DV over firewire, network streams (QTL or SDP), still images and movie files as inputs.
- Number of layers only limited by available hardware
- Filters for layers with plug-in architecture
- OpenGL effects for layers (rotate/scale/translate etc..)
- Text & 3D model layers
- Configurable smooth interpolation on all parameters
- Preset (state) saving and preset animation
- Quick access to directories of files
What are the objectives/features of V3?
How do you see the projects connecting/merging?
Things like BPM sync etc.. have been requested for pixelTANGO but I have little personal interest in them. Also I think pixelTANGO has a more unified design that acts more like an application than a patch. For example there is a plugin system that dynamically generates an array of abstractions in the "fx/" folder and manages the seamless routing between them. V3 effects could be added to this perhaps. PDP too for that matter. (these are pix_ based effects) Also I want to build something similar for transitions that I think its a strong-point of V3.
What benifits do you think there are to merging the projects?
What do you think of things like PiDiP/PDP integration?
Did you see the Article in La Presse on friday the 11th on the TOT project?
Anyhow I'd love to hear your thoughts on the matter.
Oh and fwish looks pretty amazing, how did you get the alpha-channel working well? (multiimage, or alpha video? or? The OSX developers have broken pix_mask and don't see it being valuable! yuck!)
b>
Thomas Ouellet Fredericks wrote:
Here are videos (screen captures, not yet the actual installation) and part of the code of my Fwish (Bassin du destion) installation. One version has fish that do not collide, the other does not because I decided it is nicer when the fish overlap.
http://www.danslchamp.org/mrtof/code.htm
tom tom@danslchamp.org
On Tue, 15 Mar 2005 18:30:41 +0100, Frank Barknecht fbar@footils.org wrote:
Hallo Nicolas, Nicolas Montgermont hat gesagt: // Nicolas Montgermont wrote:
I've been experimenting pmpd with datastructure for a week now,
Wow! That's quite a patch for one week, wonderful!!
and I encounter a few problems that are all present in the attached patch:
- Computation speed! The simple model presented here (5 mass, 8
link) seems to charge all my CPU at a metro period of 100ms. The string patch designed by Frank Barknecht in the datastructure tutorial was much more faster. Does anybody see any "bad" programming in the patch?
I also get a very high load. I will need a bit time to take a deeper look, but generally the data structures are far from the efficiency that e.g. Gem has. However I don't think your model should be that slow.
- use the $0 variable to have mutiple instanciation, but I have to
use the external "sprintf" to build the "pd-$0-data" message. Is there a solution using only native pd objects to do that?
Yes, and it even works better here (maybe I have another sprintf, I get lots of errors like "sprintf: no method for float").
Anyway the solution is to replace every "sprintf" with "makefilename", you can keep the "pd-%d-data" part, it's the same for makefilename.
Ciao
Frank Barknecht _ ______footils.org__
_ __latest track: "scans" _ http://footils.org/cms/show/41
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://iem.at/cgi-bin/mailman/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://iem.at/cgi-bin/mailman/listinfo/pd-list
Can your pd read the following video? I made it with the animation codec. Thanks for all the help!
Tom
On Wed, 16 Mar 2005 14:43:35 -0500, Thomas Ouellet Fredericks iamonthebeach@gmail.com wrote:
Ok. You did not have cylcone loaded so you were using another gate object, so I replaced it with demux (its better and from zexy). The new version (once I know in what format to convert the videos) should work, I am uploading it now.
www.danslchamp.org/mrtof/code.htm
Tom
On Wed, 16 Mar 2005 14:11:23 -0500, Thomas Ouellet Fredericks iamonthebeach@gmail.com wrote:
I would have liked to see your demo at the SAT but I got held up at work. I am less interested in VJing lately, so the next version of V3 will mostly be oriented towards installation work on integration into other complete packages (like pixelTANGO). I would like to merge the projects because I do not wish to further the development of V3 but I do not want it go to waste ( I put a lot of math in there!).
The next version will only have 3 parts to it :
- a multiple video file player (in XP, gem crashes when you switch
videofiles, so I need to create a new instance of pix_movie for every video). 2) a "breakable" video surface that will be composed of a dynamic number of objects. I have also created a messaging system to give CUES to the 3d objects (like go to point A in 5 seconds then go to point B while rotating x degrees then scaling big in 1 second). 3) a gemwindow manager thingy.
What is done :
- video player (just need to add multiple video file support) with
many options (loop points and frame number and variable speed playback, etc) 2) I have made my own state saving mechanism : I never got memento to work for me. 3) The breakable window thingy is almost complete.
How I imagine it could connect to pixelTANGO :
v3 vidplayer (v3.vid)) -> pixelTANGO -> v3 breakable surface (v3.surface) -> geo
Off topic : does gemkeyboard and gemouse work in OS X?
Tom
On Wed, 16 Mar 2005 12:52:52 -0500, B. Bogart ben@ekran.org wrote:
Hey Tom,
I spoke to Patrick a bit at the SAT on thursday. We were talking about how it could be possible to merge V3 with pixelTANGO. Here are a few of the objectives of pixelTANGO:
- pixelTANGO (aka pt) is a set of abstractions and externals, for pd/GEM, that make using pd and GEM easier, faster and more satisfying.
- The purpose of pt is to balance usability and ease of learning with programmability, modularity and flexibility.
- This balance means that pt will always be playing catch-up to build easy to use interfaces to the ever growing and complex functionality of GEM.
- This means that often pixelTANGO will be used with "traditional" pd/Gem programming for and by artists to create performances as well as contribute more specialized pt modules back to the community.
- Make pd/Gem more accessible to artists by increasing the ease of use and making a more shallow learning curve
- Keep the modular nature of pd/Gem intact
- Ability to use full resolution DV videos, live, recorded and streamed over IP.
- Artist can work in 2D and 3D or both
- External control of pt through MIDI, OSC and custom hardware (Via AID*1)
- Community supported and developed
Exitsing features of pixelTANGO are:
- Easy two file drag and drop installation (on OSX)
- Complete documentation
- DV over firewire, network streams (QTL or SDP), still images and movie files as inputs.
- Number of layers only limited by available hardware
- Filters for layers with plug-in architecture
- OpenGL effects for layers (rotate/scale/translate etc..)
- Text & 3D model layers
- Configurable smooth interpolation on all parameters
- Preset (state) saving and preset animation
- Quick access to directories of files
What are the objectives/features of V3?
How do you see the projects connecting/merging?
Things like BPM sync etc.. have been requested for pixelTANGO but I have little personal interest in them. Also I think pixelTANGO has a more unified design that acts more like an application than a patch. For example there is a plugin system that dynamically generates an array of abstractions in the "fx/" folder and manages the seamless routing between them. V3 effects could be added to this perhaps. PDP too for that matter. (these are pix_ based effects) Also I want to build something similar for transitions that I think its a strong-point of V3.
What benifits do you think there are to merging the projects?
What do you think of things like PiDiP/PDP integration?
Did you see the Article in La Presse on friday the 11th on the TOT project?
Anyhow I'd love to hear your thoughts on the matter.
Oh and fwish looks pretty amazing, how did you get the alpha-channel working well? (multiimage, or alpha video? or? The OSX developers have broken pix_mask and don't see it being valuable! yuck!)
b>
Thomas Ouellet Fredericks wrote:
Here are videos (screen captures, not yet the actual installation) and part of the code of my Fwish (Bassin du destion) installation. One version has fish that do not collide, the other does not because I decided it is nicer when the fish overlap.
http://www.danslchamp.org/mrtof/code.htm
tom tom@danslchamp.org
On Tue, 15 Mar 2005 18:30:41 +0100, Frank Barknecht fbar@footils.org wrote:
Hallo Nicolas, Nicolas Montgermont hat gesagt: // Nicolas Montgermont wrote:
I've been experimenting pmpd with datastructure for a week now,
Wow! That's quite a patch for one week, wonderful!!
and I encounter a few problems that are all present in the attached patch:
- Computation speed! The simple model presented here (5 mass, 8
link) seems to charge all my CPU at a metro period of 100ms. The string patch designed by Frank Barknecht in the datastructure tutorial was much more faster. Does anybody see any "bad" programming in the patch?
I also get a very high load. I will need a bit time to take a deeper look, but generally the data structures are far from the efficiency that e.g. Gem has. However I don't think your model should be that slow.
- use the $0 variable to have mutiple instanciation, but I have to
use the external "sprintf" to build the "pd-$0-data" message. Is there a solution using only native pd objects to do that?
Yes, and it even works better here (maybe I have another sprintf, I get lots of errors like "sprintf: no method for float").
Anyway the solution is to replace every "sprintf" with "makefilename", you can keep the "pd-%d-data" part, it's the same for makefilename.
Ciao
Frank Barknecht _ ______footils.org__
_ __latest track: "scans" _ http://footils.org/cms/show/41
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://iem.at/cgi-bin/mailman/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://iem.at/cgi-bin/mailman/listinfo/pd-list
Hallo, Thomas Ouellet Fredericks hat gesagt: // Thomas Ouellet Fredericks wrote:
Ok. You did not have cylcone loaded so you were using another gate object, so I replaced it with demux (its better and from zexy). The new version (once I know in what format to convert the videos) should work
Apart from the videos it is working now. There was one [gate] still in fish2.pd, which clashed with gate in iem - I disabled loading of iem to make it work here.
I have no idea, why the videos don't work here. Maybe I should recompile Gem because some library is missing. I also couldn't the other video you sent me.
Ciao
Frank Barknecht _ ______footils.org__
_ __latest track: "scans" _ http://footils.org/cms/show/41
-
Frank Barknecht -
Thomas Ouellet Fredericks