Mike Harris wrote:
Joseph A. Caputo wrote:
On Wednesday 29 June 2005 7:58, Mike Harris wrote:
It is a P4 2.8Ghz. It barely breaks out a sweat, the CPU fan does
not come on.
Also, sureley transcoding should just take longer rather than
dropping frames if CPU speed were an issue? It is not as
Hi JAC,
I did not specify libmpeg2 on the configure command line, so I guess I
am not using it. Here is the ./configure output:
Warning: DVB location points into kernel (ok if kernel >= 2.6.11)
# Basic Settings
Compile type release
Compiler cache no
DistCC no
Install prefix /
On Wednesday 29 June 2005 7:58, Mike Harris wrote:
> Hi Devan,
>
> It is a P4 2.8Ghz. It barely breaks out a sweat, the CPU fan does not
> come on.
> Also, sureley transcoding should just take longer rather than dropping
> frames if CPU speed were an issue? It is not as if it has to keep up
> w
Hi Devan,
It is a P4 2.8Ghz. It barely breaks out a sweat, the CPU fan does not
come on.
Also, sureley transcoding should just take longer rather than dropping
frames if CPU speed were an issue? It is not as if it has to keep up
with broadcast.
And what's more, I did not have this problem wi
MPEG4 does take more CPU time so that could be a factor, whats your system?On 6/25/05, Mike Harris <[EMAIL PROTECTED]
> wrote:Hi,I recently upgraded to Myth 0.18. After doing so, transcoding video from
MPEG2 -> MPEG4 results in jerky video - it looks as though some framesare being dropped.I record
On Sun, 2005-06-26 at 11:06 +1000, Mike Harris wrote:
> I recently upgraded to Myth 0.18. After doing so, transcoding video from
> MPEG2 -> MPEG4 results in jerky video - it looks as though some frames
> are being dropped.
You know, I notice this a little bit, too. I suspect in part it's due to
Hi,
I recently upgraded to Myth 0.18. After doing so, transcoding video from
MPEG2 -> MPEG4 results in jerky video - it looks as though some frames
are being dropped.
I record from DVB so programs are stored in MPEG2 initially. I have
tried various combinations of the motion compensation opt
