Patches item #1760624, was opened at 2007-07-25 15:01
Message generated for change (Comment added) made by millerpuckette
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1760624&group_…
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: puredata
Group: feature
Status: Open
Resolution: None
Priority: 8
Private: No
Submitted By: Hans-Christoph Steiner (eighthave)
Assigned to: Miller Puckette (millerpuckette)
Summary: font/box size overhaul with properties panel clean-up
Initial Comment:
This patch includes everything from branch-v0-39-2-extended to make the fonts and boxes the same size on every platform.
The default font is changed to Monaco on Mac OSX (included with the OS) and Bitstream Vera Sans Mono on Windows and GNU/Linux (included with GNOME). The font is free as in speech and beer, so it can be distributed with any Pd package.
The iemgui properties panels were also changed to reflect the new fonts, plus they were cleaned up a bit to make them more readable.
It applies cleanly, builds and seems to work fine on 0.40.3 and 0.41.0-test04.
----------------------------------------------------------------------
>Comment By: Miller Puckette (millerpuckette)
Date: 2007-07-29 16:44
Message:
Logged In: YES
user_id=313747
Originator: NO
This did something funny on my machine (fedora 6). "10" and "12"
show up with the same font size, and/but boxes sized differently
(in 12 point, not fitting the un-enlarged text). I'll bring the
machine to Montreal so we can look...
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1760624&group_…
Patches item #1625445, was opened at 2006-12-31 11:50
Message generated for change (Comment added) made by millerpuckette
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1625445&group_…
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: puredata
Group: feature
Status: Open
Resolution: None
Priority: 8
Private: No
Submitted By: Hans-Christoph Steiner (eighthave)
Assigned to: Miller Puckette (millerpuckette)
Summary: extended character support
Initial Comment:
Enable support for more characters, like characters with umlauts and accents.
Following this discussion:
http://lists.puredata.info/pipermail/pd-list/2006-12/045571.html
----------------------------------------------------------------------
>Comment By: Miller Puckette (millerpuckette)
Date: 2007-07-29 16:11
Message:
Logged In: YES
user_id=313747
Originator: NO
Had to change it to reject \0177 (delete) characters.
----------------------------------------------------------------------
Comment By: Miller Puckette (millerpuckette)
Date: 2007-05-19 21:04
Message:
Logged In: YES
user_id=313747
Originator: NO
Taken for 0.41. I'll edit the comment to make it appropriately scary.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1625445&group_…
Patches item #1755720, was opened at 2007-07-17 13:51
Message generated for change (Comment added) made by millerpuckette
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1755720&group_…
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: puredata
Group: bugfix
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nathaniel Dose (dosena2)
Assigned to: Nobody/Anonymous (nobody)
Summary: patch: OS X sysexin/midiin support #3
Initial Comment:
Here is changed file 3 of 3 for enabling "sysexin" and "midiin". This is the most extensive patch of the 3, but is still small. Attached is a udiff.
Basically sys_poll_midi had only 1 byte of sysex as state at one time - now it keeps track of a whole (multibyte) sysex message. I was told to post here by the dev mailing list.
Please change the value of the file-local variables nd_sysex* as needed! I am not familiar yet with your naming conventions.
$ cvs status s_midi_pm.c
===================================================================
File: s_midi_pm.c Status: Locally Modified
Working revision: 1.6
Repository revision: 1.6 /cvsroot/pure-data/pd/src/s_midi_pm.c,v
Sticky Tag: stable_0_40 (branch: 1.6.2)
Sticky Date: (none)
Sticky Options: (none)
$ cvs diff -u s_midi_pm.c
Index: s_midi_pm.c
===================================================================
RCS file: /cvsroot/pure-data/pd/src/s_midi_pm.c,v
retrieving revision 1.6
diff -u -r1.6 s_midi_pm.c
--- s_midi_pm.c 8 Jul 2005 00:02:45 -0000 1.6
+++ s_midi_pm.c 17 Jul 2007 20:48:27 -0000
@@ -140,7 +140,7 @@
writemidi4(mac_midioutdevlist[portno], byte, 0, 0, 0);
else if (byte == 0xf0)
{
- mess[0] = 0xf7;
+ mess[0] = 0xf0;
nbytes = 1;
sysex = 1;
}
@@ -209,6 +209,38 @@
}
}
+/* this is non-zero if we are in the middle of transmitting sysex */
+
+int nd_sysex_mode=0;
+
+/* send in 4 bytes of sysex data. if one of the bytes is 0xF7 (sysex end) stop and unset nd_sysex_mode */
+void nd_sysex_inword(int midiindev, int status, int data1, int data2, int data3)
+{
+ if (nd_sysex_mode) {
+ sys_midibytein(midiindev, status);
+ if (status == 0xF7)
+ nd_sysex_mode = 0;
+ }
+
+ if (nd_sysex_mode) {
+ sys_midibytein(midiindev, data1);
+ if (data1 == 0xF7)
+ nd_sysex_mode = 0;
+ }
+
+ if (nd_sysex_mode) {
+ sys_midibytein(midiindev, data2);
+ if (data2 == 0xF7)
+ nd_sysex_mode = 0;
+ }
+
+ if (nd_sysex_mode) {
+ sys_midibytein(midiindev, data3);
+ if (data3 == 0xF7)
+ nd_sysex_mode = 0;
+ }
+}
+
void sys_poll_midi(void)
{
int i, nmess;
@@ -221,6 +253,7 @@
int status = Pm_MessageStatus(buffer.message);
int data1 = Pm_MessageData1(buffer.message);
int data2 = Pm_MessageData2(buffer.message);
+ int data3 = ((buffer.message >> 24) & 0xFF);
int msgtype = (status >> 4) - 8;
switch (msgtype)
{
@@ -239,8 +272,12 @@
sys_midibytein(i, data1);
break;
case 7:
- sys_midibytein(i, status);
+ nd_sysex_mode=1;
+ nd_sysex_inword(i, status, data1, data2, data3);
break;
+ default:
+ if (nd_sysex_mode)
+ nd_sysex_inword(i, status, data1, data2, data3);
}
}
}
----------------------------------------------------------------------
>Comment By: Miller Puckette (millerpuckette)
Date: 2007-07-29 13:41
Message:
Logged In: YES
user_id=313747
Originator: NO
These three should be reflected in 0.41-test05.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1755720&group_…
Patches item #1763221, was opened at 2007-07-29 12:18
Message generated for change (Comment added) made by nobody
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1763221&group_…
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: puredata
Group: bugfix
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Stephen Sinclair (radarsat1)
Assigned to: Nobody/Anonymous (nobody)
Summary: fix jack-related compile error on Ubuntu Gutsy (gcc-4.1.3)
Initial Comment:
I was compiling PureData from scratch today and after automake/configure/make, I received this error:
cc -g -O2 -DPD -Wall -W -Wstrict-prototypes -Wno-unused -Wno-parentheses -Wno-switch -DDL_OPEN -DPA_USE_OSS -DUNIX -DUNISTD -DUSEAPI_OSS -I../portaudio/pa_common -I../portaudio/pablio -I../portmidi/pm_common -I../portmidi/pm_linux -fno-strict-aliasing -DPA_USE_ALSA -DUSEAPI_ALSA -O6 -funroll-loops -fomit-frame-pointer -DUSEAPI_JACK -D_LARGEFILE64_SOURCE -DINSTALL_PREFIX=\"/home/ssteve/.local\" -c -o ../obj/s_audio_jack.o s_audio_jack.c
s_audio_jack.c:197: error: ‘jack_error_callback’ redeclared as different kind of symbol
/usr/include/jack/jack.h:776: error: previous declaration of ‘jack_error_callback’ was here
make: *** [s_audio_jack.o] Error 1
The solution was to rename the jack_error_callback function, so I added an underscore. Maybe there is a better solution. I am using Ubuntu Gutsy (development version of Ubuntu), with gcc-4.1.3:
$ gcc --version
gcc (GCC) 4.1.3 20070718 (prerelease) (Ubuntu 4.1.2-14ubuntu1)
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2007-07-29 13:39
Message:
Logged In: NO
This should already be fixed in 0.41-test05
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1763221&group_…
Bugs item #1763228, was opened at 2007-07-29 15:43
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1763228&group_…
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: pd-extended
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: marius schebella (mariusschebella)
Assigned to: Hans-Christoph Steiner (eighthave)
Summary: vline~ broken
Initial Comment:
with the latest autobuild (july 29) labeled "Pure Data 0.39.3-extended-rc5" for mac osx (intel) the vline~ object does not work.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1763228&group_…
Patches item #1763221, was opened at 2007-07-29 15:18
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1763221&group_…
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: puredata
Group: bugfix
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Stephen Sinclair (radarsat1)
Assigned to: Nobody/Anonymous (nobody)
Summary: fix jack-related compile error on Ubuntu Gutsy (gcc-4.1.3)
Initial Comment:
I was compiling PureData from scratch today and after automake/configure/make, I received this error:
cc -g -O2 -DPD -Wall -W -Wstrict-prototypes -Wno-unused -Wno-parentheses -Wno-switch -DDL_OPEN -DPA_USE_OSS -DUNIX -DUNISTD -DUSEAPI_OSS -I../portaudio/pa_common -I../portaudio/pablio -I../portmidi/pm_common -I../portmidi/pm_linux -fno-strict-aliasing -DPA_USE_ALSA -DUSEAPI_ALSA -O6 -funroll-loops -fomit-frame-pointer -DUSEAPI_JACK -D_LARGEFILE64_SOURCE -DINSTALL_PREFIX=\"/home/ssteve/.local\" -c -o ../obj/s_audio_jack.o s_audio_jack.c
s_audio_jack.c:197: error: ‘jack_error_callback’ redeclared as different kind of symbol
/usr/include/jack/jack.h:776: error: previous declaration of ‘jack_error_callback’ was here
make: *** [s_audio_jack.o] Error 1
The solution was to rename the jack_error_callback function, so I added an underscore. Maybe there is a better solution. I am using Ubuntu Gutsy (development version of Ubuntu), with gcc-4.1.3:
$ gcc --version
gcc (GCC) 4.1.3 20070718 (prerelease) (Ubuntu 4.1.2-14ubuntu1)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1763221&group_…
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&group_…
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&group_…
Bugs item #1754855, was opened at 2007-07-16 15:52
Message generated for change (Comment added) made by cclepper
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1754855&group_…
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: 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&group_…
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&group_…
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-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&group_…
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&group_…
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-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&group_…