Inventive Software
23rd June 2007, 15:25
Hey there everybody!
Whilst feeling a little bored last night, I decided to break out the 5 GB uncompressed 1080p RGB24 sample video I'd downloaded a long time ago, when a user whose name escapes me provided some short lossless 1080p samples to the community. I downloaded the "Life" sample, which is NTSC, 825 frames, 1920x1080, and (as mentioned earlier) RGB24.
Since I have a codec test coming up in a few months, I thought it best to try Microsoft's VC-1 codec (aka WMV9 Advanced Profile) for size and quality. Unfortunately, whilst I have the codec and the sample, I don't have the computer to encode OR decode it (my desktop's about 5 years old, my laptop has no battery and I've lost the power supply [the klutz I am :D])! Nevertheless, I set up Windows Media Encoder to the ready, set up a profile that provided me with the following constraints:
10 Mbps VBR, 25 Mbps peak. No audio since the sample doesn't have it.
Using WMV Powertoy excellently provided by Zambelli, I configured the encoder to conform to Advanced Profile, with the Inloop and Overlap filter on, and B-frames set to 1. I can't remember the other options, and I'll provide them next time I'm online.
The CPU is a *gulp* Celeron 800 MHz that has nothing more complex than SSE (1). :D The RAM is 512 MB of PC133 SDRAM. Hard disk is a 120 GB separated into several partitions, NTFS being the partitions used where the sample was stored.
Because space is limited on my computer, I first encoded the sample with Lagarith 1.3.12 to reduce the file size and bandwidth requirements for the hard disk, and got the sample down to 2.25 GB and 700 Mbits/sec from 1.5 Gbits/sec and 5 GB.
Now, timings. :D
Since this is a slow computer, and I had lots of time on my hand, I wasn't worried how long it would take. I was surprised just HOW slow it was, so much so I had to add SPF values alongside the FPS encoder values to figure it out (SPF = Seconds Per Frame :eek:). Anyway, figures!
Pass 1 took (wait for it): 27 minutes 53 seconds, or 1673 seconds. Encode FPS was: 0.4931261 FPS, or 2.0278 seconds per frame!
Pass 2 was longer, and took: 1 hour, 25 minutes, 23 seconds, or 5123 seconds. Encode FPS was a mind-numbing 0.1610384 FPS, or 6.2096 seconds per frame! I felt sure I could count the macroblocks being encoded! :D
I must thank my Celeron 800 for not cracking under the pressure, and it did a masterful job of not overheating in 2 hours of 100% CPU usage! Nevertheless, a Core2Duo would have been VERY nice in this regard. Donations welcome BTW. :)
The encoded file is about 30 MB, and I can't play it, so need people with capable horsepower to see what it looks like.
Download link: http://www.megaupload.com/?d=Z3FFXTAI
I think the average bitrate ended up being about 10 Mbps. I'm currently trying H.264 with x264 (on the same hardware, yes I'm nuts) and seeing what that looks like (having FINALLY figured out x264 can't handle RGB24 *glares at devs ;)*).
One thing I've noticed is that MS's VC-1 implementation seems desperately slow compared to x264. It's high time that they speed it up and severely optimise it so that it's around x264's speed. Just my $0.02.;)
Whilst feeling a little bored last night, I decided to break out the 5 GB uncompressed 1080p RGB24 sample video I'd downloaded a long time ago, when a user whose name escapes me provided some short lossless 1080p samples to the community. I downloaded the "Life" sample, which is NTSC, 825 frames, 1920x1080, and (as mentioned earlier) RGB24.
Since I have a codec test coming up in a few months, I thought it best to try Microsoft's VC-1 codec (aka WMV9 Advanced Profile) for size and quality. Unfortunately, whilst I have the codec and the sample, I don't have the computer to encode OR decode it (my desktop's about 5 years old, my laptop has no battery and I've lost the power supply [the klutz I am :D])! Nevertheless, I set up Windows Media Encoder to the ready, set up a profile that provided me with the following constraints:
10 Mbps VBR, 25 Mbps peak. No audio since the sample doesn't have it.
Using WMV Powertoy excellently provided by Zambelli, I configured the encoder to conform to Advanced Profile, with the Inloop and Overlap filter on, and B-frames set to 1. I can't remember the other options, and I'll provide them next time I'm online.
The CPU is a *gulp* Celeron 800 MHz that has nothing more complex than SSE (1). :D The RAM is 512 MB of PC133 SDRAM. Hard disk is a 120 GB separated into several partitions, NTFS being the partitions used where the sample was stored.
Because space is limited on my computer, I first encoded the sample with Lagarith 1.3.12 to reduce the file size and bandwidth requirements for the hard disk, and got the sample down to 2.25 GB and 700 Mbits/sec from 1.5 Gbits/sec and 5 GB.
Now, timings. :D
Since this is a slow computer, and I had lots of time on my hand, I wasn't worried how long it would take. I was surprised just HOW slow it was, so much so I had to add SPF values alongside the FPS encoder values to figure it out (SPF = Seconds Per Frame :eek:). Anyway, figures!
Pass 1 took (wait for it): 27 minutes 53 seconds, or 1673 seconds. Encode FPS was: 0.4931261 FPS, or 2.0278 seconds per frame!
Pass 2 was longer, and took: 1 hour, 25 minutes, 23 seconds, or 5123 seconds. Encode FPS was a mind-numbing 0.1610384 FPS, or 6.2096 seconds per frame! I felt sure I could count the macroblocks being encoded! :D
I must thank my Celeron 800 for not cracking under the pressure, and it did a masterful job of not overheating in 2 hours of 100% CPU usage! Nevertheless, a Core2Duo would have been VERY nice in this regard. Donations welcome BTW. :)
The encoded file is about 30 MB, and I can't play it, so need people with capable horsepower to see what it looks like.
Download link: http://www.megaupload.com/?d=Z3FFXTAI
I think the average bitrate ended up being about 10 Mbps. I'm currently trying H.264 with x264 (on the same hardware, yes I'm nuts) and seeing what that looks like (having FINALLY figured out x264 can't handle RGB24 *glares at devs ;)*).
One thing I've noticed is that MS's VC-1 implementation seems desperately slow compared to x264. It's high time that they speed it up and severely optimise it so that it's around x264's speed. Just my $0.02.;)