Phoronix IRC Log: 2009-12-09
Kano: michaellarabel: could you buy a bluray drive? your h264 testfile is really boring with 10% cpu usaage
GNU\colossus: http://şøñđëřżēıċħęŋđőmæîņĭśŧşũþėŗ.de/char.jpg
michaellarabel: Kano I have a Blu-ray drive in one of my test systems I think
Kano: then rent a bluray
Kano: use win and the correct tool
michaellarabel: I have Blu-rays as well but not any uncopyrighted material
Kano: there is a bluray with the blender movies
Kano: maybe those have got high rate m2ts
Kano: or use any other file, as long as you dont upload it
Kano: i hope you know how to rip an iso
Kano: is the big buck bunny bluray not available in the us
Kano: you can buy it in germany
Kano: http://www.amazon.de/Buck-Bunny-Blu-ray-Sacha-Goedegebure/dp/B001EKNKBG/ref=sr_1_1?ie=UTF8&s=dvd&qid=1260365854&sr=8-1
Kano: no idea of the bitrate used however
Kano: usally animations look best on bluray
Kano: at least the comments show that the encoding must be really good
michaellarabel: Where in Germany can you find the movie?
Kano: everywhere?
michaellarabel: Ohhh, you mean through Amazon, I thought you meant in a store.
michaellarabel: I will be back in DE in like two weeks if I do find it in a store
Kano: i saw it in media market too. most likely in others like saturn (which is easy to find in munich)
michaellarabel: Yeah, I know saturns in Munich, but what about Berlin?
Kano: it must be there too
michaellarabel: k
Kano: something special in berlin?
michaellarabel: Just some business.
Kano: hmm just saw that vc1 is used for bbb
Kano: many are vc1
Kano: btw. your git repo is always broken when you commit somthing new
michaellarabel: Yes I know and it's not because of my Git viewer at all but something else.
Kano: but how can you commit something that is in a tar file but not in git?
michaellarabel: Because of how its pulled off the local drive but when the Git command is fetching it over HTTP it's not going correctly. I think one of the post hooks is not working right on committing.
Kano: should be easy to track
Kano: just add status output to your hooks
Kano: and check error level
Kano: michaellarabel: first hack could be using always exit 0 to end your hooks
Kano: best add a message at begin + end to see where it stops
Kano: michaellarabel: did you try adding a begin/end message to your hooks
Kano: to find which is the bad one
michaellarabel: Not yet, though I just made a commit, probably broke things again. I think I know what hook is bad, I just haven't had time to confirm.
Kano: michaellarabel: before you test your hooks
Kano: checking phoronix-test-suite.diff:
Kano: 6 files changed, 16 insertions(+), 7 deletions(-)
Kano: missing files: 2
Kano: maybe fix it first
michaellarabel: well i just committed a few new files that should be fixed when I run the command manually