View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007667 | MMW v4 | Other | public | 2011-04-15 10:43 | 2012-12-18 04:28 |
| Reporter | Ludek | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.0 | ||||
| Target Version | 4.1 | Fixed in Version | 4.0 | ||
| Summary | 0007667: UPnP/DLNA transcoding: WAVs fail to stream on-the-fly | ||||
| Description | If I have wav files above 1412 bitrate set to auto convert to 16/44.1 wavs, the first time I try to play them using MM4 as the DLNA client and server, they just scroll through on the client machine without playing, staying a couple of seconds on each track. If I look on the server machine I can see the auto-converted wav files being created in the cache. If I try to play them again, they play fine as they are now in the server cache? | ||||
| Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=57065 http://www.mediamonkey.com/forum/viewtopic.php?f=20&t=68663 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1611 | ||||
|
|
Fixed in build 1365. |
|
|
Verified 1380 |
|
|
This is being reported as still failing on 1511: http://www.mediamonkey.com/forum/viewtopic.php?f=20&t=68663 |
|
|
I just tried it with BubbleUPnP client on an Android phone and with MediaMonkey client on another computer and both worked just fine (tested with 4.1.0.1609). It is probably a problem on the client side. i.e. the client might get length from WAV header beforehand and somehow be not satisfied with the value as this value cannot be predicted. |
|
|
Reading the forum post it is rather mime type causing the playback to fail, i.e. audio/wav vs audio/x-wav OK, added audio/wav, audio/wave, audio/x-flac to the server protocol info in build 1611. Also changed "audio/x-wav" -> "audio/wav" protocol info when serving particular wav file, so it might help. |
|
|
Verified 1614 |
