Displaying 8 results from an estimated 8 matches for "frame_num".
2008 Feb 13
0
Determine number of 20ms frames in packet - without decoding
...encoding in WB/UWB mode every frame
consist of NB frame with one/two WB layers appended.
--
Regards,
Alexander Chemeris.
SIPez LLC.
SIP VoIP, IM and Presence Consulting
http://www.SIPez.com
tel: +1 (617) 273-4000
-------------- next part --------------
A non-text attachment was scrubbed...
Name: frame_num.c
Type: application/octet-stream
Size: 3819 bytes
Desc: not available
Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20080213/d6c2cc22/frame_num.obj
2008 Feb 12
2
Determine number of 20ms frames in packet - without decoding
Hi Alexander,
> Here is first attempt. I'm sending it here for review - am I understand
> you correctly? If general approach is correct, I'll change code to use
> modes from modes.c.
I haven't tested, but it looks sane. Just a few comments:
- printf("\tERROR not enough bits left after wb\n"); this is actually
now an error. It just means you got to the end of the
2013 Jun 30
0
[PATCH v2] nv50: H.264/MPEG2 decoding support via VP2, available on NV84-NV96, NVA0
...urces[VL_NUM_COMPONENTS];
+ struct pipe_sampler_view *sampler_view_planes[VL_NUM_COMPONENTS];
+ struct pipe_sampler_view *sampler_view_components[VL_NUM_COMPONENTS];
+ struct pipe_surface *surfaces[VL_NUM_COMPONENTS * 2];
+
+ struct nouveau_bo *interlaced, *full;
+ int mvidx;
+ unsigned frame_num, frame_num_max;
+};
+
+struct nv84_decoder {
+ struct pipe_video_decoder base;
+ struct nouveau_client *client;
+ struct nouveau_object *bsp_channel, *vp_channel, *bsp, *vp;
+ struct nouveau_pushbuf *bsp_pushbuf, *vp_pushbuf;
+ struct nouveau_bufctx *bsp_bufctx, *vp_bufctx;
+
+ struct n...
2013 Jun 27
4
[PATCH] nv50: H.264/MPEG2 decoding support via VP2, available on NV84-NV96, NVA0
...urces[VL_NUM_COMPONENTS];
+ struct pipe_sampler_view *sampler_view_planes[VL_NUM_COMPONENTS];
+ struct pipe_sampler_view *sampler_view_components[VL_NUM_COMPONENTS];
+ struct pipe_surface *surfaces[VL_NUM_COMPONENTS * 2];
+
+ struct nouveau_bo *interlaced, *full;
+ int mvidx;
+ unsigned frame_num, frame_num_max;
+};
+
+struct nv84_decoder {
+ struct pipe_video_decoder base;
+ struct nouveau_client *client;
+ struct nouveau_object *bsp_channel, *vp_channel, *bsp, *vp;
+ struct nouveau_pushbuf *bsp_pushbuf, *vp_pushbuf;
+ struct nouveau_bufctx *bsp_bufctx, *vp_bufctx;
+
+ struct n...
2013 Jun 29
0
[PATCH] nv50: H.264/MPEG2 decoding support via VP2, available on NV84-NV96, NVA0
...struct pipe_sampler_view *sampler_view_planes[VL_NUM_COMPONENTS];
> + struct pipe_sampler_view *sampler_view_components[VL_NUM_COMPONENTS];
> + struct pipe_surface *surfaces[VL_NUM_COMPONENTS * 2];
> +
> + struct nouveau_bo *interlaced, *full;
> + int mvidx;
> + unsigned frame_num, frame_num_max;
> +};
> +
Looking at the params associated with each video engine, I was wondering
about compacting it into a struct (names chosen are the first thing that
came to mind)
struct nv84_decoder_eng {
struct nouveau_object *obj;
struct nouveau_object *channel;
struct nou...
2013 Jun 29
2
[PATCH] nv50: H.264/MPEG2 decoding support via VP2, available on NV84-NV96, NVA0
...*sampler_view_planes[VL_NUM_COMPONENTS];
>> + struct pipe_sampler_view *sampler_view_components[VL_NUM_COMPONENTS];
>> + struct pipe_surface *surfaces[VL_NUM_COMPONENTS * 2];
>> +
>> + struct nouveau_bo *interlaced, *full;
>> + int mvidx;
>> + unsigned frame_num, frame_num_max;
>> +};
>> +
>
> Looking at the params associated with each video engine, I was wondering
> about compacting it into a struct (names chosen are the first thing that
> came to mind)
>
> struct nv84_decoder_eng {
> struct nouveau_object *obj;
>...
2013 Jun 30
0
[PATCH] nv50: H.264/MPEG2 decoding support via VP2, available on NV84-NV96, NVA0
..._NUM_COMPONENTS];
>>> + struct pipe_sampler_view *sampler_view_components[VL_NUM_COMPONENTS];
>>> + struct pipe_surface *surfaces[VL_NUM_COMPONENTS * 2];
>>> +
>>> + struct nouveau_bo *interlaced, *full;
>>> + int mvidx;
>>> + unsigned frame_num, frame_num_max;
>>> +};
>>> +
>>
>> Looking at the params associated with each video engine, I was wondering
>> about compacting it into a struct (names chosen are the first thing that
>> came to mind)
>>
>> struct nv84_decoder_eng {
>>...
2013 Aug 11
10
[PATCH 00/10] Add support for MPEG2 and VC-1 on VP3/VP4 for NV98-NVAF
As it turns out, with the proprietary firmware, the VP3 and VP4 interfaces are
identical. Furthermore, this is all already implemented for nvc0. So these
patches (a) move the easily sharable bits of the nvc0 implementation into the
nouveau directory, and then (b) implement the other parts in nv50. The
non-shared parts are still largely copies, but there are some differences, not
the least of which