Andrew Jeffery wrote:
> Righto, installed freevo (1.x branch) and mplayer from
svn and the
> recordings that showed massive lengths previously are
either correct or
> display as None in length... The encoding server still
bails when trying
> to encode a recording of 'None' length:
>
> |
> | 2008-04-09 11:11:19,924 DEBUG encodingcore.py
(286):
> |
source="/var/tv/recordings/03-06_21:30_Kitchen_Nightmar
es_USA.avi"
> | 2008-04-09 11:11:19,924 DEBUG encodingcore.py
(292): Video length
> is None
> | Failed to analyse
> |
"/var/tv/recordings/03-06_21:30_Kitchen_Nightmares_USA.
avi": unsupported
> | operand type(s) for /: 'NoneType' and 'int'
> | 2008-04-09 11:11:19,924 DEBUG encodingserver.py
(109): Analysis failed
>
> I also can't tell if mplayer's reporting the correct
time as the OSD
> seems to be broken (lol), though the commandline says:
>
> A:41250.0 V:41250.2 A-V: -0.240 ct: -0.124 36/ 36 7%
0% 0.6% 0 0
>
> Which if I'm reading it right says that the audio and
video are at
> ~41,250 seconds in? If that's the case it doesn't look
like it's been
> fixed :(
I don't know much about MPEG_TS streams as I don't receive
DVB or have
any DVB files.
First thing that I would try is to see what mminfo says
about the files,
this is what freevo uses. The next thing to try is to see
what mplayer
says about the file, there is a script in TOOLS/midentify
that prints
out the information. and is basically:
mplayer -vo null -ao null -frames 0 -identify "$ "
HTH
Duncan
>
> Andrew
>
> PS: fingers crossed I haven't left anything out this
time ;)
>
> Andrew Jeffery wrote:
> |
> |
> | A Mennucc wrote:
> | | it would help knowing which version of freevo and
mplayer/mencoder
> | | you are using
> |
> | Ah yes, sorry about that - actually thought of it
afterwards but hadn't
> | got around to emailing again  The other
thing I thought of after
> | sending it was that I probably shouldn't be rambling
about problems in
> | the 1.7.6.1 release ;)
> |
> | I ran some diffs against the 1.7.6.1 and svn head (of
the 1.x branch)
> | versions of the encoding(core|client).py and the
video.reencode plugin,
> | and it looks as if not much has changed apart from
adding the ability to
> | re-encode slices of video files. However I'm about to
tackle installing
> | from svn though to see if I can reproduce the
problems
> |
> | | note that I had some problems in the past that was
solved by
> | | updating freevo to 1.8.0 and mplayer to a latest
SVN
> | |
> |
> | I'll pull in the mplayer head revision as well and
give that a shot. The
> | version I'm using is Mplayer 1.0 rc2 p25993 (Gentoo's
current version -
> | I'm guessing p25993 is the revision number...)
------------------------------------------------------------
-------------
This SF.net email is sponsored by the 2008 JavaOne(SM)
Conference
Don't miss this year's exciting event. There's still time to
save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;1987
57673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Freevo-devel mailing list
Freevo-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-dev
el
|
