CANOPUS PROCODER DEMO > > Frames Per Second Slowdown

Discussion in 'Professional Video Production' started by Juna Kuristag, Sep 9, 2003.

  1. For all the Canopus Procoder-savvy:

    What causes the frames per second to slow down at a drastic rate when
    transcoding from MPEG2 to DV AVI?

    Some of my MPEG2 files output to as much as 13 frames per second and finish
    in decent/moderately fast time. Other files on the other hand start at 10+
    frames per second and slowly decline all the way till its practically zero.
    It takes so long I might as well start digging my own grave and just wait
    till the time goes by.

    For example, one of the MPEG2 files (34 MB) was outputted into DV AVI
    (Microsoft NTSC) in around 1:49 seconds. Another MPEG2 file (also 34 MB)
    was estimated to finish in 54 hours. Talk about insanity.

    I'm using a 1.7 Ghz Pentium Pro, with 1 GB of RAM and 120 GB of HD space.
    WinXp Pro.


    Note: This is not the first post I've seen on usenet regarding this ---
    check it out:
    From: John ()
    Subject: Procoder demo is taking DAYS to encode a 90 minute video?
    Date: 2002-08-28 09:03:24 PST

    I grabbed Canopus's Procoder and I fed it a 90 minute video and when
    it starts, the frames per second are around 15 or so but it quickly
    drops to almost nothing......encoding time rises from a few hours to
    DAYS and cpu usage is almost 0. What gives? I'm using WinXP Pro Corp.
    with a p4/1.6A.

    I've been encoding videos long enought to know something is screwed
    with their encoder. Any clues? I tried Canopus's support forums but
    get some SQL error.===============
    Juna Kuristag, Sep 9, 2003
    1. Advertisements

  2. Juna Kuristag

    Juan Lauda Guest

    Sounds like the OS is running out of resources.

    Try using Task Manager and/or Performance Monitor to monitor the physical
    and virtual memory usage.
    With 1GB of RAM installed you would think that this would be enough, but if
    the ProCoder software has memory leaks then it will never be enough...
    Juan Lauda, Sep 9, 2003
    1. Advertisements

  3. Nothing seemed out of the ordinary when looking at the performance monitor
    ..... quite a bit was used for processing but even when the dropouts started
    happening, there was little change in the figures ... that is, unless I just
    don't know how to read em =)

    A temporary fix (that doesn't work with all MPEG2 files) is if you cut them
    up and convert them in less frames. I'm not sure exactly why this makes a
    difference with some files, but been having some success experimenting
    around. It may have to do with the way the files were encoded in the first
    place and where they came from. Of course, this is purely assumption and
    not everything has worked with this method. But its better than waiting
    thats for sure.
    Juna Kuristag, Sep 9, 2003
  4. Juna Kuristag

    Juan Lauda Guest

    You need to monitor the memory, virtual memory and disk usage statistics,
    not the CPU usage, when ProCoder starts misbehaving. Memory usage is
    obvious, the virtual memory and disk usage statistics will show when
    ProCoder is running out of real memory and relying more and more on the
    memory paging file. This type of behaviour is symptomatic of memory leakage
    in an intensive process and is born out by the fact the the symptoms are
    less acute when coding smaller files. This is because it requires less
    memory to buffer a smaller file.
    Juan Lauda, Sep 9, 2003
  5. I'm beginning to believe that the encoding of the original file may have
    something to do with the sudden drop in frames. I have tested one
    particular file and it constantly drops in the same spot along the progress
    bar almost every single time.

    Probably my temporary fix of only converting certain selected parts is more
    ideal since at least this way one can get around the encoding error, etc.

    Any one else got any ideas?

    Juna Kuristag, Sep 9, 2003
  6. Juna Kuristag

    Hughy Guest

    It sounds like a problem related to your computer or its configuration,
    rather than the Procoder software. The same algorithm should be applied
    to all frames, so if the first ones are quick, then each following frame
    should take a similar time to process. Viruses can drastically slow down
    machine responses too - have you run your virus checker lately?

    Another thing you might try is closing down unnecessary processes running
    in the background (including your virus software).

    If all else fails, the Canopus support forums often provide a quick
    response to problems - have you tried them? You'll have to log in, but
    that's not an issue.

    Hughy, Sep 10, 2003
  7. Juna Kuristag

    Mike Rehmus Guest

    Might ask Canopus directly. I recently received ProcoderLE as part of a
    software bundle. It would gradually slow down to about .1 fps. After an
    upgrade, the frame rate held steady at 15 fps. For that product, it was a
    known bug.
    Mike Rehmus, Sep 10, 2003
  8. Juna Kuristag

    Mark E Guest

    I think I know what you're talking about. That same thing was happening and
    I just upgraded and the problem went away. There are some bugs in the demo
    that they distribute, so I would recommend getting your hands on 1.5 if
    you're able to. At first I thought it was a memory / system problem, but I
    found no matter what I did it still went bezerk.

    Canopus have themselves an amazing product however, they need to be better
    about supporting it. At the $500 dollars I paid ($699 retail) you would
    expect better support on their webpage. I have signed up for their support
    forums but I find little help from them otherwise. Thank goodness its a
    pretty straight forward program to use otherwise I'd have something to say.

    The most annoying thing about the program now is I can't manage to turn off
    the "Done" SOUND that blasts in my ear each time a conversion is finished.
    (Anyone know how to turn this off?)
    Mark E, Sep 10, 2003
  9. Juna Kuristag

    Guy Guest

    It is amazing that a bug like that could ever get through software QA. Just
    a thought......
    Guy, Sep 10, 2003
  10. Juna Kuristag

    Paul W Guest

    I posted the same problem to the Conopus Forum the other week. No
    answers as to why this happens. I just hope that the expensive full
    paid version dosen't have this problem.

    "I decided to try the demo of Procoder after hearing great things
    about it's MPEG encoding.

    The end quality for SVCD and VCD from a DIVX or MJPEG source is out
    standing.I don't have a DVD writer at this strange so didn't test it
    However when I try to encode from a PAL DV source the encoder starts
    at 20 fps and after about 18 seconds the CPU usage drops to about 5%
    and the frame rate drops to about 2fps and keeps going down.

    The build of the demo is

    Is there some setting I'm missing here??

    Systems is Asus P4PE mobo, 512Meg Ram, P2.4G, Win2K svspack 3."
    Paul W, Sep 11, 2003
  11. Juna Kuristag

    Mark E Guest

    I guess you should pull what Juna did by sending this to a few different
    newsgroups. Although some might think thats spam (just kidding)
    Mark E, Sep 11, 2003
  12. Juna Kuristag

    Paul W Guest

    Problem solved.

    I found a file on the Canopus downloads called "DV Fileconverter" It
    converts in a lossless way MS DV files into Canopus DV files. Load
    these into procoder and it converts ok. Its says at 3fps and CPU at
    100% ( I suspect that the fps is lying it looks more like 10fps in the
    preview screen)
    Paul W, Sep 15, 2003
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.