benh wrote: > I ran that command on the AAC/M4A file: > > > Code: -------------------- > > Stream mapping: > Stream #0:0 -> #0:0 (copy) > Press [q] to stop, [?] for help > [mov,mp4,m4a,3gp,3g2,mj2 @ 0x55ea023e6980] Packet corrupt (stream = 0, dts = 7911424). > 01 The Tears Of A Clown.m4a: corrupt input packet in stream 0 > [mov,mp4,m4a,3gp,3g2,mj2 @ 0x55ea023e6980] stream 0, offset 0x2be9ec: partial file > 01 The Tears Of A Clown.m4a: Invalid data found when processing input > [ipod @ 0x55ea023fe6c0] Starting second pass: moving the moov atom to the beginning of the file > size= 2792kB time=00:02:59.39 bitrate= 127.5kbits/s speed= 373x > video:0kB audio:2760kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 1.131287% -------------------- > > > > The problem persists after running that command. I'm not sure if the > errors given indicate an actual problem or not
Without seeing the original command you used I cannot answer definitively. The file name extensions affect ffmpeg behaviour. > For the ALAC files, they are transcodes from flac, and are tracks in > different albums by different artists from different sources. On one > album, other tracks exhibit the same issue in a grouped player or set of > synchronized players, but not to a singular player. On another, it's > just the one track. I don't understand > When played in a singular player, problematic tracks do something > strange, visually. In Material Skin while watching the progress bar, > the track hits the 10 to 9 seconds left mark, the audio from the problem > track continues to play, but the progress bar switches to the next track > and appears to be about 10 seconds in. Generally ignore the on-screen timer behaviour - it is generated locally within browser and not closely tied to action until the file has been playing and audio is heard. > When the next track actually starts, the progress bar goes back to the > beginning of that new track. It's as if the player is confused about > what's happening. When played as a group, when the track hits the 10 to > 9 seconds left mark, the audio skips to the next track at the same time > the progress bar does. This seems normal. Time display on browser is started when user presses "play" - the timer will then be updated by LMS with real time value once playing has actually started. In this because there is a problem in playing the file - the timer update becomes apparent. Can you confirm that the LMS supplied "faad" runs OK within your docker environment. What does the faad banner show in terms of version and patches. To see what is going on try enabling player.source to INFO. Note time and try to play a known single file unti the error "cannot play for file " shows and then note end time. Copy into a text file, all log entries from server.log from start time to end time Zip text file and attach to a post. ------------------------------------------------------------------------ bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=114439 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
