On Sonntag, 29. August 2021 15:11:27 CEST Christian Schoenebeck wrote: > On Samstag, 28. August 2021 20:23:34 CEST Kolja Koch wrote: > > > wav2gig -a '(.*) - \d* - .* - .*.wav" \ > > > > > > -b '.* - (\d*) - .* - .*.wav" \ > > > -c '.* - \d* - (.*) - .*.wav" \ > > > -d '.* - \d* - .* - (.*).wav" > > > > It took me a moment to understand your proposal right. > > That is indeed very flexible, especially when combined with > > > > > pattern1|pattern2|pattern3 > > > > as you proposed. > > Also, this would make wav2gig easily to be invoked by other programs. > > > > From a user point of view, this anyway seems to me like it's hard to > > understand. E.g. if I'm no programmer and would be confronted with this > > kind of logic, I'd be scared away very soon. > > > > So why not use both approaches? > > - implement those name-switches as of your example > > - write a wrapper for wav2gig with a commandline-interface using the > > easytag-logic or whatever we would agree to be user-friendly. Not all > > name-schemes would have to be implemented here. This will call wav2gig > > with the corresponding Name-switches. > > - Write a real gui for that wrapper, that might be invoked by e.g. > > gigedit. [...] > Regex patterns are doing the job, including use cases that go beyond your > personal needs, and I don't have to maintain parsing code by myself. So the > plan is to make this feature configurable by standard regex patterns only > for now; no self-invented formats/tags and no custom parser code on top > that would need to be developed, documented, extended and ... fixed. > Instead some regex examples in the man page should already be a good > starting point for new users. > > For more complex uses cases there are plenty of RegEx howtos and live RegEx > debug tools on the net. And if someone fails: there is still this mailing > list and the forum site where users can just ask. > > Additionally I would add a verbosity switch and maybe a --dry-run switch for > providing users diagnostics for the individual input wav files' meta info > being picked by wav2gig and why. But that should be really it for > foreseeable future.
Done. See latest revision of 'man wav2gig' how this tool behaves now: http://svn.linuxsampler.org/cgi-bin/viewvc.cgi/libgig/trunk/man/wav2gig.1.in?view=markup CU Christian _______________________________________________ Linuxsampler-devel mailing list Linuxsampler-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
