Difference between FourCC codes "avc1" and "avc3"? avc1 with sound prob?

[pxstein]

What is the difference between the two "FourCC" codes "avc1" and "avc3" (when encoding AVC H.264)?

I got the impression that a FourCC "avc1" causes occasionally audio output problems when playing MP4 videos on (some) Android Smartphones.

If I encode the video with "avc3" and same other parameters then audio is working

[LigH.de]

If you get playback issues on devices with lower processing speed, the encoded video complexity might exceed the abilities of the video decoder. The solution may be to restrict the AVC encoder to maximum values of a lower Profile@Level which is more compatible to your device.

I wonder which converter allows you to select an "avc3" FourCC. It is also not easy to find specifications about this format. The only explanation I found so far was in a mailing list for gstreamer:

Amendment 2 of ISO/IEC 14496-15 (AVC file format) is defining a new structure for fragmented MP4 called "avc3". The principal difference between AVC1 and AVC3 is the location of the codec initialisation data (e.g. SPS, PPS). In AVC1 this data is placed in the initial MOOV box (moov.trak.mdia.minf.stbl.stsd.avc1) but in AVC3 this data goes in the first sample of every fragment (i.e. the first sample in each mdat box). The principal reason for avc3 is to make it easier for client implementations, because it removes the requirement to insert the SPS+PPS in to the decoder pipeline every time there is a representation change.

This appears to be rather specific to the Quicktime MOV / ISO Base Media container family. But it seems to change only a small part of the file structure, not the multiplexing structure in general, or the video encoding complexity, so I see no reason why it should support the playback in a noticeable degree.