Ashutosh Pradhan (12020-08-17): > I have provided the sample for $ ./ffplay -f lavfi -i atone > in the folder > https://drive.google.com/drive/folders/1manne188m5T-7wWZb7ZJBLZasLmsX05i?usp=sharing
Thank you. That was more helpful. Honestly, this is not "nice", it is just boring. Which is not your fault: you could not hope to achieve in a summer what eludes years-long PhD theses in musicology and artificial intelligence. The project was as it is, and you seem to have more or less succeeded to implement it. Variations of rhythm would have been nice, though. But the fact remains that this is of no practical use. It is of no use to just listen to and enjoy, and since it uses an external library it is of no use for testing. (This project seems to be based on an old proposal of mine, with the goal to have a varied and somewhat realistic source for audio testing. But testing requires we trust the source is bit-exact.) Since you know the API best, could you say in a few words how hard it would be to get rid of fluidsynth and use an internal synthesizer instead? But in any case, your most urgent matter at hand is this: > > $ ./ffmpeg_g -lavfi atone /tmp/atone.ogg ... > > zsh: segmentation fault ./ffmpeg_g -lavfi atone /tmp/atone.ogg Because we definitely cannot accept a patch that segfaults like that. Regards, -- Nicolas George
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
