Quote:
Originally Posted by LeetDonkey
Hello
I've run into an odd thing on two different PCs running windows 10
- Setup a job
- Enable distributed encoding
- Check that ripbot264temp is properly shared
- Start job
When I click start job the network share of ripbot264temp is removed and ripbot264 fails at indexing the file.
Now If I'm quick and manage to reshare the ripbot264temp directory while ripbot is copying tools, it will proceed to encode in a normal way right until the next item in the queue and the share will be removed again automatically.
I've tried searching the thread but I haven't found anything that could help me.
Does anyone have any idea what's going on?
|
Hello. First of all thank you. I use ripbot264 for 8 years now. Now I pass the upper step using distributed encoding but i have exactly the same problem as the one indicated above. Do you have a solution for this problem? Thank you.
PS : Using ripbot264 1.20 . The issue appears with non-English versions of Windows. Tested on 3 new Windows install. The shared folder problem is not on the English windows...