-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ffmpeg not installed? #54
Comments
If you want to use ffmpeg to export a video, you need the |
Thanks, but it still doesn't work. I put |
...indeed: For instance, your GRIN example script changes It certainly doesn't make sense to be forced to put a copy of Also, one cannot simply change PS.: You should re-open this issue until it is solved. |
Yip, just checked. Adding |
HELLO??? |
Hi @kerstin921 , This is an open source project. We're all developing this in our free time. I am sorry for not replying within 24 hours. It seems you found a bug in the video exporting feature, and from what I can tell you're already half way there in understanding the problem and fixing it... So if it's not too much to ask, please fix it, create a PR and it will get accepted. This is how open source works. |
Hi flaport, thanks for this information. I was under the impression that this basically is Python's official FDTD package, which is why I was so confused about the existence of such bugs (meaning it should've been reported earlier as people simply cannot miss it running your example scripts). What is a PR and how does it solve the issue? |
Yeah...no.
This package is nowhere near production-ready and already breaks at the very first steps - so I'm out. Not worth the trouble and time investment only to find more bugs along the road.
|
Thanks for the hint @kerstin921 , gprmax seems indeed pretty cool! |
It is, they used |
@flaport Just to illustrate how bad the problem is, consider this baby example (even much simpler than your examples):
The output:
And this perfectly illustrates the problem with Python: People putting hundreds of non-functional packages into the official PyPI repository, tricking users to waste endless hours into experimenting with packages that don't even pass the simplest test cases, then waving hands and saying "It's open-course!" and "Community!". While in reality, they just want to have a GitHub repository to pad their CVs and couldn't care less about quality. |
Hi @kerstin921 , I am sorry you had a bad experience with this package. Of course having non-functional code in the library must be very frustrating for you. I know the library has not been actively maintained recently and I have probably been accepting pull requests too easily in the past, which made parts of the code unstable (see for example #15, which introduced the video generation function). That said, I will do a thorough review of the library in the near future (when I find the time) to find and remove bugs and to make sure it's back to a stable state. Please do understand that I have a full time job which means I don't have the time to work on and maintain the projects like I used to. I am sorry this lead to lost time for you. |
It's not 100% lost time (maybe 80% or so) as I'm still familiarizing and learning a few things while trying to get your package working. The problem is that the very basic examples seem not to be working. Usually, such problems are quickly resolved (since examples normally give a working demonstration) because else you'd bascially be dealing with a "cool", but non-functioning codebase published for everyone on the internet. And some of the files/many functions contain almost no documentation, so even for willing beta testers like me it quickly gets super frustrating to fix anything (and I'm not getting paid). Sorry to stress you out |
But maybe that's just me as I use to write code as if meant for kindergardeners (i.e. every little piece is documented), so I can basically just give it to a collegue and there will hardly ever come back questions |
png can be merged with ffmpeg using the following DOS commands after installation, but each file shall be parsed correctly : ffmpeg -framerate 10 -start_number 0 -i file%4d.png -c:v libx264 -pix_fmt yuv420p out.mp4 files by 10 steps (ex: file0010.png, file0020.png...file5000.png) ffmpeg -framerate 10 -start_number 0 -i file%4d.png -c:v libx264 -pix_fmt yuv420p out.mp4 example of storing files by single entries: simfolder = grid.save_simulation("Emtest") # initializing environment to save simulation data with open(os.path.join(simfolder, "grid.txt"), "w") as f: for i in range(500): |
None of your example files will generate a video on Windows.
The error
ffmpeg not installed?
is thrown despiteffmpeg-python
being installed.I looked up the relevant function
generate_video()
in your source code and it saysNote: this function requires ``ffmpeg`` to be available in your path.
, so I've tried copying theffmpeg
package folder into the same folder as the.ipynb
notebook containing your example simulations and even moving all.py
files directly into it, but to no avail.Could you please check what's wrong and, if necessary, make corrections so that
fdtd
will recognize theffmpeg
package?The text was updated successfully, but these errors were encountered: