Results 1 to 8 of 8

Thread: AonE vs Bakasan codecs/methods?

  1. #1

    AonE vs Bakasan codecs/methods?

    Everything from AonE plays perfectly for me, but every time I try downloading and playing something from Bakasan, I get lots of artifacts and my player always crashes.

    Does anyone else have this problem, and do you know what the cause is?

    TIA

  2. #2

    AonE vs Bakasan codecs/methods?

    This is likely to open up a can of worms....

  3. #3

    RE: AonE vs Bakasan codecs/methods?

    why do people try to get bakasan's version... they always fuck you up... in my opinion with misstranslations on purpose and a torrent with a single seed so that people waste their time trying to get the episode

  4. #4

    RE: AonE vs Bakasan codecs/methods?

    man this shit never stops does it....

    well since i'm such a nice person, i'll explain it to you

    anbu-aone episodes are encoded in divx

    bakasan eps are encoded in xvid.

    download the xvid codec at www.divx-digest.com/software/xvid.html

    and download the latest ffdshow at
    http://sourceforge.net/project/showf...ckage_id=59355

    to be honest i've downloaded a few bakasan eps before and they aren't too bad if bakasan did all the work himself


  5. #5

    AonE vs Bakasan codecs/methods?

    Originally posted by: kage_bunshin
    man this shit never stops does it....

    well since i'm such a nice person, i'll explain it to you

    anbu-aone episodes are encoded in divx

    bakasan eps are encoded in xvid.
    mplayer naruto.ep.075.anbu-aone.avi
    MPlayer 0.92-3.2.2 (C) 2000-2003 MPlayer Team
    CPU: Intel Celeron 2/Pentium III Tualatin (Family: 6, Stepping: 1)
    Detected cache-line size is 32 bytes
    CPUflags: MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 0
    Compiled for x86 CPU with extensions: MMX MMX2 SSE

    Playing naruto.ep.075.anbu-aone.avi
    AVI file format detected.
    VIDEO: [DX50] 640x480 12bpp 23.98 fps 1157.7 kbps (141.3 kbyte/s)
    Clip info:
    Software: VirtualDubMod 1.5.4.1 (build 2066/release)
    ================================================== ========================
    Opening audio decoder: [mp3lib] MPEG layer-2, layer-3
    MP3lib: init layer2&3 finished, tables done
    AUDIO: 48000 Hz, 2 ch, 16 bit (0x10), ratio: 16000->192000 (128.0 kbit)
    Selected audio codec: [mp3] afm:mp3lib (mp3lib MPEG layer-2, layer-3)
    ================================================== ========================
    vo: X11 running at 1152x864 with depth 24 and 32 bpp (":0.0" => local display)
    ================================================== ========================
    Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
    Selected video codec: [ffodivx] vfm:ffmpeg (FFmpeg MPEG-4)
    ================================================== ========================
    Checking audio filter chain for 48000Hz/2ch/16bit -> 48000Hz/2ch/16bit...
    AF_pre: af format: 2 bps, 2 ch, 48000 hz, little endian signed int
    AF_pre: 48000Hz 2ch Signed 16-bit (Little-Endian)
    AO: [oss] 48000Hz 2ch Signed 16-bit (Little-Endian) (2 bps)
    Building audio filter chain for 48000Hz/2ch/16bit -> 48000Hz/2ch/16bit...
    Starting playback...
    <u>This file was encoded with XviD build 26</u>
    VDec: vo config request - 640 x 480 (preferred csp: Planar YV12)
    VDec: using Planar YV12 as output csp (no 0)
    Movie-Aspect is 1.33:1 - prescaling to correct movie aspect.
    VO: [xv] 640x480 =&gt; 640x480 Planar YV12
    Exiting... (Quit)


    Yeah, AonE uses DivX *mumble mumble*
    The only thing AonE does is use the DivX compatibility mode to fake a [DX50] header instead of [XVID] so that DivX codecs can play it (or recognize that they can). And AonE uses releases from the stable branch of XviD that can be replayed by most MPEG4 decoders, whereas others sometimes encode wtih the most actual XviD development snapshot.

    The difference is the way the codec is used - and don't blame the codec for that. It's just the difference between a good and a bad encoder.
    --
    "If you were young again, would you start writing TeX again or would you use Microsoft Word, or another word processor?
    I hope to die before I have to use Microsoft Word." (Donald E. Knuth)

  6. #6

    RE: AonE vs Bakasan codecs/methods?

    Even with the latest codecs installed, I still got tons of artifacts, until my player crashed.

    So it's just a codec issue? I'll try to see if they play on a fresh install.

    Although I prefer the AonE ones, it's nice to be able to see the Bakasan ones a couple of days before the AonE ones come out.

    Thanks guys.

    Elessar, How'd you pull that info? TIA.

  7. #7

    RE: AonE vs Bakasan codecs/methods?

    This brings up a intresting question. I assume gotwoot is a arm of AonE. These forums are here so we can talk about release and etc.

    But asking about another groups encoding methods, especially someone like bakasan on a forum where we do the same thing... i dunno.

  8. #8

    AonE vs Bakasan codecs/methods?


    <u>This file was encoded with XviD build 26</u>


    Yeah, AonE uses DivX *mumble mumble*
    The only thing AonE does is use the DivX compatibility mode to fake a [DX50] header instead of [XVID] so that DivX codecs can play it (or recognize that they can). And AonE uses releases from the stable branch of XviD that can be replayed by most MPEG4 decoders, whereas others sometimes encode wtih the most actual XviD development snapshot.

    The difference is the way the codec is used - and don't blame the codec for that. It's just the difference between a good and a bad encoder.[/quote]

    Oops my bad. haha

    Thanks for correcting me

    Wait actually, i checked the properties in the older eps, and it says its encoded in Divx

    The recent anbu-aone eps starting from ep 53 i think say XviD though

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •