Re: [GEM-dev] GEM-dev Digest, Vol 78, Issue 4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2014-02-28 01:02, me.grimm wrote: videos were being loaded but I couldn't see if anything was happening yeah i compiled your code with the same outcome just so you are aware. just to make sure i understood this correctly: the problem of not seeing anything is related to videoAVFoundation not being ready yet, and not to some obscure issue with the window handling, right? i mean: you *do* see a white rectangle, and when you compile the videoTEST plugin, it does create noise? fgadmrs IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJTFennAAoJELZQGcR/ejb4+NIP/if/q9G0t6Bp0sewA/66k9oW OX3VtIVA/dPvS47UI88aa3IztZg3zn7HcaRvl+R5NgX1SJGBxj+f8fuSkQDIYm4h lg1UP+te6mJbtmnR+lUIgYEnXeNNJC+Bv7M2omwXWYEhAXRDXefcdv5iab9AGsFy YLG8Z7EzjXJHfE44+YRigwI7B+apy6cWTePLi529SJQekeL4On8e+nnp2xGanzwh g4cqLXrV3/LNWKLWzJ/+I2LnrTmuCx871P1TMedXZK35DZaXgGMg8UzHAQqXlWDy Ph6B06lWRr4UxqvMdtx+pQDiTpJpmwaMevaFRZoeebg3oGarjSWdr/4TB6JYq973 UcdRcqHASQ05Poms6MMSc8oQG4wNa32/gVhsd8YiwTm65tqU5w+ssaXG9cYhKlMk ZLbcnBGu/w/54mv6weVZ4ntXc8qAHz65HoMF1gz0leZunT+TEa1axeT8pDWdqfSM X1wn9YnVXd9vTBF6lluVqZD+VhboTp8etx9WUAlhUT9czXXVxAtYtilDZ/hdDMrp 2mO+d652ArrJX53qF67dxJR2t65hOHmT2gobK4zFt+I/s7UFjcIoW1hceQHnDfWZ qVWlCu2EFknpYGBXqTUsbpACwxFmBz48NtxR2XSDQaVrwnDWlTG9PgdKU9vWLuBS odVjHafa1DHlYbOKgXtM =VWRS -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] AVFoundation status
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2014-02-26 15:27, Dan Wilcox wrote: Well, that was just a hack to make sure the Carbon framework wasn't being pulled in. I realize now I could just do ./configure --without-quicktime. That was one of the aforementioned hacks I wanted to clean up before pushing. I pushed when you requested and now I get a note about the very thing I didn't want to push :P Trust me, it won't be like that in the final commit. no problem. i did not want to sound grumpy, esp. since i'm really thankful that you do that! but then, i just wanted to express what i think is good practice for committing before it's *way* too late. fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJTDfp3AAoJELZQGcR/ejb4yJ0P/jXUYHEr3PShYqWpoonDCWbW 42lEYlZHBFDuc84X3eqUp+mWd3Qra4X/Fa8UBXAdYwrKmrJcdvMSL6B0A9vw66TQ rkQFFd9ADDuzB0TL11P+xHgwLy5iliB+MwYow3hh5BzPMR2U2VbCK5UoSb8aMn7j pkt55AHPXOacOC/G9uXC8WqMSqPLdeIAmLFTZUTmk55eOcTK39yU0WrlwxFkRpOd uQ+u31evCenWwvsD7n4h3qVy1G5fCj1FxieIF26eaYrGYgfyaSRA01lo+GyDihJW Eqt95artYbNQ0nFPkBW1L8rIojB5ElVXfzKX/t3gqivcAhR3ng9IMfNPtoJLq2ef 9vzQ2MznQ9tEAOc7PRZiJL2L5w0XqGw+CvochnOtt6D5tusKxMwiWw+qYUqAVYfc rgRnD83r+aLoTLm0t6ND1p+sA6AsrKMBaIAz+Y7+C33kAmDUi6ZUO4bilLWZ/gK9 1k3wO4YSd4D6cMrGDcCHhk08HOBDg+gV9lSVGXslrbJ6gRVad1RPbGgrh30bgq9F 9TyteZhko7xyzyyM3M3dID675lglEYbvv+MvvcDNbpWyjhLsCl7r5QH71CtHYnLN asBHrFvxpRlr/cwEVXhq5YkxKJJYZQAhb+Q2ZlT50Rp6aV6MvWFvM1ZDCeBhe16W a46FEBfa4hPOwE6WURWP =CPqt -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] AVFoundation status
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2014-02-24 15:58, Dan Wilcox wrote: I've updated the build system to handle the ObjC files and it appears to be working, although I did some quick hacks to remove the quicktime checking so I'll need to clean that up before I push nay of the code to Github. please do not hesitate to push now (and create a pull-request whenever you feel it's ready). i've seen so many good code lost, because people just forgot to put unfinished code online and then never came back to it. fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJTDHTQAAoJELZQGcR/ejb4ysQP/A+VuwX9MN2GsW/mK+qbEYBp KzN5LZXmo0xa2cS/KIvdcNTK5rpqlekI2wc3xIcUQ1X4HhcCsjM5X2r+ifaMgD/j 6RwU8fFFjFPk3L6f/oHuWNh5+3TlcUpyjr3uOXJtknbKi/UAg8hqyjIOf7ZqbS9F lDwILB2GYXNZw0XbdsX6pmXGAj5Ql6kZXXSpahDCnAwTJqO+6kcCwzA+63IEWHZI S5fCKkO8538F//Nlva4KlmHVw8FVJyo9gB/EaNmHUzw6fvwIOPyhSau3/HEaizcH p+no01ipuuZnPkr8/cJsFWDY67XjZAcu0dQ2SDQS0hPppVt48a0Zdwepo3oKqoLT Q6bExNj3yhVOl4wHl5HDS6IOqIDI5bXgMjsat6degAPQAvESDQncH/BiIM59JHiI EomoAp+GA2jruWMVE3TGTH4GUw2uDS7llM4ide389P2JWJyTIVZakPt9A+hbdhz4 tQm0US4l7Yjvd0eU/pHZw2MGkMqed0BHgzhNfFUkAOaL0waLKlZ2pB6/R5Z45hyd JWhG2mVbv7/b3EmVHxPhkUaVYxA3bl1WIlOX6dBpGwzrzMx2z/HyhC8VcI21/Jpm zMcPjcNjQ2icspGTGewTsVTwRvJsqho8X4Sa85O+5RDNT3JRlZ5IYxtI+OQp0HS2 DiGpG8SuG6S/d8/0MMiR =l/tf -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] AVFoundation status
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2014-02-25 17:40, Dan Wilcox wrote: ok. I've pushed to my fork on Github and made a PR so you can see the changes as I Commit them. cool, thanks a lot. btw, is it intentional that you have disabled quicktime4linux support in your updated configure.ac? i would highly appreciate to put code that potentially effects others (e.g. the linux port) into separate commits. this includes all files outside plugins/*AVFoundation/ (namely configure.ac, Makefile.am,...) i'm surprised how fast your proceed. very nice :-) fgmadsr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJTDM3QAAoJELZQGcR/ejb4se0QAJYqdo2RgQt8c/DdXrMCrA/w klgznd4RrDmcwPVg55ytmnZtfQ5LzEKx6c/UjBX5WHidLWstbJLqsSv0lnYxB6hI xsQfgVGbO7573s2Ky4BObDLgC/tkRS0hrGQYH2C7v2pDCd3VLV46CoMpT9iid1pM i1J0Wak1OZxl7wNTbAyTIJv/uq8by/6sTJe6xmoJP2FIeclE5mFIj3evjbs1+1jF NWdVTok6I8TKxR5Nm4g69Dh9jVmko/5BwHwaT3HieWGgFE8kyabXg2zK9RDueAJn MdqVjPsJWBk4PduyZLE57RyXW55mwYuSF1Ku32kJ4BHsskgHqThM/cwGG5F4IiNj JDrfzAAlX/IRAUxwZFEDEHM6qHWRnqW58amKDY1JwYm85gI5y/T+nzTKpcwz7UQU Xbckry6epKHYaF7nMnn318CR/hdt/tS8CjHukLJixAEKXKkzlavml3Le75d9NOn7 uq6vRL3LBE5cdWNfFsuSMO/4oP7Zh9iFqZbDfg+GTUMUPGPUeH5ssSX72u6C6Vfg zEYDGyMHzoQAgkGlR68r7CcR0D5sv5Y0whw1Z58IAdngJMWq2P9ZWn5xsbKzBZsX WSevaUw4YytGa3WIFRSjr60KtDsfh9X8RzKjeSdeR35rW4w7n7J+MJb0cPYjehOw O9Yut0uf+lL/AT/vx0qH =h3Er -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] Mipmap Pix_Texture - Compile error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2014-01-11 21:47, j-p wrote: I'm trying to compile the latest Gem to use the mipmap code from this if you refer to the git-version: that already has Claude's patch included. mfgadr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJS08NXAAoJELZQGcR/ejb4BVAP/iPplnicmBjPR3BtaB2RI7uo Pp0nJ3odfnk8lqbt6K20aEZBkvbF7m8R4xPGjL02SgKoOGMiSy2ncHWgtr1vyt5n peQTLD+OZ+wVJ+DmMfu3IoAWpcJ4o8jQOXHpwF7ZuWddVQBmtw9Nygo5lv/fnNxy e84QysvR7iCjBkSunT191a6GYOhbtu5lXvkI+8PmJvsmEzy3gvTEQLeejQ93DUOB 9Ds27udGqtGS0cMgeq8KEBtAw/Ps8GkMBX8YcHqphQhfizwS/klLKxEOaanGKCOt vGVahfDfc9VUkSYGrW6q4jOrp8cVeIrEVjjMm06W2TI+h+JqKu6q9Vne+hSDyt7i /24wqOMHgg2NGtxMep5v0Mji+7R4TUZmcSLekdNUNud2gDZ9frD6YwzF4/oR5Qdn Knjh2px5VRSYETbuYVUeswCOyj2FAcTmfv7CvgxGMffbIap2VgvefKcg1Vo9oLY9 ktDz+Ln6GNzNH2qQy3InvwYiQz5NQ1zXNRGBGIvzRdZ5ey76fNPl+lvXsVNRb4AU MO6dx/FuYhF0iMtrmyaaFDwongPo++5esKH/Qad9u5HH21zgMIJno6dpsqE0QYyj +60ZYroEaB7gu4Wkx0TVXCt9IhlTxIROFtLH+69w7mCq0XymvGvX2VgyrhETpzvC 9PD417EUzrtgoBKoW2Fc =NR+t -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] GEM for Windows build on Microsoft Visual C++
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2014-01-08 21:57, Antoine Villeret wrote: hello, windows_stuff is the branch where I put what I've done. ok, thanks. i've manually merged in this branch (completely leaving out the build\win-vc2010e\ folder). i've also excluded the PDF and it's ODT and instead converted it into a wiki-page [1]mainly because i prefer having text as text rather than 2 binary blobs. fgamsdr IOhannes [1] https://github.com/umlaeute/Gem/wiki/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJSzqXJAAoJELZQGcR/ejb4Wx0P/2jt+Q/yuMckd4ts8N9Go/jt 4M0zIap285idu36JBZGUnLjyf7KMY4CIbfJJtImb7JhreZ2qclO/bDKKS5sssbDC zwphJMaIHll4gvyo4lL2UlY+mns/nVZCSd3eeyJwTWUT8eexaRI0+8GGypGBxfWP F+UeX4luQVBCEz51+h8jyt6xaIhiSR0QzZ/QmG2+7LouPEXCBQkYsyBNpe7tGeGU J0YCX80rQprQWpufCdN8JUMGAgM05fr2+COHrDfc7fVBBkp0jV+UZcTJGjvny4vJ C6Ig7IGuAwa7W4KsHY1RSALq3nOIpII99b+He6/68L+pTr8PFc1bTDq1DcBB98/e zRpAVaDjS/SXxdk4sod+ic7XEXZiD1hc7KRGIlqSjwsa2pfdWebu3vi9K2+esFo4 sUdOLUkYN+OlndK1MBlEvDioFGv2g4yxhAJa/A3rjUBE2aRpBcfuW1KolvXPoMJt 0fTAWiJrKffxX5zGKbVdAiTZoyYjDIzAlfz//OQMxFEK8sKY/ylubYNILaWniJrS qLvQV9cuXzLVu2/zFM2ZumYHkupU0bOQ+W+JWftGHfw1rCO2TqsXwXHf/Vr7r6Lc ytiqMFG/RB/CuPYHGIP15mdtG2mouowSslMpGNhdQNgEePW4nSzBLmKLkI1/ISeR 0BhHnlZYaJ90KUJNGnEu =r5Il -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] GEM for Windows build on Microsoft Visual C++
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2013-12-13 11:04, Antoine Villeret wrote: hi, I'm sorry, I can't build working plugins DLL on Windows. too bad. in any case, i'd like to include your attempts for future reference. which one is the correct branch? vce2010 or windows_stuff? fgsmdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJSzCZeAAoJELZQGcR/ejb4el0P/AwTix5wut+PQdFaAD7H8TwT fbEynHIlD6xpBsmRX3NFOWIYYbU7ktc2I+GIsVLH2jrWzUdPwhF8qxc32rfiQvbb TSnzdBQ9YoLvN+/m7fU842H9NRwmqNIhA5wtHpVtj5o53VGe5DwoGy5eei7W8IQJ Bq6Q127pxkYrhm1ygrMN+XLTWTHB6scD2y7Vz+YyTMKjCcpYabEPzC0G0SkesT/v e0HCzghQ0tbOpD29XYeJQkt5OYKH1MYYP74JLs+BvyHxF9J59SoYNbePggsmY9gE TO8Jw8E5/26PCoPY6SuEhc1AdBo+ZDqKcGxS5Uaq1qb+XYjf3LMNnFPOGuCrhr/R Wi4RxEkZQt9M/VefDn8DM4O9CRnW7p3D5GTOVCV5ueNeZWfc/wKJtq1BG8TJG9xJ hndmqIH5fz3p8f5hmlnB1rCW+z3ElwLwrwlkI89k38i91h2usZrozr4Yn9IoTBSQ cR3F35hrQtBlCNByk92k7HfOyUBxSHNPlhw9/R1hfkCpt/D1q6BfXeNZ0qz3ICIC yBj4VBZtCr5jNFLllWiQSsobJrF7k5/a9mQ5Jf4yPEn2Mle2KYLrJ6Ie2LAtZjYE HOAphs/rogvzLee6b9RTHVO66rbVCTWiKtvDUYuhfbgs1CKftkbpWRvOp9Pm/wQx wuNMIgWNanTPlXYZFtnY =z4Yb -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] [pix_imageInPlace] expansion
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2013-12-12 04:35, j-p wrote: Hi, are there any future plans to write more straight-to-texture-ram objects like pix_imageInPlace? no not currently. i do have plans however for a replacement for [pix_imageInPlace] and [pix_multiimage] using [pix_buffer]. probably an object that uploads an entire [pix_buffer] to textures. and another question - is there currently a way to convert a raw list of numbers into an image, as a pix_set object does, but store it in a buffer along with other images? [pix_set]+[pix_buffer]? gasdmr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJSqXfLAAoJELZQGcR/ejb4aXMP/iDNygn1t2Ap66eTsE6gzfJn 5l+xCbAVwHeTl2Pt0OS4iXNIQTFGMZD41pa6a9FQos3Vsy0JGpAtlCh1daixGWpl /6A/v1RofBBOyoPm2N7tR0i6i6h1AZ8Zx1MAHEDJ0m1GL8Z3HQjTgaOAy5w0M/W7 0oTpcdOK5Vr1NInWJz4naDwXAHGsJc9xzj0Vid8PSPvMCPHRIY85ewnfsZ77xX86 UDd6jhAIAzTHDuzbgPT89YCxzCz3P7j+SOdv06oa3WgnO1jH5C7/PBLd56rfkiVV y64990/SwYC+eSzeZle2MaME52XAjAzw9OuYWWJpm8MnCqYOaNqYo4hQMxfIxmrY n7mqejbHV4j7QxMnEwNQc6dH6i3/le6Fi6jZL4spGBSCEzra9dHSFBHtjXw8qpSG WWJxN9A8E/5w8lge3fVXNyfUpUQxBoqNj0PmFuMKRRyYmh9gzqMUVX9By+gUCfWf wzFmoM9Nj5R07F180kB91CNo1O800Hhk78PBWKUbCUDhUCETQoyo+f9Q6Yi+9ONL Rjky7NY7ehY/oWR/Chvo7MNYxoheJ4z6OlsyPKoYfzgG4YhWY8okYp/2BkxLIg4I x94dpMYSo/ZDTh0JyVGF5yyaZftxN/Yes9UdIGH9jiRvyVzB5cGv1uG18Rfphv31 YPIRPwBonAJ11Mq22aGE =Yz9B -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] GEM for Windows build on Microsoft Visual C++
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2013-11-04 14:20, Antoine Villeret wrote: Hi, I built GEM on Windows with Visual C++ 2010 Express under Windows 7. I made a how-to pdf with a step-by-step. this is very welcome.?! I have a working Gem.dll and several extras. cool. I managed to build filmDS by making some changes in the code (adding a lacking qedit.h and changing #include order) but this could have broken other builds. hmm, weird (i mean: why does it work on the original build?) I also have a question concerning Gem's dependencies. I need to put some dll (freetype6.dll, ftgl.dll, pthreadVC2.dll and zlib/dll) beside Gem.dll. iirc, i build a static library of FTGL and link to that. this should fix the freetype6.dll/ftgl.dll issue (maybe zlib.dll as well). as for pthreadVC2.dll: isn't this shipped with Pd-vanilla? I build Gem mainly to be able to build pix_opencv on Windows and I don't try IT a lot. So if somebody have time to test this on Windows, I'll be happy to make an archive with binaries. For now, there is a new folder under the build\ folder in my github Gem/vce2010 branch. https://github.com/avilleret/Gem.git thanks. fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJSd6KLAAoJELZQGcR/ejb4pOkP/3CT1dwl0FcXgB7XRqQZIZ/C F2lVyEBeuEqjF20dOUHqqGvVUofn4lk3HlXSTxRa3vP58K10yru5cf3IQGHsiktw qkNu3tradDqKVG5N8rEEbe9BoeDY6niVM1m/GDq93JGMconALGXKX0e07Oc2YseM WpYwKNincp09YnzOlOsUekEbt3Sp0pAhqd1MIP98s7tvOxf3cmHd0jWUtG10F2My VVCslSy4A7eEi2fFNlCD20aKdBFdvbt6gkbb5VT8aPLiesBvppFlr9dK3HdvaCH3 OIkMjMgOnUdQCyXS1eBQ3HJ9xQXWwEc3HxR/AYsk5ibAy+xb2uP1GG3u5HOVZQ1e 9u225ubnHSuQ7OkbILfBiZSdZtnWnhGY9jzQswiURKPyDxnT19YYj/2US2ilOmpO oBH8BewPWzX4tNsttu/DqbZJREj3pUiZlQz9t9xtp2GFgIK2B7E/qB+VXS6HgZVC SqXZGZ9Ms1KdyVkuzuDt9Af13B8KOnjGWq+rsUzu+dr0PPrQSTScwCwehhceSNtY yrHsXMtJkD8mvsZiGp0f2QFN0N3/oNCpQ0gRuflqA15BGjMQn6/4UNFkLl1ja2XO M67+U2VAvKbw1VBkVX7gKgyVzc1BpdFQ7Mb8fTCriW7ARo3Rtv7BCDsxH8P516+o Y2KHWwXIeNdC+BgHANex =eW2b -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] Building Gem with MinGW
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-09-12 09:05, Antoine Villeret wrote: hi, I tried to build Gem under Windows 7 with MinGW. cool. last time i tried, i *could* successfully compile Gem on w7/mingw. i'll have a look into your problem asap. in any case, there is a substential problem with the MinGW build, and that is that all the Direct* plugins will *not* work. that is: no DirectShow video and movie sources. the rest *should* work just fine. fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlIxbNQACgkQkX2Xpv6ydvRlfACg7fbMx3YiUAK6Cv76iYjJZ1Xw RrEAn2DzcM0zBolscgpaMv4/Bv2l3oL3 =fvN1 -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] Oculus Rift distortion/support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-09-12 10:11, Antoine Villeret wrote: so after converting all the .vert and .frag files to UNIX line ending, it works (!!?? windows donesn't understand itself ???) unfortunately a Gem bug. i think it has been fixed a while ago. it probably IS time to do a release :-) fgmasdf IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlIxnvAACgkQkX2Xpv6ydvTpXwCgine/GeKbngY5UGVEQ7vOB5m/ 7AkAoJXEGx2OR9+PYYsr0oCJq2Tn0Bsr =EmLO -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] Building Gem with MinGW
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-09-12 16:24, Antoine Villeret wrote: hi, I found a workaround by putting the allocation in a #ifndef _WIN32 statement pthread_t is a structure under windows and not only a 64bit int. with pd-vanilla I got : C:\\MinGW\\msys\\1.0\\home\\antoine\\pd\\pd-vanilla\\extra\\Gem\\Gem.dll: couldn't load Gem: can't load library on startup... maybe because pd was build using microsoft compiler and Gem with MinGW no, this shouldn't be a problem. C-binaries are compatible between different compilers, C++-binaries are not. Pd only has a C-interface, so there shouldn't be a problem. otoh, Gem's plugins are all C++, that's the reason why Direct*-plugins don't work with a mingw build. I also managed to produce a Gem.dll form Microsoft Visual C++ 2010 Express and this time Gem loads in pd-vanilla 0.45.2 and it seems to work ! cool. but i am wondering if i am doing right : Gem claims that some dll are missing and I added them directly to the Windows\System32 folder should I include them in the Visual Project instead ? you should be able to put them besides Gem.dll. if that doesn't work, put them besides pd.exe. Windows\System32 is a *bad* place. fgvmadsr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlIx0A0ACgkQkX2Xpv6ydvR0uwCeLvnnsxTl4LNbFl1J21LvEXDi iuoAoOpCirT4B/O4x5AV+gleUUauXwNT =IRvg -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] help with glsl abstractions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-09-02 12:41, Nicolas Montgermont wrote: Le 01/09/13 11:31, Jack a écrit : number of texunit available is return by GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS. Here on Intel HD 4000, GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS is 32. And on NVidia GTX660M is 160. Mmmm, here creating [GLdefine GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS] and banging it gives: 35661... did I miss something obvious? yes. GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS is a label, that can be used to query the maximum number of combined texture image units. it is not the number itself. you have to use it with glGet() in order to query the result. [gemhead] | [GEMglGetIntegerv GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS] | [ \ btw, this gives 20 on my old and trusted GeForce 7800 GTX. fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlIkvhgACgkQkX2Xpv6ydvT/oACdF9tgeTBP2eq/ORF9M1K1bVPe WzAAoKcfs4acrWskoiMGR0wwstJP28c9 =lo6L -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] help with glsl abstractions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-08-30 18:14, Jack wrote: I am totaly beginner in git/repository. aye, git has a somewhat steep learning curve. for a programmer i think it is worth it. IOhannes tell me to fork the Gem repo and to make a pull-request via Github. I don't know how to do that for now, so I will do it soon... - - go to http://github.com/ and get yourself an account (e.g. rybn), then log in. - - go to http://github.com/umlaeute/Gem, and click on the Fork button in the upper-right corner. - - this will fork the repository into http://github.com/rybn/Gem, go there and follow the instructions to clone the repository to your local machine. - - do work (add new abstractions/,...) and commit them to your local copy - - push them to github - - go back to http://github.com/rybn/Gem and click on Pull Request and follow the instructions there. - - i will get a notification that i should merge in your changes and can do so (after reviewing them) fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlIkwI4ACgkQkX2Xpv6ydvTQ3wCfTE7H2qqYhKxjf+Am+MrKVCUs zRkAn2qX0Qc+eWPICgM5tQzMqG1EidVB =weC/ -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] [PD] multiblob tracking in Gem while objects keep their IDs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (moving the post to gem-dev) On 2013-06-16 19:58, Max wrote: Now that it's clarified that this is a bug, not a feature. It should be evaluated why it behaves differently and if it is worth it to keep the changes or we can go back to the original. yes. i haven#t fully reviewed the new algorithm, but the main motivation (for me to include it) was that it supports a dynamic number of blobs (rather than a fixed maximum number). i think that *this* behaviour is desirable and i don't really see how it would break compatibility. (and if it does break compatibility, i think that it can easily be fixed: e.g. by explicitely specifying a maximum-number-of-blobs (using the argument) it will become static/fixed, and if you don't specify no number it is dynamic). the other thing is how blobs are detected. here there might be some incompatibility, which ought to be investigated and fixed. What can i do, to help fixing it? I didn't quite understand what you meant at the IRC. isolating the problem to a static patch (static in the sense that it doesn't require any moving images), so we can do: if i feed imageA into the object, the old version will output blob1@x1,y1 blob2@x2,y2 whereas the new one will output blob1@x1,y1 blob2@x3,y3 blob3@x4,y4 finally, we have to make sure that the problem is not simply related to a wrong output order. e.g. do the downstream algorithms (in Bewegungsmelder) assume that the (upstream) blob-labels are ordered from top-left to bottom-right? Maybe ricoardo can tell us more about the changes? If the changes are worth to keep but can't be compatible to the original i see two options: 1. make ricardos version pix_multiblob2 anything but this name! personally i do have the bad habit of using version numbers in object names ([pix_texture2], [pix_movement2]) but i always regretted it (even though [pix_texture2] is somehow related to (non) power-of-two textures (hence the '2'), and [pix_movement2] is something like a 2nd order [pix_movement]). 2. send a message (and second argument) to pix_multiblob to set it to the alternative (ricardos) mode. hmm.. i always wanted to add a 2nd argument / mode-message to change the output format from the current iemmatrix mode to a more pd-ish format (a number of lists). i'm a bit afraid of having too many options for anybody to be able to handle. but yes, basically these are the two ways how to proceed if the two algorithms cannot be made compatible. (and i only wrote down my concerns so we can circumvent them) fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlG+u5IACgkQkX2Xpv6ydvTJVQCgvEsu+n5z/RJ67lMgMWlK2ykB ZiIAn37sRWYAIBbRo5g8nvxrcFqyyVWn =Sy5e -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] video with alpha in Gem?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-05-28 12:47, Patrice Colet wrote: I've tried gem-git on ubuntu precise with gmerlin and then rbga videos crashes when changing frame in pix_film indeed. i'm afraid that i have to confirm the bug. i'm not sure yet, whether the problem is in Gem or in gmerlin. fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlGltKgACgkQkX2Xpv6ydvTbZgCfUE7PHimVkJXdrNpCzKbWnpQs Mq4AoOvFGmrPdd8w+B4+/f4ehDCK2Q9l =8oTC -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] model bug: ignores normals in obj file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-03-26 19:33, Claude Heiland-Allen wrote:
Hi,
diff --git a/plugins/modelOBJ/modelOBJ.cpp
b/plugins/modelOBJ/modelOBJ.cpp index 4ff9d9e..be79716 100644 ---
a/plugins/modelOBJ/modelOBJ.cpp +++
b/plugins/modelOBJ/modelOBJ.cpp @@ -63,11 +63,13 @@ bool modelOBJ
:: open(const std::stringname, const gem::Pro
glmFacetNormals (m_model);
+/* gem::Properties props=requestprops;
if(gem::Properties::UNSET==requestprops.type(smooth)) {
props.set(smooth, 0.5); } setProperties(props); +*/
this does a bit too much, as it effectively disables smooth (and
other properties even if they *are* set).
i've just pushed a changeset, that will only try to automatically
smooth if the model doesn't yet contain normals.
i hope this is backwards compatible.
fgamsdr
IOhannes
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlFStEEACgkQkX2Xpv6ydvTIYACg97XO3qSu2KIDWQRY9veQ+LOY
utQAoI46gd9z1TnA9JkLqtQTEQvnuBS8
=w50S
-END PGP SIGNATURE-
___
GEM-dev mailing list
GEM-dev@iem.at
http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] upgrading Gem's sourceforge project
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-01-17 16:58, IOhannes m zmoelnig wrote: hi all, i'm currently thinking of upgrading the pd-gem project on sourceforge, since sf seems to want drop support for the older system on the long run (and i'd prefer to do it while i can choose when to do it). so i've initiated an upgrade of the pd-gem project *just now*. in the meantime, i have pulled all recent changes (there aren't so many anyhow), to my github account. fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlFIiksACgkQkX2Xpv6ydvRMSACg0qXUFqvZ3aFwzuZa8NV6Rs2S tlAAoOccBs5cLPx5V5LOCPSdqg/STkwQ =0spb -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] pix_share_write error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-03-19 16:06, Antoine Villeret wrote: this is in my github repos in the branch pix_share_write : https://github.com/avilleret/Gem/tree/pix_share_write hehe, i have incorporated your changes about 7 hours ago :-) I don't know if it's a good idea but it seems to work for me generally, i find it always pleasing, if an error is not (only) printed to the pd-console but you get some message back into the patch, so you can react on the error programmatically. I'm wondering if it could be good to have a dictionary instead of a hash table : when we use [set id sizex sizey pixel_format( message, pix_share* could try to find the id in the dictionary if there is no entry with that id, it generates a random shmem id, verify that nobody else is using it and tries to allocated data if it fails it could generates another id until it succeed and store the id in the dictionary pix_share_read will know the dictionary and can find the right shmem id how is that supposed to work in two separate instances of Pd? fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlFIiw8ACgkQkX2Xpv6ydvQxGgCePjlJJTseMuPVMhuYQGWkavgv u10AoMhpJaE6OsdPQk7HbhmMM0W75aTo =5+nU -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] filmMPEG1 error in compiling
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-02-10 23:50, Hans-Christoph Steiner wrote: the filmMPEG1 plugin uses the libmpeg1 to playback MPEG1 videos. Uninstall libmpeg1 if you don't need it. that's a bit crude, as you might need a given library for other reasons than Gem, so uninstalling might often not be an option. the canonical way to deal with it, is to disable support when running configure: ./configure --without-mpeg Post the build transcript if you want to try to fix it. definitely. even if you have found a way to make it work for now, i would still be interested in the build transcript, namely, the output of configure, config.log and the actual error you got when trying to compile. system Ubuntu 10.04 on AMD64 bleeding edge :-) anyhow, gem-0.93.3 is shipped with quantal. fgmfasdrt IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlEYqYkACgkQkX2Xpv6ydvQxsgCdHKyS6K33UEqhx92G/4gM1TWI 3RMAoNC+75pkeSVHvi0rWYxmZ8TYEMJK =fTKh -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] filmMPEG1 error in compiling
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-02-11 01:27, Elektro Moon wrote: Jack, thanks a lot, i managed to compile Gem 0.93.0. cool, what did you do? Gents, Unfortunately, if i use gemwin, it prints GL: invalid enumerant. Even how often? what is the _exact_ version of Gem you are using? (as it is printed on startup) text3D does not render anything. i'm sure you have a font in the right place, do you? I need pdp2gem be installed and use Gem 0.93 or higher, as 0.92.x does not render polish special characters such as . When I have 0.93.x the pdp2gem is not loading if I have 0.92.x polish letters are not in Gemwin. you need a pdp2gem that has been compiled against Gem-0.93, rather than Gem-0.92. A total devil's circle. no. fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlEYqhoACgkQkX2Xpv6ydvRBsQCg7Cub2cePbhaFLNRKYjaoqqfG XrcAnif4SwlW9urd6EurduVZtxrPZc+i =Lkpp -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] filmMPEG1 error in compiling
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-02-11 17:37, Elektro Moon wrote: Iohannes, strange things are happening. I reinstalled pd-extended 0.43.4 on my Ubuntu. I achieved the polish letters with arialunicode fonts. Than I reinstalled gem2pdp which required Gem 0.92.3 from the repository. So gem2pdp worked but not the polish letters. Uninstalling gem2pdp and adding the path to Gem 93.4 from git-hub caused quick note: Gem is _not_ hosted on github; please use the repository on sourceforge, as this is he one that is most uptodate; the github clone might be out of date. again the GL: invalid enumerate in pd. I know that there are fixes to gem2pdp but I never managed to compile from source. Anytime I add the folders where pd.pd_linux, gem.pd_linux and pdp.pd_linux exists, the compilation is stopped with the result of missing Pd and Gem sources. Which are the right folders for this? for compilation you need the header files, not the binaries (aka: *._pd_linux). on debian, Pd and Gem install their headers into /usr/include/pd resp. /usr/include/Gem. when installing from source, the paths you have to provide depend on where you unpacked the configured sources. fgamsrd IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlEZID8ACgkQkX2Xpv6ydvRzDQCfbHiR0ME4FB+cOc/OLmqoU8wg d1oAnikNni5t2temY8TPW6RpoS0GDGI0 =S09Y -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] jenkins Gem-fink builds post to auto-builds
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-02-07 05:34, Hans-Christoph Steiner wrote: As an example, I made the Gem-fink jenkins build post the binaries to auto-build.puredata.info: http://autobuild.puredata.info/auto-build/2013-02-06/ hmm, would it be possible to only upload a zip-file that is named after the build-host and put all those zipfiles into a single folder? something like: .../2013-02-06/Gem/gem-macosx105-powerpc.zip -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlETZf0ACgkQkX2Xpv6ydvRCFQCfdtAUKB8LVZTXsc41OVfx3XiS M8EAoKJ02yzWSqdLyhCTStCOB4w45FL6 =V6k5 -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] publishing gem auto-builds
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-01-24 10:03, Nicolas Montgermont wrote: Where can I download a build? for example the template libraries on mac 10.5: https://macosx105-i386.pdlab.puredata.info/job/template-libraries/label=macosx105-i386/ seems like there are no artifacts. i think in the configuration, you have to specify which artifacts should be exported (something like: *.pd_*, *.so, *.dll) sdfmrt IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlEBACUACgkQkX2Xpv6ydvSUvQCfUbPyPblojDFQG9myN59Cm/QC sQYAn3rvEX0sgUuixtimxPdFYXPRThND =J6qU -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] error: Cannot open
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-01-24 15:32, Elektro Moon wrote: Dears, did anybody manage to open a playlist created previously in VLC? The only extension is .m3u what VLC handles for me anyway, but neither opening it in PD with the extension nor without works. actually i don't think it is really possible. (even libvlc has removed direct support for playlist-files; the application has to parse the playlist and then create a media_list_t structure according to it, which can be played; Gem does nothing of that kind) otoh, m3u is a rather simple file-format; you could even try to parse it from within Pd. And still the question is how do you loop it pd? send a [loop( message to pix_video or in the message box there should be a loop command? that's a tricky question: how do you loop a live-video stream? after all [pix_video] is really an interface to infinite pix streams, not to fixed-length media; hence you don't get information about film length and EOS, which you need if you want to loop. the object to play fixed-length media is [pix_film]. unfortunately, there is no VLC backend for [pix_film] so far. luckily there is a GMERLIN-backend for pix_film, which can play a lot of files as well. fmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEUEARECAAYFAlEBSpoACgkQkX2Xpv6ydvQh9ACgvI+cdD9kA3iGVE62QQsaN/Lt 8NIAmLQkx09/Vz5ixIXWri2ueoojOrM= =HppR -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] error: Cannot open
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-01-21 00:04, Elektro Moon wrote: Iohannes, I tested your suggestion with [dimen 1280 720( to pix_video, but no difference. post your patch. fgmdasr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlD9CwsACgkQkX2Xpv6ydvQrIgCfWiSH0vvkGMTUGOwj/OnFssSh 5jgAnikNwyFKTmW9tnRgFYnj+LJgryNv =oS+i -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
[GEM-dev] upgrading Gem's sourceforge project
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi all, i'm currently thinking of upgrading the pd-gem project on sourceforge, since sf seems to want drop support for the older system on the long run (and i'd prefer to do it while i can choose when to do it). some information on the upgrade process can be found at [1]. i think the main difference we will experience is, that the repository address will change. OLD: ssh://pd-gem.git.sourceforge.net/gitroot/pd-gem/Gem NEW: ssh://git.code.sf.net/p/pd-gem/Gem (or git:// rather than ssh:// for anonymous checkouts) from other projects i have migrated it seems that the old repository will stay available, but they won't get automatically synched after the migration (which might to lead to some confusion until everybody uses the new URL)(btw, it seems to be possible to manually push to the old repository for now) if somebody has objections, they should speak up, f gamdr IOhannes [1] https://sourceforge.net/p/upgrade/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlD4H7kACgkQkX2Xpv6ydvSB1ACg46B7sEzi9iFmgqEojbrGlHkx OAsAn1wHNqDD8KT/CGIaxtqkZzXwPZ09 =KCM8 -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] [PD-dev] pix_opencv
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-12-12 19:42, Antoine Villeret wrote: i've already tried to make a C++ external from the template but i never reach something which works so if you have a working template please let me know pix-opencv depends on external libraries, and afaik often needs specific versions thereof. i think it is a perfect candidate to *not* use a template Makefile but instead use something more intelligent like autotools, scons, cmake,...which reminds me that it already does use autoconf and what about including it in Gem ? as it depends on it (and it may depends on very new feature such as ROI soon) i think it's a better choice pix-opencv is developed by different people than Gem. i think it is good to keep the repositories (and user-management) separate. so: i'd rather not have pix-opencv be part of Gem. but: i agree that pix-opencv could be made more readily available to users. it might be a good idea to distribute it together with Gem-releases. so: the build-system needs little changes to build a pix_opencv found in extra/ (basically, uncomment the relevant lines at the end of extra/configure.ac and add a line to extra/Makefile.am) we could then create a script that pulls in pix-opencv to extra/pix_opencv before the builds are actually started. caveat: both Gem and pix-opencv are complex projects. Gem has slow release cycles, those of pix-opencv seems to be even more so. synchronizing both projects so that we can create a stable Gem-package including a stable pix-opencv could be impossible. so in a way it would be better if pix-opencv was distributed separately, but actively. fgmasdr Ihannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlDJlRcACgkQkX2Xpv6ydvRQ0gCguxWsVlMU838wbLxW9zs0px4W rmwAn2vf35asYl+NRTwxs+FXjtrWCzhk =HCe3 -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] pix_set new features
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-12-07 13:39, Antoine Villeret wrote: i think this is a good idea i usually make changes to pix_object to fit the requirement of my working projects if i have the opportunity to do that for other objects (and i hope this happens soon) i'll let you know so my plan is actually something like this: - - add a new property ROI to the GemState. - - add a new object [pix_roi] that allows you to set the roi in a normalized form (0..1 rather than 0..width); this object will simply set the ROI property. - - have the pix_objects use these roi-property. in order for the latter to work more consistently, it would be nice (in a 2nd step?), to change the architecture of the pix_objects slightly: - - add new virtual methods called like processLineRGBA(void*data, unsigned int width, imageStruct*img); for line-wise processing (with context). GemPixObject would then take care of calling processLine correctly for the given ROI. if done correctly, we could also utilize this to allow parallel processing of pixes as well (see [1]. fgmasdr IOhannes [1] http://hirntier.blogspot.co.at/2009/02/parallelizing-video-routines.html best a -- do it yourself http://antoine.villeret.free.fr http://drii.ensad.fr -- Google lit ce mail... si vous refusez cela, utilisez l'adresse antoine.villeret [at] free.fr pour me contacter 2012/12/7 IOhannes m zmölnig zmoel...@iem.at: On 12/07/2012 01:50, Antoine Villeret wrote: hi all, i've added some new features to pix_set : - roisize and roioffset which allow to set only a small part of the whole image - fill which set all the pixels by sending only one value (no need to make a huge list...) the help patch have been updated and i also make an example 04.pix/27.bitmap_font.pd feedback are welcome feel free to include it in Gem thanks for your patches. eventually i would like to have generic ROI support for all pix_ objects (apart from some objects where it doesn't make sense). this however, would require a rewrite (substantial adaption) of the processing core of all objects :-( fgmasdr IOhannes ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlDG9QQACgkQkX2Xpv6ydvTC8QCfUE8isxKGWz7EKPS4Vz7aNk6w bk8AnjRUwJdQw5r9opjCkDAmyFl5JUup =lJyp -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] pix_set new features
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-12-11 14:16, Antoine Villeret wrote: it sounds great, how can I help ? who starts ? i started to implement [pix_roi] and adapted [pix_set] accordingly. [pix_set] now also tries to write on an incoming image (rather than always using it's own image). hopefully this won't break anything. check whether it does what it should. fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlDHZwoACgkQkX2Xpv6ydvRKjwCeL1TkkDCUBDclPGijlqmOEwbw N2AAoNZhdnV+BdN6Jbn4r55n4w2eBLAO =NL2h -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] pix_set new features
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-12-11 18:48, Antoine Villeret wrote: is does thanks while i understood the need of normalized coordinates for texture in OpenGL, i dislike it in pix_objets, because we deal with array of pix and i think it's more human readable to use pixel coordinate in this case this also add some conversion both in the code and in the patch but this is only my point of view i understand that (esp. in the context of pix_set), but i want ROI to also work with simpler effects where you might want to specify an area, where the effect is applied, without having to care about the pix dimensions. also Gem uses normalized values whenever possible. i started a pix_roi-help.pd and updated pix_set-help.pd (remove my roi messages) (in my repos, on master branch git://github.com/avilleret/Gem.git) cool fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlDHdLQACgkQkX2Xpv6ydvT8qgCcDDsEjlQCUxCZh29v8GSNDKtr brEAoKzyq02dP5/0R2MQmJHIpmaA/dPi =qemJ -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] pix_set new features
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-12-11 19:00, IOhannes m zmoelnig wrote: On 2012-12-11 18:48, Antoine Villeret wrote: is does thanks while i understood the need of normalized coordinates for texture in OpenGL, i dislike it in pix_objets, because we deal with array of pix and i think it's more human readable to use pixel coordinate in this case this also add some conversion both in the code and in the patch but this is only my point of view i understand that (esp. in the context of pix_set), but i want ROI to also work with simpler effects where you might want to specify an area, where the effect is applied, without having to care about the pix dimensions. also Gem uses normalized values whenever possible. however, i'm not so much opposed to add a special message to specify the ROI in absolute values and [pix_roi] would then normalize the values internally. fgmadr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlDHeHAACgkQkX2Xpv6ydvTIGQCeO2tuvkrwvMWD85eYk7wV17CE o6AAoJjTHpoqTjp+UDuiK95zQHiWDbIm =8jSq -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] [ pd-gem-Bugs-3517368 ] gem 0.93 does not play .mpg files on Mac OS X
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-10-22 21:15, SourceForge.net wrote: Bugs item #3517368, was opened at 2012-04-12 19:30 Message generated for change (Settings changed) made by eighthave You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=507079aid=3517368group_id=64325 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Pixes (pix_ objects) Group: None Status: Open Resolution: None Priority: 7 Private: No Submitted By: Hans-Christoph Steiner (eighthave) Assigned to: Nobody/Anonymous (nobody) Summary: gem 0.93 does not play .mpg files on Mac OS X as chris has pointed out, it's probably better to drop mpg support on OSX, rather than trying to fix it (esp. since i don't have too much time right now). it _is_ a regression, but with a low priority. fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlCGYGcACgkQkX2Xpv6ydvRpdwCfUuri4rGDL1LGsWQcb7NTktG1 ZhYAoJlwzq5p7mS6NYQl24SOfDQVbbU7 =cthx -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] [ pd-gem-Bugs-3517368 ] gem 0.93 does not play .mpg files on Mac OS X
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-10-23 16:31, chris clepper wrote: On Tue, Oct 23, 2012 at 10:18 AM, Hans-Christoph Steiner h...@at.or.atwrote: as chris has pointed out, it's probably better to drop mpg support on OSX, rather than trying to fix it (esp. since i don't have too much time right now). it _is_ a regression, but with a low priority. I think we should leave it open for someone to fix rather than removing it, but I agree, it is low priority. I suggested removing the alea.mpg file (and maybe replace the other antiquated media files too). There is no way to remove MPEG-1 support as it's part of Quicktime. ah yes, with dropping mpg support i mainly meant not bothering about how good or bad mpg files play back (thus, officialy not supporting it) rather than removing code that deals with mpg files. fgasdrm IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlCGsnAACgkQkX2Xpv6ydvQD3gCg8gUfEX+ovSbzf6qCu9P4yJeP 1nEAn3rS74RosZW9kvzOV8ZbVdyV4Bk9 =aMX9 -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] Gem + gem_filmGMERLIN Plugin Crash 10.7.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-03-18 03:21, Hans-Christoph Steiner wrote: I'm happy to update my packages once Burkhard makes a new release. Feel free to nag ;) gavl-1.4.0 and gmerlin-avdeocder has been released on 8th of june. nagnagbws IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAXkSUACgkQkX2Xpv6ydvS8qACfW7YacTHVqdTqZOl9j3pHhIQc ZpgAoISO2bmMMBb0jaLVXf7zzTeDKHVt =udn9 -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] pb to compil pdgst on ubuntu studio 12.04
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-07-03 15:44, q.dum...@free.fr wrote: Hello, Try to install on my pdgst pd-extended, but it does not work. before i fight my way through your 3 mails: do they differ, or are they the same? fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/zBosACgkQkX2Xpv6ydvRLIwCgvrntcSmOVbhySyBlToMmCO74 qBoAoOpA911HEhXTNBEh18yaBMz8JPFH =S/2Z -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] [PD] how to play long videos in PD ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-06-12 15:02, Фывапр Олджэвич wrote: Hi, lists ! i try to play videos of 2 minutes long via [pix_movie] or [ pix_film ] . Non of them work . Nothing appears in GEM-window. But if i load a video of 1 or 2 seconds - it plays it . How can I play longer videos in PureData ? Maybe I miss something ? check for errors on the Pd-console (and probably on the cmdline as well). maybe your longer videos are simply using a an unsupported codec. fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/XP9QACgkQkX2Xpv6ydvTOcACgvdQX7AI4Uxsy14P9Xrs13cep jXwAoJk36RcpVTdL2RbfK5G4hDNLCBh3 =T7Uz -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] videoV4L2 exposes channel, frequency, norm, width and height to pd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-06-05 12:45, Antoine Villeret wrote: hello, i made a small change to plugins/videoV4L2 in order to expose channel, frequency, norm, width and height parameters to pd what's wrong with widthheight in the current implementation? fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/N6OgACgkQkX2Xpv6ydvS6jQCg87J8gqI227+GbPuX9pmqPRD9 CZYAoLJnseBOyPRr2x6L9+r5ZwsKLMxV =CihP -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] videoV4L2 exposes channel, frequency, norm, width and height to pd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-06-05 13:09, IOhannes m zmoelnig wrote: On 2012-06-05 12:45, Antoine Villeret wrote: hello, i made a small change to plugins/videoV4L2 in order to expose channel, frequency, norm, width and height parameters to pd what's wrong with widthheight in the current implementation? ah. looking at your patch i see that you only added the keys to the enumeration. so you already could have changed the values, but the interface did not tell you so (mainly because for compat reasons it was kind of clear that you could _set_ those values) fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/N6eMACgkQkX2Xpv6ydvRXpACgn3jkSqIyzjO62pJKeBaHnvfn yIwAn0SsdUpw1/r6VaHa+fIVzEvnIGMp =q72y -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] [ pd-gem-Bugs-3521302 ] pix_write and pix_buffe crash when writing a file fail
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-05-02 14:25, SourceForge.net wrote: -- Comment By: Cyrille Henry (nusmuk) Date: 2012-05-02 05:25 Message: yesterday, my computer upgrade to 7:6.5.7.8-1ubuntu1.2 it did not fix the problem. but yes, the problem is fixed for latter ubuntu version. I did not have problem with 12.04, i gess i'll have to upgrade soon. so do you think that the problem is an ubuntu problem and that i can close the ticket? fgam,sdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+hK3QACgkQkX2Xpv6ydvSBXQCfZxxbjJYN+SG1pckr/MTOUJpT NUoAoNGS+gSfqSHm6V/xfT+YCvfylWNz =SeGu -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] [ pd-gem-Bugs-3521302 ] pix_write and pix_buffe crash when writing a file fail
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-05-02 14:51, Cyrille Henry wrote: so do you think that the problem is an ubuntu problem and that i can close the ticket? yes, blaming to old magick++ lib on ubuntu is certainly the best thing to do. at least it's the easiest thing todo :-) fgamdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+hLvoACgkQkX2Xpv6ydvQpPgCfRsudEmjq4mtFw17lKSZUcXS1 0NMAoMB96vejxzwqGDJedfN2wuFFPLsZ =45LC -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] Can't create object [pix_multitexture]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-04-17 17:08, Jack wrote: No, it is not [pix_multiimage]. In fact, i am looking for an object/abstraction to use a single texture where i can change the texture coordinate to show a part of this texture (which is a font set). Because I have a lot of text to show in the gemwin. Maybe you have something that i can use (or a method to achieve this) ? [pix_coordinate] (which should really be called [tex_coordinate])? fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+T0uEACgkQkX2Xpv6ydvRg9wCcDwddMgliqcv9KrA9vImn7Nq9 0B8AoIOvd+cSWE4lCjTIxBCrGxuVQufQ =0M2L -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] vlc plugin under OSX
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-04-04 20:16, m.e.grimm wrote: got it... yes worked i get: dylib loading file './gem_videoVLC.so'! now though i get: [pix_video]: backend #0='vlc' : vlc GLEW version 1.5.4 [pix_video]: no valid video backend found you have to specify a valid device that VLC can open. unlike other video-backends, there is no default capture device for vlc. try [device screen://( fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk98lwwACgkQkX2Xpv6ydvQvOwCgutJHEFWavMCf0BeaPahFCZ3g 8xgAn2PBNGx3Qz64XreUeK/lrm2mcjWc =fVdi -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] vlc plugin under OSX
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-04-04 15:58, Hans-Christoph Steiner wrote: That would mean adding -I/Applications/VLC.app/Contents/MacOS/include to CPPFLAGS and -L/Applications/VLC.app/Contents/MacOS/lib/ to LDFLAGS for the build. IMHO, the Gem build system would do that when it builds the VLC plugin on Mac OS X. yes, but i don't think that Gem should do that automatically for you. it should be possible though, to simply specify where VLC resides. fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk98l58ACgkQkX2Xpv6ydvS9lACfStn/9Tf10r/rP7G19Cy68AuY rewAn3JYVEgB3mJgz0A4IPWgiPrZlgEQ =HcS9 -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] Gem + gem_filmGMERLIN Plugin Crash 10.7.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-03-19 15:52, IOhannes m zmoelnig wrote: On 2012-03-19 15:41, m.e.grimm wrote: Looks like you don't have libmpeg2 installed. In this case gmerlin-avdecoder removes the video stream from the internal structure, so every access to video stream 0 might result in a crash. well yes, but in that case Gem should not try to access the video stream 0, thus preventing a crash... thanks for reporting in the tracker. is it possible for you to get back to the state where the crash happened? so we can make work with gmerlin even if it was compiled without libmpeg2 support... fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9rLyoACgkQkX2Xpv6ydvSLzACg3XwiYdsyy2qohbg6QIKM7uTX E40AoOpeegXvnPN/u+YeQ+uoUH4KGZWE =Lia3 -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] ImageMagick Compiling Error w/ Gem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-03-21 13:51, m.e.grimm wrote: and copy the generated imageMAGICK.preproc to pastie.org ok but this generates 4mb and pastie/pastebin/etc pastes cannot be larger than 64 kb then zip it and send it to me in a personal email. fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9p0G4ACgkQkX2Xpv6ydvTIEQCg2obACvJgNzHdBy7VCq+9JIZj gjwAnjVT8+pc3mLGHbE7O/DGSlkCjWx0 =fjCE -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] ImageMagick Compiling Error w/ Gem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-03-20 18:36, m.e.grimm wrote: reported. i got this reply: Unlike C++ and Java, C does not have namespaces and conflicts are possible. The only solution is to not include the ImageMagick headers and Carbon headers in the same source module. please check out the current git master (7342f1acb68), i hope it is fixed there. fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9p2uYACgkQkX2Xpv6ydvT3vQCcC1TpT79khmY0bmqH7DtPvyaS akoAoJ3nGla9biZ99pWIrr9TarWqR+gp =Amto -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] ImageMagick Compiling Error w/ Gem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-03-19 15:17, m.e.grimm wrote: g++ -DHAVE_CONFIG_H -I. -I../../src -I../../src -DPD -I/Applications/Pd-extended.app/Contents/Resources/include/pd -I/sw/include/ImageMagick -g -O2 -freg-struct-return -Os -falign-loops -falign-functions -falign-jumps -funroll-loops -ffast-math -mmmx -fpascal-strings -MT gem_imageMAGICK_la-imageMAGICK.lo -MD -MP -MF .deps/gem_imageMAGICK_la-imageMAGICK.Tpo -c imageMAGICK.cpp -fno-common -DPIC -o .libs/gem_imageMAGICK_la-imageMAGICK.o please run the following in plugins/imageMAGICK: $ cpp -DHAVE_CONFIG_H -I. -I../../src -I../../src - -DPD -I/Applications/Pd-extended.app/Contents/Resources/include/pd - -I/sw/include/ImageMagick -g -O2 -freg-struct-return -Os -falign-loops - -falign-functions -falign-jumps -funroll-loops -ffast-math -mmmx - -fpascal-strings imageMAGICK.cpp -fno-common -DPIC -o imageMAGICK.preproc and copy the generated imageMAGICK.preproc to pastie.org fgmnase IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9o5l0ACgkQkX2Xpv6ydvQ/UACfcgymHPwq3c1GGWME3cg4MOt0 kOQAn30LOllTVBNRfhEluMi9H0NeYxnj =o969 -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] ImageMagick Compiling Error w/ Gem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-03-19 15:17, m.e.grimm wrote: ive been compiling with --without-imagemagick but just tried again and was currious about the error. seems to be a problem with ImageMagick's symbols clashing with System symbols. you could file a bug-report for ImageMagick. fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9nSFgACgkQkX2Xpv6ydvTB8ACgko3Hv0XssW60ulgT7LFBsZIH mB0AnA3oSBdr/Ih5coR/QR2JgGIyRNx9 =ClOh -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] Gem + gem_filmGMERLIN Plugin Crash 10.7.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-03-07 22:45, m.e.grimm wrote: OK. Well It works. Pd-Extended 64bit recent autobuild + Gem with filmGMERLIN plugin on OSX 10.7.3 [...] congrats! do i read that correctly, that there was no need in the end to modify Gem (or gmerlin) in any way? See attached screen shot. yes, that (color problem) was kind of expected. it should be easy to fix, though. I am not sure what the problem was. This is still very unstable, crashing when loading alea.mpg in pix_film. As you can see by the iirc, gmerlin-avdecoder cannot open alea.mpg; it shouldn't crash though. fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9YbmEACgkQkX2Xpv6ydvRWqACfYFHSxnKfY1l4K0npZiEsf9/Q iGEAoPar7lo4jV6vvLmvXcTj3dy9WMHD =uA6W -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] pix_equal (was Re: new pix_colordetect)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-03-01 01:36, Ricardo Fabbri wrote: Hi, just a sample of the tracking that the proposed [pix_equal] allows: http://vimeo.com/36239477 Let me know if this simple object should be included in Gem. i'm still reluctant to include random simple objects into streamline Gem. in the given case i will most likely include it, but be prepared that once i find a decent [pix_expr] implementation that object will be replaced by an abstractions. not a bit deal, i guess :-) also, i'd like to point to the existance of frei0r and FreeFrame-1.0 plugins, that would allow you to write code once for a large number of hosts, and which integrate seemlessly into Gem as well - at least for algorithms that don't do any fancy analysis which has to be output in non-pix form (like [pix_multiblob]) fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9PMmMACgkQkX2Xpv6ydvTA9ACeNnow6mSV0oVgnC1amgcnu7uU bXMAnA5fv8VCZucM5MRt6OuWwmZEvebI =/RBh -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] pix_equal (was Re: new pix_colordetect)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-03-01 09:25, IOhannes m zmoelnig wrote: i'm still reluctant to include random simple objects into streamline Gem. in the given case i will most likely include it, but be prepared that once i find a decent [pix_expr] implementation that object will be replaced by an abstractions. not a bit deal, i guess :-) so i did include the object, with a noteable modification: color ranges in Gem are always normalized! e.g. it should be 1 1 1 1 rather than 255 255 255 255. this change will break your (riccardo's) patch, so take care! PS: [pix_equal] could have been done with [pix_curve] and is virtually identical to [pix_alpha] vhmysdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9POVgACgkQkX2Xpv6ydvTjIwCghCt6Zakx99a06Q4wNVzXO9f9 FpsAn1uspRdk1Yakl6XfNadupi+Cdox8 =/dZr -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] Gem + gem_filmGMERLIN Plugin Crash 10.7.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-02-28 19:43, m.e.grimm wrote: well, run them on a file, so they can actually do something. well. that would be smart. yes. bgavdemux works fine. but now I am noticing that the only two binaries I have here are bgavdemux bgavdump could that be right? i don't know. where is here? most likely the missing tests have been build correctly, but they are not installed by fink (so you don't find them in your path). e.g. the debian package does not install any of those test binaries. so maybe i have some more work to do or did something wrong also I just compiled Gem from the git source and get the same/similar crash log: http://pastebin.com/K1zQbzCP i attached a minimal example that should trigger the same problem (according to your backtrace). if the example crashes, then i think it is a problem with gmerlin-avdecoder itself (or i forgot to initialize something, but burkhard should know an answer to that as well) if it does not crash then the problem is with Gem (btw, when creating the test, i noticed a small typo in Gem's filmGMERLIN which might simply fix the problem...so if the test runs ok, try an update of filmGMERLIN...) fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9N6aUACgkQkX2Xpv6ydvSA/wCgtHfQDIheuoJWQhlKr7AHdbr0 vvcAn2NthCjTpH0iXJmP8HccTGmLzdhs =lEvV -END PGP SIGNATURE- gmerlin_test.tgz Description: GNU Unix tar archive smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] Gem + gem_filmGMERLIN Plugin Crash 10.7.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-02-29 15:26, m.e.grimm wrote: oh this is a crash: trying to create video converter Segmentation fault: 11 sorry. trying to multitask this morn and only half paying attention. so now what should i do? send the example to gmerlin-dev and ask for assistance. f gamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9OSYUACgkQkX2Xpv6ydvTsDQCgpnwMn5jlUxtdkrk/+GRn/qUy z64An0S6JfCE0HODKoDaItLiQCcQwEyY =XJhG -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] Gem + gem_filmGMERLIN Plugin Crash 10.7.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-02-28 17:38, m.e.grimm wrote: here is the crash report: http://pastebin.com/KF0jDSPu does any of the gmerlin-avdec tools work? I compiled gem_filmGMERLIN for 64-bit Gem-0.93.3 on 10.7.3 and am would you mind working on a checkout of the master branch of Gem? once things are sorted out, they can be backported to 0.93.3 (or not, depending on their nature) make[2]: *** [gem_imageMAGICK_la-imageMAGICK.lo] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1 Not sure if this has something to do with the gmerlin plugin prob though no, it's unrelated. compilation of the imageMAGICK (an image-loader plugin based on ImageMagick) fails. either disable it (./configure --without-ImageMagick) or ignore it, by running make -k fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9NDEgACgkQkX2Xpv6ydvRTPgCbByAkyAdFEOzAWIt9jhhWIDIj wZ4An0E5JQ+dx3QwgTaWbA/9oyhg7s2D =itT/ -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] Gem + gem_filmGMERLIN Plugin Crash 10.7.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-02-28 18:41, m.e.grimm wrote: would you mind working on a checkout of the master branch of Gem? yes. although using git im getting a permission denial checking out: megrimm-mbp:Desktop megrimm$ git clone git://pd-gem.git.sourceforge.net Cloning into 'pd-gem.git.sourceforge.net'... fatal: unable to connect to : [0: ::1]: errno=Connection refused [1: 127.0.0.1]: errno=Connection refused that should be $ git://pd-gem.git.sourceforge.net/gitroot/pd-gem/Gem and your authenticated git checkout (read-write) is looking for your password? quite obviously it's looking for _a_ password :-) does any of the gmerlin-avdec tools work? yeah ... i am at a loss though for commands to test this. there is no man page or anything... how do i? i don't know which binaries get installed by the gmerlin-avdec fink package. try to get a list of installed files and see whether something goes to bin/ fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9NEpMACgkQkX2Xpv6ydvQ8sgCfTanVu5tVktdpumoluGWDKi/Z DvkAn3OIvvPWYubCcqcu/FG2S6lfNzPI =88or -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] Gem + gem_filmGMERLIN Plugin Crash 10.7.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-02-28 18:44, IOhannes m zmoelnig wrote: i don't know which binaries get installed by the gmerlin-avdec fink package. try to get a list of installed files and see whether something goes to bin/ tests/bgavdemux tests/bgavdump tests/bgavsave tests/count_samples tests/frametable tests/indexdump tests/indextest tests/mmstest tests/rtsptest tests/seektest tests/vcdtest tests/ymltest those are the executables that are created on my system when gmerlin-avdecoder is compiled. something like bgavdump should be a good test. fmrgr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9NE3EACgkQkX2Xpv6ydvThQQCgyfRV+D+mQVNX0MK01z0CzZ/E Jd4AoNk6BJ7fXlo0OSQOa1jmpSchGydl =NG/2 -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] blob orientation in pix_multiblob
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-02-24 19:36, Ricardo Fabbri wrote: Looking forward to your feedback. If you think this should be included, I will then go ahead and polish the documentation. thanks, i added the relevant commits to the main repository. it would be great if you could add some (easy to understand :-)) documentation fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9LXl8ACgkQkX2Xpv6ydvSwswCgkw6Zx2ORKymMP1p0oOapM0rV 2AkAn2FHR2vFYIw0DTCR577KtaUu/BnO =y32G -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] how to share texture on different thread without having to copy it on the CPU?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-02-23 12:35, Cyrille Henry wrote: hello, is there a solution to share texture between 2 pd instance, or between 2 software, without having to copy it back in CPU? somthing like pix_buffer_read and pix_buffer_write, but for gpu texture. it look like possible, but does anyone already implement it? http://developer.download.nvidia.com/opengl/specs/GL_NV_copy_image.txt syphon on osx does something like this. Gem-support is currently rudimentary though... (only output, and only the main framebuffer (gemwin)) fgmasdfr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9GO44ACgkQkX2Xpv6ydvRUUwCgiDPDYU2Dj4+YqbyHS+mgB79h M94An1uIOtEniRtxcJa4kHWwHsGPUmcG =gUof -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] pix_opencv not working with Gem from git
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-02-16 22:28, Antoine Villeret wrote: pdgst is working on 32 bit but i got an undefined symbol error on 64 bit : pdgst.pd_linux: undefined symbol: g_object_get_property seems like a problem with gstreamer/glib... and I also noticed that making Gem as a normal user lead to an error : Assembler messages: Fatal error: can't create .libs/gem_modelOBJ_la-modelOBJ.o: Permission denied i think you have leftovers from a previous build run as a different user (probably root). something like: $ chown -R antoine . $ make should do the trick (until next time you decide to run sudo make) hmst IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8+EXMACgkQkX2Xpv6ydvTGgwCg6zfNBNcZnOpSKoMpMRiJuorE FGcAn2NutPYPUc3lCFCVun0i68sOPZRo =puql -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] pix_opencv not working with Gem from git
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-02-16 23:00, Hans-Christoph Steiner wrote: -mms-bitfields should really only be used on Win32, unless you are doing something really weird, or building for Win32 on GNU/Linux+MinGW. well yes. what i don't really understand is, why gcc on linux (i'm not talking about a cross-compiler like i686-w64-mingw32-gcc that runs on linux but really builds w32 binaries, but instead about a native compiler that produces binaries for linux) provides and uses the -mms-bitfields flag at all. what are the possible uses of ms-bitfields on linux? fgmar IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8+HZEACgkQkX2Xpv6ydvRRogCgn+HRKrtRDCogvnsNFW8nbtxS o9cAn2tLjh7hCYPKeLJxEE3MYcIOa1j8 =OBge -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] please reopen bug 3222807
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-02-15 03:21, Matteo Sisti Sette wrote: Hi, Bug 3222807 should be reopened. Or if you prefer to file a new one and copy-paste the information because it is good for the bugs-closed statistic then go ahead. while i do like bugs being closed (also for the statistics :-)), this is usually not the reason why a ticket get's closed. also: if you talk about a specific issue, please provide a link. it is not very hard to go to the sourceforge page, navigate to the tracker (hopefully choosing the right one), pasting the bug-id you gave into the search field, doing a search and then clicking on the result. however, it is super-easy to just click on a direct link to the ticket (and i figure it is about the same amount of work for you to copy the correct bug-id as to copy the entire url) furthermore: if you want to re-open an automatically closed bug, you should be able by adding another comment to the issue. sf will automatically re-open it. and: keep in mind, that if a given bugreport closed as fixed, this doesn't mean that a specific version of Gem will suddenly stop having a given problem. bugs are usually closed as soon as there is a fix in the current development branch of Gem. this doesn't mean that you as an end-user can already download a fixed release. It affects both Windows and Linux. Zmoelnig said he tested it on Mac OS and works, I believe that, but I've tested it again on Linux and I confirm the issue. And windows of course. the ticket has been closed because it is really believed to be fixed. only now i tested with a git-snapshot of Gem (b41709baf), and Gem-0.93.3, as is packaged in Debian. both can load the sol2.tif file just fine. and yes, i have installed the imageMAGICK plugin for Gem (gem-plugin-magick on debian) to do the decoding. imageMAGICK is _the_ plugin to load images on linux. if you need to be able to load a large number of different image-formats, then you really should use it. if you are on w32 or OSX, starting with 0.93 you can use the imageQT plugin on both platforms, which uses QuickTime and should be able to open any image file that QuickTime can open (if not, it's a bug, and it is definitely a separate bug from #3222807; if you think that this bug is (still) there, please go ahead and open a new bugreport). note that i cannot currently test whether it works as expected on w32. obviously, you will need QuickTime installed on your machine, in order to use imageQT (OSX (i386/ppc) already comes with it; in w32 land, you have to install it manually). i don't know by heart, whether the Gem-0.93.3 w32-installer has the imageQT plugin selected by default; however, it is definitely included in the installer. Also note the annoying threaded loaded image: ... as if the image was succesfully loaded (well it is succesfully loaded but not decoded). well, if you get the dreaded threaded loaded message, you are surely using an uptodate version of Gem... - regarding windows, Zmoelnig said: w32: Gem uses some rather old static code to decode image files (hence there is only a very limited number of supported formats); this code might not be able to read your TIFF file, and i have no real intent to fix this; rather, the w32 version should switch to a more common API (DirectSomething and/or QT) for reading images. Well that definitely needs to be done. no. that definitely has already been done. As does [...] upgrading to a the latest stable release of Gem... mfgasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk87fb8ACgkQkX2Xpv6ydvQpZACfTj9AitbgMD/zmh8PH0tq59Rx f0AAn0RPEqH3BbT1kQtgGzns5L4yPX7N =vcdI -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] gemvertexbuffer (prev.. vertex operations / vertex_* (prev.. gem port to opengl-es - initial developments..))
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-02-08 04:44, dmotd wrote: as any other primitive, you can connectmultiple gemhead to a single gemvertexbuffer. that's true, but i'm not sure it's a widely used feature, my sense is that people will create multiple gemvertexbuffer instead. which could mean that the documentation is lacking. i don't really see a strong interest splinting gemvertexbuffer in 2 different objects, but if you do so, and if you are ready to code it, then i have no objection, as long as you can provide a compatible abstraction that replace the current gemvertexbuffer object. of course, i wouldn't want to break your current functionality. no problems from my side. i don't especially like the _name_ [gemvertexbuffer] (it is too similar to [gemframebuffer] (which goes well with [gemwin]), but the functionality/usage is very different), and if it was made into an abstraction, all the better. one could also use something like [pix_texture], that applies textures that it either generated itself (from a pix) or that was generated somehow else (by taking the texture id in it's 2nd inlet). but i'm not so sure that this scales well for the different VBO types. fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8yMy0ACgkQkX2Xpv6ydvTSEgCeOrsIy34fUJO0K7K1yxxZ0+Tz d5sAnigbwBE47x3mq7zrhxkYlo7sUI+7 =0fBX -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] pb to compil pdgst on ubuntu 10.04
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-02-06 00:00, ben...@free.fr wrote: hello, I didn't managed to compile the nice pdgst pack of objects on ubuntu 10.04 It tried with the latest Gem from git and with pd 0.42.5 src, Pd-0.42.5-extended src and pd 0.43.0 with different warnings but the same error (see below) libgstreamer-plugins-base0.10-dev is installed, gstreamer I also tried to upgrade gstreamer with ppa:gstreamer-developers with no success thanks for any advice ++benjamin make[1]: entrant dans le répertoire « /home/benjamin/ZSofts/PD/pdgst/src » gcc -g -O2 -fPIC -DPD -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DPDGST_PLUGIN -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -I/home/benjamin/ZSofts/PD/pd-0.43-0/src -I../include -o s_main.o -c s_main.c s_main.c: In function ?sys_findprogdir?: s_main.c is a source file from pd, not from pdgst. it seems, that you somehow managed to have the Pd sources at the same place sa the pdgst sources. you should not do that, but instead point PD_SRC (and GEM_SRC) to the location of the pd (resp. Gem) sources. something like: $ make PD_SRC=/home/me/dev/pd/src GEM_SRC=/home/me/dev/Gem/src fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8vsL0ACgkQkX2Xpv6ydvR6uwCcDzLOruSjd9l398JTPnmw3AYw ivgAoKG800GqBpojaX8k95STuuYM4T4l =ilR4 -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] vertex operations / vertex_* (prev.. gem port to opengl-es - initial developments..)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-02-04 17:23, dmotd wrote: it makes sense to resurrect some of vertex_* code and clean it up, although i'm a little hesitant about working with it directly as it has personally i would like to get rid of it entirely - i simply haven't had the heart yet to do so... i think a simpler approach is taken using the new [gemvertexbuffer] object (by cyrille and antoine), which basically allows to use a table as VBO input. shouldn't that be enough for your needs? most Geos could be implemented as an abstraction based on [gemvertexbuffer] (who's first?) fgmadsr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8v1wEACgkQkX2Xpv6ydvSG9wCfXLMG58NwJCVEumrpuDVzzBgC fkUAnjlVVK07gTQKmanSSrSURqqMNE4b =xrgn -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] Compiling Gem 0.92-3 on OSX 10.6.8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-02-01 19:41, Florian Grond wrote: and make I found the following gem_filmDarwin.so gem_filmQT.so gem_imageQT.so gem_imageSGI.so gem_recordQT.so gem_videoDarwin.so Gem.d_fat If I compare it with what I see in /Library/Pd/Gem I figured that I don't have have some of the so files well, you the Gem binary release has been compiled on machines that have more development libraries installed that your machine; therefore there is support for some more backends, which results in more plugins (files with .so extension) anyhow, you should even be able to use the plugins from the release with your self-compiled Gem! and I also miss the Gem.pd_Darwin well, you specified that you wanted to create a Gem.d_fat, rather than a Gem.pd_darwin at the cmdline. you get what you ask for. I thought I could just take Gem.d_fat and the so files and place it in /Library/Pd/Gem which I did, PD-extended starts but shows compiled Nov 10 2011 this seems to be a bug in Pd-extended, which (for reasons of incompatibility) prefers to not be able to load .d_fat files on osx and instead uses only .pd_darwin (though - for reasons unknown - it allows e.g. .l_i386 and .pd_linux on linux/i386; so this seems to solve some special osx issue) i would advise you to file a bug-report against pd-extended. Everything seems to work, but I figured it uses the Gem.pd_Darwin universal binary. So I tried this configuer line: ./configure --with-pd=/Users/maki/Development/pure-data/src --enable-fat-binary=i386 the output from configure tells me that the target is now Gem.pd_darwin right; you could have simply renamed all .d_fat files to .pd_darwin After make, when I copy the Gem.pd_Darwin into /Library/Pd/Gem PD can't load it and says Symbol not found : _sys_close expected in flat namespace again, seems to be a problem with Pd version mismatch. i suspect that you compiled Gem using Pd-0.43 and are now using Pd-0.42 (or some other older version). it's always best to use the same version for compilation and running! I also have some class files that I've added to the sources but the seem not to get compiled. (That's the reason why I need to compile Gem) I can't find the corresponding object files. depends on how you added them. just putting the .cpp/.h files into src/Pixes/ is no longer enough! you have to explicitely add them to src/Pixes/Makefile.am fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8qUFgACgkQkX2Xpv6ydvTVegCfdHEfK+RyIxdQs3kjz37gE5Hk yUkAni4ea07c8h9QDlF70gzzOmrEdyp6 =PMty -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] gem port to opengl-es - initial developments..
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-02-01 18:30, dmotd wrote: hi gem folks, i've had a bit of free time to begin porting gem to opengl-es. kjul! cloned gem git, checkout 0.93 tag, created es branch. any reason why you did not use master? added egl drop in for GemWinCreate in master is an (experimental) new class of objects that implement window-handling rather than using the olde fixed GemWinCreate (look at src/Output). currently only OSX-10.6 builds make use of that, but the more it gets tested the sooner it will be the one and only method to create windows. successful build against pd-0.43 using enable-Controls and others disabled. -- reports: -- libxxf86vm doesn't seem to work properly on the tablet, so for the time being the window modelines are hard coded. there are some other window manager hints that are specific to the device too. gemwin successfully creates the egl window buffer and rendering context. gem crashes when glClearDepthf and glFrustumf are called (both are in the future (see above), those calls will not be hardcoded into GemManager any more, but instead are called from an abstraction (gemwin.pd) floating-point variations to the base GL functions and part of the GL-ES so they should be there but are not? spec). furthermore looking at the output of 'nm -C Gem.pd_linux' shows that these functions are not present in the compiled lib, what does this mean? what do you mean by not present? they are most likely undefined, as they will be imported from GL-ES i am coding on a linux-amd64 pc, cross-compiling in scratchbox and testing on the device, using git/scp as a go-between.. this is a bit cumbersome/inefficient - can anyone suggest a virtual machine image (linux based) that provides a graphical gl-es environment and a minimal editor/ide to build and test with? i haven't found a useable one yet. in theory, there are android-for-eee images availabe, which should , and there is myOS[1], which i haven't tried for some time (though it seems to be a dead project anyhow) but it never worked with my nvidia-card... if you have success in getting a simple setup for GL-ES development, please let us know! i'll keep everyone up to speed as i make developments, and if anyone can replicate my dev environment and wants to contribute i'll happily push to a public git sooner rather than later. oh please! fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8qU+cACgkQkX2Xpv6ydvSqKACg11zIQKLVO0zDipoKVez3KNgm AB4AnRVAFyc/czu2U37Q2jB1MPAO1kX9 =HABi -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] Gem 0.93.3 compilation on ubuntu Natty (11.04) 64 bit: imageMAGICK.cpp:82:54: error: ‘GetMimeList’ was not declared in this scope
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-01-30 09:59, IOhannes m zmoelnig wrote: Am I right that GetMimeList() should be defined in a mime.h header file associated with imagemagick? no. GetMimeList() is a member of the imageMAGICK class. it seems like oh, i just noticed that the GetMimeList should indeed be part of ImageMagick's mime.h header, and (at least according to my in-source notes, is there since 6.6.2-0 (though they changed API right after that, which is taken care of in gem) fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8qZxYACgkQkX2Xpv6ydvTn9ACfZkLoPMyDP2Y9LbSCcBQjzD7C ruEAoL/GlGzRrsFeSNg3Fo0Oxy2NFvvL =tac3 -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] Compiling Gem 0.92-3 on OSX 10.6.8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-01-31 01:28, Hans-Christoph Steiner wrote: You need to point it to your Pd headers ./configure --with-pd=/path/to/pure-data.git hmm, but my pure-data.git/ directory usually looks like: snip $ ls branches config description HEAD hooks info objects refs /snip i'd use something like $ ./configure --with-pd=/path/to/pure-data :-) anyhow, it seems that florian is trying to build using the xcode project: - - please be aware that these projects have not been updated for _ages_ - - autoconf/configure (as hans pointed out) is the currently used build environment - - max (or one of his students) claimed that they had updated the xcode project for the git snapshot, but they never sent me any diffs (or they got lost) regarding FTGL: $ configure should find automatically, that you don't have FTGL installed and disable it for you. finally: your subject mentions Gem-0.93.3 and OSX-10.6 in one line. the _only_ way to make this work is by forcing the build to be i386 only. look at the configure flags (./configure --help), there should be (oh, 0.92 is a _long_ time ago) a flag that allows you to set the architecture/fatness of the built dll. something like: --enable-fat-binary=i386 should do the trick. if it does not, you might have to add -arch i386 to the CXXFLAGS and LDFLAGS manually (and make sure that there are no -arch x86_64 anywhere. fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8nq80ACgkQkX2Xpv6ydvTB3QCg6gQ1gcLh3ZoqTejRkwhycK4r REUAoNDzhGCAnICtIfoSuZMM8zIpzOA/ =txkz -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] Gem 0.93.3 compilation on ubuntu Natty (11.04) 64 bit: imageMAGICK.cpp:82:54: error: ‘GetMimeList’ was not declared in this scope
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-01-29 07:08, John Harrison wrote: On my Natty 64 bit laptop I've been running an SVN of Gem 93 but recently hmm, developmen of Gem has moved from svn to git. despite my plans to sync the svn repository with git every now and then, i never found the time todo so. therefore it would be highly appreciated if you could use either the released sources of Gem (0.93.3) or use a git checkout: $ git clone git://pd-gem.git.sourceforge.net/gitroot/pd-gem/Gem if you want to stay stable, use the 0.93 branch (which is 0.93.3 + a few minor bugfixes): $ cd Gem $ git checkout 0.93 I've had a problem that any video I try to load with [pix_film] (or probably [pix_movie] although I haven't tried) crashes Pd. I thought I'd compile the latest Gem release with plugins to see if that fixed the problem. When I try to compile, though, I get: imageMAGICK.cpp:82:54: error: ‘GetMimeList’ was not declared in this scope I have Natty's libmagick++-dev, libmagickcore-dev, libmagickwand-dev (all version 6.6.2.6) installed. Am I right that GetMimeList() should be defined in a mime.h header file associated with imagemagick? no. GetMimeList() is a member of the imageMAGICK class. it seems like your imageMAGICK.h and imageMAGICK.cpp are slightly out of sync - e.g. because you modified one or only updated the other. alternatively it could mean, that the build-system is somewhat broken so that the 2 files are _made_ out of sync (with some compiler switches) - which should obviously never happen. fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8mXAgACgkQkX2Xpv6ydvSPZwCgio339wOg7/ad9wkiWOnYrb1Q aWgAoI4XOpp7K0nBGMr4l1J1y3PR89VM =B4Ar -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] more mingwoes32
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-01-16 17:01, Kristen Eisenberg wrote: testing Kristen Eisenberg Billige Flüge thank you for testing with us. fgamd IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8UVbsACgkQkX2Xpv6ydvQc+ACg7qEHu+PdCHG9Ij2Ct18Or8+u N0AAnA/0zBN0WLKcHPAl5fippNcoDv1M =qFrE -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] A/D video converter DFG/1394-1e with unicap
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-01-11 14:03, kubro bubro wrote: yes, i dont need it in unicap, if it works just somehow i will be happy. i tried dc1394 and dv4l before. removed unicap, and try dsc1394: [pix_video]: backend #0='v4l2': v4l2 analog [pix_video]: backend #1='v4l' : v4l analog [pix_video]: backend #2='dv4l': dv4l dv [pix_video]: backend #3='dc1394' : dc1394 iidc [pix_video]: backend #4='vlc' : vlc videoDC1394: no cameras found which simply means that your device is not an IIDC device (which is not surprising as IIDC is an industrial standard and usually outside of consumer world; i just mentioned it because i don't know your device and IIDC and DV are the 2 standards for video over ieee1394) doesnt matter if run as root, or set dimen 720 576 could be. leave that away for now. iirc, dv defines the video dimensions, so you cannot set that to an arbitrary size. [pix_video] will try to grab the data in the format requested, but it will not do conversions (if it can help it) with dv4l is more fun: videoctl: dimen 720 576 //doesnt matter about this, allways the same videoctl: driver dv4l [pix_video] should select the correct driver for a given device. videoctl: device /dev/fw1 info: proplist numread 10 info: proplist read 50_fields float 1 info: proplist read PAL float 1 info: proplist read is_color float 1 info: proplist read letterbox float 1 info: proplist read normal float 1 info: proplist read progressive float 1 info: proplist read quality float 0 info: proplist read recording_datetime symbol -MM-DD hh:mm:ss info: proplist read timestamp float 0 info: proplist read wide float 1 info: proplist numwrite 1 info: proplist write quality float 5 GEM: Direct Rendering enabled! GEM: GLEW version 1.5.4 GEM: Start rendering good. starting capture thread good. GEM: Stop rendering bad. why is rendering stopped? i that done manually (by you), or does it happen automatically? no errors, but picture is black, with some still(i mean not mooving) noisy artefacts on the bottom of the picture.. do you get anything on the terminal? (stdout/stderr, not the Pd-console) also, does this device work with any other application? which one? gmasdrt IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8NjNsACgkQkX2Xpv6ydvT6jgCfV+8V2u5bp0rkM6DiRs6i5pNN nvAAn02n5swW83K9lwRHfh3Doj3FeHOm =1v08 -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] artoolkit segmentation fault
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-01-10 16:05, kubro bubro wrote: Program received signal SIGSEGV, Segmentation fault. 0x7677df9c in GemBase::gem_startstopMess(int) () from /usr/local/lib/pd/extra/Gem/Gem.pd_linux (gdb) watchdog: signaling pd... watchdog: signaling pd... kill use the -nrt flag to Pd to avoid starting the pd-watchdog which starts signalling Pd Kill the program being debugged? (y or n) y (gdb) trace Tracepoint 1 at 0x7677df9c please provide a backtrace with bt. fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8NjrAACgkQkX2Xpv6ydvS6FQCfY/yHJPyvndPGRvaOYjOVoQw7 fHIAoOxL/0umAS9RJO/9aA9RX9YhIRa8 =p7Ej -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] A/D video converter DFG/1394-1e with unicap
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-01-10 15:27, kubro bubro wrote: hello last year we was trying to run firewire A/D video converter DFG/1394-1e with unicap in gem whitout success. there are three unicap backend is highly experimental (mainly because i never managed to have a proper installation of unicap on my system...even the applications that are bundled with unicap don't work properly!) however, do you really need the unicap backend? Gem has built in support for dv (videoDV4L) and iidc (videoDC1394), one of which should work with your device (presumably dv4l) maybe it will just work if you remove the unicap plugin entirely (so it cannot claim the device), and use [device /dev/fw1( fgmasrd IOhannes PS: and yes, Pd bails out because of the GOPs inside the [pd properties] subpatch; this is a bug in Pd (and should not create a real problem) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEUEARECAAYFAk8MTfcACgkQkX2Xpv6ydvQFeACgjciJ9Au1FvDtkFynhUYaJ/0j GHsAkweQeRqNF5m/4Y+GLr8PYgBTxTo= =3FQm -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
[GEM-dev] announce: assimp model loader
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 i just pushed a changeset to sourceforge, that adds some possibilities to 3d model loading to Gem. first, model-loading is now factored out into plugins as well. the old .obj loader code has been ported into a new gem_modelOBJ plugin. then i tried to create another asset importer plugin based on assimp. the plugin is (not surprisingly) called gem_modelASSIMP. assimp [1] should allow us to read a large number of 3d model formats (including dfx, 3ds, md5, blender, collada,...) what works: - - loading of models - - UV-textures what needs to be done: - - check for other texcoord generations. - - allow feedback on which textures should be loaded - - probably do the texture loading within the model-importer (on user-request) - - implement animations - - improve performance cudos to hans for bringing assimp to my attention. check and have fun (and report back any problems...) fg,asdr IOhannes [1] http://assimp.sourceforge.net there are also debian packages, and ubuntu (starting with precise(!)) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8F7YIACgkQkX2Xpv6ydvTwtwCgyE8VPOReImeMmypUSJru4Qig 7IIAn1ZOYqVRe7SgsNaGfe77Uzm8//ER =NhqH -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] vertexbuffer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-12-27 21:47, cyrille henry wrote: hello, I commit few change in the vertexbuffer branch. it look like it's ready to be merged with the master. Iohannes, could you check and merge it if you agree? i reviewed the code, and tried to do it nicer :-) changes so far: - - proper initialization of all class members - - created class that contains all the data for a single VBO; which can then be reused for position/color/... - - single messages to set all data of a VBO in one go; e.g. position tabX tabY tabZ rather than posX tabX, posY tabY, posZ tabZ - - allow interleaved data, e.g. position tabXYZ - - i really dislike the name posVBO_enable: where the hell does VBO come from? changed it to position_enable (et simil.) - - updated the help-patch please check whether it still performs as intended. if it's ok, i'll include it. fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8B3f4ACgkQkX2Xpv6ydvS2SQCgjeHrXQcAjx8cKIlJxGM0Kd7I +2QAoMWyKlL5z/OeAEbMBamJSrNmaPk7 =dgCz -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
[GEM-dev] ann: videoVLC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gem now has a videoVLC plugin, that allows to open any medium playable by VLC to be opened as a video-device, by specifying the vlc-URI as the device e.g. using [device screen://( will grab the screen and make that available as video stream. tested on linux and w32. fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7yD9wACgkQkX2Xpv6ydvQFigCfd0Et09sh12wfhfLmZRGgYlEt xZcAn16wC0g7l90sgvvLCxXcbrhTYTAZ =GYmB -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] pull_request - pix_noise
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-12-15 13:35, Nicolas Montgermont wrote: Le 14/12/11 15:54, IOhannes m zmoelnig a écrit : btw, i pushed a cleaned up version. The [Grey( message is now generating a blue image. unable to reproduce. [GREY(, [GRAY(, [grey( and [gray( all produce greyscale images, with no need to [bang(, [set( or whatever. fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7p8BgACgkQkX2Xpv6ydvRAiQCggUZVqB8zWCq1C9JJuvl5b9c8 xigAn0yMbPpIGb8FTHNZpsBgWKp7vZyG =iwFM -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] pull_request - pix_noise
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-12-15 14:47, Nicolas Montgermont wrote: Le 15/12/11 14:03, IOhannes m zmoelnig a écrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-12-15 13:35, Nicolas Montgermont wrote: Le 14/12/11 15:54, IOhannes m zmoelnig a écrit : btw, i pushed a cleaned up version. The [Grey( message is now generating a blue image. unable to reproduce. [GREY(, [GRAY(, [grey( and [gray( all produce greyscale images, with no need to [bang(, [set( or whatever. using pix_noise-help.pd patch and clicking on the message create and then on the message GREY Macbook Pro 2.4GHz osx 10.6.8 Pd-extended-0.42.5 Gem ver: 0.93.git 5284ad0 i had a look and found the following: - - the code was always buggy :-) - - it used fixed color offsets within pixels (e.g. 3 for blue), which is simply wrong on OSX. Gem has special constants chRed,... for platform independent color offsets. - - i also changed the color-type from GL_RGBA to GL_RGBA_GEM, which will actually do the same (GL_RGBA on w32linux and GEM_BGRA_EXT on osx) but with less confusion :-) fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7qG1oACgkQkX2Xpv6ydvSfjwCgqNv008XJ/H8sVwqteNdGFEiK L+oAn18msJ18kBYF6X6dOoP9CpfECQIj =7Enf -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] build plugins
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-12-15 20:18, IOhannes m zmoelnig wrote: plugins will only get build if you have the proper libraries installed. e.g. you will need to have gmerlin-avdec-dev installed in order to get a filmGMERLIN plugin (which will be called gem_filmGMERLIN.so) but you should always get the imageSGI plugin, as it doesn't depend on any external library. fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7qSBMACgkQkX2Xpv6ydvTX7gCgsf26YB7RhGTFWcrZJiy0pGcm mZIAoLPBVRCuhPevG/vakGKZDCkT7jZO =EuPd -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] pull_request - pix_noise
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-12-14 12:51, Jack wrote: Iohannes pointed, it was correlated on big texture. It seems ok now. Hope that'll help! Best n Good news ! It could be useful for shaders too. ++ btw, i pushed a cleaned up version. fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7ouLwACgkQkX2Xpv6ydvQHLACgqVyOB8XO7ob88owA6kW907wF eKUAniiAN+NH470QNDR9vEa9ZrQbWzEZ =JYR8 -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
[GEM-dev] Gem MinGW
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 as you might have noticed there have been some bug tickets regarding MinGW in the last days. you might also have noticed that all of them have been set to pending/fixed. this basically indicates, that it is now possible to compile Gem on MinGW. what is working: - - Gem *core* compiles - - Gem loads - - this means that all objects are available - - the plugin mechanism works what is not working: - - you'll not be able to load a plugin compiled with VisualC++ into a MinGW-compiled Gem or vice versa (at least as long as there is no C-API for plugins) - - what will need some more work DirectShow image acquisition (videoDS, filmDS) will need to be reimplemented for MinGW...hopefully in a way that allows the new implementations to be used with the M$VC builds as well... what is unknown/untested: - - i haven't had any libraries additional libraries installed thus i don't know, how much work the following still needs: FTGL-, QuickTime-, JPEG-, TIFF-, ImageMagick-,... support (actually, the only plugins i was able to test were imageSGI (for which i lacked a test image to load) and videoVFW (which does not support my camera) chances are high, that most of these libraries will just work. mmgfasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7oyysACgkQkX2Xpv6ydvS8WgCg88Rf7+88xl5fRySkPm1Cj9jM kuAAoIBsAliCrFFxeKP+poA6xGmAPdx2 =tvuT -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] pix_write Pull request
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-12-07 16:22, IOhannes m zmoelnig wrote: maybe it's time to wrap that up into a CodingStyle.txt file :-) http://pd-gem.git.sourceforge.net/git/gitweb.cgi?p=pd-gem/Gem;a=blob;f=doc/CodingStyle.txt fmasr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7fkbYACgkQkX2Xpv6ydvToKwCfRE5zFbUM01BdpHeCp+WkTS6P 7e8AoLAjYgatYgYsyegQC7qCSQOUTStr =oiB5 -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] help files update - git
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-12-05 20:06, Nicolas Montgermont wrote: Hello Iohannes / list, I've worked on a few help files. It was mainly help files that were not in the Gem format. I've done that using git. You can find them here: g...@github.com:nixhol/Gem.git the name of the branch is: help-files I've cloned the Gem sourceforge repository, then i've created a branch, worked on the files, and then i've pushed my modifs on my github repository. Is this the good workflow for contributing to Gem using git? or do you prefer another way? yes, i think this is the best way to contribute to Gem. i incorporated your fixes and pushed to sourceforge. i'm not yet sure whether it is best to _merge_ your branch into master or to _rebase_ it onto master. for know i prefer a rebase (if possible), but if that makes problems for somebody i could do merges as well. gamsd IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7eLIgACgkQkX2Xpv6ydvQ6NQCeNv395DdyWXIlvGsRUz4ofd04 hPkAniQB10HEeAe9oz0gtLHCsg9nwtTF =dpsr -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] pix_write relative path - osx
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-12-01 20:24, Hans-Christoph Steiner wrote: Of course don't add dependencies that are not needed. You mentioned that pix_multiblob outputs data that vanilla objects don't handle well, so it seems relevant. I am saying its silly to avoid using iemmatrix in pix_blobtracker-help.pd since pix_blobtracker.pd already depends on it. it's not deliberately avoided. there is just no need to use it. fgmadr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7X1l4ACgkQkX2Xpv6ydvQXogCePwmZsOcs546PcuFlsV9XHUMY 7Y0AnA1ZA6pbpmQBu8F5p2wMqo9VseOH =Mi3X -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] pix_write relative path - osx
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-11-30 11:52, cyrille henry wrote: hello, getdir should not be included in Gem help file because it's not vanilla. sure. jack and me were mainly suggesting a workaround to get things going no. if we can't provide a pix_write help patch that is working for everybody, then it's a bug. a better workaround have to be found. oh sure. nobody doubts that the help-patch should be working everywhere (as long as it supposed to be a working help-patch, which not all help-patches arelooking at pix_write-help.pd is see that this is one of them) fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7WD/AACgkQkX2Xpv6ydvSNMwCgoJRWpXSpF2Z/3a67NyMfhoGv HwUAn2IpY3vT+CzTaYGng5sLoqaK1y7q =foZN -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] 0.93.4?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-11-29 20:02, Hans-Christoph Steiner wrote: Hey IOhannes, With the pix_write bug, do you have any plans to release a 0.93.4? no, there is a download for a fixed imageQT plugin available at [1]. fgmasdr IOhannes [1] http://gem.iem.at/releases/0.93.3/imageQT.tgz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7VPDAACgkQkX2Xpv6ydvThNwCg6rkjTTLtSE5S6mD/r9FwAQpi TGAAnjcjq7pRCmpe3XyEqI0AtASOEnOy =ozuF -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] Gem and Optimus
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-11-08 12:10, Jack wrote: Hello, It's a good new for me today. I can now use the NVidia graphic card on my Optimus laptop with Gem and Bumblebee. Before when i launched pd and gem with : $ optirun pd-gem Pd crashed very often. Until this morning (with an upgrade of different openGL library on my Ubuntu 11.04) i can launch pd and Gem without problem. This is nice ! :) So people who have laptop with Optimus should upgrade their openGL library today and install the last Bumblebee. which version of bumblebee and openGL/nvidia-drivers do you have installed for a success? fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7CK58ACgkQkX2Xpv6ydvTSjwCfaY+fQ5kspN+NIB/BjgNA4yo5 9d0AoLrMUZA1KMC5pJR+nNMsCfRwPLHn =9hCB -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] Gem and Optimus
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-11-15 13:04, Jack wrote: Le 15/11/2011 10:06, IOhannes m zmoelnig a écrit which version of bumblebee and openGL/nvidia-drivers do you have installed for a success? $ dpkg -l | grep OpenGL thx fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7CbY0ACgkQkX2Xpv6ydvRf2gCfZjxqrptGLKtUjjb6pKqGiAHH 2c8An1aAhUuOHRd88eXzyMJa3fhOlrQB =U2Z4 -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] Gem and Optimus
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-11-15 12:33, Benjamin ~ 01xy wrote: Hello, yes, good news :) ... but one question, what is this command : pd-gem ? a special compiled pd+gem version ? no, it's a script that comes with the debian(ubuntu) package for Gem which makes sure that the debian-installed version of puredata and the debian-installed version of Gem are used. fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7CbdgACgkQkX2Xpv6ydvTJNgCfWDulZhbWFW+tsuCGQr0l2M72 R/IAoNp6N4165HNnZPsgEJncdyVpQyWA =X1YQ -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] new pix_colordetect
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-11-11 16:23, Ricardo Fabbri wrote: sorry for the typos... writing from mobile.. On Friday, November 11, 2011, Ricardo Fabbri rfab...@gmail.com wrote: Hello, IOhannes, glad to hear it can be useful. It could also be called pix_colorclassify or pix_colorclass, since it outputs 6 color classes 'red', green', ..., i would go for [pix_colorclassify]. if you agree and are willing to change the name in your branch, i'll import it as is. 'white' (and a seventh 'not sure' class label). However, to me the output is in symbolic form. The 'red' symbol is encoded as [1 0 0] and so on. makes sense. some more remarks (without having looked at the code in detail, so i might be asking for things already there) - - it would be great if the user could modify those labels. e.g. [1 0 0] sounds like a great label for red, but some weird user might chose to prefer [0.5 1 0.8]. it would also be nice to be able to parameterize the detection code, but i guess it is too fine tuned to the six given classes (so it would both complicate things from the dev's and the user's povs) fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7BMB4ACgkQkX2Xpv6ydvSPawCfcHHRavRQh5exECfF4S1noim+ iukAoMpVYNd1zeeenVhRYmyHwUtNT+E8 =ajwb -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] output of multiple matrices
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-11-10 05:10, Ricardo Fabbri wrote: Hi, how would I output multiple images (multiple image outlets) in a Gem external object in C++? if this is straightforward and documented, just let me know and I will figure it out. it should be straightforward and is definitely not documented. this has been asked before on this list, so it seems that there is indeed a problem. mfat IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk67hssACgkQkX2Xpv6ydvTWIQCg0vhQnVWH9IEthGDI8X4Nb6Vq W1IAnR3twCFUsvHV3J8m2ZX72SApMt4M =R6Xo -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
[GEM-dev] Gem-crash with string concatenation (was Re: gemframebuffer flood)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-10-27 20:44, cyrille henry wrote: hum, this did not tell that i use ubuntu 64 bit. indeed, it did not tell that. i tried to compile/run Gem on a 64bit debian installation, and indeed it crashes! please report a bug. fgvamnsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6ueTAACgkQkX2Xpv6ydvRvogCgvSdoDuWG1jvtHpBduiLZJr/P rJwAnRuopRt3AR01eMH4NagwaFP53bt/ =t+fW -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] Gem-crash with string concatenation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-10-31 11:32, IOhannes m zmoelnig wrote: On 2011-10-27 20:44, cyrille henry wrote: hum, this did not tell that i use ubuntu 64 bit. indeed, it did not tell that. i tried to compile/run Gem on a 64bit debian installation, and indeed it crashes! i think the problem is the CPU capabilities detection code (which tries to determine whether your CPU is capable of running e.g. SSE2 code) given that any x86_64 CPU on the market supports SSE2 (and SSE and MMX), i disabled that check on this architecture for now. at least, this fixed the problem here. fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6ulzgACgkQkX2Xpv6ydvThoQCeNQ2nYCidjNKNWUnTpX+CKOHW +ZoAoIZm3YzyPC3JBliOMiulT3L/YKF0 =DMUL -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] gemframebuffer flood
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-10-25 19:00, cyrille henry wrote: sorry, i forget to reply to list. so, latest git did not compile. i add 2 ; in order to compile. doh! i had only MMX enabled when compiling, so i didn't catch it... should be fixed now. but this did not really solve my problem. hmm... in this case i need more info about your system (architecture, configure flags, compiler flags,...) msdf IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6pCJgACgkQkX2Xpv6ydvTb7QCglLveaV68ec8gQ5LdtoncWxXq HlgAoOeFWJfNpLWpDhtFfrXjdzjHwRue =lNdf -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] gemframebuffer flood
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-10-25 12:24, cyrille henry wrote: about bugs to be fixed comment in this patch : 1 - should be fixed since yesterday thanks to Iohannes 2 - i don't think i have this problem on my computer. (i add a translate on the scene B in order to have the square cut by the edge of the windows, and the blur did not appear on the other side of the window.) see : http://chnry.free.fr/blur.png did i miss the problem, or did it work better on my computer than on your's? as said, i couldn't see it either. then i played around a bit, and manged to produce this [1]. @guido: is that what you mean? fgmasdr IOhannes [1] http://iem.at/~zmoelnig/GEM/blur.png -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6mkBQACgkQkX2Xpv6ydvToOwCgxuV4DoNpNqK/Wkwxbccc03aS dQYAn2B9wRRPP8CDvjWZJzQaJmRDLDpW =C9aK -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] getting latest Gem into Pd-extended
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-10-23 19:51, Hans-Christoph Steiner wrote: On Oct 23, 2011, at 12:05 PM, IOhannes m zmölnig wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/21/2011 09:23 PM, Hans-Christoph Steiner wrote: The GNU/Linux issue is fixed, with the __sync_bla_bla symbol. when? by whom? how? you reported that bug, no changes happened on the Gem side, and 3 days lated, magically, the issue is fixed? sorry that i got confused... I caused the problem by adding CPU/optimization flags to Gem's CXXFLAGS in externals/Makefile. I posted on some thread about it, I thought it was this one. To fix it, I just removed that change. http://pure-data.svn.sourceforge.net/viewvc/pure-data/trunk/externals/Makefile?r1=15612r2=15619 ah, thanks for the clarification. after re-reading the thread i notice that you mentioned that you removed that, but haven't tested it again yet. this was eventually overlooked by me, as it was in the same email with the 2 (then 3) questions for definitive answers. fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6lEmAACgkQkX2Xpv6ydvTEPACeNk/A6N6IU8ul0cU4NPLFD83U E9YAoN4l0BAa3g4lYTXuagJm5U1jFpmV =WBPB -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] getting latest Gem into Pd-extended
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-10-18 21:47, Hans-Christoph Steiner wrote: Hey IOhannes, I would like to include the latest version of Gem in Pd-extended 0.43. It currently needs a little work. It builds on GNU/linux, but gives a missing symbol (something like _sync_foo_bar). it builds on GNU/linux without the missing symbols as well, else i coulldn't use it myself :-) i assume that this is on some ubuntu flavour (which one), with a certain compiler version (which one) and some special C(XX)FLAGS. according to the internet, adding something like -march=i486 to the C(XX)FLAGS should help. It doesn't build on Mac OS X 10.5. what does latest Gem mean here? the git version (which is indeed the 'latest') of Gem has the issue fixed. the 'svn' version (both trunk and branch/0.93) and the releases have it not fixed (yet). if you want/must stick to the current release (which is fair enough) or svn, a very simple workaround would be to add /sw/bin to the beginning of the PATH before calling Gem's autogen.sh fgmasdrt IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6f11QACgkQkX2Xpv6ydvR2rQCeJcrbm+ylRw0HLbMxORutCrNJ 4U8AoLBoobx8gVr62cxGaQYuSBzFrJk/ =zYps -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] compiling gem on arch linux
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-10-11 19:17, kubro bubro wrote: i do make with -j 4 argument to have faster result with my 4core [...] but every time it ends with: make[2]: Entering directory `/home/kubriel/Downloads/Gem-0.93.0/extra' make[2]: Nothing to be done for `all-am'. make[2]: Leaving directory `/home/kubriel/Downloads/Gem-0.93.0/extra' make[1]: Leaving directory `/home/kubriel/Downloads/Gem-0.93.0/extra' make[1]: Entering directory `/home/kubriel/Downloads/Gem-0.93.0' make[1]: Nothing to be done for `all-am'. make[1]: Leaving directory `/home/kubriel/Downloads/Gem-0.93.0' make: *** [all-recursive] Error 1 using -j4 is nice to speed up things, but it makes finding errors harder. in order to get reasonable information at a reasonable speed, run a non-parallelized make right after the failed build with -j4. something like $ make -j4 $ make then you should be able to give us information where it actually failed. the same error with make install. i have to add -I /usr/include/ImageMagick to find image magick headers shouldnt make install just copy compiled stuff to prefix directory? it will do so, if the build has succeeded. if the build is not complete yet, it will first try to finish it. since your build stopped with an error, it did not complete yet. fgasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6WolIACgkQkX2Xpv6ydvQ6DwCfddCioIusLl5kNX8U6NneboZL FgoAoJe5AjOptCYQspPtFZ0uysOOazu7 =vZHy -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] compiling gem on arch linux
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-10-11 19:17, kubro bubro wrote: there is another confusion. in README.txt in gem directory seems like old. it says it is 0.91 version, and that: To install GEM on linux: chdir into Gemdir/src/ read the README.os (like README.linux) etc... but there is not README.linux anymore in src directory yes, that file has been deleted :-) the documentation was unfortunately not updated before the 0.93.0 release. speaking of which: why are you using 0.93.0? there is a 0.93.1 release available. micro release numbers indicate bugfixes... fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6Wom8ACgkQkX2Xpv6ydvR0iACg9KhcfnhYTNUixFBKsL1zkRh9 OOcAnjkWe7XOjlGIIJHIYkAQmm+1dXGz =aTzj -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
