Running a 2.16 ghz core2duo macbook pro, while doing other stuff, getting around 25fps on h.264 640px width, 1250kbs.
Handbrake from the SVN version 0.7.1a5
Macbookpro core2 2.16
Forum rules
Guide to Posting Benchmarks
Guide to Posting Benchmarks
Running on a MacBookPro C2D 2.33 save version as noted above I'm getting apprx. 29 fps on h.264 640x363, 1000kbps, whereas under 0.7.1 (titer's last official release) I tend to get a few (4-5) fps above that. Any ideas on why this is happening?
Also the encoded result clearly differs in terms of colour saturation and blending, have you guys switched to another h.264 encoding lib?
Also the encoded result clearly differs in terms of colour saturation and blending, have you guys switched to another h.264 encoding lib?
RTouris and zaphod, you are running 0.7.1a5? This would be the file in the beta directory, labeled 0.7.1a5, that was briefly available to the public?
That file's full name is HandBrake_0.7.1a5_PPC.zip.
So, um, that "PPC" part might be the speed issue with you guys and your MacBooks. Could it be running through Rosetta?
I don't believe we ever released a universal of 0.7.1a5. Johnallen was going to put one together, but before that happened, we got dugg.
On the other hand, maybe you're not using that PPC copy. If you're checking code out of the SVN and compiling yourselves, please test with the MediaFork_0.8.0_mpeg4ip branch. That has much better universal support. The trunk hasn't been touched in a month.
We upgraded from revision 401 to revision 604 of x264.
If you're getting differences in colors..well..are you playing the video in QuickTime? Titer added something to give brighter colors in QT after 0.7.1 was released.
That file's full name is HandBrake_0.7.1a5_PPC.zip.
So, um, that "PPC" part might be the speed issue with you guys and your MacBooks. Could it be running through Rosetta?
I don't believe we ever released a universal of 0.7.1a5. Johnallen was going to put one together, but before that happened, we got dugg.
On the other hand, maybe you're not using that PPC copy. If you're checking code out of the SVN and compiling yourselves, please test with the MediaFork_0.8.0_mpeg4ip branch. That has much better universal support. The trunk hasn't been touched in a month.
Same h.264 encoding lib, but a much newer version.RTouris wrote:Also the encoded result clearly differs in terms of colour saturation and blending, have you guys switched to another h.264 encoding lib?
We upgraded from revision 401 to revision 604 of x264.
If you're getting differences in colors..well..are you playing the video in QuickTime? Titer added something to give brighter colors in QT after 0.7.1 was released.
Indeed, I'm not running the PPC version under Rosetta here, things would have been much slower compared to a few fps under the current circumstances, trust me I've been there (PPC under Rosetta vs. Intel code)
This is rev92 I'm talking about compiled sometime around the beginning of Jan or give or take a few days (this somehow ended up in my mailbox the other day and triggered my interest to pay you guys a visit, but that's another story on its own).
With regards to the colours issues I'm referring to, I am testing in both QT using the built-in H.264 decoder and the x264 Quicktime decoder (http://www.macupdate.com/info.php/id/20273), as well as VLC (latest nightly) and MPlayer...The difference is noticeable in every case to say the least and I do prefer the HB's decoding colour pattern to be honest, so I reckon there must have been something else apart from the encoding lib rev. differentiating between now and back then...
But here we are, eagerly waiting for the first "public" release, so without further ado...![Smile :-)](./images/smilies/icon_smile.gif)
![Wink ;-)](./images/smilies/icon_wink.gif)
With regards to the colours issues I'm referring to, I am testing in both QT using the built-in H.264 decoder and the x264 Quicktime decoder (http://www.macupdate.com/info.php/id/20273), as well as VLC (latest nightly) and MPlayer...The difference is noticeable in every case to say the least and I do prefer the HB's decoding colour pattern to be honest, so I reckon there must have been something else apart from the encoding lib rev. differentiating between now and back then...
But here we are, eagerly waiting for the first "public" release, so without further ado...
![Smile :-)](./images/smilies/icon_smile.gif)
-
- Posts: 9
- Joined: Mon Dec 04, 2006 11:18 pm
-
- Bright Spark User
- Posts: 183
- Joined: Wed Mar 14, 2007 1:49 pm
For some reason my performance appears to be pretty dismal and I don't understand why. I'm trying to rip on a MacBook Pro Core 2 Duo 2.33Ghz with the standard 2GB RAM with the following settings:
Application: MediaFork 0.8.0b1
File Format: MP4
Codec: AVC/H.264 Video / AAC Audio
Encoder: x264 (h.264 iPod)
2-Pass Encoding: Yes
De-interlaced: Yes
Output: 640 x 352
Sample Rate: 44.1
Bitrate: 128
With these settings I'm getting a rate of around 4-5 fps and my laptop isn't even breaking a sweat. Activity monitor shows my CPUs to idle around 80% of the time and I've got around 1.2GB memory spare.
Any ideas are gratefully received.
Application: MediaFork 0.8.0b1
File Format: MP4
Codec: AVC/H.264 Video / AAC Audio
Encoder: x264 (h.264 iPod)
2-Pass Encoding: Yes
De-interlaced: Yes
Output: 640 x 352
Sample Rate: 44.1
Bitrate: 128
With these settings I'm getting a rate of around 4-5 fps and my laptop isn't even breaking a sweat. Activity monitor shows my CPUs to idle around 80% of the time and I've got around 1.2GB memory spare.
Any ideas are gratefully received.
Looks like the issue is due to the reading of the disk from the SuperDrive. If I copy the VIDEO_TS folder to the hard drive and then rip the file from there then I'm seeing around 31fps and my processors are only around 15% idle. I can only assume from this that the SuperDrive can't feed the data fast enough to HandBrake or else I have a problem...although it was able to copy the data to the drive fast enough.
Ignore my earlier posts. Not sure what was happening yesterday but I'm ripping directly from another DVD at the moment with the same settings, with the exception of the video bitrate that has been knocked back to 600kbps, and am now seeing 35fps average with maxed-out processors.
Move along, there's nothing to see here.
Move along, there's nothing to see here.