ADTS .aac file support in helix

Email lists > Helix DNA datatypes discussion

Thread: ADTS .aac file support in helix

Search this list only Search all lists
ADTS .aac file support in helix
	2008-03-04 11:35:07

Hi, Is there a support for ADTS .aac file in helix? Looks like while parsing the bit-stream in CAudioSpecificConfig::Read in gaConfig.cpp, SYNC word FFF and ID3 tags are not taken care of. Hence we get wrong configurations. I am using helix-client-s60-50-mmf-mdf-arm profile on CayS210. I did took latest changes from head for gaConfig.cpp to Cays210. I can play ADIF .aac files which doesn't have ID3 tags in it. I shall add the ADTS support if it is not already supported. Please confirm the same. Thanks Praveen
ADTS .aac file support in helix
United States	2008-03-04 17:27:13

Hi Praveen, Eric is the best resource to discuss this issue. He will respond back to you shortly. Thank you, -leina From: nokia-private-dev-bounceshelixcommunity.org [mailto:nokia-private-dev-bounceshelixcommunity.org] On Behalf Of Praveen.Thimmashettynokia.com Sent: Tuesday, March 04, 2008 9:35 AM To: nokia-private-devhelixcommunity.org; datatype-devhelixcommunity.org Subject: [Nokia-private-dev] ADTS .aac file support in helix Hi, Is there a support for ADTS .aac file in helix? Looks like while parsing the bit-stream in CAudioSpecificConfig::Read in gaConfig.cpp, SYNC word FFF and ID3 tags are not taken care of. Hence we get wrong configurations. I am using helix-client-s60-50-mmf-mdf-arm profile on CayS210. I did took latest changes from head for gaConfig.cpp to Cays210. I can play ADIF .aac files which doesn't have ID3 tags in it. I shall add the ADTS support if it is not already supported. Please confirm the same. Thanks Praveen
ADTS .aac file support in helix
Austria	2008-03-05 07:41:48

Content-class: urn:content-classes:message Content-Type: multipart/alternative; ;     boundary="----_=_NextPart_001_01C87E1E.17479FF4" Hi, Is there a support for ADTS .aac file in helix? yes Looks like while parsing the bit-stream in CAudioSpecificConfig::Read in gaConfig.cpp, SYNC word FFF and ID3 tags are not taken care of. Hence we get wrong configurations. It is not CAudioSpecificConfig classes job to deal with either sync or ID3 tags but just to parse the configuration. ID3 tags are dealt with external to this class in datatype/aac/fileformat. Also, ADTS files do not have AudioSpecificConfig - LOAS files do. Which components is invoking CAudioSpecificConfig in you ADTS test? I am using helix-client-s60-50-mmf-mdf-arm profile on CayS210. I did took latest changes from head for gaConfig.cpp to Cays210. I can play ADIF .aac files which doesn't have ID3 tags in it. I shall add the ADTS support if it is not already supported. Please confirm the same. Thanks Praveen _______________________________________________ Nokia-private-dev mailing list Nokia-private-devhelixcommunity.org http://lists.helixcommunity.org/mailman/listinfo/nokia-private-dev
ADTS .aac file support in helix
	2008-03-05 11:50:30

Please find my explanations below. From: ext Milko Boic [mailto:milkoreal.com] Sent: Wednesday, March 05, 2008 7:42 AM To: Thimmashetty Praveen (Nokia-D-MSW/Dallas); nokia-private-devhelixcommunity.org; datatype-devhelixcommunity.org Subject: Re: [Nokia-private-dev] ADTS .aac file support in helix At 09:35 AM 3/4/2008, Praveen.Thimmashettynokia.com wrote: Content-class: urn:content-classes:message Content-Type: multipart/alternative;     ; boundary="----_=_NextPart_001_01C87E1E.17479FF4" Hi, Is there a support for ADTS .aac file in helix? yes Looks like while parsing the bit-stream in CAudioSpecificConfig::Read in gaConfig.cpp, SYNC word FFF and ID3 tags are not taken care of. Hence we get wrong configurations. It is not CAudioSpecificConfig classes job to deal with either sync or ID3 tags but just to parse the configuration. ID3 tags are dealt with external to this class in datatype/aac/fileformat. Also, ADTS files do not have AudioSpecificConfig - LOAS files do. Which components is invoking CAudioSpecificConfig in you ADTS test? Praveen: AAC FIleformat does all the header parsing. But in CAACFileFormat::CreatePacketizer, AACPayloadFormat is not created. This will lead to load a mp4 renderer, which has no details about the header that got parsed at aac fileformat. mp4 renderer is invoking CAudioSpecificConfig, to read the bit-stream configuration. ; I am using helix-client-s60-50-mmf-mdf-arm profile on CayS210. I did took latest changes from head for gaConfig.cpp to Cays210. I can play ADIF .aac files which doesn't have ID3 tags in it. I shall add the ADTS support if it is not already supported. Please confirm the same. Thanks Praveen _______________________________________________ Nokia-private-dev mailing list Nokia-private-devhelixcommunity.org http://lists.helixcommunity.org/mailman/listinfo/nokia-private-dev
ADTS .aac file support in helix
United States	2008-03-14 13:12:33

Further comments inline below... At 10:50 AM 3/5/2008, Praveen.Thimmashettynokia.com wrote: Please find my explanations below. From: ext Milko Boic [ milkoreal.com" eudora="autourl"> mailto:milkoreal.com] Sent: Wednesday, March 05, 2008 7:42 AM To: Thimmashetty Praveen (Nokia-D-MSW/Dallas); nokia-private-devhelixcommunity.org; datatype-devhelixcommunity.org Subject: Re: [Nokia-private-dev] ADTS .aac file support in helix At 09:35 AM 3/4/2008, Praveen.Thimmashettynokia.com wrote: Content-class: urn:content-classes:message Content-Type: multipart/alternative; ;     boundary="----_=_NextPart_001_01C87E1E.17479FF4" Hi, Is there a support for ADTS .aac file in helix? yes Looks like while parsing the bit-stream in CAudioSpecificConfig::Read in gaConfig.cpp, SYNC word FFF and ID3 tags are not taken care of. Hence we get wrong configurations. It is not CAudioSpecificConfig classes job to deal with either sync or ID3 tags but just to parse the configuration. ID3 tags are dealt with external to this class in datatype/aac/fileformat. Also, ADTS files do not have AudioSpecificConfig - LOAS files do. Which components is invoking CAudioSpecificConfig in you ADTS test? Praveen: AAC FIleformat does all the header parsing. But in CAACFileFormat::CreatePacketizer, AACPayloadFormat is not created. That is proper behavior.  We packetize only in non-playback environment for writer compatibility reasons (transcoding case). This will lead to load a mp4 renderer, which has no details about the header that got parsed at aac fileformat. mp4 renderer is invoking CAudioSpecificConfig, to read the bit-stream configuration. 1.) What you are describing is not a consequence of your first observation. 2.) Renderer employs parsing scheme based on type of configuration stored in the first byte of the OpaqueData when mime type of the stream is set to X_HX_AAC_GENERIC. 3.) For ADTS, the configuration scheme is set to 1 . /* configuration types for AAC OpenDecoder() */ enum { ; eAACConfigADIF ;         ; = 0, ;   eAACConfigADTS        ;   = 1, ;   eAACConfigAudioSpecificCfg = 2 } ; 4.) ADTS configuration scheme means that configuration data is the first ADTS frame Trace through the AAC file format and determine that indeed the file you are testing is being detected as ADTS type file and that OpequeData is set per description above. Thanks, Milko I am using helix-client-s60-50-mmf-mdf-arm profile on CayS210. I did took latest changes from head for gaConfig.cpp to Cays210. I can play ADIF .aac files which doesn't have ID3 tags in it. I shall add the ADTS support if it is not already supported. Please confirm the same. Thanks Praveen _______________________________________________ Nokia-private-dev mailing list Nokia-private-devhelixcommunity.org http://lists.helixcommunity.org/mailman/listinfo/nokia-private-dev

[1-5]

about | contact Other archives ( Real Estate discussion Medical topics )