What Happened!

Cavalicious · Post by **Cavalicious** » Mon Mar 26, 2007 12:17 am

Yesterday I was running test with the different encoding rate that will be compatible with AppleTV, and I encoded Casino Royale in 40 minutes (previously ripped with MTR). Today using the same settings, its taking 2+ hours...all to not even be able to play the MP4 once done. I'm getting a "Not able to open Movie" error with quicktime. My setup is as follows:

24" iMac 2.33 C2D, 2GB RAM, 500GB STA

6000 bitrate (used 7000 yesterday with quicker speeds).
h.264
defaults for rest.

I just deleted and reinstalled Mediafork, encoding now. Still only running Average 27.33 framerate??!!

Lets see if I will atleast be able to play it this time when done.

Please let me know iff I'm doing something wrong.

Cavalicious · Post by **Cavalicious** » Mon Mar 26, 2007 4:53 am

Got it to work...I had to turn off "put hard drives to sleep when possible."

Got my Average Framerate back up to 80fps!

hawkman · Post by **hawkman** » Mon Mar 26, 2007 5:15 am

You're getting 80fps on H.264?! Are you certain? That's blindingly (and suspiciously) fast...

dynaflash · Post by **dynaflash** » Mon Mar 26, 2007 6:15 am

yeah, I would be very suspicious if you are truly getting 80 fps with h.264 especially at 6000 kbps! if you are, I want your computer.

Cavalicious · Post by **Cavalicious** » Mon Mar 26, 2007 1:47 pm

Really, I am.

Its just the 24" iMac with the upgraded 2.33 Core2Duo, 2GB Ram and a 500mb STA HD. Also the upgraded Video card (don't think that matters).

Mind you, I'm not encoding directly from the DVD (You can't with Casino Royale). I ripped it using MTR R14 first.

That being said, I load up the folder in MF and start to encode. It starts out at ~70fps on average then towards the end the Average reads 80fps. Both Cores during the encode read anywhere between 96%-100%.

Now you see why it shocked me when it was taking 2+ hours!

rhester · Post by **rhester** » Mon Mar 26, 2007 2:13 pm

I am unaware of any hardware currently available on the planet capable of 6000kbps H.264 full-resolution encodes at 80fps. Something is wrong.

Rodney

Cavalicious · Post by **Cavalicious** » Mon Mar 26, 2007 2:57 pm

I don't think 6000bps (average) should be considered "full resolution." But either way it did create a 2.49gb .mp4 that works fine with my AppleTV.

If there is something "wrong", I don't think its on my iMac. Maybe the software isn't really encoding 6000bps...I don't know. All I can say is it took ~44 minutes to complete.

jbrjake · Post by **jbrjake** » Mon Mar 26, 2007 3:36 pm

What everyone is trying to politely tell you is that you are probably using ffmpeg to encode and not x264.

And resolution has nothing to do with bitrate.

Cavalicious · Post by **Cavalicious** » Mon Mar 26, 2007 4:17 pm

When I get home, I'll reencode and take pics of the screen. Then you can let me know what I'm doing "wrong."

I'm not trying to argue the "facts." I just want to let all know what I'm doing, and if something is incorrect...correct me by all means.

Cavalicious · Post by **Cavalicious** » Tue Mar 27, 2007 4:28 am

Ok, figured out what I was doing..."wrong" I guess. I was indeed setting it up to encode with h.264 (first). BUT, I was then setting the Destination path, which once done, defaulted the codecs back to to MPEG-4 Video.

Once I realized this, I changed the settings back to h.264 and started to encode @ 6000kbps. I guess this isn't possible, because once completed (avg. 31 fps/2 hours later) the file was unusable (i.e. Quicktime could not open file).

So, all in all, I guess I was wrong (I'll own up), but I would still like to know why the file was unuseable? is 6000 too high for h.264?

hawkman · Post by **hawkman** » Tue Mar 27, 2007 12:10 pm

Shouldn't be - I've (accidentally) encoded stuff at bitrates like that before...