[sip-comm-dev] Feedback Video quality


#1

I got the latest updates via SVN and checked the video stuff again
and see the follwing message when starting SC:

     [java] 19:14:28.881 SCHWERWIEGEND: impl.neomedia.device.DeviceConfiguration.registerCustomRenderers().1005 Failed to register custom Renderer
net.java.sip.communicator.impl.neomedia.jmfext.media.renderer.video.JAWTRenderer with JMF.

Looking at the preview video at the media options wizard:

- it's faster now (more frames per second?)
- at the same time the quality is not as good, colour is ok, but quite
  "edgy" lines, not straight as before

BTW, any reason why jmf.log file is created?

Regards,
Werner

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#2

Hi Werner,

\[java\] 19:14:28\.881 SCHWERWIEGEND: impl\.neomedia\.device\.DeviceConfiguration\.registerCustomRenderers\(\)\.1005 Failed to register custom Renderer

net.java.sip.communicator.impl.neomedia.jmfext.media.renderer.video.JAWTRenderer with JMF.

JAWTRenderer has its first implementation on Mac OS X only and its
native counterpart is not built because it causes an invalid memory
access due to what seems to be class loading-related issues due to
OSGi (A great thank you to Damian Minkov for discovering it!). An
implementation of JAWTRenderer on Windows is in the works... and in
the hands of Sébastien Vincent. I'll be working on the Linux version
soon.

- it's faster now (more frames per second?)

It depends on when you last looked it prior to the look you took now
:wink: Multiple video-related changes and optimizations were put into
place but not all of them affect the preview.

- at the same time the quality is not as good, colour is ok, but quite
"edgy" lines, not straight as before

While the preview uses our SwScaler which provides scaling with better
quality than JMF's AWTRenderer, I think the AWTRenderer scales the
image once again. It could be it but I'll have to check it out more
carefully to be sure.

BTW, any reason why jmf.log file is created?

Your local copy logging.properties has been modified to enable
debugging of the neomedia bundle and, consequently, Damian Minkov
enables jmf.log.

Best regards,
Lubo

···

On Fri, Apr 30, 2010 at 8:26 PM, Werner Dittmann <Werner.Dittmann@t-online.de> wrote:

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net