| 1 |
One current thing: Cleanup mpg123_noise() ... remove that accidentally public symbol |
| 2 |
or make it official. The functionality is in syn123 and it was never documented. |
| 3 |
|
| 4 |
Things that need to be done... |
| 5 |
|
| 6 |
... as always, mostly outdated. |
| 7 |
|
| 8 |
0. Fix that ugly crash that happens sometimes when Ctrl+C-ing with jack output active: |
| 9 |
|
| 10 |
Program terminated with signal 11, Segmentation fault. |
| 11 |
[New process 6293] |
| 12 |
[New process 6291] |
| 13 |
[New process 6292] |
| 14 |
[New process 6284] |
| 15 |
#0 0x00002aced607695b in memcpy () from /lib/libc.so.6 |
| 16 |
(gdb) bt |
| 17 |
#0 0x00002aced607695b in memcpy () from /lib/libc.so.6 |
| 18 |
#1 0x00002aced5b4f092 in jack_ringbuffer_read () from /usr/lib/libjack.so.0 |
| 19 |
#2 0x00000000004151dd in process_callback () |
| 20 |
#3 0x00002aced5b4bf40 in Jack::JackClient::Execute () from /usr/lib/libjack.so.0 |
| 21 |
#4 0x00002aced5b5f8da in Jack::JackPosixThread::ThreadHandler () from /usr/lib/libjack.so.0 |
| 22 |
#5 0x00002aced6354fa7 in start_thread () from /lib/libpthread.so.0 |
| 23 |
#6 0x00002aced60c802d in clone () from /lib/libc.so.6 |
| 24 |
|
| 25 |
|
| 26 |
1. mpg123 could pick up new sample rates suggested by the output modules (like a jack server fixed to 96kHz) and adapt to that. |
| 27 |
|
| 28 |
Also, the libsyn123 resampler should be employed. Just generally, libsyn123 |
| 29 |
could also provide encoding conversions for formats not directly supported |
| 30 |
by accelerated decoders. See out123, which is the |
| 31 |
|
| 32 |
2. What's about SINGLE_MIX? |
| 33 |
Check what is _really_ happening there, make some test file... |
| 34 |
|
| 35 |
3. Add playback of WAV files in mpg123 and out123. |
| 36 |
|
| 37 |
Parsing the standard 44-byte header really is no big issue. WAV64 is |
| 38 |
not really a thing, is it? Anyway, mpg123/out123 will probably just ignore |
| 39 |
the length in the header. Also, both programs need a switch to enable |
| 40 |
treating input as WAV, though out123 might get away with a default |
| 41 |
mode of looking out for a header unless format options were given. Yes, |
| 42 |
that makes sense. And perhaps I really should limit this to out123. |
| 43 |
|
| 44 |
4. Enable some way to avoid libmpg123 messages (Note: …) messing up display |
| 45 |
of the progress bar. |
| 46 |
|
| 47 |
- cleanup callback from app |
| 48 |
- fprintf callback from app |
| 49 |
- log buffer |