RipBot264 v1.18.3 - Simple and easy to use GUI -> IPOD . PSP . CONSOLES . BLURAY

[Nosirus]

https://youtu.be/ScGt6vEu5co

Almost !

But you have to type the command each time

[Atak_Snajpera]

What happens if you manually run \\DESKTOP-8NBTRJ0\RipBot264temp\Job1\Chunks\1.cmd from remote-pc?

Ps. That behaviour seen on your video means that something is wrong with shared folder. (ACCESS DENIED)

[byteshare]

Is there a way to specify avs2yuv64.exe rather than avs2yuv.exe when using MT? I think this might be the reason I get issues (often encodes cut out early) with MT in RipBot but not another application.

[Atak_Snajpera]

Originally Posted by byteshare

Is there a way to specify avs2yuv64.exe rather than avs2yuv.exe when using MT? I think this might be the reason I get issues (often encodes cut out early) with MT in RipBot but not another application.

avs2yuv64.exe will require AviSynth 64bit.
AviSynth 64bit will require ALL plugins in script to be 64 bit as well.
Not all plugins are available for x64 architecture.

[byteshare]

Originally Posted by Atak_Snajpera

avs2yuv64.exe will require AviSynth 64bit.
AviSynth 64bit will require ALL plugins in script to be 64 bit as well.
Not all plugins are available for x64 architecture.

Is there a way to know easily if they are x64?
For example MDegrain: http://avisynth.nl/index.php/Temporal_Degrain
I thought was x64.
Sorry if I'm wasting your time, just thought this was easier than it seems now that you explained it a little.

[Atak_Snajpera]

I mean that every single plugin which is used by RipBot264 would have to be 64bit. Not only MDegrain.

[byteshare]

Originally Posted by Atak_Snajpera

I mean that every single plugin which is used by RipBot264 would have to be 64bit. Not only MDegrain.

Why do you include the avs2yuv64.exe than?
RipBot264v1.19.6\Tools\avs2yuv\avs2yuv64.exe
-Update- Don't mean to come off hostile, just wondering if there are other places that RipBot will use the x64 version?

[Atak_Snajpera]

Because It is part of package. Generally I do not delete any files after extraction. I just keep everything intact.
https://github.com/MasterNobody/avs2yuv/releases

[byteshare]

Originally Posted by Atak_Snajpera

Because It is part of package. Generally I do not delete any files after extraction. I just keep everything intact.
https://github.com/MasterNobody/avs2yuv/releases

Thank you for the clarification.

[Nosirus]

Originally Posted by Atak_Snajpera

What happens if you manually run \\DESKTOP-8NBTRJ0\RipBot264temp\Job1\Chunks\1.cmd from remote-pc?

Ps. That behaviour seen on your video means that something is wrong with shared folder. (ACCESS DENIED)

It works fine, if I run 1.cmd from another computer

But, this other computer, also does not want to encode with the option "distributed encoding"

edit:
I have an NAS encoder directly on are disk that is in network will fix the problem? If yes, how ?

[Atak_Snajpera]

When you get this https://youtu.be/ScGt6vEu5co what do you see in Encoding Server app window?

[Nosirus]

Originally Posted by Atak_Snajpera

I mean that every single plugin which is used by RipBot264 would have to be 64bit. Not only MDegrain.

Just "encode" then "encoding termined" loop

I do not know how to make it work once, it seems to link to the "residential group" but the folder "D:\Temp\RipBot264temp" is automatically deleted

The network management of windows is really a horror!

I often have this error

[Atak_Snajpera]

Have you disabled Password protected sharing?
https://youtu.be/b-BICnj62iE?t=13s

[sirjaymz]

Looking at most of the scripts created, it looks as if RB uses the netbios name of the locations of the directories and file locations.

can you make it so that i can use a share on a NAS instead?

I gather that in the ripbot264.ini file that the variable TEMP translates into a netbios name for the temp location and the job working directory when in DE mode.

I tried setting the TEMP variable as
StoreTempFilesin=\\nas\sharedrive as the temp location,
which Iwould translate expect it to translate to
\\nas\sharedrive\Temp\RipBot264temp\
But that doesn't seem to work.

Any plan to allow us to use a NAS unit instead of having the files local? or suggestions how i could accomplish?

[Nosirus]

Originally Posted by Atak_Snajpera

Have you disabled Password protected sharing?
https://youtu.be/b-BICnj62iE?t=13s

Yes i had followed tutorial

The folder share "D:\Temp\RipBot264temp" is well indicated, but I have to re-apply it for it to work

RipBot264 seems to change rights every time, possible?

[Atak_Snajpera]

How about this question?

When you get this https://youtu.be/ScGt6vEu5co what do you see in Encoding Server app window?

[jlpsvk]

@Atak_Snajpera
Anything new with too long command when trying to encode 4K HDR with distributed encoding? Any chance for a quick fix?

[Nosirus]

Originally Posted by Atak_Snajpera

How about this question?

Just "encoding terminated" in loop

https://www.youtube.com/watch?v=3MMWx1ni_Fk

What's happening, thanks for your support

[byteshare]

Originally Posted by Nosirus

Just "encoding terminated" in loop

https://www.youtube.com/watch?v=3MMWx1ni_Fk

What's happening, thanks for your support

Something is wrong with your setup. Can you go into the job folder and use AvsPmod to see if the script checks out?
For example:
C:\Temp\RipBot264temp\Job238\Chunks\1.avs
load the 1.avs into AvsPmod while the encode is trying in RipBot and see what error it gives you (bottom left click the triangle).
AvsPmod: https://avspmod.github.io/

[Danette]

In version 1.19.6, the batch function is not working correctly (at least, not on my Win7 system). Previous versions were fine.

I add the files (about 45 files) and they all appear in the “Batch mode” batch list. However, when I click “Start”, the pre-processing begins, but only the first 3 files are processed out of the 45 in the batch list. I then click “Done”, after those 3 are pre-processed, and those 3 files appear, as they should, in the list of jobs that begin to process. Those 3 then are converted correctly.

Also, thanks Atak_Snajpera, for adding custom script in batch mode, although I haven’t tried it yet due to the above problem.