[mythtv] Fwd: [mythtv-commits] mythtv branch master updated by jyavenard. v0.28-pre-1024-g9cba5e2

[Craig Treleaven]

At 9:39 AM +1100 3/28/14, Jean-Yves Avenard wrote:
>On 28 March 2014 03:42, Craig Treleaven <ctreleaven at cogeco.ca> wrote:
>
>>  Built a new version with the patch and tested videos (OK), music (fine but
>>  no album art displayed in Notification) and photos (slash zero displayed).
>>  However, I can't make any sense of the files the patch produced!  ...
>
>It makes perfect sense to me....
>
>All photos taken with the camera app are jpeg (like all cameras no?)
>
>
>>  The logs say that a png file was transferred.  The errors I saw were in
>>  libpng.  How can it be that these files are in jpeg format?  I can view
>>  these without issue in Finder's Quick Look and GraphicConverter (after
>>  adding the .jpeg extension, at least for the Finder).  And the Qt4-based
>>  QIviewer opens and displays them without error.
>
>the log showing the type of image is very crude and actually the
>detection jpeg/png is only use for the log...
>I can't acces  your log anymore (one of the reason I don't use
>pastebin.ca anymore... only keeps the data for a couple of days, plus
>they are slow usually)
>
>When it comes to image format detection and the like, it's all done by
>Qt, myth has no knowledge of things...
>
>What matters is that the file is properly received, whatever your Qt
>lib does after that
>
>So whatever is displayed in the log, is unimportant
>>
>>  BTW, airplayimage is just a more-heavily compressed version of
>>  airplayimagebin; they are the same picture.
>
>I explained that earlier...
>airplayimagebin is the image as received by AirPlay.
>
>From that we create a QImage which is a bitmap. Then we save the image
>into a jpeg: so the image is re-compressed.
>
>whatever default Qt uses for compression, I haven't been paying attention
>
>My guess is that your libpng warning you got earlier is likely not
>related to anything...
>
>Is your Qt built with jpeg decoding support? it's a default format
>normally... but I don't know how Qt is built

I started to reply to this but got looking at the Qt image plugins v. 
the libraries they depend on.  I *think* a fresh rebuild of Qt4 may 
fix my issue but, as you know, that ties up a machine for a long 
time.  I'll kick it off in a little bit and test in the morning.

BTW, MacPorts added a mechanism to scan for linking issues like this 
when they started doing binary software installs.  I think the rather 
singular layout of Qt4 might mean that the plugins aren't being 
checked.  Should be simple enough to prevent going forward, if that 
is actually the problem.

Craig