Opened 3 years ago
Closed 3 years ago
#15683 closed enhancement (fixed)
mpg123-1.29.2
Reported by: | Douglas R. Reno | Owned by: | pierre |
---|---|---|---|
Priority: | normal | Milestone: | 11.1 |
Component: | BOOK | Version: | git |
Severity: | normal | Keywords: | |
Cc: |
Description ¶
New minor version
Change History (5)
comment:1 by , 3 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 3 years ago
Summary: | mpg123-1.29.1 → mpg123-1.29.2 |
---|
comment:3 by , 3 years ago
thomas: Releasing mpg123 version 1.29.1: mpg123: Keep default output encoding of s16 for raw and file outputs also with the new resampler. This reverts the unintentional change in 1.26.0 of switching to f32 for forced output rate unless the NtoM resampler is selected. In any case, you should make sure to specify your desired --encoding if you depend on it. Catch error in indexing (mpg123_scan() return value was ignored before, bug 322). mpg123-strip: Lift the resync limit, as it should be to clean up really dirty streams. mpg123-id3dump: Also lift resync limit for the same reasons. libout123: fix reporting of device property flags for buffer libmpg123: more safeguarding against attempts to decode if decoder setup failed and user ignored the returned error code (bug 322) If you for some reason are stuck on 1.26.x, I recommend updating at least to the changes in the 1.26-fixes branch. but of course, the proper thing is to jump from 1.25.x or anything in between to 1.29.1 to avoid that little default output encoding surprise with forced rate.
comment:4 by , 3 years ago
thomas: Releasing mpg123 version 1.29.2: libmpg123: Fix non-live-decoder safeguard for mpg123_framebyframe_decode() (was a no-op in practice, bug 324).
comment:5 by , 3 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Fixed at commit 49887e89742615e66caa79aaa4556c58c73df345
Note:
See TracTickets
for help on using tickets.
Now 1.29.2