TML 0.2.1 testing

2005-01-11
2013-03-26
  • I must say that i'm really impressed from this new ARM version.
    Finally video plays fine and at least some 100-500 times faster than with 68k version. No color problems, no key-frame problems.I've tried to "fail" the player feeding it with varuous codecs (divx5/4/Xvid) and enabling some advanced mpeg-4 features. Player played 100%fine w/o single problem, except for slight artifact with one feature, that is almost never used anyway.As is see it now - plyaer is already has  decent video optimizations, and plays video at tremendous speeds. Just for reference, i had  to work very hard to reach 25fps with MMplayer(overclodking T3 to 600mhz). All we need is audio suports and SD-card support - and we have a first free player for palm !!!!
    Another good feature i saw while testing - is very small Heap memory requirements. Most clips used about 1mb of  memory. Even full hi-res+ video resolution used only 3mb.
    Great job. Keep up the great progress.
    BTW,  what are "disp" and "dec" good for? I haven't figured out. I also saw some "xvid-edge_size" but i didnt' see any difference when changing it, What does it do?

    All files were tested on my T3 running at 533mhz. (T3 has 12mb of heap)
    Test:...............1
        Video information
    resolution: ........320x136
    codec:..............XviD (v1.1) - latest at the moment)
    video data rate:....130kbit/sec
    fps:................8
    B-frames:...........NO
    Adv. features:......NO
        Resutlts:
    Heap used:..........1063496
    disp:...............12.215%
    dec:................86.542%
    fps:................46.377
    comments:
    This resolution is from converting a DVD that has aspect ratio of 1:2.35 (The Matrix in this case). VEry fast playback. 100% good. No any problems.

    Test:...............2
        Video information
    resolution: ........320x160
    codec:..............XviD (v1.1)
    video data rate:....150kbit/sec
    fps:................8
    B-frames:...........NO
    Adv. features:......NO
        Resutlts:
    Heap used:..........1151352
    disp:...............15.36%
    dec:................83.364%
    fps:................40.951
    comments:
    Used usual (for 320screen) resolution that would be a result of usual-dvd conversion aspect ratio.Played 100% fine.

    Test:...............3
        Video information
    resolution: ........80x48
    codec:..............XviD (v1.1)
    video data rate:....30kbit/sec
    fps:................8
    B-frames:...........NO
    Adv. features:......NO
        Resutlts:
    Heap used:..........267088
    disp:...............15.6%
    dec:................77.45%
    fps:................219.61
    comments:
    Used tiny resoulution and small data rate - as you see i got 220fps - i even hardly noticed any video playback :-) - it was played sooooo fast.

    Test:...............4
        Video information
    resolution: ........320x256
    codec:..............XviD (v1.1)
    video data rate:....250kbit/sec
    fps:................8
    B-frames:...........NO
    Adv. features:......NO
        Resutlts:
    Heap used:..........1647768
    disp:...............12.51%
    dec:................86.550%
    fps:................26.199
    comments:
    Almost full screen. Played 100% fine.

    Test:...............5
        Video information
    resolution: ........320x320
    codec:..............XviD (v1.1)
    video data rate:....250kbit/sec
    fps:................24
    B-frames:...........NO
    Adv. features:......NO
        Resutlts:
    Heap used:..........1978712
    disp:...............16.677%
    dec:................82.87%
    fps:................25.907
    comments:
    Used maxumu resoluton player currently supports.  Not bad at all - 25fps -is a huge speed. Also memory consumption is surprisingly small - only 2  megabytes. it is only 15% of my palm's heap memory.

    Test:...............6
        Video information
    resolution: ........320x160
    codec:..............XviD (v1.1)
    video data rate:....150kbit/sec
    fps:................24
    B-frames:...........1
    Adv. features:......NO
        Resutlts:
    Heap used:..........1151352
    disp:...............13.390
    dec:................85.122%
    fps:................43.252
    comments:
    Used one b-frame here.Played 100% fine.

    Test:...............7
        Video information
    resolution: ........320x160
    codec:..............XviD (v1.1)
    video data rate:....150kbit/sec
    fps:................24
    B-frames:...........3
    Adv. features:......NO
        Resutlts:
    Heap used:..........1151352
    disp:...............14.41%
    dec:................84.96%
    fps:................42.012
    comments:
    I used here 3(!!) b-frames. This is the maximum value that anyone uses.(and very rarely). To my surprise - no problems at all.Even the speed is great (considering b-frames are harder to decode)

    Test:...............8
        Video information
    resolution: ........320x160
    codec:..............XviD (v1.1)
    video data rate:....700kbit/sec
    fps:................24
    B-frames:...........NO
    Adv. features:......NO
        Resutlts:
    Heap used:..........1151352
    disp:...............12.108%
    dec:................86.585%
    fps:................35.453
    comments:
    As you see - i tried to use IMMENSE bitrate here - 700kbit/s. player ate the file fine. and it's only resulted in slightly smaller speed then in previous test.
    I have a question here: how is it possible that same amount of  memory is used for 150kbit and 700kbit streams?

    Test:...............9
        Video information
    resolution: ........320x480
    codec:..............XviD (v1.1)
    video data rate:....350kbit/sec
    fps:................24
    B-frames:...........1
    Adv. features:......NO
        Resutlts:
    Heap used:..........2806072
    disp:...............10.87%
    dec:................88.466%
    fps:................16.646
    comments:
    I know that player currently doens' supports Hi-res+, but i made such large resolution to see the impact on performance and memory. Surprisingly few memory used - less than 3megabytes, and speed is not bad for such large resolution. Not bad at all.

    Test:...............10
        Video information
    resolution: ........320x160
    codec:..............DivX (ver. 4.12)
    video data rate:....350kbit/sec
    fps:................24
    B-frames:...........No
    Adv. features:......NO
        Resutlts:
    Heap used:..........1151352
    disp:...............13.8%
    dec:................84.67%
    fps:................41.87
    comments:
    Used old Divx4 codec - and player played 100% fine. I'm surprised.

    Test:...............11
        Video information
    resolution: ........320x160
    codec:..............XviD (v1.1)
    video data rate:....150kbit/sec
    fps:................24
    B-frames:...........1
    Adv. features:......Q-Pel=ON
        Resutlts:
    Heap used:..........1151352
    disp:...............15.271%
    dec:................83.251%
    fps:................36.453
    comments:
    One b-frame, and Q-pel. Played fine. NO problems whatsoever.

    Test:...............12
        Video information
    resolution: ........320x160
    codec:..............XviD (v1.1)
    video data rate:....150kbit/sec
    fps:................24
    B-frames:...........1
    Adv. features:......Q-Pel=ON, adaptive quantization=ON
        Resutlts:
    Heap used:..........1151352
    disp:...............10.945%
    dec:................87.56%
    fps:................36.816
    comments:
    I used in addition to one b-frame also Quarter pixel (qpel) and adoptive quantization. Played perfectly.

    Test:...............13
        Video information
    resolution: ........320x160
    codec:..............XviD (v1.1)
    video data rate:....150kbit/sec
    fps:................24
    B-frames:...........1
    Adv. features:......Packed bitstream=ON
        Resutlts:
    Heap used:..........1151352
    disp:...............20.324%
    dec:................79.0%
    fps:................56.679
    comments:
    I enabled here packed bitstream.
    i saw artifacts for small period of time- and number of reported frames was more than it should be (about 600 instead of 400)
    also a speed is surprisingly fast for such test. This is the only  feature that didn't work for 100% with player.

    Test:...............14
        Video information
    resolution: ........320x160
    codec:..............DivX 5.2.1 (latest at the moment)
    video data rate:....150kbit/sec
    fps:................24
    B-frames:...........No
    Adv. features:......NO
        Resutlts:
    Heap used:..........1151352
    disp:...............15.468%
    dec:................83.213%
    fps:................48.921
    comments:
    Latest Divx woks also perfectly, and very fast, about the same speed as Xvid (note, i didnt' use b-frames here in Divx).Very good.

     
    • Nicholas Hardy
      Nicholas Hardy
      2005-01-12

      Wow those are much better results then I've had. Although I'm testing on a Tungsten-TE with the lower specs.  Are you sure it didn't increase the heap usage where you had qpel enabled? Because Martijn sent me a sample using that feature, which blew up the memory requirements when I last tested.  Also remember that many people aren't using something as high as a T3.  I think I saw some news item that said that the Tungsten-TE had a big market share.  The TE has only 2MB of heap, so some of your tests wouldn't have run.

      I'd say that the performance+compatibility you're experiencing is a credit to the great work of the xvid developers. Their code is quite nicely portable and as I understand is one of the best MPEG4 implementations in terms of support, quality and speed.

      Note that the code is currently based on XviD 1.0.3. Would there be much advantage to trying out using XviD 1.1 decoder?

      > what are "disp" and "dec" good for?
      These are a just something I wanted for understanding how the performance was going. 'dec' is percentage of CPU time spent in the xvid codec, 'disp' is the percentage spent drawing to the screen.

      > xvid-edge_size
      This is a technical setting within the xvid code which I don't fully understand.  You should find it can have a significant effect on the heap usage.  I need to reduce it significantly to play full-screen on my TE.  If you reduce it to the bottom you should see the same artifacts that appeared in the m68k version.  Note that in the original xvid it has a constant value of 64, so I'm not sure what happens when you reduce it (especially with things like qpel).  I've currently set the default to 32, see if you can find any artifacts at this level that are removed by increasing it.

      > how is it possible that same amount of memory is used for 150kbit and 700kbit streams?
      I'm not entirely sure how codec bitrates work so I'm not sure what goes in those bits.  What I do know is that most of the heap is currently used by allocating various temporary copies of images inside the decoder.  Also the memory usage measurement is taken in between decoding 2 frames - the peak memory usage is probably slightly higher.
      Also remember that since you're testing with a file stream, all the data is coming from RAM. I imagine there will be a reduction in pulling high-bitrate streams off an SD card.

      > packed bitstream
      Could you tell me anything more about that feature? Is it important enough to try fixing the problems soon? You say it's rarely used, I think I remember reading something about it with respect to it being used more with the DivX5 encoder?

       
    • Hi Nickolas
      I made more deep advanced mpeg-4 testing. I took one clips and used same resolution/datarate/framerate in all tests. I only changed codecs/their settings. I also double checked the qpel issue you told me - and i see _exactly_ same heap used
      size  for all  these clips. Reguarding packed bitstream - forget it - it was my mistake. This feature is not only never used and not recommended, but also broken for current Xvid buids. I fould very good Xvid faq here:
      http://ronald.vslcatena.nl/docs/xvidfaq.html
      I tried all Xvid features that are being used:
      Qpel,Gmc,Trellis, mpeg quantization,1-3 b-frames. And everything played 100% good. Only some features slow down playback , as you see by results. I also compaired results to MMplayer. I understand that it is not fare to compare Mmplaer
      to  TML from both sides, but i just wanted to see the relation between how both player handle advanced xvid stuff, and other codecs. I used "benchmark" feature in mmplayer 0.2.12, T3 was running during all tests on the same speed.

      Test:...............1
          Video information
      resolution: ........320x240
      codec:..............XviD (v1.1)
      video data rate:....180kbit/sec
      fps:................15
      B-frames:...........NO
      Adv. features:......NO
          Resutlts:
      Heap used:..........1565032
      disp:...............15.96%
      dec:................83.309%
      fps:................32.65
      MMplayer benchamk...40.7
      comments:
      All adv. features off - also b-frames=off, therefore fastest

      speed

      Test:...............2
          Video information
      resolution: ........320x240
      codec:..............XviD (v1.1)
      video data rate:....180kbit/sec
      fps:................15
      B-frames:...........1
      Adv. features:......NO
          Resutlts:
      Heap used:..........1565032
      disp:...............13.963%
      dec:................85.23%
      fps:................29.089
      MMplayer benchamk...37.3
      comments:
      1 b-frame added. In all next Xvid tests i also use 1 b-frame

      with conjunction with another feature(s)]

      Test:...............3
          Video information
      resolution: ........320x240
      codec:..............XviD (v1.1)
      video data rate:....180kbit/sec
      fps:................15
      B-frames:...........1
      Adv. features:......Q-Pel=ON
          Resutlts:
      Heap used:..........1565032
      disp:...............11.162%
      dec:................89.280%
      fps:................22.831
      MMplayer benchamk...failed, returned me blank error.
      Coomments: Used Q-pel here. As you see - it really affects

      speed. It is also written in Xvid devs told me that this

      feature really increases cpu load and mem usage during

      playback. MMplayer probabl dosnt' support Qpel (at least yet)

      Test:...............4
          Video information
      resolution: ........320x240
      codec:..............XviD (v1.1)
      video data rate:....180kbit/sec
      fps:................15
      B-frames:...........1
      Adv. features:......GMC=ON
          Resutlts:
      Heap used:..........1565032
      disp:...............11.466%
      dec:................87.62%
      fps:................22.831
      MMplayer benchamk...failed,soft reset.
      Coomments: GMC (global motion compensation)   - also much

      slower speed, as in Qpel case.As you see, with gmc case (by

      the way, divx5 has olso gmc now) - TML again wins and plays

      100% fine, while MMplayer (best s/w palyer till now, kinoma

      and smartmovie are crap) - fails, even resets itself. Tha't 

      really good news :-)

      Test:...............5
          Video information
      resolution: ........320x240
      codec:..............DivX 5.2.1
      video data rate:....180kbit/sec
      fps:................15
      B-frames:...........NO
      Adv. features:......No
          Resutlts:
      Heap used:..........1565032
      disp:...............15.33%
      dec:................83.6%
      fps:................31.472
      MMplayer benchamk...40.0
      Coomments:
      Latest Divx5 (free version) w/o any advanced features. As you

      see - it plays almost as fast as Xvid w/o adv. features. 

      Great playback.

      Test:...............6
          Video information
      resolution: ........320x240
      codec:..............DivX 3.1.1 alpha
      video data rate:....180kbit/sec
      fps:................15
      B-frames:...........NO
      Adv. features:......No
          Resutlts:
      Heap used:..........n/a
      disp:...............n/a
      dec:................n/a
      fps:................n/a
      MMplayer benchamk...failed, soft reset.
      Coomments:
      I know that nobody gonna encode movies in this per-historic

      old format, but there are still many clips (dvd-rips) that

      are made w/ this codec. TML didn't play, no error , notheing

      - this is probably not compativle w/ Xvid. MMplayer didnt'

      play it either, soft reset. I didnt' expect other results.

      Test:...............7
          Video information
      resolution: ........320x240
      codec:..............Divx 4.12
      video data rate:....180kbit/sec
      fps:................15
      B-frames:...........NO
      Adv. features:......No
          Resutlts:
      Heap used:..........1565032
      disp:...............14.6%
      dec:................84.2%
      fps:................30.654
      MMplayer benchamk...39.3
      Coomments: Divx 4 is nicely supported. No adv features (since

      they don't exist there). Playback is very fast as well, right

      after Xvid and Divx5.

      Test:...............8
          Video information
      resolution: ........320x240
      codec:..............Xvid v1.1
      video data rate:....180kbit/sec
      fps:................15
      B-frames:...........1
      Adv. features:......Trellis=ON
          Resutlts:
      Heap used:..........1565032
      disp:...............14.1%
      dec:................85.4%
      fps:................29.05
      MMplayer benchamk...38.2
      Coomments: This is similair result to second test where is

      one b-frame. I don't even sure that trellis affects playback

      at all - maybe it's just adds optimization during

      compression, but has no impact on playback whatsoever.

      Test:...............9
          Video information
      resolution: ........320x240
      codec:..............Xvid v1.1
      video data rate:....180kbit/sec
      fps:................15
      B-frames:...........3
      Adv. features:......No
          Resutlts:
      Heap used:..........1565032
      disp:...............14.3%
      dec:................84.98%
      fps:................28.690
      MMplayer benchamk...38.1
      Coomments:
      3 b-frames. Played nicely, only little slower than 1 b-frame.

      Test:...............10
          Video information
      resolution: ........320x240
      codec:..............Xvid v1.1
      video data rate:....180kbit/sec
      fps:................15
      B-frames:...........1
      Adv. features:......Mpeg quantization matrix
          Resutlts:
      Heap used:..........1565032
      disp:...............15.76%
      dec:................83.42%
      fps:................28.143
      MMplayer benchamk...37.1
      Coomments:
      Mpeg quant is used  for higher bitrate encodes, but wanted to

      test it anyway.

      By the way, Nicolas, do you have email or something? I want to send you test files to see the result on TE.

       
    • picard
      picard
      2005-01-12

      Very nice start. I really like what you guys started. I'am the author of BetaPlayer ( http://betaplayer.corecodec.org ) an open-source player for windows ce device. Unfortunatelly I have very little experience with PalmOS developement. But checking out this project I feel the motivation again to start playing with PalmOS a little. I'am sure we can help each other in the future.

      edge_size is the border (in pixels) around the decoder video surfaces so the motion comensation vectors can address out of the original surface rectangle. I think you are safe using 32.

      I tested a clip on my Tungsten3 400Mhz with TML 0.2.1
      http://picard.exceed.hu/kill2na.avi
      heap: 1565040
      FPS: 23.485

      Btw it's interesting for me that mmplayer is not that much faster. Example with BetaPlayer on a wince device with XScale PXA255 400Mhz (similar to T3) I can go above 80fps with this kill2na.avi sample.

      bye, Picard

       
    • Ok, I have done some contrabuting to TML over the last few days. So far what I have done and tested:

      -I have added a Multimedia Player interface to TML using the Phoenity icon set (http://phoenity.com/)
      -I have added OGG Vorbis audio playback support from the POggPL (Palm OGG Player) (http://sourceforge.net/projects/poggpl/)
      -I have added VFS support!!!!! (using the navigator from POggPL). I had to temporarily toss internal support. Although, I think the VFS is more conventional.
      -5-way navigator support in audio playback.

      The navigator from POggPL (a custom gadget) has some issues. It does not allow scrolling so scrolling support will need to be added or the user only gets to see 6 or so lines of files and folders. Also, the navigator pulls from the first card, so if you are a Tapwave user or you use a RAM disk and the files are on the second card you are out of luck. Some how a card selecting option may need to be added.

      I am also working on adding JPEG image support so JPEG image files can be viewed, zoomed and panned. I am attempting to add features to directly compete with the not so much competitive Kinoma (with its buggy image viewing support).

      The video playback was way too fast for me (but hey, that's not a bad thing), so I put a temporary 4 tick delay after the drawing code. I also started setting it up so it centers the movie on a square in the screen. Although it is not really centered on the x coordinates. I used the function (screenWidth - videoWidth) / 2 to center the video. Some video scaling would be nice here for videos larger than the screen. Also, eventually full screen (160x160, 320x320, 480x320, 320x480) mode support with no controls (tap screen during video playback to access controls) would be good.

      Also, junglemike, what are you using to encode the avi files? I did some tests using PocketDVD for Palm and got OK results. Using the option to make the video a width of 160 (I forget the height) only about 60% of the 14 second clip plays (the dancing Panda scene from *My Fellow Americans*). I did another encoding using the almost 320 pixil across setting of the same (well almost, give or take a hand full of milliseconds) scene. This scene plays about 45% and then pops up a "Fatal Exception" dialog. It does this in the 0.2.9 version and in my tweaked version. I am not sure of any technical details though. Also I did a 5 second encoding of the WB opening scene of the movie that goes to some gold text then stops. The only thing that plays is the WB logo fading then it stops. BTW, I am using a Tungsten T3 at 400MHz.

      Another thing that will need to be done is allowing buttons to be tapped (Pause, Stop, volume, position) during video playback. It would suck to have to wait an hour or two before regaining control of the Palm without a reset.

      If you want the source code please send an email to dkirker _at_ worldnet.att.net. Also, could I be added as a developer to this project? I am not good with codecs, but I can add some features.

      Thanks,
      Donald Kirker

       
    • Nicholas Hardy
      Nicholas Hardy
      2005-01-13

      I've started some work on a new 0.3 branch. I haven't seen your code yet, but it might be better to make the changes again in this version. It has some more internal structure to it, includes some preliminary work on decoding AVI files with full video + audio playback (raw uncompressed at the moment).  Some of the other changes you've mentioned would possibly be easier to make on this version.  I've always considered the 0.1, 0.2 versions to just be a hacked copy of xvid (and the sample xvid_decraw.c code).  The 0.3 version isn't released yet, but see 'Development Status' in Docs for more information.

      In previous discussions I think we'd said that the first aim of the project would be to get a working movie player going.  Under that plan playback of straight audio and display of image files could wait till later.  Of course if we have enough developers, then we can do many things simultaneously. :)

      We should discuss our goals and milestones further in another thread.

       
    • Donald C. Kirker
      - Sounds terreific, is there something to try out?
      I would love to see more people joining the project.
      - you said about ogg support. I think it's impossible to add .ogg stream to avi container. At least i didn't see any. Or maybe you are implying that we also need to support .ogm container stright from the beginning.?

      - picard
      Hey, Beta player is a masterpiece!! I've always dremed of something similair for palm platform. MMplayer/SmartMovie/Kinoma are so crippled, so buggy, shareware products, compared to beta.

      MMplayer has huge problems playing full screen video on 480-res palms, the workaround is to pre-rotate video (see this thread for details)
      http://www.mmplayer.com/forums/viewtopic.php?t=1753
      If you try to play, say 480x272@25fps@300kbps file "as is" on 400mhz T3 - you'll get less than 10 fps
      SmartMovie is also VERY slow - and i was unalbe to get more than 12-16fps on full screen even overclocking T3 to 533-600mhz.
      Kinoma - is total crap, it doesn't even support .avi container and cost 50$.
      That's all options we currently have for palm.
      notheing that could play .ogm/mkv/wmv/mp4 at all. So my opinion is that this player will have huge success, even if it will have only 1/5 of beta's capabilities.

       
    • I will post what I have done so far after school (3pm PST) at a website for another one of my projects.

      junglemike, OGG support is separate. What I have so far allows you to play either adio-less videos (using ver. 0.2.9) or OGG Vorbis adio files (sing POggPL). I have found an open source JPEG library that has VFS support which could be for the image viewer.

      What I have implemented so far has three modes: Msic, Video, Image. In order to listen to msic files you mst be in Music mode, in order to view videos you mst be in Video mode, etc. etc. It is easy to switch between modes.

      When I post the binary and source I will post some screen shots.

      Also, Nicholas, when do you think you will have ver. 0.3 ready? I did see the source you have posted at the Subversion Repository, but I am reluctant to start re-adding the Media Player features if there will be any major changes.

      Also, I lied. the navigator from the POggPL does allow scrolling. It is jst very user-unfriendly. You have to drag your pen up and down in the navigator area to scroll and in order to scroll up you must start scrolling down first otherwise it will only select a song or file (depending on the mode you are in).

      I have successfully gotten video's to play off VFS with the navigator from POggPL, so I think we may have some work cut out if we used it.

      Anyway, I would like to help out. I am not good with codecs but I can do things with the interface and what I have already done. Let me know how I can join.

      Thanks,
      Donald

       
    • >junglemike, OGG support is separate. What I have >so far allows you to play either adio-less videos >(using ver. 0.2.9) or OGG Vorbis adio files (sing >POggPL). I have found an open source JPEG library >that has VFS support which could be for the image >viewer.
      Ok, now i really puzzled,  All this sound revolutionary, but where can i get it to try? Where version 0.2.9???  - All i can see  -is 0.2.1 version that i already tested. I'm dying to try the new things.

      >When I post the binary and source I will post some >screen shots.
      Whre do you post all this stuff?

      >Anyway, I would like to help out. I am not good >with codecs but I can do things with the interface >and what I have already done. Let me know how I >can join.

      If it was up to me - i would be more than happy. Althought i didn't see all this good stuff you are talking about - but sounds promising.

       
    • Ahh, I mean version 0.2.1 (got the version and release date screwed up). I am posting the sources at http://www.wapuniverse.com/other/projects/TML/source.zip, binary at http://www.wapuniverse.com/other/projects/TML/mediaplayer.prc, and screen shots at http://www.wapuniverse.com/other/projects/TML/screens.html.

      I am going to get the subversion 0.3 from the subversion repository and play with it.

      And about the OGG media file support, its like Windows Media Player. It plays MPEG (AVI) video files and MP3 audio files. Well, I have gotten The Magic Lantern to play MPEG (AVI) video files and OGG Vorbis audio files. Soon to come from my end will be a JPEG image viewer for the ultimate multimedia experience (well, not ultimate yet..., but soon, I hope).

      -Donald

       
    • pablo
      pablo
      2005-01-14

      Hello,

      Could you also make the 0.2.9 version available?

      Thanks.

       
    • Nicholas Hardy
      Nicholas Hardy
      2005-01-14

      Donald: I've had a look at the source, looks nice. What stage would you say it's at? It looks like there's bits you're still working on. Anyway, I've committed it to the repository with very little change (in src.arm).

      I've added you as a developer to sourceforge. A password to write to the subversion repository has been emailed to dkirker _at_ worldnet.att.net.

      If you feel it's ready to release, then go ahead anytime. By the way we've labelled the previous versions I would make this 0.2.2. To be consistent with the previous release you can use this http://hi.errai.net/~nicholas/magiclantern/Makefile.release makefile which builds all the source+binary files automatically - but you might not have all the requirements in a minimal cygwin environment. Run as 'VERSION=0.2.2 make -f Makefile.release' in an empty directory together with a README.txt and testmovie.avi.pdb. But you can really do whatever you want :)

      As for the 0.3 version, it's coming along nicely. Ironed out a few bugs in it recently. Works fairly nicely playing an uncompressed avi with audio + video. Seems to keep reasonable sync (in ideal circumstances). The VFS playback isn't working at the moment, but I'll try to get a release of what's working out soonish.

      Most of the 0.3 API stuff is still uncertain, you'll see that half of what's declared in the headers isn't even coded yet. Still, there shouldn't be too many major changes in the near future. For some idea of what I intended with the structure look at http://hi.errai.net/~nicholas/magiclantern/designFull.png. This design didn't include playback of straight audio files, but that capability could certainly be added. At the moment all the code under that design is in the backend subdirectory, the code in the 'main' directory is more likely to be changed.

      One final thing: sorry, but I'm going to be away for a week (Saturday 15 - Saturday 22). Have fun while I'm away :)  I'll get on later tonight so I can reply if you've got any questions.

       
    • Nicholas Hardy
      Nicholas Hardy
      2005-01-14

      Ok, I've got a sample version of 0.3 for you to play with.

      http://hi.errai.net/~nicholas/magiclantern/TML_Player-0.3-pre1-bin.zip

      Use it with an uncompressed avi only. Same business as before with creating a testmovie.avi stream database. This time the avi must have raw RGB data (BGR24 in particular). The audio stream must be raw PCM (_should_ support most audio frequencies and bit sizes, but most of my tests have been with something like 44100Hz,16,little-endian,stereo). 

      Big resolutions WILL fail.

      VFS playback is still choppy and unstable, I'll work on that when I get back (unless someone else wants to fix it in the meantime).

      A/V sync is a bit simplistic at the moment. It's pretty easy to make a video which will play badly.

      Because of all these limitations, I haven't included it as a release yet (I am calling it 0.3-pre1).  Feel free to test it a bit within these limits if you like, but I'm posting this more so you can see where its up to (without having to build the code yourself).

       
    • Hans Schmucker
      Hans Schmucker
      2005-01-24

      Didn't try anything besides the standard testdata and version 0.2.1, but it seems to work perfect on the zodiac and I'm getting around 50 fps (48 - 51)