dlna allegro

1, Debugging 3pp (Allegro)

I need to get some trace info from the Allegro code.

I found their version of "ifdef debug" and tried to enable it.  It ends up calling printf().  I get a compiler warning about incompatible version of built in function printf, and ultimately nothing appears on the serial port console or logclient output when I run the build.Question: What's the "right" way to enable logclient (preferable) or serial port console (acceptable) output from this 3pp code?

A:  I haven't done this in the KreaTV environment so maybe there is an easier way, but generally you just define AsDebug as 1 (Engine/Includes/AsConfig.h) and then remap RP_PRINTF (Engine/Inlcudes/AsStdLib.h) to call whatever printf style function you want (for example, add your own wrapper function that then calls TTracker for output to logclient).

Yury might have a better suggestion.

 

A: Hi Sam,

I you use fprintf and write it to stderr the logs will appear in logclient.

 

A: In the allegro/patches/series file, you can uncomment the dlna_debug.patch file, and it enables much of the allegro debugging:

#dlna_debug.patch

AAA: When I enable that patch in my IP920 build, appman resets and restarts over and over.  

 

A:  The patch dlna_debug.patch was originally generated when I was working on DMR function. So currently it enables logs most related renderer.

    And everyone who wants to debug allegro is welcome to modify the patch to enable other logs, e.g. DMS, Xml Parser, etc. It is easy to maintain the patch by the tool quilt ( http://wiki.mot-mobility.com/KreaTV/Quilt )    Regarding the issue you met, I don't have IP920 box so I can't help debug it. The patch is tested on VIP19x3 and works well.   Maybe Will Jennings also tested it before :)

 

A:  I enabled KDEBUG in TDlnaContentDirectoryService.cpp and TDlnaOperationTypes.cpp (very nice KTRACE stuff already in there, btw), and it looks like the portal is reporting exactly what Alegro is seeing; nothing appears to be found when I browse into the Media/Videos folder.

Has anyone successfully found and played media content since Alegro was put on trunk?  If so, is there some trick I'm missing?

 

 

 

2, code : platform/3pp/allegro 

IIP: platform/iips/options/dlna

 

KREATV-314_dlna_dms_st 

DEV_dms_cds 

 

 

 

 

3, bugs:

Bug 19299 -DLNA: cannot play asset from DMS

Bug 18714 -DLNA: (Allegro) Playback of kms2095(mp4, h.264, ac3) results in streamer crash.

Bug 18452 -[DLNA] Audio and video playback doesn't work

 

 

4, DMS server

Twonkey DMS server using Ethernet interface (not sure if this helps).

 

 

5, DMC applications

  It may be interesting to use DMC to control other DMRs to play media contents.  Here's an introduction of some open sourced DMC application running on Linux.1)  Cling  (recommended)   http://4thline.org/projects/cling     Cling is a Java/Android UPnP library and tools. It contains a powerful DLNA DMC that works perfectly with DMR on Windows Media Player 11.    It supports playing status, pause/play, jump, progress bar, position, duration, volume, and all the functions works great if the DMR supports well.2)  gupnp-av-cp  it is part of  gupnp-tools  which can be downloaded directly by yum or apt-get    gupnp-av-cp is a simple DMC and very easy to use, the play/pause/stop works well;    but the progress bar, position seems not working.3)  upnp-inspector  also can be downloaded directly by yum or apt-get    It is a powerful tool to inspector upnp devices on the network.    By "right click the devices" it is able to browse the contents in DMS and control the playback of DMR.    Sometimes it's not working and need this application restart to get new information.And another information, Windows Media Player 11 is a great DMP/DMR/DMS, so we can verify some features on this application (thought it only running on Windows...)

 

 The below mail is to introduce some DMC tools that can be used to test DMR function.    Please ignore it if you're not interested :)To Test Team:     gupnp-av-cp  is recommended to be used to test DMR, because it's simple to use, and easy to install, though it sometimes becomes in an unstable state. Restart it if its state becomes abnormal.    But if you have any paid version of DLNA apps on Android or iPad, I think that will be more powerful and stable to use.

 

 

 

6, DMR

 

 

 7, history:

Hi Colleagues,Please be informed that the Motorola DLNA stack and the related platform components are going to be removed since they will be unsupported in KreaTV 4.4:* platform/3pp/dlnalib* platform/dlnamediacontroller* platform/dlnamediaserverAlso I identified configs which use the Motorola stack and need to be updated:* products/ip-box/boot_image/custom/config.vip2262_nexus.template* products/ip-box/boot_image/custom/config.vip25x2_nexus.template* products/ip-box/boot_image/evaluation/config* products/ip-box/boot_image/smoke-test/config.vip25x2* products/ip-box/boot_image/kreatvgfx_webkit/config* products/ip-box/boot_image/kreatvgfx/config
Task record:  19128 The removal was agreed with Martin and Yuri. Are there any points against it?PS: The Motorola DLNA stack is still available at a separate repository:  http://svn.ea.mot.com/dev/vendor/dlna , there is a plan to keep it for possible future use.
Please be informed that the Motorola DLNA stack has been removed from trunk:  221424 From now on, in order to include the new Allegro-based DLNA functionality into your configs, please use united  kreatv-option-dlna  instead of kreatv-option-dlnamediacontroller and kreatv-option-dlnamediaserver

8, How to build DLNA

Hi

Just so on-one misses it; nowadays you need to include this in the config file go get a fully functional DLNA from the start:kreatv-option-is-default::cfg.dlna.dms.enabled=TRUE
kreatv-option-license::file=%BSG_SRC_ABS%/platform/iips/options/license/kreatv_dlna_dmp.license
kreatv-option-license::file=%BSG_SRC_ABS%/platform/iips/options/license/kreatv_dlna_dms.license
kreatv-option-license::file=%BSG_SRC_ABS%/platform/iips/options/license/kreatv_dlna_dmr.licensekreatv-option-dlnamediaserver-pluginkreatv-option-mp4And if you are interested:kreatv-option-env-variables::PLATFORM_DEBUG_DMS=1

 

I don't think so. In any case the license handling for DLNA is no different from any of the other licenses. So I don't think there's a need for a DLNA specific license information page in the Wiki. There's some information in the documentation about licenses already:

   http://kreatvdocs.ea.mot.com/trunk/resources/tutorials/configuring_bootimages.html I think the right way to go here is to add more information there rather than on the Wiki. Licenses are after all targeting the customers and not the developers.

 

 

9,