While simple-synoindex-server works fine with file name :
2017/10/17 15:50:10 SynoIndex: -A /volume1/music/Lossless/Massive Attack/Mezzanine/
It don't work with a file name containing special characters like (, { or [ . While simple-synoindex-server logs correct path with appropriated escape characters, the genuine synoindex binary fail to add this path to the index :
2017/10/17 15:10:52 SynoIndex: -A /volume1/music/Lossless/Massive\ Attack/Mezzanine\ \(1998\)\ \{16-44kHz\}\ \[FLAC\]/
BTW Adding a file name with special characters directly with genuine synoindex binary works fine :
synoindex -A /volume1/music/Lossless/Massive\ Attack/Mezzanine\ \(1998\)\ \{16-44kHz\}\ \[FLAC\]
While simple-synoindex-server works fine with file name :
2017/10/17 15:50:10 SynoIndex: -A /volume1/music/Lossless/Massive Attack/Mezzanine/It don't work with a file name containing special characters like (, { or [ . While simple-synoindex-server logs correct path with appropriated escape characters, the genuine synoindex binary fail to add this path to the index :
2017/10/17 15:10:52 SynoIndex: -A /volume1/music/Lossless/Massive\ Attack/Mezzanine\ \(1998\)\ \{16-44kHz\}\ \[FLAC\]/BTW Adding a file name with special characters directly with genuine synoindex binary works fine :
synoindex -A /volume1/music/Lossless/Massive\ Attack/Mezzanine\ \(1998\)\ \{16-44kHz\}\ \[FLAC\]Any chances to fix this ?