WMA playback w/ ffmpeg on win32

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Jason Holtzapple
    #1

    WMA playback w/ ffmpeg on win32

    --- John Harding <john_squeezebox (AT) john (DOT) harding.name> wrote:
    > It turns out the problem is with how ffmpeg writes the decoded data out to
    > stdout when decoding. ...
    >
    > The next problem is that, when streaming data through ffmpeg to stdout, it
    > doesn't know the size of the RIFF chunk and DATA chunk to write out at the
    > beginning of the stream, and leaves them as zero.

    This seems like a critical fix for the squeezebox, so it would
    be great if you would file a bug report with the ffmpeg folks...

    --Jason

    __________________________________
    Do you Yahoo!?
    Yahoo! Finance: Get your refund fast by filing online.
    http://taxes.yahoo.com/filing.html
    Tags: None
    • Roy M. Silvernail
      #2
      WMA playback w/ ffmpeg on win32

      On Mon, 2004-02-16 at 18:00, Jason Holtzapple wrote:
      > --- John Harding <john_squeezebox (AT) john (DOT) harding.name> wrote:
      > > It turns out the problem is with how ffmpeg writes the decoded data out to
      > > stdout when decoding. ...
      > >
      > > The next problem is that, when streaming data through ffmpeg to stdout, it
      > > doesn't know the size of the RIFF chunk and DATA chunk to write out at the
      > > beginning of the stream, and leaves them as zero.
      >
      > This seems like a critical fix for the squeezebox, so it would
      > be great if you would file a bug report with the ffmpeg folks...

      RIFF == WAV, and this is required behavior. The wav spec mandates the
      chunk sizes be written to the RIFF header. If AIFF were an option, this
      wouldn't happen. But ffmpeg doesn't offer AIFF output.

      And good luck with the bug report. I filed a report on the brokenness
      of internet radio ogg streams and have seen no action whatsoever. I
      watched the mailing list for about 6 weeks and as far as I can tell, the
      only interest is in video. If I get really enthused, I might fix the
      STDOUT text-mode problem and post a patch to their list, but who knows
      if it will be accepted.
      --
      Roy M. Silvernail is roy (AT) rant-central (DOT) com, and you're not
      Never Forget: It's Only 1's and 0's!
      SpamAssassin->procmail->/dev/null->bliss
      http://www.rant-central.com

        Comment

        • John Harding
          #3
          WMA playback w/ ffmpeg on win32

          I know the chunk sizes are required for the RIFF/WAV format, but it doesn't
          make sense to try to seek back to the beginning and put them in when you're
          writing to stdout which doesn't support seeking.
          Seems like the right thing for ffmpeg to do when writing to stdout is
          1) Ensure output stream is in binary mode (platform dependent, possibly)
          2) Don't seek back to fill in missing chunk sizes (all platforms)


          ----- Original Message -----
          From: "Roy M. Silvernail" <roy (AT) rant-central (DOT) com>
          To: "Slim Devices Discussion" <discuss (AT) lists (DOT) slimdevices.com>
          Sent: Monday, February 16, 2004 3:30 PM
          Subject: [slim] WMA playback w/ ffmpeg on win32


          > On Mon, 2004-02-16 at 18:00, Jason Holtzapple wrote:
          > > --- John Harding <john_squeezebox (AT) john (DOT) harding.name> wrote:
          > > > It turns out the problem is with how ffmpeg writes the decoded data
          out to
          > > > stdout when decoding. ...
          > > >
          > > > The next problem is that, when streaming data through ffmpeg to
          stdout, it
          > > > doesn't know the size of the RIFF chunk and DATA chunk to write out at
          the
          > > > beginning of the stream, and leaves them as zero.
          > >
          > > This seems like a critical fix for the squeezebox, so it would
          > > be great if you would file a bug report with the ffmpeg folks...
          >
          > RIFF == WAV, and this is required behavior. The wav spec mandates the
          > chunk sizes be written to the RIFF header. If AIFF were an option, this
          > wouldn't happen. But ffmpeg doesn't offer AIFF output.
          >
          > And good luck with the bug report. I filed a report on the brokenness
          > of internet radio ogg streams and have seen no action whatsoever. I
          > watched the mailing list for about 6 weeks and as far as I can tell, the
          > only interest is in video. If I get really enthused, I might fix the
          > STDOUT text-mode problem and post a patch to their list, but who knows
          > if it will be accepted.
          > --
          > Roy M. Silvernail is roy (AT) rant-central (DOT) com, and you're not
          > Never Forget: It's Only 1's and 0's!
          > SpamAssassin->procmail->/dev/null->bliss
          > http://www.rant-central.com
          >
          >

            Comment

            • Roy M. Silvernail
              #4
              WMA playback w/ ffmpeg on win32

              John Harding said:
              > I know the chunk sizes are required for the RIFF/WAV format, but it
              > doesn't
              > make sense to try to seek back to the beginning and put them in when
              > you're
              > writing to stdout which doesn't support seeking.

              Agreed.

              > Seems like the right thing for ffmpeg to do when writing to stdout is
              > 1) Ensure output stream is in binary mode (platform dependent, possibly)

              Yes.

              > 2) Don't seek back to fill in missing chunk sizes (all platforms)

              Some decoders solve this by disallowing WAV if the output stream is
              non-seekable. So point #2 fails the annoying nitpick test. I'd tend more
              toward encouraging adding AIFF output, but having read their developer's
              list for a few weeks, I'd bet that if anything is going to be done, one of
              us will have to step in and do it. The active developers are focused
              almost exclusively on video and I don't think anyone ever reads their
              Source Forge bug tracker.
              --
              Roy M. Silvernail is roy (AT) rant-central (DOT) com, and you're not
              http://www.rant-central.com is the new scytale
              Never Forget: It's Only 1's and 0's!
              SpamAssassin->procmail->/dev/null->bliss

                Comment

                • dean blackketter
                  Gadfly, Former Founder Slim Devices
                  • Apr 2005
                  • 4427
                  #5
                  WMA playback w/ ffmpeg on win32

                  I'm not sure if adding AIFF support would improve things, it has the
                  same requirements as WAV for including size information in the chunk
                  headers.

                  On Feb 18, 2004, at 10:35 AM, Roy M. Silvernail wrote:

                  >
                  > John Harding said:
                  >> I know the chunk sizes are required for the RIFF/WAV format, but it
                  >> doesn't
                  >> make sense to try to seek back to the beginning and put them in when
                  >> you're
                  >> writing to stdout which doesn't support seeking.
                  >
                  > Agreed.
                  >
                  >> Seems like the right thing for ffmpeg to do when writing to stdout is
                  >> 1) Ensure output stream is in binary mode (platform dependent,
                  >> possibly)
                  >
                  > Yes.
                  >
                  >> 2) Don't seek back to fill in missing chunk sizes (all platforms)
                  >
                  > Some decoders solve this by disallowing WAV if the output stream is
                  > non-seekable. So point #2 fails the annoying nitpick test. I'd tend
                  > more
                  > toward encouraging adding AIFF output, but having read their
                  > developer's
                  > list for a few weeks, I'd bet that if anything is going to be done,
                  > one of
                  > us will have to step in and do it. The active developers are focused
                  > almost exclusively on video and I don't think anyone ever reads their
                  > Source Forge bug tracker.
                  > --
                  > Roy M. Silvernail is roy (AT) rant-central (DOT) com, and you're not
                  > http://www.rant-central.com is the new scytale
                  > Never Forget: It's Only 1's and 0's!
                  > SpamAssassin->procmail->/dev/null->bliss
                  >
                  >

                    Comment

                    • Roy M. Silvernail
                      #6
                      WMA playback w/ ffmpeg on win32

                      dean blackketter said:
                      > I'm not sure if adding AIFF support would improve things, it has the
                      > same requirements as WAV for including size information in the chunk
                      > headers.

                      Ack! Sorry... I stand corrected.
                      --
                      Roy M. Silvernail is roy (AT) rant-central (DOT) com, and you're not
                      http://www.rant-central.com is the new scytale
                      Never Forget: It's Only 1's and 0's!
                      SpamAssassin->procmail->/dev/null->bliss

                        Comment

                        Previous template Next
                        Working...

                        We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.

                        By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.

                        I Agree