Feed for discussion General in project Multimedia.
http://community.qnx.com/sf/discussion/do/listTopics/projects.multimedia/discussion.general
Posts for Generalpost119555: Screen Video Capture
http://community.qnx.com/sf/go/post119555
Hi
I understand there is a way to capture a screen as one image, but is there a way to capture screen as a video?sang lee2019-03-01T19:33:41Zpost117295: Unable to play .wav file using wave command in TI J6 VAYU EVM
http://community.qnx.com/sf/go/post117295
Hello,
While i am playing a .wav file using wave command in TI J6 EVM board, we are unable to get the audio.
The following output shows in the terminal
#wave sample.wav
SampleRate = 44100, Channels = 2, SampleBits = 16
Format Signed 16-bit Little Endian
Frag Size 3760
Total Frags 64
Rate 44100
Voices 2
Mixer Pcm Group [Wave playback channel]
Playback Volume level shows 100:100 but we are unable to play the audio.
We are configure the board with latest BSP package(BSP SDK 6.6) and I have copied three files to micro SD card:
1)ifs-dra74x-vayu-evm.bin(Build the BSP SDK 6.6 then generated .bin file)
2)MLO
3)u-boot.img
I prepared the bootable micro SD card and build the BSP by using BSP user guide(Texas Instruments DRA74x and DRA75x (Jacinto 6)Vayu EVM ). i referred the below mentioned link for BSP package and user guide.
http://community.qnx.com/sf/frs/do/listReleases/projects.bsp/frs.qnx_sdp_6_6_bsp_for_the_ti_dra74
Please let me know if any additional packages or patches are needed to add in BSP and additional playback information about the same issue.saikrishna kavva(deleted)2016-12-23T11:07:36Zpost115919: mm-renderer initial play position for HLS real-time broadcast type streams
http://community.qnx.com/sf/go/post115919
For an HLS real-time broadcast type stream, what is the play position at which mm-renderer starts playing the stream? For example, is it 4 chunks back from the end of the first (sliding window) playlist file?
Configuration of interest is: iHE-AAC audio only stream with chunks of 10 seconds each.Dave Mantel(deleted)2016-03-07T16:24:57Zpost115872: RE: can mm-renderer reload cookies from cookie file during play of an HLS stream
http://community.qnx.com/sf/go/post115872
No, mm-renderer only shows that context parameter to the MMF filters once, when it's building its graph for playback. The filters make their own copy, and any changes you make to the context parameter after that have no effect on the existing graph.
-----Original Message-----
From: Dave Mantel [mailto:community-noreply@qnx.com]
Sent: Thursday, February 25, 2016 16:50
To: general-multimedia <general-multimedia@community.qnx.com>
Subject: can mm-renderer reload cookies from cookie file during play of an HLS stream
For the purpose of authentication schemes using HTTP cookies, is there a way to force mm-renderer to reload cookies from a cookie file during playback of HLS stream.
Its understood that we can set a cookie file to be read initially before playback start using mmr_context_parameters() and OPT_COOKIEFILE. Can we call mmr_context_parameters() or mmr_track_parameters() with OPT_COOKIEFILE parameter after during playback (i.e. after mmr_play()) to periodically force mm-renderer to re-read the cookie file, so as that mm-renderer will use cookies that have been updated in the cookie file by the application ?
_______________________________________________
General
http://community.qnx.com/sf/go/post115871
To cancel your subscription to this discussion, please e-mail general-multimedia-unsubscribe@community.qnx.comWojtek Lerch2016-02-26T03:50:12Zpost115871: can mm-renderer reload cookies from cookie file during play of an HLS stream
http://community.qnx.com/sf/go/post115871
For the purpose of authentication schemes using HTTP cookies, is there a way to force mm-renderer to reload cookies from a cookie file during playback of HLS stream.
Its understood that we can set a cookie file to be read initially before playback start using mmr_context_parameters() and OPT_COOKIEFILE. Can we call mmr_context_parameters() or mmr_track_parameters() with OPT_COOKIEFILE parameter after during playback (i.e. after mmr_play()) to periodically force mm-renderer to re-read the cookie file, so as that mm-renderer will use cookies that have been updated in the cookie file by the application ?Dave Mantel(deleted)2016-02-25T21:50:20Zpost115867: Re: RE: mm-renderer authentication
http://community.qnx.com/sf/go/post115867
Moving further along, we get the following error reported by mm-renderer:
Feb 24 12:21:31 2 20 2 mmr: AudioCard8: Start() DRM OPL failed err: 4052
What is this error trying to say and how can it be fixed?Alex Cellarius(deleted)2016-02-24T18:16:19Zpost115866: Re: DRM (copyright protectrion) and mm-renderer
http://community.qnx.com/sf/go/post115866
Thanks Adrian for clarifying. I mostly wanted to make sure I wasn't missing something that was available.
DennisDennis Kellly2016-02-24T13:32:29Zpost115865: Re: DRM (copyright protectrion) and mm-renderer
http://community.qnx.com/sf/go/post115865
In general terms DRM us not supported in CAR or AnM. It is supported on some other platforms (BB10 for example), but requires third party licensing and client-side work.
It could be done through services, however.
Some forms of encrypted HLS are supported with patches, but that is all.
Is there a specific question or questions I can answer?
Adrian B
Sent from my BlackBerry 10 smartphone on the Rogers network.
Original Message
From: Dennis Kellly
Sent: Wednesday, February 24, 2016 7:03 AM
To: general-multimedia
Reply To: general-multimedia@community.qnx.com
Subject: DRM (copyright protectrion) and mm-renderer
mm-renderer can return errors similar to MMR_ERROR_DRM_OUTPUT_PROTECTION when encountering a "protected" streamn.
I can find no discussion of how "DRM" fits into mm-renderer arcfhitecture for AnM or CAR. Seems like a big omission. Can anyone point me to some documentation, or provide some hints?
_______________________________________________
General
http://community.qnx.com/sf/go/post115863
To cancel your subscription to this discussion, please e-mail general-multimedia-unsubscribe@community.qnx.comAdrian Boak(deleted)2016-02-24T13:17:27Zpost115863: DRM (copyright protectrion) and mm-renderer
http://community.qnx.com/sf/go/post115863
mm-renderer can return errors similar to MMR_ERROR_DRM_OUTPUT_PROTECTION when encountering a "protected" streamn.
I can find no discussion of how "DRM" fits into mm-renderer arcfhitecture for AnM or CAR. Seems like a big omission. Can anyone point me to some documentation, or provide some hints?Dennis Kellly2016-02-24T12:03:44Zpost115829: Re: RE: mm-renderer authentication
http://community.qnx.com/sf/go/post115829
Thanks. The examples are helpful.Dennis Kellly2016-02-22T14:42:24Zpost115828: RE: mm-renderer authentication
http://community.qnx.com/sf/go/post115828
mmrplay has a -C option to set context parameters:
# mmrplay -C OPT_COOKIEFILE=/foo/bar -C othereparam=othervalue http://foo.bar/foo.bar
mmcli has a ContextParameters command:
# mmcli -i mmrenderer_cli.so
000.000 Starting...
> ContextParameters OPT_COOKIEFILE=/foo/bar,othereparam=othervalue
> -----Original Message-----
> From: Dennis Kelly [mailto:community-noreply@qnx.com]
> Sent: Monday, February 22, 2016 9:08
> To: general-multimedia@community.qnx.com
> Subject: RE: mm-renderer authentication
>
> Curl, ssl.
>
> "Is there a way to set the OPT_COOKIEFILE parameter normally configured
> via calling mmr_context_parameters()?"
>
> -----Original Message-----
> From: Wojtek Lerch [mailto:community-noreply@qnx.com]
> Sent: Monday, February 22, 2016 9:06 AM
> To: general-multimedia@community.qnx.com
> Subject: RE: mm-renderer authentication
>
> What kind of authentication? What kind of encrypted audio? Is it something
> you know mm-renderer already supports and you just want to figure out
> how to use it, or is there a chance it might require new work inside mm-
> renderer?
>
> > -----Original Message-----
> > From: Dennis Kellly [mailto:community-noreply@qnx.com]
> > Sent: Monday, February 22, 2016 8:47
> > To: general-multimedia
> > Subject: mm-renderer authentication
> >
> > Is there a way to present mmrplay or mmrcli (i.e the mm-renderer
> > utilities) with options and parameters from the authentication result
> > so that the encrypted audio is played? Something like that would help
> > to figure out how to use and debug the mm-renderer API in our code.
> >
> >
> >
> > _______________________________________________
> >
> > General
> > http://community.qnx.com/sf/go/post115825
> > To cancel your subscription to this discussion, please e-mail general-
> > multimedia-unsubscribe@community.qnx.com
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post115826
> To cancel your subscription to this discussion, please e-mail general-
> multimedia-unsubscribe@community.qnx.com
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post115827
> To cancel your subscription to this discussion, please e-mail general-
> multimedia-unsubscribe@community.qnx.comWojtek Lerch2016-02-22T14:34:13Zpost115827: RE: mm-renderer authentication
http://community.qnx.com/sf/go/post115827
Curl, ssl.
"Is there a way to set the OPT_COOKIEFILE parameter normally configured via calling mmr_context_parameters()?"
-----Original Message-----
From: Wojtek Lerch [mailto:community-noreply@qnx.com]
Sent: Monday, February 22, 2016 9:06 AM
To: general-multimedia@community.qnx.com
Subject: RE: mm-renderer authentication
What kind of authentication? What kind of encrypted audio? Is it something you know mm-renderer already supports and you just want to figure out how to use it, or is there a chance it might require new work inside mm-renderer?
> -----Original Message-----
> From: Dennis Kellly [mailto:community-noreply@qnx.com]
> Sent: Monday, February 22, 2016 8:47
> To: general-multimedia
> Subject: mm-renderer authentication
>
> Is there a way to present mmrplay or mmrcli (i.e the mm-renderer
> utilities) with options and parameters from the authentication result
> so that the encrypted audio is played? Something like that would help
> to figure out how to use and debug the mm-renderer API in our code.
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post115825
> To cancel your subscription to this discussion, please e-mail general-
> multimedia-unsubscribe@community.qnx.com
_______________________________________________
General
http://community.qnx.com/sf/go/post115826
To cancel your subscription to this discussion, please e-mail general-multimedia-unsubscribe@community.qnx.comDennis Kellly2016-02-22T14:08:08Zpost115826: RE: mm-renderer authentication
http://community.qnx.com/sf/go/post115826
What kind of authentication? What kind of encrypted audio? Is it something you know mm-renderer already supports and you just want to figure out how to use it, or is there a chance it might require new work inside mm-renderer?
> -----Original Message-----
> From: Dennis Kellly [mailto:community-noreply@qnx.com]
> Sent: Monday, February 22, 2016 8:47
> To: general-multimedia
> Subject: mm-renderer authentication
>
> Is there a way to present mmrplay or mmrcli (i.e the mm-renderer utilities)
> with options and parameters from the authentication result so that the
> encrypted audio is played? Something like that would help to figure out how
> to use and debug the mm-renderer API in our code.
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post115825
> To cancel your subscription to this discussion, please e-mail general-
> multimedia-unsubscribe@community.qnx.comWojtek Lerch2016-02-22T14:06:26Zpost115825: mm-renderer authentication
http://community.qnx.com/sf/go/post115825
Is there a way to present mmrplay or mmrcli (i.e the mm-renderer utilities) with options and parameters from the authentication result so that the encrypted audio is played? Something like that would help to figure out how to use and debug the mm-renderer API in our code.Dennis Kellly2016-02-22T13:47:20Zpost114384: RE: RE: ipod Authentication issue
http://community.qnx.com/sf/go/post114384
Hi Jaime,
Unfortunately we are restricted from public discussion of iPod material so a support ticket is the correct action. I heard that you might have created a ticket so we will follow-up in this way.
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2015-08-31T13:53:09Zpost114374: Re: RE: ipod Authentication issue
http://community.qnx.com/sf/go/post114374
use -i iofs-i2c-ipod.so
QNX_BUILDID=(GNU)94248aea636e5cdbf3dd7839faaa5331
NAME=iofs-i2c-ipod.so
DESCRIPTION=IPOD Driver
DATE=2014/10/28-11:54:40-EDT
STATE=stable
HOST=slave2
USER=builder
VERSION=AnM1.1
TAGID=121Jaime Almeida(deleted)2015-08-28T22:36:23Zpost114373: Re: RE: ipod Authentication issue
http://community.qnx.com/sf/go/post114373
use -i io-fs-media
QNX_BUILDID=(GNU)9cc68021bc73a6451f424a14191c1723
NAME=io-fs-media
DESCRIPTION=Media IOFS Filesystem
DATE=2014/10/28-11:54:43-EDT
STATE=stable
HOST=slave2
USER=builder
VERSION=AnM1.1
TAGID=121
use -i deva-ctrl-ipod.so
QNX_BUILDID=(GNU)9f0054f49f8e3264dbd97ff341664276
NAME=deva-ctrl-ipod.so
DESCRIPTION=Driver for the IPOD.
DATE=2014/02/22-18:43:57-EST
STATE=stable
HOST=sdp-builder-08
USER=builder
VERSION=6.6.0
TAGID=282
use -i iofs-ipod.so
QNX_BUILDID=(GNU)353298ffe7022be12a6eb9193816ea51
NAME=iofs-ipod.so
DESCRIPTION=IPOD Driver
DATE=2014/10/28-11:54:41-EDT
STATE=stable
HOST=slave2
USER=builder
VERSION=AnM1.1
TAGID=121Jaime Almeida(deleted)2015-08-28T22:33:46Zpost114372: Re: RE: ipod Authentication issue
http://community.qnx.com/sf/go/post114372
I have the same issue regaring the Apple Auth IC, but in my case we are using the correct i2c addr and bus.
If we use isend and irecv we can "talk" to the Apple Auth IC, but using the ipod driver we always get the same error as stated.
Further analysis with an i2c sniffer yielded that the read operation fails (no ACK from Auth IC) but is not retried as speficied in the Apple docs.Jaime Almeida(deleted)2015-08-28T22:30:48Zpost113954: Re: RE: RE: Playing video files
http://community.qnx.com/sf/go/post113954
>>>I'm running QNX 6.6.0 with Apps and Media SDK on imx6 Sabrelite system.
If this is true, why are you taking components from the old "accelerator kit"?
>>>the accelerator kit that was used as a source of the libraries is pretty old.
Have you tried the A&M reference image or your target? It plays videos using A&M components - so take all your components from there.Dennis Kellly2015-06-12T11:00:58Zpost113953: Re: RE: RE: Playing video files
http://community.qnx.com/sf/go/post113953
The missing library was indeed libimxvpuapi.so.1. I copied it to /usr/lib and tried playing the video again. I got a following error:
17.691[2] skeleton_video_decoder.c:911 imx6_video_decoder-225306->SetOutputFormat:Input media type or fourcc: '1CVA'---'I420'
17.692[5] skeletonmmf.c:391 imx6_video_decoder-225306->imxmmf_open:input fourcc '1CVA'
17.693[2] skeletonmmf.c:461 imx6_video_decoder-225306->imxmmf_open:vpu_Init failed. err=-1
17.694[2] skeleton_video_decoder.c:914 imx6_video_decoder-225306->SetOutputFormat:could not open the vpu codec
...
/root/html.mp4: error 1 "MMR_ERROR_UNKNOWN" (errno#19,"Can't build graph").
After that I copied a folder named 'vpu' to /lib/firmware and played the video again, the VPU library was found, but I got a segmentation fault in the end: Process 225306 (mm-renderer) terminated SIGSEGV code=1 fltno=11 ip=7829a7a2(/proc/boot/libscreen.so.1@screen_post_window+0xd1) mapaddr=0000a7a2. ref=00000001.
I guess it might be caused by library versions mismatch as the accelerator kit that was used as a source of the libraries is pretty old. Do you have any other suggestions?Mykhailo Rimel(deleted)2015-06-12T08:50:33Zpost113947: RE: RE: Playing video files
http://community.qnx.com/sf/go/post113947
You're most likely missing a required library on the target (my guess is libimxvpuapi.so.1). If you start mm-renderer with the environment variable set:
DL_DEBUG=libs
The linker will be verbose about attempts to load libraries and their dependencies. It can be helpful to track down required libraries.
--
Ryan J. Allen
QNX Software Systems
-----Original Message-----
From: Mykhailo Rimel [mailto:community-noreply@qnx.com]
Sent: Thursday, June 11, 2015 11:00 AM
To: general-multimedia
Subject: Re: RE: Playing video files
Hi, Ryan
Thank you for the fast response.
I have tried playing the file in audio only: # mmrplay /root/html.mp4 and it was successful. After that I found a imx6_video_decoder.so in old accelerator kit and copied it to /lib/dll/mmedia. However, I got an error while trying to play html.mp4 with video: 17.460[2] AoAdd: couldn't load /lib/dll/mmedia/imx6_video_decoder.so (Library cannot be found).
Shall I copy any other files from that accelerator kit or is it any other way to get this decoder library?
_______________________________________________
General
http://community.qnx.com/sf/go/post113946
To cancel your subscription to this discussion, please e-mail general-multimedia-unsubscribe@community.qnx.comRyan Allen(deleted)2015-06-11T15:53:57Zpost113946: Re: RE: Playing video files
http://community.qnx.com/sf/go/post113946
Hi, Ryan
Thank you for the fast response.
I have tried playing the file in audio only: # mmrplay /root/html.mp4 and it was successful. After that I found a imx6_video_decoder.so in old accelerator kit and copied it to /lib/dll/mmedia. However, I got an error while trying to play html.mp4 with video: 17.460[2] AoAdd: couldn't load /lib/dll/mmedia/imx6_video_decoder.so (Library cannot be found).
Shall I copy any other files from that accelerator kit or is it any other way to get this decoder library?Mykhailo Rimel(deleted)2015-06-11T15:00:24Zpost113945: RE: Playing video files
http://community.qnx.com/sf/go/post113945
Hi Mykhailo,
Do the files play in audio only? Remove the "-v screen:" argument to mmrplay. If they play in audio only then it is related to the video decoder (you'd be looking to add imx6_video_decoder.so to your /lib/dll/mmedia directory); if they do not play in audio only then this needs to be understood before your tackle video.
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2015-06-11T13:22:09Zpost113944: Playing video files
http://community.qnx.com/sf/go/post113944
Hello,
I'm trying to play video files of different format (.mp4, .mpg, .avi) but getting errors (see log below). As far as I understand, I need to get an appropriate video decoder. Can someone tell how to get it or what else I'm missing? I'm running QNX 6.6.0 with Apps and Media SDK on imx6 Sabrelite system.
# pps
slog2_api: cannot connect to slogger2 server...errno=No such file or directory
pps: slog2_register() failed (No such file or directory)
pps: NOTICE: PPS initializing
pps: NOTICE: PPS attaching /pps
pps: NOTICE: PPS starting
# mkdir -p /pps/services/multimedia/renderer
# mm-renderer -c -v -e
55.483[5] Initializing "Playlist engine plugin" (mmr-playlist-engine.so)
57.510[3] newctrl: dll(/lib/dll/mmedia/audio_streamer.so) already on clist
57.513[3] newctrl: dll(/lib/dll/mmedia/fildes_streamer.so) already on clist
57.589[3] newctrl: dll(/lib/dll/mmedia/http_streamer.so) already on clist
57.595[3] newctrl: dll(/lib/dll/mmedia/mdev_streamer.so) already on clist
57.596[1] Unable to Initialize the AOI streamers
57.641[5] Initialized "Playlist engine plugin" (mmr-playlist-engine.so)
57.651[5] Initializing "Single-track engine plugin" (mmr-track-engine.so)
57.652[5] Initialized "Single-track engine plugin" (mmr-track-engine.so)
57.715[5] Initializing "QNX MMF routing plugin" (mmr-mmf-routing.so)
57.715[5] load config from: /etc/system/config/aoi.conf
57.716[2] could not open /etc/system/config/aoi.conf for read.
57.717[5] MmInit: -1 DLL ignored from conf /etc/system/config/aoi.conf
57.779[3] newctrl: dll(/lib/dll/mmedia/audio_streamer.so) already on clist
57.837[3] newctrl: dll(/lib/dll/mmedia/fildes_streamer.so) already on clist
57.941[3] newctrl: dll(/lib/dll/mmedia/http_streamer.so) already on clist
57.944[3] newctrl: dll(/lib/dll/mmedia/mdev_streamer.so) already on clist
58.333[5] Could not load the file2b_streamer
58.334[5] Could not load the ivahd_video_decoder
58.337[5] Could not load the flac_parser
58.340[5] Could not load the mpeg2ps_parser
58.340[5] Could not load the mkv_parser
58.343[5] Could not load the asf_parser
58.346[5] Could not load the cloudfs_streamer
58.347[5] Could not load the dupfd_streamer
58.347[5] Could not load the rtsp_streamer
58.348[5] Could not load the remote_frame_writer
58.349[6] MMF router (built on Feb 22 2014 at 19:06:57) initialized
58.349[5] Initialized "QNX MMF routing plugin" (mmr-mmf-routing.so)
58.350[5] Initialization complete
#
#
#
# mmrplay -a "" -v screen: /root/html.mp4
36.291[6] New client ID '@control.17180098587' (@control.17180098587.n0.p229403.u0.g0)
36.294[6] Created context 'testplayer' owned by pid 229403 (0:0), mode=0500
36.295[6] Created context 'testplayer' as #0 for client '@control.17180098587'
36.297[6] Looking for a router for track /root/html.mp4 (2 track params)
36.297[6] Picked router 'MMF router' for track /root/html.mp4
36.298[6] Creating engine 'Single-track engine' for track /root/html.mp4
36.301[5] Found a hint for URL.
36.301[6] in apply_prefetch_parameters
36.311[5] IsStreamPlaylist: playlist initial tag not found... consider it a non playlist stream
36.314[5] Skipping audio graph -- no audio device.
36.343[5] Created the mp4_parser filter based on the parser tag
36.344[5] Skipping Audio subgraph because there is no device specified.
36.344[6] Video writer getting PID 229403.
36.344[5] Finding decoder for stream 1.
36.345[5] Skipping queue after parser.
36.345[5] Couldn't create the ivahd_video_decoder filter (based on the video-decoder tag), mmerr=4046, looking for another one
36.369[2] Couldn't find a suitable video-decoder filter, mmerr=4047
36.370[5] Couldn't find a decoder for the parser output.
36.371[2] The create() call in plugin MMF router failed
36.371[3] Error 5 (mmf#4047) in mmr_input_attach():
36.371[3] Couldn't create routing plugin
36.371[2] Engine 'Single-track engine' failed to create
36.372[5] inputAttach failed (5, mmf#4047:Can't build graph)
/root/html.mp4: error 5 "MMR_ERROR_UNSUPPORTED_MEDIA_TYPE" (mmf#4047,"Can't build graph")
36.373[6] Client ID @control.17180098587 has 1 contexts to close, enqueuing a cleanup command
36.376[6] Destroying context 'testplayer'
36.377[6] Destroyed context 'testplayer' (0 opens left)
36.377[6] Worker 3: deleting client ID @control.17180098587Mykhailo Rimel(deleted)2015-06-11T12:55:00Zpost113823: Regarding source code of Apps and Media 1.1
http://community.qnx.com/sf/go/post113823
Hi,
I have installed QNX SDP 6.6 and Apps and Media 1.1. I am able to run mmrplay to play an audio files.
But I do not see any source code of the Multimedia framework.
Is there any way to get the source code.
Thanks in advance.
Regards,
Archana
________________________________
SASKEN BUSINESS DISCLAIMER: This message may contain confidential, proprietary or legally privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Communication Technologies Limited ("Sasken") unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email.
Read Disclaimer at http://www.sasken.com/extras/mail_disclaimer.htmlarchana gondane(deleted)2015-05-15T08:45:13Zpost113776: RE: RE: RE: Stream to external device over WiFi
http://community.qnx.com/sf/go/post113776
For rendering remote content on consumer devices, I think your idea of HTTP is the most versatile. The downside is that the application logic is on the headunit and often that means it's non-trivial to update in the field. Even though OTA updates are technically possible, each update often has testing and release process overhead.
Another option might be to have the content be available via HTTP (not unlike DLNA), but have a custom application on the consumer device. This can provide some extra flexibility compared to the software being fully on the HU, but then means maintaining client application software (for better or worse). Your API for browsing and getting the content might look a lot like DLNA, which means you might be better off to leverage that, but creating your own API could also allow for extensions.
If going the route of a custom app on the consumer devices you could also establish your own API to talk to a server application on the HU, but this comes with added complexity and I'm not sure it buys you much unless HTTP is a limiting factor for your design.
Aside from HTTP, I don't know of any file sharing type API that would work for both iOS and Android (not to mention other mobile OS's ;) ).
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2015-05-05T12:04:09Zpost113774: Re: RE: RE: Stream to external device over WiFi
http://community.qnx.com/sf/go/post113774
Hi Ryan,
Thanks for the follow up.
I'm talking about the former option, the external device would need to render the contents and the head unit would need to make the media contents available for browsing and playing on the device connected via WiFi.
I've done some research by looking into the CAR platform documentation and I'm trying to understand the options, but your help is much appreciated.
The external device would need to be a consumer device running common mobile OSes (iOS, Android). I was going in the direction of doing streaming over HTTP and having the external device use a HTML5 user interface to control and render the videos, but I'm certainly open to other options as I don't currently have a clear idea of what this entails, especially on the QNX side.
Thanks for your support so far.Simon S(deleted)2015-05-04T17:28:42Zpost113773: RE: RE: Stream to external device over WiFi
http://community.qnx.com/sf/go/post113773
Hi Simon,
It isn't clear to me if you're just trying to access the media contents from the headunit on the external device, or if the expectation is that the headunit will "render" content to the external device. The former tends to be more straightforward, while the latter is more complicated. In the latter case there's also the question of media synchronization (ie, do you need to synchronize audio and/or video across multiple devices).
The other question is whether the external devices are purpose-built or if they may be consumer devices. If you have to support a consumer tablet, for example, this might further restrict your options.
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2015-05-04T17:12:26Zpost113761: Re: RE: Stream to external device over WiFi
http://community.qnx.com/sf/go/post113761
Hi Ryan,
thanks for your reply. Sure I'll try to describe my scenario a little bit better, unfortunately I am not very familiar with the subject therefore I might be missing obvious things.
I am working on a project running on QNX Car Platform and I've been asked to assess the feasibility to stream (or more generally, display) media stored on USB keys / DVD disks connected to the unit on external devices connected to the unit via the WiFi access point exposed by the unit.
I'm trying to figure out what options are available and what would be a quick and cost-effective way to do that. I understand DLNA might be a viable option although I've been informed that developing a solution based on DLNA would be expensive due to licensing costs, so I'm looking at custom options like building a simple media server, capable for example of doing HTTP streaming. But again, I am probably missing many things here hence why I'm asking for advice.Simon S(deleted)2015-04-30T07:41:05Zpost113759: RE: Stream to external device over WiFi
http://community.qnx.com/sf/go/post113759
Simon,
There are a few different possible meanings to this. Can you describe what you are hoping to achieve with a little more detail?
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2015-04-29T17:53:36Zpost113755: Stream to external device over WiFi
http://community.qnx.com/sf/go/post113755
Hello, I'm really new to QNX. I'm trying to figure out if and how it would be possible to stream media contents from QNX Car Platform to an external device over WiFi.
Any help or pointers are greatly appreciated.Simon S(deleted)2015-04-29T14:22:35Zpost113300: RE: Screen API incorrectly sets LVDS register on Sabrelite
http://community.qnx.com/sf/go/post113300
Hi Scott,
I would definitely suggest reaching out to the FAE. I think the source is intended to be included in the BSP, so maybe the source you have is correct. In that case the documentation I linked to earlier might be useful.
Based on feedback from my colleagues I feel reasonably confident that it is not a graphics.conf issue, and that you want to make this change in the wfd config. The good news is that I believe what you're asking for is possible:
"LVDS data mapping is a wfdcfg option (TIMING_LDB_DATA_MAPPING_SPWG_24 or _18). We support both bit-packing orders used by three standards."
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2015-02-12T00:47:18Zpost113299: Re: Screen API incorrectly sets LVDS register on Sabrelite
http://community.qnx.com/sf/go/post113299
Hi Ryan & Dennis,
Thank you for the replies! Unfortunately, I'm not using a Hannstar display like the one Boundary Devices sells. After reading about the wfd config file, I believe I will need to obtain the source code for this so I can modify it as needed.
Please let me know if you find the location of this source code. Otherwise, I'll try working with my FAE to get it.
Just to illustrate what I'm trying to do, my display requires VESA/SPWG data mapping while in 8-bit (per pixel) mode. The current wfd config file in the Sabrelite BSP configures it for JEIDA data mapping. The differences can be seen in the attached photo.
It looks like I either need to obtain and modify the wfd config source code, or their is a configuration option in the graphics.conf file that I haven't tried yet.
ScottScott Moser2015-02-11T23:44:58Zpost113298: Re: Screen API incorrectly sets LVDS register on Sabrelite
http://community.qnx.com/sf/go/post113298
Hi Scott,
I'm not sure that our graphics experts are monitoring this discussion board so I reached out to them. They informed me that LVDS data mapping is a wfd config option. The wfd config is provided as a separate library that is available in source form. I don't see it posted, so you might have to reach out to your support rep to get this, but I have asked to see if it's hiding somewhere in front of me.
We do have some docs about updating the wfd config:
http://www.qnx.com/developers/docs/660/topic/com.qnx.doc.screen.wfdcfg/topic/manual/cwfdcfg_about.html?cp=1_1_7Ryan Allen(deleted)2015-02-11T22:44:43Zpost113291: Re: Screen API incorrectly sets LVDS register on Sabrelite
http://community.qnx.com/sf/go/post113291
Scott-
What version of screen are you trying to use?
It is not necessary to change any registers in the i.mx6 to use rbga8888 on the LVDS 10" Hannstar screen (http://boundarydevices.com/product/nit6x_10-1hannstar/).Dennis Kellly2015-02-11T13:09:49Zpost113286: Re: Screen API incorrectly sets LVDS register on Sabrelite
http://community.qnx.com/sf/go/post113286
I am using U-Boot to load QNX. I failed to mention that U-Boot correctly outputs data in 8-bit format and that is where I got the 0x221 value for the IOMUXC_GPR2 (20E_0008) register from.Scott Moser2015-02-11T02:34:29Zpost113285: Screen API incorrectly sets LVDS register on Sabrelite
http://community.qnx.com/sf/go/post113285
Hello,
I'm running QNX6.6 on my Sabrelite board and I'm trying to configure it for my 10" LCD display operating in 8-bit mode. I have the display connected to LVDS0 and I am able to output 6-bit data just fine (with the LCD in 6-bit mode); however, when I try to output data in 8-bit format (with the LCD in 8-bit mode), it is obvious something is not configured properly since the image looks terrible.
Does anyone know if QNX6.6 supports 8-bit format through the LVDS lines and the screen API? I tried several different formats in the framebuffer class in the graphics.conf file, but none seemed to set the i.MX6's IOMUXC_GPR2 register appropriately. I am currently using format=rgba8888 as a starting point since rgb888 doesn't work at all. Specifically, it appears that I need data in the SPWG standard and not the JEIDA standard that QNX configures it for. When format=rgba8888, the register (20E_0008) is set to 0x1ED. I wrote an application to change this register to 0x221 which appears to be the value I need. When I run my application, the i.MX6 outputs 8-bit data and the display looks great.
Is there a way either through starting the screen API or through the graphics.conf file to configure this register for 8-bit data properly on the Sabrelite? If no one knows, can they at least point me to the source code for the screen driver?
Thank you for your time.
Sincerely,
ScottScott Moser2015-02-11T02:30:48Zpost111427: OMAP5 - MPEG HW ecoding/decoding
http://community.qnx.com/sf/go/post111427
Hi all,
I'm trying to compile the TI DCE package for OMAP5.
I want to use IPC3.0 (and not Syslink) and I'm having some trouble locating the repository for the Ducati image (M4/IVA-HD side).
For the host side I use LIBDCE from http://git.omapzoom.org/?p=repo/libdce.git;a=summary together with IPC3.0 (ipcdev).
For the slave side (Ducati), I'm considering http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/ce/3_24_00_08/index_FDS.html
Can I find the 3_24_00_08 codec engine image already compiled somewhere ?
Am I looking at the correct repositories?
What I'm trying to do is to test using my QNX app the OMAP5 HW video encoding/decoding capabilities.
Thank you !Ruxandra Lica2014-08-14T08:05:56Zpost110993: Re: mm-renderer "unknown client"
http://community.qnx.com/sf/go/post110993
Solved - somehow the mode parameter to mmr_context_create() was not matching S_IRUSR | S_IXUSR.Dennis Kellly2014-07-09T13:03:00Zpost110992: mm-renderer "unknown client"
http://community.qnx.com/sf/go/post110992
Trying to start a video player on 6.5 SP1. Get this error from mm-renderer. It refuses to create the context.
07.222[2] Unable to handle new client ID '@control.17180311595' (no credentialinfo)
07.223[2] Request from an unknown client ID '@control.17180311595'
Cannot find any reference to this in the docs. Where are the "credentials" coming from?Dennis Kellly2014-07-09T12:19:59Zpost110590: Re: Can iPhone Be Used Both As An iPod And BT-A2DP Playback
http://community.qnx.com/sf/go/post110590
The iPod audio can only be streamed to one transport at one time and it will automatically route audio
to the most recent connection. Afterwards, the user can choose the audio transport through a ticker option on the device itself.
Thanks
Kevin
On 2014-06-01, 10:23 AM, "Neeraj Mishra" <community-noreply@qnx.com> wrote:
>iPhone is Connected For HFP And A2DP/AVRCP1.4
>Can We Connect iPhone Again As An iPod Via The USB?
>If We Do, Will It Affect Any Audio Related Functionality Or Any Other
>Functionalities As Such?
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post110550
>To cancel your subscription to this discussion, please e-mail
>general-multimedia-unsubscribe@community.qnx.comKevin Mar(deleted)2014-06-04T22:32:49Zpost110550: Can iPhone Be Used Both As An iPod And BT-A2DP Playback
http://community.qnx.com/sf/go/post110550
iPhone is Connected For HFP And A2DP/AVRCP1.4
Can We Connect iPhone Again As An iPod Via The USB?
If We Do, Will It Affect Any Audio Related Functionality Or Any Other Functionalities As Such?Neeraj Mishra(deleted)2014-06-01T14:23:41Zpost106968: Re: Aviage and Android phones
http://community.qnx.com/sf/go/post106968
Finally got it working. I was missing the "check_MS_desc" option.
Thanks.Yuh-Fwu Guu2013-11-22T13:35:56Zpost106862: Multi channel audio
http://community.qnx.com/sf/go/post106862
Hello,
I'm using the audio library, based on the example given by wave.c
Though I'm currently hitting a wall trying to play a multichannel sound : up to 24 channels...
Where am I supposed to configure the mixer in order to tell him to add the 24 streams to the left and right ears ?
Currently if I put some sound in the first channel, it is played in the right (or left) ouput... but I want it to be center as all the others... Is it possible ?
regards,
PaulThilloy Paul2013-11-19T16:49:54Zpost106733: Re: why openCV isn't efficient on QNX?
http://community.qnx.com/sf/go/post106733
Thank you for your advice , I will try it .robort smith2013-11-13T08:56:49Zpost106731: Re: why openCV isn't efficient on QNX?
http://community.qnx.com/sf/go/post106731
The first thing you should do is to narrow down the area in your application where the largest performance difference is.
If it is related to I/O then the root cause is either IPC overhead or driver performance.
If it is purely the number of CPU cycles burnt for computing the exact same thing then the question is more about the compiler than than the OS as such.
Were you compiling the windoze version yourself too or you were grabbing some binaries built by someone else?
It is possible that your windoze binaries are using hardware optimizations that are not enabled during the QNX build (SSE) or more efficient libraries (e.g., Intel Integrated Performance Primitives).
Whatever the specific reason, your first job is to narrow it down as much as possible.
--
Mate
On Nov 13, 2013, at 4:21 PM, robort smith <community-noreply@qnx.com>
wrote:
> I have compiled opencv on QNX successfully,and it can work normally. The problem is that it isn't efficient. It cost more time for QNX to run the same function than windows.
>
> Is there anything I can do about this problem?
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post106729
> To cancel your subscription to this discussion, please e-mail general-multimedia-unsubscribe@community.qnx.comMate Szarvas2013-11-13T07:33:37Zpost106729: why openCV isn't efficient on QNX?
http://community.qnx.com/sf/go/post106729
I have compiled opencv on QNX successfully,and it can work normally. The problem is that it isn't efficient. It cost more time for QNX to run the same function than windows.
Is there anything I can do about this problem?robort smith2013-11-13T07:21:53Zpost106706: Re: Aviage and Android phones
http://community.qnx.com/sf/go/post106706
If the driver isn't starting at all on device insertion then the USB
device enumerator must not be starting it (or, starts it with incorrect
arguments such that it fails). If you are using enum-usb then the mtp enum
file you shared should be correct. You might try different devices to see
if it's a device-specific failure. You might also check to make sure that
enum-usb can find both io-fs-media and iofs-pfs.so in its path and library
search paths okay.
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2013-11-12T20:39:55Zpost106667: Re: Aviage and Android phones
http://community.qnx.com/sf/go/post106667
Starting the iofs-pfs.so manually via running "io-fs-media -dpfs" from the command prompt works. the directory "/fs/pfs0" showed up and MME/QDB database query listed the mp3 audio files from the Android device. I can also get MME to play the audio files.
What else should I check to see why the auto-detect did not work? The file "mcd.conf" has the pfs section as followings...
[/fs/pfs*]
Callout = PATH_MEDIA_PROCMGR
Argument = /proc/mount
Priority = 11,10
Start Rule = INSERTED
Stop Rule = EJECTED
Thanks.Yuh-Fwu Guu2013-11-11T17:32:47Zpost106664: Re: Aviage and Android phones
http://community.qnx.com/sf/go/post106664
We do have iofs-pfs.so and it is in the path /lib/dll. The file /etc/system/enum/devices/usb/mtp is configured to have io-fs-media starts iofs-pfs driver via the following...
device(usb, mscomp=MTP) driver(io-fs-media "-dpfs,device=$(busno):$(devno):$(iface)")
I was expecting it to start the driver just like it starts the required ipod driver, but it did not. Anything else I should check?
Thanks.Yuh-Fwu Guu2013-11-11T16:34:00Zpost106662: Re: Aviage and Android phones
http://community.qnx.com/sf/go/post106662
You need to have and run the pfs driver (iofs-pfs.so loaded by
io-fs-media). Refer to the Aviage documentation for usage notes on
iofs-pfs.so. If you don't have the driver contact your QNX representative.
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2013-11-11T16:10:48Zpost106660: Aviage and Android phones
http://community.qnx.com/sf/go/post106660
Aviage and mcd can be configured to detect USB stick and play mp3 audio files on the stick. We can do the same with an iPhone connected thru the USB port. How do we do the same with an Ardroid phone? "/fs/usb0" shows up when the USB stick was inserted to the USB port, and "/fs/ipod0" shows up when the iPhone was inserted to the USB port. I was expecting to see "/fs/pfs0" when an Android phone was inserted, but nothing happens. What am I missing?
Thanks.Yuh-Fwu Guu2013-11-11T16:06:47Zpost106133: How can I use opencv under QNX?
http://community.qnx.com/sf/go/post106133
How can I use opencv under QNX?
Now I am trying to use opencv under QNX to trace some objects. While opencv does't support QNX . Is there any thing I can do for this?robort smith2013-10-22T10:17:13Zpost105383: Re: Access to MME source is forbidden
http://community.qnx.com/sf/go/post105383
The source code is no longer been generally available.
Regards,
GillesGilles Roy2013-09-25T02:01:25Zpost105381: Access to MME source is forbidden
http://community.qnx.com/sf/go/post105381
Hi All,
I am trying to check out the MME source code tree with the command listed in the SourceGuide Wiki:
svn checkout --username <userid> http://community.qnx.com/svn/repos/multimedia/trunk
Where I substitute <userid> with the email address I created a "myQNX" login under. However, after entering my password, I get this following error:
Authentication realm: <http://community.qnx.com:80> Authorization Realm
Password for 'acheney@nvidia.com':
svn: access to '/svn/repos/multimedia/trunk' forbidden
I know I am entering the correct password because when I enter the wrong password it gives a different error (reprompts for username).
Is there an extra registration needed to get access?
Thanks
Adam CheneyAdam Cheney2013-09-25T00:10:03Zpost105267: How to deal with MJPEG foramt video?
http://community.qnx.com/sf/go/post105267
Now I am writing USB camera driver.I have already get single frames successfully.At current,The problems are that I don't know how to deal with these frames,and how to show these frames on screen.robort smith2013-09-20T08:44:52Zpost104397: library table restore
http://community.qnx.com/sf/go/post104397
Deleted the contents of library table using query "delete * from library"
due to which its giving "No music files found" err when USB is inserted.
However Iphone usb is working fine.
Kindly help how to resolve this.abhay artya(deleted)2013-08-21T13:34:08Zpost103821: Re: Regarding QNX support for FLAC Codec
http://community.qnx.com/sf/go/post103821
There are ports of it, but it is not officially supported on 6.5 or 6.4.1.
Sent from my BlackBerry 10 smartphone on the Rogers network.
From: Devan Lippman
Sent: Wednesday, July 31, 2013 4:50 PM
To: general-multimedia
Reply To: general-multimedia@community.qnx.com
Subject: Re: Regarding QNX support for FLAC Codec
Is this supported in 6.5 or 6.4.1?
thanks,
Devan
_______________________________________________
General
http://community.qnx.com/sf/go/post103814
To cancel your subscription to this discussion, please e-mail general-multimedia-unsubscribe@community.qnx.comAdrian Boak(deleted)2013-07-31T23:15:36Zpost103814: Re: Regarding QNX support for FLAC Codec
http://community.qnx.com/sf/go/post103814
Is this supported in 6.5 or 6.4.1?
thanks,
DevanDevan Lippman(deleted)2013-07-31T20:50:55Zpost102232: Re: use wave play sound. wave in deadloop
http://community.qnx.com/sf/go/post102232
I check again. It will deadloop in select() function.Di Jin(deleted)2013-06-13T02:49:22Zpost102200: use wave play sound. wave in deadloop
http://community.qnx.com/sf/go/post102200
Dear sir.
I use wave to play a .wav file. I found the wave is deadloop. the information is:
# wave start.wav
SampleRate = 44100, Channels = 2, SampleBits = 16
Format Signed 16-bit Little Endian
Frag Size 3760
Total Frags 64
Rate 44100
Voices 2
Mixer Pcm Group [Wave playback channel]
When I trace the code I found the program will deadloop in while (N < mSamples && n > 0)
I don't know why. the mSamples = 1361076, After N > 240000 the program deadloop, but key still can use.
By the way, I can not get any data from DMA. I check the I2S, it does not send any data.Di Jin(deleted)2013-06-12T12:49:00Zpost101730: Re: MP3 codecs
http://community.qnx.com/sf/go/post101730
As far as I know, Neutrino does not include an mp3 codec as part of the
core OS. We do have MP3 codecs as part of the Aviage package. You may
wish to speak to your QNX representative about that.
--
Ryan J. Allen
QNX Software Systems
On 13-05-27 7:23 AM, "electronics g" <community-noreply@qnx.com> wrote:
>Hi everyone,
>Where can I find mp3 codec for QNX Neutrino 6.5? Could anyone please help
>me with this....
>
>I deeply appreciate the help
>
>
>Thanks in advanceRyan Allen(deleted)2013-05-27T18:52:44Zpost101729: Re: Playing a .mp3 file in Neutrino 6.5
http://community.qnx.com/sf/go/post101729
You will use snd_pcm_plugin_prepare() and snd_pcm_plugin_write() on QNX,
as is done by the wave.c example. Please spend some time looking at the
example as its usage likely differs somewhat compared to the Windows APIs.
<http://www.qnx.com/developers/docs/6.5.0_sp1/topic/com.qnx.doc.neutrino_au
dio/wavec.html>
--
Ryan J. Allen
QNX Software Systems
On 13-05-27 3:36 AM, "electronics g" <community-noreply@qnx.com> wrote:
>Hi all,
>I am new to QNX and I am using i.MX51 board. I am trying to play an audio
>file and to start with I went through wave.c example
>(http://www.qnx.com/developers/docs/6.4.0/neutrino/audio/wavec.html) and
>was able to play the .wav file.
>Now my next task is to play a .mp3 file for which I have the codecs in
>Windows. I have ported all the required calls from Windows to QNX and I
>am also able to play the file but only for first 3 secs. Now in order to
>play the file continuously I need to continuously decode and fill the
>frames in the buffer. In Windows, they use two APIs: waveOutPrepareHeader
>and waveOutWrite which accomplish the task. But in QNX I am not getting
>any equivalent API which could be used to play the complete audio file. :(
>Any suggestions? Please help, I am new to all this....
>
>Thanks in advanceRyan Allen(deleted)2013-05-27T18:51:13Zpost101707: MP3 codecs
http://community.qnx.com/sf/go/post101707
Hi everyone,
Where can I find mp3 codec for QNX Neutrino 6.5? Could anyone please help me with this....
I deeply appreciate the help
Thanks in advanceelectronics g2013-05-27T11:23:08Zpost101700: Playing a .mp3 file in Neutrino 6.5
http://community.qnx.com/sf/go/post101700
Hi all,
I am new to QNX and I am using i.MX51 board. I am trying to play an audio file and to start with I went through wave.c example (http://www.qnx.com/developers/docs/6.4.0/neutrino/audio/wavec.html) and was able to play the .wav file.
Now my next task is to play a .mp3 file for which I have the codecs in Windows. I have ported all the required calls from Windows to QNX and I am also able to play the file but only for first 3 secs. Now in order to play the file continuously I need to continuously decode and fill the frames in the buffer. In Windows, they use two APIs: waveOutPrepareHeader and waveOutWrite which accomplish the task. But in QNX I am not getting any equivalent API which could be used to play the complete audio file. :(
Any suggestions? Please help, I am new to all this....
Thanks in advanceelectronics g2013-05-27T07:36:42Zpost100667: how to capture video using beagleboard
http://community.qnx.com/sf/go/post100667
hi:
this is my first using of QNX,i have a beagleboard omap3530,and a QNX system on it.now i want to capture the video through the board.i thought do it using a USB camera,but it seems there is no driver of USB camera in the system.my USB camera is connected to a USB HUB whitch connect to the USB OTG. this is the output of command usb -vvv:
USB 0 (OMAP3530) v1.10, v1.01 DDK, v1.01 HCD
Device Address : 1
Upstream Host Controller : 0
Upstream Device Address : 0
Upstream Port : 0
Upstream Port Speed : High
Vendor : 0x1a40
Product : 0x0101 (USB 2.0 Hub [MTT])
Device Release : r1.00
USB Spec Release : v2.00
Serial Number : N/A
Class : 0x09 (Hub)
Subclass : 0x00
Protocol : 0x02
Max PacketSize0 : 64
Languages : 0x0409 (English)
Current Frame : 247 (1024 bytes)
Hub Number Ports : 4
Hub Characteristics : 0x0080 (Ganged power, Global over-current)
Hub Power On->Good : 100 ms
Hub Power Requirements : 100 mA
Configurations : 1
Configuration : 1
Attributes : 0xe0 (Self-powered, Remote-wakeup)
Max Power : 100 mA
Interfaces : 1 (with 1 alternate)
Interface : 0 / 0
Class : 0x09 (Hub)
Subclass : 0x00
Protocol : 0x01
Endpoints : Control + 1
Endpoint : 0
Attributes : Control
Max Packet Size: 64
Endpoint : 1
Attributes : Interrupt/IN
Max Packet Size: 1
Interval : 12 ms
Interface : 0 / 1
Class : 0x09 (Hub)
Subclass : 0x00
Protocol : 0x02
Endpoints : Control + 1
Endpoint : 0
Attributes : Control
Max Packet Size: 64
Endpoint : 1
Attributes : Interrupt/IN
Max Packet Size: 1
Interval : 12 ms
Device Address : 2
Upstream Host Controller : 0
Upstream Device Address : 1
Upstream Port : 1
Upstream Port Speed : High
Vendor : 0x1e4e (Etron Technologies)
Product : 0x0100 (USB2.0 Camera)
Device Release : r0.02
USB Spec Release : v2.00
Serial Number : N/A
Class : 0xef (Unknown)
Subclass : 0x02
Protocol : 0x01
Max PacketSize0 : 64
Languages : 0x0409 (English)
Current Frame : 261 (1024 bytes)
Configurations : 1
Configuration : 1
Attributes : 0x80 (Bus-powered)
Max Power : 100 mA
Interfaces : 2 (with 12 alternate)
Interface : 0 / 0 (USB2.0 Camera)
Class : 0x0e (Unknown)
Subclass : 0x01
Protocol : 0x00
Endpoints : Control + 1
Endpoint : 0
Attributes : Control
Max Packet Size: 64
Endpoint : 3
Attributes : Interrupt/IN
Max Packet Size: 64
Interval : 4 ms
Interface : 1 / 0
Class : 0x0e (Unknown)
Subclass : 0x02
Protocol : 0x00
Endpoints : Control + 0
Endpoint : 0
Attributes : Control
Max Packet Size: 64
Interface : 1 / 1
Class : 0x0e (Unknown)
Subclass : 0x02
Protocol : 0x00
Endpoints : Control + 1
Endpoint : 0
Attributes : Control
Max Packet Size: 64
Endpoint : 1
Attributes : Isoch/IN
Max Packet Size: 160
Interval : 1 ms
Interface : 1 / 2
Class : 0x0e (Unknown)
Subclass : 0x02
Protocol : 0x00
Endpoints : Control + 1
Endpoint : 0
Attributes : Control
Max Packet Size: 64
Endpoint : 1
Attributes : Isoch/IN
Max Packet Size: 208
Interval : 1 ms
Interface : 1 / 3
Class : 0x0e (Unknown)
Subclass : 0x02
Protocol : 0x00
Endpoints : Control + 1
Endpoint : 0
Attributes : Control
Max Packet Size: 64
Endpoint : 1
Attributes : Isoch/IN
Max Packet Size: 768
Interval : 1 ms
Interface : 1 / 4
Class : 0x0e (Unknown)
Subclass : 0x02
Protocol : 0x00
Endpoints : Control + 1
Endpoint : 0
Attributes : Control
Max Packet Size: 64
Endpoint : 1
Attributes : Isoch/IN
Max Packet Size: 780
Interval : 1 ms
Interface : 1 / 5
Class : 0x0e (Unknown)
Subclass : 0x02
Protocol : 0x00
Endpoints : Control + 1
Endpoint : 0
Attributes : Control
Max Packet Size: 64
Endpoint : 1
Attributes : Isoch/IN
Max Packet Size: 812
Interval : 1 ms
Interface : 1 / 6
Class : 0x0e (Unknown)
Subclass : 0x02
Protocol : 0x00
Endpoints : Control + 1
Endpoint : 0
Attributes : Control
Max Packet Size: 64
Endpoint : 1
Attributes : Isoch/IN
Max Packet Size: 976
Interval : 1 ms
Interface : 1 / 7
Class : 0x0e (Unknown)
Subclass : 0x02
Protocol : 0x00
Endpoints : Control + 1
Endpoint : 0
Attributes : Control
Max Packet Size: 64
Endpoint : 1
Attributes : Isoch/IN
Max Packet Size: 1020
Interval : 1 ms
Interface : 1 / 8
Class : 0x0e (Unknown)
Subclass : 0x02
Protocol : 0x00
Endpoints : Control + 1
Endpoint : 0
Attributes : Control
Max Packet Size: 64
Endpoint : 1
Attributes : Isoch/IN
Max Packet Size: 1024
Interval : 1 ms
Interface : 1 / 9
Class : 0x0e (Unknown)
Subclass : 0x02
Protocol : 0x00
Endpoints : Control + 1
Endpoint : 0
Attributes : Control
Max Packet Size: 64
Endpoint : 1
Attributes : Isoch/IN
Max Packet Size: 2648
Interval : 1 ms
Interface : 1 / 10
Class : 0x0e (Unknown)
Subclass : 0x02
Protocol : 0x00
Endpoints : Control + 1
Endpoint : 0
Attributes : Control
Max Packet Size: 64
Endpoint : 1
Attributes : Isoch/IN
Max Packet Size: 2816
Interval : 1 ms
Interface : 1 / 11
Class : 0x0e (Unknown)
Subclass : 0x02
Protocol : 0x00
Endpoints : Control + 1
Endpoint : 0
Attributes : Control
Max Packet Size: 64
Endpoint : 1
Attributes : Isoch/IN
Max Packet Size: 4916
Interval : 1 ms
Interface : 1 / 12
Class : 0x0e (Unknown)
Subclass : 0x02
Protocol : 0x00
Endpoints : Control + 1
Endpoint : 0
Attributes : Control
Max Packet Size: 64
Endpoint : 1
Attributes : Isoch/IN
Max Packet Size: 5116
Interval : 1 ms
Device Address : 3
Upstream Host Controller : 0
Upstream Device Address : 1
Upstream Port : 2
Upstream Port Speed : High
Vendor : 0x0b95 (ASIX Elec. Corp.)
Product : 0x7720 (AX88x72A)
Device Release : r0.01
USB Spec Release : v2.00
Serial Number : 000001
Class : 0xff (Vendor-specific)
Subclass : 0xff
Protocol : 0x00
Max PacketSize0 : 64
Languages : 0x0409 (English)
Current Frame : 272 (1024 bytes)
Configurations : 1
Configuration : 1 (0)
Attributes : 0xa0 (Bus-powered, Remote-wakeup)
Max Power : 250 mA
Interfaces : 1
Interface : 0 / 0 (0)
Class : 0xff (Vendor-specific)
Subclass : 0xff
Protocol : 0x00
Endpoints : Control + 3
Endpoint : 0
Attributes : Control
Max Packet Size: 64
Endpoint : 1
Attributes : Interrupt/IN
Max Packet Size: 8
Interval : 11 ms
Endpoint : 2
Attributes : Bulk/IN
Max Packet Size: 512
Endpoint : 3
Attributes : Bulk/OUT
Max Packet Size: 512
there is a device named usb2.0 camera.but how can i use it.
i want to know if someone have done this work before.and please give me some advices.thanks very much.white shaw2013-04-17T02:11:39Zpost100626: Ask to join the multimedia project
http://community.qnx.com/sf/go/post100626
Hello, I'm sorry for the inconvenience.
I asked almost one year ago to join the qnx multimedia project and I never
received any awnser, so I try again by mail.
I wonder if it would be possible to get source code to compile for my
environnement and why not to improve some features.
I thank you in advance, please accept me :D
Florian
________________________________________________________________
This document should only be read by those persons to whom it is
addressed and is not intended to be relied upon by any person
without subsequent written confirmation of its contents. If you
have received this e-mail message in error, please destroy it
and delete it from your computer.
Any form of reproduction, dissemination, copying, disclosure,
modification, distribution and/or publication of this E-mail
message is strictly prohibited.
________________________________________________________________Florian Gaultier(deleted)2013-04-16T08:37:54Zpost95601: RE: Aviage and MPEG2-TS input stream
http://community.qnx.com/sf/go/post95601
I thought but I wanted to make sure before we start investing time on this.
Thanks much!
>-----Original Message-----
>From: Ryan Allen [mailto:community-noreply@qnx.com]
>Sent: Monday, September 17, 2012 9:57 AM
>To: general-multimedia@community.qnx.com
>Subject: Re: Aviage and MPEG2-TS input stream
>
>The current release version of Aviage does not have a parser for mpeg2ts.
>Please feel free to contact your QNX account rep to discuss your specific
>requirements and what may be possible.
>
>--
>Ryan J. Allen
>QNX Software Systems
>
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post95600
>To cancel your subscription to this discussion, please e-mail general-
>multimedia-unsubscribe@community.qnx.comZahira Ammarguellat2012-09-17T14:04:51Zpost95600: Re: Aviage and MPEG2-TS input stream
http://community.qnx.com/sf/go/post95600
The current release version of Aviage does not have a parser for mpeg2ts.
Please feel free to contact your QNX account rep to discuss your specific
requirements and what may be possible.
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2012-09-17T13:59:59Zpost95476: Aviage and MPEG2-TS input stream
http://community.qnx.com/sf/go/post95476
Hello,
I was wondering if Aviage can be configured to play from an input stream instead of a input file. I have an MPEG2_TS stream that I would like to feed to Aviage to render on my device.
Also is there an MPEG2_TS parser?
Any help is appreciated.
-ZahiraZahira Ammarguellat2012-09-10T15:19:51Zpost94692: Re: Could MME support PEQ (48KHz) in playback
http://community.qnx.com/sf/go/post94692
Some customers have specific hardware (like a DSP) and a channel of
communication that they can use to communicate with the hardware. This
would allow them to configure things like EQ (if supported by the
hardware).
But this isn't part of our standard audio solution.
Regards,
GillesGilles Roy2012-08-08T15:30:19Zpost94587: Re: Could MME support PEQ (48KHz) in playback
http://community.qnx.com/sf/go/post94587
Thanks very much Allen!
So only hardware EQ could support? Thanks!Alan Zhang2012-08-02T06:00:04Zpost94586: Re: Could MME support PEQ (48KHz) in playback
http://community.qnx.com/sf/go/post94586
As far as I know, all customers who have any EQ do so after the audio has left the MME (ie, at DSP or external amplifier). MME has no knowledge of it in these cases. There is no software equalizer.
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2012-08-02T05:54:38Zpost94585: Could MME support PEQ (48KHz) in playback
http://community.qnx.com/sf/go/post94585
Could MME support PEQ (48KHz) in playback? ThanksAlan Zhang2012-08-02T05:48:58Zpost94283: Re: mmplay replacement
http://community.qnx.com/sf/go/post94283
I don't believe we ship any comparable application today. We do have the
Aviage multimedia suite (which you could talk to your sales rep about) but
this is a much larger and more complete multimedia solution than mmplay
would have been.
As Dennis pointed out, for simple PCM wave file playback we do have the
"wave" example. It is shipped as a binary but the source is available as
part of the Audio Developer's Guide. You could use this as a starting
point to create a solution that fits your needs. There are no file
parsers or audio codecs (as there are in mmf, which is what mmplay used)
so you are limited to playback of PCM stream wave files, but if the files
are all internal to your system (i.e. users cannot "bring their own
media") then this should not be a problem:
<http://www.qnx.com/developers/docs/6.5.0/topic/com.qnx.doc.neutrino_audio/
wavec.html>
--
Ryan J. Allen
QNX Software Systems
On 12-07-16 7:59 PM, "David DeMint" <community-noreply@qnx.com> wrote:
>I am looking for a simple jutebox like utility that I can put on the
>command line simular to mmplay.Ryan Allen(deleted)2012-07-17T12:54:04Zpost94273: Re: mmplay replacement
http://community.qnx.com/sf/go/post94273
I am looking for a simple jutebox like utility that I can put on the command line simular to mmplay.David DeMint(deleted)2012-07-16T23:59:46Zpost94272: Re: mmplay replacement
http://community.qnx.com/sf/go/post94272
/usr/bin/waveDennis Kellly2012-07-16T22:53:49Zpost94270: mmplay replacement
http://community.qnx.com/sf/go/post94270
Since mmplay is EOL, what utility do you use the play a wav file with version 6.5.0David DeMint(deleted)2012-07-16T22:49:23Zpost93937: Re: audio
http://community.qnx.com/sf/go/post93937
Ryan,
Thanks. A few questions. There is no usage message. How do I run the example? How do I configure the audio system? Are there sample wav files available or do I need to fetch some from the web? Is playing audio on the blackberry X in two/three months going to be this hard?
I have avoided audio on QNX for years as I did not want to be pulled into this particular swamp. I thought it would become easier, but alas...
TerryTerry Laughlin(deleted)2012-06-28T19:58:14Zpost93942: Re: audio
http://community.qnx.com/sf/go/post93942
Terry,
If you take a look at the wave.c example I linked there is an "#ifdef
__USAGE" section that shows the usage. If you have a preferred playback
device (/dev/snd/pcmPreferredp) then I think you can get away with running
"wave /path/to/file.wav". If you don't have a preferred output device you
can change the device with the "-a" argument. If you "ls /dev/snd/"
you'll hopefully see "pcmC#D#p" devices, where the # characters are
replaced with the card and device numbers respectfully.
I do not think any sample wave files are shipped with Neutrino. You'll
want to create your own custom wave files for your needs but you could
probably find examples online. Note that .wav is strictly a container
format so it is possible that some wave files do not contain raw pcm data
(instead they might contain encoded data that requires software to decode
that data to pcm), though these types of files are not common.
BlackBerry 10 provides a framework on top of Neutrino that makes some
things easier. Developers that are using the native NDK may still do
direct audio control using these low-level APIs.
A look through the QNX Audio Dev Guide may help. Note that this is
different than the audio DDK, which may be what you were looking at
before. The Audio Dev Guide will probably give you more information then
you ever wanted to know about playing audio but understanding it may go a
long way when you are trying to debug problems related to playback in the
future:
<http://www.qnx.com/developers/docs/6.5.0/topic/com.qnx.doc.neutrino_audio/
about.html>
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2012-06-28T19:49:36Zpost93936: Re: audio
http://community.qnx.com/sf/go/post93936
Terry,
You could look at the "wave" example:
<http://www.qnx.com/developers/docs/6.5.0/topic/com.qnx.doc.neutrino_audio/
wavec.html>
This example plays a .wav file (you may have a "wave" binary that matches
this source available) by parsing the header, setting up the output, and
streaming the PCM from the file to the output device. If you saved your
sound(s) as wave files you could play them in the same way using this
example.
This is based on there being supported audio hardware, of course. If you
have a playback entry in /dev/snd/ (ends with a 'p' character) then you
should be good to go.
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2012-06-28T19:41:44Zpost93944: Re: audio
http://community.qnx.com/sf/go/post93944
Thanks,
TerryTerry Laughlin(deleted)2012-06-28T19:33:44Zpost93935: audio
http://community.qnx.com/sf/go/post93935
I want to play a (simple) sound as an alarm (the buzzer is not loud enough). I really don't want to code to do this. How do I make a big sound to wake me up? I have looked at the audio docs and they all relate to creating an audio driver. I want sound, not a project.
Thnx,
TerryTerry Laughlin(deleted)2012-06-28T18:52:44Zpost93921: Flash Lite error
http://community.qnx.com/sf/go/post93921
When playing flash (HMI) on the i.MX53 evaluation board following error occurs:
#flash flash.conf abc.swf
unknown symbol: __clz_tab
emerg: Failed to open flash lite dll (flashlite-8888.so): Unresolved symbols
What could be the reason for this error?. The error looks like flashlite-8888.so is not compatible with arm.le.v7 for i.MX53. Is arm.le.v7 version of flashlite-8888.so available?.Ramesh Vemula(deleted)2012-06-28T13:39:45Zpost93778: RE: playing two wav files simultaneously
http://community.qnx.com/sf/go/post93778
Thanks Ryan.
-----Original Message-----
From: Ryan Allen [mailto:community-noreply@qnx.com]
Sent: Tuesday, June 19, 2012 5:50 AM
To: general-multimedia@community.qnx.com
Subject: Re: playing two wav files simultaneously
Ramesh,
The intel_hda driver only creates a mixer for one playback device. If you want a mixer for both devices you'll have to create a PR for this.
Without a mixer on both devices you will always be limited to one process sending audio to one of the playback devices.
--
Ryan J. Allen
QNX Software Systems
_______________________________________________
General
http://community.qnx.com/sf/go/post93745
To cancel your subscription to this discussion, please e-mail general-multimedia-unsubscribe@community.qnx.comRamesh Vemula(deleted)2012-06-20T05:37:09Zpost93745: Re: playing two wav files simultaneously
http://community.qnx.com/sf/go/post93745
Ramesh,
The intel_hda driver only creates a mixer for one playback device. If you
want a mixer for both devices you'll have to create a PR for this.
Without a mixer on both devices you will always be limited to one process
sending audio to one of the playback devices.
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2012-06-18T20:53:48Zpost93690: Re: playing two wav files simultaneously
http://community.qnx.com/sf/go/post93690
Ryan,
Please find attached output of the two commands you mentioned.Ramesh Vemula(deleted)2012-06-15T08:55:32Zpost93658: Re: playing two wav files simultaneously
http://community.qnx.com/sf/go/post93658
Ramesh,
Can you provide the output of "pidin -p io-audio arg" and "pidin -p io-audio mem", please?
Thank you,
--
Ryan J. Allen
QNX Software Systems
________________________________
From: "Ramesh Vemula" <community-noreply@qnx.com>
To: "general-multimedia" <general-multimedia@community.qnx.com>
Sent: 14 June, 2012 6:01 AM
Subject: Re: playing two wav files simultaneously
Thanks Gilles, it solved the problem. However customer wants to have both outputs behave in the same manner. For example, if output1 is playing a track session and output2 is playing another track session (both via mme). And output1 is tied to the software mixer (pcmC0D2p), when I pause both outputs and play a wave file using the wave utility, output1 will work, but output2 will fail as it is not tied to a software mixer. They can't tie it to the same software mixer as output1 because they need to play different audio independently.
Is it possible to have two software mixers each tied to a dedicated output?.
_______________________________________________
General
http://community.qnx.com/sf/go/post93656
To cancel your subscription to this discussion, please e-mail general-multimedia-unsubscribe@community.qnx.comRyan Allen(deleted)2012-06-14T11:49:33Zpost93656: Re: playing two wav files simultaneously
http://community.qnx.com/sf/go/post93656
Thanks Gilles, it solved the problem. However customer wants to have both outputs behave in the same manner. For example, if output1 is playing a track session and output2 is playing another track session (both via mme). And output1 is tied to the software mixer (pcmC0D2p), when I pause both outputs and play a wave file using the wave utility, output1 will work, but output2 will fail as it is not tied to a software mixer. They can't tie it to the same software mixer as output1 because they need to play different audio independently.
Is it possible to have two software mixers each tied to a dedicated output?.Ramesh Vemula(deleted)2012-06-14T10:01:52Zpost93572: Re: playing two wav files simultaneously
http://community.qnx.com/sf/go/post93572
I think I see the problem. In mme_data.sql you have:
INSERT INTO outputdevices(type, permanent, name, devicepath) VALUES(1, 1,
'output1', 'snd:/dev/snd/pcmC0D0p');
This means MME will use pcmC0D0p.
But wave will use pcmPreferredp, which points to:
pcmPreferredp -> pcmC0D2p
pcmC0D2p is your software mixer. If you change MME to use pcmPreferredp or
pcmC0D2p it should be able to concurrently playback with the wave utility.
Regards,
GillesGilles Roy2012-06-07T14:59:18Zpost93568: Re: playing two wav files simultaneously
http://community.qnx.com/sf/go/post93568
Hi Gilles,
Please find attached mme_data.sql.
output of ls -al /dev/snd:
total 0
-rw-rw-rw- 1 root root 0 May 13 2011 controlC0
-rw-rw-rw- 1 root root 0 May 13 2011 mixerC0D0
-rw-rw-rw- 1 root root 0 May 18 15:22 pcmC0D0c
-rw-rw-rw- 1 root root 0 May 18 15:22 pcmC0D0p
-rw-rw-rw- 1 root root 0 May 18 15:22 pcmC0D1c
-rw-rw-rw- 1 root root 0 May 18 15:22 pcmC0D1p
-rw-rw-rw- 1 root root 0 May 13 2011 pcmC0D2p
lrw-rw-rw- 1 root root 0 May 18 15:22 pcmPreferredc -> pcmC0D0c
lrw-rw-rw- 1 root root 0 May 18 15:22 pcmPreferredp -> pcmC0D2pRamesh Vemula(deleted)2012-06-07T09:44:33Zpost93518: Re: playing two wav files simultaneously
http://community.qnx.com/sf/go/post93518
We might need more logs. It sounds like the MME is not using a mixer
(hardware or software) device. If you want multiple connections to the
audio device you need to use the software mixer, this should allow the
scenario you listed to work.
Can you post the output of:
ls -al /dev/snd
And also post the contents of mme_data.sql?
Thanks,
GillesGilles Roy2012-06-05T14:48:53Zpost93514: playing two wav files simultaneously
http://community.qnx.com/sf/go/post93514
While playing a wav audio file with MME, is it possible to pause the play, then play a wav audio file using the "wave" utility?. Using the wave utility two wav files can be played simultaneously, but If I played one wav file via MME, then try to play a second wav file using the wave utility, it failed as follows:
SampleRate = 22050, Channels = 1, SampleBits = 8
snd_pcm_plugin_params failed: Invalid atgument
What could be the reason for this error?.Ramesh Vemula(deleted)2012-06-05T13:18:51Zpost92520: deva was hang up
http://community.qnx.com/sf/go/post92520
Dear all,
I'm developing deva driver, when I use "wave" command to play .wav file, it jumps to interrupt handler but after that, it was hang up, it means I cannot press any key as Enter or Ctrl+C. How about this case, please help me. Thank you!Vinh Pham2012-04-11T09:58:38Zpost92174: Re: Error trying to play a .mp4 file
http://community.qnx.com/sf/go/post92174
You will need the ipp_video_decoder. You will need to talk to your sales
contact about how to get it.
On 12-03-19 9:25 AM, "Yuh-Fwu Guu" <community-noreply@qnx.com> wrote:
>All we have in /lib/dll/mmedia are listed below...what else do we need to
>get the video decoders?
>
>aac_parser.so
>audio_streamer.so
>audio_writer.so
>cdda_parser.so
>cdda_streamer.so
>damping_audio_writer.so
>fildes_streamer.so
>gf_writer.so
>http_streamer.so
>media_streamer.so
>mp4_parser.so
>mpega_parser.so
>ogg_decoder.so
>ogg_encoder.so
>qnx_raac_decoder.so
>queue_filter.so
>rawfile_writer.so
>rtp_reader.so
>stream_reader.so
>tmpfile_streamer.so
>wav_parser.so
>wavfile_writer.so
>wma9_decoder.so
>wma9_parser.so
>xing_mpega_decoder.so
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post92173
>Adrian Boak(deleted)2012-03-19T13:27:06Zpost92173: Re: Error trying to play a .mp4 file
http://community.qnx.com/sf/go/post92173
All we have in /lib/dll/mmedia are listed below...what else do we need to get the video decoders?
aac_parser.so
audio_streamer.so
audio_writer.so
cdda_parser.so
cdda_streamer.so
damping_audio_writer.so
fildes_streamer.so
gf_writer.so
http_streamer.so
media_streamer.so
mp4_parser.so
mpega_parser.so
ogg_decoder.so
ogg_encoder.so
qnx_raac_decoder.so
queue_filter.so
rawfile_writer.so
rtp_reader.so
stream_reader.so
tmpfile_streamer.so
wav_parser.so
wavfile_writer.so
wma9_decoder.so
wma9_parser.so
xing_mpega_decoder.soYuh-Fwu Guu2012-03-19T13:25:10Zpost92171: Re: Error trying to play a .mp4 file
http://community.qnx.com/sf/go/post92171
On x86, the video decoder ,if you have one, will be called
ipp_video_decoder.so and should be in /lib/dll/mmedia
On 12-03-19 8:45 AM, "Yuh-Fwu Guu" <community-noreply@qnx.com> wrote:
>x86 + QNX 6.5.0 + Aviage 2.0
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post92169
>Adrian Boak(deleted)2012-03-19T13:02:47Zpost92170: Re: Error trying to play a .mp4 file
http://community.qnx.com/sf/go/post92170
I forgot we also have QNX CAR Subscription and with licenses of the followings...
Interface for iPod
Interface for WMDRM10-ND
Codec for MP3
Codec for WMA9
Interface for Zune
Codec for AAC Interface for PlaysForSure
Acoustic Processing
DVD Playback
Interface for TI OMAP
Aviage HMI Suite.Yuh-Fwu Guu2012-03-19T12:53:52Zpost92169: Re: Error trying to play a .mp4 file
http://community.qnx.com/sf/go/post92169
x86 + QNX 6.5.0 + Aviage 2.0Yuh-Fwu Guu2012-03-19T12:45:56Zpost92167: Re: Error trying to play a .mp4 file
http://community.qnx.com/sf/go/post92167
You probably don't have a video decoder. What CPU platform are you using?
On 12-03-19 8:24 AM, "Yuh-Fwu Guu" <community-noreply@qnx.com> wrote:
>How do I find out what video decoder we have? All I have done was
>installed QNX 6.5.0 and Aviage Multimedia 2.0.
>
>I guess I need help configure the mme to play .mp4 video?
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post92166
>Adrian Boak(deleted)2012-03-19T12:33:54Zpost92166: Re: Error trying to play a .mp4 file
http://community.qnx.com/sf/go/post92166
How do I find out what video decoder we have? All I have done was installed QNX 6.5.0 and Aviage Multimedia 2.0.
I guess I need help configure the mme to play .mp4 video?Yuh-Fwu Guu2012-03-19T12:24:45Zpost92151: Re: Error trying to play a .mp4 file
http://community.qnx.com/sf/go/post92151
> I am still having problem playing the same mp4 file. It has progressed a bit
> now that I have audio, but there is no video. Could someone please help...
What video decoders do you have on your device? I just downloaded the file and tried it on a Playbook, and it played using the ivahd_video_decoder filter.
> 4 20 1 io-media-generic/trackplayer: Couldn't find a suitable video-
> decoder filter, mmerr=4047
That sounds pretty clear to me, even before I looked up error 4047 and confirmed that it means "no filter supports format"...Wojtek Lerch2012-03-16T18:10:26Zpost92149: Re: Error trying to play a .mp4 file
http://community.qnx.com/sf/go/post92149
I am still having problem playing the same mp4 file. It has progressed a bit now that I have audio, but there is no video. Could someone please help...
The sloginfo contains the followings...
5 20 1 io-media-generic/mmf: writer hint snd:* found
5 20 1 io-media-generic/mmf: writer hint gf:* found
1 27 0 MME:_setiomoutputattr(5759): Output device type 2 not supported
5 20 1 io-media-generic/mmf: Configuring the queue for -1 bytes, lw = 0, hw = 0.
5 20 1 io-media-generic/aoi: MP4Parser: max sample size = 277930.
5 20 1 io-media-generic/aoi: MP4Parser: max sample size = 995.
5 20 1 io-media-generic/mmf: Configuring the queue for 1512877 bytes, lw = 302575, hw = 1210301.
5 20 1 io-media-generic/mmf: Configuring the queue for 192000 bytes, lw = 19200, hw = 172800.
5 20 1 io-media-generic/aoi: audio_writer using output device: '/dev/snd/pcmC0D0p'
5 20 1 io-media-generic/aoi: audio_writer asking for Signed 16-bit Little Endian, 1..2x19200B frags, 48000Hz, bps=4, 2ch
5 20 1 io-media-generic/aoi: audio_writer settings: Signed 16-bit Little Endian, 3x19200B frags, 48000Hz, bps=4, 2ch, Q time 300ms
5 20 1 io-media-generic/aoi: audio_writer PGA_StreamerCreate() push mode = 0 adjusting chunk_size from 19200bytes to 19200bytes
5 20 1 io-media-generic/aoi: audio_writer mixer disabled
4 20 1 io-media-generic/trackplayer: Couldn't find a suitable video-decoder filter, mmerr=4047
2 20 1 io-media-generic/trackplayer: Error 10004, 2, 4047:
2 20 1 io-media-generic/trackplayer: Couldn't create a linking filter for parsed stream
2 27 0 MME:_attachinput(3694): Could not attach input (/fs/usb0///Captain America - The First Avenger - Trailer 2.mp4) to controlcontext PCM1 (fid=3). errno=5
2 27 0 MME:_play(3150): Could not attach file '/fs/usb0///Captain America - The First Avenger - Trailer 2.mp4'
2 27 0 MME:_playuntilok(5511): Stopping playback because 1 errors were hit consecutively while playing track session 2
2 27 0 MME:_setgenericvalue(851): Send Error for request=2, value=3. errno 22Yuh-Fwu Guu2012-03-16T16:38:22Zpost91228: Re: gf_writer and mp4_parser
http://community.qnx.com/sf/go/post91228
Hello!~
You can check the config file of io-display!xiaolong zhang2012-01-30T10:11:28Zpost91136: RTP/RTCP support
http://community.qnx.com/sf/go/post91136
A customer is interested in RTP/RTCP support to be able to record H.264 frames to disk from an IP camera.
No playback or processing of the H.264 data in anyway on the QNX host!
Is there a library in aviage which provides this support (for example, a full-featured version of curl)?
Or, is RTP/RTCP implemented in a UDP application or specialized mme library?
Any subset of Aviage which would give the customer an API to record RTP data frames?
TIADennis Kellly2012-01-25T16:10:05Zpost91007: Re: Error trying to play a .mp4 file
http://community.qnx.com/sf/go/post91007
I think this link is where I downloaded the file...
http://www.dvdloc8.com/clip.php?movieid=24662&clipid=1Yuh-Fwu Guu2012-01-19T13:31:28Zpost91000: Re: Error trying to play a .mp4 file
http://community.qnx.com/sf/go/post91000
> Are you talking about this mp4 file? It's a movie trailer (Captain America) I
> downloaded from internet and it's more than 121 MB.
Just a link to where you downloaded it from would be perfect.Wojtek Lerch2012-01-19T03:53:30Zpost90993: Re: Error trying to play a .mp4 file
http://community.qnx.com/sf/go/post90993
Are you talking about this mp4 file? It's a movie trailer (Captain America) I downloaded from internet and it's more than 121 MB.
I did not have an mp4 file to test before, so I searched internet for mp4 file example and found one.
I will see if I could find one with a smaller size.
Thanks.Yuh-Fwu Guu2012-01-18T22:55:24Zpost90992: Re: Error trying to play a .mp4 file
http://community.qnx.com/sf/go/post90992
It might be easier to answer these if I could have a copy of the file...Wojtek Lerch2012-01-18T22:13:18Zpost90991: Re: Error trying to play a .mp4 file
http://community.qnx.com/sf/go/post90991
I am able to play the same file on the QNX CAR M6 demo.
Does this mean that the qnx_raac_decoder version I have from QNX6.5.0 and MME 1.2 is different from the one on the QNX CAR M6?
If this is the case, how do I get the updated version?
Thanks.Yuh-Fwu Guu2012-01-18T21:59:23Zpost90990: Re: Error trying to play a .mp4 file
http://community.qnx.com/sf/go/post90990
Yuh-Fwu Guu wrote:
> Hello,
>
> I am trying to play an mp4 file and I am getting the error "Couldn't load the qnx_raac_decoder filter (based on the decoder tag), mmerr=48". I do have "qnx_raac_decoder.so" located in /lib/dll/mmedia along with many other ".so" files. Can someone tell me what I am missing? I am running QNX6.5.0 and MME 1.2 on an x86 system.
Error 48 is MM_ENOTSUP, "stream format not supported". The
qnx_raac_decoder doesn't support all variants of AAC.Wojtek Lerch2012-01-18T21:43:33Zpost90989: Error trying to play a .mp4 file
http://community.qnx.com/sf/go/post90989
Hello,
I am trying to play an mp4 file and I am getting the error "Couldn't load the qnx_raac_decoder filter (based on the decoder tag), mmerr=48". I do have "qnx_raac_decoder.so" located in /lib/dll/mmedia along with many other ".so" files. Can someone tell me what I am missing? I am running QNX6.5.0 and MME 1.2 on an x86 system.
The entries generated by calling the mme_play() function are the followings...
Sev Major Minor Args
5 27 0 MME:io_handle_msg(117): RCV -> MME_IOMSG_TYPE_PLAY: "fid=6"
5 27 0 MME:_playuntilok(5489): Reset consecutive playback error count
5 27 0 MME:_playuntilok(5507): Consecutive playback errors: current=0 max=1
5 27 0 MME:_suspend_sync(1133): Suspending sync: ccid 1, msid 2
5 27 0 MME:mme_ms_lock(541): Lock call for media store 2 of type playback.
6 20 1 io-media-generic/trackplayer: Created graph instance 'PCM1'
6 20 1 io-media-generic: open( 'graphs/trackplayer/PCM1' ): success
5 20 1 io-media-generic/mmf: writer hint snd:* found
6 20 1 io-media-generic/mmf: URL 'snd:/dev/snd/pcmC0D0p' matches pattern 'snd:*'
5 27 0 MME:_attachoutputs(3611): Attached outputdevice snd:/dev/snd/pcmC0D0p to controlcontext PCM1. id=0
5 20 1 io-media-generic/mmf: writer hint gf:* found
6 20 1 io-media-generic/mmf: URL 'gf:8086,8108,0?layer=1&aspn=72&aspd=77&sat=20' matches pattern 'gf:*'
1 27 0 MME:_setiomoutputattr(5759): Output device type 2 not supported
5 27 0 MME:_attachoutputs(3611): Attached outputdevice gf:8086,8108,0?layer=1&aspn=72&aspd=77&sat=20 to controlcontext PCM1. id=1
5 27 0 MME:cleanup_thread(262): Got pulse with code 0 and index 0.
6 20 1 io-media-generic/mmf: URL '/fs/mnt/Public2/usb0///Captain America - The First Avenger - Trailer 2.mp4' matches pattern '*.mp4'
6 20 1 io-media-generic/mmf: Setting long resource 'StreamerStickyError' (value='1')
6 20 1 io-media-generic/mmf: Setting long resource 'MM_TMPFILE_STREAMER_SEEKABLE' (value='1')
6 20 1 io-media-generic/mmf: Setting long resource 'MM_AUDIO_WRITER_NO_MIXER' (value='1')
5 20 1 io-media-generic/mmf: Configuring the queue for -1 bytes, lw = 0, hw = 0.
6 20 1 io-media-generic/trackplayer: Loaded the mp4_parser filter based on the parser tag
6 20 1 io-media-generic/mmf: Setting long resource 'AVSyncDelay' (value='0')
5 20 1 io-media-generic/mmf: Configuring the queue for 1512877 bytes, lw = 302575, hw = 1210301.
4 20 1 io-media-generic/trackplayer: Couldn't load the qnx_raac_decoder filter (based on the decoder tag), mmerr=48
4 20 1 io-media-generic/trackplayer: Couldn't find a suitable decoder filter, mmerr=48
2 20 1 io-media-generic/trackplayer: Error 10004, 2, 48:
2 20 1 io-media-generic/trackplayer: Couldn't create a linking filter for parsed stream
2 27 0 MME:_attachinput(3694): Could not attach input (/fs/mnt/Public2/usb0///Captain America - The First Avenger - Trailer 2.mp4) to controlcontext PCM1 (fid=6). errno=5
5 27 0 MME:_attachinput(3727): io-media iom_attach_input time=0.112.
5 27 0 MME:ntfy_log_event(753): MME_EVENT_PLAY_ERROR(type: 10; fid/trksessionid: 6; offset: 0)
5 27 0 MME:mme_ms_unlock(702): Unlock call for media store 2 of type playback.
5 27 0 MME:_resume_sync(1148): Resuming sync: ccid 1, msid 2
2 27 0 MME:_play(3150): Could not attach file '/fs/mnt/Public2/usb0///Captain America - The First Avenger - Trailer 2.mp4'
5 27 0 MME:_playuntilok(5536): Incrementing consecutive playback error count
5 27 0 MME:_playuntilok(5507): Consecutive playback errors: current=1 max=1
2 27 0 MME:_playuntilok(5511): Stopping playback because 1 errors were hit consecutively while playing track session 1
5 27 0 MME:ntfy_log_event(618): MME_EVENT_FINISHED_WITH_ERROR
6 20 1 io-media-generic/trackplayer: Destroyed graph instance 'PCM1'
2 27 0 MME:_setgenericvalue(851): Send Error for request=2, value=6. errno 22
5 27 0 MME:cleanup_thread(262): Got pulse with code 0 and index 0.
Thanks.Yuh-Fwu Guu2012-01-18T21:38:29Zpost90686: Re: gf_writer and mp4_parser
http://community.qnx.com/sf/go/post90686
Hi,
Can anyone please comment about the gf_writer for arm target??
I tried to run with it. But its crashing ....
Thanks,
ArunArun Johnson2011-12-19T17:11:55Zpost90667: Re: gf_writer and mp4_parser
http://community.qnx.com/sf/go/post90667
Hi,
I am working on armle target with io-display as the video renderer
my decoder is decoding the video in I420 format. and the layers all support packed YUV ( Packed YUV, 16bpp: U8Y8V8Y8 ). The deoder is linked to gf_writer for arm for rendering to screen. gf_writer finally accepts a layer and agrees for software color conversion. The decoder can decode the first MRA and then it gives a seg fault. I verified the decoder with rawfile_writer. everythign seems to be fine. I can get the output in the fil without crash.
Can anyone tell the requirements for the display driver to successfully integrate with gf_writer ?
Thanks,
ArunArun Johnson2011-12-16T15:25:53Zpost90654: Re: gf_writer and mp4_parser
http://community.qnx.com/sf/go/post90654
please correct me if I am wrong
so you are saying that , it can render to the screen if the display driver supports packed yuv ??
Thanks,
ArunArun Johnson2011-12-16T01:04:24Zpost90653: Re: gf_writer and mp4_parser
http://community.qnx.com/sf/go/post90653
No it doesn't. Our allocators don't work that way. It would need to be converted to a packed format.
----- Original Message -----
From: Arun Johnson [mailto:community-noreply@qnx.com]
Sent: Thursday, December 15, 2011 07:31 PM
To: general-multimedia <post90651@community.qnx.com>
Subject: Re: gf_writer and mp4_parser
for one of the video only mp4 file, just before the crash , I am getting the following logs..
can anyone tell me if the gf_writer from QNX has a direct planar YUV rendering support ???
fwriter->Resume(0,-24893630447616)
mp4_parser->NextBuffer
mp4_parser sending MRAE_TYPE_DECODER_CONFIG with 2 payloads.
Gfwriter Status. 256
Gfwriter GetResources
mp4_parser new MRA
mp4_parser MRAE_TYPE_BYTE_POSITION, offset 36.
mp4_parser IOV, offset 36, size 32768.
mp4_parser offset in IOV buffer = 0
mp4_parser TRACE chan 1169376 passing on chunk 0 of 1830, ref. offset 36, ref. size 3892
mp4_parser (3) output size = 3892
mp4_parser TRACE file offset 36, buffer offset 0, buffer size 3892
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 3892
mp4_parser TRACE chan 1169376 passing on chunk 1 of 1830, ref. offset 3928, ref. size 65
mp4_parser (3) output size = 65
mp4_parser TRACE file offset 36, buffer offset 3892, buffer size 65
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 3957
mp4_parser TRACE chan 1169376 passing on chunk 2 of 1830, ref. offset 3993, ref. size 1306
mp4_parser (3) output size = 1306
mp4_parser TRACE file offset 36, buffer offset 3957, buffer size 1306
mp4_parsermp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 5263
mp4_parser TRACE chan 1169376 passing on chunk 3 of 1830, ref. offset 5299, ref. size 59
mp4_parser (3) output size = 59
mp4_parser TRACE file offset 36, buffer offset 5263, buffer size 59
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 5322
mp4_parser TRACE chan 1169376 passing on chunk 4 of 1830, ref. offset 5358, ref. size 1312
mp4_parser (3) output size = 1312
mp4_parser TRACE file offset 36, buffer offset 5322, buffer size 1312
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 6634
mp4_parser TRACE chan 1169376 passing on chunk 5 of 1830, ref. offset 6670, ref. size 1508
mp4_parser (3) output size = 1508
mp4_parser TRACE file offset 36, buffer offset 6634, buffer size 1508
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 8142
mp4_parser TRACE chan 1169376 passing on chunk 6 of 1830, ref. offset 8178, ref. size 1508
mp4_parser (3) output size = 1508
mp4_parser TRACE file offset 36, buffer offset 8142, buffer size 1508
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 9650
mp4_parser TRACE chan 1169376 passing on chunk 7 of 1830, ref. offset 9686, ref. size 1644
mp4_parser (3) output size = 1644
mp4_parser TRACE file offset 36, buffer offset 9650, buffer size 1644
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 11294
mp4_parser TRACE chan 1169376 passing on chunk 8 of 1830, ref. offset 11330, ref. size 1410
mp4_parser (3) output size = 1410
mp4_parser TRACE file offset 36, buffer offset 11294, buffer size 1410
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 12704
mp4_parser TRACE chan 1169376 passing on chunk 9 of 1830, ref. offset 12740, ref. size 73
mp4_parser (3) output size = 73
mp4_parser TRACE file offset 36, buffer offset 12704, buffer size 73
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 12777
mp4_parser TRACE chan 1169376 passing on chunk 10 of 1830, ref. offset 12813, ref. size 1347
mp4_parser (3) output size = 1347
mp4_parser TRACE file offset 36, buffer offset 12777, buffer size 1347
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 14124
mp4_parser TRACE chan 1169376 passing on chunk 11 of 1830, ref. offset 14160, ref. size 1559
mp4_parser (3) output size = 1559
mp4_parser TRACE file offset 36, buffer offset 14124, buffer size 1559
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 15683
mp4_parser TRACE chan 1169376 passing on chunk 12 of 1830, ref. offset 15719, ref. size 4274
mp4_parser (3) output size = 4274
mp4_parser TRACE file offset 36, buffer offset 15683, buffer size 4274
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 19957
mp4_parser TRACE chan 1169376 passing on chunk 13 of 1830, ref. offset 19993, ref. size 1509
mp4_parser (3) output size = 1509
mp4_parser TRACE file offset 36, buffer offset 19957, buffer size 1509
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 21466
mp4_parser TRACE chan 1169376 passing on chunk 14 of 1830, ref. offset 21502, ref. size 1438
mp4_parser (3) output size = 1438
mp4_parser TRACE file offset 36, buffer offset 21466, buffer size 1438
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 22904
mp4_parser TRACE chan 1169376 passing on chunk 15 of 1830, ref. offset 22940, ref. size 65
mp4_parser (3) output size = 65
mp4_parser TRACE file offset 36, buffer offset 22904, buffer size 65
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 22969
mp4_parser TRACE chan 1169376 passing on chunk 16 of 1830, ref. offset 23005, ref. size 1526
mp4_parser (3) output size = 1526
mp4_parser TRACE file offset 36, buffer offset 22969, buffer size 1526
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 24495
mp4_parser TRACE chan 1169376 passing on chunk 17 of 1830, ref. offset 24531, ref. size 1451
mp4_parser (3) output size = 1451
mp4_parser TRACE file offset 36, buffer offset 24495, buffer size 1451
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 25946
mp4_parser TRACE chan 1169376 passing on chunk 18 of 1830, ref. offset 25982, ref. size 1376
mp4_parser (3) output size = 1376
mp4_parser TRACE file offset 36, buffer offset 25946, buffer size 1376
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 27322
mp4_parser TRACE chan 1169376 passing on chunk 19 of 1830, ref. offset 27358, ref. size 1615
mp4_parser (3) output size = 1615
mp4_parser TRACE file offset 36, buffer offset 27322, buffer size 1615
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 28937
mp4_parser TRACE chan 1169376 passing on chunk 20 of 1830, ref. offset 28973, ref. size 1439
mp4_parser (3) output size = 1439
mp4_parser TRACE file offset 36, buffer offset 28937, buffer size 1439
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 30376
mp4_parser TRACE chan 1169376 passing on chunk 21 of 1830, ref. offset 30412, ref. size 133
mp4_parser (3) output size = 133
mp4_parser TRACE file offset 36, buffer offset 30376, buffer size 133
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 30509
mp4_parser TRACE chan 1169376 passing on chunk 22 of 1830, ref. offset 30545, ref. size 1331
mp4_parser (3) output size = 1331
mp4_parser TRACE file offset 36, buffer offset 30509, buffer size 1331
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 31840
mp4_parser TRACE chan 1169376 passing on chunk 23 of 1830, ref. offset 31876, ref. size 1403
mp4_parser (1) output size = 928
mp4_parser TRACE file offset 36, buffer offset 31840, buffer size 928
mp4_parser adding MRAE_TYPE_PARTIAL_PACKET
mp4_parser freeing imra 0
mp4_parser NextBuffer sending an MRA with 53 elements
getting MRAE_TYPE_DECODER_CONFIG
getting the track ES configuration, 38 bytes
CORRECT NAL HEADER SIZE, 4 bytes
video_decoder NextBuffer() forwarding property type 0x9 index 3
sheeva_video_decoder got PTS from parser of 0.
video_decoder: got iov.
video_decoder DecodeAndOutput isize = 3892, ipdata = 176000
sheeva_video_decoder: DecodeAndOutput Initializing decoder with init_data = 10b240, init_size = 35
sheeva_video_decoder->DecodeAndOutput() bytes_consumed = 3892 got_picture 1
video_decoder->DecodeAndOutput() output timestamp = 0
video_decoder->DecodeAndOutput() Y pl_size 337920
video_decoder->DecodeAndOutput() MmfSetMraBufferElement looping
video_decoder->DecodeAndOutput() U pl_size 84480
video_decoder->DecodeAndOutput() MmfSetMraBufferElement looping
video_decoder->DecodeAndOutput() V pl_size 84480
video_decoder->DecodeAndOutput() MmfSetMraBufferElement looping
video_decoder DecodeAndOutput isize = 3892, ipdata = 176000 bytes_consumed 3892
_______________________________________________
General
http://community.qnx.com/sf/go/post90651Adrian Boak(deleted)2011-12-16T00:46:00Zpost90652: Re: gf_writer and mp4_parser
http://community.qnx.com/sf/go/post90652
continuing from the previous mail.....
it gives me a seg fault at
terminated SIGSEGV code=1 fltno=11 ip=7800a3c0(libmmedia.so.1@__clz_tab+0x1118) mapaddr=0000a3c0.
Thanks,
ArunArun Johnson2011-12-16T00:38:15Zpost90651: Re: gf_writer and mp4_parser
http://community.qnx.com/sf/go/post90651
for one of the video only mp4 file, just before the crash , I am getting the following logs..
can anyone tell me if the gf_writer from QNX has a direct planar YUV rendering support ???
fwriter->Resume(0,-24893630447616)
mp4_parser->NextBuffer
mp4_parser sending MRAE_TYPE_DECODER_CONFIG with 2 payloads.
Gfwriter Status. 256
Gfwriter GetResources
mp4_parser new MRA
mp4_parser MRAE_TYPE_BYTE_POSITION, offset 36.
mp4_parser IOV, offset 36, size 32768.
mp4_parser offset in IOV buffer = 0
mp4_parser TRACE chan 1169376 passing on chunk 0 of 1830, ref. offset 36, ref. size 3892
mp4_parser (3) output size = 3892
mp4_parser TRACE file offset 36, buffer offset 0, buffer size 3892
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 3892
mp4_parser TRACE chan 1169376 passing on chunk 1 of 1830, ref. offset 3928, ref. size 65
mp4_parser (3) output size = 65
mp4_parser TRACE file offset 36, buffer offset 3892, buffer size 65
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 3957
mp4_parser TRACE chan 1169376 passing on chunk 2 of 1830, ref. offset 3993, ref. size 1306
mp4_parser (3) output size = 1306
mp4_parser TRACE file offset 36, buffer offset 3957, buffer size 1306
mp4_parsermp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 5263
mp4_parser TRACE chan 1169376 passing on chunk 3 of 1830, ref. offset 5299, ref. size 59
mp4_parser (3) output size = 59
mp4_parser TRACE file offset 36, buffer offset 5263, buffer size 59
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 5322
mp4_parser TRACE chan 1169376 passing on chunk 4 of 1830, ref. offset 5358, ref. size 1312
mp4_parser (3) output size = 1312
mp4_parser TRACE file offset 36, buffer offset 5322, buffer size 1312
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 6634
mp4_parser TRACE chan 1169376 passing on chunk 5 of 1830, ref. offset 6670, ref. size 1508
mp4_parser (3) output size = 1508
mp4_parser TRACE file offset 36, buffer offset 6634, buffer size 1508
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 8142
mp4_parser TRACE chan 1169376 passing on chunk 6 of 1830, ref. offset 8178, ref. size 1508
mp4_parser (3) output size = 1508
mp4_parser TRACE file offset 36, buffer offset 8142, buffer size 1508
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 9650
mp4_parser TRACE chan 1169376 passing on chunk 7 of 1830, ref. offset 9686, ref. size 1644
mp4_parser (3) output size = 1644
mp4_parser TRACE file offset 36, buffer offset 9650, buffer size 1644
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 11294
mp4_parser TRACE chan 1169376 passing on chunk 8 of 1830, ref. offset 11330, ref. size 1410
mp4_parser (3) output size = 1410
mp4_parser TRACE file offset 36, buffer offset 11294, buffer size 1410
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 12704
mp4_parser TRACE chan 1169376 passing on chunk 9 of 1830, ref. offset 12740, ref. size 73
mp4_parser (3) output size = 73
mp4_parser TRACE file offset 36, buffer offset 12704, buffer size 73
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 12777
mp4_parser TRACE chan 1169376 passing on chunk 10 of 1830, ref. offset 12813, ref. size 1347
mp4_parser (3) output size = 1347
mp4_parser TRACE file offset 36, buffer offset 12777, buffer size 1347
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 14124
mp4_parser TRACE chan 1169376 passing on chunk 11 of 1830, ref. offset 14160, ref. size 1559
mp4_parser (3) output size = 1559
mp4_parser TRACE file offset 36, buffer offset 14124, buffer size 1559
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 15683
mp4_parser TRACE chan 1169376 passing on chunk 12 of 1830, ref. offset 15719, ref. size 4274
mp4_parser (3) output size = 4274
mp4_parser TRACE file offset 36, buffer offset 15683, buffer size 4274
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 19957
mp4_parser TRACE chan 1169376 passing on chunk 13 of 1830, ref. offset 19993, ref. size 1509
mp4_parser (3) output size = 1509
mp4_parser TRACE file offset 36, buffer offset 19957, buffer size 1509
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 21466
mp4_parser TRACE chan 1169376 passing on chunk 14 of 1830, ref. offset 21502, ref. size 1438
mp4_parser (3) output size = 1438
mp4_parser TRACE file offset 36, buffer offset 21466, buffer size 1438
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 22904
mp4_parser TRACE chan 1169376 passing on chunk 15 of 1830, ref. offset 22940, ref. size 65
mp4_parser (3) output size = 65
mp4_parser TRACE file offset 36, buffer offset 22904, buffer size 65
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 22969
mp4_parser TRACE chan 1169376 passing on chunk 16 of 1830, ref. offset 23005, ref. size 1526
mp4_parser (3) output size = 1526
mp4_parser TRACE file offset 36, buffer offset 22969, buffer size 1526
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 24495
mp4_parser TRACE chan 1169376 passing on chunk 17 of 1830, ref. offset 24531, ref. size 1451
mp4_parser (3) output size = 1451
mp4_parser TRACE file offset 36, buffer offset 24495, buffer size 1451
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 25946
mp4_parser TRACE chan 1169376 passing on chunk 18 of 1830, ref. offset 25982, ref. size 1376
mp4_parser (3) output size = 1376
mp4_parser TRACE file offset 36, buffer offset 25946, buffer size 1376
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 27322
mp4_parser TRACE chan 1169376 passing on chunk 19 of 1830, ref. offset 27358, ref. size 1615
mp4_parser (3) output size = 1615
mp4_parser TRACE file offset 36, buffer offset 27322, buffer size 1615
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 28937
mp4_parser TRACE chan 1169376 passing on chunk 20 of 1830, ref. offset 28973, ref. size 1439
mp4_parser (3) output size = 1439
mp4_parser TRACE file offset 36, buffer offset 28937, buffer size 1439
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 30376
mp4_parser TRACE chan 1169376 passing on chunk 21 of 1830, ref. offset 30412, ref. size 133
mp4_parser (3) output size = 133
mp4_parser TRACE file offset 36, buffer offset 30376, buffer size 133
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 30509
mp4_parser TRACE chan 1169376 passing on chunk 22 of 1830, ref. offset 30545, ref. size 1331
mp4_parser (3) output size = 1331
mp4_parser TRACE file offset 36, buffer offset 30509, buffer size 1331
mp4_parser mp4_parser_COMPLETE_MODE
mp4_parser offset in IOV buffer = 31840
mp4_parser TRACE chan 1169376 passing on chunk 23 of 1830, ref. offset 31876, ref. size 1403
mp4_parser (1) output size = 928
mp4_parser TRACE file offset 36, buffer offset 31840, buffer size 928
mp4_parser adding MRAE_TYPE_PARTIAL_PACKET
mp4_parser freeing imra 0
mp4_parser NextBuffer sending an MRA with 53 elements
getting MRAE_TYPE_DECODER_CONFIG
getting the track ES configuration, 38 bytes
CORRECT NAL HEADER SIZE, 4 bytes
video_decoder NextBuffer() forwarding property type 0x9 index 3
sheeva_video_decoder got PTS from parser of 0.
video_decoder: got iov.
video_decoder DecodeAndOutput isize = 3892, ipdata = 176000
sheeva_video_decoder: DecodeAndOutput Initializing decoder with init_data = 10b240, init_size = 35
sheeva_video_decoder->DecodeAndOutput() bytes_consumed = 3892 got_picture 1
video_decoder->DecodeAndOutput() output timestamp = 0
video_decoder->DecodeAndOutput() Y pl_size 337920
video_decoder->DecodeAndOutput() MmfSetMraBufferElement looping
video_decoder->DecodeAndOutput() U pl_size 84480
video_decoder->DecodeAndOutput() MmfSetMraBufferElement looping
video_decoder->DecodeAndOutput() V pl_size 84480
video_decoder->DecodeAndOutput() MmfSetMraBufferElement looping
video_decoder DecodeAndOutput isize = 3892, ipdata = 176000 bytes_consumed 3892Arun Johnson2011-12-16T00:31:49Zpost90649: gf_writer and mp4_parser
http://community.qnx.com/sf/go/post90649
Hi,
I was trying to play an mp4 file and I am getting the following problems with the playback. I am working on armlev7 platform. I was able to play all audio formats(aac,mp3,wma) using the framework components.
Can anyone tell me where am I going wrong:
Logs from the individual components.
Gfwriter Start.
Gfwriter->Resume(0,-24893630447616)
mp4_parser->NextBuffer
mp4_parser->MmfAcquireMra() failed
GfwriterTask NextBuffer MM_STATUS_ERROR.
GfwriterTask status != MM_STATUS_PLAYING (0x1)
mp4_parser->NextBuffer
mp4_parser->MmfAcquireMra() failed
Gfwriter Status. 1
Gfwriter Stop.
New mutex WaitForPlayingStatus set channel STOPPED
gf_writer: Filter status set to stopped.
Gfwriter Status. 16
gf_writer->Flush()
New mutex Flush.
Gfwriter Stop.
New mutex WaitForPlayingStatus set channel STOPPED
gf_writer: Filter status set to stopped.
Gfwriter Status. 16
gf_writer->Flush()
New mutex Flush.
Gfwriter ReleaseInputChannel.
mp4_parser: ReleaseOutputChannel: enter
mp4_parser: ReleaseOutputChannel: exit
mp4_parser: ReleaseOutputChannel: enter
mp4_parser: ReleaseOutputChannel: exit
Gfwriter Destroy.
Thanks,
ArunArun Johnson2011-12-15T21:11:08Zpost90477: Re: mp4_files
http://community.qnx.com/sf/go/post90477
i am using mp4_parser with aviage core 1.2
Thanks,
ArunArun Johnson2011-12-07T19:55:01Zpost90476: Re: mp4_files
http://community.qnx.com/sf/go/post90476
I tried removing that ..Its still giving me the following:
Jan 01 00:00:08 5 20 1 io-media-generic/mmf: writer hint snd:* found
Jan 01 00:00:08 5 20 1 io-media-generic/mmf: writer hint gf:* found
Jan 01 00:00:08 1 27 0 MME:_setiomoutputattr(5959): Output device type 2 not supported
Jan 01 00:00:08 5 20 1 io-media-generic/mmf: Configuring the queue for -1 bytes, lw = 0, hw = 0, thr = -1.
Jan 01 00:00:08 2 20 1 io-media-generic/aoi: fildes streamer seek: failing (22)
Jan 01 00:00:08 5 20 1 io-media-generic/aoi: MP4Parser: max sample size = 10875.
Jan 01 00:00:08 2 20 1 io-media-generic/aoi: fildes streamer seek: failing (22)
Jan 01 00:00:08 5 20 1 io-media-generic/mmf: Configuring the queue for 881335 bytes, lw = 176267, hw = 705068, thr = -1.
Jan 01 00:00:08 5 20 1 io-media-generic/trackplayer: Skipping subgraph 0 because there is no device specified.
I am using the attached m4v file for this run.
Thanks,
ArunArun Johnson2011-12-07T19:25:50Zpost90475: Re: mp4_files
http://community.qnx.com/sf/go/post90475
> can anyone tell me what's the error related to output saying:
> Jan 01 00:04:25 2 20 1 io-media-generic/aoi: fildes streamer seek:
> failing (22)
This one means that lseek returned EINVAL. The only reason I can think of is that either a bug in the parser or a problem in your MP4 file caused the parser to attempt a seek to a negative position in the file.
> Jan 01 00:04:25 2 20 1 io-media-generic/aoi: fildes streamer seeking
> failing on StreamerStickyErrror resource set
The StreamerStickyErrror resource that you have in your configuration file asks the streamer to remember the first error that happens, and keep returning it from any subsequent calls. It's a way to prevent other parsers from wasting time trying to read a file after an I/O error, such as when the file is on a scratched disc or the media has been ejected.
Try removing both resource{} elements that set the StreamerStickyErrror resource from your configuration file. If that makes the file play, it could be that the invalid seek was caused by a bug in the parser. What version are you running? Can I have a copy of your MP4 file?Wojtek Lerch2011-12-07T19:01:53Zpost90474: Re: mp4_files
http://community.qnx.com/sf/go/post90474
Hi ,
can anyone tell me what's the error related to output saying:
Jan 01 00:04:25 5 20 1 io-media-generic/mmf: writer hint snd:* found
Jan 01 00:04:25 5 20 1 io-media-generic/mmf: writer hint gf:* found
Jan 01 00:04:25 1 27 0 MME:_setiomoutputattr(5959): Output device type 2 not supported
Jan 01 00:04:25 5 20 1 io-media-generic/mmf: Configuring the queue for -1 bytes, lw = 0, hw = 0, thr = -1.
Jan 01 00:04:25 2 20 1 io-media-generic/aoi: fildes streamer seek: failing (22)
Jan 01 00:04:25 2 20 1 io-media-generic/aoi: fildes streamer seeking failing on StreamerStickyErrror resource set
Jan 01 00:04:25 5 20 1 io-media-generic/mmf: Configuring the queue for 881335 bytes, lw = 176267, hw = 705068, thr = -1.
Jan 01 00:04:25 5 20 1 io-media-generic/trackplayer: Skipping subgraph 0 because there is no device specified.
Thanks,
ArunArun Johnson2011-12-07T18:45:23Zpost90456: Re: mp4_filesClick me.
http://community.qnx.com/sf/go/post90456
The post contains invalid characters .Please click uhe above post link to view the content.Adrian Boak(deleted)2011-12-06T20:08:41Zpost90455: Re: mp4_filesClick me.
http://community.qnx.com/sf/go/post90455
The post contains invalid characters .Please click uhe above post link to view the content.Arun Johnson2011-12-06T20:05:56Zpost90454: Re: mp4_files
http://community.qnx.com/sf/go/post90454
> I am attaching my cfg file.
The file is indeed incorrect -- it's missing a "value=0" line in the resource{} element that was supposed to unset the StreamerStickyError resource (around line 237 in your file). Try adding it back and see what happens.Wojtek Lerch2011-12-06T19:40:02Zpost90453: Re: mp4_files
http://community.qnx.com/sf/go/post90453
I am working on arm target. with qnx6 filesystem nio my eMMC mounted by:
mount -t qnx6 /dev/hd0t179 /media
Thanks,
ArunArun Johnson2011-12-06T19:33:18Zpost90452: Re: mp4_files
http://community.qnx.com/sf/go/post90452
> 2 20 1 io-media-generic/aoi: fildes streamer seek: failing (22)
Actually this one is even more interesting... Errno 22 is EINVAL -- what filesystem was your file living in?Wojtek Lerch2011-12-06T19:32:10Zpost90451: Re: mp4_files
http://community.qnx.com/sf/go/post90451
I am working on arm target. with qnx6 filesystem nio my eMMC mounted by:
mount -t qnx6 /dev/hd0t179 /media
Thanks,
ArunArun Johnson2011-12-06T19:30:57Zpost90450: Re: mp4_files
http://community.qnx.com/sf/go/post90450
Hi Wojtek,
I am attaching my cfg file.
Thanks,
ArunArun Johnson2011-12-06T19:29:22Zpost90449: Re: mp4_filesClick me.
http://community.qnx.com/sf/go/post90449
The post contains invalid characters .Please click uhe above post link to view the content.Adrian Boak(deleted)2011-12-06T19:25:16Zpost90448: Re: mp4_files
http://community.qnx.com/sf/go/post90448
> 2 20 1 io-media-generic/mmf: A resource element is missing a 'value'
> attribute
This indicates that there's something wrong with your io-media configuration file. Can I have a copy?Wojtek Lerch2011-12-06T19:24:51Zpost90447: Re: mp4_filesClick me.
http://community.qnx.com/sf/go/post90447
The post contains invalid characters .Please click uhe above post link to view the content.Arun Johnson2011-12-06T19:19:49Zpost90428: Re: mp4_files
http://community.qnx.com/sf/go/post90428
> Jan 01 00:00:49 4 20 1 io-media-generic/trackplayer: Couldn't load
> the mp4_parser filter (based on the parser tag), mmerr=4047
Error 4047 (MM_ENFSF) means that the filter was loaded but didn't like your file. (Apologies for an inaccurate error message...)Wojtek Lerch2011-12-05T18:52:57Zpost90426: mp4_files
http://community.qnx.com/sf/go/post90426
Hi,
I was trying to use MME for mp4 playback. but its failing with there errors. The logs are attached as follows:
I am using mmecli as the client for playback. can anybody please tell me whats going wrong ? The mp4_parser.so is the default parser and the video+audio files is a good playable file.
Jan 01 00:00:06 2 20 1 io-media-generic/trackplayer: Error 10004:
Jan 01 00:00:06 2 20 1 io-media-generic/trackplayer: Couldn't find a parser for '/media/drive/salt-video.mp4'
Jan 01 00:00:06 2 27 200 MDP:metadata_get(801): Failed iom_get_track_info, errno = 5
Jan 01 00:00:06 3 27 200 MDP:mdp_mgr_metadata_get_int(1161): Error getting metadata for group 00000002 from "/media/drive/salt-video.mp4": An external resource call used by the MDP failed. (10).
Jan 01 00:00:49 5 20 1 io-media-generic/mmf: writer hint snd:* found
Jan 01 00:00:49 5 20 1 io-media-generic/mmf: writer hint gf:* found
Jan 01 00:00:49 1 27 0 MME:_setiomoutputattr(5959): Output device type 2 not supported
Jan 01 00:00:49 5 20 1 io-media-generic/mmf: Configuring the queue for -1 bytes, lw = 0, hw = 0, thr = -1.
Jan 01 00:00:49 4 20 1 io-media-generic/trackplayer: Couldn't load the mp4_parser filter (based on the parser tag), mmerr=4047
Jan 01 00:00:49 4 20 1 io-media-generic/trackplayer: Couldn't find a suitable parser filter, mmerr=4047
Jan 01 00:00:49 2 20 1 io-media-generic/trackplayer: Error 10004, 2, 4047:
Jan 01 00:00:49 2 20 1 io-media-generic/trackplayer: Couldn't create a linking filter for raw stream
Jan 01 00:00:49 2 27 0 MME:_attachinput(3782): Could not attach input (/media/drive///salt-video.mp4) to controlcontext default (fid=2). errno=5
Jan 01 00:00:49 2 27 0 MME:_play(3224): Could not attach file '/media/drive///salt-video.mp4'
Jan 01 00:00:49 2 27 0 MME:_setgenericvalue(888): Send Error for request=2, value=0. errno 11
Thanks,
ArunArun Johnson2011-12-05T18:40:00Zpost90373: Re: QDB and SQLite
http://community.qnx.com/sf/go/post90373
At compile time QDB saves SQLITE_VERSION_NUMBER (from the sqlite header);
at run-time it compares this to the sqlite library's version number. If
it doesn't match, qdb exits. So, fundamentally, you have a version
mis-match here.
Either:
A) the sqlite header file qdb is being built against doesn't match the
sqlite library that you're building (perhaps you forgot to "make hinstall"
in lib/sqlite before building qdb); or
B) qdb isn't using the libsqlite library you are putting on your target
(another library may be in the library search path).
To test for (B), you could start QDB with the DL_DEBUG environment
variable to determine where qdb is loading libsqlite from:
DL_DEBUG=libs qdb -c ...
If qdb is loading the correct library then it's likely that (a) is the
problem and qdb is being built against a different sqlite header.
(As an aside: if you can, I would recommend using qnx-provided binaries
rather than binaries you've built yourself.)
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2011-11-30T18:16:47Zpost90372: Re: mp4_parser
http://community.qnx.com/sf/go/post90372
It is an mp4 file parser, so it parses/demuxes files in the iso family
(mp4, m4a, m4v, mov, 3gp, 3gp2, etc). Audio and video.
On 11-11-30 12:18 PM, "Preetham Chandrian" <community-noreply@qnx.com>
wrote:
>Hi,
>
>I am using aviage on arm target.
>I can see an mp4_parser.so as one of the filters provided with the
>package.
>
>Is this a mp4 stream parser (audio and video) or just a video parser ?
>
>Can someone please clarify the details about this ?
>
>Thanks,
>Preetham
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post90371
>Adrian Boak(deleted)2011-11-30T17:23:19Zpost90371: mp4_parser
http://community.qnx.com/sf/go/post90371
Hi,
I am using aviage on arm target.
I can see an mp4_parser.so as one of the filters provided with the package.
Is this a mp4 stream parser (audio and video) or just a video parser ?
Can someone please clarify the details about this ?
Thanks,
PreethamPreetham Chandrian2011-11-30T17:18:35Zpost90370: Re: MmSetDefaultClock
http://community.qnx.com/sf/go/post90370
As I said earlier. MMF is not a customer-facing, or supported API for
Aviage. Sorry. If you want to play media using Aviage, please use the
MME.
On 11-11-30 12:01 PM, "Arun Johnson" <community-noreply@qnx.com> wrote:
>No I wanted to have an understanding of the framework internally so that
>I can write my own player.
>
>by commenting out MmSetDefaultClock, I am able to get the graph started
>but Mmstatus returns MM_STATUS_ERROR.
>
>Is there anything else I need to consider for plying just a wave file.
>
>you help is reapply appreciated
>
>thanks,
>arun
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post90369
>Adrian Boak(deleted)2011-11-30T17:05:00Zpost90369: Re: MmSetDefaultClock
http://community.qnx.com/sf/go/post90369
No I wanted to have an understanding of the framework internally so that I can write my own player.
by commenting out MmSetDefaultClock, I am able to get the graph started
but Mmstatus returns MM_STATUS_ERROR.
Is there anything else I need to consider for plying just a wave file.
you help is reapply appreciated
thanks,
arunArun Johnson2011-11-30T17:01:31Zpost90368: Re: QDB and SQLite
http://community.qnx.com/sf/go/post90368
This is what I got : I was using the source file from trunk: to get this
use -i /tmp/qdb /tmp/libsqlite3.so.1
NAME=qdb
DESCRIPTION=QNX SQL Database Server
DATE=2011/11/29-11:42:24-EST
STATE=Experimental
HOST=pc138
USER=ajohnson
NAME=libsqlite3.so
DESCRIPTION=SQLite Library
DATE=2011/11/16-12:20:39-EST
STATE=Experimental
HOST=pc138
USER=ajohnsonArun Johnson2011-11-30T16:58:11Zpost90367: Re: QDB and SQLite
http://community.qnx.com/sf/go/post90367
Find "qdb" and "libsqlite.so.1" on the target and run:
"use -i /path/to/qdb /path/to/libsqlite.so.1"
Most likely they will be from different builds and the use information
will not match.
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2011-11-30T16:48:45Zpost90366: Re: MmSetDefaultClock
http://community.qnx.com/sf/go/post90366
If you are using Aviage, MMF is not a customer-facing API. Why have you
chosen that? Is there something the MME is not able to do for you?
On 11-11-30 11:37 AM, "Arun Johnson" <community-noreply@qnx.com> wrote:
>I am using Aviage for the purpose.
>
>Thanks
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post90364
>Adrian Boak(deleted)2011-11-30T16:47:18Zpost90365: Re: QDB and SQLite
http://community.qnx.com/sf/go/post90365
I am so sorry I couldnt understand the use of -i
I am new to this and trying to run this on arm.
I am using
qdb -c /db/qdb.cfg -v -Otempstore=/fs/tmpfs -Rset
to set it up ..everything else I got from the multimedia package (Aviage core 1.2)
Thanks,
ArunArun Johnson2011-11-30T16:39:49Zpost90364: Re: MmSetDefaultClock
http://community.qnx.com/sf/go/post90364
I am using Aviage for the purpose.
ThanksArun Johnson2011-11-30T16:37:43Zpost90363: Re: MmSetDefaultClock
http://community.qnx.com/sf/go/post90363
I am trying to learn about the library using examples from QNX Neutrino, Multimedia Developer's guide. Specifically Ex: "playing MP3". I was learning to use the
media reader, wave parser and audio writer to get playing a wave file. I assume this is all I need to play a wave file.
io-audio is functional in my system and I am able to play wave files using the wave utility. I am trying to achieve the same functionality with MMF. But this function is giving me a linking error.
Thanks,
ArunArun Johnson2011-11-30T16:37:01Zpost90362: Re: QDB and SQLite
http://community.qnx.com/sf/go/post90362
Could you provide the use -i for qdb and sqlite?
On 11-11-30 10:36 AM, "Arun Johnson" <community-noreply@qnx.com> wrote:
>Hi,
>
>I am setting up aviage on arm target.
> I am getting a conflict while setting QDB
>
>its giving me :
>
>qdb: QDB requires SQLite version "3.6.12", found "3.6.23.1"
>
>
>I know its something to do with the some libraries. But can anybody point
>me the correct libraries I need to get this going ?
>
>or can I upgrade QDB ?
>
>what can be a solution to this ?
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post90356
>Jim Gilderson2011-11-30T16:21:45Zpost90361: Re: MmSetDefaultClock
http://community.qnx.com/sf/go/post90361
MMF is not normally a customer-facing API. Also, there should be no
reason to call that function. What are you trying to accomplish?
Are you using Aviage, or the Blackberry NDK?
On 11-11-30 11:12 AM, "Arun Johnson" <community-noreply@qnx.com> wrote:
>sorry,
>What I meant is I am trying to create my own graph using the library.
>that's when I got the error.
>
>Thanks,
>Arun
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post90359
>Adrian Boak(deleted)2011-11-30T16:16:10Zpost90359: Re: MmSetDefaultClock
http://community.qnx.com/sf/go/post90359
sorry,
What I meant is I am trying to create my own graph using the library.
that's when I got the error.
Thanks,
ArunArun Johnson2011-11-30T16:12:51Zpost90358: Re: MmSetDefaultClock
http://community.qnx.com/sf/go/post90358
You don't create a graph if you are using the MME. MME talks to io-media
which in turn uses MMF to play back the content. Do you have the MME
documentation?
On 11-11-30 11:06 AM, "Arun Johnson" <community-noreply@qnx.com> wrote:
>Hi,
>
>I was trying to build my own graph using MME.
>
>The function MMSetDefaultClock giving me a link error :
>
>(.text+0x3bc): undefined reference to `MmSetDefaultClock'
>
>But all other functions are getting linked !
>I am including libmmedia.so as a shared library.
>
>Can somebody help me with this ?
>
>Thanks,
>Arun
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post90357
>Adrian Boak(deleted)2011-11-30T16:09:34Zpost90357: MmSetDefaultClock
http://community.qnx.com/sf/go/post90357
Hi,
I was trying to build my own graph using MME.
The function MMSetDefaultClock giving me a link error :
(.text+0x3bc): undefined reference to `MmSetDefaultClock'
But all other functions are getting linked !
I am including libmmedia.so as a shared library.
Can somebody help me with this ?
Thanks,
ArunArun Johnson2011-11-30T16:06:33Zpost90356: QDB and SQLite
http://community.qnx.com/sf/go/post90356
Hi,
I am setting up aviage on arm target.
I am getting a conflict while setting QDB
its giving me :
qdb: QDB requires SQLite version "3.6.12", found "3.6.23.1"
I know its something to do with the some libraries. But can anybody point me the correct libraries I need to get this going ?
or can I upgrade QDB ?
what can be a solution to this ?Arun Johnson2011-11-30T15:36:35Zpost90316: Re: Regarding QNX support for FLAC Codec
http://community.qnx.com/sf/go/post90316
What QNX version and platform are you working on? We're working on the
FLAC implementation now, but the rollout of the feature depends on what
you're working with.
On 11-11-28 5:44 AM, "Suresha Iholle" <community-noreply@qnx.com> wrote:
>Hi,
>
>could you please let me know whether FLAC 1.2.1 codec support is present
>in QNX or not.
>And what we need to do if we need to support FLAC codec in QNX.
>
>Regards,
>suresha
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post90314
>Adrian Boak(deleted)2011-11-28T14:45:32Zpost90314: Regarding QNX support for FLAC Codec
http://community.qnx.com/sf/go/post90314
Hi,
could you please let me know whether FLAC 1.2.1 codec support is present in QNX or not.
And what we need to do if we need to support FLAC codec in QNX.
Regards,
sureshaSuresha Iholle2011-11-28T10:44:12Zpost90286: Re: mp4 player
http://community.qnx.com/sf/go/post90286
If you're using Aviage, use the MME APIs. You're platform will need to have a supported video decoder however.
----- Original Message -----
From: Arun Johnson [mailto:community-noreply@qnx.com]
Sent: Wednesday, November 23, 2011 12:26 PM
To: general-multimedia <post90266@community.qnx.com>
Subject: mp4 player
hi,
i want to create a mp4 player that can play H.264 video and AAC audio.
Could aviage chieve this ?
what should be the approach ?
Thanks,
Arun
_______________________________________________
General
http://community.qnx.com/sf/go/post90266Adrian Boak(deleted)2011-11-24T18:04:09Zpost90266: mp4 player
http://community.qnx.com/sf/go/post90266
hi,
i want to create a mp4 player that can play H.264 video and AAC audio.
Could aviage chieve this ?
what should be the approach ?
Thanks,
ArunArun Johnson2011-11-23T17:26:58Zpost90259: Re: building graphs
http://community.qnx.com/sf/go/post90259
Hi Adrian,
I am working on a armlev7 platform. I am trying to make an mp4 player with H.264 video and AAC audio with AV sync.
I managed to bring up io-fs-media,qdb,mcd,io-media-generic on the platform. and I was even able to use mmecli to create track sessions and play some wave files.
Now I can see an mp4_parser.so in mmedia.
1) does this parser parses mp4 container and gives video and audio streams as two seperate output channels ??
basically I have a decoder for h.264 and AAC audio.
how do I use all these components to get my player working ??
When I was building some sample applications, I saw that "MmSetDefaultClock(graph"
is not getting linked with libmmedia.so.1. Is there something missing here ??
I am suing Aviage core 1.2
I will really appreciate your help on getting my mp4 player running in QNX.
Thanks and Regards,
ArunArun Johnson2011-11-23T14:27:45Zpost90251: Re: building graphs
http://community.qnx.com/sf/go/post90251
Normally we don't recommend using MMF directly. What platform is this on and what are you trying to accomplish?
In the old framework MME us the standard user API. In the new framework we recommend using mm-renderer, flash, or html 5.
----- Original Message -----
From: Arun Johnson [mailto:community-noreply@qnx.com]
Sent: Tuesday, November 22, 2011 07:26 PM
To: general-multimedia <post90250@community.qnx.com>
Subject: building graphs
Hi,
I was trying to make a wav player by building my own graghs using the multimedia library.
the fucntion, MmAcquireOutputChannel ()
is supposed to give an ouput channel of some type from the filter returned from MmFindMediaReader(). But I can see an output channel only if i use MEDIA_TYPE_UNKNOWN.
if I proceed with this media type to build a graph with just
wav_parser and audio_writer, as I assume there is no decoder required for playing wav files It ultimately fails to create the graph.
I am able to play to file with mmecli with the intruction in the quick start guide.
does mme handles the playback in the same way ????
_______________________________________________
General
http://community.qnx.com/sf/go/post90250Adrian Boak(deleted)2011-11-23T01:03:17Zpost90250: building graphs
http://community.qnx.com/sf/go/post90250
Hi,
I was trying to make a wav player by building my own graghs using the multimedia library.
the fucntion, MmAcquireOutputChannel ()
is supposed to give an ouput channel of some type from the filter returned from MmFindMediaReader(). But I can see an output channel only if i use MEDIA_TYPE_UNKNOWN.
if I proceed with this media type to build a graph with just
wav_parser and audio_writer, as I assume there is no decoder required for playing wav files It ultimately fails to create the graph.
I am able to play to file with mmecli with the intruction in the quick start guide.
does mme handles the playback in the same way ????Arun Johnson2011-11-23T00:26:25Zpost90139: Re: armle targets
http://community.qnx.com/sf/go/post90139
Hi
I will comment on some of your points below.
gf_writer was only shipped with x86 in 1.2 as there was no available ARM
video decoder.
In general, a 3rd party video decoder must be wrapped to comply with our
Multimedia Framework.
This is not a trivial task and is typically done by QNX via custom
engineering.
There is no standard documentation on this.
I would recommend contacting your support contact if you need to pursue
this.
On 11-11-16 10:29 AM, "Arun Johnson" <community-noreply@qnx.com> wrote:
>Hi,
>I am working on using Aviage on armle target. With core package, I
>realized that there is no gf_writer.
>
>Is it possible to display video in arm target ? I have edited
>mme_data.sql to add another video output device and attached the
>zoneoutput to this device.
>
>my mme_sql is as follows:
>
>INSERT INTO outputdevices(type, permanent, name, devicepath) VALUES(1, 1,
>'default_audio', 'snd:/dev/snd/pcmPreferredp');
>INSERT INTO outputdevices(type, permanent, name, devicepath) VALUES(2, 1,
>'default_video', 'gf:0000,0000');
>INSERT INTO zones(zoneid, name) VALUES(1, 'defaultzone');
>INSERT INTO zoneoutputs(zoneid, outputdeviceid) SELECT 1, outputdeviceid
>FROM outputdevices WHERE name='default_audio';
>INSERT INTO zoneoutputs(zoneid, outputdeviceid) SELECT 1, outputdeviceid
>FROM outputdevices WHERE name='default_video';
>INSERT INTO renderers(path) VALUES('/dev/io-media');
>INSERT INTO controlcontexts(zoneid, rendid, name) VALUES( 1, 1, 'default'
>);
>
>Its giving me an error for could not attach parser while playing mp4
>video. I know that the mp4_parser is there in the correct location and it
>is liked properly.
>
>Its also giving me an error "output device type 2 not supported."
>
>Is there a way in Aviage to attach my own h.264 decoder that has DSP
>implementation ? if yes, can you point me to the right direction ?
>
>Is there any interface format to write my decoder so as to make aviage
>linked to it ? I didnt see any documentation about writing our own
>decoder
>
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post90132
>Jim Gilderson2011-11-16T20:11:44Zpost90132: armle targets
http://community.qnx.com/sf/go/post90132
Hi,
I am working on using Aviage on armle target. With core package, I realized that there is no gf_writer.
Is it possible to display video in arm target ? I have edited mme_data.sql to add another video output device and attached the zoneoutput to this device.
my mme_sql is as follows:
INSERT INTO outputdevices(type, permanent, name, devicepath) VALUES(1, 1, 'default_audio', 'snd:/dev/snd/pcmPreferredp');
INSERT INTO outputdevices(type, permanent, name, devicepath) VALUES(2, 1, 'default_video', 'gf:0000,0000');
INSERT INTO zones(zoneid, name) VALUES(1, 'defaultzone');
INSERT INTO zoneoutputs(zoneid, outputdeviceid) SELECT 1, outputdeviceid FROM outputdevices WHERE name='default_audio';
INSERT INTO zoneoutputs(zoneid, outputdeviceid) SELECT 1, outputdeviceid FROM outputdevices WHERE name='default_video';
INSERT INTO renderers(path) VALUES('/dev/io-media');
INSERT INTO controlcontexts(zoneid, rendid, name) VALUES( 1, 1, 'default' );
Its giving me an error for could not attach parser while playing mp4 video. I know that the mp4_parser is there in the correct location and it is liked properly.
Its also giving me an error "output device type 2 not supported."
Is there a way in Aviage to attach my own h.264 decoder that has DSP implementation ? if yes, can you point me to the right direction ?
Is there any interface format to write my decoder so as to make aviage linked to it ? I didnt see any documentation about writing our own decoderArun Johnson2011-11-16T15:29:12Zpost90000: Re: io-media-generic/mmf fail
http://community.qnx.com/sf/go/post90000
I tried that, but the problem was due to the absence of "libmmfilter.so.1" file in the build for the target. when i copied that and pointed that location in LD_LIBRARY_PATH. It got initializedArun Johnson2011-11-10T16:20:37Zpost89981: Re: io-media-generic/mmf fail
http://community.qnx.com/sf/go/post89981
Is the stream_reader.so DLL in the the /db/armle/lib/dll/mmedia folder?
Try to manually start io-media on the command line, but do this:
DL_DEBUG=1 io-media-generic -M mmf,dlldir=/db/armle/lib/dll/mmedia/
Setting DL_DEBUG=1 will print some extra info while loading shared
libraries that might help narrow down the issue.
Regards,
GillesGilles Roy2011-11-10T01:58:38Zpost89979: Re: Support for Hantro Video decoder
http://community.qnx.com/sf/go/post89979
No we haven't.
----- Original Message -----
From: Dennis Kellly [mailto:community-noreply@qnx.com]
Sent: Wednesday, November 09, 2011 06:00 PM
To: general-multimedia <post89978@community.qnx.com>
Subject: RE: Support for Hantro Video decoder
It is an IP block which can be licensed and added to an SOC - primarily for Flash video acceleration (I presume).
Hantro is owned by On2 Tech.
The AT91SAM9M10 includes one of their decoders. There are press releases about Freescale and Hantro but unclear which parts may have it.
-----Original Message-----
From: Adrian Boak [mailto:community-noreply@qnx.com]
Sent: Wednesday, November 09, 2011 5:56 PM
To: general-multimedia
Subject: Re: Support for Hantro Video decoder
What is the Hantro video decoder? A piece of hardware? What platform is it on?
----- Original Message -----
From: Dennis Kellly [mailto:community-noreply@qnx.com]
Sent: Wednesday, November 09, 2011 05:44 PM
To: general-multimedia <post89975@community.qnx.com>
Subject: Support for Hantro Video decoder
Has QNX ever supported any parts with the Hantro h/w video decoder units?
_______________________________________________
General
http://community.qnx.com/sf/go/post89975
_______________________________________________
General
http://community.qnx.com/sf/go/post89977
_______________________________________________
General
http://community.qnx.com/sf/go/post89978Adrian Boak(deleted)2011-11-09T23:49:22Zpost89978: RE: Support for Hantro Video decoder
http://community.qnx.com/sf/go/post89978
It is an IP block which can be licensed and added to an SOC - primarily for Flash video acceleration (I presume).
Hantro is owned by On2 Tech.
The AT91SAM9M10 includes one of their decoders. There are press releases about Freescale and Hantro but unclear which parts may have it.
-----Original Message-----
From: Adrian Boak [mailto:community-noreply@qnx.com]
Sent: Wednesday, November 09, 2011 5:56 PM
To: general-multimedia
Subject: Re: Support for Hantro Video decoder
What is the Hantro video decoder? A piece of hardware? What platform is it on?
----- Original Message -----
From: Dennis Kellly [mailto:community-noreply@qnx.com]
Sent: Wednesday, November 09, 2011 05:44 PM
To: general-multimedia <post89975@community.qnx.com>
Subject: Support for Hantro Video decoder
Has QNX ever supported any parts with the Hantro h/w video decoder units?
_______________________________________________
General
http://community.qnx.com/sf/go/post89975
_______________________________________________
General
http://community.qnx.com/sf/go/post89977Dennis Kellly2011-11-09T23:00:59Zpost89977: Re: Support for Hantro Video decoder
http://community.qnx.com/sf/go/post89977
What is the Hantro video decoder? A piece of hardware? What platform is it on?
----- Original Message -----
From: Dennis Kellly [mailto:community-noreply@qnx.com]
Sent: Wednesday, November 09, 2011 05:44 PM
To: general-multimedia <post89975@community.qnx.com>
Subject: Support for Hantro Video decoder
Has QNX ever supported any parts with the Hantro h/w video decoder units?
_______________________________________________
General
http://community.qnx.com/sf/go/post89975Adrian Boak(deleted)2011-11-09T22:55:50Zpost89975: Support for Hantro Video decoder
http://community.qnx.com/sf/go/post89975
Has QNX ever supported any parts with the Hantro h/w video decoder units?Dennis Kellly2011-11-09T22:44:04Zpost89974: io-media-generic/mmf fail
http://community.qnx.com/sf/go/post89974
Hi,
I completly swiched over to the armle core. Bit io-media-generic fails to initialize.
io-media-generic -M mmf,dlldir=/db/armle/lib/dll/mmedia/
io-media-generic/mmf: Could not load the "stream_reader" DLL
io-media-generic: Initialization of module mmf failed
dlldir has all the related .so files for it to initialize.
anyone know why this is happening ?
Thanks,
ArunArun Johnson2011-11-09T22:38:11Zpost89960: Re: io-media-generic
http://community.qnx.com/sf/go/post89960
I think you are right that this may be related to armle vs armle-v7. I
don't believe we shipped 1.2 for armle-v7. You will need to go through a
formal sales or support channel to discuss options for an armle-v7 build
of Aviage.
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2011-11-09T17:31:09Zpost89959: io-media-generic
http://community.qnx.com/sf/go/post89959
Hi,
I got QDB up and running. many thanks to all the help. It was related to the location of the libraries for qdb. It seems
to be located in the correct folder structure..Since i am using windows host and cross compiling to arm, I copied it to
a temp location. That was causing it to behave differently.
I am getting an error in io-media-generic
ldd:FATAL: Unresolved symbol "__aeabi_atexit" called from libaoi.so.1
Process 163871 (io-media-generic) exited status=1.
I was wondering if it its relate to armle Vs armle-v7...
i am using aviage core 1.2.0
I successfully setup io-fs-media,qdb and mcd running. But io-media-generic is giving me a fatal error. Is this an issue with the media core ?
Thanks,
ArunArun Johnson2011-11-09T17:17:41Zpost89956: Re: QDB - disk I/O Error
http://community.qnx.com/sf/go/post89956
HI,
I got QDB up and running. many thanks to all the help. It was related to the location of the libraries for qdb. It seems to be located in the correct folder structure..Since i am using windows host and cross compiling to arm, I copied it to a temp location. That was causing it to behave differently.
Now I am getting an error in io-media-generic
ldd:FATAL: Unresolved symbol "__aeabi_atexit" called from libaoi.so.1
Process 163871 (io-media-generic) exited status=1.
I was wondering if it its relate to armle Vs armle-v7...
i am using aviage core 1.2.0
Thanks,
ArunArun Johnson2011-11-09T16:33:33Zpost89944: Re: QDB - disk I/O Error
http://community.qnx.com/sf/go/post89944
/Fs/tmpfs/ provided by io-fs -dtmp should be fine as a filesystem to store
the databases.
Are there any other files in /fs/tmpfs/ ? Perhaps a lock file or
something similar that sqlite is honoring but that your attempt to write
to the file ignores.
Have you made any modifications to the .sql files? Initially I would be
trying this with the default files. Can you read all of the .sql files
without error (try simply to "cat" the files from the shell).
To try to narrow down the error I would first try to clear all files in
/fs/tmpfs/ (simple to do: just kill io-fs-media and re-start it), then
start with a simplified config file. Try specifying only one database
(for example, just mme_temp and not mme or mme_library) to see if qdb will
start. If this still fails you could see if adding some tracing to sqlite
will help; if a query is causing a problem then this will show the
specific query. You do this by adding arguments:
qdb -otempstore=/fs/tmpfs/,trace,profile -vvvvvv
(At least six -v's.)
Generally speaking the default configuration should "just work", as long
as all of the files are in the right places.
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2011-11-08T16:57:07Zpost89943: Re: QDB - disk I/O Error
http://community.qnx.com/sf/go/post89943
I am using :
io-fs-media -d tmp -cpages=4 -cbundles=0 before the qdb call.
this successfully creates a RAMdisk..... /fs/tmpfs.
this call is supposed to create an abstraction for full posix file system right ?
This is where I am trying to create the db.
Thanks,
ArunArun Johnson2011-11-08T16:40:15Zpost89941: Re: QDB - disk I/O Error
http://community.qnx.com/sf/go/post89941
>>>qdb: processing [mme_temp]/db/mme_temp.sql - disk I/O error
I am guessing this file is located in shared memory? If so, I suspect the failure is due to the filesystem not supporting full posix semantics.
As a quick test, try
# devb-ram ram capacity=8192
# dinit –h /dev/hd1t77 <<<< careful that /dev/hd1 is ramdisk!!!
# mount /dev/hd1t77 /tmp2
Now change the location of the file to reside under /tmp2 and see if it works.Dennis Kellly2011-11-08T16:11:37Zpost89940: Re: QDB - disk I/O Error
http://community.qnx.com/sf/go/post89940
I am using the default qdb.conf file.
[mme_temp]
Filename = /fs/tmpfs/mme_temp.db
Schema File = /db/mme_temp.sql
I am able to write to this file by myself.
I tried a different location its giving me input/output error.
I am working on armle-v7 board with aviage core 1.2.0.Arun Johnson2011-11-08T15:42:53Zpost89939: Re: QDB - disk I/O Error
http://community.qnx.com/sf/go/post89939
Qdb uses libsqlite3 for database operations. It looks like sqlite3
encountered an IO error while trying to write (10 == SQLITE_IOERR, 778 ==
SQLITE_IOERR_WRITE). I would check your qdb.cfg file to see where
/db/mme_temp.sql is meant to be written (the Filename option for this
database) and try to write this file yourself. You could try specifying a
different path to write Filename to.
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2011-11-08T15:01:07Zpost89937: QDB - disk I/O Error
http://community.qnx.com/sf/go/post89937
Hi,
I was trying to start up QDB with after io-fs-media call.
qdb -c /db/qdb.cfg -vvvvvvvV -Otempstore=/fs/tmpfs -Rset
its giving the following error :
QDB: No script registered for handling corrupt database.
QDB: exec: rc 10, ext 778
qdb: processing [mme_temp]/db/mme_temp.sql - disk I/O error
Its unable to start QDB, can anyone tell me why this is happening ?
Thanks,
ArunArun Johnson2011-11-08T14:39:40Zpost89315: Re: Software to Create a video recording file for QNX
http://community.qnx.com/sf/go/post89315
I don't think we have anything that can do what you're looking for. The
only way you may be able to optimize would be to capture the video
directly within your VM software (if this is possible), as opposed to
capturing a Phindows connection to the VM. I don't imagine this would be
significantly different.
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2011-10-11T21:04:53Zpost89307: Re: Software to Create a video recording file for QNX
http://community.qnx.com/sf/go/post89307
Here is the situation that I am looking to.
I have a QNX Virtual Machine that is running a software program with a user interface. I want to be able to record everything that happens on the user interface. Right now, I have to do this manually using a Phindows session and a windows program that allows me to capture the screen and convert to video. I would like to automate this so that I can turn the file into a video file. Ideally I would like to create an wmv or something that can be opened easily, but really any format will work as long as I can convert it over.Jeff Tippey2011-10-11T16:11:03Zpost89305: Re: Software to Create a video recording file for QNX
http://community.qnx.com/sf/go/post89305
Are you intending to record a tutorial type video? Or do you want the
end-user of your QNX-based product to be able to record their own videos?
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2011-10-11T15:49:05Zpost89296: Re: Software to Create a video recording file for QNX
http://community.qnx.com/sf/go/post89296
Thank you guys for taking the time to respond. One quick add on, say for instance that I have a virtual machine that is the QNX machine. Now I am running completely in software. The issue is that I want to record what would be showing on the display and turn that into video that I can easily open using Windows Media Player or something like that. Is there any easy way to accomplish this? Would this take the hardware component out of the mix?Jeff Tippey2011-10-11T12:42:17Zpost89171: Re: Software to Create a video recording file for QNX
http://community.qnx.com/sf/go/post89171
QNX doesn't have an "off the shelf" solution for this. Normally this kind of thing is also highly dependent on the specific hardware that is doing the video recording. Some video hardware can feed you the stream already encoded in a compressed format.
Regards,
Gilles
Sent from my Blackberry
----- Original Message -----
From: Jeff Tippey [mailto:community-noreply@qnx.com]
Sent: Thursday, September 29, 2011 04:08 PM
To: general-multimedia <post89166@community.qnx.com>
Subject: Software to Create a video recording file for QNX
I am sorry if this comes across as a dumb question. I am looking for a piece of software that can create a video recording file (ie an MPEG or some video standard that I can play on any OS). I have been told by a couple of people that nothing like this exists for QNX. I am having a hard time believing this, does anything like this exist?
Thank you for your help
_______________________________________________
General
http://community.qnx.com/sf/go/post89166Gilles Roy2011-09-29T22:28:06Zpost89168: Re: Software to Create a video recording file for QNX
http://community.qnx.com/sf/go/post89168
Yes, it exists. Show the BlackBerry Playbook to anyone who does not
believe: it's running on QNX and can record full size 1080p H264 video
with no issues.
On 11-09-29 4:08 PM, "Jeff Tippey" <community-noreply@qnx.com> wrote:
>I am sorry if this comes across as a dumb question. I am looking for a
>piece of software that can create a video recording file (ie an MPEG or
>some video standard that I can play on any OS). I have been told by a
>couple of people that nothing like this exists for QNX. I am having a
>hard time believing this, does anything like this exist?
>
>Thank you for your help
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post89166
>Mate Szarvas2011-09-29T20:46:55Zpost89166: Software to Create a video recording file for QNX
http://community.qnx.com/sf/go/post89166
I am sorry if this comes across as a dumb question. I am looking for a piece of software that can create a video recording file (ie an MPEG or some video standard that I can play on any OS). I have been told by a couple of people that nothing like this exists for QNX. I am having a hard time believing this, does anything like this exist?
Thank you for your helpJeff Tippey2011-09-29T20:08:18Zpost87691: Re: snd_pvm_open_preferred - preferences file.
http://community.qnx.com/sf/go/post87691
Ryan:
Got it!
This works as well.
pcmPreferredc 1 0
pcmPreferredp 1 0
Thanks, excellent information.Andy Rhind2011-07-29T13:40:55Zpost87662: Re: snd_pvm_open_preferred - preferences file.
http://community.qnx.com/sf/go/post87662
It would look something like this:
> # cat /etc/system/config/audio/preferences
> pcmPreferredp "Audiopci 1371" 1
>
Preferred device name (you can set preferred playback or capture
device), the device name (if you have the audio driver source you can
lookup the function call to ado_card_set_shortname(); if you don't, you
should be able to get this by calling snd_pcm_info() and looking at
snd_pcm_info_t.name (this is the longname, not the shortname, but should
still work). The last number is the device number for that card.
With the above config my /dev/snd/ looks like this:
-rw-rw-rw- 1 root root 0 Jul 28 17:31 pcmC0D0p
-rw-rw-rw- 1 root root 0 Jul 28 17:31 pcmC0D1p
lrw-rw-rw- 1 root root 0 Jul 28 17:31 pcmPreferredp
-> pcmC0D1p
If I swap the last 1 for 0, pcmPreferredp points to pcmC0D0p.
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2011-07-28T21:35:36Zpost87627: Re: snd_pvm_open_preferred - preferences file.
http://community.qnx.com/sf/go/post87627
Update:
After reading some of the Linux ALSA documentation we tried to create/edit the '/etc/system/config/audio/preferences' file and enter 'hw:0,1' in the hope that this would tell svn_pvm_open_preferred () to open card 0, device 1. Sadly this didnt work.
Thanks,
AndyAndy Rhind2011-07-27T14:57:42Zpost87605: snd_pvm_open_preferred - preferences file.
http://community.qnx.com/sf/go/post87605
Hi:
A question from the docs :
This page
http://www.qnx.com/developers/docs/6.5.0/index.jsp?topic=/com.qnx.doc.neutrino_audio/libs/snd_pcm_open_preferred.html
mentions how the function opens this file "/etc/system/config/audio/preferences" to access the preferences when choosing the audio device to open.
We wish to use just those preferences. But a sample of the file cant be found in QNX 6.4.1 or 6.5 . We feel that it may just be a matter of creating the file and plugging in the right values. If so - what format is used to set the desired values?
Thanks,
AndyAndy Rhind2011-07-26T13:44:44Zpost87473: Video file types that qnx.media.MediaPlayer support?
http://community.qnx.com/sf/go/post87473
I want to use qnx.media.MediaPlayer to play .flv or .mov files, but no luck. However the same code can play .mp4 files without any problem.
I want to use .flv or .mov files because they support alpha channel. So my question is: what format of video files does MediaPlayer support? Does it support any video format that support alpha channel?Jennifer Li(deleted)2011-07-20T15:49:24Zpost86717: Cookie support with qnx MediaPlayer
http://community.qnx.com/sf/go/post86717
We have a requirement that we need to send a cookie along with our request for media, is there a way to either add cookies or for the qnx player to pick up the cookies that the other actionscript code is using for it's communication with the server?
Thanks
JeremyJeremy Barnet(deleted)2011-06-20T13:52:45Zpost83883: Re: RE: Audio capture on the 293e (82801IBM)
http://community.qnx.com/sf/go/post83883
> Can you try this one and see if you can capture via microphone?
>
> Johnny
Used microphone via MIC IN with the new dll, still nothing.
I attached the startup, record and playback slog outputs for your reference.
The same with the previous DLL you gave me, the Audio Mixer photon app shows only Input Gain having slider controls under Record Settings. I took a screenshot of this one too and it's also in the attached zip file.Cyril Keith Flores(deleted)2011-03-10T02:10:17Zpost83869: Re: RE: Audio capture on the 293e (82801IBM)
http://community.qnx.com/sf/go/post83869
Can you try this one and see if you can capture via microphone?
JohnnyJohnny Lin(deleted)2011-03-09T15:47:35Zpost83843: Re: Audio capture on the 293e (82801IBM)
http://community.qnx.com/sf/go/post83843
> Can you plug the output of a CD player to your MIC IN and maximise its output
> and see if you can capture its audio?
I did not maximize anything but I was able to capture audio via MIC IN using 3.5mm-to-3.5mm against an iPhone playing an mp3.
I attached the slog output, the bigger file is when I captured and played back successfully both via LINE IN and MIC IN through the iPhone. The smaller one is capture and playback using just the a regular microphone. I have not used any other microphone unit yet but this one works in a laptop running Windows.Cyril Keith Flores(deleted)2011-03-09T05:40:18Zpost83838: Re: RE: Audio capture on the 293e (82801IBM)
http://community.qnx.com/sf/go/post83838
Here is the result of the corrected io-audio parameter sequencing.Cyril Keith Flores(deleted)2011-03-09T02:10:45Zpost83815: RE: Audio capture on the 293e (82801IBM)
http://community.qnx.com/sf/go/post83815
Sorry it's my mistake. Should start the driver as:
io-audio -l 0x7fffffff -d intel_hda
Note the "-l" is the lower case of "L".
Johnny
-----Original Message-----
From: Cyril Keith Flores [mailto:community-noreply@qnx.com]
Sent: Tue 3/8/2011 2:10 AM
To: general-multimedia
Subject: Re: Audio capture on the 293e (82801IBM)
Slog doesn't say much.
Time Sev Major Minor Args
Jan 11 20:46:20 1 7 0 driver_go()
Attached screenshot of the slay & re-run.
I'm still on the recording-from-player.
_______________________________________________
General
http://community.qnx.com/sf/go/post83812Johnny Lin(deleted)2011-03-08T12:54:24Zpost83814: Re: Audio capture on the 293e (82801IBM)
http://community.qnx.com/sf/go/post83814
A little update. I didn't execute anything since but I just did an sloginfo a few minutes after and I got some more.
Time Sev Major Minor Args
Jan 11 20:46:20 1 7 0 driver_go()
Jan 11 20:58:15 1 7 0 IO_OPEN mode=0 oflag=104201 []
Jan 11 20:58:15 1 7 0 IO_CLOSE_DUP [/dev/snd] pid 65551
Jan 11 20:58:15 1 7 0 IO_CLOSE [/dev/snd]Cyril Keith Flores(deleted)2011-03-08T07:41:31Zpost83812: Re: Audio capture on the 293e (82801IBM)
http://community.qnx.com/sf/go/post83812
Slog doesn't say much.
Time Sev Major Minor Args
Jan 11 20:46:20 1 7 0 driver_go()
Attached screenshot of the slay & re-run.
I'm still on the recording-from-player.Cyril Keith Flores(deleted)2011-03-08T07:10:49Zpost83760: Re: Audio capture on the 293e (82801IBM)
http://community.qnx.com/sf/go/post83760
That looks good. Can you do the following:
1. slay io-audio
2. start the io-audio as: "io-audio -d intel_hda -l 0x7ffffff -vvv"
3. run: "sloginfo -c > /tmp/hda.log"
4. post the hda.log
BTW, have you tried to input an audio from a CD/IPOD/MP3 or even your
laptop's headphone output and see if your MIC IN can capture?
On Thu, 2011-03-03 at 22:47 -0500, Cyril Keith Flores wrote:
> By the way, this is what it looks like after I tried using your new
> DLL.
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post83735
>
>Johnny Lin(deleted)2011-03-04T22:02:34Zpost83735: Re: Audio capture on the 293e (82801IBM)
http://community.qnx.com/sf/go/post83735
By the way, this is what it looks like after I tried using your new DLL.Cyril Keith Flores(deleted)2011-03-04T03:47:53Zpost83720: Re: Audio capture on the 293e (82801IBM)
http://community.qnx.com/sf/go/post83720
Can you plug the output of a CD player to your MIC IN and maximise its output and see if you can capture its audio?Johnny Lin(deleted)2011-03-03T15:01:01Zpost83709: Re: Audio capture on the 293e (82801IBM)
http://community.qnx.com/sf/go/post83709
Hi Johnny,
I tried the new mixer DLL, I can see that there is already an Input Gain control on the mixer program but I still am not able to capture audio. There is nothing on the sloginfo too.
The mic I am using works on my laptop under Windows XP. I am also looking into whether the connectors I am using the mic on are also at fault.
Thanks for that file, how did you obtain it?Cyril Keith Flores(deleted)2011-03-03T06:53:44Zpost83701: Re: Audio capture on the 293e (82801IBM)
http://community.qnx.com/sf/go/post83701
Can you try the attached DLL deva-mixer-hda.so? Just find this file in your system, make sure keep a copy for the old deva-mixer-hda.so, replace the old one in your system, and restart the system.
Best regards,
JohnnyJohnny Lin(deleted)2011-03-02T21:46:04Zpost83671: Re: Audio capture on the 293e (82801IBM)
http://community.qnx.com/sf/go/post83671
Also, Input Gain on the Audio Mixer doesn't show anything. (refer to attached screenshot)
@Johnny,
Yes, audio playback is working normally.Cyril Keith Flores(deleted)2011-03-02T07:27:59Zpost83620: Re: Low volume with Intel HDA and ALC888 [QNX 6.4.1]
http://community.qnx.com/sf/go/post83620
Can you try "mix_ctl -d" to see if all the amplifiers are maximised?
Thanks and best regards,
JohnnyJohnny Lin(deleted)2011-03-01T15:03:40Zpost83619: Re: Audio capture on the 293e (82801IBM)
http://community.qnx.com/sf/go/post83619
Hi,
Can you playback other audio?
Thanks and best regards,
Johnny
*********************************************
Hello,
I am having issues capturing audio on the said chip. waverec shows it is recording audio but there is nothing on the
playback of the recorded file.
I used io-audio -d intel_hda on 6.5Johnny Lin(deleted)2011-03-01T15:01:21Zpost83609: Low volume with Intel HDA and ALC888 [QNX 6.4.1]
http://community.qnx.com/sf/go/post83609
Hi all,
I am using a board with Intel HDA and Realtek ALC888 codec under QNX 6.4.1
It works, but the volume is much lower than I expect it to be.
When driving the same PC with a Windows, I can turn up the volume to a higher level than QNX allows me to do.
I have read the manuals about io-audio and deva-ctrl-intel-hda, but I'm not able to find a hint what to try.
I have turned up all channels (although the PC only provides the Stereo Front as a jack), but I can't reach the same volume as with Windows.
Does anybody have an idea what to try?
Regards, ChristianChristian Reinecke2011-03-01T07:36:44Zpost83562: Re: MME related processes can not be slayed or killed after MME crashed
http://community.qnx.com/sf/go/post83562
> b. The pidin output after performing slays, and from the outpout, we can see
> that the process io-media-generic 131097 and mme-generic 131098 still remain
> running on system after slay:
> # slay -fv io-fs-media qdb io-media-generic mme-generic mcd
> slay: usr/sbin/io-fs-media 126998 on (tty not known)
> slay: usr/sbin/io-fs-media 131099 on (tty not known)
> slay: usr/sbin/qdb 131095 on (tty not known)
> slay: usr/sbin/io-media-generic 131097 on (tty not known)
> slay: usr/sbin/mme-generic 131098 on (tty not known)
> slay: bin/mcd 131096 on (tty not known)
Have you tried using "slay -9f ... " ? Usually works for hard-to-slay processes...Cyril Keith Flores(deleted)2011-02-28T07:41:57Zpost83516: Re: Audio capture on the 293e (82801IBM)
http://community.qnx.com/sf/go/post83516
I'm not sure that any audio driver developers are monitoring this forum.
I would suggest contacting QNX support for assistance with this.
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2011-02-25T16:05:56Zpost83481: Audio capture on the 293e (82801IBM)
http://community.qnx.com/sf/go/post83481
Hello,
I am having issues capturing audio on the said chip. waverec shows it is recording audio but there is nothing on the playback of the recorded file.
I used io-audio -d intel_hda on 6.5Cyril Keith Flores(deleted)2011-02-25T02:48:28Zpost79031: Re: Comprehensive List of codecs/formats supported by MME
http://community.qnx.com/sf/go/post79031
Rumor has it that there *might* be such a codec available for a specific platform. As Dan indicates, you'll need to contact QNX professional services to get a definitive answer. I'm still waiting on mine.Glenn Schmottlach2010-12-16T16:21:56Zpost78994: Re: Comprehensive List of codecs/formats supported by MME
http://community.qnx.com/sf/go/post78994
You should be contacting your QNX support contact for help with this
type of issue.
> ------------------------------------------------------------------------
>
> Michael Briggs <mailto:community-noreply@qnx.com>
> December 16, 2010 9:55 AM
>
>
> Glenn -
>
> Did you ever get an answer to this request? I too am interested in
> AAC+ support.
>
> - Mike Briggs
>Dan Cardamore(deleted)2010-12-16T15:03:16Zpost78987: RE: Comprehensive List of codecs/formats supported by MME
http://community.qnx.com/sf/go/post78987
Glenn -
Did you ever get an answer to this request? I too am interested in AAC+ support.
- Mike Briggs
-----Original Message-----
From: Glenn Schmottlach [mailto:community-noreply@qnx.com]
Sent: Monday, December 13, 2010 6:15 PM
To: general-multimedia
Subject: Comprehensive List of codecs/formats supported by MME
Is there a comprehensive list of codecs (particularly the audio variety) that MME supports including any formats (e.g. data-rates, containers, etc...). I can't seem to deduce this information from the release notes.
I am particularly interested in AAC+ support which (it appears) may not be supported on my platform:
# use -i mme-generic
NAME=mme-generic
DESCRIPTION=MME Generic build
DATE=2010/10/15-13:22:53-EDT
STATE=stable
HOST=ccbuild
USER=builder
VERSION=20.26.1
TAGID=3579@384818
# use -i io-media-generic
NAME=io-media-generic
DESCRIPTION=Generic io-media system
DATE=2010/10/15-13:15:43-EDT
STATE=stable
HOST=ccbuild
USER=builder
VERSION=20.26.1
TAGID=3579@384818
Thanks . . .
_______________________________________________
General
http://community.qnx.com/sf/go/post78557Michael Briggs2010-12-16T14:55:47Zpost78557: Comprehensive List of codecs/formats supported by MME
http://community.qnx.com/sf/go/post78557
Is there a comprehensive list of codecs (particularly the audio variety) that MME supports including any formats (e.g. data-rates, containers, etc...). I can't seem to deduce this information from the release notes.
I am particularly interested in AAC+ support which (it appears) may not be supported on my platform:
# use -i mme-generic
NAME=mme-generic
DESCRIPTION=MME Generic build
DATE=2010/10/15-13:22:53-EDT
STATE=stable
HOST=ccbuild
USER=builder
VERSION=20.26.1
TAGID=3579@384818
# use -i io-media-generic
NAME=io-media-generic
DESCRIPTION=Generic io-media system
DATE=2010/10/15-13:15:43-EDT
STATE=stable
HOST=ccbuild
USER=builder
VERSION=20.26.1
TAGID=3579@384818
Thanks . . .Glenn Schmottlach2010-12-13T23:14:35Zpost75588: About the cpu usage of io-media-generic and io-audio while playing mp3 tracks
http://community.qnx.com/sf/go/post75588
Hi,
Just have an general enquiry about the cpu usage of io-media-generic and io-audio processes. During playback of a mp3 track, it has been observed by hogs command that io-media-generic process is consuming about 22% cpu time while io-audio is about 8% cpu time. Not sure whether the cpu consumption of these processes are normal, and is there a way to reduce the cpu usage of them, thanks.
(The mp3 track is being played on a 400MHz ARM 11 platform with Aviage 1.2 via USB)
Regards,
ChrisChris Li(deleted)2010-11-22T23:39:10Zpost70220: facing issues with launching qnx screen
http://community.qnx.com/sf/go/post70220
Hello,
I am trying to integrate Adobe Air on my target(omap3730).
Looks like qnx screen is required to run the Adobe Air.
When i run the screen , i am getting the following error of unresolved symbols:
unknown symbol: __khrGetDisplayConfigValue
unknown symbol: __khrEnumerateDisplays
unknown symbol: __khrOpenWinmgrConf
unknown symbol: wfdWaitForVSyncQNX
ldd:FATAL: Could not resolve all symbols
Any help on this will be great.
Thanks,
Chiranjeevichiranjeevi kinnera2010-10-12T08:16:06Zpost66272: Couldn't create prefetch mutex. 16
http://community.qnx.com/sf/go/post66272
Hello all!
when I play a mp3 file and do seektotime near to the end , I control to play the other mp3 file immediately.As a result ,it tips the errror: Couldn't create prefetch mutex. 16.
IN the config file of io-media-generic.cfg, I config all the prefetch value =2.
the error log is as follow,please give me some advices,thanks!
io-media-generic/aoi: Fraunhofer MP3 Decoder:->got a flush.
io-media-generic/mmf: Couldn't lock mutex, prefetch event lost.
io-media-generic/aoi: Fraunhofer MP3 Decoder:->got a flush.
io-media-generic/mmf: Couldn't lock mutex, prefetch event lost.
io-media-generic/trackplayer: Skipping video subgraph because there is no video device specified.
io-media-generic/mmf: Configuring the queue for -1 bytes, lw = 0, hw = 0.
io-media-generic/aoi: mpega_parser->ParseID3v2_3or4 couldn't parse the Comment field
io-media-generic/trackplayer: Skipping video subgraph because there is no device specified.
io-media-generic/mmf: Configuring the queue for 241500 bytes, lw = 48300, hw = 193200.
io-media-generic/trackplayer: Couldn't load the xing_mpega_decoder filter (based on the decoder tag), mmerr=4046
io-media-generic/mmf: Configuring the queue for 176400 bytes, lw = 17640, hw = 158760.
io-media-generic/aoi: Fraunhofer MP3 Decoder:->QueryOutputFormats 'AWAR', 44100x16 (1 x 304128bytes)
io-media-generic/aoi: audio_writer using output device: '/dev/snd/pcmPreferredp'
io-media-generic/aoi: audio_writer asking for Signed 16-bit Little Endian, 1..2x17640B frags, 44100Hz, bps=4, 2ch
io-media-generic/aoi: audio_writer settings: Signed 16-bit Little Endian, 3x4096B frags, 44100Hz, bps=4, 2ch, Q time 69ms
io-media-generic/aoi: audio_writer PGA_StreamerCreate() adjusting chunk_size from 17640bytes to 20480bytes
io-media-generic/aoi: audio_writer using mixer device '/dev/snd/mixerC0D0'
io-media-generic/aoi: AudioWriterTask() adjusting chunk_size from 20480bytes to 20480bytes
io-media-generic/aoi: Fraunhofer MP3 Decoder:->SetOutputFormat 'AWAR', 44100x16bits
io-media-generic/trackplayer: Skipping subgraph 1 because there is no device specified.
io-media-generic/mmf: Couldn't create prefetch mutex. 16
io-media-generic/trackplayer: Couldn't set up prefetchingKailen High2010-09-08T10:42:19Zpost66141: Re: QDB Input/Output Error
http://community.qnx.com/sf/go/post66141
This bug is old (2006/2007) all Sqlite libraries used by QNX should have the
fix.
I think we would have to see the QDB logs to get more information. Simply
the output of sloginfo might help, but even better would be if you started
QDB with -o profile -vvvvvv (among the other options). Then in a telnet
window start sloginfo -w (log the output) and then reproduce your issue.
Post the output of sloginfo afterwards.
Regards,
Gilles
On 10-09-07 10:58 AM, "Tysen Moore" <community-noreply@qnx.com> wrote:
> I'm seeing some errors when doing simple QDB requests. I am seeing
> ³Input/Output error², code 5. This is a simple database with a simple query.
> I¹ve read from the QDB documentation that these are actually SQLite error
> messages coming from QDB. I¹ve also seen that a bug exists in SQLite which
> can erroneously cause this error: https://issues.rpath.com/browse/RPL-1729. I
> was wondering if anyone had more information on the possible cause for this
> error? Also, what version of SQLite does QDB use? This problem is creating a
> lot of problems because critical data is not reliably returned from QDB. Any
> added information you could give would be much appreciated. As always thanks
> for the time and help.
>
> The Query made is similar to:
> SELECT value FROM keyvalueTbl WHERE key = 'CurrentStr';
>
> The database is configured as:
> [keyvalue]
> Filename = /fs/etfs/usr/share/misc/keyvalue
> Base Schema = /etc/keyvalue.sql
> Data Schema = /etc/keyvalue_data.sql
> Compression = bzip
>
> # use -i qdb
> NAME=qdb
> DESCRIPTION=QNX SQL Database Server
> DATE=2010/04/26-18:05:44-EDT
> STATE=stable
> HOST=spare1
> USER=builder
> VERSION=20.21
> TAGID=3336@295193
>
> # use -i /usr/lib/libsqlite3.so.1
> NAME=libsqlite3.so
> DESCRIPTION=SQLite Library
> DATE=2010/04/26-15:51:08-EDT
> STATE=stable
> HOST=spare1
> USER=builder
> VERSION=20.21
> TAGID=3336@295193
>
> # use -i /usr/lib/libsqlite3.so
> NAME=libsqlite3.so
> DESCRIPTION=SQLite Library
> DATE=2010/04/26-15:51:08-EDT
> STATE=stable
> HOST=spare1
> USER=builder
> VERSION=20.21
> TAGID=3336@295193
>
_______________________________________________
General
http://community.
> qnx.com/sf/go/post66140Gilles Roy2010-09-07T15:11:10Zpost66140: QDB Input/Output Error
http://community.qnx.com/sf/go/post66140
I'm seeing some errors when doing simple QDB requests. I am seeing “Input/Output error”, code 5. This is a simple database with a simple query. I’ve read from the QDB documentation that these are actually SQLite error messages coming from QDB. I’ve also seen that a bug exists in SQLite which can erroneously cause this error: https://issues.rpath.com/browse/RPL-1729. I was wondering if anyone had more information on the possible cause for this error? Also, what version of SQLite does QDB use? This problem is creating a lot of problems because critical data is not reliably returned from QDB. Any added information you could give would be much appreciated. As always thanks for the time and help.
The Query made is similar to:
SELECT value FROM keyvalueTbl WHERE key = 'CurrentStr';
The database is configured as:
[keyvalue]
Filename = /fs/etfs/usr/share/misc/keyvalue
Base Schema = /etc/keyvalue.sql
Data Schema = /etc/keyvalue_data.sql
Compression = bzip
# use -i qdb
NAME=qdb
DESCRIPTION=QNX SQL Database Server
DATE=2010/04/26-18:05:44-EDT
STATE=stable
HOST=spare1
USER=builder
VERSION=20.21
TAGID=3336@295193
# use -i /usr/lib/libsqlite3.so.1
NAME=libsqlite3.so
DESCRIPTION=SQLite Library
DATE=2010/04/26-15:51:08-EDT
STATE=stable
HOST=spare1
USER=builder
VERSION=20.21
TAGID=3336@295193
# use -i /usr/lib/libsqlite3.so
NAME=libsqlite3.so
DESCRIPTION=SQLite Library
DATE=2010/04/26-15:51:08-EDT
STATE=stable
HOST=spare1
USER=builder
VERSION=20.21
TAGID=3336@295193Tysen Moore2010-09-07T14:58:32Zpost64602: Re: RE: RE: RE: How to display the Artwork image in the touchscreen
http://community.qnx.com/sf/go/post64602
Nah...Not mad.
Just figure if i'm gonna take the time to do some testing like this, might as well generate some semi-formal documentation.Michael Briggs2010-08-26T15:50:03Zpost64563: RE: RE: RE: How to display the Artwork image in the touchscreen
http://community.qnx.com/sf/go/post64563
Now I wonder if you are serious or got mad and ironic. Thanks if
serious and sorry if mad.
--
Mate
-----Original Message-----
From: Michael Briggs [mailto:community-noreply@qnx.com]
Sent: August 26, 2010 10:43 PM
To: general-multimedia
Subject: Re: RE: RE: How to display the Artwork image in the touchscreen
As soon as I can get some measureable information, I'll write something
up, white paper style.
_______________________________________________
General
http://community.qnx.com/sf/go/post64535Mate Szarvas2010-08-26T14:19:00Zpost64535: Re: RE: RE: How to display the Artwork image in the touchscreen
http://community.qnx.com/sf/go/post64535
As soon as I can get some measureable information, I'll write something up, white paper style.Michael Briggs2010-08-26T13:43:24Zpost64532: RE: RE: How to display the Artwork image in the touchscreen
http://community.qnx.com/sf/go/post64532
Appreciate if you can share your findings about 3rd pty libs, especially
if you find something that can resize JPEG-s measureably faster than QNX
img lib : )
--
Mate
-----Original Message-----
From: Michael Briggs [mailto:community-noreply@qnx.com]
Sent: August 26, 2010 10:37 PM
To: general-multimedia
Subject: Re: RE: How to display the Artwork image in the touchscreen
Yeah, we maintain a rolling 4 image "buffer" of re-scaled images.
We're also investigating using QNX 6.5.x w/ the ARM v7 (NEON)
instruction set to get some hardware optimization.
Another option we're considering is using a 3rd party image library
instead of the QNX Img library.
I think one of the reasons for the big time jump in the 10MB+ JPEGs is
memory paging.
_______________________________________________
General
http://community.qnx.com/sf/go/post64528Mate Szarvas2010-08-26T13:40:44Zpost64528: Re: RE: How to display the Artwork image in the touchscreen
http://community.qnx.com/sf/go/post64528
Yeah, we maintain a rolling 4 image "buffer" of re-scaled images.
We're also investigating using QNX 6.5.x w/ the ARM v7 (NEON) instruction set to get some hardware optimization.
Another option we're considering is using a 3rd party image library instead of the QNX Img library.
I think one of the reasons for the big time jump in the 10MB+ JPEGs is memory paging.Michael Briggs2010-08-26T13:36:33Zpost64516: RE: How to display the Artwork image in the touchscreen
http://community.qnx.com/sf/go/post64516
You may consider maintaining a cache of the rescaled images in case the
user also has the opportunity to navigate. Will not help the first
time, and 5+ seconds is a real pain, but at least helps the second time
on.
--
Mate
-----Original Message-----
From: Michael Briggs [mailto:community-noreply@qnx.com]
Sent: August 26, 2010 9:45 PM
To: general-multimedia
Subject: Re: How to display the Artwork image in the touchscreen
Yeah.
We have a requirement to show a slide show of user pictures from USB
stick.
Makes for a fun headache.
I was just trying to provide a head's up for dealing with large /
non-pre scaled images inside flash.
_______________________________________________
General
http://community.qnx.com/sf/go/post64513Mate Szarvas2010-08-26T12:59:55Zpost64513: Re: How to display the Artwork image in the touchscreen
http://community.qnx.com/sf/go/post64513
Yeah.
We have a requirement to show a slide show of user pictures from USB stick.
Makes for a fun headache.
I was just trying to provide a head's up for dealing with large / non-pre scaled images inside flash.Michael Briggs2010-08-26T12:44:33Zpost64495: About playing video
http://community.qnx.com/sf/go/post64495
About video decoder in mme
Hello everyone!
I want to known if the mme spports video decoder based on armle(mx35) and qnx640?
In order to play a mp4 video file, I plan to write a h264 decoder filter,and do the work of h264 codec migrated.
Please give me some advices, is it possible to play the video files for my plan?
Otherwise, in the release of qnx car project,I can find ffmpeg_decoder.so, is it for the video decoded? and in
this case,what video formats does it supported?
Thanks very much for your reply solving my issue.Xiaolong Zhang2010-08-26T07:54:57Zpost64486: Re: How to display the Artwork image in the touchscreen
http://community.qnx.com/sf/go/post64486
On 10-08-25 4:48 PM, "Michael Briggs" <community-noreply@qnx.com> wrote:
> communication and QNX's Img library for manipulations. It ain't quick on our
> platform, but it does get the job done. We're seeing ~5.5 seconds to scale a
> ~6mb JPEG image down to ~400x200 and >25seconds to scale down a 12mbJPEG
> image. We're running QNX 6.4.1 here.
Multimedia images (i.e. embedded MP3 cover art or such) usually isn't this
large. I suppose your application is not specific to cover art pulled from
files?
Regards,
GillesGilles Roy2010-08-26T02:55:09Zpost64454: Re: How to display the Artwork image in the touchscreen
http://community.qnx.com/sf/go/post64454
Just as a head's up, Flash's image scaling capability is.....poor. Yes, it can do it, but you won't be happy with the performance if your source image is bigger than your viewing screen (or image object).
I just finished writing an image scaling library that uses DBUS for communication and QNX's Img library for manipulations. It ain't quick on our platform, but it does get the job done. We're seeing ~5.5 seconds to scale a ~6mb JPEG image down to ~400x200 and >25seconds to scale down a 12mbJPEG image. We're running QNX 6.4.1 here.
So, while yes, Flash can do it, if you're not dealing with pre-scaled images, you'll want to find a way to pre-scale them before ya get the pictures into flash.
- Mike BriggsMichael Briggs2010-08-25T20:48:06Zpost64447: Re: How to display the Artwork image in the touchscreen
http://community.qnx.com/sf/go/post64447
On 10-08-24 6:28 AM, "Kailen High" <community-noreply@qnx.com> wrote:
> Thirdly, how can I display the image(in the tmpfs) in the touchscreen,
> through flash? or other methods? thaks very
> much!
I don't know if any flash programmers are monitoring this forum. If you are
using flash, it has all of the required decoders for the various image
formats, so it should be fairly easy to make it display the image, I just
don't know how to do so. It is very dependant on what your HMI is being
built on.
GillesGilles Roy2010-08-25T20:24:38Zpost64040: How to display the Artwork image in the touchscreen
http://community.qnx.com/sf/go/post64040
Hi all!
I want to display the artwork image by the touchscreen.
Firstly,I use the function (metadata_image_load() and others) to load the mp3 image to the tmpfs.
Secondly,when I receive the msg(MME_EVENT_METADATA_IMAGE and so on) ,I can gained the image info,please see the log
as follow.
Thirdly, how can I display the image(in the tmpfs) in the touchscreen, through flash? or other methods? thaks very
much!
the log is as follow:
mme_play(): success
Ply status thread received MME_EVENT_TRACKCHANGE event
the current id is:2
MMe MME_TRKCHANGE AM_SendToApp ok
Created metadata session 1
Get currentinfo successfully
Receive NOWPLAYING_METADATA,begin parse the songInfo
the msid2 is 1
,the fid2 is 0
qdb_statement(): success
The clumns is 7
The rows is 1
The song info is filename:88.mp3
; songtitle:
; songartist:
; songalbum:Myself
;songgenre:
; songyear:2010
;songsize:7946231
;songduration :198220
;HMI_MMEPLAYINFO AM_SendToApp ok
PLAYSTATESPEED(2,1000)
Receiving asynchronous manner an event
MME_EVENT_METADATA_INFO(RID=1 error=0 len=457
xmlbuf=<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<container type="file">
<track index="0">
<audio>
<stream index="0">
<common duration="197785" title="鍗虫椂鐢熸晥" artist="钄′緷鏋?" album="Myself" year="2010" discnumber="0"
tracknumber="15"/>
</stream>
</audio>
<images>
<image index="0" loadable="true">
<format size="16153" mimetype="image/jpeg" description="Front cover"/>
</image>
</images>
</track>
</container>
tmpfile=/fs/tmpfs/AAA397325)
url=0,sync_mode=32
IRID=2
12
Metadata received MME_EVENT_METADATA_IMAGE event
Successful image
MME_EVENT_METADATA_IMAGE(RID=2 error=0 len=32 URL=/fs/tmpfs/imagecache/1/CAA331806)Kailen High2010-08-24T10:28:29Zpost63255: Re: How to set the fid in different msid
http://community.qnx.com/sf/go/post63255
Hi all!
I known that all the media files fid is uniqe,they can not be changed.I have to query the library to get my result through limit.
Now,I want to display the album art in the toutchscreen.
Firstly,how can I associate the media file with the specified jpg? I located the media files in path of media/drive,the album ipg on the path of media/artwork.
Secondly,in order to display the album ipg,how can I get the metadata of the jig?
thanks very much!Kailen High2010-08-17T14:39:41Zpost63077: Re: How to set the fid in different msid
http://community.qnx.com/sf/go/post63077
Tony's right. You can filter the results from your query on the library
table to limit your selection to a specific artist, mediastore, etc.
You shouldn't consider the fid to be the offset. If you run the same
query you should associate offset with the fid yourself. You'll see the
"row number" if you use the qdbc tool.
If you want to playback at a specific offset (ie, the Nth track in a
track session) you can use mme_play_offset().
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2010-08-16T14:34:18Zpost63063: RE: How to set the fid in different msid
http://community.qnx.com/sf/go/post63063
If you inspect the library table columns, you will see that there are fields for all those attributes and more:
qdbc -dmme "select * from library limit 1"
You can play from one storage type (select ... where msid=x), artist (select ... where artist_id=x), or many other attributes. You can find the artist_id values in the library_artists table (select * from library_artists) and the others work similarly.
-----Original Message-----
From: Kailen High [mailto:community-noreply@qnx.com]
Sent: Sun 8/15/2010 11:05
To: general-multimedia
Subject: Re: How to set the fid in different msid
Hi Dan!
Thanks for your reply.Because I want to distinguish the media files of the different store types(USB or HardDrive). I need select one of the store device ,and play the media files of the device selected.Further more ,In order to control the playback conveniently, I want to begin playing the fid with value=1 in differnt store types. thanks!
Secondly,I want to view the playlist by album(artist),how should I do?
please give me some advices,thanks very much!
_______________________________________________
General
http://community.qnx.com/sf/go/post63023Tony Smith2010-08-16T13:38:16Zpost63023: Re: How to set the fid in different msid
http://community.qnx.com/sf/go/post63023
Hi Dan!
Thanks for your reply.Because I want to distinguish the media files of the different store types(USB or HardDrive). I need select one of the store device ,and play the media files of the device selected.Further more ,In order to control the playback conveniently, I want to begin playing the fid with value=1 in differnt store types. thanks!
Secondly,I want to view the playlist by album(artist),how should I do?
please give me some advices,thanks very much!Kailen High2010-08-15T15:05:32Zpost62262: Re: How to set the fid in different msid
http://community.qnx.com/sf/go/post62262
fids are unique across the entire database, so this isn't something you should be trying to achieve.
Why?
Dan
On 2010-08-09, at 6:33 AM, Kailen High wrote:
> Hi all!
> Now , I have two store types of usb and harddrive.In the first msid ,it has 4 media files. but I found that the fid is began with 1 in the first msid, and ,the fid is begin with 6 in the second msid .
> I want to the value is 1 in the begining of fid in different msid,how can I do?
> please give me some advice.thanks!
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post62258
>
Dan Cardamore
dcardamore@qnx.comDan Cardamore(deleted)2010-08-09T11:11:09Zpost62258: How to set the fid in different msid
http://community.qnx.com/sf/go/post62258
Hi all!
Now , I have two store types of usb and harddrive.In the first msid ,it has 4 media files. but I found that the fid is began with 1 in the first msid, and ,the fid is begin with 6 in the second msid .
I want to the value is 1 in the begining of fid in different msid,how can I do?
please give me some advice.thanks!Kailen High2010-08-09T10:33:46Zpost61143: Re: Seeking advice for Aviage to support low power mode
http://community.qnx.com/sf/go/post61143
Got it and thanks for your info, Gilles.
Regards,
ChrisChris Li(deleted)2010-07-30T04:28:32Zpost61133: Re: Seeking advice for Aviage to support low power mode
http://community.qnx.com/sf/go/post61133
On 10-07-29 10:25 PM, "Chris Li" <community-noreply@qnx.com> wrote:
> Yes, you are right. I have also tried using kill() as well, it is faster but
> still far from the target time limit. Now we are considering using other
> methods, e.g., find a way to 'pause' the io-usb but not slay it.
>
> Just wonder, if the io-usb is really can be 'paused' by stopping the
> associated interrupts, suspending the threads etc, will it cause any issues to
> Aviage, or whether Aviage is recoverable without slaying any instances,
> thanks.
I suspect in the OS forum you might get tips on how to quickly kill io-usb,
as Ryan suggested.
Pausing USB might be odd in some Multimedia scenarios. For example, if the
MME was reading from a usb stick, would it just block until you unpaused
io-usb? If MME/io-media threads start blocking, then when you call into the
MME your threads will start blocked, etc... it will creep up until many
parts of the system might be blocked.
USB calls failing might be easier to handle. You could/would get MME play
errors, or sync abort errors, but I suspect that the MME would recover when
the usb stack comes back up.
Regards,
GillesGilles Roy2010-07-30T02:38:00Zpost61131: Re: RE: Seeking advice for Aviage to support low power mode
http://community.qnx.com/sf/go/post61131
> You can also skip any chance of io-usb (or whatever process you kill) cleaning
> up by using SIGKILL rather than SIGTERM. The safety of this depends on what
> state you expect the system to be in after the low power mode (and whether the
> newly spawned instance of io-usb, or whatever process, can recover the
> hardware without cleanup).
>
> In any case, if I'm not mistaken, the OS will spawn a little cleanup thread in
> your dead process to free up system resources that may otherwise be left; I
> don't know how long this will take but it may be a factor in what is taking so
> long. It might be an idea to take a kernel trace of your current method to
> get an idea of where the longest times are spent (ie, is it in the system()
> call, io-usb "cleaning up" by catching the SIGTERM, the OS cleanup thread, etc
> .).
>
> And if the conversation has really shifted from "what is safe from an MME
> perspective" to "how can I kill something quickly" then I would also suggest
> posting the question in the OS forum. There are a lot of bright people who
> monitor that forum that don't monitor the MME forum.
> <http://community.qnx.com/sf/discussion/do/listTopics/projects.core_os/discussion.newcode>
>
> --
> Ryan J. Allen
> QNX Software Systems
>
Thanks your info and suggestion, Ryan.
Actually I am not keen to slay instances in order to go to low power mode unless have to do so. Now just consider finding a way to 'pause' io-usb rather than slaying it. And just wonder whether it will cause any issues to Aviage if the io-usb is suspended while playing a track or the mme is enumerating a usb device, thanks.
Regards,
ChrisChris Li(deleted)2010-07-30T02:35:35Zpost61130: Re: Seeking advice for Aviage to support low power mode
http://community.qnx.com/sf/go/post61130
Hi Gilles,
Yes, you are right. I have also tried using kill() as well, it is faster but still far from the target time limit. Now we are considering using other methods, e.g., find a way to 'pause' the io-usb but not slay it.
Just wonder, if the io-usb is really can be 'paused' by stopping the associated interrupts, suspending the threads etc, will it cause any issues to Aviage, or whether Aviage is recoverable without slaying any instances, thanks.
Regards,
ChrisChris Li(deleted)2010-07-30T02:25:08Zpost61129: RE: Seeking advice for Aviage to support low power mode
http://community.qnx.com/sf/go/post61129
You can also skip any chance of io-usb (or whatever process you kill) cleaning up by using SIGKILL rather than SIGTERM. The safety of this depends on what state you expect the system to be in after the low power mode (and whether the newly spawned instance of io-usb, or whatever process, can recover the hardware without cleanup).
In any case, if I'm not mistaken, the OS will spawn a little cleanup thread in your dead process to free up system resources that may otherwise be left; I don't know how long this will take but it may be a factor in what is taking so long. It might be an idea to take a kernel trace of your current method to get an idea of where the longest times are spent (ie, is it in the system() call, io-usb "cleaning up" by catching the SIGTERM, the OS cleanup thread, etc.).
And if the conversation has really shifted from "what is safe from an MME perspective" to "how can I kill something quickly" then I would also suggest posting the question in the OS forum. There are a lot of bright people who monitor that forum that don't monitor the MME forum.
<http://community.qnx.com/sf/discussion/do/listTopics/projects.core_os/discussion.newcode>
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2010-07-30T02:17:42Zpost61128: Re: Seeking advice for Aviage to support low power mode
http://community.qnx.com/sf/go/post61128
On 10-07-29 9:56 PM, "Chris Li" <community-noreply@qnx.com> wrote:
> Actually I just use a timer to trace how long the system("slay io-usb") call
> takes, it is not the exact time it used for slaying the io-usb. However, I
> need to use this mechanism to slay other instances which depended on io-usb as
> well, so the whole slaying process for all necessary instances takes much
> longer than 5ms.
OK, well if you had tracked the pid ahead of time you could call kill(). It
would be much faster than system("slay io-usb"). I was just thinking you
might be able to get away with just slaying io-usb and then slaying they
other processes once you power down the USB power.
Regards,
GillesGilles Roy2010-07-30T02:08:35Zpost61127: Re: Seeking advice for Aviage to support low power mode
http://community.qnx.com/sf/go/post61127
> On 10-07-29 6:58 PM, "Chris Li" <community-noreply@qnx.com> wrote:
> > So far I have found that it took at least 50ms to slay the io-usb instance
> > from a system call, sometimes 70ms or longer.
>
> 5 msec isn't much time. One thing you might also consider is the priority at
> which you are terminating io-usb at. You might be terminating it at priority
> 10 (often a typical process priority) while other thing might be running at
> higher priority on the system.
>
Yes, I have thought about the priority problem and tried increasing the calling thread's priority from 10 to 20, it just has a slight improvement but far from reaching the goal of 5ms.
> Also, how are you testing this? Using something like "time slay io-usb" in a
> shell is bad. It has to spawn a time process, which spawns slay, etc.. all
> of which might take over 5 msec if it is pulling these binaries from a flash
> file system.
>
> Gilles
Actually I just use a timer to trace how long the system("slay io-usb") call takes, it is not the exact time it used for slaying the io-usb. However, I need to use this mechanism to slay other instances which depended on io-usb as well, so the whole slaying process for all necessary instances takes much longer than 5ms.
Regards,
ChrisChris Li(deleted)2010-07-30T01:56:01Zpost61124: Re: Seeking advice for Aviage to support low power mode
http://community.qnx.com/sf/go/post61124
On 10-07-29 6:58 PM, "Chris Li" <community-noreply@qnx.com> wrote:
> So far I have found that it took at least 50ms to slay the io-usb instance
> from a system call, sometimes 70ms or longer.
5 msec isn't much time. One thing you might also consider is the priority at
which you are terminating io-usb at. You might be terminating it at priority
10 (often a typical process priority) while other thing might be running at
higher priority on the system.
Also, how are you testing this? Using something like "time slay io-usb" in a
shell is bad. It has to spawn a time process, which spawns slay, etc.. all
of which might take over 5 msec if it is pulling these binaries from a flash
file system.
GillesGilles Roy2010-07-30T01:14:12Zpost61116: Re: RE: Seeking advice for Aviage to support low power mode
http://community.qnx.com/sf/go/post61116
Hi Gilles,
So far I have found that it took at least 50ms to slay the io-usb instance from a system call, sometimes 70ms or longer.
Regards,
ChrisChris Li(deleted)2010-07-29T22:58:02Zpost61091: Re: RE: Seeking advice for Aviage to support low power mode
http://community.qnx.com/sf/go/post61091
Have you just tried to time how long slaying io-usb only takes?Gilles Roy2010-07-29T18:09:36Zpost60994: Re: RE: Seeking advice for Aviage to support low power mode
http://community.qnx.com/sf/go/post60994
Much thanks your advice, Ryan.
Just found that the whole process of slaying the necessary instances like mme-generic, iPod driver or umass driver, enum-device and io-usb takes at least hundreds of ms to finish, it is still a bit hard to satisfy the 5ms requirement.
Regards,
ChrisChris Li(deleted)2010-07-29T02:21:43Zpost60827: RE: Seeking advice for Aviage to support low power mode
http://community.qnx.com/sf/go/post60827
I think there could be two approaches:
1. you kill io-usb and drivers that depend on it (devb-umass, io-fs-media -dipod, etc.). These mediastores will go away, and the MME will eject them. Upon restarting the driver the MME will re-insert the mediastores and you must recover your playback state as desired.
2. slay mme-generic. No other process should write to the database, and the database is the only real persistent location between executions. If mme-generic dies it won't log funny mediastore ejections, etc. And it is meant to try to recover from "sudden deaths" in case of unexpected crashes. Upon restarting mme-generic it will re-discover available mediastores.
Playback and sync will stop automatically in either case, because the MME or the mediastore will go away. If you're concerned about your application getting undesired events in the case of suggestion 1. then killing the MME may be better; if you're concerned about the database being consistent then suggestion 1. may technically be safer, but you will end up with errors and ejections of each mediastore.
--
Ryan J. Allen
QNX Software SystemsRyan Allen(deleted)2010-07-28T02:51:02Zpost60825: Seeking advice for Aviage to support low power mode
http://community.qnx.com/sf/go/post60825
Hi,
There is a customer requirement that the system needs to go to low power mode within 5ms, and before it enters low power mode, the io-usb instance needs to be slain so the USB transceiver can be shut off.
Because io-usb is the crucial instance for Aviage suite while the connected iPod or usb key is playing, we can't just slay io-usb without doing some proper handlings for Aviage beforehand. E.g., we might need to use mme_stop() to stop any playback first, then do some handling for Aviage like slaying all Aviage instances including the io-usb in worst case, then the system can go to low power mode. However, it seems it is hard to get all these things done within 5ms.
Now just seeking some advice of how to handle this case for Aviage to let it be able to enter low power mode within 5ms, and to ensure it is recoverable
after back from low power mode, much thanks.
(Our testing hardware is a 400MHz freescale iMX31 platform and the Aviage Multimedia Suite is version 1.2)
Regards,
ChrisChris Li(deleted)2010-07-28T02:14:56Zpost60550: About h264 video decoder
http://community.qnx.com/sf/go/post60550
Hi all!
I am writing a h264 decoder filter,but the io-media is down when I run it .the log is as follow,thanks !
fid=2
mme_play(): success
io-media-generic: open('graphs/trackplayer/default')
io-media-generic/trackplayer: Calling graph create function
io-media-generic/trackplayer: Created graph instance 'default'
io-media-generic: open( 'graphs/trackplayer/default' ): success
io-media-generic/trackplayer: Calling graph handler for dcmd GRAPHOPTIONS
io-media-generic/trackplayer: Dcmd GRAPHOPTIONS returning 0
io-media-generic/trackplayer: Calling graph handler for dcmd SETNOTIFICATION
io-media-generic/trackplayer: Dcmd SETNOTIFICATION returning 0
io-media-generic/trackplayer: Calling graph handler for dcmd SETTRANSITION
io-media-generic/trackplayer: Dcmd SETTRANSITION returning 0
io-media-generic/trackplayer: Calling graph handler for dcmd CAPABILITIES
io-media-generic/trackplayer: Dcmd CAPABILITIES returning 0
io-media-generic/trackplayer: Calling graph handler for dcmd ATTACHOUTPUT
io-media-generic/mmf: writer hint gf:* found
io-media-generic/mmf: URL 'gf:0000,0000,0?layer=1&aspn=72&aspd=77&sat=25' matches pattern 'gf:*'
io-media-generic/trackplayer: Dcmd ATTACHOUTPUT returning 0
00:10:22 | CRIT | _setiomoutputattr |5802| Output device type 2 not supported
io-media-generic/trackplayer: Calling graph handler for dcmd SETSPEED
io-media-generic/trackplayer: Dcmd SETSPEED returning 0
io-media-generic/trackplayer: Calling graph handler for dcmd GETSTATUS
io-media-generic/trackplayer: Dcmd GETSTATUS returning 0
io-media-generic/trackplayer: Calling graph handler for dcmd SETNOTIFICATION
io-media-generic/trackplayer: Dcmd SETNOTIFICATION returning 0
io-media-generic/trackplayer: Calling graph handler for dcmd ATTACHINPUT
io-media-generic/aoi: AoHold: reloaded /fs/etfs/kscope/armle/lib/dll/mmedia/upnp_streamer.so
io-media-generic/aoi: AoRelease: unloading /fs/etfs/kscope/armle/lib/dll/mmedia/upnp_streamer.so
io-media-generic/mmf: URL '/media/drive///test.mp4' matches pattern '*.mp4'
io-media-generic/trackplayer: Tag 'format' has 0 kids
io-media-generic/mmf: Setting long resource 'StreamerStickyError' (value='1')
io-media-generic/aoi: Graphbuilder: entry build_mmgraph
io-media-generic/aoi: Graphbuilder: entry build_mmgraph
io-media-generic/mmf: Setting long resource 'MM_TMPFILE_STREAMER_SEEKABLE' (value='1')
io-media-generic/mmf: Resource 'MM_TMPFILE_STREAMER_SEEKABLE' is not supported (but optional)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/aoi: medialib: Entry------- MmAcquireChannel
io-media-generic/aoi: medialib: MmAcquireChannel-Mediaoutput
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib: Entry------- MmAcquireChannel
io-media-generic/aoi: medialib: MmAcquireChannel-MediaInput
io-media-generic/aoi: medialib: MmAcquireChannel-AcquireChannel(c)flag=32,ID=QueueIn
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/aoi: medialib: Entry------- MmAcquireChannel
io-media-generic/aoi: medialib: MmAcquireChannel-Mediaoutput
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/trackplayer: Skipping audio graph -- no audio device.
io-media-generic/aoi: Graphbuilder:Entry----- find_next_filter
io-media-generic/aoi: Graphbuilder:comming--- input->hints != NULL
io-media-generic/aoi: Graphbuilder:tag=parser
io-media-generic/aoi: Graphbuilder:comming to iom_cfg_find_attr
io-media-generic/aoi: medialib:Entry----------MmTryChannelsFilter
io-media-generic/aoi: mp4_parser: Entry---------- SniffStream
io-media-generic/aoi: 0:Box: "ftyp", 0...24
io-media-generic/aoi: MP4Parser: valid mp4 file.
io-media-generic/aoi: mp4_parser: Ending---------- SniffStream
io-media-generic/aoi: mp4_parser: Entry-----------Create
io-media-generic/aoi: mp4_parser: Ending-----------Create
io-media-generic/aoi: MP4Parser0 iterating through our postable event returning type = 0x4 MM_EV_METADATA_UPDATE
io-media-generic/aoi: MP4Parser0 iterating through our postable event END cookie = 1
io-media-generic/aoi: medialib:MmTryChannelsFilter--go through all of the channels
io-media-generic/aoi: Before comming to for loop --MmIterateChannels
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:MmTryChannelsFilter,for_loop=1,ic=1859128
io-media-generic/aoi: forloop--if match---------------------
io-media-generic/aoi: medialib: Entry------- MmAcquireChannel
io-media-generic/aoi: medialib: MmAcquireChannel-MediaInput
io-media-generic/aoi: medialib: MmAcquireChannel-AcquireChannel(c)flag=16,ID=MP4AudioIn
io-media-generic/aoi: mp4_parser: Entry---------- RateInputFormat
io-media-generic/aoi: MP4Parser: Entry SetChannelsParameters
io-media-generic/aoi: 0:Box: "ftyp", 0...24
io-media-generic/aoi: 0:Box: "moov", 24...31463
io-media-generic/aoi: Box: moov,
io-media-generic/aoi: 1:Box: "mvhd", 32...140
io-media-generic/aoi: reading in mvhd box, version 0
io-media-generic/aoi: 1:Box: "trak", 140...18145
io-media-generic/aoi: 2:Box: "tkhd", 148...240
io-media-generic/aoi: 2:Box: "edts", 240...276
io-media-generic/aoi: 3:Box: "elst", 248...276
io-media-generic/aoi: 2:Box: "mdia", 276...18145
io-media-generic/aoi: 3:Box: "mdhd", 284...316
io-media-generic/aoi: 3:Box: "hdlr", 316...374
io-media-generic/aoi: 3:Box: "minf", 374...18145
io-media-generic/aoi: 4:Box: "smhd", 382...398
io-media-generic/aoi: 4:Box: "dinf", 398...434
io-media-generic/aoi: 5:Box: "dref", 406...434
io-media-generic/aoi: contains 1 entries:
io-media-generic/aoi: 6:Box: "url ", 422...434
io-media-generic/aoi: 4:Box: "stbl", 434...18145
io-media-generic/aoi: 5:Box: "stsd", 442...545
io-media-generic/aoi: contains 1 entries:
io-media-generic/aoi: 6:Box: "mp4a", 458...545
io-media-generic/aoi: 7:Box: "esds", 494...545
io-media-generic/aoi: parsing esds 39 byte box:
io-media-generic/aoi: esds_box_handler have descr_header: descr_tag=3, descr_len=34
io-media-generic/aoi: esds_box_handler have descr_header: descr_tag=4, descr_len=20
io-media-generic/aoi: esds_box_handler have descr_header: descr_tag=5, descr_len=2
io-media-generic/aoi: esds_box_handler have descr_header: descr_tag=6, descr_len=1
io-media-generic/aoi: 5:Box: "stts", 545...569
io-media-generic/aoi: 5:Box: "stsc", 569...5013
io-media-generic/aoi: 5:Box: "stsz", 5013...16653
io-media-generic/aoi: 5:Box: "stco", 16653...18145
io-media-generic/aoi: 1:Box: "trak", 18145...30474
io-media-generic/aoi: 2:Box: "tkhd", 18153...18245
io-media-generic/aoi: 2:Box: "edts", 18245...18281
io-media-generic/aoi: 3:Box: "elst", 18253...18281
io-media-generic/aoi: 2:Box: "mdia", 18281...30474
io-media-generic/aoi: 3:Box: "mdhd", 18289...18321
io-media-generic/aoi: 3:Box: "hdlr", 18321...18379
io-media-generic/aoi: 3:Box: "minf", 18379...30474
io-media-generic/aoi: 4:Box: "vmhd", 18387...18407
io-media-generic/aoi: 4:Box: "dinf", 18407...18443
io-media-generic/aoi: 5:Box: "dref", 18415...18443
io-media-generic/aoi: contains 1 entries:
io-media-generic/aoi: 6:Box: "url ", 18431...18443
io-media-generic/aoi: 4:Box: "stbl", 18443...30474
io-media-generic/aoi: 5:Box: "stsd", 18451...18622
io-media-generic/aoi: contains 1 entries:
io-media-generic/aoi: 6:Box: "mp4v", 18467...18622
io-media-generic/aoi: 7:Box: "esds", 18553...18622
io-media-generic/aoi: parsing esds 57 byte box:
io-media-generic/aoi: esds_box_handler have descr_header: descr_tag=3, descr_len=55
io-media-generic/aoi: esds_box_handler have descr_header: descr_tag=4, descr_len=47
io-media-generic/aoi: esds_box_handler have descr_header: descr_tag=5, descr_len=32
io-media-generic/aoi: esds_box_handler have descr_header: descr_tag=6, descr_len=1
io-media-generic/aoi: 5:Box: "stts", 18622...18646
io-media-generic/aoi: 5:Box: "stss", 18646...18978
io-media-generic/aoi: 5:Box: "stsc", 18978...22006
io-media-generic/aoi: 5:Box: "stsz", 22006...29454
io-media-generic/aoi: 5:Box: "stco", 29454...30474
io-media-generic/aoi: 1:Box: "trak", 30474...30943
io-media-generic/aoi: 2:Box: "tkhd", 30482...30574
io-media-generic/aoi: 2:Box: "edts", 30574...30610
io-media-generic/aoi: 3:Box: "elst", 30582...30610
io-media-generic/aoi: 2:Box: "mdia", 30610...30943
io-media-generic/aoi: 3:Box: "mdhd", 30618...30650
io-media-generic/aoi: 3:Box: "hdlr", 30650...30715
io-media-generic/aoi: 3:Box: "minf", 30715...30943
io-media-generic/aoi: 4:Box: "nmhd", 30723...30735
io-media-generic/aoi: not recognized, skipping to 780f. err = 0
io-media-generic/aoi: 4:Box: "dinf", 30735...30771
io-media-generic/aoi: 5:Box: "dref", 30743...30771
io-media-generic/aoi: contains 1 entries:
io-media-generic/aoi: 6:Box: "url ", 30759...30771
io-media-generic/aoi: 4:Box: "stbl", 30771...30943
io-media-generic/aoi: 5:Box: "stsd", 30779...30851
io-media-generic/aoi: contains 1 entries:
io-media-generic/aoi: 6:Box: "mp4s", 30795...30851
io-media-generic/aoi: not recognized, skipping to 7883. err = 0
io-media-generic/aoi: 5:Box: "stts", 30851...30875
io-media-generic/aoi: 5:Box: "stsc", 30875...30903
io-media-generic/aoi: 5:Box: "stsz", 30903...30923
io-media-generic/aoi: 5:Box: "stco", 30923...30943
io-media-generic/aoi: 1:Box: "trak", 30943...31430
io-media-generic/aoi: 2:Box: "tkhd", 30951...31043
io-media-generic/aoi: 2:Box: "edts", 31043...31079
io-media-generic/aoi: 3:Box: "elst", 31051...31079
io-media-generic/aoi: 2:Box: "tref", 31079...31103
io-media-generic/aoi: not recognized, skipping to 797f. err = 0
io-media-generic/aoi: 2:Box: "mdia", 31103...31430
io-media-generic/aoi: 3:Box: "mdhd", 31111...31143
io-media-generic/aoi: 3:Box: "hdlr", 31143...31207
io-media-generic/aoi: 3:Box: "minf", 31207...31430
io-media-generic/aoi: 4:Box: "nmhd", 31215...31227
io-media-generic/aoi: not recognized, skipping to 79fb. err = 0
io-media-generic/aoi: 4:Box: "dinf", 31227...31263
io-media-generic/aoi: 5:Box: "dref", 31235...31263
io-media-generic/aoi: contains 1 entries:
io-media-generic/aoi: 6:Box: "url ", 31251...31263
io-media-generic/aoi: 4:Box: "stbl", 31263...31430
io-media-generic/aoi: 5:Box: "stsd", 31271...31338
io-media-generic/aoi: contains 1 entries:
io-media-generic/aoi: 6:Box: "mp4s", 31287...31338
io-media-generic/aoi: not recognized, skipping to 7a6a. err = 0
io-media-generic/aoi: 5:Box: "stts", 31338...31362
io-media-generic/aoi: 5:Box: "stsc", 31362...31390
io-media-generic/aoi: 5:Box: "stsz", 31390...31410
io-media-generic/aoi: 5:Box: "stco", 31410...31430
io-media-generic/aoi: 1:Box: "iods", 31430...31463
io-media-generic/aoi: not recognized, skipping to 7ae7. err = 0
io-media-generic/aoi: 0:Box: "free", 31463...31471
io-media-generic/aoi: Box: free,
io-media-generic/aoi: not recognized, skipping to 7aef. err = 0
io-media-generic/aoi: 0:Box: "free", 31471...31479
io-media-generic/aoi: Box: free,
io-media-generic/aoi: not recognized, skipping to 7af7. err = 0
io-media-generic/aoi: 0:Box: "mdat", 31479...2808003
io-media-generic/aoi: Box: mdat,
io-media-generic/aoi: not recognized, skipping to 2ad8c3. err = 0
io-media-generic/aoi: MP4Parser: VideoTracks=1,Audiotracks=1
io-media-generic/aoi: mp4_parser: mp4a type 64
io-media-generic/aoi: MP4Parser:Entry for loop,the i= fu->track_count=4
io-media-generic/aoi: MP4Parser:The loop num=0
io-media-generic/aoi: MP4Parser: num_frames[0] = 2905
io-media-generic/aoi: MP4Parser: Track duration 61973333 found on trackid 0
io-media-generic/aoi: MP4Parser: Very important track_type=soun
io-media-generic/aoi: MP4Parser: Entry sound
io-media-generic/aoi: MP4Parser: Entry tmpfourcc=mp4a
io-media-generic/aoi: MP4Parser: Audio mp4a_type =40
io-media-generic/aoi: MP4Parser: getting the STSZ / STZ2.
io-media-generic/aoi: MP4Parser: max sample size = 502.
io-media-generic/aoi: MP4Parser: getting the STCO.
io-media-generic/aoi: MP4Parser: Track 1 has 369 STCO entries.
io-media-generic/aoi: MP4Parser: getting the STSS.
io-media-generic/aoi: MP4Parser: getting the STTS and CTTS.
io-media-generic/aoi: MP4Parser: Track 0 has 1 STTS entries.
io-media-generic/aoi: MP4Parser: Track 0 has 0 CTTS entries.
io-media-generic/aoi: MP4Parser: channel fourcc = M4AC
io-media-generic/aoi: bitrate = 128000, interface = 128000
io-media-generic/aoi: aac_framerate = 48000, timescale = 48000
io-media-generic/aoi: MP4Parser:The loop num=1
io-media-generic/aoi: MP4Parser: num_frames[1] = 1857
io-media-generic/aoi: MP4Parser: Track duration 61961961 found on trackid 1
io-media-generic/aoi: MP4Parser: Very important track_type=vide
io-media-generic/aoi: MP4Parser: Entry video
io-media-generic/aoi: MP4Parser:before if video fu->file_info->tracks[i].has_esds=1
io-media-generic/aoi: MP4Parser:before if video esds->has_type4=1
io-media-generic/aoi: MP4Parser: video mp4v_type=20
io-media-generic/aoi: MP4Parser: getting the STSZ / STZ2.
io-media-generic/aoi: MP4Parser: max sample size = 12977.
io-media-generic/aoi: MP4Parser: getting the STCO.
io-media-generic/aoi: MP4Parser: Track 1 has 251 STCO entries.
io-media-generic/aoi: MP4Parser: getting the STSS.
io-media-generic/aoi: MP4Parser: Added a 79 entry Sync Table for track 1.
io-media-generic/aoi: MP4Parser: getting the STTS and CTTS.
io-media-generic/aoi: MP4Parser: Track 1 has 1 STTS entries.
io-media-generic/aoi: MP4Parser: Track 1 has 0 CTTS entries.
io-media-generic/aoi: MP4Parser: Storing a mp4v decoder config.
io-media-generic/aoi: MP4Parser: channel fourcc = MP4V
io-media-generic/aoi: bitrate = 256000, interface = 230470
io-media-generic/aoi: MP4Parser:The loop num=2
io-media-generic/aoi: MP4Parser:The loop num=3
io-media-generic/aoi: MP4Parser: Ending ------------------- SetChannelsParameters
io-media-generic/aoi: mp4_parser: Ending---------- RateInputFormat,return80
io-media-generic/aoi: mp4_parser: Entry---------- RateInputFormat
io-media-generic/aoi: mp4_parser: Entry----------SetInputFormat
io-media-generic/aoi: mp4_parser: Entry----------SetMediaOutput
io-media-generic/trackplayer: Loaded the mp4_parser filter based on the parser tag
io-media-generic/aoi: Graphbuilder:beforeEntry----- MmFindChannelsFilter( mmgraph, oc )
io-media-generic/aoi: Graphbuilder:afterEntry----- MmFindChannelsFilter( mmgraph, oc )
io-media-generic/mmf: Setting long resource 'AVSyncDelay' (value='0')
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/aoi: mp4_parser: Entry----------IterateOutputChannels
io-media-generic/aoi: mp4_parser: *cookie=0
io-media-generic/aoi: mp4_parser: f->user->ochannel_count=2
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/aoi: mp4_parser: Entry----------IterateOutputChannels
io-media-generic/aoi: mp4_parser: *cookie=1
io-media-generic/aoi: mp4_parser: f->user->ochannel_count=2
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/aoi: mp4_parser: Entry----------IterateOutputChannels
io-media-generic/aoi: mp4_parser: *cookie=2
io-media-generic/aoi: mp4_parser: f->user->ochannel_count=2
io-media-generic/aoi: mp4_parser: *cookie) >= f->user->ochannel_count.return NULL
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/aoi: mp4_parser: Entry----------IterateOutputChannels
io-media-generic/aoi: mp4_parser: *cookie=0
io-media-generic/aoi: mp4_parser: f->user->ochannel_count=2
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/aoi: mp4_parser: Entry----------IterateOutputChannels
io-media-generic/aoi: mp4_parser: *cookie=1
io-media-generic/aoi: mp4_parser: f->user->ochannel_count=2
io-media-generic/aoi: medialib: Entry------- MmAcquireChannel
io-media-generic/aoi: medialib: MmAcquireChannel-Mediaoutput
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: mp4_parser: Entry----------AcquireOutputChannel
io-media-generic/trackplayer: Skipping audio subgraph because there is no device specified.
io-media-generic/trackplayer: Found video stream with bitrate 230470.
io-media-generic/trackplayer: No audio stream found.
io-media-generic/mmf: Configuring the queue for 345705 bytes, lw = 69141, hw = 276564.
io-media-generic/trackplayer: Skipping subgraph 0 because there is no device specified.
io-media-generic/trackplayer: Finding decoder for stream 1.
io-media-generic/aoi: GfMixer Create.
io-media-generic/aoi: GfMixer SetResource.
io-media-generic/aoi: gf_writer: Got params:
io-media-generic/aoi: gf_writer: layer: 1
io-media-generic/aoi: gf_writer: aspect_num: 72
io-media-generic/aoi: gf_writer: aspect_denom: 77
io-media-generic/aoi: gf_writer: saturation: 25
io-media-generic/aoi: GfMixer using device 0000,0000,0.
io-media-generic/aoi: GfMixer SetResource.
io-media-generic/aoi: gf_writer setting the resource: VideoWriterThreadPrioBase to 21
io-media-generic/aoi: GfMixer SetResource.
io-media-generic/aoi: gf_writer setting the resource: VideoWriterThreadPrioInc to 0
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: Gf_Writer: Entry IterateInputChannels
io-media-generic/aoi: medialib: Entry------- MmAcquireChannel
io-media-generic/aoi: medialib: MmAcquireChannel-MediaInput
io-media-generic/aoi: medialib: MmAcquireChannel-AcquireChannel(c)flag=0,ID=input-0
io-media-generic/aoi: Gf_Writer: Entry AcquireInputChannel
io-media-generic/aoi: GfMixer AcquireInputChannel.
io-media-generic/aoi: mp4_parser: Entry----------IterateOutputFormats
io-media-generic/aoi: mp4_parser: avsync delay = 0
io-media-generic/aoi: mp4_parser: calculating relative track offsets for 4 tracks
io-media-generic/aoi: mp4_parser: track 0 has 369 chunks.
io-media-generic/aoi: mp4_parser: track 0 max chunks size = 5540
io-media-generic/aoi: mp4_parser: track 1 max chunks size = 26885
io-media-generic/aoi: mp4_parser: track 2 max chunks size = 0
io-media-generic/aoi: mp4_parser: track 3 max chunks size = 0
io-media-generic/aoi: mp4_parser: track 1 has 251 chunks.
io-media-generic/aoi: mp4_parser: track 2 has 0 chunks.
io-media-generic/aoi: mp4_parser: track 2 has no offsets.
io-media-generic/aoi: mp4_parser: track 3 has 0 chunks.
io-media-generic/aoi: mp4_parser: track 3 has no offsets.
io-media-generic/aoi: mp4_parser: max distance 3529 -- min distance -46287.
io-media-generic/aoi: mp4_parser: 0 iters gave max distance between corresponding chunks = 55356.
io-media-generic/aoi: mp4_parser: we need 4 32768 byte MRAs to cover this distance.
io-media-generic/aoi: Gf_Writer: Entry RateInputFormat
io-media-generic/aoi: Gf_Writer:MmFormat_t fmt1=909288,fmt->mf.mtype.width=352,fmt->mf.mtype.height=288
io-media-generic/aoi: Gf_Writer: fmt->mf.mtype=-2147483646
io-media-generic/aoi: GfMixer RateInputFormat -2147483646.
io-media-generic/aoi: Gf_Writer: Entry RateInputFormat
io-media-generic/aoi: Gf_Writer:MmFormat_t fmt1=909288,fmt->mf.mtype.width=352,fmt->mf.mtype.height=288
io-media-generic/aoi: mp4_parser: Entry----------IterateOutputFormats
io-media-generic/aoi: mp4_parser: avsync delay = 0
io-media-generic/aoi: Gf_Writer: Entry RateInputFormat
io-media-generic/aoi: Gf_Writer:MmFormat_t fmt1=909288,fmt->mf.mtype.width=352,fmt->mf.mtype.height=288
io-media-generic/aoi: Gf_Writer: fmt->mf.mtype=-2147483646
io-media-generic/aoi: GfMixer RateInputFormat -2147483646.
io-media-generic/aoi: Gf_Writer: Entry RateInputFormat
io-media-generic/aoi: Gf_Writer:MmFormat_t fmt1=909288,fmt->mf.mtype.width=352,fmt->mf.mtype.height=288
io-media-generic/aoi: mp4_parser: Entry----------IterateOutputFormats
io-media-generic/aoi: Couldn't negotiate formats.
io-media-generic/aoi: Graphbuilder: Not connected let's find a decoder
io-media-generic/trackplayer: Adding queue size 30
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib: Entry------- MmAcquireChannel
io-media-generic/aoi: medialib: MmAcquireChannel-MediaInput
io-media-generic/aoi: medialib: MmAcquireChannel-AcquireChannel(c)flag=32,ID=QueueIn
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/aoi: medialib: Entry------- MmAcquireChannel
io-media-generic/aoi: medialib: MmAcquireChannel-Mediaoutput
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: Graphbuilder: find_next_filter
io-media-generic/aoi: Graphbuilder:Entry----- find_next_filter
io-media-generic/aoi: Graphbuilder:comming--- input->hints != NULL
io-media-generic/aoi: Graphbuilder:tag=decoder
io-media-generic/aoi: Graphbuilder:comming to iom_cfg_find_attr
io-media-generic/aoi: medialib:Entry----------MmTryChannelsFilter
io-media-generic/aoi: medialib:MmTryChannelsFilter-------AOFormatInspector
io-media-generic/aoi: mp4_parser: Entry----------IterateOutputFormats
io-media-generic/aoi: mp4_parser: avsync delay = 0
io-media-generic/aoi: h264_decoder: Entry-----RateFormat
io-media-generic/aoi: H264_decoder: RateFormat-AODataFormat_t *fmt =911568
io-media-generic/aoi: h264_decoder:AODataFormat_t fmt=911568, fmt->fourcc=1297101910,FOURCC= 'V4PM,fmt->mtype=80000002
io-media-generic/aoi: h264_decoder:fmt->u.video.width=352,fmt->u.video.height=288
io-media-generic/aoi: h264_decoder:video.frame_rate=30,u.video.duration=0,u.video.scale=0
io-media-generic/aoi: h264_decoder:MmFOURCC('M','P','1','V')=1297101142
io-media-generic/aoi: h264_decoder:MmFOURCC('M','P','2','V')=1297101398
io-media-generic/aoi: h264_decoder:MmFOURCC('M','P','4','V')=1297101910
io-media-generic/aoi: h264_decoder:MmFOURCC('a','v','c','1')=1096172337
io-media-generic/aoi: h264_decoder:MmFOURCC('M','1','A','3')=1295073587
io-media-generic/aoi: h264_decoder:MmFOURCC('M','4','A','C')=1295270211
io-media-generic/aoi: h264_decoder: RateFormat(mp4v) 80
io-media-generic/aoi: mp4_parser: Entry----------IterateOutputFormats
io-media-generic/aoi: mp4_parser: avsync delay = 0
io-media-generic/aoi: h264_decoder: Entry-----RateFormat
io-media-generic/aoi: H264_decoder: RateFormat-AODataFormat_t *fmt =911568
io-media-generic/aoi: h264_decoder:AODataFormat_t fmt=911568, fmt->fourcc=1297101910,FOURCC= 'V4PM,fmt->mtype=80000002
io-media-generic/aoi: h264_decoder:fmt->u.video.width=352,fmt->u.video.height=288
io-media-generic/aoi: h264_decoder:video.frame_rate=30,u.video.duration=0,u.video.scale=0
io-media-generic/aoi: h264_decoder:MmFOURCC('M','P','1','V')=1297101142
io-media-generic/aoi: h264_decoder:MmFOURCC('M','P','2','V')=1297101398
io-media-generic/aoi: h264_decoder:MmFOURCC('M','P','4','V')=1297101910
io-media-generic/aoi: h264_decoder:MmFOURCC('a','v','c','1')=1096172337
io-media-generic/aoi: h264_decoder:MmFOURCC('M','1','A','3')=1295073587
io-media-generic/aoi: h264_decoder:MmFOURCC('M','4','A','C')=1295270211
io-media-generic/aoi: h264_decoder: RateFormat(mp4v) 80
io-media-generic/aoi: mp4_parser: Entry----------IterateOutputFormats
io-media-generic/aoi: h264_decoder: Entry---------------------- Create
io-media-generic/aoi: medialib:MmTryChannelsFilter--go through all of the channels
io-media-generic/aoi: Before comming to for loop --MmIterateChannels
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: h264_decoder:Entry IterateInputChannels
io-media-generic/aoi: h264_decoder:*cookie=0
io-media-generic/aoi: f->ichannels[0].element.ID=h264videoIn,ichannels[0].flags=16,direction=1
io-media-generic/aoi: width=0, height=0
io-media-generic/aoi: h264_decoder:Ending IterateInputChannels
io-media-generic/aoi: medialib:MmTryChannelsFilter,for_loop=1,ic=2124064
io-media-generic/aoi: forloop--if match---------------------
io-media-generic/aoi: medialib: Entry------- MmAcquireChannel
io-media-generic/aoi: medialib: MmAcquireChannel-MediaInput
io-media-generic/aoi: medialib: MmAcquireChannel-AcquireChannel(c)flag=16,ID=h264videoIn
io-media-generic/aoi: mp4_parser: Entry----------IterateOutputFormats
io-media-generic/aoi: mp4_parser: avsync delay = 0
io-media-generic/aoi: H264_decoder:Entry---------RateInputFormat
io-media-generic/aoi: H264_decoder: RateInputFormat-MmFormat_t fmt =908092
io-media-generic/aoi: h264_decoder:fmt->u.video.width=352,fmt->u.video.height=288
io-media-generic/aoi: h264_decoder:video.frame_rate=30,u.video.duration=0,u.video.scale=0
io-media-generic/aoi: H264_decoder:RateInputFormat-negotiable=1,cookie=0
io-media-generic/aoi: H264_decoder:Entry---------RateInputFormat
io-media-generic/aoi: H264_decoder: RateInputFormat-MmFormat_t fmt =908092
io-media-generic/aoi: h264_decoder:fmt->u.video.width=352,fmt->u.video.height=288
io-media-generic/aoi: h264_decoder:video.frame_rate=30,u.video.duration=0,u.video.scale=0
io-media-generic/aoi: H264_decoder:RateInputFormat-negotiable=0,cookie=0
io-media-generic/aoi: H264_decoder:EndingRateInputFormat-return 100
io-media-generic/aoi: mp4_parser: Entry----------VerifyOutputFormat
io-media-generic/aoi: mp4_parser: Entry----------IterateOutputFormats
io-media-generic/aoi: mp4_parser: avsync delay = 0
io-media-generic/aoi: H264_decoder:Entry---------RateInputFormat
io-media-generic/aoi: H264_decoder: RateInputFormat-MmFormat_t fmt =908092
io-media-generic/aoi: h264_decoder:fmt->u.video.width=352,fmt->u.video.height=288
io-media-generic/aoi: h264_decoder:video.frame_rate=30,u.video.duration=0,u.video.scale=0
io-media-generic/aoi: H264_decoder:RateInputFormat-negotiable=1,cookie=0
io-media-generic/aoi: mp4_parser: Entry----------IterateOutputFormats
io-media-generic/aoi: h264_decoder: Entry---- SetInputFormat
io-media-generic/aoi: H264_decoder:fmt =910332,fmt->mf.u.video.width=352,fmt->mf.u.video.height=288
io-media-generic/aoi: H264_decoder:channela=2124064,channela->format.mf.u.video.width=0,channela->format.mf.u.video.height=0
io-media-generic/aoi: H264_decoder:channelb=2124064,channelb->format.mf.u.video.width=352,channelb->format.mf.u.video.height=
288
io-media-generic/aoi: h264_decoder: Endding SetInputFormat,return mm_ok
io-media-generic/aoi: mp4_parser: Entry----------SetOutputFormat
io-media-generic/aoi: h264_decoder: entry SetMediaOutput
io-media-generic/aoi: h264_decoder: Endding SetMediaOutput,return mm_ok
io-media-generic/trackplayer: Loaded the h264_decoder filter based on the decoder tag
io-media-generic/aoi: Graphbuilder:beforeEntry----- MmFindChannelsFilter( mmgraph, oc )
io-media-generic/aoi: Graphbuilder:afterEntry----- MmFindChannelsFilter( mmgraph, oc )
io-media-generic/mmf: Setting long resource 'MM_H264_DECODER_NUM_THREADS' (value='2')
io-media-generic/mmf: Resource 'MM_H264_DECODER_NUM_THREADS' is not supported (but optional)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/aoi: h264_decoder: Entry-- IterateOutputChannels
io-media-generic/aoi: h264_decoder: Endding--IterateOutputChannels,retrun &f->ochannels[0]
io-media-generic/aoi: medialib: Entry------- MmAcquireChannel
io-media-generic/aoi: medialib: MmAcquireChannel-Mediaoutput
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: h264_decoder:Entry IterateInputChannels
io-media-generic/aoi: h264_decoder:*cookie=0
io-media-generic/aoi: f->ichannels[0].element.ID=h264videoIn,ichannels[0].flags=19,direction=1
io-media-generic/aoi: width=352, height=288
io-media-generic/aoi: h264_decoder:Ending IterateInputChannels
io-media-generic/aoi: h264_decoder: Entry------ AcquireOutputChannel
io-media-generic/aoi: h264_decoder:OC->direction=2,OC->format.mf.u.video.width=0,c->format.mf.u.video.height=0
io-media-generic/aoi: h264_decoder: Endding-- AcquireOutputChannel,return mm_ok
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib: Entry------- MmAcquireChannel
io-media-generic/aoi: medialib: MmAcquireChannel-MediaInput
io-media-generic/aoi: medialib: MmAcquireChannel-AcquireChannel(c)flag=32,ID=QueueIn
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/aoi: medialib: Entry------- MmAcquireChannel
io-media-generic/aoi: medialib: MmAcquireChannel-Mediaoutput
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: h264_decoder: Entry IterateOutputFormats
io-media-generic/aoi: H264_decoder: IterateOutputFormats-channelFormat_t fmt1 =910408
io-media-generic/aoi: H264_decoder:fmt1=910408 fmt1->mf.u.video.width=0,fmt1->mf.u.video.height=0
io-media-generic/aoi: H264_decoder:c->direction=2,c->element.ID=h264videoOut
io-media-generic/aoi: H264_decoder:c->format.mf.u.video.width=0,c->format.mf.u.video.height=0
io-media-generic/aoi: h264_decoder: cnum = *cookie=0
io-media-generic/aoi: H264_decoder: fmt2=910408,fmt2->mf.u.video.width=300,fmt2->mf.u.video.height=200
io-media-generic/aoi: h264_decoder: fmt->mf.fourcc = MmFOURCC('Y','U','Y','2')=844715353
io-media-generic/aoi: Gf_Writer: Entry RateInputFormat
io-media-generic/aoi: Gf_Writer:MmFormat_t fmt1=909288,fmt->mf.mtype.width=300,fmt->mf.mtype.height=200
io-media-generic/aoi: Gf_Writer: fmt->mf.mtype=2
io-media-generic/aoi: GfWriter attaching device 0000,0000,0.
io-media-generic/aoi: GfWriter given a FOURCC of 'YUY2'.
io-media-generic/aoi: layer index : 1
io-media-generic/aoi: Gf_writer:RateInputFormat MmFormat_t *fmt2=909288
io-media-generic/aoi: GfMixer:Entry FourccToGF
io-media-generic/aoi: Gf_writer:FourccToGF-MmFormat_t *fmt=909288
io-media-generic/aoi: Translating FOURCCa 'YUY2'
io-media-generic/aoi: Translating FOURCC1 =844715353
io-media-generic/aoi: Translating FOURCCb'YUY2'
io-media-generic/aoi: Translating FOURCC2 =844715353
io-media-generic/aoi: GfMixer:ret=33563408,Endding----------FOURCCtoGF
io-media-generic/aoi: format = 1310.
io-media-generic/aoi: format = 1018.
io-media-generic/aoi: format = 1420.
io-media-generic/aoi: H264_decoder:Entry-------VerifyOutputFormat
io-media-generic/aoi: H264_decoder: new_fmt->mf.u.video.width=300,new_fmt->mf.u.video.height=200
io-media-generic/aoi: H264_decoder: ofmt->mf.u.video.width=300,ofmt->mf.u.video.height=200
io-media-generic/aoi: H264_decoder: VerifyOutputFormat-MmFormat_t new_fmt=909288,ofmt=910408
io-media-generic/aoi: H264_decoder:VerifyOutputFormat-return 100
io-media-generic/aoi: Gf_Writer: Entry RateInputFormat
io-media-generic/aoi: Gf_Writer:MmFormat_t fmt1=909288,fmt->mf.mtype.width=300,fmt->mf.mtype.height=200
io-media-generic/aoi: h264_decoder: Entry IterateOutputFormats
io-media-generic/aoi: H264_decoder: IterateOutputFormats-channelFormat_t fmt1 =910408
io-media-generic/aoi: H264_decoder:fmt1=910408 fmt1->mf.u.video.width=300,fmt1->mf.u.video.height=200
io-media-generic/aoi: H264_decoder:c->direction=2,c->element.ID=h264videoOut
io-media-generic/aoi: H264_decoder:c->format.mf.u.video.width=0,c->format.mf.u.video.height=0
io-media-generic/aoi: h264_decoder: cnum = *cookie=1
io-media-generic/aoi: H264_decoder: fmt2=910408,fmt2->mf.u.video.width=300,fmt2->mf.u.video.height=200
io-media-generic/aoi: h264_decoder: fmt->mf.fourcc = MmFOURCC('R','G','B','2')=843204434
io-media-generic/aoi: Gf_Writer: Entry RateInputFormat
io-media-generic/aoi: Gf_Writer:MmFormat_t fmt1=909288,fmt->mf.mtype.width=300,fmt->mf.mtype.height=200
io-media-generic/aoi: Gf_Writer: fmt->mf.mtype=2
io-media-generic/aoi: GfWriter attaching device 0000,0000,0.
io-media-generic/aoi: GfWriter given a FOURCC of 'RGB2'.
io-media-generic/aoi: layer index : 1
io-media-generic/aoi: Gf_writer:RateInputFormat MmFormat_t *fmt2=909288
io-media-generic/aoi: GfMixer:Entry FourccToGF
io-media-generic/aoi: Gf_writer:FourccToGF-MmFormat_t *fmt=909288
io-media-generic/aoi: Translating FOURCCa 'RGB2'
io-media-generic/aoi: Translating FOURCC1 =843204434
io-media-generic/aoi: Translating FOURCCb'RGB2'
io-media-generic/aoi: Translating FOURCC2 =843204434
io-media-generic/aoi: GfMixer:ret=4880,Endding----------FOURCCtoGF
io-media-generic/aoi: format = 1310.
io-media-generic/aoi: format = 1018.
io-media-generic/aoi: format = 1420.
io-media-generic/aoi: H264_decoder:Entry-------VerifyOutputFormat
io-media-generic/aoi: H264_decoder: new_fmt->mf.u.video.width=300,new_fmt->mf.u.video.height=200
io-media-generic/aoi: H264_decoder: ofmt->mf.u.video.width=300,ofmt->mf.u.video.height=200
io-media-generic/aoi: H264_decoder: VerifyOutputFormat-MmFormat_t new_fmt=909288,ofmt=910408
io-media-generic/aoi: H264_decoder:VerifyOutputFormat-return 100
io-media-generic/aoi: Gf_Writer: Entry RateInputFormat
io-media-generic/aoi: Gf_Writer:MmFormat_t fmt1=909288,fmt->mf.mtype.width=300,fmt->mf.mtype.height=200
io-media-generic/aoi: h264_decoder: Entry IterateOutputFormats
io-media-generic/aoi: H264_decoder: IterateOutputFormats-channelFormat_t fmt1 =910408
io-media-generic/aoi: H264_decoder:fmt1=910408 fmt1->mf.u.video.width=300,fmt1->mf.u.video.height=200
io-media-generic/aoi: H264_decoder:c->direction=2,c->element.ID=h264videoOut
io-media-generic/aoi: H264_decoder:c->format.mf.u.video.width=0,c->format.mf.u.video.height=0
io-media-generic/aoi: h264_decoder: cnum = *cookie=2
io-media-generic/aoi: H264_decoder: fmt2=910408,fmt2->mf.u.video.width=300,fmt2->mf.u.video.height=200
io-media-generic/aoi: h264_decoder: fmt->mf.fourcc = MmFOURCC(''R','G','B','A')=1094862674
io-media-generic/aoi: Gf_Writer: Entry RateInputFormat
io-media-generic/aoi: Gf_Writer:MmFormat_t fmt1=909288,fmt->mf.mtype.width=300,fmt->mf.mtype.height=200
io-media-generic/aoi: Gf_Writer: fmt->mf.mtype=2
io-media-generic/aoi: GfWriter attaching device 0000,0000,0.
io-media-generic/aoi: GfWriter given a FOURCC of 'RGBA'.
io-media-generic/aoi: layer index : 1
io-media-generic/aoi: Gf_writer:RateInputFormat MmFormat_t *fmt2=909288
io-media-generic/aoi: GfMixer:Entry FourccToGF
io-media-generic/aoi: Gf_writer:FourccToGF-MmFormat_t *fmt=909288
io-media-generic/aoi: Translating FOURCCa 'RGBA'
io-media-generic/aoi: Translating FOURCC1 =1094862674
io-media-generic/aoi: Translating FOURCCb'RGBA'
io-media-generic/aoi: Translating FOURCC2 =1094862674
io-media-generic/aoi: GfMixer:ret=5904,Endding----------FOURCCtoGF
io-media-generic/aoi: format = 1310.
io-media-generic/aoi: format = 1018.
io-media-generic/aoi: format = 1420.
io-media-generic/aoi: H264_decoder:Entry-------VerifyOutputFormat
io-media-generic/aoi: H264_decoder: new_fmt->mf.u.video.width=300,new_fmt->mf.u.video.height=200
io-media-generic/aoi: H264_decoder: ofmt->mf.u.video.width=300,ofmt->mf.u.video.height=200
io-media-generic/aoi: H264_decoder: VerifyOutputFormat-MmFormat_t new_fmt=909288,ofmt=910408
io-media-generic/aoi: H264_decoder:VerifyOutputFormat-return 100
io-media-generic/aoi: Gf_Writer: Entry RateInputFormat
io-media-generic/aoi: Gf_Writer:MmFormat_t fmt1=909288,fmt->mf.mtype.width=300,fmt->mf.mtype.height=200
io-media-generic/aoi: h264_decoder: Entry IterateOutputFormats
io-media-generic/aoi: H264_decoder: IterateOutputFormats-channelFormat_t fmt1 =910408
io-media-generic/aoi: H264_decoder:fmt1=910408 fmt1->mf.u.video.width=300,fmt1->mf.u.video.height=200
io-media-generic/aoi: H264_decoder:c->direction=2,c->element.ID=h264videoOut
io-media-generic/aoi: H264_decoder:c->format.mf.u.video.width=0,c->format.mf.u.video.height=0
io-media-generic/aoi: h264_decoder: cnum = *cookie=3
io-media-generic/aoi: H264_decoder: fmt2=910408,fmt2->mf.u.video.width=300,fmt2->mf.u.video.height=200
io-media-generic/aoi: h264_decoder: fmt->mf.fourcc = MmFOURCC('U','Y','U','Y')=1498831189
io-media-generic/aoi: Gf_Writer: Entry RateInputFormat
io-media-generic/aoi: Gf_Writer:MmFormat_t fmt1=909288,fmt->mf.mtype.width=300,fmt->mf.mtype.height=200
io-media-generic/aoi: Gf_Writer: fmt->mf.mtype=2
io-media-generic/aoi: GfWriter attaching device 0000,0000,0.
io-media-generic/aoi: GfWriter given a FOURCC of 'UYVY'.
io-media-generic/aoi: layer index : 1
io-media-generic/aoi: Gf_writer:RateInputFormat MmFormat_t *fmt2=909288
io-media-generic/aoi: GfMixer:Entry FourccToGF
io-media-generic/aoi: Gf_writer:FourccToGF-MmFormat_t *fmt=909288
io-media-generic/aoi: Translating FOURCCa 'UYVY'
io-media-generic/aoi: Translating FOURCC1 =1498831189
io-media-generic/aoi: Translating FOURCCb'UYVY'
io-media-generic/aoi: Translating FOURCC2 =1498831189
io-media-generic/aoi: GfMixer:ret=16786192,Endding----------FOURCCtoGF
io-media-generic/aoi: format = 1310.
io-media-generic/aoi: format = 1018.
io-media-generic/aoi: format = 1420.
io-media-generic/aoi: H264_decoder:Entry-------VerifyOutputFormat
io-media-generic/aoi: H264_decoder: new_fmt->mf.u.video.width=300,new_fmt->mf.u.video.height=200
io-media-generic/aoi: H264_decoder: ofmt->mf.u.video.width=300,ofmt->mf.u.video.height=200
io-media-generic/aoi: H264_decoder: VerifyOutputFormat-MmFormat_t new_fmt=909288,ofmt=910408
io-media-generic/aoi: H264_decoder:VerifyOutputFormat-return 100
io-media-generic/aoi: Gf_Writer: Entry RateInputFormat
io-media-generic/aoi: Gf_Writer:MmFormat_t fmt1=909288,fmt->mf.mtype.width=300,fmt->mf.mtype.height=200
io-media-generic/aoi: h264_decoder: Entry IterateOutputFormats
io-media-generic/aoi: H264_decoder: IterateOutputFormats-channelFormat_t fmt1 =910408
io-media-generic/aoi: H264_decoder:fmt1=910408 fmt1->mf.u.video.width=300,fmt1->mf.u.video.height=200
io-media-generic/aoi: H264_decoder:c->direction=2,c->element.ID=h264videoOut
io-media-generic/aoi: H264_decoder:c->format.mf.u.video.width=0,c->format.mf.u.video.height=0
io-media-generic/aoi: h264_decoder: cnum = *cookie=4
io-media-generic/aoi: H264_decoder: fmt2=910408,fmt2->mf.u.video.width=300,fmt2->mf.u.video.height=200
io-media-generic/aoi: h264_decoder: fmt->mf.fourcc = MmFOURCC('Y','V','U','9')=961893977
io-media-generic/aoi: Gf_Writer: Entry RateInputFormat
io-media-generic/aoi: Gf_Writer:MmFormat_t fmt1=909288,fmt->mf.mtype.width=300,fmt->mf.mtype.height=200
io-media-generic/aoi: Gf_Writer: fmt->mf.mtype=2
io-media-generic/aoi: GfWriter attaching device 0000,0000,0.
io-media-generic/aoi: GfWriter given a FOURCC of 'YVU9'.
io-media-generic/aoi: layer index : 1
io-media-generic/aoi: Gf_writer:RateInputFormat MmFormat_t *fmt2=909288
io-media-generic/aoi: GfMixer:Entry FourccToGF
io-media-generic/aoi: Gf_writer:FourccToGF-MmFormat_t *fmt=909288
io-media-generic/aoi: Translating FOURCCa 'YVU9'
io-media-generic/aoi: Translating FOURCC1 =961893977
io-media-generic/aoi: Translating FOURCCb'YVU9'
io-media-generic/aoi: Translating FOURCC2 =961893977
io-media-generic/aoi: GfMixer:ret=16785544,Endding----------FOURCCtoGF
io-media-generic/aoi: format = 1310.
io-media-generic/aoi: format = 1018.
io-media-generic/aoi: format = 1420.
io-media-generic/aoi: H264_decoder:Entry-------VerifyOutputFormat
io-media-generic/aoi: H264_decoder: new_fmt->mf.u.video.width=300,new_fmt->mf.u.video.height=200
io-media-generic/aoi: H264_decoder: ofmt->mf.u.video.width=300,ofmt->mf.u.video.height=200
io-media-generic/aoi: H264_decoder: VerifyOutputFormat-MmFormat_t new_fmt=909288,ofmt=910408
io-media-generic/aoi: H264_decoder:VerifyOutputFormat-return 100
io-media-generic/aoi: Gf_Writer: Entry RateInputFormat
io-media-generic/aoi: Gf_Writer:MmFormat_t fmt1=909288,fmt->mf.mtype.width=300,fmt->mf.mtype.height=200
io-media-generic/aoi: h264_decoder: Entry IterateOutputFormats
io-media-generic/aoi: H264_decoder: IterateOutputFormats-channelFormat_t fmt1 =910408
io-media-generic/aoi: H264_decoder:fmt1=910408 fmt1->mf.u.video.width=300,fmt1->mf.u.video.height=200
io-media-generic/aoi: H264_decoder:c->direction=2,c->element.ID=h264videoOut
io-media-generic/aoi: H264_decoder:c->format.mf.u.video.width=0,c->format.mf.u.video.height=0
io-media-generic/aoi: h264_decoder: cnum = *cookie=5
io-media-generic/aoi: H264_decoder: fmt2=910408,fmt2->mf.u.video.width=300,fmt2->mf.u.video.height=200
io-media-generic/aoi: h264_decoder: fmt->mf.fourcc = MmFOURCC('v','4','2','2')=842150998
io-media-generic/aoi: Gf_Writer: Entry RateInputFormat
io-media-generic/aoi: Gf_Writer:MmFormat_t fmt1=909288,fmt->mf.mtype.width=300,fmt->mf.mtype.height=200
io-media-generic/aoi: Gf_Writer: fmt->mf.mtype=2
io-media-generic/aoi: GfWriter attaching device 0000,0000,0.
io-media-generic/aoi: GfWriter given a FOURCC of 'V422'.
io-media-generic/aoi: layer index : 1
io-media-generic/aoi: Gf_writer:RateInputFormat MmFormat_t *fmt2=909288
io-media-generic/aoi: GfMixer:Entry FourccToGF
io-media-generic/aoi: Gf_writer:FourccToGF-MmFormat_t *fmt=909288
io-media-generic/aoi: Translating FOURCCa 'V422'
io-media-generic/aoi: Translating FOURCC1 =842150998
io-media-generic/aoi: Translating FOURCCb'V422'
io-media-generic/aoi: Translating FOURCC2 =842150998
io-media-generic/aoi: GfMixer:ret=67117840,Endding----------FOURCCtoGF
io-media-generic/aoi: format = 1310.
io-media-generic/aoi: format = 1018.
io-media-generic/aoi: format = 1420.
io-media-generic/aoi: H264_decoder:Entry-------VerifyOutputFormat
io-media-generic/aoi: H264_decoder: new_fmt->mf.u.video.width=300,new_fmt->mf.u.video.height=200
io-media-generic/aoi: H264_decoder: ofmt->mf.u.video.width=300,ofmt->mf.u.video.height=200
io-media-generic/aoi: H264_decoder: VerifyOutputFormat-MmFormat_t new_fmt=909288,ofmt=910408
io-media-generic/aoi: H264_decoder:VerifyOutputFormat-return 100
io-media-generic/aoi: Gf_Writer: Entry RateInputFormat
io-media-generic/aoi: Gf_Writer:MmFormat_t fmt1=909288,fmt->mf.mtype.width=300,fmt->mf.mtype.height=200
io-media-generic/aoi: h264_decoder: Entry IterateOutputFormats
io-media-generic/aoi: H264_decoder: IterateOutputFormats-channelFormat_t fmt1 =910408
io-media-generic/aoi: H264_decoder:fmt1=910408 fmt1->mf.u.video.width=300,fmt1->mf.u.video.height=200
io-media-generic/aoi: H264_decoder:c->direction=2,c->element.ID=h264videoOut
io-media-generic/aoi: H264_decoder:c->format.mf.u.video.width=0,c->format.mf.u.video.height=0
io-media-generic/aoi: h264_decoder: cnum = *cookie=6
io-media-generic/aoi: H264_decoder: fmt2=910408,fmt2->mf.u.video.width=300,fmt2->mf.u.video.height=200
io-media-generic/aoi: h264_decoder: fmt->mf.fourcc = MmFOURCC('','U','P','S')=1397773600
io-media-generic/aoi: Gf_Writer: Entry RateInputFormat
io-media-generic/aoi: Gf_Writer:MmFormat_t fmt1=909288,fmt->mf.mtype.width=300,fmt->mf.mtype.height=200
io-media-generic/aoi: Gf_Writer: fmt->mf.mtype=2
io-media-generic/aoi: GfWriter attaching device 0000,0000,0.
io-media-generic/aoi: GfWriter given a FOURCC of ' UPS'.
io-media-generic/aoi: layer index : 1
io-media-generic/aoi: Gf_writer:RateInputFormat MmFormat_t *fmt2=909288
io-media-generic/aoi: GfMixer:Entry FourccToGF
io-media-generic/aoi: Gf_writer:FourccToGF-MmFormat_t *fmt=909288
io-media-generic/aoi: Translating FOURCCa ' UPS'
io-media-generic/aoi: Translating FOURCC1 =1397773600
io-media-generic/aoi: Translating FOURCCb' UPS'
io-media-generic/aoi: Translating FOURCC2 =1397773600
io-media-generic/aoi: GfMixer:ret=5152,Endding----------FOURCCtoGF
io-media-generic/aoi: format = 1310.
io-media-generic/aoi: format = 1018.
io-media-generic/aoi: format = 1420.
io-media-generic/aoi: H264_decoder:Entry-------VerifyOutputFormat
io-media-generic/aoi: H264_decoder: new_fmt->mf.u.video.width=300,new_fmt->mf.u.video.height=200
io-media-generic/aoi: H264_decoder: ofmt->mf.u.video.width=300,ofmt->mf.u.video.height=200
io-media-generic/aoi: H264_decoder: VerifyOutputFormat-MmFormat_t new_fmt=909288,ofmt=910408
io-media-generic/aoi: H264_decoder:VerifyOutputFormat-return 100
io-media-generic/aoi: Gf_Writer: Entry RateInputFormat
io-media-generic/aoi: Gf_Writer:MmFormat_t fmt1=909288,fmt->mf.mtype.width=300,fmt->mf.mtype.height=200
io-media-generic/aoi: h264_decoder: Entry IterateOutputFormats
io-media-generic/aoi: H264_decoder: IterateOutputFormats-channelFormat_t fmt1 =910408
io-media-generic/aoi: H264_decoder:fmt1=910408 fmt1->mf.u.video.width=300,fmt1->mf.u.video.height=200
io-media-generic/aoi: H264_decoder:c->direction=2,c->element.ID=h264videoOut
io-media-generic/aoi: H264_decoder:c->format.mf.u.video.width=0,c->format.mf.u.video.height=0
io-media-generic/aoi: h264_decoder: cnum = *cookie=7
io-media-generic/aoi: GF_writer:Entry---------SetInputFormat
io-media-generic/aoi: GfMixer:Entry FourccToGF
io-media-generic/aoi: Gf_writer:FourccToGF-MmFormat_t *fmt=911528
io-media-generic/aoi: Translating FOURCCa ' UPS'
io-media-generic/aoi: Translating FOURCC1 =1397773600
io-media-generic/aoi: Translating FOURCCb' UPS'
io-media-generic/aoi: Translating FOURCC2 =1397773600
io-media-generic/aoi: GfMixer:ret=5152,Endding----------FOURCCtoGF
io-media-generic/aoi: Comming to CreateGFSurfs
io-media-generic/aoi: fo->u.video.width=300,fo->u.video.height=200
io-media-generic/aoi: GfWriter attaching device 0000,0000,0.
io-media-generic/aoi: attached to layer 1.
io-media-generic/aoi: format = 1310.
io-media-generic/aoi: format = 1018.
io-media-generic/aoi: format = 1420.
io-media-generic/aoi: format_match= 75.
io-media-generic/aoi: gf_writer: Using format 1420
io-media-generic/aoi: scaling to 479
io-media-generic/aoi: UpdateTargetCoords dst_view_h = 479
io-media-generic/aoi: UpdateTargetCoords mult=2.395000
io-media-generic/aoi: UpdateTargetCoords src_height = 200, disph=479
io-media-generic/aoi: scale screen 800 x 480, display surfaces of 718 x 479,
io-media-generic/aoi: GF: c->format.mf.mtype =0x2,0x2,MEDIA_TYPE_SUBPICTURE=10
imx35_layer_set_dest_viewport
imx35_layer_program enter
imx35_wait_vsync
io-media-generic/aoi: H264_decoder:Entry----SetOutputFormat
io-media-generic/aoi: H264_decoder:MmFormat_t fo =911528,fo->mf.u.video.width=300,fo->mf.u.video.height=200
io-media-generic/aoi: h264_decoder->SetOutputFormat ' UPS', 0x16
io-media-generic/aoi: H264_decoder: Endding setoutputformat-return mm_ok
io-media-generic/aoi: Gf_Writer: Entry SetMediaOutput
io-media-generic/trackplayer: The gf_writer filter accepted input from queue_filter
io-media-generic/mmf: Setting long resource 'StreamerStickyError' (value='0')
io-media-generic/aoi: GfMixer SetResource.
io-media-generic/aoi: GfMixer HandleHiliteResource.
io-media-generic/aoi: MmFinalizeGraph(): couldn't register a MM_EV_STATE_TRANSITION_COMPLETE callback err = 48
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi=NULL
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: Gf_Writer: Entry IterateInputChannels
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: Gf_Writer: Entry IterateInputChannels
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: Gf_Writer: Entry IterateInputChannels
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: h264_decoder:Entry IterateInputChannels
io-media-generic/aoi: h264_decoder:*cookie=0
io-media-generic/aoi: f->ichannels[0].element.ID=h264videoIn,ichannels[0].flags=19,direction=1
io-media-generic/aoi: width=352, height=288
io-media-generic/aoi: h264_decoder:Ending IterateInputChannels
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: h264_decoder:Entry IterateInputChannels
io-media-generic/aoi: h264_decoder:*cookie=1
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi=NULL
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: Gf_Writer: Entry IterateInputChannels
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: Gf_Writer: Entry IterateInputChannels
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: Gf_Writer: Entry IterateInputChannels
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: h264_decoder:Entry IterateInputChannels
io-media-generic/aoi: h264_decoder:*cookie=0
io-media-generic/aoi: f->ichannels[0].element.ID=h264videoIn,ichannels[0].flags=19,direction=1
io-media-generic/aoi: width=352, height=288
io-media-generic/aoi: h264_decoder:Ending IterateInputChannels
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: h264_decoder:Entry IterateInputChannels
io-media-generic/aoi: h264_decoder:*cookie=1
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi=NULL
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: Gf_Writer: Entry IterateInputChannels
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: Gf_Writer: Entry IterateInputChannels
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: Gf_Writer: Entry IterateInputChannels
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: h264_decoder:Entry IterateInputChannels
io-media-generic/aoi: h264_decoder:*cookie=0
io-media-generic/aoi: f->ichannels[0].element.ID=h264videoIn,ichannels[0].flags=19,direction=1
io-media-generic/aoi: width=352, height=288
io-media-generic/aoi: h264_decoder:Ending IterateInputChannels
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: h264_decoder:Entry IterateInputChannels
io-media-generic/aoi: h264_decoder:*cookie=1
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_INPUT d=1
io-media-generic/aoi: medialib:MmIterateChannels,mi!=NULL,return mi->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() for VideoCard0 -> input-0 84 x 32768 bytes
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28010000, pad
dr = 0x822f0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28050000, pad
dr = 0x86a00000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28090000, pad
dr = 0x868b0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 280d0000, pad
dr = 0x86240000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28110000, pad
dr = 0x879a0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28150000, pad
dr = 0x856f0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28190000, pad
dr = 0x860e0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 281d0000, pad
dr = 0x872e0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28210000, pad
dr = 0x875a0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28250000, pad
dr = 0x82840000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28290000, pad
dr = 0x86bd0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 282d0000, pad
dr = 0x86b00000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28310000, pad
dr = 0x863a0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28350000, pad
dr = 0x870f0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28390000, pad
dr = 0x822b0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 283d0000, pad
dr = 0x86870000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28410000, pad
dr = 0x86200000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28450000, pad
dr = 0x860a0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28490000, pad
dr = 0x872a0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 284d0000, pad
dr = 0x87560000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28510000, pad
dr = 0x82800000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28550000, pad
dr = 0x86ac0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28590000, pad
dr = 0x870b0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 285d0000, pad
dr = 0x82270000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28610000, pad
dr = 0x86830000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28650000, pad
dr = 0x861c0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28690000, pad
dr = 0x86060000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 286d0000, pad
dr = 0x87260000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28710000, pad
dr = 0x87520000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28750000, pad
dr = 0x86a80000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28790000, pad
dr = 0x87070000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 287d0000, pad
dr = 0x82230000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28810000, pad
dr = 0x867f0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28850000, pad
dr = 0x86020000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28890000, pad
dr = 0x874e0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 288d0000, pad
dr = 0x87030000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28910000, pad
dr = 0x821f0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28950000, pad
dr = 0x867b0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28990000, pad
dr = 0x85fe0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 289d0000, pad
dr = 0x874a0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28a10000, pad
dr = 0x821b0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28a50000, pad
dr = 0x86770000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28a90000, pad
dr = 0x85fa0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28ad0000, pad
dr = 0x87460000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28b10000, pad
dr = 0x82170000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28b50000, pad
dr = 0x86730000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28b90000, pad
dr = 0x87420000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28bd0000, pad
dr = 0x82130000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28c10000, pad
dr = 0x866f0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28c50000, pad
dr = 0x873e0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28c90000, pad
dr = 0x820f0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28cd0000, pad
dr = 0x866b0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28d10000, pad
dr = 0x873a0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28d50000, pad
dr = 0x820b0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28d90000, pad
dr = 0x86670000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28dd0000, pad
dr = 0x87360000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28e10000, pad
dr = 0x82070000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28e50000, pad
dr = 0x86630000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28e90000, pad
dr = 0x82030000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28ed0000, pad
dr = 0x865f0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28f10000, pad
dr = 0x81ff0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28f50000, pad
dr = 0x865b0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28f90000, pad
dr = 0x81fb0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 28fd0000, pad
dr = 0x86570000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 29010000, pad
dr = 0x81f70000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 29050000, pad
dr = 0x86530000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 29090000, pad
dr = 0x81f30000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 290d0000, pad
dr = 0x864f0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 29110000, pad
dr = 0x81ef0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 29150000, pad
dr = 0x864b0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 29190000, pad
dr = 0x81eb0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 291d0000, pad
dr = 0x86470000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 29210000, pad
dr = 0x81e70000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 29250000, pad
dr = 0x81e30000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 29290000, pad
dr = 0x81df0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 292d0000, pad
dr = 0x81db0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 29310000, pad
dr = 0x81d70000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 29350000, pad
dr = 0x81d30000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 29390000, pad
dr = 0x81cf0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 293d0000, pad
dr = 0x81cb0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 29410000, pad
dr = 0x81c70000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 29450000, pad
dr = 0x81c30000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 29490000, pad
dr = 0x81bf0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 294d0000, pad
dr = 0x81bb0000.
io-media-generic/aoi: GFMemoryAllocator->AllocateMemoryPool() Created surface is 1216 x 200, 486400 bytes big @ 29510000, pad
dr = 0x81b70000.
io-media-generic/aoi: gf_writer:allocateMemoryPool Endding return MM-ok
io-media-generic/aoi: gf_writer:Entry--------GetBufferInfo
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/aoi: mp4_parser INPUT seeing nbuffer = 51, bsize = 32768 bytes
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/aoi: mp4_parser: Entry----------IterateOutputChannels
io-media-generic/aoi: mp4_parser: *cookie=0
io-media-generic/aoi: mp4_parser: f->user->ochannel_count=2
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/aoi: mp4_parser: Entry----------IterateOutputChannels
io-media-generic/aoi: mp4_parser: *cookie=1
io-media-generic/aoi: mp4_parser: f->user->ochannel_count=2
io-media-generic/aoi: gf_writer:Entry--------GetBufferInfo
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/aoi: mp4_parser: Entry----------IterateOutputChannels
io-media-generic/aoi: mp4_parser: *cookie=2
io-media-generic/aoi: mp4_parser: f->user->ochannel_count=2
io-media-generic/aoi: mp4_parser: *cookie) >= f->user->ochannel_count.return NULL
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/aoi: h264_decoder INPUT seeing nbuffer = 84, bsize = 32768 bytes
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/aoi: medialib:Entry------------MmIterateChannels
io-media-generic/aoi: medialib:MmIterateChannels,CHANNEL_OUTPUT d=2
io-media-generic/aoi: medialib:MmIterateChannels,mo!=NULL,return mo->IterateChannels(f,cookie)
io-media-generic/aoi: h264_decoder: Entry-- IterateOutputChannels
io-media-generic/aoi: h264_decoder: Endding--IterateOutputChannels,retrun &f->ochannels[0]
Process 655386 (io-media-generic) terminated SIGSEGV code=1 fltno=11 ip=00000000 mapaddr=00083000.
imx35_layer_program enter
00:10:32 | ERRO | _attachinput |3694| Could not attach input (/media/drive///test.mp4) to controlcontext defa
ult (fid=2). errno=536870915
00:10:32 | ERRO | _play |3138| Could not attach file '/media/drive///test.mp4'
00:10:32 | ERRO | _checkiomevents |947 | Could not read events from io-media. Bad file descriptor
00:10:32 | ERRO | _getstatus |4739| Graph failed to return state (Bad file descriptor)
00:10:32 | ERRO | _checkiomevents |947 | Could not read events from io-media. Bad file descriptor
00:10:32 | ERRO | _getstatus |4739| Graph failed to return state (Bad file descriptor)
00:10:32 | CRIT | _destroygraph |3308| Could not destroy graph. Leaking a graph. (9)
00:10:32 | ERRO | _getgraph |3434| Could not create graph. device=/dev/io-media/graphs/trackplayer, name=d
efault
00:10:32 | ERRO | _play |3102| Could not create a graph
00:10:32 | ERRO | _getgraph |3434| Could not create graph. device=/dev/io-media/graphs/trackplayer, name=d
efault
00:10:32 | ERRO | _play |3102| Could not create a graph
00:10:32 | ERRO | _getgraph |3434| Could not create graph. device=/dev/io-media/graphs/trackplayer, name=d
efault
00:10:32 | ERRO | _play |3102| Could not create a graph
00:10:32 | ERRO | _getgraph |3434| Could not create graph. device=/dev/io-media/graphs/trackplayer, name=d
efault
00:10:32 | ERRO | _play |3102| Could not create a graph
00:10:32 | ERRO | _playuntilok |5553| Stopping playback because 5 errors were hit consecutively while playing
track session 1
15Kailen High2010-07-26T10:29:31Z