Batch Processing stops randomly
Posted: Sat Jul 06, 2013 12:36 pm
Hi,
I have an issue with 1.7.4 and Windows 8. The videos I cut are on a network drive connected by a Gigabit ethernet.
What I usually do is to define the cut points for multiple videos and save a long batch. Then start the batch process and do something else during that time. The network connection is fast enough to work with the videos on the network drive with nearly no delay. This has worked for me on a Windows 7 system very good with different versions of smart cutter.
Now I recently updated to Windows 8. And now the batch randomly stops. That means it processes like 4-5 files, then displays the "Transcoding Complete"-Message, but there are more videos in the batch that did not process. On the drive there is a 0 byte file for the video that it last tried to start to process. I watched it doing that. It stayed at 99% for the previous file for quite a long time and then suddenly displayed the transcoding complete message. Do you have an idea why that happens? Would be great if it would work again like before...
Achim
I have an issue with 1.7.4 and Windows 8. The videos I cut are on a network drive connected by a Gigabit ethernet.
What I usually do is to define the cut points for multiple videos and save a long batch. Then start the batch process and do something else during that time. The network connection is fast enough to work with the videos on the network drive with nearly no delay. This has worked for me on a Windows 7 system very good with different versions of smart cutter.
Now I recently updated to Windows 8. And now the batch randomly stops. That means it processes like 4-5 files, then displays the "Transcoding Complete"-Message, but there are more videos in the batch that did not process. On the drive there is a 0 byte file for the video that it last tried to start to process. I watched it doing that. It stayed at 99% for the previous file for quite a long time and then suddenly displayed the transcoding complete message. Do you have an idea why that happens? Would be great if it would work again like before...
Achim