search for: vp5

...return 0; } +static int +firmware_present(struct pipe_screen *pscreen, enum pipe_video_profile profile) +{ + struct nouveau_screen *screen = nouveau_screen(pscreen); + int chipset = screen->device->chipset; + int vp3 = chipset < 0xa3 || chipset == 0xaa || chipset == 0xac; + int vp5 = chipset >= 0xd0; + int ret; + + /* For all chipsets, try to create a BSP objects. Assume that if firmware + * is present for it, firmware is also present for VP/PPP */ + if (!(screen->firmware_info.profiles_checked & 1)) { + struct nouveau_object *bsp = NULL; + int oc...

...r second - possible? Working? <p>Hello, I am using the latest binary download from vp32.com, just as a starter. We try using the VP32 codec in a video conferencing application, replacing Intel indeo for obvious reasons. I must note that I have considered contacting ON2 for a license of the VP5 codec, but after sending emails for amore than a week and never getting back calls after they were announced, and after not reaching anyone early in the office there (and I have a substantial time difference), I have decided that we will not license anything for the time being. Dan, you might take...

Nullsoft Streaming Video. Basically a video container format. Can be used for files or streaming. Though it can use any audio video formats internally currently it is just VP3/MP3 (or VP5/MP3, but that's internal only and not publicly available). Basically video for the next version of SHOUTcast. http://www.nullsoft.com/nsv/ From: "Geoff Shang" <gshang@uq.net.au> > BTW, what is NSV, anyone know? > > Geoff. --- >8 ---- List archives: http://www.xip...

http://news.com.com/2100-1023-938564.html <p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.

...class id's is a bit off. That doesn't strictly matter for BSP, but there's a mismatch in the logic between mesa and the kernel, which causes problems for NVD7 and NVD9 cards. In nouveau_vp3_video.c:firmware_present, if (chipset < 0xc0) oclass = 0x85b1; else if (vp5) oclass = 0x95b1; else oclass = 0x90b1; should become if (chipset < 0xc0) oclass = 0x85b1; else if (chipset < 0xe0) oclass = 0x90b1; else oclass = 0x95b1; Since the kernel expects the 90b1 class to be used on the NVD9 car...

...#39;t strictly matter for BSP, but there's a mismatch > in the logic between mesa and the kernel, which causes problems for NVD7 and > NVD9 cards. > > In nouveau_vp3_video.c:firmware_present, > > if (chipset < 0xc0) > oclass = 0x85b1; > else if (vp5) > oclass = 0x95b1; > else > oclass = 0x90b1; > > should become > > if (chipset < 0xc0) > oclass = 0x85b1; > else if (chipset < 0xe0) > oclass = 0x90b1; > else > oclass = 0x95b1; > &...

...p://nouveau.freedesktop.org/wiki/VideoAcceleration/ and our internal names. This is more of an FYI than anything else, to help translation; I don't expect it to help with this particular H264 hang. > > VP2 (same) > VP3 -> MSDEC > VP4.0 -> MSDEC2 > VP4.2 -> MSDEC3 > VP5 -> MSDEC4 > > Looking at your code, it seems that you're instantiating all 3 engines (VLD, PDEC, PPP) on the same channel. This probably isn't causing the hang, but it's bad practice in general, as it prevents the engines from running in parallel. It's also impossible t...

On Thu, Nov 21, 2013 at 5:22 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Thu, Nov 21, 2013 at 5:07 PM, Benjamin Morris <bmorris at nvidia.com> wrote: >> On 11/19/2013 08:16 PM, Ilia Mirkin wrote: >>> Hello, >>> >>> I hope this is an appropriate style of request for this forum. I added >>> code to support video decoding on the tesla

...he firmware? Do the information given at > > [1], [2] still apply or are they outdated? > > You definitely need firmware to do vdpau (just try removing it and > reboot, and see what happens) on all NV84+ cards. AFAIK there is no > active work being done to replace the firmware on VP5 cards (nvd0+), > although that is the one that is probably the most feasible since the > actual video decoding is done with firmware that's on the card (or > with dedicated hardware, who knows) so all that's left is providing > the little "os" running on the connected...

...map between the names on http://nouveau.freedesktop.org/wiki/VideoAcceleration/ and our internal names. This is more of an FYI than anything else, to help translation; I don't expect it to help with this particular H264 hang. VP2 (same) VP3 -> MSDEC VP4.0 -> MSDEC2 VP4.2 -> MSDEC3 VP5 -> MSDEC4 Looking at your code, it seems that you're instantiating all 3 engines (VLD, PDEC, PPP) on the same channel. This probably isn't causing the hang, but it's bad practice in general, as it prevents the engines from running in parallel. It's also impossible to use mul...

....pl?photo=33&SID=12&tag=SNnb323 although, as Freun said, it was "Not really all that informative,..." Is anyone aware of a site that has a downloadable video clip that was created for comparison purposes with different video codecs (MPEG 1, 2, 4, divx, Windows, Real, VP3, VP4, VP5, and so on)? Preferably, each of the video clips would be created from the same "reference" video file, that would be about one minute long, and would consist of a mix of high speed action and talking heads. The site should also have links to locations from which the video player...

Hello, I am using the latest binary download from vp32.com, just as a starter. We try using the VP32 codec in a video conferencing application, replacing Intel indeo for obvious reasons. I must note that I have considered contacting ON2 for a license of the VP5 codec, but after sending emails for amore than a week and never getting back calls after they were announced, and after not reaching anyone early in the office there (and I have a substantial time difference), I have decided that we will not license anything for the time being. Dan, you might take...

...lusion, do I still need the firmware? Do the information given at > [1], [2] still apply or are they outdated? You definitely need firmware to do vdpau (just try removing it and reboot, and see what happens) on all NV84+ cards. AFAIK there is no active work being done to replace the firmware on VP5 cards (nvd0+), although that is the one that is probably the most feasible since the actual video decoding is done with firmware that's on the card (or with dedicated hardware, who knows) so all that's left is providing the little "os" running on the connected falcon processors....

Hello, I run the Gentoo Linux distribution and use a self-compiled Linux 3.10.17 kernel. According to [1] http://nouveau.freedesktop.org/wiki/InstallDRM/ [2] http://nouveau.freedesktop.org/wiki/VideoAcceleration/ I need the original firmware from the binary driver in order to sucessully use DRM and to use VDPAU video acceleration. I used the python script from [2] and I had a look at the ebuild

One thing I have noticed when encoding VCDs is that often videos with complex backgrounds don't compress nearly as well as those with simple ones. Part of the problem is that TV cameras seam to have the focus so that the entire image is clear rather than focusing on the foreground (and blurring the backgrounds). The result is that a good number of bits are wasted trying to perfectly

Sorry for the crosspost but I think it's important. Tom Pepper of Nullsoft, posted this yesterday. "We've considered heavily which direction seems most appropriate for the second generation audio codec of SHOUTcast. Our primary goal in the decision process was to provide smaller consumption of bits while maintaining similar quality and compatibility with existing playback systems.

Sorry for the crosspost but I think it's important. Tom Pepper of Nullsoft, posted this yesterday. "We've considered heavily which direction seems most appropriate for the second generation audio codec of SHOUTcast. Our primary goal in the decision process was to provide smaller consumption of bits while maintaining similar quality and compatibility with existing playback systems.

Sorry for the crosspost but I think it's important. Tom Pepper of Nullsoft, posted this yesterday. "We've considered heavily which direction seems most appropriate for the second generation audio codec of SHOUTcast. Our primary goal in the decision process was to provide smaller consumption of bits while maintaining similar quality and compatibility with existing playback systems.

Hi List, Just batting a few ideas around here, but would it be possible to include in to the codec, estimation for common video artifacts that occur in the analogue world? For example, anything that's gone through a composite stage will likely have dot-crawl and false colour - if we can recognise this effect in the encoder, we can treat it as a special case. Other artifacts that come to

...but I couldn't figure out what was wrong. Getting h264 to work will be a larger effort, and will be able to build on this patchset. For now h264 and mpeg4 are not reported in the capabilities of pre-nvc0 cards. This patchset has received limited testing on VP3, pre-nvc0 VP4, post-nvc0 VP4, and VP5. It's worth noting that the mpeg1 decoding looks all weird and blocky, but it's the exact same issue as when using the blob. And the same bug exists on VP2 (although not with mesa/xvmc). They probably are missing some detail about difference of mpeg2 vs mpeg1 (oddification maybe? who knows....