Project Home
Project Home
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - Customer config requirement - reasonable ?: (6 Items)
   
Customer config requirement - reasonable ?  
Hi,

My customer has the following requirements for media support
They'll be using X86 on 6.4.1 or 6.4.2.

"
 
Could you point us to how media is handled in the OS?   For example, in our OS we use a media server kit -- which 
handles audio/video to display memory and audio outputs.  The media server kit also handles "translators" to decode 
various media types.  There is essentially server to go through to decode all media.   
How is that different in QNX?
 
Here is a use future case:  Let's suppose I have an m2ts transport stream video that came from an AVCHD camcorder.  
Video is h.264 layer 10 / AVC.  Audio is Dolby AC3.   In what state are the decoders for QNX?  Experimental, in 
development, or mature / production ready.   This isn't an immediate use case we need -- but is a future use case we 
need to consider.
 
Here is a more common use case:  
MPEG 4 layer 2 video with either MP3 or ACC audio.   Let's suppose that video is encoded with a Divx encoder.   What 
state are QNX decoders for this video / audio format?    Is additional licensing required for these codecs?
 
Dolby AC3 audio decode support -- Is there a software codec already in existence and available through QNX -- what path 
through Dolby would be necessary to license it?   This is not needed right away... but helps to know what is involved.

"

I know we have an AC3 codec for X86 - are there any 3rd party license issues with it ? There is mention of Intel in the 
add-on package, but it's not clear to me what's required.

I see we have H.264, MP2 and MP4 support, but does DIVX complicate things ?

Please can I get some answers to the customer's questions ? 

Thanks !

Dave
Re: Customer config requirement - reasonable ?  
> Hi,
> 
> My customer has the following requirements for media support
> They'll be using X86 on 6.4.1 or 6.4.2.
> 
> "
>  
> Could you point us to how media is handled in the OS?   For example, in our OS
>  we use a media server kit -- which handles audio/video to display memory and 
> audio outputs.  The media server kit also handles "translators" to decode 
> various media types.  There is essentially server to go through to decode all 
> media.   
> How is that different in QNX?

I think this is well answered by our documentation.  Best to start with "Introduction to the MME".


>  
> Here is a use future case:  Let's suppose I have an m2ts transport stream 
> video that came from an AVCHD camcorder.  Video is h.264 layer 10 / AVC.  
> Audio is Dolby AC3.   In what state are the decoders for QNX?  Experimental, 
> in development, or mature / production ready.   This isn't an immediate use 
> case we need -- but is a future use case we need to consider.

Currently we don't have mpeg2ts support.   This is something that can be done, just hasn't been done yet.
We do have an H.264 & AC3 decoders for intel.  Other platforms can be done also.   H.264 and AC3 are released with MM 1.2 already and are acclerated using IPP.



>  
> Here is a more common use case:  
> MPEG 4 layer 2 video with either MP3 or ACC audio.   Let's suppose that video 
> is encoded with a Divx encoder.   What state are QNX decoders for this video /
>  audio format?    Is additional licensing required for these codecs?

See our licensing guide for this information.  It is included in the MM 1.2 GA package.

mpeg4 parser = GA
mp3 decoder (software) = GA
aac decoder (software) = GA
mpeg4-video decoder (intel IPP) = GA


> Dolby AC3 audio decode support -- Is there a software codec already in 
> existence and available through QNX -- what path through Dolby would be 
> necessary to license it?   This is not needed right away... but helps to know 
> what is involved.

Yes.  GA with our Intel IPP MM 1.2 package.  See the licensing guide.


> 
> "
> 
> I know we have an AC3 codec for X86 - are there any 3rd party license issues 
> with it ? There is mention of Intel in the add-on package, but it's not clear 
> to me what's required.

See the licensing guide.

> 
> I see we have H.264, MP2 and MP4 support, but does DIVX complicate things ?

DIVX 4+ is an mpeg4 video codec.  If you need divx 3 then it may require some work.

> 
> Please can I get some answers to the customer's questions ? 
> 
> Thanks !
> 
> Dave


RE: Customer config requirement - reasonable ?  
Thanks for your reply Dan !
 
One thing - I am not sure what licensing guide you are referring to. I downloaded the whole 1.2 GA doc. zip (took a 
while at 2KB/s which is all the site would give me today on my 12Mbps link) - but did not see anything labelled 
'licensing' guide.
 
I found our 'general' licensing information, but it does not seem to deal with any details relating to MME.
 
If I can't find it easily, I doubt that customers can...
 
What am I missing ?
 
Thanks !
 
Dave

________________________________

From: Dan Cardamore [mailto:community-noreply@qnx.com]
Sent: Tue 12/8/2009 7:08 AM
To: general-multimedia
Subject: Re: Customer config requirement - reasonable ?



> Hi,
>
> My customer has the following requirements for media support
> They'll be using X86 on 6.4.1 or 6.4.2.
>
> "
> 
> Could you point us to how media is handled in the OS?   For example, in our OS
>  we use a media server kit -- which handles audio/video to display memory and
> audio outputs.  The media server kit also handles "translators" to decode
> various media types.  There is essentially server to go through to decode all
> media.  
> How is that different in QNX?

I think this is well answered by our documentation.  Best to start with "Introduction to the MME".


> 
> Here is a use future case:  Let's suppose I have an m2ts transport stream
> video that came from an AVCHD camcorder.  Video is h.264 layer 10 / AVC. 
> Audio is Dolby AC3.   In what state are the decoders for QNX?  Experimental,
> in development, or mature / production ready.   This isn't an immediate use
> case we need -- but is a future use case we need to consider.

Currently we don't have mpeg2ts support.   This is something that can be done, just hasn't been done yet.
We do have an H.264 & AC3 decoders for intel.  Other platforms can be done also.   H.264 and AC3 are released with MM 1.2 already and are acclerated using IPP.



> 
> Here is a more common use case: 
> MPEG 4 layer 2 video with either MP3 or ACC audio.   Let's suppose that video
> is encoded with a Divx encoder.   What state are QNX decoders for this video /
>  audio format?    Is additional licensing required for these codecs?

See our licensing guide for this information.  It is included in the MM 1.2 GA package.

mpeg4 parser = GA
mp3 decoder (software) = GA
aac decoder (software) = GA
mpeg4-video decoder (intel IPP) = GA


> Dolby AC3 audio decode support -- Is there a software codec already in
> existence and available through QNX -- what path through Dolby would be
> necessary to license it?   This is not needed right away... but helps to know
> what is involved.

Yes.  GA with our Intel IPP MM 1.2 package.  See the licensing guide.


>
> "
>
> I know we have an AC3 codec for X86 - are there any 3rd party license issues
> with it ? There is mention of Intel in the add-on package, but it's not clear
> to me what's required.

See the licensing guide.

>
> I see we have H.264, MP2 and MP4 support, but does DIVX complicate things ?

DIVX 4+ is an mpeg4 video codec.  If you need divx 3 then it may require some work.

>
> Please can I get some answers to the customer's questions ?
>
> Thanks !
>
> Dave






_______________________________________________

General
http://community.qnx.com/sf/go/post43358



Attachment: Text winmail.dat 6.53 KB
Re: RE: Customer config requirement - reasonable ?  
On the "Project Home" tab in this project there is a "Read the Legal Stuff:  Licenses(s)" section.  If you read through 
that it has the info you're looking for as well as a link to the document.

Here is a link to the doc anyways:
http://www.qnx.com/download/feature.html?programid=16860
RE: RE: Customer config requirement - reasonable ?  
Thanks Dan,
 
Now I finally see what you mean - under the 'Read the Legal Stuff' there's a link to Foundry terms of use on pegasus.ott
.qnx.com that is inacessible from outside, and a 'supplemental license' that links to 'coming soon'. I suggest that this
 needs some work.
 
The link to the development suite license does work and does seem to have some good information, thanks.
 
Regards
 
Dave

________________________________

From: Dan Cardamore [mailto:community-noreply@qnx.com]
Sent: Tue 12/8/2009 11:29 AM
To: general-multimedia
Subject: Re: RE: Customer config requirement - reasonable ?



On the "Project Home" tab in this project there is a "Read the Legal Stuff:  Licenses(s)" section.  If you read through 
that it has the info you're looking for as well as a link to the document.

Here is a link to the doc anyways:
http://www.qnx.com/download/feature.html?programid=16860



_______________________________________________

General
http://community.qnx.com/sf/go/post43386



Attachment: Text winmail.dat 4.1 KB
Re: RE: RE: Customer config requirement - reasonable ?  
Foundry terms are interesting, but not the ones that are relevant to this discussion.

You need the link http://licensing.qnx.com/license-guide/ which is listed there and should be externally accessible.