hi all
somehow related to frank's question, but i would like to achieve the opposite: _more_ hw acceleration (instead of less).
i found, that on new macs, playing even full-hd h.264 quicktime files doesn't eat any noticable cpu processing. on a macbook pro unibody, it takes around 13% (says 'activity monitor') playing it with quicktime 7.X.X. the same movie played by [pix_film] from Gem from pd-extended-0.40.3 takes ~60% (of one core). if it is correct to believe, that gem makes use of the quicktime API on os x, is there a way to make it use of the gpu accelerated h.264 decoding feature?
hm.. i should have checked, whether the plain decoding uses much cpu or if probably some significant chunk is used for displaying. i'll test tomorrow, when i have access to a mac again.
any hints about the topic are welcome.
roman
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
The video might be using hardware acceleration for the h.264, but getting no benefit. Quicktime player just displays the movie and nothing else, while GEM requests the fully decoded pixels in RAM. The video might be getting uploaded to the GPU, decoded, then bounced back to RAM and then uploaded again. Apple has some new optimized ways to play video, but they are far too limited for use in GEM.
On Tue, May 12, 2009 at 2:52 PM, Roman Haefeli reduzierer@yahoo.de wrote:
hi all
somehow related to frank's question, but i would like to achieve the opposite: _more_ hw acceleration (instead of less).
i found, that on new macs, playing even full-hd h.264 quicktime files doesn't eat any noticable cpu processing. on a macbook pro unibody, it takes around 13% (says 'activity monitor') playing it with quicktime 7.X.X. the same movie played by [pix_film] from Gem from pd-extended-0.40.3 takes ~60% (of one core). if it is correct to believe, that gem makes use of the quicktime API on os x, is there a way to make it use of the gpu accelerated h.264 decoding feature?
hm.. i should have checked, whether the plain decoding uses much cpu or if probably some significant chunk is used for displaying. i'll test tomorrow, when i have access to a mac again.
any hints about the topic are welcome.
roman
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
On Tue, 2009-05-12 at 16:46 -0400, chris clepper wrote:
The video might be using hardware acceleration for the h.264, but getting no benefit. Quicktime player just displays the movie and nothing else, while GEM requests the fully decoded pixels in RAM. The video might be getting uploaded to the GPU, decoded, then bounced back to RAM and then uploaded again. Apple has some new optimized ways to play video, but they are far too limited for use in GEM.
i see. thanks for the explanation. one reason, why i was thinking, that gem doesn't use hw acceleration was that the cpu power used is quite similar to the ones, when the same file is played by mplayer or vlc. but according to what you say, it would probably be still impossible to play 1080p with [pix_film] without hw accel.
roman
On Tue, May 12, 2009 at 2:52 PM, Roman Haefeli reduzierer@yahoo.de wrote: hi all
somehow related to frank's question, but i would like to achieve the opposite: _more_ hw acceleration (instead of less). i found, that on new macs, playing even full-hd h.264 quicktime files doesn't eat any noticable cpu processing. on a macbook pro unibody, it takes around 13% (says 'activity monitor') playing it with quicktime 7.X.X. the same movie played by [pix_film] from Gem from pd-extended-0.40.3 takes ~60% (of one core). if it is correct to believe, that gem makes use of the quicktime API on os x, is there a way to make it use of the gpu accelerated h.264 decoding feature? hm.. i should have checked, whether the plain decoding uses much cpu or if probably some significant chunk is used for displaying. i'll test tomorrow, when i have access to a mac again. any hints about the topic are welcome. roman ___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de _______________________________________________ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
On Tue, May 12, 2009 at 5:12 PM, Roman Haefeli reduzierer@yahoo.de wrote:
i see. thanks for the explanation. one reason, why i was thinking, that gem doesn't use hw acceleration was that the cpu power used is quite similar to the ones, when the same file is played by mplayer or vlc. but according to what you say, it would probably be still impossible to play 1080p with [pix_film] without hw accel.
I made many GEM based art works that played 4 1080 clips and recorded a live stream to disk all in real time. I think the problem you are having is the H.264 codec, which is intended for ultra-low data bandwidth applications. Switching to Apple Intermediate or one of the professional codecs (DVCPRO_HD or ProRes) will improve performance far more than trying to offload the 100:1 compressed H.264 to the GPU.
-
chris clepper -
Roman Haefeli