Re: [LAD] [A plugin scanner:] Cache text file formats: rdf, ttl, custom xml?
Ehm... help ? Bug ? I took the time to integrate LRDF library support into the program. We never had lrdf enumerated controls, or lrdf preset support (interesting, I didn't know about those presets). Yeah I know, about 10 years late... I had a bad feeling there were going to be 'mismatches' between what lrdf reports and what the plugin reports. This seems to be happening. I may have found some serious mistakes in the various .rdf files: In blop.rdf all of the listings are like this: -- [ ... ] Quantiser (100 Steps) Mike RawesGNU General Public Licence Version 2 or Later ladspa:hasLabel="Range Minimum" /> ladspa:hasLabel="Range Maximum" /> ladspa:hasLabel="Match Range" /> [ ... ] -- And in swh-plugins.rdf they are also all like that: -- [ ... ] Steve Harris Impulse convolver ladspa:hasLabel="impulse" /> ladspa:hasLabel="high_lat" /> ladspa:hasLabel="gain" /> [ ... ] -- Meanwhile in tap-plugins.rdf things seem correct: -- [ ... ] Tom Szilagyi TAP Equalizer ladspa:hasLabel="band_1_gain" /> ladspa:hasLabel="band_2_gain" /> ladspa:hasLabel="band_3_gain" /> [ ... ] -- The blop and SWH are not correct and do not jive with what the plugin reports. The result is mismatched enums to ports. Tap plugins however are just fine. What's wrong here? Two different libraries... Did the specs change or was it a mistake? Thanks. Tim. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] [A plugin scanner:] Cache text file formats: rdf, ttl, custom xml?
On 10/31/2018 04:36 PM, Tim wrote: > I may have found some serious mistakes in the various .rdf files: > And in swh-plugins.rdf they are also all like that: To illustrate that one, here is swh-plugins.rdf 1416 port #1: Steve HarrisAnalogue Oscillator ladspa:hasLabel="wave" /> And here is the *mismatched* corresponding swh-scales.rdf entry: Also, we have some weird incomplete listings in the rdf files like: Plugin: Bode frequency shifter (CV) Port name: "Mix (-1=down, +1=up)" idx #1 Possible enum values: val="1" label="up" (No corresponding down enum.) Thanks again. Tim. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
[LAD] Fixes for Blop and SWH LADSPA plugin RDF files + program to do it
Hi, as I mentioned in LAD today, I think I found some problems with Blop and SWH LADSPA RDF files. I fixed them automatically with a program, and by hand for the few odd incomplete enumerations. Here are the fixes and the program I used. https://www.dropbox.com/s/vapxxr9s9zvyari/corrected.tar.gz?dl=0 https://www.dropbox.com/s/tllg1iudino4ah0/FixLrdfFiles.tar.gz?dl=0 Thanks. Tim. The MusE sequencer project. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Fixes for Blop and SWH LADSPA plugin RDF files + program to do it
Am 01.11.18 um 04:00 schrieb Tim: Hi, as I mentioned in LAD today, I think I found some problems with Blop and SWH LADSPA RDF files. I fixed them automatically with a program, and by hand for the few odd incomplete enumerations. Hi We've implemented a special case rule in our rdf scanner, (shift the index to the correct value) for some known wrong indexes in rdf files, and I guess others have that as well. So, "fixing" those wrong entry's, after so long time, may break existing implementations. As reference, here is our list: static struct { unsigned long from, to; } ranges_1_based[] = { // swh {1181, 1440}, {1605, 1605}, {1881, 1922}, // blop {1641, 1680}, {2021, 2038}, }; regards hermann ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev