2017-08-20, 10:28
tmm does automaticly (?) do a "getting mediainfo" (in German: "hole mediainfo").
This takes hours, never stops and is not stopable. On Debian GNU/Linux unstable. When I click on the red cross (in the statusbar right) it disappear from the job list but still runs because all other jobs are still wating.
The video files on a NFS-share.
Using tmm from git.
EDIT: Just to be sure I copied the complete data (all videos, folders) to my local hard drive. The behaviour is the same. So I think it doesn't matter that the videos are on a remote drive (e.g. NFS share).
EDIT2: Did a second test with the Windows (ver7 on a VM) version (2.9.4) of tmm. It takes very long (>10m), too. But it finishs. So there is a difference between these two systems. Which parts of the OS does tmm use when "getting mediainfo"? Maybe there is something "wrong" with one of the related OS-components.
This takes hours, never stops and is not stopable. On Debian GNU/Linux unstable. When I click on the red cross (in the statusbar right) it disappear from the job list but still runs because all other jobs are still wating.
The video files on a NFS-share.
Using tmm from git.
EDIT: Just to be sure I copied the complete data (all videos, folders) to my local hard drive. The behaviour is the same. So I think it doesn't matter that the videos are on a remote drive (e.g. NFS share).
EDIT2: Did a second test with the Windows (ver7 on a VM) version (2.9.4) of tmm. It takes very long (>10m), too. But it finishs. So there is a difference between these two systems. Which parts of the OS does tmm use when "getting mediainfo"? Maybe there is something "wrong" with one of the related OS-components.