Hello all, I played around a little bit with the wav2gig tool, in order to get samples extracted by akaiextract into a gig-file. Currently, wav2gig only supports a hard coded naming convention for the wav-files in order to get the information needed for the import process.
- Are there any plans to integrate the import-process into gigedit? If so, we could present the user with an interface similar to the "Fill Tag" scanner in eastag: http://src.gnu-darwin.org/ports/audio/easytag/work/easytag-2.1/doc/EasyTAG_Documentation.html#vh_1_2_2 Note: Any characters in the filename that should be ignored can be entered directly and work like a delimiter, just like the " - " in the example. Disadvantage is, that this will only work, if there are indeed delimiters. In my case, the filenames look like this: 'STFLSF 5 L.wav' where 'ST' is the instrument, 'FLS' the articulation and 'F 5' is the note 'F#5'. The 'L' stands for 'left', as there is also a file for the right channel. Unfortunately, there is also 'STFLSF5 L.wav' where 'F5' is the note 'F5'. Theoretically, there could also be a 'F -1' (= 'F#-1'). I know, we cannot cover any name-scheme one might (not) think of, but as you can see, the only 'dynamic' part of the filename in my case is the note-name, so using the 'easytag'-scanner I could enter 'STFLS%n ' where %n would refer to the note-name. Missing paramters: - The notenumber could be extracted by investigating the notename - the sign-charater(s) should be entered (' ' in my case, might be '#', 'sharp', 'flat', 'is' or whatever). - 'name' (and name2) could be entered as a static value and eventually used for auto-generating the gig-filename. - velocity_nr could in my case also be entered as a static value (default = 64 or 127?) Exception to the given scheme that might occur during the import- process might have to be dealt with individually: ignore file (ignore all exceptions), abort import. Sidenote: With my filenames, it looks like they have a fixed length with each index with a fixed meaning. Another filename-scheme from my list: 'T1FTG2 AIF L.wav' index 0 to 1: name index 2 to 3: name2 index 4 to 6: note-name index 7 to 10: ??? index 11 : pan So this could lead to a different 'fixed-width' approach. Of course, this all could be implemented as commandline options to wav2gig, or maybe with a switch that will lead to an interactive 'shell': - Show the first found wav-filename - The user enters the name-scheme - The user enters missing information from the name-scheme as static values I'm willing to participate on this, though my programming-skills are those of a layman... ;) Cheers, Kolja _______________________________________________ Linuxsampler-devel mailing list Linuxsampler-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
