| Summary: | ASTERISK-01268: ast_translator() bug? | ||
| Reporter: | Paul Cadach (pcadach) | Labels: | |
| Date Opened: | 2004-03-22 13:39:23.000-0600 | Date Closed: | 2011-06-07 14:05:04 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | When translator re-codes between different codecs with different frame/packet sizes, it could produce data looses. ****** ADDITIONAL INFORMATION ****** Typical example is transcoding from G.723.1 (30 ms/packet) to G.711 (20 ms/packet). First, it feeds G.723.1 packet through G.723.1 decoder and produces SLINEAR 30 ms frame then passes it to G.711 coder which produces G.711 frame with 20 ms frame. Next G.723.1 packet produces SLINEAR 30 ms frame too which, theoretically, in conjunction with previously stored 10 ms, must produce 2 (!) G.711 20 ms frames, but ast_translate() allows to fed out only one frame per call. May be, as solution, ast_translate must be joined with ast_smoother? | ||
| Comments: | By: Paul Cadach (pcadach) 2004-03-22 14:00:41.000-0600 Ok, found where I was wrong... Could be closed. | ||