Hi Chris++
Here is another crack at showing my CPU problem.
You'll need 16 different videos to test it.
First change the makefilename and random numbers to reflect your video clips. Then start the patch with the big green bang. Then you can turn on the big green toggle to start the pause/unpause.
It look 20min on this g5 dual 2Ghz with 1GB ram, so hopefully it will not take too much longer on your machines.
I'm really at a loss for why this is happening, I've tried a smaller test with 3 videos and using a metro sending "rate" messages, but that has been playing for some time without an issue.
Thanks Chris, Please let me know if your patch runs continuously on your machine for hours...
.b..
All of the G5 machines here are tied up indefinitely, so I can't test your patch in the near term. I do have pieces with 6-8 clips going right now and the frame rate is well over 30.
On 3/17/06, B. Bogart ben@ekran.org wrote:
Hi Chris++
Here is another crack at showing my CPU problem.
You'll need 16 different videos to test it.
First change the makefilename and random numbers to reflect your video clips. Then start the patch with the big green bang. Then you can turn on the big green toggle to start the pause/unpause.
It look 20min on this g5 dual 2Ghz with 1GB ram, so hopefully it will not take too much longer on your machines.
I'm really at a loss for why this is happening, I've tried a smaller test with 3 videos and using a metro sending "rate" messages, but that has been playing for some time without an issue.
Thanks Chris, Please let me know if your patch runs continuously on your machine for hours...
.b..
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
I just realized that there is no need for me to test your patch. You can install the Apple CHUD tools and run Shark yourself. All of the directions are on this page:
http://developer.apple.com/tools/performance/optimizingwithsystemtrace.html
Save the session and post it online somewhere and one of us will have a look.
On 3/17/06, chris clepper cgc@humboldtblvd.com wrote:
All of the G5 machines here are tied up indefinitely, so I can't test your patch in the near term. I do have pieces with 6-8 clips going right now and the frame rate is well over 30.
On 3/17/06, B. Bogart ben@ekran.org wrote:
Hi Chris++
Here is another crack at showing my CPU problem.
You'll need 16 different videos to test it.
First change the makefilename and random numbers to reflect your video clips. Then start the patch with the big green bang. Then you can turn on the big green toggle to start the pause/unpause.
It look 20min on this g5 dual 2Ghz with 1GB ram, so hopefully it will not take too much longer on your machines.
I'm really at a loss for why this is happening, I've tried a smaller test with 3 videos and using a metro sending "rate" messages, but that has been playing for some time without an issue.
Thanks Chris, Please let me know if your patch runs continuously on your machine for hours...
.b..
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Use this URL instead http://developer.apple.com/tools/sharkoptimize.html
On 3/17/06, chris clepper cgc@humboldtblvd.com wrote:
I just realized that there is no need for me to test your patch. You can install the Apple CHUD tools and run Shark yourself. All of the directions are on this page:
http://developer.apple.com/tools/performance/optimizingwithsystemtrace.html
Save the session and post it online somewhere and one of us will have a look.
Hi Chris,
Here are a couple links:
This one was the profile done while the video is running fine: http://www.ekran.org/ben/research/While-PD-runs-fine@start.mshark
This is the one once PD has been running for a while (20-30min): http://www.ekran.org/ben/research/Pd-is-now-slogging.mshark
Looks like while things are looking ok 25% CPU goes into "DecodeBlocks" which looks like the decompression process. When things go bad it looks like "mentorGetNextFrame" takes up 45% so that looks like the problem. Sorry I don't have the debugging symbols in this gem binary, but I hope the profiles can still help.
Thanks for the tips Chris, shark is indeed pretty sharp... :)
.b.
On Fri, March 17, 2006 11:33 am, chris clepper said:
Use this URL instead http://developer.apple.com/tools/sharkoptimize.html
On 3/17/06, chris clepper cgc@humboldtblvd.com wrote:
I just realized that there is no need for me to test your patch. You can install the Apple CHUD tools and run Shark yourself. All of the directions are on this page:
http://developer.apple.com/tools/performance/optimizingwithsystemtrace.html
Save the session and post it online somewhere and one of us will have a look.
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
I won't be able to look at the Shark traces until later, but both of the functions you list are Quicktime internals. What version of QT are you using?
On 3/17/06, B. Bogart ben@ekran.org wrote:
Hi Chris,
Here are a couple links:
This one was the profile done while the video is running fine: http://www.ekran.org/ben/research/While-PD-runs-fine@start.mshark
This is the one once PD has been running for a while (20-30min): http://www.ekran.org/ben/research/Pd-is-now-slogging.mshark
Looks like while things are looking ok 25% CPU goes into "DecodeBlocks" which looks like the decompression process. When things go bad it looks like "mentorGetNextFrame" takes up 45% so that looks like the problem. Sorry I don't have the debugging symbols in this gem binary, but I hope the profiles can still help.
Thanks for the tips Chris, shark is indeed pretty sharp... :)
.b.
On Fri, March 17, 2006 11:33 am, chris clepper said:
Use this URL instead http://developer.apple.com/tools/sharkoptimize.html
On 3/17/06, chris clepper cgc@humboldtblvd.com wrote:
I just realized that there is no need for me to test your patch. You can install the Apple CHUD tools and run Shark yourself. All of the directions are on this page:
http://developer.apple.com/tools/performance/optimizingwithsystemtrace.html
Save the session and post it online somewhere and one of us will have a look.
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
No problem,
I'll be back on this machine not until wednesday.
Quicktime 7.0.4 Seems that is the most up to date.
The machine is 10.3.9
Thanks, ..b.
On Fri, March 17, 2006 3:21 pm, chris clepper said:
I won't be able to look at the Shark traces until later, but both of the functions you list are Quicktime internals. What version of QT are you using?
On 3/17/06, B. Bogart ben@ekran.org wrote:
Hi Chris,
Here are a couple links:
This one was the profile done while the video is running fine: http://www.ekran.org/ben/research/While-PD-runs-fine@start.mshark
This is the one once PD has been running for a while (20-30min): http://www.ekran.org/ben/research/Pd-is-now-slogging.mshark
Looks like while things are looking ok 25% CPU goes into "DecodeBlocks" which looks like the decompression process. When things go bad it looks like "mentorGetNextFrame" takes up 45% so that looks like the problem. Sorry I don't have the debugging symbols in this gem binary, but I hope the profiles can still help.
Thanks for the tips Chris, shark is indeed pretty sharp... :)
.b.
On Fri, March 17, 2006 11:33 am, chris clepper said:
Use this URL instead
http://developer.apple.com/tools/sharkoptimize.html
On 3/17/06, chris clepper cgc@humboldtblvd.com wrote:
I just realized that there is no need for me to test your patch. You can install the Apple CHUD tools and run Shark yourself. All of the directions are on this page:
http://developer.apple.com/tools/performance/optimizingwithsystemtrace.html
Save the session and post it online somewhere and one of us will have
a
look.
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Ok. I'll recommend going back to Quicktime 6.5 on 10.3 since that was pretty stable and we don't target any version 7 features.
On 3/17/06, B. Bogart ben@ekran.org wrote:
No problem,
I'll be back on this machine not until wednesday.
Quicktime 7.0.4 Seems that is the most up to date.
The machine is 10.3.9
Thanks, ..b.
-
B. Bogart -
chris clepper