#211 output buffer fails to buffer next file while current file finishes

svn
closed-invalid
None
5
2014-09-26
2014-08-06
No

The output buffer (-b option) is great but it appears to not anticipate the next file. To avoid the unanticipated delay between files and audio output starvation when slow filesystems are used, it would be nice if the next file was buffered while the current file is playing. I experienced a laggy start of the next file with -b set to 65536 (playing songs through NFS sharing a slow raid-1) with v1.20.1.

Discussion

  • Thomas Orgis

    Thomas Orgis - 2014-08-06

    The output buffer (-b option) is great but it appears to not anticipate the next file.

    It anticipates nothing or end end of the world: It is told to drain
    before loading the next track. This is the historic behaviour. Some
    time ago, I added the --smooth command-line switch:

    mpg123 --longhelp | grep smooth
    --smooth           keep buffer over track boundaries
    

    I have a feeling that this is what your are looking for.

    (Note to self: stable streaming with track-agnostic buffering would be
    a prime scenario for something like mpg123 -s playlist.m3u | out123 -b
    4096 ... though in that case, one could just insert a standard pipe
    byte buffer and spare any IPC code for that. Heck, you can use netcat
    and dispense with network file protocols altogether.)

     
  • Michael Truog

    Michael Truog - 2014-08-07

    Yes, this option solves the problem. Thank you for working on mpg123, I remember using it on a Pentium I and it working well there... it still is the best. I just wish the mpg321 Linux clone wouldn't confuse matters, since it lacks the extra work and cool options. Thanks!

     
  • Thomas Orgis

    Thomas Orgis - 2014-09-26
    • status: open --> closed-invalid
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks