Pierre Ossman wrote:
> Still broken I'm afraid. And I've confirmed it's the new huffman
> encoder as if I back out just that change, it starts working again.
>
> This is the kind of output I get from the client:
>
> Corrupt JPEG data: premature end of data segment
> Invalid JPEG file structure: two SOI markers
>   
I've done some further testing with this and cannot reproduce it at the
codec level, which means it must only occur at the application level. 
Unfortunately, I can't test it at the application level until someone
fixes the build so that I can once again build vncviewer with SIMD
support.  I am also waiting on that in order to be able to do some
holistic performance analysis of where we stand vs. TurboVNC 0.5, which
is crucial for planning the next phase of development.

At the codec level, I've run a variety of images through both codecs
(unmodified libjpeg and libjpeg/SIMD with my accelerated Huffman codec)
using both disk-based and memory-based destination managers, and the
results are bit-for-bit identical between the two codecs.


------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel

Reply via email to