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.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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'
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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.
Logged In: YES
user_id=663212
Originator: NO
Intel or PowerPC?
Logged In: YES
user_id=1846262
Originator: YES
Sorry, this is on the prehistoric PowerPC's.
File Added: RGB-Grab.pd
RGB Grab Check
RGB Grab Check
Logged In: YES
user_id=1846262
Originator: YES
Sorry, this is on the prehistoric PowerPC's.
File Added: RGB-Grab.pd
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?)
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'
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
Test output 1
test output 2
Logged In: YES
user_id=1846262
Originator: YES
File Added: Test2.jpg
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.
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...
Logged In: YES
user_id=564396
Originator: NO
i just checked that there has indeed been a fix for this committed some months ago.
happy to close this bug-report.