[Helix-client-dev] X-MP3-DRAFT-00

_______________________________________________
Helix-client-dev mailing list
Helix-client-dev <at> helixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/helix-client-dev

[Helix-client-dev] Hold commit to hxclient_3_6_1

_______________________________________________
Helix-client-dev mailing list
Helix-client-dev <at> helixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/helix-client-dev

[Helix-client-dev] CR/CN: Use ALSA sound on Linux

Fixed to actually use ALSA on Linux when HELIX_FEATURE_ALSA is defined,
instead of just compiling and ignoring it!

Index: hxaudev.cpp
===================================================================
RCS file: /cvsroot/audio/device/hxaudev.cpp,v
retrieving revision 1.40
diff -u -w -r1.40 hxaudev.cpp
--- hxaudev.cpp 14 Jun 2011 02:02:08 -0000      1.40
+++ hxaudev.cpp 16 Mar 2012 20:57:01 -0000
@@ -256,7 +256,7 @@
  #endif

  #if defined(_LINUX) ||  defined(_FREEBSD) || defined(_NETBSD)
-# if defined(HELIX_FEATURE_OLPC) || defined(HELIX_CONFIG_MOBLIN)
+# if defined(HELIX_FEATURE_OLPC) || defined(HELIX_CONFIG_MOBLIN) || 
defined(HELIX_FEATURE_ALSA)
      UINT16 nSoundDriver = kALSA;
  #elif defined(ANDROID)
      UINT16 nSoundDriver = kAndroidAudio;

[Helix-client-dev] CR/CN: Use ALSA sound on Linux

Fixed to actually use ALSA on Linux when HELIX_FEATURE_ALSA is defined,
instead of just compiling and ignoring it!

Index: hxaudev.cpp
===================================================================
RCS file: /cvsroot/audio/device/hxaudev.cpp,v
retrieving revision 1.40
diff -u -w -r1.40 hxaudev.cpp
--- hxaudev.cpp 14 Jun 2011 02:02:08 -0000      1.40
+++ hxaudev.cpp 16 Mar 2012 20:57:01 -0000
@@ -256,7 +256,7 @@
  #endif

  #if defined(_LINUX) ||  defined(_FREEBSD) || defined(_NETBSD)
-# if defined(HELIX_FEATURE_OLPC) || defined(HELIX_CONFIG_MOBLIN)
+# if defined(HELIX_FEATURE_OLPC) || defined(HELIX_CONFIG_MOBLIN) || 
defined(HELIX_FEATURE_ALSA)
      UINT16 nSoundDriver = kALSA;
  #elif defined(ANDROID)
      UINT16 nSoundDriver = kAndroidAudio;

[Helix-client-dev] RE: Hold commit to hxclient_3_6_1

_______________________________________________
Helix-client-dev mailing list
Helix-client-dev <at> helixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/helix-client-dev

[Helix-client-dev] Hold commit to hxclient_3_6_1

_______________________________________________
Helix-client-dev mailing list
Helix-client-dev <at> helixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/helix-client-dev

[Helix-client-dev] CR/CN: GMP Meta-editor fixes: Bug #18367, Issue #18358. [GMPMetaEditor branch]

Modified by: pbasic at real.com
Date: 2011/10/28
Project: GMPMetaEditor (meta3gp.exe)

Synopsis:
GMP Meta-editor fixes: Bug #18367, Issue #18358. [GMPMetaEditor branch]

Details:
1.) Fixed GMP Meta-editor (Redmine) Bug #18367: "meta3gp error with
artist/composer over 255 chars".

The code has been corrected to pass the value of meta-flavor parameter
to all the routines which check the length of meta-data string
parameters.

2.) Fixed GMP Meta-editor (Redmine) Issue #18358: "Metadata tool
increases filesize although no metadata is added".

The final output file contains a 'free' atom following the 'moov'
atom.  The space required for sample tables contained by the 'moov'
atom seems to be overestimated by the mp4-filewriter.  With this
strategy, the 'free' atom can sometimes account for more than 10% of
output file size which is not desirable.  Quick fix is to employ
already existing mp4-filewriter's "ForceMoovFirst" option.  In this
mode, mp4-filewriter uses a second temporary file to store the 'mdat'
samples while it builds the sample tables in the 'moov' atom.  The
filewriter then simply appends 'mdat' atom right after the 'moov' atom
without putting an extraneous 'free' atom between them.  Usage of a
second temporary file keeps the final output file size to the minimum,
but probably reduces Meta-editor tool's performance.  Some testing on
larger files is required to determine whether more elaborate fixes are
required at this moment.

Files Modified:
datatype/tools/dtdriver/apps/meta3gp/main.cpp
datatype/tools/dtdriver/engine/ffdriver.cpp
datatype/tools/dtdriver/engine/pub/ffdriver.h

Platforms and Profiles Affected:
All

Image Size and Heap Use impact:
None

Platforms and Profiles Build Verified:
system id: win32-i386-vc7
profile: helix-client-all-defines

Platforms and Profiles Functionality Verified:
x86 Windows XP SP2

Branch:
GMPMetaEditor

Copyright assignment:
I am a RealNetworks employee or contractor.

_______________________________________________
Helix-client-dev mailing list
Helix-client-dev <at> helixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/helix-client-dev

[Helix-client-dev] Backup branch for Huawei 7x27 project

_______________________________________________
Helix-client-dev mailing list
Helix-client-dev <at> helixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/helix-client-dev

[Helix-client-dev] RE: Backup branch for Thinkpad project

Done.
361atlas Unfreeze now.

Hi, Shuo
Please use hxclient_3_6_1_wolf for thinkpad daily build.

Thanks
Joe

-----Original Message-----
From: Joe Li 
Sent: Friday, October 14, 2011 7:01 PM
To: helix-client-dev <at> lists.helixcommunity.org
Cc: Qiang Luo; Sheldon Fu; James Brennan; Charles Chen; Goldi Goel; Helen Hua; Adam Cappio; Lionel
Bouchard; Sai Ramanath; Chris Young; DL-china-helix-client-dev; Jamie Gordon; Frank Lan
Subject: Backup branch for Thinkpad project

Hi, all

Since Thinkpad project will reach to final release sooner, we are going to branch it out 361atlas for source
code maintainmenting.

Branch name is: hxclient_3_6_1_wolf

Please hold off checkins to the branch after 2011-10-14 20:00 （BeiJing time） until next unfreeze mail.
Thanks
Joe


-----Original Message-----
From: Jamie Gordon 
Sent: Saturday, August 27, 2011 3:45 AM
To: Frank Lan
Cc: Qiang Luo; Sheldon Fu; James Brennan; Charles Chen; Goldi Goel; Helen Hua; Adam Cappio; Lionel
Bouchard; Sai Ramanath; Chris Young; china-helix-client-dev <at> real.com; china-helix-client-qa <at> real.com
Subject: Re: Backup branch for Apollo project - seek feedback

Yup, sounds good!

On 8/26/2011 4:18 AM, Frank Lan wrote:
> All,
> 
> Several months ago, when we decided to use 361 as a common branch for 
> all products development, Qiang ever suggested making backup branch for 
> each product when it is near to code freeze timeline, so that it can 
> avoid of being impacted by other products. I think it’s a very good idea.
> 
> Now it’s time to branch out Lenovo Apollo project (ship @ Sep/Oct 
> timeline). Currently there are another 10 projects base on 361 branch in 
> parallel. I’m thinking about to create the branch name as 
> “hxclient_3_6_1_≤animal name>” for all backup branches of products.
> 
> For example, Apollo backup branch name to be “hxclient_3_6_1_tiger”, 
> maybe LePAD branch in future could be “hxclient_3_6_1_lion”, ThinkPAD 
> tablet could be “hxclient_3_6_1_wolf” etc., in this way, we won’t leak 
> any customer or confidential information from branch name.
> 
> Any idea about this? China team will make backup branch from next Monday 
> if there’s no other opinion. Thank you.
> 
> Regards,
> 
> Frank Lan
> 
> ------------------------------------------------------------------------
> 
> *From:*Joe Li
> *Sent:* Friday, August 26, 2011 6:08 PM
> *To:* helix-client-dev <at> lists.helixcommunity.org
> *Cc:* china-helix-client-qa <at> real.com; china-helix-client-dev <at> real.com; 
> Frank Lan; Richard Qu; James Brennan; Helen Hua
> *Subject:* RE: for Apollo project branch out //branch appollo from 
> 361atlas at 2011/08/26
> 
> Hi, all
> 
> Since Apollo will reach to final release sooner, we are going to branch 
> it out 361atlas for source code maintainmenting.
> 
> Please hold off checkins to the branch after 2011-8-26 20:00 （BeiJing 
> time）until next unfreeze mail.
> 
> Do you have any idea for the Branch name?
> 
> hxclient_3_6_1A_atlas? Or anything else?
> 
> Thanks
> 
> Joe
> 
> ------------------------------------------------------------------------
> 
> *From:*Helen Hua
> *Sent:* Friday, August 26, 2011 5:00 PM
> *To:* Joe Li
> *Cc:* china-helix-client-qa <at> real.com; china-helix-client-dev <at> real.com; 
> Frank Lan; Richard Qu; James Brennan; Helen Hua
> *Subject:* for Apollo project branch out
> *Importance:* High
> 
> Hi, Joe,
> 
> In order to tune Apollo for production, Please branch out for Apollo 
> project, thanks.
> 
> Best Regards
> 
> Helen
> 

_______________________________________________
Helix-client-dev mailing list
Helix-client-dev <at> helixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/helix-client-dev

[Helix-client-dev] Backup branch for Thinkpad project

Hi, all

Since Thinkpad project will reach to final release sooner, we are going to branch it out 361atlas for source
code maintainmenting.

Branch name is: hxclient_3_6_1_wolf

Please hold off checkins to the branch after 2011-10-14 20:00 （BeiJing time） until next unfreeze mail.
Thanks
Joe


-----Original Message-----
From: Jamie Gordon 
Sent: Saturday, August 27, 2011 3:45 AM
To: Frank Lan
Cc: Qiang Luo; Sheldon Fu; James Brennan; Charles Chen; Goldi Goel; Helen Hua; Adam Cappio; Lionel
Bouchard; Sai Ramanath; Chris Young; china-helix-client-dev <at> real.com; china-helix-client-qa <at> real.com
Subject: Re: Backup branch for Apollo project - seek feedback

Yup, sounds good!

On 8/26/2011 4:18 AM, Frank Lan wrote:
> All,
> 
> Several months ago, when we decided to use 361 as a common branch for 
> all products development, Qiang ever suggested making backup branch for 
> each product when it is near to code freeze timeline, so that it can 
> avoid of being impacted by other products. I think it’s a very good idea.
> 
> Now it’s time to branch out Lenovo Apollo project (ship @ Sep/Oct 
> timeline). Currently there are another 10 projects base on 361 branch in 
> parallel. I’m thinking about to create the branch name as 
> “hxclient_3_6_1_≤animal name>” for all backup branches of products.
> 
> For example, Apollo backup branch name to be “hxclient_3_6_1_tiger”, 
> maybe LePAD branch in future could be “hxclient_3_6_1_lion”, ThinkPAD 
> tablet could be “hxclient_3_6_1_wolf” etc., in this way, we won’t leak 
> any customer or confidential information from branch name.
> 
> Any idea about this? China team will make backup branch from next Monday 
> if there’s no other opinion. Thank you.
> 
> Regards,
> 
> Frank Lan
> 
> ------------------------------------------------------------------------
> 
> *From:*Joe Li
> *Sent:* Friday, August 26, 2011 6:08 PM
> *To:* helix-client-dev <at> lists.helixcommunity.org
> *Cc:* china-helix-client-qa <at> real.com; china-helix-client-dev <at> real.com; 
> Frank Lan; Richard Qu; James Brennan; Helen Hua
> *Subject:* RE: for Apollo project branch out //branch appollo from 
> 361atlas at 2011/08/26
> 
> Hi, all
> 
> Since Apollo will reach to final release sooner, we are going to branch 
> it out 361atlas for source code maintainmenting.
> 
> Please hold off checkins to the branch after 2011-8-26 20:00 （BeiJing 
> time）until next unfreeze mail.
> 
> Do you have any idea for the Branch name?
> 
> hxclient_3_6_1A_atlas? Or anything else?
> 
> Thanks
> 
> Joe
> 
> ------------------------------------------------------------------------
> 
> *From:*Helen Hua
> *Sent:* Friday, August 26, 2011 5:00 PM
> *To:* Joe Li
> *Cc:* china-helix-client-qa <at> real.com; china-helix-client-dev <at> real.com; 
> Frank Lan; Richard Qu; James Brennan; Helen Hua
> *Subject:* for Apollo project branch out
> *Importance:* High
> 
> Hi, Joe,
> 
> In order to tune Apollo for production, Please branch out for Apollo 
> project, thanks.
> 
> Best Regards
> 
> Helen
> 

_______________________________________________
Helix-client-dev mailing list
Helix-client-dev <at> helixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/helix-client-dev

[Helix-client-dev] RE: Backup branch for Apollo project - seek feedback

Hi,all
Apollo project has been branched from 361atlas.
you can continue work on 361 atlas now;
thanks all

---------------------------------------------------------------------------
Apollo Porject info:
ContextA8, Qualcom8x55

export SYSTEM_ID=android-2.3-arm-qsd_8x55
[0] Set BIF branch (hxclient_3_6_1_tiger_restricted)
[1] Set Target(s) (android_omx)
[2] Set Profile (/media/sda2/helix.0715/build/umakepf/helix-client-android-full)
---------------------------------------------------------------------------
Thanks
Joe


-----Original Message-----
From: Jamie Gordon 
Sent: Saturday, August 27, 2011 3:45 AM
To: Frank Lan
Cc: Qiang Luo; Sheldon Fu; James Brennan; Charles Chen; Goldi Goel; Helen Hua; Adam Cappio; Lionel
Bouchard; Sai Ramanath; Chris Young; china-helix-client-dev <at> real.com; china-helix-client-qa <at> real.com
Subject: Re: Backup branch for Apollo project - seek feedback

Yup, sounds good!

On 8/26/2011 4:18 AM, Frank Lan wrote:
> All,
> 
> Several months ago, when we decided to use 361 as a common branch for 
> all products development, Qiang ever suggested making backup branch for 
> each product when it is near to code freeze timeline, so that it can 
> avoid of being impacted by other products. I think it’s a very good idea.
> 
> Now it’s time to branch out Lenovo Apollo project (ship @ Sep/Oct 
> timeline). Currently there are another 10 projects base on 361 branch in 
> parallel. I’m thinking about to create the branch name as 
> “hxclient_3_6_1_≤animal name>” for all backup branches of products.
> 
> For example, Apollo backup branch name to be “hxclient_3_6_1_tiger”, 
> maybe LePAD branch in future could be “hxclient_3_6_1_lion”, ThinkPAD 
> tablet could be “hxclient_3_6_1_wolf” etc., in this way, we won’t leak 
> any customer or confidential information from branch name.
> 
> Any idea about this? China team will make backup branch from next Monday 
> if there’s no other opinion. Thank you.
> 
> Regards,
> 
> Frank Lan
> 
> ------------------------------------------------------------------------
> 
> *From:*Joe Li
> *Sent:* Friday, August 26, 2011 6:08 PM
> *To:* helix-client-dev <at> lists.helixcommunity.org
> *Cc:* china-helix-client-qa <at> real.com; china-helix-client-dev <at> real.com; 
> Frank Lan; Richard Qu; James Brennan; Helen Hua
> *Subject:* RE: for Apollo project branch out //branch appollo from 
> 361atlas at 2011/08/26
> 
> Hi, all
> 
> Since Apollo will reach to final release sooner, we are going to branch 
> it out 361atlas for source code maintainmenting.
> 
> Please hold off checkins to the branch after 2011-8-26 20:00 （BeiJing 
> time）until next unfreeze mail.
> 
> Do you have any idea for the Branch name?
> 
> hxclient_3_6_1A_atlas? Or anything else?
> 
> Thanks
> 
> Joe
> 
> ------------------------------------------------------------------------
> 
> *From:*Helen Hua
> *Sent:* Friday, August 26, 2011 5:00 PM
> *To:* Joe Li
> *Cc:* china-helix-client-qa <at> real.com; china-helix-client-dev <at> real.com; 
> Frank Lan; Richard Qu; James Brennan; Helen Hua
> *Subject:* for Apollo project branch out
> *Importance:* High
> 
> Hi, Joe,
> 
> In order to tune Apollo for production, Please branch out for Apollo 
> project, thanks.
> 
> Best Regards
> 
> Helen
> 

_______________________________________________
Helix-client-dev mailing list
Helix-client-dev <at> helixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/helix-client-dev