Problems with Ripbot264 1.19.2 and Windows 10

[cjbrown80]

I've upgraded both of my PCs to Windows 10 x64 (one is a 6700k, two is a 3930k, both clean installs), and ripbot264 distributed encoding, no longer works properly. It seems to take forever when I'm adding a job after I've selected my cropping, sizing and subtitles. It displays "Please wait... Gathering information..." for what seems like 10 minutes, when before, it used to only take several seconds. After I start the job, it takes a similarly long time to "Copying tools to shared folder". When it finally does start, I get an error either "Source file could not be indexed", or it just hangs on the indexing phase. I have installed AviSynth 2.6, ffdshow v1.3.4532, newest Haali and Java 8 Update 66. I've also made sure the ripbot264 temp folder is shared and accessible from the remote machine. Any help would be greatly appreciated.
-Chris

[redwudz]

Sorry, probably not much help from me as I don't use RB on W10 or distributed encoding, but..

Does RB work correctly without distributed encoding?

Have you tried uninstalling RB and reinstalling. Sometimes that helps.

But others here may have some better advice.

[cjbrown80]

It works fine without DE enabled, but I need it for the DE. It has something to do with the Encoding Client and/or the temp folder sharing. Thanks.

[redwudz]

RipBot's author drops by here on occasion, but he mostly posts to Doom9: http://forum.doom9.org/showthread.php?t=127611
You can do a search there for DE and W10. I think he has tested RB on a W10 emulator.

[cjbrown80]

Yeah, I just registered for the Doom9 forum, but I can't post for a five day grace period. If he doesn't respond by day after Xmas, I'll post there too.

[zicaman]

hi my friends! first of all, happy holidays all of you!!

im a old ripbot264 user, im using since 2011, but im having problems lately, after compression, the file doesnt appear on the save directory, im triyng to convert M2Ts and Ts files from a bluray disc, before that ripbot was normal with mpeg to mkv files. hope anyone can help me! thanks again!

[Shaylen]

@zicaman

The only work around for this problem is to manually mux the output files from the temp dir of RipBot264 with the mkvtoolnix GUI. If you try to mux with the job[no]_MuxFiles.cmd that RipBot264 creates, you would see an error on the command prompt and for some reason it's unavoidable. If you are going to use the work around just make sure you do not close RipBot264 after the encode is complete because by default it destroys the encoded video stream on close.

[Cauptain]

Easy way to avoid this.

In each PC create a same USER (Not need login, just create) - Eg: "ripbot" WITH password (minimum 8 chars - obrigatory)

In principal PC, give Full Access for "ripbot" user (Share an Security) in RIPBOT264 extracted folder and RB Temporary folder.

Enjoy.


PS: Run all *.exe on WINDOWS 10 in ADMINISTRATOR MODE (Right click)



Claudio

[zicaman]

Thanks Saylen, i will try that! happy holidays!