VST GUID non ASCII; MIDI channel 128 about pyflp HOT 12 CLOSED

@all-contributors please add @zacanger for bug

from pyflp.

Make sure you use parse_zip if you want to parse an FLP in the ZIP.

You are the first user of my library probably, thanks its motivating :))

FLPInspect is botched up, its pending an entire rewrite, so currently its unuseable.

from pyflp.

Hi @demberto , thanks for the response.
I'm not working with a zip.
I have an .flp file in the same directory and want to analyze that with PyFLP.
This is all the code I have so far 😄 you can see the file structure and error message as well.

from pyflp.

Hmm, you encountered a bug. Can you attach the FLP here please?

from pyflp.

I think I found the reason, or another bug 😁
I tried to recreate the problem by creating an empty file (which works 👍 ) and then add plugins and samples till I reach the .flp which was broken.
I found out that if you drag a MIDI file onto a channel, your analyzer will crash with:

Since both of the errors have that 128 in them, I suspect they both come from the same issue.

from pyflp.

Ok, another bug. But this is not related to the first one at all. The MIDI channel limited to 15 are the 16 colors you can choose for your notes. Now it seems there's another use case for them too. I will try to reproduce this issue, if I can't maybe you can send me the test.flp?

The GUID error you ran with earlier, it is exclusively used by Waves plugins AFAIK. Can you check your warm.flp for any Waves plugins?

I think this definitely makes a point to improve the error handling. I could add more info about what insert or channel failed to parse for example.

from pyflp.

Hi there,
I was able to get what I wanted by using node.js and a custom flp-parser library.
However, regarding this issue: I didn't use Waves plugins for the test file but kHS Plugins and two Serum instances.
I hope this helps 😄

from pyflp.

Hey! ran into same issue when I opened 1 flp but didn't occur for other flps:

Also I should note, I just spent the last 4 hours writing a parser so I could quickly look through the samples used in an flp, only to find out someone already did it (you), so thank you! Is there anyway to reach you besides github?

from pyflp.

@tochibedford I will fix this issue ASAP. You can reach me via email: [email protected]. I check my mails often so I reply as soon as I can generally :)

from pyflp.

@tochibedford @SilasNiewierra Please test your FLPs with v1.1.1, I have fixed both issues

You can run

pip install --upgrade pyflp

to update to PyFLP 1.1.1

from pyflp.

Closing this issue due to lack of response, bugs fixes in v1.1.1

from pyflp.

@demberto

I've put up a pull request to add @zacanger! 🎉

from pyflp.