On Mittwoch, 8. September 2021 19:27:49 CEST Kolja Koch wrote:
> Hi,
>
> thanks for the tipps!
>
> I made some progress, see attached screenshots.
>
> example1 shows processing the default-naming-scheme. I already renamed
> these files with my initial shell-script to that. When hitting OK, a
> wav2gig-command is created:
>
> wav2gig --regex-name1 "(.*) - .* - \d* - \d* - .* .*" --regex-name2 ".*
> - (.*) - \d* - \d* - .* .*" --regex-velocity-nr ".* - .* - (\d*) - \d*
> - .* .*" --regex-note-nr ".* - .* - \d* - (\d*) - .* .*" --regex-note-
> name ".* - .* - \d* - \d* - (.*) .*" [list of files]
>
> This actually worked! :)
>
> example2 however shows a much more complex case. As to see on the left,
> there are a lot of files in that folder and they don't have any note-
> number nor velocity. The tool will calculate the notenumbers based on
> given sign-characters (' ' for sharp in this case).
Well, there must be some note/velocity numbers info somewhere, either in the
wav file (content) itself, or as part of the file name. For other use cases
more options would need to be added to wav2gig, like a default value for
velocity, note, ... if there is no match.
> Another thing to
> mention is that the (mono-)files' last character show their stereo-
> position (L for left, R for right).
Yeah, that's something that is supported in the korg2gig tool already, but not
in wav2gig yet:
http://svn.linuxsampler.org/cgi-bin/viewvc.cgi/libgig/trunk/src/tools/korg2gig.cpp?revision=3175&view=markup#l232
> So with the specifier-string one
> can enter in the middle of the window, this added to the corresponding
> name2 (%m appears twice). Also, not all files comply to the specifier-
> scheme, that's why I entered a second one, wich will be used against
> the remaining files. This way, all files could be processed, creating
> 18 gig files out of that. Theoretically, you can enter as many
> specifier-schemes as you like.
> Surely, this wouldn't actually work with wav2gig, since I don't know
> how to translate this into the required regex.
> Another thing is that there's no velocity given. Don't know, how
> wav2gig would react on this.
>
> I'm not absolutely sure, how to go on from now. The whole thing would
> need some cleanup, I'd like to implement some options, help and
> preferences. In order to implement the bottleneck from above I would
> have to patch wav2gig, I'm afraid. This wouldn't be something for your
> mainstream, thou, I guess.
Well, like always, it's a long way to the top. :)
> Maybe I'm putting that on a github-site, have never done that before...
Sure, why not. But more cleanup would not really be negative. ;)
CU
Christian
_______________________________________________
Linuxsampler-devel mailing list
Linuxsampler-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
