{"push_id":663865748,"size":2,"distinct_size":2,"ref":"refs/heads/opti-5.1","head":"3ae498986e5a6e2c7d24d180ca03370e0b51fb60","before":"ddf33cb2f1210eff48e79622143431978fc01609","commits":[{"sha":"244f5a4f16ba86472440d9a034b257503fcb3ca2","author":{"email":"3ce769fcca9b899e0f55f72e4a3c60028561bd28@google.com","name":"Robert Shih"},"message":"ESQueue:use 0x000001 instead of 0x00000001 as sync word in H264/MPEG_VIDEO\n\nH264/MPEG_VIDEO sync words can be either 0x000001 (3 bytes) or\n0x00000001 (4 bytes); simply searching for 0x000001 in appendData\nsuffices because:\n\n1. 0x000001 is a suffix of 0x00000001, as such we would continue to\n   identify all sync words that we used to identify originally.\n\n2. the parsing logic downstream of appendData in\n   dequeueAccessUnitMPEGVideo and dequeueAccessUnitH264\n   can both handle 0x000001.\n\nBug: 19900317\nChange-Id: Iac42aad74563d056a443b4396eacbae0f7a4738b","distinct":true,"url":"https://api.github.com/repos/OptiPop/frameworks_av/commits/244f5a4f16ba86472440d9a034b257503fcb3ca2"},{"sha":"3ae498986e5a6e2c7d24d180ca03370e0b51fb60","author":{"email":"4bada73e411a9c678a318a79d04d7df4a5fc4429@gmail.com","name":"Chet Kener"},"message":"Merge \"ESQueue:use 0x000001 instead of 0x00000001 as sync word in H264/MPEG_VIDEO\" into opti-5.1","distinct":true,"url":"https://api.github.com/repos/OptiPop/frameworks_av/commits/3ae498986e5a6e2c7d24d180ca03370e0b51fb60"}]}