atrocity wrote: 
> I'm using ffmpeg to do the work and can immediately see via its helper
> ffprobe that there are differences in the metadata. A "normal" AAC/M4A
> file starts off with:
> 

This is not metadata (i.e. additiopnal info) but file structure - how
the file is encoded into MPEG4. 

The usual issue is that media files often have the info about the audio
data (i.e where frames starts) and other data placed at the end of the
file after the audio data  - this is no use when streaming when such
data is needed to start playing the audio (i.e. all frame start position
data) is needed  before audio is received. Streamed files can only be
played as they are received - there is no jumping up and down the data
stream which is possible with a file This issue happens with some m4a
podcasts as well where file is expected to be downloaded anbd played
rather than streamed.

If it is this issue - it has been discussed many times in other
threads.

Possible solution is to convert the file with ffmpeg using the
"-movflags faststart"  which moves all the data ("mdat") from start of
file to end of file making it suitable for streaming.

Try somehting like the following - you may need to tweak for your file.

Code:
--------------------
    
  ffmpeg -i input.mp4 -codec copy -map 0 -movflags faststart output.mp4
  
--------------------


------------------------------------------------------------------------
bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806
View this thread: http://forums.slimdevices.com/showthread.php?t=109839

_______________________________________________
Squeezecenter mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/squeezecenter

Reply via email to