search for: page0

..._skyboxbk (1) != 0 Reference Count for Material skybox/mm_skyboxlf (1) != 0 Reference Count for Material skybox/mm_skyboxft (1) != 0 Reference Count for Material skybox/mm_skyboxup (1) != 0 Reference Count for Material skybox/mm_skyboxdn (1) != 0 Reference Count for Material fonts/tahoma_10_000_000-page0 (1) != 0 Reference Count for Material fonts/vamp_mainfont_55_1000_000-page1 (1) != 0 Reference Count for Material fonts/vamp_mainfont_55_1000_000-page2 (1) != 0 Reference Count for Material fonts/vamp_mainfont_55_1000_000-page0 (1) != 0 Reference Count for Material fonts/vamp_mainfont_20_1000_000-p...

...w/vga.c Mon Jul 17 22:35:54 2006 +0800 @@ -1392,7 +1392,8 @@ static void vga_draw_graphic(VGAState *s static void vga_draw_graphic(VGAState *s, int full_update) { int y1, y, update, page_min, page_max, linesize, y_start, double_scan, mask; - int width, height, shift_control, line_offset, page0, page1, bwidth; + int width, height, shift_control, line_offset, bwidth; + ram_addr_t page0, page1; int disp_width, multi_scan, multi_run; uint8_t *d; uint32_t v, addr1, addr; _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com...

Salut alex, j''ai un petit souci. quand j''utilise "demotaskbaricon" avec traducteur-wxruby, que j''ouvre mon application(donc l''icone apparaît dans la barre de lancement rapide) et que je ferme mon application, l''icone disparaît tout de suite. Mais quand je l''utilise avec l''exemple Wizard et que je ferme mon application

...ows, and you want FourCC data, sure you'll have to run it through a table. But that's better than forcing FourCC on GNU/Linux, making us look up arbitrary 32-bit sequences to see what parameters they call for. I know you're frustrated by Ogg's lack of a FourCC field standard in Page0, but we do have a standard developing, and given the power of even embedded CPUs, ours makes much more sense. Think of all of Page0 as your "fourcc", supporting with a single codec a hundred different FourCC codecs, no more squeezing codec versions into the 4 letter space and still...

On Tue, Nov 08, 2005 at 04:59:33PM -0800, Arc wrote: > This is also interesting work in that, once we're done, we'll have a standard to > use for a compressed lossless format.. a FLAC for video, for editing or archival > purposes, similar to HuffYUV. Well, we're talking about an uncompressed format. OggMNG is already "FLAC for video". However, it doesn't do

...buffer. + */ +static inline void btrfs_release_extent_buffer(struct extent_buffer *eb) +{ + btrfs_release_extent_buffer_page(eb, 0); + __free_extent_buffer(eb); +} + struct extent_buffer *alloc_extent_buffer(struct extent_io_tree *tree, u64 start, unsigned long len, struct page *page0, @@ -3174,10 +3207,7 @@ struct extent_buffer *alloc_extent_buffer(struct extent_io_tree *tree, free_eb: if (!atomic_dec_and_test(&eb->refs)) return exists; - for (index = 1; index < i; index++) - page_cache_release(extent_buffer_page(eb, index)); - page_cache_release(extent_buff...

...odec it came from (and thus, we could say that "AXYZ" usually uses 4:4:4), just as knowing that something is of the "WAVE" fourcc, also known as a .wav file, doesn't tell us what samplerate, bits per sample, or number of channels is used. In Ogg, we tell compatability by page0/packet0. The entire first packet, including all it's configuration variables, versions, etc is used to detirmine compatability. The fields we're talking about will go into packet0, so that a list of which plugins can accept it can be easily generated. > Agreed.. Though it's wo...

On Wed, Nov 09, 2005 at 05:33:37AM -0800, Arc wrote: > > Data pages are identified to be part of a logical bitstream through their > > serial number, so don't need any additional identifiers. Thus, Arc, I don't > > quite understand why you would require another 32 bits at the beginning of > > each data packet, when ogg pages are already covering that

...s nessesary as we want to use the first packet's granulepos, not the last, when multiple packets are in a single page. This is only usable before Packet#1 is processed, so a codec needs to be able to be detirmined to be cont/discont based only on the information aquired from Page0/Packet0. An error is generated if this change is requested later in the stream. The debate is not over wether this is a good way of doing it, but rather, wether treating different codecs/streams differently is a good idea. Before you argue this you had better read Monty's fu...

...s nessesary as we want to use the first packet's granulepos, not the last, when multiple packets are in a single page. This is only usable before Packet#1 is processed, so a codec needs to be able to be detirmined to be cont/discont based only on the information aquired from Page0/Packet0. An error is generated if this change is requested later in the stream. The debate is not over wether this is a good way of doing it, but rather, wether treating different codecs/streams differently is a good idea. Before you argue this you had better read Monty's fu...

...s nessesary as we want to use the first packet's granulepos, not the last, when multiple packets are in a single page. This is only usable before Packet#1 is processed, so a codec needs to be able to be detirmined to be cont/discont based only on the information aquired from Page0/Packet0. An error is generated if this change is requested later in the stream. The debate is not over wether this is a good way of doing it, but rather, wether treating different codecs/streams differently is a good idea. Before you argue this you had better read Monty's fu...

...s nessesary as we want to use the first packet's granulepos, not the last, when multiple packets are in a single page. This is only usable before Packet#1 is processed, so a codec needs to be able to be detirmined to be cont/discont based only on the information aquired from Page0/Packet0. An error is generated if this change is requested later in the stream. The debate is not over wether this is a good way of doing it, but rather, wether treating different codecs/streams differently is a good idea. Before you argue this you had better read Monty's fu...

...s nessesary as we want to use the first packet's granulepos, not the last, when multiple packets are in a single page. This is only usable before Packet#1 is processed, so a codec needs to be able to be detirmined to be cont/discont based only on the information aquired from Page0/Packet0. An error is generated if this change is requested later in the stream. The debate is not over wether this is a good way of doing it, but rather, wether treating different codecs/streams differently is a good idea. Before you argue this you had better read Monty's fu...

Timothy B. Terriberry wrote: >Chapter 4 of the Theora specification does a reasonable job of laying >out all of the possible parameters for a Y'CbCr-style color space, which >includes as a subset those needed for RGB. Much more detailed >information is available from Charles Poynton's Color and Gamma FAQs: >http://www.poynton.com/Poynton-color.html >If you wish to do any

...ng similar for an identifier, to allow future codecs to begin with PCM* or YUV*, that makes some sense, but I currently feel that the three letters are sufficient and allow 3rd party codecs to use a prefix if PCM/YUV/RGB is in their name. It's become a pseduo-standard that the first byte of page0 be a header ID byte, and the variable length codec identification magic follows. In the OggStream code that I'm working on, 8 bytes are used to identify a codec from the plugin to the application, with the first 7 of those useable such that the null-padding will null-terminate the string....

...ng similar for an identifier, to allow future codecs to begin with PCM* or YUV*, that makes some sense, but I currently feel that the three letters are sufficient and allow 3rd party codecs to use a prefix if PCM/YUV/RGB is in their name. It's become a pseduo-standard that the first byte of page0 be a header ID byte, and the variable length codec identification magic follows. In the OggStream code that I'm working on, 8 bytes are used to identify a codec from the plugin to the application, with the first 7 of those useable such that the null-padding will null-terminate the string....

On Tue, Nov 08, 2005 at 06:08:25PM +0800, illiminable wrote: > Why not just make it OggRawFOURCC, do we really need one stream format for > rgb, and one for yuv ? [snip] > I just meant oggRaw, not fourcc. Oh, thank god you corrected this. :-) I was contemplating an "OggVid" format, and here is why I'm steering against it (though, yes, this has been a topic of

On Tue, Nov 08, 2005 at 06:08:25PM +0800, illiminable wrote: > Why not just make it OggRawFOURCC, do we really need one stream format for > rgb, and one for yuv ? [snip] > I just meant oggRaw, not fourcc. Oh, thank god you corrected this. :-) I was contemplating an "OggVid" format, and here is why I'm steering against it (though, yes, this has been a topic of

I've been implementing Ogg FLAC support in an editor I'm working on, and I must admit to being frustrated by the lack of support for the codec on the Ogg layer... and this is more than lacking granulepos. The codec's I've worked with, and my own (Writ), use Page 0 for general information about the codec. Specifically, the samplerate, bitrate, quality, number of channels, all

...page_min = 0; page_max = 0; - d = s->ds->data; - linesize = s->ds->linesize; + d = ds_get_data(s->ds); + linesize = ds_get_linesize(s->ds); y1 = 0; for(y = 0; y < height; y++) { addr = addr1; @@ -1789,7 +1802,7 @@ page_min = page0; if (page_max == 0 || page1 > page_max) page_max = page1; - if (!s->ds->shared_buf) { + if (!is_buffer_shared(s->ds->surface)) { vga_draw_line(s, d, s->vram_ptr + addr, width); if (s->cursor_d...