[pix_film] is well known for this kind of crash-y issues.
It might depends on the codec you use (i.e. different codecs are installed on MacMini)
However, have you tried using [pix_movie] instead?
In my experience it's more reliable.
M
I?ve been working trying to fix a Puredata patch that uses MIDI input from an external device to control playback of 2 movies that are displayed in a single GEM window. I have been able to get the patch working properly on my own computer (a 2.53GHz MacBook Pro with OSX 10.6.3) but can?t get it to work on the computer where the patch needs to run (a 1.66GHz MacMini with OSX 10.5).
I?ve read through the forums and archives and based on the input I have created several version of the patch (all of them have crashed on the MacMini). I couldn?t find any instance of a bug report documenting this issue so I decided to add it here.
I?ve posted my code, two different approaches each with the associated full crash reports. In the first approach I use two separate Gemheads to control the movies; in the second approach I use a single Gemhead to control both movies.
Please note that the download is quite large (100MB). The reason being, I have included videos in the zip files so that the application can run properly. One more important note, you need to install pdmtl in order to run the patch (as I use one of their abstractions in my patches).
Link to code and crash reports: http://itp.nyu.edu/~jt1428/downloads/gem_issue/see-saw-examples.ziphttp://itp.nyu.edu/%7Ejt1428/downloads/gem_issue/see-saw-examples.zip
Any help is greatly appreciated.
On 2010-07-04 14:14, Marco Donnarumma wrote:
[pix_film] is well known for this kind of crash-y issues.
this is entire news for me. there are 2 bug-reports in Gem's bug-tracker that have "pix_film" in their title. then i found (after admittedly quick searching) one (1) more report related to pix_film's "gmerlin" backend.
if you know so many "crash-y issues" please report them at https://sourceforge.net/tracker/?group_id=64325&atid=507079
However, have you tried using [pix_movie] instead?
In my experience it's more reliable.
in my experience it is less reliable (esp. on OSX where there is still the unresolved flickering thing).
fgmasdr IOhannes
Thanks for pointing out. Might be some stereotype of mine, but I've worked in a easier way on cross-platform projects with [pix_movie] which seems to handle in a better way different codecs on different platforms. I don't know the guts of both obj though. However on the archive list there are threads about this same topic, which I referred to when I had issues to solve. Your experience is surely more reliable.
M
On Thu, Jul 8, 2010 at 4:12 PM, IOhannes m zmoelnig zmoelnig@iem.at wrote:
On 2010-07-04 14:14, Marco Donnarumma wrote:
[pix_film] is well known for this kind of crash-y issues.
this is entire news for me. there are 2 bug-reports in Gem's bug-tracker that have "pix_film" in their title. then i found (after admittedly quick searching) one (1) more report related to pix_film's "gmerlin" backend.
if you know so many "crash-y issues" please report them at https://sourceforge.net/tracker/?group_id=64325&atid=507079
However, have you tried using [pix_movie] instead?
In my experience it's more reliable.
in my experience it is less reliable (esp. on OSX where there is still the unresolved flickering thing).
fgmasdr IOhannes
-
IOhannes m zmoelnig -
Marco Donnarumma