Bugs item #1754855, was opened at 2007-07-16 15:52 Message generated for change (Comment added) made by mr-bo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1754855...
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: gem Group: v0.39.2 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mr-Bo (mr-bo) Assigned to: Nobody/Anonymous (nobody) Summary: pix_write producing some strange RGB values
Initial Comment: Just to notify that pix_write is producing some strange RGB values, out of line with whats in the render window.
This is on pd extended on OSX 10.4
----------------------------------------------------------------------
Comment By: Mr-Bo (mr-bo)
Date: 2007-07-28 02:27
Message: Logged In: YES user_id=1846262 Originator: YES
Im glad ther's an identification at least. Is this local to my hardware/pd-extended setup? If ther's a place to get a fix id gladly investigate. I could not manage to make sense or gain consistancy on the RGB outofballance...
----------------------------------------------------------------------
Comment By: christopher clepper (cclepper) Date: 2007-07-27 21:05
Message: Logged In: YES user_id=663212 Originator: NO
This turned out to be a very obscure bug having to do with pixel alignment. The change is actually in GemPixUtil.cpp. For the record OSX does automatic alignment to 128 bits and for blocks over a certain size it even page aligns on 4k boundaries.
----------------------------------------------------------------------
Comment By: Mr-Bo (mr-bo) Date: 2007-07-27 13:38
Message: Logged In: YES user_id=1846262 Originator: YES
File Added: Test2.jpg
----------------------------------------------------------------------
Comment By: Mr-Bo (mr-bo) Date: 2007-07-27 13:37
Message: Logged In: YES user_id=1846262 Originator: YES
Yes, this is related to PD extended - didnt know what tag to label it under. Let me know if I can label it correctly. With regards to the quicktime bug, well, the problem doesnt occur on a older GEM version (0.90 compiled Mar 06). Additionaly, the problem persists when outputing .jpg format. Beats me. The two files attached have background colour set to 1 0 0.3. Guess which is the odd one out...? File Added: Test1.jpg
----------------------------------------------------------------------
Comment By: christopher clepper (cclepper) Date: 2007-07-23 16:38
Message: Logged In: YES user_id=663212 Originator: NO
This appears to be a bug with the TIFF writing component in Quicktime. Try adding a 1 after the file name to select JPG image writing. Example message: 'file $1 1'
----------------------------------------------------------------------
Comment By: IOhannes m zmölnig (zmoelnig) Date: 2007-07-23 16:19
Message: Logged In: YES user_id=564396 Originator: NO
could you please provide images (screenshots) on how it does look like and how it is supposed to look. (sorry for the added inconvenience).
furthermore: is this related to pd-extended? (or rather: why does this issue have a 0.39.2 tag?)
----------------------------------------------------------------------
Comment By: Mr-Bo (mr-bo) Date: 2007-07-17 23:16
Message: Logged In: YES user_id=1846262 Originator: YES
Sorry, this is on the prehistoric PowerPC's. File Added: RGB-Grab.pd
----------------------------------------------------------------------
Comment By: Mr-Bo (mr-bo) Date: 2007-07-17 14:51
Message: Logged In: YES user_id=1846262 Originator: YES
Sorry, this is on the prehistoric PowerPC's. File Added: RGB-Grab.pd
----------------------------------------------------------------------
Comment By: christopher clepper (cclepper) Date: 2007-07-17 14:35
Message: Logged In: YES user_id=663212 Originator: NO
Intel or PowerPC?
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave) Date: 2007-07-16 19:35
Message: Logged In: YES user_id=27104 Originator: NO
An example patch is always very helpful, especially if it triggers the problem every time that it is run. Ideally the example patch would have only enough objects to cause the problem, but nothing else.
----------------------------------------------------------------------
You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1754855...