Pearl Harbour on Flask

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Trancemaster
    Snoogins
    • Dec 2001
    • 149

    Pearl Harbour on Flask

    I'm at the end of my tether with this one.

    I ripped Pearl Harbour with Smart Ripper no problem. I then set it encoding on Flask, DivX3.11. It came out alright, but the quality was a bit poor. I decided to re-encode, with DivX 4.12 instead. I set it on 1 pass quality based and was ready for a massive file size. I used MP3/96Kb/48000Hz for the audio, no crop or anything. I set it going, and it took about 8 hours. This morning I went to check the quality and found a 2.7Gb file! But guess what? I open it in WMP (XP) and get an error saying it is an unknown file format. I then tried playing it in the Playa, which promptly crashes. I then tried looking at the properties, but Windows said they could not be displayed. Has anyone else come across this problem? I don't really want to set it going again for another 8 hours if this is going to happen again. I'm about ready to give DivX up and move to VCD instead.

    As far as info goes my PC is Athlon 1Ghz, 384MB RAM, Win XP, Flask 0.6 Preview. I've made plenty of DivX's with no problems, but just recently things seem to be going downhill. I'm wondering whether it might have something to do with DivX4.12, 4.11 never gave me any problems.

    Any help would be greatly appreciated.
    Snooch to the Nooch!
  • UncasMS
    Super Moderator
    • Nov 2001
    • 9047

    #2
    avi is limited to 2gb


    there is no other reason i could think of!

    i did a 3 cd nandub rip with a predicted 2.2gb síze

    everything was fine with that file/size

    Comment

    • Trancemaster
      Snoogins
      • Dec 2001
      • 149

      #3
      It's OK, I think I sorted it now.

      I opened the file in VirtualDub and the AVI import filter said it was "reconstructing missing index blocks" This took about 5 mins. I then did a direct stream copy to a new avi. The file still would'nt play, but it got a bit further before crashing! I re-opened it in VirtualDub again and asked the import filter to re-derive the keyframes. This took about four hours, but at least the file plays now! I guess the file must have just been corrupted or something.

      Cheers anyway Uncas!
      Snooch to the Nooch!

      Comment

      Working...