I recently bought a canon XF105(http://www.kdenlive.org/video-editor/canon-xf105) which outputs @ 50Mbps MXF container, mpeg2 codec.

The current issue I am facing is the audio de-synchronizes from the video(as if the video lags in playback)(I've tried splitting audio track with avidemux)

I'm currently running on a i7 920 with 6GB of ram. I'm wondering if it's a seeking problem with the MXF format and requires trans-coding it to a more friendly format .ts or something

I know my hardware can play the video, I've tried it under *gasp* windows in Sony vegas pro 8 with no issues

You shouldn't have seeking issue with mpeg-2, in theory... Anyway the stable version of avidemux havs well known A/V sync issues. You can use the 2.6 "nighly builds" win32 (yes, NOT 64-bit) under WINE. It works and it keep everything in sync as long as you cut at keyframes specific points seeking with the "double arrow" button.
Here is the link:
http://avidemux.org/nightly/win32/
They upload new versions almost every day...
Ignazio

I've tried playing with melt and I get the same issue. I was only using avidemux to extract the audio, and not re-encode it

Does it also desynchronize when played with "ffplay"?

Tried compiling melt from git and kdenlive from svn and still get a desync with ffplay & in kdenlive. Any ideas why it's not playing correctly?

$ ffplay AA000501.MXF
ffplay version N-30954-g1986380, Copyright (c) 2003-2011 the FFmpeg developers
built on Jun 22 2011 13:28:34 with gcc 4.6.0 20110603 (prerelease)
configuration: --prefix=/usr --enable-libmp3lame --enable-libvorbis --enable-libxvid --enable-libx264 --enable-libvpx --enable-libtheora --enable-postproc --enable-shared --enable-x11grab --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libschroedinger --enable-libopenjpeg --enable-librtmp --enable-gpl --enable-version3 --enable-runtime-cpudetect --disable-debug
libavutil 50. 43. 0 / 50. 43. 0
libavcodec 52.122. 0 / 52.122. 0
libavformat 52.110. 0 / 52.110. 0
libavdevice 52. 5. 0 / 52. 5. 0
libavfilter 1. 80. 0 / 1. 80. 0
libswscale 0. 14. 1 / 0. 14. 1
libpostproc 51. 2. 0 / 51. 2. 0
Input #0, mxf, from 'AA000501.MXF':
Duration: 00:00:10.01, start: 0.000000, bitrate: 52173 kb/s
Stream #0.0: Video: mpeg2video (4:2:2), yuv422p, 1920x1080 [PAR 1:1 DAR 16:9], 50000 kb/s, 29.97 fps, 29.97 tbr, 29.97 tbn, 59.94 tbc
Stream #0.1: Audio: pcm_s16le, 48000 Hz, 1 channels, s16, 768 kb/s
Stream #0.2: Audio: pcm_s16le, 48000 Hz, 1 channels, s16, 768 kb/s
[buffersink @ 0xc89f60] auto-inserting filter 'auto-inserted scaler 0' between the filter 'src' and the filter 'out'
[scale @ 0x7f45b0000b40] w:1920 h:1080 fmt:yuv422p -> w:1920 h:1080 fmt:yuv420p flags:0x4
[mpeg2video @ 0xc81ee0] warning: first frame is no keyframe 0B f=0/0
^C 6.01 A-V: -4.444 s:0.0 aq= 0KB vq= 0KB sq= 0B f=0/0 f=0/0
Last message repeated 1 times

There is a problem with libavformat with the particular MXF generated by your camera. You can report it as a bug to libav.org or ffmpeg.org.

Well I googled what codec the XF105 was using, it's a custom codec (XF) that is based off of the mpeg-2 codec. Thank you all for your help :) I've submitted a ticket with ffmpeg