Video didn't write when packaging the program with PyInstaller

[abhitronix]

Video didn't write when packaging the program with PyInstaller

[Seraphli]

I use compression=False when packing the program. But the issue still exists.
So the reason is not what you explained.
I tried to pack the program without --windowed, and there is no bug.

[Seraphli]

That's not solved. I want to pack an app that doesn't pop up a console when running. So missing --windowed will result in a window application coming with a console. That's not the way I want.

[abhiTronix]

@Seraphli Do you have a log or terminal log? and how you are managing the FFmpeg backend? Are you providing FFmpeg prebuilt package with your app?

[abhiTronix]

@Seraphli Judging from your app, it is obvious that you are not running WriteGear in compression mode and Hence FFmpeg binaries are not necessary. So coming back to your problem, the empty output error might be related to OpenCV's CODEC. Kindly try changing your output video extension to .avi instead of .mp4 and revert the results here.

[Seraphli]

The script is running fine before being packed. So after packed, I have to set the custom ffmpeg path, right? I thought it would find the right place. ffmpeg has been downloaded before, by vidgear.

[Seraphli]

It is using ffmpeg because the app is just a packed version of the code I posted.

[abhiTronix]

The script is running fine before being packed. So after packed, I have to set the custom ffmpeg path, right?

@Seraphli That is not a right thing to do as different windows machines may not have common path to the custom FFmpeg binary and will end up in broken application. Using non-compression mode(compression=False) i.e OpenCV builtin writer is more suitable in this case.

I thought it would find the right place. ffmpeg has been downloaded before, by vidgear.

I don't think Pyinstaller environment is letting the vidgear to auto-download/auto-install ffmpeg binaries on host machine as it starts immediately without downloading the appropriate binary. Therefore kindly switch off compression mode and try non-compression mode instead.

It is using ffmpeg because the app is just a packed version of the code I posted.

Wrong. When writegear fails to download custom FFmpeg binaries on windows, it automatically switch backs to non-compression mode which uses OpenCV's builtin Writer Class instead.

[Seraphli]

I find out that the packed version has no problem on Ubuntu, but it has the problem on Windows. It will take some time to trace the problem.

[abhiTronix]

I find out that the packed version has no problem on Ubuntu, but it has the problem on Windows. It will take some time to trace the problem.

@Seraphli That's because Ubuntu provides system wide FFmpeg installation and therefore vidgear find no problem identifying it. Clearly this problem is related to your machine configurations and paths, not vidgear API itself.

[abhiTronix]

Closed. Feel free to reopen if something related to vidgear API doesn't works. Goodluck

[abhiTronix]

I tried to pack the program without --windowed, and there is no bug.

@Seraphli Nice Find. Thank you for sharing. Here's some insight for others:

---

-w, --windowed, --noconsole : Windows and Mac OS X: do not provide a console window for standard i/o. On Mac OS X this also triggers building an OS X .app bundle. This option is ignored in *NIX systems.

---

[abhiTronix]

That's not solved.

As you stated, it's not vidgear related bug(or no bug at all) that's why it is marked solved. Otherwise it will be marked invalid.

I want to pack an app that doesn't pop up a console when running. So missing --windowed will result in a window application coming with a console. That's not the way I want.

Open this issue on Pyinstaller forum, they can guide you properly, as I never used Pyinstaller before. Goodluck.