View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0013744 | MMW v4 | Conversion/Leveling | public | 2016-12-12 23:25 | 2017-02-26 14:46 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | sometimes |
| Status | feedback | Resolution | open | ||
| Target Version | 4.1.16 | ||||
| Summary | 0013744: Conversion: Direct Conversion to network path can introduce artifacts | ||||
| Description | As WLAN is slower connection and when you convert large number of files bandwidth can hit bottleneck and start failing packets which creates artifacts on destination. I managed to replicate once, but never before/after. Is there way to add INI switch to always use local temp file for conversion? | ||||
| Additional Information | DVB-842-53544 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Currently there is an option to cache network files only when burning. Are you sure that conversion the file into local temp and then copying to network location would solve the problem? Could you test this with the user (DVB-842-53544) to be sure? |
|
|
I was able to replicate once today with one laptop I got on service today. To replicate Device needs to be on the edge of WiFi reception that introduce failed packets and transfer rate needs to be <50KBps so that MMW conversion thread waits for packets. Artifact can be introduced at points of failed packets. and not on all tracks converted with multiple cores. I ended in 5 out of 300 tracks converted (owner of laptop reported that today) and my original NAS files play without artifact. So yes, caching tracks on slow connection would evade this, but on normal LAN connections it would slow conversion. |
