I save a jpeg file with photoshop CS4 (baseline standard in photoshop’s option). But nenojpeg can’t decode it. It’s error code is NJ_SYNTAX_ERROR.
Can you give me any suggestion about this problem?
Thanks!

Thx a bunch ! ( i added loop and stream from memory, now to implement simple fft )

Video: http://video-test-sequences.hexagon.cc/torrents
Audio: http://cid-bee3c9ac9541c85b.skydrive.live.com/browse.aspx/.Public/LadyWashington
Demo disk info: http://x264dev.multimedia.cx/?p=328
Avisynth script: http://forum.doom9.org/showpost.php?p=1394744&postcount=622

1. freely available
2. 1080p/24
3. running time of a few minutes
4. good mix of static, high-detail scenes and action scenes
5. typical content with real, photographed/filmed images

As cool as »Big Buck Bunny« and »Elephants Dream« might be, they barely fulfill point 4 and they absolutely miss point 5. When comparing codecs, real-world images, CG and cartoons are three completely different worlds. I’d like to focus on real images, but if I was going to include CG imagery as well (I’m not sure yet), I’ll certainly include »Big Buck Bunny«, as it’s just perfect for that case.

See: http://media.xiph.org/

I am also curious how well animated sources are compressed. I have come across http://x264dev.multimedia.cx/?p=102, but the source used seems to have been SD as well and the output bitrate is at just 250kbps. If it’s not too much of a hassle, could you include a HD cartoon source in the next instalment as well?

A common mistake people make is picking a CRF value and then changing an option to see how the filesize changes and then using the size difference to determine how much that option changes compression efficiency. That’s because the simple explanation for CRF encoding is that it produces constant quality, but the options used change the way the rate factor is calculated. So you pick a slower option, get a larger filesize and end up being confused. This is particularly apparent if you turn of the psy-stuff, for instance by using –subme 5 and comparing it to the defaults, where you end up with higher encoding speed and lower filesize.

nurbs: In fact, I use --crf for my personal encodes all the time, because it saves you the second pass without sacrificing quality – the only downside is that you don’t have any kind of direct control over the target bitrate, but since I’m usually encoding files for online distribution or hard drive storage, this isn’t an issue. For the codec comparison, however, two-pass encoding is the only way, because I want a specified target bitrate there.

About bitrates: I generally encode my blu-rays downscaled to 720p (actually 1280*xxx; depending on the aspect ratio of the movie) with –crf 21 in x264, which lets the codec decide the bitrate based on the complexity of the video. The quality is good enough for me, and while I can tell the difference when I’m looking for it it’s nothing I’d notice when I’m just watching the movie.
With that setup I get bitrates mostly between 2 and 4 Mbps, so depending on the content and the level of quality you are satisfied with 4 Mbps is probably a reasonable bitrate for 720p if you want rather good quality on most sources. Stuff like 300 or Planet Terror will probably take more than that if you want transparency to the source. Generally grainy or old footage takes more bitrate, while the new stuff shot with digital cameras can be compressed better because there is less noise and grain.

Edit: Damn it, I meant: For instance 0.98 is twice as good as 0.96, which is twice as good as 0.92.