GEM-dev

gem-dev@lists.iem.at

2417 discussions

[ pd-gem-Bugs-3453593 ] plugins don't work with MinGW builds
by SourceForge.net 07 Dec '11

07 Dec '11

Bugs item #3453593, was opened at 2011-12-07 06:14 Message generated for change (Tracker Item Submitted) made by zmoelnig You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3453593&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: build-system Group: win32 Status: Open Resolution: None Priority: 5 Private: No Submitted By: IOhannes m zmölnig (zmoelnig) Assigned to: Nobody/Anonymous (nobody) Summary: plugins don't work with MinGW builds Initial Comment: when building Gem with MinGW, the resulting Gem.dll cannot use any of the resulting plugins (e.g. gem_imageSGI.dll) uncommenting the debugging printout in PluginFactoryTIMPL.h reveals, that Gem and the plugin see _different_ pluginfactories! (at least their addresses differ) system: - Gem-0.93git59cc4030375e20 - Windows7 - MinGW/MSYS - g++-4.6.1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3453593&group_…

1 0

[ pd-gem-Bugs-3453590 ] MinGW compiled GemBase crashes
by SourceForge.net 07 Dec '11

07 Dec '11

Bugs item #3453590, was opened at 2011-12-07 06:10 Message generated for change (Tracker Item Submitted) made by zmoelnig You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3453590&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: build-system Group: win32 Status: Open Resolution: None Priority: 5 Private: No Submitted By: IOhannes m zmölnig (zmoelnig) Assigned to: Nobody/Anonymous (nobody) Summary: MinGW compiled GemBase crashes Initial Comment: when using Gem compiled with MinGW, virtually all objectclasses derived from GemBase crash when they receive any message. only GemBase subclasses are affected, other objectclasses like [gemwin] or [gemhead] work fine. system: - Gem-0.93git59cc4030375e20 - Windows7 - MinGW/MSYS - g++-4.6.1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3453590&group_…

1 0

help files update - git
by Nicolas Montgermont 07 Dec '11

07 Dec '11

Hello Iohannes / list, I've worked on a few help files. It was mainly help files that were not in the Gem format. I've done that using git. You can find them here: git@github.com:nixhol/Gem.git the name of the branch is: help-files I've cloned the Gem sourceforge repository, then i've created a branch, worked on the files, and then i've pushed my modifs on my github repository. Is this the good workflow for contributing to Gem using git? or do you prefer another way? Thanks Nicolas -- http://nim.on.free.fr

3 4

[ pd-gem-Bugs-3195435 ] pix_film prints an error msg if frame <0 but not if = 0
by SourceForge.net 05 Dec '11

05 Dec '11

Bugs item #3195435, was opened at 2011-02-28 12:00 Message generated for change (Comment added) made by zmoelnig You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3195435&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: Pixes (pix_ objects) Group: any operating system Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: pix_film prints an error msg if frame <0 but not if = 0 Initial Comment: This is a very minor issue, however... The right inlet of [pix_film] accepts a frame number which ranges from 1 to N if the video has N frames. If it receives a negative frame number, it prints an error message: error: [pix_film]: selection number must be > 0 To be consistent, it should print the same error message when it receives 0 as the frame number, but it doesn't. Indeed I thing the condition is actually that the frame be >=1 (consider floats!) Also I would suggest to specify in the help patch that the frame numbers start from 1 (unless I am the only one who would expect it to start from 0) ---------------------------------------------------------------------- >Comment By: IOhannes m zmölnig (zmoelnig) Date: 2011-12-05 02:00 Message: i agree that it should be consistent. i also agree that the frames should range from 0..(N-1) rather than 1..N? i even think that for (most?) backends the frame number ranges from 0..(N-1). does the problem still exist with Gem-0.93? (minor sidenote: the error message says indeed that the frame number must be ">0" but the check is done whether it is "!<0", so this should be ok) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3195435&group_…

1 0

[ pd-gem-Bugs-3336856 ] pix_film crashes with Apple Animation (runlength) videos
by SourceForge.net 05 Dec '11

05 Dec '11

Bugs item #3336856, was opened at 2011-06-27 02:28 Message generated for change (Comment added) made by zmoelnig You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3336856&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: Pixes (pix_ objects) Group: linux >Status: Pending >Resolution: Postponed Priority: 5 Private: No Submitted By: Matteo Sisti Sette (sistisette) Assigned to: Nobody/Anonymous (nobody) Summary: pix_film crashes with Apple Animation (runlength) videos Initial Comment: pix_film crashes when loading png-encoded videos. I encoded them with ffmpeg using -vcodec png. I don't know which backend is being used for decoding the video files (how can I find out?) but lqtplay plays the same files without crashing (and Gem is linked against the same libquicktime as lqtplayed, at least that's what ldd says). ---------------------------------------------------------------------- >Comment By: IOhannes m zmölnig (zmoelnig) Date: 2011-12-05 01:56 Message: more information is requried in order to fix this. ---------------------------------------------------------------------- Comment By: IOhannes m zmölnig (zmoelnig) Date: 2011-06-27 03:09 Message: could you please provide a (short) movie that triggers the problem? also, please provide a backtrace of the crash, ---------------------------------------------------------------------- Comment By: IOhannes m zmölnig (zmoelnig) Date: 2011-06-27 03:09 Message: could you provide a backtrace of the crash? on linux/osx/similar you can use gdb for producing one: $ gdb -args /path/to/pd -nrt -stderr -lib Gem -open /my/faulty/patch.pd [...] (gdb) run [... do something to trigger the crasher bug ...] (gdb) backtrace [...] ---------------------------------------------------------------------- Comment By: Matteo Sisti Sette (sistisette) Date: 2011-06-27 02:36 Message: Sorry It's NOT PNG, it's Apple Animation codec (runlength). I was testing several videos and I got confused. I edited the summary but I can't seem to edit the description. The rest of the description is correct: lqtplay does not crash, Pd does. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3336856&group_…

1 0

[ pd-gem-Bugs-3448076 ] [text3d]: problems with strings starting with newline
by SourceForge.net 05 Dec '11

05 Dec '11

Bugs item #3448076, was opened at 2011-12-02 01:27 Message generated for change (Settings changed) made by zmoelnig You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3448076&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: rendering (e.g. display) Group: any operating system >Status: Pending Resolution: Fixed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: [text3d]: problems with strings starting with newline Initial Comment: When sending [text3d] a 'string' message starting with a newline character (10), the Gem window shows an unexpected text, where every newline character (including the first one) is replaced by a character looking similar to [] (an empty box). Example: [string 10 97 97 10 98 98( is rendered as: []aa[]bb [string 97 97 10 98 98( is (correctly) rendered as: aa bb This is on / with: - Gem 0.93.git cb1745f - Pd 0.43.1test4 - Ubuntu 11.04 and: - Pd-extended 0.42.6 - Mac OS X (10.6) Credit for finding this bug goes to Michèle Graf and Selina Grüter ---------------------------------------------------------------------- Comment By: Roman Haefeli (reduzent) Date: 2011-12-02 05:08 Message: I can confirm it is fixed. Thanks ---------------------------------------------------------------------- Comment By: IOhannes m zmölnig (zmoelnig) Date: 2011-12-02 02:48 Message: should be fixed with git.d5d0b83dc ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3448076&group_…

1 0

[ pd-gem-Bugs-3448076 ] [text3d]: problems with strings starting with newline
by SourceForge.net 02 Dec '11

02 Dec '11

Bugs item #3448076, was opened at 2011-12-02 01:27 Message generated for change (Comment added) made by reduzent You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3448076&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: rendering (e.g. display) Group: any operating system Status: Pending Resolution: Fixed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: [text3d]: problems with strings starting with newline Initial Comment: When sending [text3d] a 'string' message starting with a newline character (10), the Gem window shows an unexpected text, where every newline character (including the first one) is replaced by a character looking similar to [] (an empty box). Example: [string 10 97 97 10 98 98( is rendered as: []aa[]bb [string 97 97 10 98 98( is (correctly) rendered as: aa bb This is on / with: - Gem 0.93.git cb1745f - Pd 0.43.1test4 - Ubuntu 11.04 and: - Pd-extended 0.42.6 - Mac OS X (10.6) Credit for finding this bug goes to Michèle Graf and Selina Grüter ---------------------------------------------------------------------- Comment By: Roman Haefeli (reduzent) Date: 2011-12-02 05:08 Message: I can confirm it is fixed. Thanks ---------------------------------------------------------------------- Comment By: IOhannes m zmölnig (zmoelnig) Date: 2011-12-02 02:48 Message: should be fixed with git.d5d0b83dc ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3448076&group_…

1 0

[ pd-gem-Bugs-3448076 ] [text3d]: problems with strings starting with newline
by SourceForge.net 02 Dec '11

02 Dec '11

Bugs item #3448076, was opened at 2011-12-02 01:27 Message generated for change (Comment added) made by zmoelnig You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3448076&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: rendering (e.g. display) Group: any operating system >Status: Pending >Resolution: Fixed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: [text3d]: problems with strings starting with newline Initial Comment: When sending [text3d] a 'string' message starting with a newline character (10), the Gem window shows an unexpected text, where every newline character (including the first one) is replaced by a character looking similar to [] (an empty box). Example: [string 10 97 97 10 98 98( is rendered as: []aa[]bb [string 97 97 10 98 98( is (correctly) rendered as: aa bb This is on / with: - Gem 0.93.git cb1745f - Pd 0.43.1test4 - Ubuntu 11.04 and: - Pd-extended 0.42.6 - Mac OS X (10.6) Credit for finding this bug goes to Michèle Graf and Selina Grüter ---------------------------------------------------------------------- >Comment By: IOhannes m zmölnig (zmoelnig) Date: 2011-12-02 02:48 Message: should be fixed with git.d5d0b83dc ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3448076&group_…

1 0

[ pd-gem-Bugs-3448076 ] [text3d]: problems with strings starting with newline
by SourceForge.net 02 Dec '11

02 Dec '11

Bugs item #3448076, was opened at 2011-12-02 01:27 Message generated for change (Tracker Item Submitted) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3448076&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: rendering (e.g. display) Group: any operating system Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: [text3d]: problems with strings starting with newline Initial Comment: When sending [text3d] a 'string' message starting with a newline character (10), the Gem window shows an unexpected text, where every newline character (including the first one) is replaced by a character looking similar to [] (an empty box). Example: [string 10 97 97 10 98 98( is rendered as: []aa[]bb [string 97 97 10 98 98( is (correctly) rendered as: aa bb This is on / with: - Gem 0.93.git cb1745f - Pd 0.43.1test4 - Ubuntu 11.04 and: - Pd-extended 0.42.6 - Mac OS X (10.6) Credit for finding this bug goes to Michèle Graf and Selina Grüter ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3448076&group_…

1 0

pix_write relative path - osx
by Nicolas Montgermont 01 Dec '11

01 Dec '11

Hello list, I was wondering if the problem of the relative path of [pix_write] under osx may be fixed soon. For reminder the actual behavior (gem compiled this morning, used with pd-extended 0.42.5, osx.6.8) is: - if you send no filename, you have in the terminal: error: ERROR: -43 in GraphicsExportSetOutputFile() error: GEM: Unable to save image to 'gem00000.tif' - if you send a relative filename, eg. [file toto(, you have the same error: error: ERROR: -43 in GraphicsExportSetOutputFile() error: GEM: Unable to save image to 'toto00000.tif' - if you send a filename including the "~" home variable, it gives the same error. It only works if you set pix_write to an absolute filename inside an existing directory, eg. [file /Users/nix/snap_pd/test (. From what i've seen in workshop, this is a major difficulty for learners. They are not specially used to explicit a directory from root, and they must not have spaces in any directory name used. It makes also a patch containing pix_write on an osx computer non directly usable on any another ... Is there any possibility to have relative path in pix_write under osx, or can we imagine some workaround? it will be of great help thanks, n -- http://nim.on.free.fr

6 18

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

GEM-dev