Displaying 3 results from an estimated 3 matches for "7x16".
Did you mean:
0x16
2017 May 18
4
Strange behavior with OGG packets?
...ead packet is never found, but in
it's place we have a packet at b_o_s=256 (which is where OpusHead usually
lives), but the byte size is reported to be 0 and e_o_s=0 as well. (This is
generated by parsing the packets via ogg's *ogg_stream_packetout* function.
It appears a matrix larger than 7x16 causes this issue. (The matrix values
are all signed short vals, so >224 bytes seems to fail.
I'm not very familiar with ogg internals so any advice would be greatly
appreciated! Thanks so much! :)
Cheers,
Drew
-------------- next part --------------
An HTML attachment was scrubbed...
URL:...
2017 May 18
0
Strange behavior with OGG packets?
...found,
> but in it's place we have a packet at b_o_s=256 (which is where OpusHead
> usually lives), but the byte size is reported to be 0 and e_o_s=0 as well.
> (This is generated by parsing the packets via ogg's *ogg_stream_packetout* function.
> It appears a matrix larger than 7x16 causes this issue. (The matrix values
> are all signed short vals, so >224 bytes seems to fail.
>
> I'm not very familiar with ogg internals so any advice would be greatly
> appreciated! Thanks so much! :)
>
> Cheers,
> Drew
>
-------------- next part --------------
A...
2017 May 18
0
Strange behavior with OGG packets?
...found, but in it's place we have a packet at b_o_s=256 (which is where
> OpusHead usually lives), but the byte size is reported to be 0 and
> e_o_s=0 as well. (This is generated by parsing the packets via
> ogg's *ogg_stream_packetout* function. It appears a matrix larger than
> 7x16 causes this issue. (The matrix values are all signed short vals, so
>>224 bytes seems to fail.
>
> I'm not very familiar with ogg internals so any advice would be greatly
> appreciated! Thanks so much! :)
>
> Cheers,
> Drew
>
>
> ____________________________...