On Feb 11, 2008 11:03 PM, Reinhard Nissl <[EMAIL PROTECTED]> wrote:
> I've posted the URL to the spec some weeks ago already. In that
> issue, have a look into Annex E.2.1, Table E-1, Page 313.
>
Sorry. I'll see what I can dig out to set that up properly. For now
hardcoding works well as most H26
On Feb 11, 2008 11:00 PM, Torgeir Veimo <[EMAIL PROTECTED]> wrote:
> Which CPU are you using?
>
AMD BE-2350 overclocked to 2.6Ghz. Now running H264 channels like a
charm with CoreAVC.
Almost there
___
vdr mailing list
vdr@linuxtv.org
http://www.li
Hi,
Morfsta schrieb:
>> Well, the spec tells you that aspect_ratio_idc 11 means a sample
>> (pixel) aspect ratio 15:11 (1.3636). And you have 1440 x 1080
>> pixels so the frame aspect ratio yields:
>>
>>far = 1.3636 * 1440 / 1080 = 1.8181
>
> Could you give me a link to where you found t
On 12 Feb 2008, at 08:27, Morfsta wrote:
> now seems to decode all the h264 channels I have access to pretty
> well with ~40% idle.
Which CPU are you using?
--
Torgeir Veimo
[EMAIL PROTECTED]
___
vdr mailing list
vdr@linuxtv.org
http://www.lin
> Well, the spec tells you that aspect_ratio_idc 11 means a sample
> (pixel) aspect ratio 15:11 (1.3636). And you have 1440 x 1080
> pixels so the frame aspect ratio yields:
>
>far = 1.3636 * 1440 / 1080 = 1.8181
>
Could you give me a link to where you found that please?
Also, I just disc
Hi,
Morfsta schrieb:
> I used xinelibout for my H264 parser but Petri Hintukainen skips
> parsing of the VUI! I am looking in your h264parser.c in VDR and you
> also seem to comment this stuff out!
Well, I have no use for this kind of information, but I have to
read over it as there is no other
On Feb 11, 2008 9:09 PM, Reinhard Nissl <[EMAIL PROTECTED]> wrote:
> In case the decoder doesn't provide the image aspect ratio (and
> it looks like that as you had to provide the image size too),
> you'll have to extract it from the H.264 data yourself (as you
> did already for the image size).
>
Hi,
Morfsta schrieb:
> The coreavc patch for xine has this code in it: -
>
> +if(!img) {
> +img = this->stream->video_out->get_frame (this->stream->video_out,
> + this->bih->biWidth,
> + this->bih->biHeight,
> + this->ratio,
> +
On Feb 11, 2008 8:09 PM, Reinhard Nissl <[EMAIL PROTECTED]> wrote:
> Anyway, does the decoder tell you the aspect ratio anywhere?
>
> The aspect ratio must be passed to get_frame(). When the frame
> has the correct aspect ratio set, xine-lib will take care to
> setup the video scaler to stretch fo
Hi,
Morfsta schrieb:
>> Just a guess: maybe the above bih.biXPelsPerMeter and
>> bih.biYPelsPerMeter can be used to set the pixel aspect ratio
>> which will then in turn yield the frame aspect ratio when applied
>> to the coded frame size. So pixel aspect for the above sample
>> should yield:
>>
On Feb 11, 2008 6:31 PM, Reinhard Nissl <[EMAIL PROTECTED]> wrote:
> Just a guess: maybe the above bih.biXPelsPerMeter and
> bih.biYPelsPerMeter can be used to set the pixel aspect ratio
> which will then in turn yield the frame aspect ratio when applied
> to the coded frame size. So pixel aspect
Hi,
Morfsta schrieb:
> I have managed to get xine to now detect the H264 video size prior to
> starting up the CoreAVC decoder and set the size within the
> initialisation function: -
>
> memset(&bih, 0x00, sizeof(bih));
> bih.biWidth = sps.width;
> bih.biHeight = sps.height;
>
OK, I spent a bit of time looking at this today as there doesn't seem
to be much movement on FFMPEG and H264 at the moment.
I have managed to get xine to now detect the H264 video size prior to
starting up the CoreAVC decoder and set the size within the
initialisation function: -
memset(&bi
Hi,
Morfsta schrieb:
> I'm not sure about that. So, if the function identifies an AUD at the
> start of the payload then it could go on and scan the rest of the
> payload for an SPS? In other words we must scan after the AUD for
>
> Data[0] = 0x00
> Data[1] = 0x00
> Data[2] = 0x01
> Data[3] & 0x
On Jan 24, 2008 9:54 PM, Reinhard Nissl <[EMAIL PROTECTED]> wrote:
> Typically, a SPS is found in the same memory block which starts
> with an AUD for an "I frame". From VDR's remux.c,
> cRemux::ScanVideoPacket():
>
> if (!p[-2] && !p[-1]) { // found 0x01
> if (h264
Hi,
Morfsta schrieb:
> It seems that you must start scanning the mpeg stream for a Sequence
> Parameter Set with a NAL Access Code of 7. At first glance this
> doesn't appear too bad, as the code is already in
> src/demuxers/demux_mpeg_pes.c to scan for a NAL code of 9 (Access Unit
> Delimiter),
Yes, I started looking at that. I also downloaded some H264 reference
utilities that someone at Dolby put together.
It seems that you must start scanning the mpeg stream for a Sequence
Parameter Set with a NAL Access Code of 7. At first glance this
doesn't appear too bad, as the code is already i
Hi,
Morfsta schrieb:
> OK, I have added the following code into src/demuxers/demux_mpeg_pes.c
>
> static int32_t GetVideoSize(const uint8_t *buf, int length, int
> *width, int *height)
> {
> int i = 0; // the minimum length of the video packet header
> //i += buf[i] + 1; // possibl
OK, I have added the following code into src/demuxers/demux_mpeg_pes.c
static int32_t GetVideoSize(const uint8_t *buf, int length, int
*width, int *height)
{
int i = 0; // the minimum length of the video packet header
//i += buf[i] + 1; // possible additional header bytes
for (; i
hmmm, I've been looking into the demux_mpeg_pes function in xine,
isn't the height and width stored in the transport stream within the
pes? I tried to adapt the code that shows the resolution in femon to
work on the stream in demux_mpeg_pes but not had much success so far..
:-(
Do you have to pars
Problem in incorrect patch.. The size of a picture 1920?1080 is sewn rigidly
up, and for BBS HD it is necessary 1440?1080
> Hey, it works ... Sort of. Anyone else having the "green bar" problem?
> I get a large green bar across the bottom of the screen and four fuzzy
> representations of the pict
Hey, it works ... Sort of. Anyone else having the "green bar" problem?
I get a large green bar across the bottom of the screen and four fuzzy
representations of the picture above it on: -
BBC HD
DigitalAlb HD-1
DigitalAlb HD-2
SVT HD
However, Channel 4 HD and a number of other HD channels work fi
Darren Salt skrev:
> I demand that Morfsta may or may not have top-posted AGAIN...
>
>> On Jan 21, 2008 4:06 PM, Darren Salt <[EMAIL PROTECTED]>
>> wrote:
>>> I demand that Morfsta may or may not have written...
Seems that there is a difference in versions somewhere. BUF_VIDEO_WVC1
is de
I demand that Morfsta may or may not have top-posted AGAIN...
> On Jan 21, 2008 4:06 PM, Darren Salt <[EMAIL PROTECTED]>
> wrote:
>> I demand that Morfsta may or may not have written...
>>> Seems that there is a difference in versions somewhere. BUF_VIDEO_WVC1
>>> is defined in xine-engine.h.
>> I
That got it!
I've got it working now in the 32-bit chroot environment, I can see it
loading the CoreAVC codec when switching to BBC HD.
Sadly, I'm doing this remotely so can't see how the results actually
look on the TV until tomorrow! I'm keen on seeing a channel that uses
spatial direct mode.
Hi,
Igor schrieb:
> is there any difference between xine-lib 1.2 branch and 1.1 branch for our
> case ?
The 1.2 branch contains my VDR plugins while the 1.1 branch needs
a patch, which vdr-xine-0.8.1 provides. Don't think that this is
relevant for our goals.
The patch for the 1.1 branch is mai
On Jan 21, 2008 7:01 AM, Morfsta <[EMAIL PROTECTED]> wrote:
> However, I get this error message: -
>
> w32codec.c:581: error: 'BUF_VIDEO_WVC1' undeclared (first use in this
> function)
Try:
--- xine-lib/src/xine-engine/buffer.h.orig 2007-11-05 18:33:03.0
-0500
+++ xine-lib/src/xine
It was in the tar file that Per posted earlier of his xine-lib!
On Jan 21, 2008 4:06 PM, Darren Salt <[EMAIL PROTECTED]> wrote:
> I demand that Morfsta may or may not have written...
>
> > Seems that there is a difference in versions somewhere. BUF_VIDEO_WVC1
> > is defined in xine-engine.h.
>
> I
I demand that Morfsta may or may not have written...
> Seems that there is a difference in versions somewhere. BUF_VIDEO_WVC1
> is defined in xine-engine.h.
I don't know where your xine-engine.h came from, but it's not xine-lib.
[snip; don't top-post]
--
| Darren Salt| linux or ds at
Seems that there is a difference in versions somewhere. BUF_VIDEO_WVC1
is defined in xine-engine.h. I added it to an include and its
compiling-ish I'm actually cross compiling 32bit in my 64 bit
environment which is fun with having to provide so many 32-bit libs.
Still I don't fancy trashing my
I demand that Morfsta may or may not have written...
[snip]
> However, I get this error message: -
> w32codec.c:581: error: 'BUF_VIDEO_WVC1' undeclared (first use in this
> function)
> I can't find anywhere in the code where this is declared but the
> coreavc patch adds it..
> Any ideas?
Inco
I demand that Gregoire Favre may or may not have written...
> On Sun, Jan 20, 2008 at 10:20:40PM +0300, Igor wrote:
>> please, try with this Makefile version from Walery
>> http://allrussian.info/thread.php?postid=1226030#post1226030
> Thank.
> I'll be lazy and wait for a current patch against x
OK, you are right. I am building it in a 32bit chroot environment and
now it tried to build in lib32dll!
However, I get this error message: -
w32codec.c:581: error: 'BUF_VIDEO_WVC1' undeclared (first use in this function)
I can't find anywhere in the code where this is declared but the
coreavc p
I demand that Morfsta may or may not have written...
> I have been using xine-1.2 from the Mercurial distribution, but it
> still creates a plugin directory called 1.1.9 and sometimes 1.1.90.
Wrong. 1.1.90 only. Any 1.1.9 which you see is from xine-lib 1.1.9.
[snip]
> Running on Ubuntu 7.10 x86_
o:
vdr@linuxtv.org> Date: Mon, 21 Jan 2008 14:40:01 +0300> Subject: Re: [vdr] VDR
- xine - CoreAVC> > linux 64bit? Most likely in it a problem.> > > Also, if I
do a make clean && make in that directory it doesn't do > > anything: -> >> > #
On Sun, Jan 20, 2008 at 10:20:40PM +0300, Igor wrote:
> please, try with this Makefile version from Walery
> http://allrussian.info/thread.php?postid=1226030#post1226030
Thank.
I'll be lazy and wait for a current patch against xine-lib-1.2 :-)
All the channels I have access to seems to works wi
linux 64bit? Most likely in it a problem.
> Also, if I do a make clean && make in that directory it doesn't do
> anything: -
>
> # make
> make[1]: Entering directory `/root/dshow/xine-lib-1.2/src/libw32dll'
> make[1]: Nothing to be done for `all-am'.
> make[1]: Leaving directory `/root/dshow/xine
Same problem. I'm not sure that the w32 codec support is being built
in xine. If I look in src/libw32dll I see: -
:~/dshow/xine-lib-1.2/src/libw32dll# ls
common.cMakefile Makefile.in qtx wine
DirectShow Makefile.am nal_parser.c w32codec.c
dmo Makefile.am
> See attached xine.log
>
>load_plugins: plugin mpeg2 will be used for video streamtype 00.
try delete /usr/local/lib libxine* and /usr/local/lib/xine dir and make
install xine again
Walery
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.o
See attached xine.log
On Jan 21, 2008 7:30 AM, Walery Daniloff <[EMAIL PROTECTED]> wrote:
> Hi,
>
> > Tried vdr-xine - this shows a black screen with audio but no video -
> > message says it can't find a plugin to handle the video.
>
> show verbose-log - xine --verbose=2
>
>
> ___
Morfsta skrev:
> I have been using xine-1.2 from the Mercurial distribution, but it
> still creates a plugin directory called 1.1.9 and sometimes 1.1.90.
>
Evereything except that you use Mercurial looks like my setup. I started of
with
the xine-lib I had on my machine, which was originally tak
Hi,
> Tried vdr-xine - this shows a black screen with audio but no video -
> message says it can't find a plugin to handle the video.
show verbose-log - xine --verbose=2
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listi
I have been using xine-1.2 from the Mercurial distribution, but it
still creates a plugin directory called 1.1.9 and sometimes 1.1.90.
I just can't get it to work!
Here's the steps I have taken: -
Running on Ubuntu 7.10 x86_64.
Downloaded xine-lib-1.2 from hg
Patched with xine.patch from google
> I'll try 1.2,
may be it's the best case :)
@Reinhard
is there any difference between xine-lib 1.2 branch and 1.1 branch for our case
?
Igor
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Gregoire Favre skrev:
> On Sun, Jan 20, 2008 at 06:38:31PM +0100, Per Mellander wrote:
>
>> Don't know if it works for x86_64.
>>
>> I checked out xine-lib one minute ago to test and I had no problem.
>
> Well, that's very strange, I checked revision 32 of the svn, and the svn
> (you spoke about
On Sun, Jan 20, 2008 at 06:38:31PM +0100, Per Mellander wrote:
> Don't know if it works for x86_64.
>
> I checked out xine-lib one minute ago to test and I had no problem.
Well, that's very strange, I checked revision 32 of the svn, and the svn
(you spoke about a CVS of xine-lib which is abandon
> I wanted to try it, but if fails at patching :
>
> patching file src/libw32dll/Makefile.am
> Hunk #1 FAILED at 13.
> Hunk #2 FAILED at 33.
> 2 out of 2 hunks FAILED -- saving rejects to file
> src/libw32dll/Makefile.am.rej
please, try with this Makefile version from Walery
http://allrussian.inf
Gregoire Favre skrev:
> Hello,
>
> one more "stupid" question : does it works also for x86_64 ?
>
> I wanted to try it, but if fails at patching :
>
> patching file src/libw32dll/Makefile.am
> Hunk #1 FAILED at 13.
> Hunk #2 FAILED at 33.
> 2 out of 2 hunks FAILED -- saving rejects to file
> src
Hello,
one more "stupid" question : does it works also for x86_64 ?
I wanted to try it, but if fails at patching :
patching file src/libw32dll/Makefile.am
Hunk #1 FAILED at 13.
Hunk #2 FAILED at 33.
2 out of 2 hunks FAILED -- saving rejects to file
src/libw32dll/Makefile.am.rej
that with coreav
Walery Daniloff skrev:
> Hi,
>> I'm sorry but the latest mail is not about how to get xineliboutput to
>> work but xine. Walery has a patch for xineliboutput and I've tried it
>> but I haven't been able to get it to work without segfault.
>>
>> http://allrussian.info/thread.php?threadid=89361&threa
Hi,
> I'm sorry but the latest mail is not about how to get xineliboutput to
> work but xine. Walery has a patch for xineliboutput and I've tried it
> but I haven't been able to get it to work without segfault.
>
> http://allrussian.info/thread.php?threadid=89361&threadview=0&hilight=&hilightuser=0
I'm sorry but the latest mail is not about how to get xineliboutput to
work but xine. Walery has a patch for xineliboutput and I've tried it
but I haven't been able to get it to work without segfault.
http://allrussian.info/thread.php?threadid=89361&threadview=0&hilight=&hilightuser=0&page=3
52 matches
Mail list logo
