<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">yes the RGBA channels are set wrong on mac osx. the cube appears blue because the alpha channel is read as blue.<div>when you change channels like this </div><div><span class="Apple-style-span" style="font-size: 12px; ">R –> G </span></div><div><span class="Apple-style-span" style="font-size: 12px; ">G –> R </span></div><div><span class="Apple-style-span" style="font-size: 12px; ">B –> A </span></div><div><span class="Apple-style-span" style="font-size: 12px; ">A –> B</span></div><div><span class="Apple-style-span" style="font-size: 12px; "></span>the movie will justified. but it´s not handy to give each record this process so <br><div>i fixed this with a change in the code of recordQT.cpp in line 241 - instead of <span class="Apple-style-span" style="color: rgb(1, 1, 2); font-family: Menlo; font-size: 11px; ">colorspace = k32BGRAPixelFormat;</span></div><div><div><div>i use <span class="Apple-style-span" style="color: rgb(1, 1, 2); font-family: Menlo; font-size: 11px; ">colorspace = k32ARGBPixelFormat;</span></div><div>but i don´t know how this affects other os</div><div><br></div><div>also the recorded mov is upside down - this can fix in quicktime pro with a click in the properties of the video track -</div><div>so i don´t looked for the code issue.</div><div><br></div><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; ">matthias</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; "><br></div></div></div></div></div><div><div>Am 02.04.2010 um 03:33 schrieb Mathieu Bouchard:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br>Johannes a écrit :<br><br><blockquote type="cite">you can file a bug report even if it only happens on a single operating<br></blockquote><blockquote type="cite">system.<br></blockquote><br>I think Max implied that he wanted to submit a report as complete as possible up front.<br><br><blockquote type="cite">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.<br></blockquote><br>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 :<br><br> <a href="http://webilus.com/wp-content/uploads/2007/11/216couleurs_du_web.jpg">http://webilus.com/wp-content/uploads/2007/11/216couleurs_du_web.jpg</a><br><br>has more colours than one would ever need, to identify the problem, so, it's perfect for that.<br><br> _ _ __ ___ _____ ________ _____________ _____________________ ...<br>| Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801_______________________________________________<br><a href="mailto:Pd-list@iem.at">Pd-list@iem.at</a> mailing list<br>UNSUBSCRIBE and account-management -> <a href="http://lists.puredata.info/listinfo/pd-list">http://lists.puredata.info/listinfo/pd-list</a><br></div></blockquote></div><br></body></html>