On Thu, 2012-04-19 at 17:49 +0200, Max Kellermann wrote: > On 2012/04/19 17:41, Jurgen Kramer <gtmkra...@xs4all.nl> wrote: > > I do not mind putting DSF file format support in a separate decoder > > plugin. Having two separate decoders would probably yield better > > readable and therefore better maintainable code. > > > > On the other hand it would mean a bit of duplicated code and effort. > > Both file formats contain DSD data and output 'PCM'. > > Duplicate code is worse than that, so either leave it as a combined > plugin, or move common code into a library used by both. The latter > looks like the cleanest solution to me.
Alright, can you live with a 2 step approach? 1. Start with adding DSF to current DSDIFF decoder 2. Create common library for DSF and DSDIFF and update DSDIFF decoder to use it. This way people can start enjoying playing DSF files soon(er). Jurgen ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
