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

[slalom]

So avisynth can't handle the memory required above a number of processors. Even if there are 2 DE servers?

[rlev11]

So avisynth can't handle the memory required above a number of processors. Even if there are 2 DE servers?

Each DE server will use the same cache size sent to it.

The default cache size for avisynth (and i do not know exactly what it is, but it is not enough) is not large enough when doing all the extra bits when doing 4k encoding and using avisynth-prefetch-threads setting once that number hits 16 or larger. Encoding performance drops off a cliff if:
A: the cache is not specified to at least 8192 or
B: we tell ripbot to only use 12 of the 16 cores either by reducing the avisynth-prefetch-threads or disabling cores using an affinity mask. Either way turns your system into a 12 core machine for ripbot performance wise.

Before we figured out the cache was the issue, I had to do 4k encoding with my 5950 and 7950's essentially performing as 5900 and 7900's. The 16 core Ryzens would perform at about half the fps of a 12 core Ryzen without crippling them (hence falling off the cliff). Of course a crippled 16 core would not fully perform like it should for 1080p either, so I had to have 2 different encoding server profiles, one for 1080 and below, and another crippled one for 4k and switch them depending on what I was encoding. Now with the cache being set to 8192 automatically in Ripbot, I no longer have to worry about anything, The 16 core Ryzens perform like they should automatically using all the cores regardless of the resolution.

[hardkhora]

\\192.168.0.1\Ripbot264temp instead of \\MY-PC\Ripbot264temp

Is there any disadvantage of using IP address in path? What are your thoughts?
This might actually help in some of the issues I've had in Windows.
I don't see it making an impact in Linux (still getting issues with Wine binding the port though for DE mode).

[hardkhora]

Since I pass through the cores from Linux to the RB virtual machine, I can mix and match.
Do you use any kind of PCIe or GPU passthrough for KNLMeansCL?
If so, which Distro are you using?

[Ryushin]

EPYC Turnin 9355P 32-Core Processor
24 Cores and 48 Threads Passed to VM
Blade Runner 4K 15 Minute Clip - 3840x1600

Encoding Servers SetMemoryMax() Prefetch x265-threads SMDerain Chunk Size CPU Time
1 8192 24 48 None 20 70% 22m:29s
1 16384 24 48 None 20 70% 22m:49s
1 8192 28 48 None 20 70% 22m:46s
1 16384 28 48 None 20 70% 23m:03s
1 16384 28 48 None 1 70% 24m:50s
1 8192 24 48 Hard 20 75% 27m:23s
1 16384 24 48 Hard 20 88% 21m:56s
1 16384 27 48 Hard 20 90% 20m:10s
1 16384 28 48 Hard 20 93% 19m:45s
1 16384 29 48 Hard 20 98% 19m:51s
1 16384 32 48 Hard 20 98% 20m:22s
2 8192 12 24 None 1 85% 24m:16s
2 16384 12 24 None 1 85% 22m:34s
2 8192 12 24 Hard 1 83% 24m:38s
2 16384 12 24 Hard 1 85% 24m:30s
2 8192 14 24 None 1 88% 20m:46s
2 16384 14 24 None 1 88% 21m:16s
2 8192 14 24 Hard 1 95% 24m:08s
2 16384 14 24 Hard 1 95% 24m:25s
1 12288 28 48 Hard 20 90% 20m:40s

Okay, I think I've finished my testing. Summary is SetMemoryMax to 16384 is a big help with 48 threads. Using a single encoding server was the faster compared to using two when encoding 4K. So it would be beneficial to have the option to SetMemoryMax per machine or at a minimum the option to set it for global. The Prefetch also needs to be increased from half of thread count to about 60% of thread count for optimum performance.

I guess for me, I'll move to a single encoding server for 4K content, and run dual encoding servers for HD content, though I still need to test HD content. I know for 2560x1400, two encoding servers for x265 was about 30-50% faster. Another test to do later.

[rlev11]

So looks to me like a cache estimate of 8 gig per 16 avisynth-prefetch-threads is reasonable as it scales up. I would imagine when you had prefetch threads set to 24 moving the cache down to 12 gig probably would have been fine as well.

I'll do some testing over the next couple of days bumping the cache up to 16384 and even beyond and see how the couple servers I only have 16 gig on them react. I have a 5950x and a 5900x with 16 gig total system memory, so it will be interesting to see the results using prefetch threads of 16 and 12 respectively. Having 16gig cache sent down to them may work without any issues, or may bog the system down.

Just curious with the hard SMdegrain what were your appx best fps numbers you were seeing in the encoding server window?

[Ryushin]

So looks to me like a cache estimate of 8 gig per 16 avisynth-prefetch-threads is reasonable as it scales up. I would imagine when you had prefetch threads set to 24 moving the cache down to 12 gig probably would have been fine as well.

I'll do some testing over the next couple of days bumping the cache up to 16384 and even beyond and see how the couple servers I only have 16 gig on them react. I have a 5950x and a 5900x with 16 gig total system memory, so it will be interesting to see the results using prefetch threads of 16 and 12 respectively. Having 16gig cache sent down to them may work without any issues, or may bog the system down.

Just curious with the hard SMdegrain what were your appx best fps numbers you were seeing in the encoding server window?

Was not really watching the fps very much. But the number of frames in the 15 minute source (15*60*23.796) video is 21416 and with 19m:45s being the fastest encoding time we get 18.072 fps.

8 GB per 16 threads is probably a good method. I just did another run with 12288 MB and the CPU graph was more spiky as some threads were waiting (added it to the previous post). So for 24 cores, 16384 MB is better. 32 cores might need another 8 GB. I suppose for testing sake, I can run two more tests giving the full 32 cores to the VM and see what that gives us.

[Ryushin]

So it looks like I encountered a limit to RB when trying to select 32 cores in my VM. So I narrowed it down and selecting 26 cores and two threads (52 threads total) results in RB crashing.

Starting Ripbot gives me a Division by Zero error, clicking okay on the error then shows the Ripbot window.

Starting the Encoding server I get a Invalid Pointer Operation then another two error windows:

---------------------------
Encodingserver
---------------------------
Access violation at address 00401EBA in module 'EncodingServer.exe'. Write of address 00000000.
---------------------------

and

---------------------------
Application Error
---------------------------
Exception EAccessViolation in module EncodingServer.exe at 00001EBA.
Access violation at address 00401EBA in module 'EncodingServer.exe'. Write of address 00000000.
---------------------------

It's almost like Atak couldn't imagine all those years ago we would have so many cores in a chip. :)

With the latest EPYC having 192 cores 384 threads, might as well use a 16 bit integer now. LOL

[Atak_Snajpera]

That sucks. Does EncodingClient.exe also crash in the same way?

If you disable SMT (26 cores/26 Threads) will it crash as well?

[Ryushin]

That sucks. Does EncodingClient.exe also crash in the same way?

If you disable SMT (26 cores/26 Threads) will it crash as well?

I disabled SMT and just passed cores to the VM. As soon as I enabled 51 cores the problem occurs. I had one job in the queue and it does not show up since it tried to divide by zero, so I can't test the Encoding Client.

[Atak_Snajpera]

So it looks like I encountered a limit to RB when trying to select 32 cores in my VM. So I narrowed it down and selecting 26 cores and two threads (52 threads total) results in RB crashing.

Starting Ripbot gives me a Division by Zero error, clicking okay on the error then shows the Ripbot window.

Starting the Encoding server I get a Invalid Pointer Operation then another two error windows:

---------------------------
Encodingserver
---------------------------
Access violation at address 00401EBA in module 'EncodingServer.exe'. Write of address 00000000.
---------------------------

and

---------------------------
Application Error
---------------------------
Exception EAccessViolation in module EncodingServer.exe at 00001EBA.
Access violation at address 00401EBA in module 'EncodingServer.exe'. Write of address 00000000.
---------------------------

It's almost like Atak couldn't imagine all those years ago we would have so many cores in a chip. :)

With the latest EPYC having 192 cores 384 threads, might as well use a 16 bit integer now. LOL

1) run this on crashing configuration
https://www.mediafire.com/file/mwfb6dfmzhswms3/server.exe/file

2) show me content of server.exe.txt file

[Ryushin]

1) run this on crashing configuration
https://www.mediafire.com/file/mwfb6dfmzhswms3/server.exe/file

2) show me content of server.exe.txt file

Here you go:
1:SysNative=C:\WINDOWS\SysNative
2:AviSynthVersion=avisynth+ 3.7.3 (r4003, 3.7, x86_64)

[Atak_Snajpera]

How many logical processors (threads) did you set in VM?
Looks like it crashes at function which checks numbers of logical processors.

[Ryushin]

1) run this on crashing configuration
https://www.mediafire.com/file/mwfb6dfmzhswms3/server.exe/file

2) show me content of server.exe.txt file

How many logical processors (threads) did you set in VM?
Looks like it crashes at function which checks numbers of logical processors.

I changed it back to 26 cores and 2 threads for each core. So 52 logical processors.

[Atak_Snajpera]

I changed it back to 26 cores and 2 threads for each core. So 52 logical processors.

So limit is 32 logical processors ? Everything above than means crash, right?

[Atak_Snajpera]

Does this application also crash?
https://www.mediafire.com/file/b2ak4ato2dwr63b/FlopsCPU.7z/file

[Ryushin]

Does this application also crash?
https://www.mediafire.com/file/b2ak4ato2dwr63b/FlopsCPU.7z/file

That works fine:
https://i.postimg.cc/QHmDnqnw/FlopsCPU.png (https://postimg.cc/QHmDnqnw)

Edit:

Changed VM to 32 cores and 2 threads per core:
https://i.postimg.cc/MXxKPXpc/Flops-CPU-32-Cores.png (https://postimg.cc/MXxKPXpc)

Task Manager:
https://i.postimg.cc/G9Q3Zr4X/Task-Manager.png (https://postimg.cc/G9Q3Zr4X)

[Atak_Snajpera]

I did not expect that...
So What is the highest number of logical processors which does not cause crash in server.exe?

[Ryushin]

I did not expect that...
So What is the highest number of logical processors which does not cause crash in server.exe?

It crashes using 51 logical processor. The Windows VM does not seem to make a distinction between cores and threads, it seems to count them the same.

I added a couple more images to the previous post.

[Atak_Snajpera]

It crashes using 51 logical processor. The Windows VM does not seem to make a distinction between cores and threads, it seems to count them the same.

I added a couple more images to the previous post.

52 also crashes ?

[Ryushin]

52 also crashes ?

52 crashes as well. Anything above 50 seems to crash.

[Atak_Snajpera]

I assume You can't check whether crash also happens on real Windows environment? You are using Linux as host for VM ,right?

[Ryushin]

I assume You can't check whether crash also happens on real Windows environment? You are using Linux as host for VM ,right?

Correct, Linux is the Hypervisor and Windows is the guest VM.

[Atak_Snajpera]

I have no clue why it crashes exactly above 50 threads. (32> would make more sense due to 32bit limitation) The same code for CPU detection in FlopsCPU seems to be working fine. I wished we had somebody here with Threadripper 32C/64T running on real windows...
I remember that 2990WX was working fine with ripbot. However that was 4 NUMA CPU and real Windows OS.

[Ryushin]

I have no clue why it crashes exactly above 50 threads. (32> would make more sense due to 32bit limitation) The same code for CPU detection in FlopsCPU seems to be working fine. I wished we had somebody here with Threadripper 32C/64T running on real windows...
I remember that 2990WX was working fine with ripbot. However that was 4 NUMA CPU and real Windows OS.

I can try to make a WinToUSB stick and boot my server off of it and give it a test. I'll need to do it after hours though.

[Atak_Snajpera]

no rush. it is already a 22:00 here...

[Ryushin]

no rush. it is already a 22:00 here...

So I made a Win To Go USB stick which turned out to be more involved then I wanted it to be. Nonetheless, the error does not occur under Windows 11 using the EPYC 9355P processor.

https://i.postimg.cc/1g4jjsVV/Win-11-EPYC-9355-P-Encoding-Server.png (https://postimg.cc/1g4jjsVV)

https://i.postimg.cc/063BgF7W/Win-11-EPYC-9355-P-Task-Manager.png (https://postimg.cc/063BgF7W)

So it probably is something with running Windows in a VM. There is something about going over 50. I'll see if I can get the Linux VM software to accurately emulate cores and threads so I can better test this.

Could also be something that Windows 11 fixes compared to Windows 10. I'm planning on upgrading that VM to Windows 11 since Windows 10 is doomed in less then a year.

Atak, I can also create a VM that you can log in remotely to do testing if you like in order to diagnose where the problem is.

[Atak_Snajpera]

So I made a Win To Go USB stick which turned out to be more involved then I wanted it to be. Nonetheless, the error does not occur under Windows 11 using the EPYC 9355P processor.

https://i.postimg.cc/1g4jjsVV/Win-11-EPYC-9355-P-Encoding-Server.png (https://postimg.cc/1g4jjsVV)

https://i.postimg.cc/063BgF7W/Win-11-EPYC-9355-P-Task-Manager.png (https://postimg.cc/063BgF7W)

So it probably is something with running Windows in a VM. There is something about going over 50. I'll see if I can get the Linux VM software to accurately emulate cores and threads so I can better test this.

Could also be something that Windows 11 fixes compared to Windows 10. I'm planning on upgrading that VM to Windows 11 since Windows 10 is doomed in less then a year.

Atak, I can also create a VM that you can log in remotely to do testing if you like in order to diagnose where the problem is.

Thank you for your time and testing. If it works fine on real machine then like you said it might be a problem with VM itself or Windows 10 running under VM.

[Ryushin]

Thank you for your time and testing. If it works fine on real machine then like you said it might be a problem with VM itself or Windows 10 running under VM.

Upgraded my VM to Win 11. Still the same crash. I'll see if there is a way to trick the VM to have cores and threads, but Windows and the Hypervisor may talk directly and just show virtual cores regardless since to the VM, it's not relevant.

[Atak_Snajpera]

Upgraded my VM to Win 11. Still the same crash. I'll see if there is a way to trick the VM to have cores and threads, but Windows and the Hypervisor may talk directly and just show virtual cores regardless since to the VM, it's not relevant.

is there only one VM software available on linux?

[Ryushin]

is there only one VM software available on linux?

The best Hypervisor software for Linux is KVM/QEMU, which is built into the kernel. It's near bare metal performance. I'm setting up a new VM to virtualize the processor instead of passing it through. It's Win11 now that is being difficult as it wants certain CPU features in order to even boot the ISO. I'll get it sorted though.

[TR-9970X]

I've been itchin' to post here, (but I had to wait 5 days) especially after all the discussion about the new default settings for Avisynth

SetCacheMode(CACHE_FAST_START)
SetMemoryMax(8192)

And there isn't any option for the user to modify it, you could possibly edit it after a job has been set up, but that's a bit cumbersome.

However, if a custom script was used that had a different value, would that over ride this default setting ?

This change sparked a discussion about high core count CPU's, and the possible need to have a higher SetMemoryMax value.

Will this be addressed sometime soon, or...


Then another more crippling problem I have had in the past week is, if I install a clean Windows 11 24H2, RipBot throws up an error with the Encoding Client, and that stops it from starting to encode.

I have Googled this problem, and tried many suggestions, but as yet, none fix this issue.

However, this only seems to occur when installing a fresh 24H2, if you've updated from 23H2, to 24H2, it works.

So whether there's some change that can be done to RipBot regarding Shared Folder Authentication, or some change with 24H2, it's a no go for RipBot.

Has anyone else had this problem ?, I've tried 24H2 on 4 different PC's, with the same Authentication problem with RipBot.

Here's the error :-

https://i.imgur.com/bjbwe78.jpg

[rlev11]

I don't use a password on my local boxes, I think I had the run these 2 commands from powershell as an admin. 24h2 forces smb signing. If you have 11 pro I think there is a group policy settings you can set, but 11 Home users have to run these scripts.

Set-SmbClientConfiguration -RequireSecuritySignature $false

Set-SmbClientConfiguration -EnableInsecureGuestLogons $true

[Atak_Snajpera]

Any idea how to bypass that stupid compatibility check in win11 24H2 installer when installing in VMware?

[rlev11]

Any idea how to bypass that stupid compatibility check in win11 24H2 installer when installing in VMware?

have you tried this:

When the Windows 11 setup begins, proceed until you see the "This PC can't run Windows 11" error message.
Open the Registry Editor:

Press Shift + F10 to open a Command Prompt.
Type regedit and press Enter to launch the Registry Editor.
Bypass TPM and CPU Checks:

Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\Setup
Right-click on Setup, select New > Key, and name it LabConfig.
Inside the LabConfig key, create the following DWORD values:
BypassTPMCheck: Set the value to 1.
BypassSecureBootCheck: Set the value to 1.
BypassRAMCheck: Set the value to 1 (optional for low RAM).
BypassCPUCheck: Set the value to 1.
Exit and Continue:

Close the Registry Editor and Command Prompt.
Click the Back button in the installer and proceed again.

[Atak_Snajpera]

have you tried this:

When the Windows 11 setup begins, proceed until you see the "This PC can't run Windows 11" error message.
Open the Registry Editor:

Press Shift + F10 to open a Command Prompt.
Type regedit and press Enter to launch the Registry Editor.
Bypass TPM and CPU Checks:

Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\Setup
Right-click on Setup, select New > Key, and name it LabConfig.
Inside the LabConfig key, create the following DWORD values:
BypassTPMCheck: Set the value to 1.
BypassSecureBootCheck: Set the value to 1.
BypassRAMCheck: Set the value to 1 (optional for low RAM).
BypassCPUCheck: Set the value to 1.
Exit and Continue:

Close the Registry Editor and Command Prompt.
Click the Back button in the installer and proceed again.

Thanks! It works now.

[Atak_Snajpera]

I've been itchin' to post here, (but I had to wait 5 days) especially after all the discussion about the new default settings for Avisynth

SetCacheMode(CACHE_FAST_START)
SetMemoryMax(8192)

And there isn't any option for the user to modify it, you could possibly edit it after a job has been set up, but that's a bit cumbersome.

However, if a custom script was used that had a different value, would that over ride this default setting ?

This change sparked a discussion about high core count CPU's, and the possible need to have a higher SetMemoryMax value.

Will this be addressed sometime soon, or...


Then another more crippling problem I have had in the past week is, if I install a clean Windows 11 24H2, RipBot throws up an error with the Encoding Client, and that stops it from starting to encode.

I have Googled this problem, and tried many suggestions, but as yet, none fix this issue.

However, this only seems to occur when installing a fresh 24H2, if you've updated from 23H2, to 24H2, it works.

So whether there's some change that can be done to RipBot regarding Shared Folder Authentication, or some change with 24H2, it's a no go for RipBot.

Has anyone else had this problem ?, I've tried 24H2 on 4 different PC's, with the same Authentication problem with RipBot.

Here's the error :-

https://i.imgur.com/bjbwe78.jpg

Did you put correct login and password here?
https://i.postimg.cc/bJbvM9g9/Capture.png

It seems to be working fine with my 24H2 on VM
https://i.postimg.cc/CSw-LVGRq/Capture.png

[rlev11]

When my servers updated to 24h2 later in the fall, nothing changed, but now that I think of it, I definitely had a connection issue with DE when I loaded a couple of them from scratch to 24h2 bout a month ago. the 2 powershell scripts did fix it. Other option I guess would be to add another local admin user to the client? with a password , and use that in the DE settings screen for file sharing back to the temp folder. Like I said I have always used a local account with no password to log into my boxes so I did the smb signing disable. The additional user should work as well, I have to do that on my box I send Veam image backups to. connecting to the file share in the Veam setup requires putting in a password.

[hardkhora]

You have backed up my theory that this issue doesn't occur if the 24H2 install is an update from 23H2, but a fresh install does.

I have tried many "fixes", Powershell commands, Group Policy settings, etc, etc, and nothing has changed it.

I'm using Pro for Workstations, btw.

As I see it, it's either installing 23H2, then updating to 24H2 right after, OR no passwords.


Tested the no password scenario, and that didn't work
Guessing you also tried to see if you could navigate with explorer to the share path without a password showing up?
If no password shows up, then I'm not sure because I've solved this before by just saving the login/password with Explorer.
Hopefully it helps, if not sorry.

[archiel]

I don't usually use DE but I though I would re-enable to see if I could replicate the temp sharing issue on a clean 24H2 install (i had already run into sharing issues elsewhere that had not existed on 23H2, nor on machines updated from 23H2).

HOWEVER, when I went back to my old DE settings, the encoding servers (ES) would load but would not connect, and there were no messages. Looking further I saw that while the ES is pointed at the LAN IP ServerIP1=127.0.0.1:1000 (in EncodingClient.ini) it is picking up two adapters
[ADAPTER0] 00-15-5D-91-23-50 = 172.30.192.1
[ADAPTER1] A8-A1-59-EA-FC-8A = 10.50.60.115

and under Network it is showing the settings for ADAPTER0, which are the settings of the Hyper-V Virtual Ethernet Adapter - ADAPTER1 is IP of the Ethernet adapter vEthernet (External Virtual Switch) and the LAN address

I then looked at RipBot264 on another PC, which also had some Hyper-V components installed (for Windows sandbox) and exhibited the same issue - the Network settings for the ES showed the Hyper-V Virtual Ethernet Adapter and would not connect to the Encoding client. Removing the Windows Sandbox and associated Hyper-V settings, but making no other changes the allowed DE to run normally.

So my initial question is how to run DE locally on a PC that has Hyper-V installed, so that the ES connects to the LAN IP/MAC not the IP of the Hyper-V Virtual Ethernet Adapter.

[rlev11]

I don't usually use DE but I though I would re-enable to see if I could replicate the temp sharing issue on a clean 24H2 install (i had already run into sharing issues elsewhere that had not existed on 23H2, nor on machines updated from 23H2).

HOWEVER, when I went back to my old DE settings, the encoding servers (ES) would load but would not connect, and there were no messages. Looking further I saw that while the ES is pointed at the LAN IP ServerIP1=127.0.0.1:1000 (in EncodingClient.ini) it is picking up two adapters
[ADAPTER0] 00-15-5D-91-23-50 = 172.30.192.1
[ADAPTER1] A8-A1-59-EA-FC-8A = 10.50.60.115

and under Network it is showing the settings for ADAPTER0, which are the settings of the Hyper-V Virtual Ethernet Adapter - ADAPTER1 is IP of the Ethernet adapter vEthernet (External Virtual Switch) and the LAN address

I then looked at RipBot264 on another PC, which also had some Hyper-V components installed (for Windows sandbox) and exhibited the same issue - the Network settings for the ES showed the Hyper-V Virtual Ethernet Adapter and would not connect to the Encoding client. Removing the Windows Sandbox and associated Hyper-V settings, but making no other changes the allowed DE to run normally.

So my initial question is how to run DE locally on a PC that has Hyper-V installed, so that the ES connects to the LAN IP/MAC not the IP of the Hyper-V Virtual Ethernet Adapter.

So How I have mine setup on my main client PC is in the ripbot.ini file I have this line that specifies the ip address of my local adapter, and not a vpn connection i also use. Yours of course may be different depending on your ip and cpu parameters. This forces the encoding server to use these settings when I open ripbot initially.
Server1CommandLine=/ip 192.168.1.201 /port 1000 /priority normal /restart-if-no-progress /avisynth-prefetch-threads 16 /x264-threads 32 /x265-threads 32

If you want to open a second server on the same client PC, just add into the ripbot.ini file this. You can also start a second server using the .bat file below by adding a second line and change the port to 2000 as well.
Server2CommandLine=/ip 192.168.1.201 /port 2000 /priority normal /restart-if-no-progress /avisynth-prefetch-threads 16 /x264-threads 32 /x265-threads 32

For my machines I have setup as encoding servers I just start them with a .bat file that has the same parameters in them like this:

encodingserver /ip 192.168.1.201 /port 1000 /restart-if-no-progress /priority normal /avisynth-prefetch-threads 16 /x264-threads 32 /x265-threads 32

[TR-9970X]

Seeing as no one seems to be interested in commenting on this question,

https://forum.doom9.org/showthread.php?p=2014035#post2014035

I have gone back in history to see when this option was added.

And if this older version of RipBot264.exe is used with the latest EC & ES, it appears to work well, and the Custom Scripts will instruct Avisynth what to do.

And just incase some of you "power users" haven't noticed, there are some new interesting commands in the latest ES build's, making this command line possibly redundant:-

Server1CommandLine=/ip 192.168.1.201 /port 1000 /priority normal /restart-if-no-progress /avisynth-prefetch-threads 16 /x264-threads 32 /x265-threads 32

I also challenge anyone to get RipBot to encode anything, either using single or DE modes, with a fresh real setup of Windows 11 24H2, NOT on any VM.

I've spent 3 days on this, and I have found my solution.

[archiel]

So How I have mine setup on my main client PC is in the ripbot.ini file I have this line that specifies the ip address of my local adapter, and not a vpn connection i also use. Yours of course may be different depending on your ip and cpu parameters. This forces the encoding server to use these settings when I open ripbot initially.
Server1CommandLine=/ip 192.168.1.201 /port 1000 /priority normal /restart-if-no-progress /avisynth-prefetch-threads 16 /x264-threads 32 /x265-threads 32

If you want to open a second server on the same client PC, just add into the ripbot.ini file this. You can also start a second server using the .bat file below by adding a second line and change the port to 2000 as well.
Server2CommandLine=/ip 192.168.1.201 /port 2000 /priority normal /restart-if-no-progress /avisynth-prefetch-threads 16 /x264-threads 32 /x265-threads 32

For my machines I have setup as encoding servers I just start them with a .bat file that has the same parameters in them like this:

encodingserver /ip 192.168.1.201 /port 1000 /restart-if-no-progress /priority normal /avisynth-prefetch-threads 16 /x264-threads 32 /x265-threads 32

I had forgotten about specifying the IP in Server#CommandLine=, will try this later and let you know if this worked.

Thanks

[archiel]

Seeing as no one seems to be interested in commenting on this question,

https://forum.doom9.org/showthread.php?p=2014035#post2014035

I have gone back in history to see when this option was added.

And if this older version of RipBot264.exe is used with the latest EC & ES, it appears to work well, and the Custom Scripts will instruct Avisynth what to do.

And just incase some of you "power users" haven't noticed, there are some new interesting commands in the latest ES build's, making this command line possibly redundant:-

Server1CommandLine=/ip 192.168.1.201 /port 1000 /priority normal /restart-if-no-progress /avisynth-prefetch-threads 16 /x264-threads 32 /x265-threads 32

I also challenge anyone to get RipBot to encode anything, either using single or DE modes, with a fresh real setup of Windows 11 24H2, NOT on any VM.

I've spent 3 days on this, and I have found my solution.

I have a clean install of Win 11 24H2 and have not had any issues - RB runs on the main machine, not on a VM. Once I have modified my Server#CommandLine entries as Rlev11 suggested, I will test it in DE mode.

While definitely not being a power user and not normally a DE user, I am still curious as to what changes there have been in ES and where I would find them.

[TR-9970X]

I have a clean install of Win 11 24H2 and have not had any issues - RB runs on the main machine, not on a VM. Once I have modified my Server#CommandLine entries as Rlev11 suggested, I will test it in DE mode.

What variant of 24H2 do you use ? eg:- Home, Pro...

I have tried 4 different fresh installs on 4 different PC's, and every time RipBot will fail the Authentication on the shared Temp folder, and therefore will go no further.

While definitely not being a power user and not normally a DE user, I am still curious as to what changes there have been in ES and where I would find them.


There's 2 different places to get a list of the commandline options.

Easiest is the under the Help tab of the Encoding Server window.

[archiel]

What variant of 24H2 do you use ? eg:- Home, Pro...

I have tried 4 different fresh installs on 4 different PC's, and every time RipBot will fail the Authentication on the shared Temp folder, and therefore will go no further.



There's 2 different places to get a list of the commandline options.

Easiest is the under the Help tab of the Encoding Server window.

I am running Win 11 pro. For clarity when I refer to single mode, I mean with DE turned off, so there is no requirement for access to the temp folder in shared mode and hence no issue. Once I have the connection issue sorted, I will re-enable DE and test.

[TR-9970X]

I am running Win 11 pro. For clarity when I refer to single mode, I mean with DE turned off, so there is no requirement for access to the temp folder in shared mode and hence no issue. Once I have the connection issue sorted, I will re-enable DE and test.

I'm running Pro for Workstations, and have been for years with no issue with 23H2 & older.

Single mode still needs to use the Temp folder.

[archiel]

Okay - connect to ES is now fixed, password-less sharing is enabled and I am getting exactly the same error
Command "AUTHENTICATE" received from client
ERROR! File \\10.50.60.115\RipBot264Temp\job5\Chunks\1.cmd does not exist!

How did you eventually solve this?

[TR-9970X]

Okay - connect to ES is now fixed, password-less sharing is enabled and I am getting exactly the same error
Command "AUTHENTICATE" received from client
ERROR! File \\10.50.60.115\RipBot264Temp\job5\Chunks\1.cmd does not exist!

How did you eventually solve this?

Not surprised...have a look at my other posts that show the 2 different errors, with & without passwords.

I found the only way I can get around this, is a fresh setup of 23H2 and then immediately upgrade that with 24H2 and whatever the difference is, it keeps the good stuff from 23H2 that 24H2 hasn't got, that causes this error.. that needs to be addressed by the author of the app.

[archiel]

Not surprised...have a look at my other posts that show the 2 different errors, with & without passwords.

I found the only way I can get around this, is a fresh setup of 23H2 and then immediately upgrade that with 24H2 and whatever the difference is, it keeps the good stuff from 23H2 that 24H2 hasn't got, that causes this error.. that needs to be addressed by the author of the app.

I was afraid that you might suggest that. I have had already run into SMB sharing issues using Everyone with other programs which suggests that there is a new security setting (or bug) in 24H2, but so far I have not seen any way of determining which it is or how to fix it.