> > in that case I would propose to issue a warning and copy the markers > > from one source - this can be achieved without understanding the markers. > > A more elaborate solution could use both markers, but ommit markers > > which are too close together. This, however requires extracting and > > understanding the information of the markers. > > As someone else already said it is not precisely known how sox handles > markers, and I don't feel that it should become a marker editing/merging > application. SoX ignores them when writing the output. Recently, new maintainers of SoX have kinda been established - do they have an opinion on this? I believe keeping the markers should not be much different from keeping the ID3 tags and other extras from the headers. (Not to play down the work to do.) Jan ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/xeonphi _______________________________________________ Sox-users mailing list Sox-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/sox-users
