Open geyang opened 3 years ago
Do I understand correctly that things are ok when you set IMAGEIO_FFMPEG_EXE
, but are mostly worried that this error seems to occur midway?
Anyway, the only thing I can come up with right now is that the PATH environment variable is changed, causing ffmpeg to be found at first, but fails to do so later. Not much else to go on, frankly.
I did not know that path variable can be changed mid way 🤣
On Sun, Mar 21, 2021 at 09:25 Almar Klein @.***> wrote:
Do I understand correctly that things are ok when you set IMAGEIO_FFMPEG_EXE, but are mostly worried that this error seems to occur midway?
Anyway, the only thing I can come up with right now is that the PATH environment variable is changed, causing ffmpeg to be found at first, but fails to do so later. Not much else to go on, frankly.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/imageio/imageio-ffmpeg/issues/48#issuecomment-803579472, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEZ5WRO5WBO7XTIGFSMJCTTEXXUNANCNFSM4ZQYDPHA .
Just jumping on here even though my help has not been requested. But my guess is that:
I got a hint from @hmaarrfk and tried os.environ["OMP_NUM_THREADS"]=1 and this solved my problem. Thanks.
Just regular call to
imageio
, and it works during the same runtime. But suddenly, this stops working and gives the following error:Actual Behavior
This is not the first time it is called in this RunTime. For background, this is running on an HPC system. The first time this happened I also set the "IMAGEIO_FFMPEG_EXE" variable. Now I always set that variable.
The real red flag is that this function call is okay in these runs before this error is suddenly gets raised.
Steps to Reproduce the Problem
This is hardware-specific. And it takes a while to reproduce inside a ML training loop. These are the constrains I have no control over.
Specifications