<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
On 05/12/2011 9:38 AM, Donald McLachlan wrote:
<blockquote cite="mid:4EDCD778.8050107@crc.ca" type="cite">
<br>
On 05/12/2011 2:03 AM, Maarten Maathuis wrote:
<br>
<blockquote type="cite">On Sun, Dec 4, 2011 at 6:11 PM, Donald
McLachlan
<br>
<a class="moz-txt-link-rfc2396E" href="mailto:Donald.McLachlan@crc.ca"><Donald.McLachlan@crc.ca></a> wrote:
<br>
<blockquote type="cite">Hi,
<br>
<br>
I don't know where to start to resolve this problem and
guessed maybe this
<br>
is a good place to start. If not, please point me in the right
direction.
<br>
<br>
Our ultimate goal is to stream 8k resolution video using sage
(see
<br>
<a class="moz-txt-link-abbreviated" href="http://www.sagecommons.org">www.sagecommons.org</a>).
<br>
<br>
- We first used ffmpeg to convert a 4k resolution video file
to yuv format,
<br>
and we were able to view it with ffplay, mplayer, and crcview
(an in house
<br>
program).
<br>
- We then used ffmpeg to convert/resample the same 4k
resolution video file
<br>
to yuv/8k resolution; the conversion completed without error.
<br>
- When trying to view the resulting yuv/8k resolution file all
three viewer
<br>
programs failed with the same X Error. For example, here is
the output from
<br>
ffplay:
<br>
<br>
ffplay -i Lupe.8k.yuv -s 8192x4320 -pix_fmt yuv420p -x 1920 -y
1080
<br>
ffplay version 0.8, Copyright (c) 2003-2011 the FFmpeg
developers
<br>
built on Nov 30 2011 13:01:22 with gcc 4.5.1 20101208
[gcc-4_5-branch
<br>
revision 167585]
<br>
configuration:
<br>
libavutil 51. 9. 1 / 51. 9. 1
<br>
libavcodec 53. 7. 0 / 53. 7. 0
<br>
libavformat 53. 4. 0 / 53. 4. 0
<br>
libavdevice 53. 1. 1 / 53. 1. 1
<br>
libavfilter 2. 23. 0 / 2. 23. 0
<br>
libswscale 2. 0. 0 / 2. 0. 0
<br>
[rawvideo @ 0x129d740] Estimating duration from bitrate, this
may be
<br>
inaccurate
<br>
Input #0, rawvideo, from 'Lupe.8k.yuv':
<br>
Duration: N/A, start: 0.000000, bitrate: N/A
<br>
Stream #0.0: Video: rawvideo, yuv420p, 8192x4320, 25 tbr,
25 tbn, 25 tbc
<br>
X Error of failed request: BadLength (poly request too large
or internal
<br>
Xlib length error)
<br>
Major opcode of failed request: 132 (XVideo)
<br>
Minor opcode of failed request: 18 ()
<br>
Serial number of failed request: 23
<br>
Current serial number in output stream: 24
<br>
<br>
In case it matters, we are using openSuse 11.4 64 bit linux,
on an ASUS P6T7
<br>
WS Supercomputer motherboard, with 12 G RAM, and a ASUS GTX590
video card.
<br>
<br>
My guess is the 8k resolution video format is exceeding a
buffer size limit
<br>
somewhere, either in software, or maybe on the video card.
<br>
Is there a way to find out what buffers are affected and is
there a way to
<br>
overcome these limits?
<br>
<br>
Thanks for any assistance you can provide,
<br>
Don
<br>
<br>
<br>
_______________________________________________
<br>
<a class="moz-txt-link-abbreviated" href="mailto:xorg@lists.freedesktop.org:">xorg@lists.freedesktop.org:</a> X.Org support
<br>
Archives: <a class="moz-txt-link-freetext" href="http://lists.freedesktop.org/archives/xorg">http://lists.freedesktop.org/archives/xorg</a>
<br>
Info: <a class="moz-txt-link-freetext" href="http://lists.freedesktop.org/mailman/listinfo/xorg">http://lists.freedesktop.org/mailman/listinfo/xorg</a>
<br>
Your subscription address:
<br>
</blockquote>
If this is using the nouveau driver (check lsmod or xorg log), i
see
<br>
that for some reason that it's limited to 4096x4096 for xvideo.
<br>
<br>
See this line:
<a class="moz-txt-link-freetext" href="http://cgit.freedesktop.org/nouveau/xf86-video-nouveau/tree/src/nouveau_xv.c#n2031">http://cgit.freedesktop.org/nouveau/xf86-video-nouveau/tree/src/nouveau_xv.c#n2031</a><br>
<br>
And then check the contents of DummyEncodingTex and you'll find
it
<br>
refers to the maximum sizes.
<br>
<br>
The command xvinfo confirms this.
<br>
<br>
NV50 and higher (everything starting geforce 8) are able to do
<br>
8192x8192, it should just be a matter of making a NV50 specific
<br>
DummyEncodingTex structure.
<br>
</blockquote>
<br>
Hi Maaten,
<br>
<br>
I believe we replaced the nouveau driver with the nvidia driver,
but I will double check.
<br>
<br>
I will run the xvinfo command to see what it says limits are.
<br>
<br>
- If need be I guess we could revert to the nouveau driver and
modify the DummyEncodingTex structure.
<br>
- Does anyone know if there something similar we can do with the
nvidia driver to enable 8k? (I guess maybe Nvidia are the ones to
ask. :-) )
<br>
<br>
Thanks, and I'll let you know how it goes,
<br>
Don
<br>
</blockquote>
<br>
Hi Maarten, (sorry for the typo on your name last time.)<br>
<br>
lsmod shows:<br>
<blockquote>nvidia 11909611 44 <br>
</blockquote>
and Xorg.0.log shows:<br>
<blockquote>/usr/lib64/xorg/modules/drivers/nvidia_drv.so<br>
[ 180.902] (II) Module nvidia: vendor="NVIDIA Corporation" [
180.902] compiled for 4.0.2, module version = 1.0.0<br>
[ 180.902] Module class: X.Org Video Driver<br>
[ 180.902] (II) NVIDIA dlloader X Driver 285.05.09 Fri Sep 23
17:33:35 PDT 2011<br>
[ 180.902] (II) NVIDIA Unified Driver for all Supported NVIDIA
GPUs<br>
</blockquote>
So I take it we are running the nvidia driver, not the nouveau
driver.<br>
<br>
Also, xvinfo shows<br>
<blockquote>maximum XvImage size: 16384 x 16384<br>
</blockquote>
Does that cover video, or just static images?<br>
<br>
In case it helps, I've attached a file with the text output of the 3
commands.<br>
<br>
Thanks,<br>
Don<br>
<br>
</body>
</html>