Re: [PD] pix_film frame control offset 8 MacOsX
hm - beware for update 10.6.5 released nov 2010 - fits to my experience - i had no problems last summer with synchronization of video + sound. i tested also on MacPro and different MacBook Pro with 10.6.6 same issue. even update to 10.6.7 didn´t solve the problem. m Am 22.03.2011 um 13:37 schrieb chris clepper: I tested this on 10.6.4 and the latest Pd-Extended and did not see this problem. On Sun, Mar 20, 2011 at 3:02 PM, Matthias Neuenhofer matth...@neuenhofer.de wrote: Dear list, i recognized that pix_film have an offset of 8 when trigger with frame number on 2. inlet. When video is loaded the 1. frame is visible and stay sending 1 - 8. Number 9 render the 2. frame, 10 the 3. frame … but i can´t get back the 1. frame this is only shown up with loading. It´s also not possible to get the last 7 frames. The length of the video in the console is printed correct when opened. Can somebody confirm this. I´m working on MAc OsX 10.6.6 and tried pd-extended 0.43, 0.41rc4 and latest 0.42. all the same behavior. Can´t remember on which version of MacOs it worked correct last. For easy testing here a 100 frame mov counting 0-99 http://matthias.neuenhofer.de/_testMOV/_testF75mov.zip lg Matthias ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] pix_film frame control offset 8 MacOsX
Dear list, i recognized that pix_film have an offset of 8 when trigger with frame number on 2. inlet. When video is loaded the 1. frame is visible and stay sending 1 - 8. Number 9 render the 2. frame, 10 the 3. frame … but i can´t get back the 1. frame this is only shown up with loading. It´s also not possible to get the last 7 frames. The length of the video in the console is printed correct when opened. Can somebody confirm this. I´m working on MAc OsX 10.6.6 and tried pd-extended 0.43, 0.41rc4 and latest 0.42. all the same behavior. Can´t remember on which version of MacOs it worked correct last. For easy testing here a 100 frame mov counting 0-99 http://matthias.neuenhofer.de/_testMOV/_testF75mov.zip lg Matthias ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] pix_film frame control offset 8 MacOsX
hi tim video is 720x576 Foto JPEG with 75% compression aspect ratio is 1.25 - normal for dv or mpg2 can you try this 768x576 same compression - aspect ratio 1.33 http://matthias.neuenhofer.de/_testMOV/_testF75qmov.zip lg Matthias Am 20.03.2011 um 20:34 schrieb tim vets: hi, f.y.i., I wanted to check this, but opening that video with [pix_film] crashes pd instantly here, saying: tk scaling is 1.12537210107 swScaler: Exactly one scaler algorithm must be chosen socket receive error: Connection reset by peer (104) Segmentation fault ubuntu Maverick, Pd-extended 0.42.5, Gem ver: 0.92.3 it plays fine with mplayer. gr, Tim 2011/3/20 Matthias Neuenhofer matth...@neuenhofer.de Dear list, i recognized that pix_film have an offset of 8 when trigger with frame number on 2. inlet. When video is loaded the 1. frame is visible and stay sending 1 - 8. Number 9 render the 2. frame, 10 the 3. frame … but i can´t get back the 1. frame this is only shown up with loading. It´s also not possible to get the last 7 frames. The length of the video in the console is printed correct when opened. Can somebody confirm this. I´m working on MAc OsX 10.6.6 and tried pd-extended 0.43, 0.41rc4 and latest 0.42. all the same behavior. Can´t remember on which version of MacOs it worked correct last. For easy testing here a 100 frame mov counting 0-99 http://matthias.neuenhofer.de/_testMOV/_testF75mov.zip lg Matthias ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] strange colors with pix_record
yes the RGBA channels are set wrong on mac osx. the cube appears blue because the alpha channel is read as blue. when you change channels like this R – G G – R B – A A – B the movie will justified. but it´s not handy to give each record this process so i fixed this with a change in the code of recordQT.cpp in line 241 - instead of colorspace = k32BGRAPixelFormat; i use colorspace = k32ARGBPixelFormat; but i don´t know how this affects other os also the recorded mov is upside down - this can fix in quicktime pro with a click in the properties of the video track - so i don´t looked for the code issue. matthias Am 02.04.2010 um 03:33 schrieb Mathieu Bouchard: Johannes a écrit : you can file a bug report even if it only happens on a single operating system. I think Max implied that he wanted to submit a report as complete as possible up front. the recording code is highly platform specific (that is: the recording backends are platform specific), so it might well be that there is a bug on one system not showing up on others. Yes, therefore it would also be a good idea to have a screenshot, especially one containing a correct picture and the equivalent broken picture side to side. That way, for example, someone who doesn't have the OS required to run the bug, can still fix the bug by just looking at the screenshot. But this requires an example with enough different colours... just grey is not enough. For example, this picture : http://webilus.com/wp-content/uploads/2007/11/216couleurs_du_web.jpg has more colours than one would ever need, to identify the problem, so, it's perfect for that. _ _ __ ___ _ _ _ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] strange colors with pix_record
hi max in your patch you use the jpeg codec for recording in this mode you can change the colourmode to YUV with pix_yuv before pix_record. the bug affects only the rgba mode - but when you use a codec without alpha channel this is a easy workaround. this was discussed in the list 2008: http://lists.puredata.info/pipermail/pd-list/2008-03/060168.html matthias Am 03.04.2010 um 00:52 schrieb Max: that version of GEM GEM: ver: 0.92.2 GEM: compiled: Jan 20 2010 unfortunately doesn't have a pix_recordQT pix_recordQT ... couldn't create m. Am 01.04.2010 um 21:25 schrieb chris clepper: The Quicktime code being used in recent GEM builds is not the code I wrote, and does not work that well. Can you try pix_recordQT and see if that loads? On Wed, Mar 31, 2010 at 10:03 AM, Max abonneme...@revolwear.com wrote: Hi List, i wonder why i get these strange colors when using pix_record with GEM ver: 0.92.2 compiled: Jan 20 2010 on OS X 10.6.3 Any Ideas? this is grayscale in GEM but instead it is quite blue in the recorded quicktime. ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] strange colors with pix_record
Am 03.04.2010 um 18:13 schrieb Max: Am 03.04.2010 um 14:32 schrieb chris clepper: Setting the quality for Photo-JPEG to 100% changes it from YUV to lossless ARGB compression. You can keep the alpha and avoid colorspace conversion. Use the 'dialog' message to do this. but Photo-JPEG has no alpha channel - don't get it. the point is that pix_record when it´s feed with rgba output a video where the channels are swap feed with yuv the colors are ok doesn´t matter in which mode the codec record the video wow - dialog, select Photo - JPEG, click on options -freezes the dialog. also: changing the compression closes the gemwin m. also on my machine mac osx 10.6.2 GEM: ver: 0.92.2 compiled: Dec 17 2009 Gem stop rendering confirm the dialog to pix_record after start rendering again 2 sec later it stop again then start again it´s ok and use the changes of the dialog matthias ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] call for testing: Pd-extended 0.41.4
I think it went to svn via Cyrille. What to do geting the release state? Marius posted a patch in the feedback discussion yesterday where he mentioned inside (feedback_filter) better quality with perspec message enable. Matthias Am 02.04.2009 um 00:34 schrieb Hans-Christoph Steiner: Hmm, I don't know about that. Let's keep it on the list so that others can participate in the discussion. Is this perspec message in the latest Gem release, or just in SVN? This release of Pd- extended will included the last release of Gem. .hc On Apr 1, 2009, at 6:09 PM, Matthias Neuenhofer wrote: Hallo Hans the gemframebuffer object miss the perpec message possibility to change frustum of the buffer. I send the code to gem-dev list and got positive feedback. Would be nice to have it in nightly ex :) Matthias Am 01.04.2009 um 18:52 schrieb Hans-Christoph Steiner: Hey, I think Pd-extended 0.41.4 is basically ready to release. Before I make a release candidate, I'd love to have some feedback on the current nightly builds. You can find the latest successful builds for each platform here: http://autobuild.puredata.info/auto-build/latest/ .hc Mistrust authority - promote decentralization. - the hacker ethic ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list Access to computers should be unlimited and total. - the hacker ethic ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] recursive video feedback in GEM or PDP?
there is the example 09.sharedTextures in 07.texture Matthias Am 01.04.2009 um 04:12 schrieb Claude Heiland-Allen: Ben Baker-Smith wrote: Also, if someone could fill me/everyone in about what the [pix_texture] second inlet is for, that would be fantastic. It's a texture id if I remember rightly, so you can have multiple [pix_texture] objects that share the same texture data (so it only needs to be loaded into graphics memory once, saving both space and time). Claude -- http://claudiusmaximus.goto10.org ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Gem-0.91-3 pd 0.42-4
in the glew.ccp line 83 the (char*) is missing before malloc symbolName = (char*)malloc(strlen((const char*)name) + 2); matthias Am 26.03.2009 um 15:36 schrieb thomas thiery: Thank you, I test the compilation and I have this error when I compile g++ -c -g -O2 -fPIC -freg-struct-return -Os -falign-loops=32 - falign-functions=32 -falign-jumps=32 -funroll-loops -ffast-math - mmmx -fpascal-strings -I.. -I/Applications/Pd-0.42-4.app/Contents/ Resources/src glew.cpp -o ../Objects/glew.o glew.cpp: In function ‘void* NSGLGetProcAddress(const GLubyte*)’: glew.cpp:80: warning: ‘NSAddImage’ is deprecated (declared at /usr/ include/mach-o/dyld.h:230) glew.cpp:80: warning: ‘NSAddImage’ is deprecated (declared at /usr/ include/mach-o/dyld.h:230) glew.cpp:83: error: invalid conversion from ‘void*’ to ‘char*’ glew.cpp:89: warning: ‘NSLookupSymbolInImage’ is deprecated (declared at /usr/include/mach-o/dyld.h:182) glew.cpp:89: warning: ‘NSLookupSymbolInImage’ is deprecated (declared at /usr/include/mach-o/dyld.h:182) glew.cpp:91: warning: ‘NSAddressOfSymbol’ is deprecated (declared at /usr/include/mach-o/dyld.h:188) glew.cpp:91: warning: ‘NSAddressOfSymbol’ is deprecated (declared at /usr/include/mach-o/dyld.h:188) make[1]: *** [glew.o] Error 1 make: *** [Base] Error 2 I can't make an interpretation of this 2009/3/26 IOhannes m zmölnig zmoel...@iem.at thomas thiery wrote: Hello IOhannes, I use this source of Gem, is it the last? http://downloads.sourceforge.net/pd-gem/gem-0.91-3.tar.gz?use_mirror=heanet it's the last official release (which does not take the peculiarities of 0.42 into account) however, the latest and greatest sources are always available via our version control system (subversion https://pd-gem.svn.sourceforge.net/svnroot/pd-gem/trunk/Gem) mfga.sdr IOhannes ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list -- Matohawk production http://matohawkitongroup.free.fr ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] wiiremote for Mac OS X
i got the same now with the version 1.0B6 from april. the version i got build but not work was 1.04B from december. mn Am 23.05.2007 um 04:54 schrieb Hans-Christoph Steiner: My guess is that I missed something in the port. There are a ton of warnings, maybe one of them holds the key to the problem. Here's what I get when compiling: cc -DPD -O2 -I /Users/pd/auto-build/pd-extended/pd/src -Wall -W - ggdb -I/sw/include -DMACOSX -DUNIX -Dunix -o aka.wiiremote.o -c aka.wiiremote.c aka.wiiremote.c:43: warning: no semicolon at end of struct or union aka.wiiremote.c: In function 'akawiiremote_foundFunc': aka.wiiremote.c:275: warning: unused parameter 'x' aka.wiiremote.c: In function 'akawiiremote_motionsensor': aka.wiiremote.c:299: warning: unused variable 'status' aka.wiiremote.c: In function 'akawiiremote_irsensor': aka.wiiremote.c:309: warning: unused variable 'status' aka.wiiremote.c: In function 'akawiiremote_expansion': aka.wiiremote.c:319: warning: unused variable 'status' aka.wiiremote.c: In function 'akawiiremote_vibration': aka.wiiremote.c:329: warning: unused variable 'status' aka.wiiremote.c: In function 'akawiiremote_led': aka.wiiremote.c:339: warning: unused variable 'status' aka.wiiremote.c: In function 'akawiiremote_assist': aka.wiiremote.c:490: warning: unused parameter 'x' aka.wiiremote.c:490: warning: unused parameter 'b' aka.wiiremote.c:490: warning: unused parameter 'm' aka.wiiremote.c: In function 'akawiiremote_new': aka.wiiremote.c:510: warning: unused parameter 's' cc -DPD -O2 -I/Users/pd/auto-build/pd-extended/pd/src -Wall -W - ggdb -I/sw/include -DMACOSX -DUNIX -Dunix -o wiiremote.o -c wiiremote.c wiiremote.c: In function 'myFoundFunc': wiiremote.c:234: warning: unused parameter 'inquiry' wiiremote.c: In function 'myUpdatedFunc': wiiremote.c:239: warning: unused parameter 'inquiry' wiiremote.c:239: warning: unused parameter 'devicesRemaining' wiiremote.c: In function 'myCompleteFunc': wiiremote.c:246: warning: unused variable 'ret' wiiremote.c:244: warning: unused parameter 'inquiry' wiiremote.c: In function 'wiiremote_search': wiiremote.c:282: warning: 'IOBluetoothDeviceInquiryCreateWithCallbackRefCon' is deprecated (declared at /System/Library/Frameworks/IOBluetooth.framework/ Headers/IOBluetoothUserLib.h:2843) wiiremote.c:282: warning: 'IOBluetoothDeviceInquiryCreateWithCallbackRefCon' is unavailable (declared at /System/Library/Frameworks/IOBluetooth.framework/ Headers/IOBluetoothUserLib.h:2843) wiiremote.c:283: warning: 'IOBluetoothDeviceInquirySetDeviceFoundCallback' is deprecated (declared at /System/Library/Frameworks/IOBluetooth.framework/ Headers/IOBluetoothUserLib.h:2894) wiiremote.c:283: warning: 'IOBluetoothDeviceInquirySetDeviceFoundCallback' is unavailable (declared at /System/Library/Frameworks/IOBluetooth.framework/ Headers/IOBluetoothUserLib.h:2894) wiiremote.c:284: warning: 'IOBluetoothDeviceInquirySetDeviceNameUpdatedCallback' is deprecated (declared at /System/Library/Frameworks/ IOBluetooth.framework/Headers/IOBluetoothUserLib.h:2914) wiiremote.c:284: warning: 'IOBluetoothDeviceInquirySetDeviceNameUpdatedCallback' is unavailable (declared at /System/Library/Frameworks/ IOBluetooth.framework/Headers/IOBluetoothUserLib.h:2914) wiiremote.c:285: warning: 'IOBluetoothDeviceInquirySetCompleteCallback' is deprecated (declared at /System/Library/Frameworks/IOBluetooth.framework/ Headers/IOBluetoothUserLib.h:2924) wiiremote.c:285: warning: 'IOBluetoothDeviceInquirySetCompleteCallback' is unavailable (declared at /System/Library/Frameworks/IOBluetooth.framework/ Headers/IOBluetoothUserLib.h:2924) wiiremote.c:291: warning: 'IOBluetoothDeviceInquiryStart' is deprecated (declared at /System/Library/Frameworks/ IOBluetooth.framework/Headers/IOBluetoothUserLib.h:2864) wiiremote.c:291: warning: 'IOBluetoothDeviceInquiryStart' is unavailable (declared at /System/Library/Frameworks/ IOBluetooth.framework/Headers/IOBluetoothUserLib.h:2864) wiiremote.c:294: warning: 'IOBluetoothDeviceInquiryDelete' is deprecated (declared at /System/Library/Frameworks/ IOBluetooth.framework/Headers/IOBluetoothUserLib.h:2854) wiiremote.c:294: warning: 'IOBluetoothDeviceInquiryDelete' is unavailable (declared at /System/Library/Frameworks/ IOBluetooth.framework/Headers/IOBluetoothUserLib.h:2854) wiiremote.c: In function 'wiiremote_stopsearch': wiiremote.c:310: warning: 'IOBluetoothDeviceInquiryStop' is deprecated (declared at /System/Library/Frameworks/ IOBluetooth.framework/Headers/IOBluetoothUserLib.h:2874) wiiremote.c:310: warning: 'IOBluetoothDeviceInquiryStop' is unavailable (declared at /System/Library/Frameworks/ IOBluetooth.framework/Headers/IOBluetoothUserLib.h:2874) wiiremote.c:317: warning: 'IOBluetoothDeviceInquiryDelete' is deprecated (declared at /System/Library/Frameworks/
