List Info

Thread: Adding datatype_aac_codec_helixaac to realplay_player_client_engine target




Adding datatype_aac_codec_helixaac to realplay_player_client_engine target
user name
2006-09-30 02:30:32
This AAC codec is from Coding Technology.

This is the only clue that I can find:

datatype/acc/codec/helixacc/platform/win/raac.rc:
VALUE "LegalCopyright",  HXVER_COPYRIGHT "and
Coding Technologies"


We don't seem to have source code to this component, do we?


 > The plan for Balto mentions adding the fixed-point
cross-platform AAC
 > codec under the Cayenne integration area.
 > https://player.helixcommunity.org/2005/dev/plans.html

That page actually says:
Open source, cross platform fixed point AAC code

It doesn't seem like it is correct.


-- 
Daniel Yek


At 11:42 AM 9/28/2006, Haydon Boone wrote:
> > Would this be the Helix one or the CT one?
>
>Helix.
>
> > The plan for Balto mentions adding the fixed-point
cross-platform
> > AAC codec under the Cayenne integration area.
>
>Right. And the codec team subsequently said that this
was unnecessary.
>
> > Does our CT license cover Linux desktops?
>
>Yes, and I believe it's what is already in-use/shipping
in current Linux RP
>10 builds.
>
> > -----Original Message-----
> > From: Donya Shirzad [mailto:dshirzadreal.com]
> > Sent: Wednesday, September 27, 2006 1:30 PM
> > To: hboonereal.com; 'Daniel Yek'; 'Player-dev'
> > Subject: RE: [Player-dev] CN-Client: Adding
datatype_aac_codec_helixaac
> > to realplay_player_client_engine target
> >
> > The plan for Balto mentions adding the fixed-point
cross-platform AAC
> > codec under the Cayenne integration area.  Would
this be the Helix one
> > or the CT one?
> > https://player.helixcommunity.org/2005/dev/plans.html
> >
> > Does our CT license cover Linux desktops?
> >
> > Thanks,
> > - Donya
> >
> > At 10:39 PM -0700 9/26/06, Haydon Boone wrote:
> > >  Is this the RN-developed AAC implementation
or the earlier AAC
> > >implementation that we licensed from Coding
Technologies, prior to
> > >availability of the RN implementation?
> > >
> > >  Opinion expressed by our codec team was
that, for at least the next
> > >version of the desktop RealPlayer products,
there were not significant
> > >gains to be seen in moving away from the CT
implementation, so we
> > >should continue to use it in these products
for this next product
> > cycle...
> > >
> > >-/Haydon
> > >
> > >>  -----Original Message-----
> > >>  From: player-dev-bounceshelixcommunity.org
> > >>  [mailto:player-dev-bounceshelixcommunity.org] On Behalf Of Daniel
> > >> Yek
> > >>  Sent: Tuesday, September 26, 2006 5:49
PM
> > >>  To: Player-dev
> > >>  Subject: [Player-dev] CN-Client: Adding
> > datatype_aac_codec_helixaac
> > >> to realplay_player_client_engine target
> > >>
> > >>  Thanks, Bob.
> > >>
> > >>  This is now checked in.
> > >>
> > >>
> > >>  --
> > >>  Daniel Yek
> > >>
> > >>
> > >>  At 02:12 PM 9/26/2006, Bob Clark wrote:
> > >>  >Looks good, Daniel.
> > >>  >--Bob
> > >>  >
> > >>  >At 07:03 PM 9/25/2006, Daniel Yek
wrote:
> > >>  >
> > >>  >>Modified by: dyekreal.com
> > >>  >>Date: 9/25/2006
> > >>  >>Project: Helix Player
> > >>  >>
> > >>  >>Synopsis: The HEAD branch of
Linux RealPlayer was missing
> > >> components  >>needed to
> > >>  >>   play back raac content. This
change includes the capability.
> > >>  >>
> > >>  >>Overview:
> > >>  >>   It is unclear to me whether
datatype_aac_codec_helixaac
> > >>  was left out
> > >>  >>   intentionally or
unintentionally.
> > >>  >>   I'm adding it now to the BIF
files used by the HEAD branch.
> > >>  >>
> > >>  >>   datatype_h263 exists in
hxplay_player_client_engine module
> > that
> > >>  >>   realplay_player_client_engine
depends on, so it appears
> > >>  to be redundant
> > >>  >>   and removed:
> > >>  >>
> > >>  >>   <module
id="hxplay_player_client_engine"
group="player"
> > >>  type="name_only">
> > >>  >>     ...
> > >>  >>     <dependlist>
> > >>  >>     ...
> > >>  >>     datatype_h263
> > >>  >>     ...
> > >>  >>     </dependlist>
> > >>  >>   </module>
> > >>  >>
> > >>  >>
> > >>  >>Files Modified:
> > >>
> > >> >>$BUILD_ROOT/bif-
> >
cvs/helix/client/build/BIF/realplay_gtk_current.bif
> > >>  >>
> > >>  >>Platforms and Profiles Affected:
> > >>  >>Linux
> > >>  >>
> > >>  >>Platforms and Profiles Build
Verified:
> > >>  >>Profile: helix_client_all_define
> > >>  >>Platform: Fedora Core 5
> > >>  >>
> > >>  >>Platforms and Profiles
Functionality verified:
> > >>  >>Profile: helix_client_all_define
> > >>  >>Platform: Fedora Core 5
> > >>  >>
> > >>  >>Branch: HEAD
> > >>  >>
> > >>  >>Copyright assignment: I am a
RealNetworks employee.
> > >>  >>
> > >>  >>
> > >>  >>Index: realplay_gtk_current.bif
> > >>
> > >>
> >
>>====================================================
===============
> > >>  >>RCS file:
/cvsroot/client/build/BIF/realplay_gtk_current.bif,v
> > >>  >>retrieving revision 1.30
> > >>  >>diff -u -w -r1.30
realplay_gtk_current.bif
> > >>  >>--- realplay_gtk_current.bif   
16 Sep 2005 01:42:37 -0000
> > 1.30
> > >>  >>+++ realplay_gtk_current.bif   
26 Sep 2006 01:54:27 -0000
> > >>  >> -51,8 +51,8 
> > >>  >>          datatype_mp3
> > >>  >>          datatype_mp4
> > >>  >>         
datatype_mp4_audio_renderer
> > >>  >>-        datatype_h263
> > >>  >>          datatype_flash
> > >>  >>+       
datatype_aac_codec_helixaac
> > >>  >>        </dependlist>
> > >>  >>      </module>
> > >>  >>
> > >>  >>
> > >>  >>
> > >>  >>
> > >>  >>--
> > >>  >>Daniel Yek
> > >>


_______________________________________________
Player-dev mailing list
Player-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/play
er-dev
[1]

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