View Full Version : RipBot264 v1.18.3 - Simple and easy to use GUI -> IPOD . PSP . CONSOLES . BLURAY
Ryushin
7th April 2020, 13:21
Not sure if it's just me, or a coincidence, but I think I've seen a 30 percent reduction in h.265 encoding speed since the last couple of updates or so. If everything appears normal to everyone else, then its probably just me.
stryker412
7th April 2020, 14:30
All depends on how clean the source is. I use CQ18 for high quality and CQ21 for the streaming encodes. I've had some 4K sources that were so clean that compressed so well I was concerned something was wrong. Watching it shows that it looks excellent. It's amazing how much data can be saved sometimes on some sources when just applying a very light MDegrain2 with a thSAD=100 value. I've had a video go from 17GB to 10GB with this very light degraining.
I've also noticed that 4K sources compress a lot better than their HD counterparts. I suspect it is because of 10 bit color vs 8 bit for HD. As an example I would have a 4K source that I resize to 1080p (for streaming) and it comes out to say 1.5GB. I take the HD 1080p source and resize it to 720p (for streaming) and it would not be unusual that it would be 1.5GB or even a little larger than the 1080p 4K.
My source will be direct off the UHD disc. I use MakeMKV to create a MKV first direct from the disc (untouched audio/video) then use Ripbot to shrink it down.
I was just having a hard time believing that a 60+GB movie can get down to 4.5GB with 4K video, HDR, and audio without looking like crap. I did see the bitrate was only 4.5Mbps
Ryushin
7th April 2020, 15:34
My source will be direct off the UHD disc. I use MakeMKV to create a MKV first direct from the disc (untouched audio/video) then use Ripbot to shrink it down.
I was just having a hard time believing that a 60+GB movie can get down to 4.5GB with 4K video, HDR, and audio without looking like crap. I did see the bitrate was only 4.5Mbps
I'm thinking almost all studios encode at a certain bit rate and they are done. I don't think any studio uses the constant quality setting. Imagine the fallout a studio would get if a 4K movie could fit on a single layer 25GB disc even with them using a CQ of 12-15 or so. For purists, more bits is always better, even if the more bits doesn't get them anything.
stryker412
7th April 2020, 18:54
Does this seem right for my system? This is for H265, CQ 16.
https://i.imgur.com/pBsjdPx.png
https://i.imgur.com/n7j0B1i.png
stryker412
8th April 2020, 12:40
Can anyone tell me why this keeps happening? I ran it twice just to make sure it wasn't a one-off issue.
https://drive.google.com/open?id=1c1ha9RE-y93WcCjLypA81gj9BmdWnlCI
Ryushin
8th April 2020, 14:54
Can anyone tell me why this keeps happening? I ran it twice just to make sure it wasn't a one-off issue.
https://drive.google.com/open?id=1c1ha9RE-y93WcCjLypA81gj9BmdWnlCI
Which decoder are you using? Looking at the settings now, it looks like Atak has taken the option away other than CPU/GPU.
Is this happening using DE or single server?
stryker412
8th April 2020, 14:59
This is with DE (my first attempt using it). I only have it set to 2 instances though. From the previous comments, I set everything back to CPU before running this attempt. I only watched a few minutes of it but out of the first 10 minutes or so this is the only time I saw this happen. However, this is also a chapter break.
Edit: I just looked and the video does it again on the 3rd chapter then the video cuts out entirely for about 5-6 minutes (audio is fine).
Edit 2: I just tried in Handbrake using the h.265 (nvenc) setting. I'm averaging around 43FPS and an encode time of just over an hour. That's a massive difference compared to using CPU. I'm not sure why in Ripbot, when I set it to GPU it doesn't seem to honor that setting.
Ryushin
8th April 2020, 18:17
This is with DE (my first attempt using it). I only have it set to 2 instances though. From the previous comments, I set everything back to CPU before running this attempt. I only watched a few minutes of it but out of the first 10 minutes or so this is the only time I saw this happen. However, this is also a chapter break.
Edit: I just looked and the video does it again on the 3rd chapter then the video cuts out entirely for about 5-6 minutes (audio is fine).
Edit 2: I just tried in Handbrake using the h.265 (nvenc) setting. I'm averaging around 43FPS and an encode time of just over an hour. That's a massive difference compared to using CPU. I'm not sure why in Ripbot, when I set it to GPU it doesn't seem to honor that setting.
Try running the video without DE. Handbrake is also not doing 10bit color yet from what I remember. I think there is also the issue that the GPU produces less quality than using the CPU in Handbrake if you are using it for encoding.
stryker412
8th April 2020, 19:09
Try running the video without DE. Handbrake is also not doing 10bit color yet from what I remember. I think there is also the issue that the GPU produces less quality than using the CPU in Handbrake if you are using it for encoding.
Doing it now. Will let you know how it goes in 10hrs or so. :D
Atak_Snajpera
8th April 2020, 23:07
This is with DE (my first attempt using it). I only have it set to 2 instances though. From the previous comments, I set everything back to CPU before running this attempt. I only watched a few minutes of it but out of the first 10 minutes or so this is the only time I saw this happen. However, this is also a chapter break.
Edit: I just looked and the video does it again on the 3rd chapter then the video cuts out entirely for about 5-6 minutes (audio is fine).
Edit 2: I just tried in Handbrake using the h.265 (nvenc) setting. I'm averaging around 43FPS and an encode time of just over an hour. That's a massive difference compared to using CPU. I'm not sure why in Ripbot, when I set it to GPU it doesn't seem to honor that setting.
Looks like lsmash is having some problems with frame accurate seeking. I assume that this issue appears at new chunk. If you want this fixed please upload first 15 minutes of original(untouched!) video file. Use mkvtoolnix to split file and remove audio and subtitles. Next make sure that problem also is present in new sample. Then upload your sample somwhere and post link here.
chainring
9th April 2020, 02:33
What's a good CQ setting for h265? I generally use 10MBps for 1080 content and feel that's a good compromise between file size and quality. I tried my first H265 file and set it at CQ 20 which resulted in a 4GB file for Infinity War. That seems REALLY low.
While it's not directly comparable, I did Infinity War at CQ16 10bit with HDR intact, resized to 2560x1066 and have AC-3 640K. It came out to 4.68GB. Looks fantastic and I'm astounded by the reduction in size.
stryker412
9th April 2020, 18:23
Looks like lsmash is having some problems with frame accurate seeking. I assume that this issue appears at new chunk. If you want this fixed please upload first 15 minutes of original(untouched!) video file. Use mkvtoolnix to split file and remove audio and subtitles. Next make sure that problem also is present in new sample. Then upload your sample somwhere and post link here.
Here you go.
https://drive.google.com/open?id=1w2yGWMtET9fo0rNA85JW0jj2uaMfIC2W
Atak_Snajpera
11th April 2020, 14:08
Can anyone tell me why this keeps happening? I ran it twice just to make sure it wasn't a one-off issue.
https://drive.google.com/open?id=1c1ha9RE-y93WcCjLypA81gj9BmdWnlCI
Here you go.
https://drive.google.com/open?id=1w2yGWMtET9fo0rNA85JW0jj2uaMfIC2W
Looks like simple remuxing in MKVtoolnix fixed this issue because I'm not getting that weird jumping frames at 11:15 mark in encoded file. There was definitely something wrong with your untouched mkv file.
stryker412
11th April 2020, 19:16
Odd, I ran it twice with Ripbot and had issues both times. I ran the same file through Handbrake without issues.
Atak_Snajpera
11th April 2020, 20:16
Odd, I ran it twice with Ripbot and had issues both times. I ran the same file through Handbrake without issues.
Run your test again but this time use that 15 min sample and check if you have that issue at 11:15 mark. To speed up encoding you can resize down to 720p resolution. I even tested your sample in my SeekTester tool and again zero errors.
stryker412
12th April 2020, 13:37
I ran a 30 minute sample this time (in 4K again) and it didn't do it. I have no idea why it does it some times but not others.
Atak_Snajpera
12th April 2020, 15:08
I ran a 30 minute sample this time (in 4K again) and it didn't do it. I have no idea why it does it some times but not others.
I can only advise you to remux your mkvs in MKVToolnix before encoding. This step will ensure that your video file is correctly muxed and should not created any problems for decoder (no seeking issues in l-smash).
stryker412
12th April 2020, 19:30
I can only advise you to remux your mkvs in MKVToolnix before encoding. This step will ensure that your video file is correctly muxed and should not created any problems for decoder (no seeking issues in l-smash).
Ok thanks. My process for years has been to create an MKV directly off the disc using MakeMKV then re-encode (smaller file size) in Ripbot. This has worked flawlessly. However, this (Avengers) is my first real attempt at 4K HEVC. I never had the NAS space for 4K but now I do. I wanted to encode some of those now but this issue is the result. I'm running it again now just to see. It has another 5hrs left though.
stryker412
13th April 2020, 01:47
The process finished and this time it seems to be ok.
chainring
13th April 2020, 04:34
Quick bug report. Or, maybe not depending on if it's expected behavior.
File name of "Virtù e Fortuna" (Westworld S02, E03) caused RipBot to not pull in the audio. When I changed the filename to a "u" instead of one with the accent, all worked properly. The file had previously been remuxed with MKVToolnix just last week, FYI.
SKPN
13th April 2020, 14:27
Is there a way for RB to resume a job where it left off? My power went out last night after chunk 137 out of 152. I know I can manually run the other chunks from the folder, but I use distributed encoding to split the jobs between two PCs, and doing it manually would not allow me to use the other PC unless I were to make changes to my network sharing settings, which I don't want to do.
SKPN
13th April 2020, 14:39
What's a good CQ setting for h265? I generally use 10MBps for 1080 content and feel that's a good compromise between file size and quality. I tried my first H265 file and set it at CQ 20 which resulted in a 4GB file for Infinity War. That seems REALLY low.
I use CQ18, default/medium speed for all of my movies, and they look identical to the originals (to my eyes) on my 55" 4K TV. My Infinity War file is 12.4GB, though that also includes the untouched surround audio. The video alone is 7.60GB.
stryker412
13th April 2020, 14:46
I use CQ18, default/medium speed for all of my movies, and they look identical to the originals (to my eyes) on my 55" 4K TV. My Infinity War file is 12.4GB, though that also includes the untouched surround audio. The video alone is 7.60GB.
Ok mine came out to 17GB with the 5.1 audio track. I used CQ16.
Atak_Snajpera
13th April 2020, 14:47
Is there a way for RB to resume a job where it left off? My power went out last night after chunk 137 out of 152. I know I can manually run the other chunks from the folder, but I use distributed encoding to split the jobs between two PCs, and doing it manually would not allow me to use the other PC unless I were to make changes to my network sharing settings, which I don't want to do.
Normally progress (list of encoded chunks) should be saved automatically in file EncodingProgress.Pass1 in Chunks folder. After restart EncodingClient.exe loads that file and starts from last encoded chunk.
Ryushin
15th April 2020, 16:19
For the last few days, it seems that when doing automatic cropping in the AviSynth menu, the encoding client could crash. Seems to be doing it about 50% of the time. More so with 4K cropping, but it can do it with HD cropping as well. I've started to doing manual cropping to keep this from happening.
Anyone else seeing this or is it just me.
GZZ
16th April 2020, 06:55
Is it possible to get some kind of fix for foreign letters in filenames, it makes some of the script fail. Ex. A movie that include the danish letter æøå will make it crash in one or more script. Lets say this file: "Adams Æbler_t00.mkv"
It runs this script: "E:\RipBot264v\Tools\mkvtoolnix\mkvextract.exe" chapters "E:\Bluray_mkv\Adams Æbler_t00.mkv" -s > "E:\Temp\RipBot264temp\job91\chapters.txt"
But the Chapters.txt file only contains: Error: (mkvextract) This file could not be opened or parsed.
So when the movie finish to encode and it want to mux the video/audio/sub/chapter it failes with this:
e:\RipBot264v>"E:\RipBot264v\tools\mkvtoolnix\mkvmerge.exe" -o "E:\Encoding\Adams Æbler_t00.mkv" --compression 0:none --title "Adams Æbler_t00.mkv" --default-duration 0:24000/1001fps "E:\Temp\RipBot264temp\job91\video.265" --chapters "E:\Temp\RipBot264temp\job91\chapters.txt"
mkvmerge v45.0.0 ('Heaven in Pennies') 64-bit
Error: Unknown chapter file format in 'E:\Temp\RipBot264temp\job91\chapters.txt'. It does not contain a supported chapter format.
So if one job failes, it makes other fails later in the process.
instead of working around foreign letters like æøå or all other language special letters that can make it fail. Then either reject the file quickly or rename foreign letters to only allow english alphabet in filenames, then it wont crash randomly. This goes for symbols aswell, like the special dash symbol that is still an issue.
Update:
Another workaround is to save the script (*.cmd) as UTF-8 files and add this line to the top of the script: chcp 65001
It will change the Commandline prompt to UTF-8 and if the script file is UTF-8 format, then it will handle æøå correctly. But I dont know if this has other issues, like if a program dosnt handle UTF-8 (old Ansi only program), then it might fail anyway.
Atak_Snajpera
18th April 2020, 12:52
For the last few days, it seems that when doing automatic cropping in the AviSynth menu, the encoding client could crash. Seems to be doing it about 50% of the time. More so with 4K cropping, but it can do it with HD cropping as well. I've started to doing manual cropping to keep this from happening.
Anyone else seeing this or is it just me.
You are probably running out of memory. Autocropping 4k source consumes on my machine extra ~15 GiB of RAM. (Jump from ~7 GiB to 22 GiB). That's my theory...
https://i.postimg.cc/MTsPF1FZ/Untitled-1.png
Ryushin
19th April 2020, 01:44
You are probably running out of memory. Autocropping 4k source consumes on my machine extra ~15 GiB of RAM. (Jump from ~7 GiB to 22 GiB). That's my theory...
That's a pretty heavy duty theory and it's probably correct. I recently dropped my memory on my VM to 8GB from 16GB. Could also be why the cropping function has been taking a lot longer to complete. I'll up it again and see that happens.
Any thoughts on why cropping suddenly explodes the memory usage. For those without huge amounts of ram it could hurt them.
Atak_Snajpera
19th April 2020, 09:20
That's a pretty heavy duty theory and it's probably correct. I recently dropped my memory on my VM to 8GB from 16GB. Could also be why the cropping function has been taking a lot longer to complete. I'll up it again and see that happens.
Any thoughts on why cropping suddenly explodes the memory usage. For those without huge amounts of ram it could hurt them.
Because you are working with 3840x2160 resolution. Typical 1080p should consume 4x less memory.
Ryushin
19th April 2020, 11:05
Because you are working with 3840x2160 resolution. Typical 1080p should consume 4x less memory.
Just wondering what is happening behind the scenes for cropping to take any kind of significant memory. I thought frames where extracted looking for dark vs lighter pixels. I would think each frame would be a few meg in size and once it's read in and analyzed, it would be discarded and then the next frame would be read in.
I'm actually curious know about what happens behind the scenes to detect the cropping. I know I've had films sometimes the cropping is horribly wrong (about 1% of the time I would think). Other times, the cropping actually detected that the film had different aspect ratios in the film such as Tron Legacy and sometimes it missed the changed aspect ratio all together like in Batman Dark Knight. How many frames are compared and at what time increments in the film are they taken from?
Atak_Snajpera
19th April 2020, 11:36
I extract 16 frames for analysis. Everything is done simultanously for max CPU usage (threadripper 3990x anyone;)
I select frames from 25% to 75% of movie duration (in order to avoid credits at the begining and end of the movie)
userx
22nd April 2020, 19:55
I think it Has to be some driver issue. Capeverde is a first generation of gcn (HD 7000 series) with only 1gib of vram.
FoldAtHome is able to use the opencl ability of my card (ATI Radeo HD 7770) so I want to re-open this issue.
EncodingServer still has problems with the 1st pass. 2nd pass is working.
Encoding started...
""\\USERX-MASTER\Ripbot264temp\Tools\ffmpeg\bin\ffmpeg.exe" -loglevel panic -i "\\USERX-MASTER\RipBot264temp\job5\Chunks\5.avs" -strict -1 -f yuv4mpegpipe - | "\\USERX-MASTER\Ripbot264temp\tools\x264\x264_x64.exe" --seek 48 --colorprim bt709 --transfer bt709 --colormatrix bt709 --opencl --opencl-device 0 --opencl-clbin "C:\Users\UserX\AppData\Local\Temp\EncodingServer1\x264_lookahead.clbin" --pass 1 --bitrate 3000 --stats "\\USERX-MASTER\RipBot264temp\job5\Chunks\5.stats" --fps 25 --force-cfr --min-keyint 25 --keyint 250 --frames 1488 --sar 1:1 --profile main --level 4.1 --aud --nal-hrd vbr --vbv-bufsize 50000 --vbv-maxrate 50000 --b-pyramid none --ref 5 --stdin y4m --output NUL -"
y4m [info]: 1280x720p 1:1 @ 25/1 fps (cfr)
x264 [info]: using SAR=1/1
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
x264 [info]: OpenCL acceleration enabled with Advanced Micro Devices, Inc. Capeverde (SI)
x264 [info]: profile Main, level 4.1, 4:2:0, 8-bit
A
x264 [info]: profile Main, l
x264 [info]: profile Main, l
restarts afterwards
Stereodude
23rd April 2020, 14:56
Okay, so I'm back after giving ripbotx264 another try. :o
How do I fully manipulate the x265 options?
The encoding server shows me that it's encoding with this command line:
Encoding started...
""\\R9-3950X\Ripbot264temp\Tools\ffmpeg\bin\ffmpeg.exe" -loglevel panic -i "\\R9-3950X\RipBot264temp\job1\Chunks\2.avs"
-strict -1 -f yuv4mpegpipe - | "\\R9-3950X\Ripbot264temp\tools\x265\x265_x64.exe" --seek 120 --colorprim bt709
--transfer bt709 --colormatrix bt709 --crf 17.5 --fps 24000/1001 --min-keyint 24 --keyint 240 --frames 1420
--sar 1:1 --profile main10 --output-depth 10 --preset veryslow --pools 4 -F 1 --no-sao --aq-strength 1.15
--vbv-maxrate 40000 --vbv-bufsize 40000 --level-idc 5.1 --keyint 120 --open-gop --ctu 32 --merange 25 --y4m --output "+" -"
How do I get rid of these encoding options that ripbotx264 is appending that I don't want?
--min-keyint 24 --keyint 240
--ctu 32 --merange 25
Atak_Snajpera
23rd April 2020, 14:59
Just add your own switches in profile. x265 will ignore previous duplicated settings.
Stereodude
23rd April 2020, 15:22
Just add your own switches in profile. x265 will ignore previous duplicated settings.
It looks like it will ignore the the one that occurs first. That means I can override the --min-keyint 24 --keyint 240 , since it's put before my switches, but --ctu 32 --merange 25 are stuck on the end after my switches which means I can't override them.
Edit: Nevermind, I see that after adding --ctu 64 --merange 57 to my switches, ripbotx264 no longer appends --ctu 32 --merange 25.
Thanks!
Stereodude
23rd April 2020, 18:17
How do I encode on a 2nd NUMA node? The same x265 switches are used for all the encodes, so I don't think I can use a x265 switch. I launched additional encoding servers and set them to NUMA node 1 (instead of 0), but the encode only consumed CPU on node 0.
The x265 command line output shows this:
x265 [info]: Thread pool 0 using 4 threads on numa nodes 0,1
However, the CPU usage in the task manager shows all the threads are running on node 0.
Normally I would use --pools "-,4" in the x265 command line to push it to node 1 (or --pools "4,-" to push it to node 0) but AFAIK the same command line switches are used for all encodes with RipBot264.
Is there a way to sort this out?
Atak_Snajpera
23rd April 2020, 19:11
Just remove those --pools switches because you are overwriting my settings.
Stereodude
23rd April 2020, 20:00
Just remove those --pools switches because you are overwriting my settings.
That worked.
Is there another way to limit per encoder thread creation that doesn't break NUMA node handling? I'm not sure that the excessive threads each x265 session spawns are detrimental to quality, but they aren't doing anything beneficial either. -F 1 is the limiting throughput factor.
guest
24th April 2020, 01:47
As a new 3950X user myself, I would be interested to know if there are any different settings required for these Ryzen chips, over what I'm use to.
Like NUMA...... as Ryzen's don't have NUMA per se, they have CCX's & CCD's, which may or may not work the same.
I did my first run with the 3950X yesterday on a 1080p x264 to x265 conversion with a custom MDG 3 filter @ 800thd, and I found that running 3 servers seemed to be the sweet spot, and was processing @ around 25 fps. The same job on my "old" Xeon 12C with 2 servers was going to take over 6.5 hours, the Ryzen was about 2.
So if any 3950X (or better) users out there have some suggestions, it would be greatly appreciated...especially you, Atak.
Stereodude
24th April 2020, 03:23
AFAIK, Windows 10 1909 has the thread scheduling all sorted out to maximize the performance of the Zen 2 CPUs to avoid the issues with moving threads in a way that causes a performance loss.
Atak_Snajpera
24th April 2020, 06:25
As a new 3950X user myself, I would be interested to know if there are any different settings required for these Ryzen chips, over what I'm use to.
Like NUMA...... as Ryzen's don't have NUMA per se, they have CCX's & CCD's, which may or may not work the same.
I did my first run with the 3950X yesterday on a 1080p x264 to x265 conversion with a custom MDG 3 filter @ 800thd, and I found that running 3 servers seemed to be the sweet spot, and was processing @ around 25 fps. The same job on my "old" Xeon 12C with 2 servers was going to take over 6.5 hours, the Ryzen was about 2.
So if any 3950X (or better) users out there have some suggestions, it would be greatly appreciated...especially you, Atak.
Are you using single machine for encoding or more in distributed encoding mode?
guest
24th April 2020, 06:36
Are you using single machine for encoding or more in distributed encoding mode?
Well, atm I am just "testing" but using DE on a single pc, but definitely plan to get several other pc's helping with DE.
slalom
24th April 2020, 19:07
A question about auto shut down
I have 4 servers, 2, 3, 4, and 5
The client is 3. On settings -> shutdown, 3 cannot be selected, I want to close 3 and 4, 4 is selected in the menu
On the main window there are two options, shutdown client, shutdown servers
Which one should I select? or both options?
Atak_Snajpera
24th April 2020, 19:24
Both.
MCFish
27th April 2020, 10:12
Is it possible to get some kind of fix for foreign letters in filenames, it makes some of the script fail. Ex. A movie that include the danish letter æøå will make it crash in one or more script. Lets say this file: "Adams Æbler_t00.mkv"
I find it easyer to rename file to Adams Aebler first....then back again.
I think he have done something about these ' tho...found them much more annoying....
Scandinavian things 'vokser ikke på trær'
mikehbkwm
28th April 2020, 01:51
Good evening, I'm going to apologize up front because I know enough to be dangerous but that's about it. I LOVE Ripbot264 and can completely use it on my main machine (Desktop - HP AMD Ryzen 7, 16GB RAM) with no issues. With that said, I also have another HP desktop, HP laptop, and ASUS laptop and if memory serves, all are Intel Core i5's with 8GB of RAM for each.
When using distributed encoding all of my servers seem to be encoding except my main machine/client (newer HP). Since the main machine is the client, does it not encode files at all? Again, sorry if that's STUPID question. I seem to be able to encode files quicker with my main machine on it's own then using distributed encoding. Call me crazy, but I would think it should speed up the process if all machines are encoding at the same time. Please tell me if I'm missing something.
Side note: I've done some additional digging and it looks like you can use the client to encode as well. Is the client encoding along with the servers, or do you have to add the client to the list of servers (IP address)? I noticed my client IP is grayed out, I'm confused if that means the client is encoding or not. When I entered the client IP into the server IP list during distributed encoding, it does nothing and never connects. Very confused on what the client is doing during this process other then distributing chunks to the other servers.
Edited: I tried some other things tonight and can confirm my client (main PC/Desktop) is not encoding. For some reason it seems like the client is not being utilized for encoding and I cannot figure out why.
Thank you for your help and assistance.
BTW - this forum is GREAT!!
guest
28th April 2020, 07:47
Good evening, I'm going to apologize up front because I know enough to be dangerous but that's about it. I LOVE Ripbot264 and can completely use it on my main machine (Desktop - HP AMD Ryzen 7, 16GB RAM) with no issues. With that said, I also have another HP desktop, HP laptop, and ASUS laptop and if memory serves, all are Intel Core i5's with 8GB of RAM for each.
When using distributed encoding all of my servers seem to be encoding except my main machine/client (newer HP). Since the main machine is the client, does it not encode files at all? Again, sorry if that's STUPID question. I seem to be able to encode files quicker with my main machine on it's own then using distributed encoding. Call me crazy, but I would think it should speed up the process if all machines are encoding at the same time. Please tell me if I'm missing something.
Side note: I've done some additional digging and it looks like you can use the client to encode as well. Is the client encoding along with the servers, or do you have to add the client to the list of servers (IP address)? I noticed my client IP is grayed out, I'm confused if that means the client is encoding or not. When I entered the client IP into the server IP list during distributed encoding, it does nothing and never connects. Very confused on what the client is doing during this process other then distributing chunks to the other servers.
Edited: I tried some other things tonight and can confirm my client (main PC/Desktop) is not encoding. For some reason it seems like the client is not being utilized for encoding and I cannot figure out why.
Thank you for your help and assistance.
BTW - this forum is GREAT!!
Welcome...
Are you sure that the IP address & port # are the same as the client machine ??
More often than not, Encoding Client detects the correct info, and you generally have to manually enter the servers IP/Port info (at least you've got them going) so you must be very close to getting it to work.
Might be an idea to post some screen shots of Encoding Client window (but don't post if directly here, as an attachment).
If you open Encoding Server, on it's own, it will display the Clients IP address...everything needs to match up for DE to work properly.
Good luck.
mikehbkwm
28th April 2020, 17:49
https://i.imgur.com/YxkZxNZ.jpg
As you can see, on Server IP 2, 3, 4 those are my other machines and Ripbot found them no problem as I have the "Encoding Server" running on those machines. On my main machine, I've left Server 1 slot open and when I manually enter my Client IP address into that, it never connects. I am so confused as to why it never connects because I know the IP address and Mac Address. Again, thank you for your help on this.
Mike
slalom
28th April 2020, 19:04
Change 127.... to 192.168. whatever you have there
mikehbkwm
28th April 2020, 19:11
Change 127.... to 192.168. whatever you have there
That's what I stated in my post. I've already tried 192.168.....and that does not work. It never connects.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.