>
> 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.
>
Yes, I th
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
> w
On Sonntag, 5. September 2021 15:45:15 CEST Kolja Koch wrote:
> Hi Christian,
>
> cool, thanks a lot for this!
> As far as I understand it, I will be able to use that in my 'gig-
> creator', that I'm working on (by the way, I ended up using wxWidget).
Yes, for now you would probably assemble a co
Hi Christian,
cool, thanks a lot for this!
As far as I understand it, I will be able to use that in my 'gig-
creator', that I'm working on (by the way, I ended up using wxWidget).
I will post as soon as I have something usable.
Cheers,
Kolja
>
> Done.
>
> See latest revision of 'man wav2gig'
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" \
On Sonntag, 29. August 2021 15:41:06 CEST Kolja Koch wrote:
> > 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
> Because somebody would need to write *and* maintain all of that
> software. Keep
> in mind that almost all people stepping by here are usually just
> saying
> feature x doesn't work, please fix it. Or feature y is nice, but
> please extend
> it in this and that way.
>
True!
> I understand t
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 prop
I was thinking a little bit more about this.
Maybe we should agree upon some kind of complexity-level we want to
catch.
For instance:
The user might want to put samples into a gig-file, that have no common
filename structure. We could write an interface to let him enter the
required attributes (wi
>
> I understand that you like the printf specifier format, as it looks
I think it's because I'm a little more used to it...
> more
> simple on first view. But keep in mind both on your easy tag example
> and
> printf the actual purpose deals with the other way around: e.g. in
> the easy
> ta
On Samstag, 28. August 2021 18:29:21 CEST Kolja Koch wrote:
> > Could you please elaborate, i.e. examples of where you would see
> >
> > > issues by
> > > just supplying regex patterns from the command line?
>
> Sure!
>
> I don't know in which order the attributes might be.
> The regex you imple
> Could you please elaborate, i.e. examples of where you would see
> > issues by
> > just supplying regex patterns from the command line?
Sure!
I don't know in which order the attributes might be.
The regex you implemented uses a fixed order:
'(Name1)(Name2)(Velocity)(Note_Nr)(Note_Name)'
Tak
On Freitag, 27. August 2021 21:19:27 CEST Kolja Koch wrote:
> Hi Christian,
>
> thanks a lot for the info!
>
> Regarding regex:
> I know regex, but was not too familiar with it.
> From what I understand, it is hard to foresee, in what order the
> attributes are in the filename, which makes direct
Hi Christian,
thanks a lot for the info!
Regarding regex:
I know regex, but was not too familiar with it.
>From what I understand, it is hard to foresee, in what order the
attributes are in the filename, which makes direct usage of regex
difficult.
I already toyed around a little bit and wrote a
On Mittwoch, 25. August 2021 12:26:38 CEST Kolja Koch wrote:
> 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 ge
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 t
16 matches
Mail list logo
