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

[guest]

Latest I can see is Core 2019.11.08, Scripts 2019.11.13, MKVtoolnix 40.0.0
(would be easier to tell if the point versions changed with each update)

I got an update this morning, only got mkvtoolnix v40, lsmash had an error, and couldn't be downloaded...

No changes to core...

Nice subtle hint there too, btw (doesn't work tho)

[guest]

Did you try it?
That solved my problem with LSMash some time ago

Yes, I have now tried it, and unfortunately, it didn't worked :(

[byteshare]

Sry for the late response, but i got a really busy day. @byteshare i also use only Windows Defender, i already had an exception for the Temp Directory but not for the Ripbot Directory. I also excluded the Ripbot folder but it changed nothing. After Going back to Version 1.24 from the first post here DE Mode was working again but as soon as i allow Ripbot updating itself to 1.25 DE Mode is broken again. There is absolutely no TCP communcation between Encoding Server and Client.
Hmm, I'm honestly not sure what has changed since I'm not having an issue, and you have already checked the Windows Defender and Firewall exceptions. And, if I remember correctly, confirmed your port is open.
Also, Pauly Dunne already mentioned better to link to an image from an image hosting site such as Imgur.
So, I'll try to think of something but sorry I'm out of ideas at the moment.
If there was a way to control which version you're on at least then you could roll back to a specific version that worked for you. I keep backups for this reason.

[howzz]

speaking of version control. is there a way to get to a previous version? i noticed the main page only gives you up to v24, but there's been countless updates since v24. i just need the version prior to Nov 3rd.

[guest]

speaking of version control. is there a way to get to a previous version? i noticed the main page only gives you up to v24, but there's been countless updates since v24. i just need the version prior to Nov 3rd.

It would be nice to have that...

Na, you're plum outta luck on that one, 'cause I'm sure you know, if you were to download v1.24 off the 1st page, and then do an update, you'd be right back with the problem build.

So you'll be after core build 22-10-18, the last one that DE works with ?

However, having said that, I might be able to help you with your problem..

PM me...

[guest]

In my quest to try and figure what might be the problem with DE not working for several of us, I have been swapping & changing different versions of EncodingClient.exe & EncodingServer.exe, using RB build (22-10-19), I know I'm no wiz when it comes to this, but I'm thinking that it might be the Encoding Client that has a problem, as from what I can see, it's looking for the wrong ports.

Have a look at the 2 screenshots, and decipher it for yourself..

using newest server, with older client.

https://www.mediafire.com/view/42ijlyrc5weqcna/wrong_ports.jpg/file

compared to this...what it should look like..

https://www.mediafire.com/view/6bt2apknpcjoos4/this_works.jpg/file

I'd guess that it's not desirable to mix and match, but you've gotta try a few things...trial & error, and I could be completely off the mark, here.

[byteshare]

In my quest to try and figure what might be the problem with DE not working for several of us, I have been swapping & changing different versions of EncodingClient.exe & EncodingServer.exe, using RB build (22-10-19), I know I'm no wiz when it comes to this, but I'm thinking that it might be the Encoding Client that has a problem, as from what I can see, it's looking for the wrong ports.

Have a look at the 2 screenshots, and decipher it for yourself..

using newest server, with older client.

https://www.mediafire.com/view/42ijlyrc5weqcna/wrong_ports.jpg/file

compared to this...what it should look like..

https://www.mediafire.com/view/6bt2apknpcjoos4/this_works.jpg/file

I'd guess that it's not desirable to mix and match, but you've gotta try a few things...trial & error, and I could be completely off the mark, here.
Guessing that the old Encoding Server 1.15.2.0 didn't work with the newer Encoding client?
also, what is happening on the "Main" window of the Encoding Server? If you can make a really good step-by-step of the things you've tried and the issues, maybe, someone would be able to figure it out. Not saying I'll figure it out, but you never know...sometimes I'm even right twice in a day (broken clock).

[guest]

Guessing that the old Encoding Server 1.15.2.0 didn't work with the newer Encoding client?
also, what is happening on the "Main" window of the Encoding Server? If you can make a really good step-by-step of the things you've tried and the issues, maybe, someone would be able to figure it out. Not saying I'll figure it out, but you never know...sometimes I'm even right twice in a day (broken clock).

Hey byteshare...

yes I know I probably should have written it down step by step, I also would think that mixing up different versions and build stuff probably isn't a good idea, but I was just a bit puzzled about incorrect looking port numbers, etc.

Maybe I'll do it again, and this time I'll document it.

edit:- or maybe I won't, with more comments on a problem, surely it will be addressed soon.

[Privateer5000]

I am not quite sure concerning the Firewall exceptions, will check it later the day. But Windows Defender has exceptions for both, Ripbot and Ripbot Temp Folder. Do i have to add exceptions to my Router Firewall as Well or only in NY machine? I mean at the moment the Client does not reach the Encoding Server running in the same machine. Another thing i realized but i do not know If it ist Important. With Version 1.24 in thhe Overview Window the Encoding Server ist named after my machine's Networkname and with Version 1.25 it ist still named "Server 1". Is it possible that the Main Problem ist that the Client is not able to detect the Encoding Server? And yes, since Yesterday in the evening i cannot create Jobs anymore, Ripbot stops with the Message that a DLL from LSmash is Missing.

[MCFish]

Just tried in a clean vm, and same happens. Queue in chunk status and no progress

[Privateer5000]

So, checked Firewall Setting, has exceptions for Ripbot Encodingclient and Encodingserver, for testing i deactivated the firewall completly but no change. Chunks are being prepared and then nothing. The Client tries to connect to the Server but the Server do not recognize anything.

[Ronski]

I seem to be having the same problem, I've not used Ripbot for a while, went to use it today, both installations updated, now it just sits there with the encoding client showing "Pass1...[0.0%] 0/163714 frames, 0.00 fps, 0 kbps, eta" and the encoding servers showing waiting for connection on both machines. The encoding client shows all my encoding clients as offline.

Just noticed on my main PC the servers are v1.15.2.0 and on the other it's v1.16.0.0.

If I set distributed encoding to auto reconnect then the server icons in the client flicker as it seems to try to reconnect.

[FuzzyNutz]

I identified this issue here before and it seemed to be addressed shortly after. Now the issue is back. If the version of MKVToolNix GUI on a users system is newer than that associated with the RipBot264 update, the update should leave MKVToolNix untouched.

Please make it so!

[guest]

I seem to be having the same problem, I've not used Ripbot for a while, went to use it today, both installations updated, now it just sits there with the encoding client showing "Pass1...[0.0%] 0/163714 frames, 0.00 fps, 0 kbps, eta" and the encoding servers showing waiting for connection on both machines. The encoding client shows all my encoding clients as offline.

Just noticed on my main PC the servers are v1.15.2.0 and on the other it's v1.16.0.0.

If I set distributed encoding to auto reconnect then the server icons in the client flicker as it seems to try to reconnect.

Just like this :-

http://www.mediafire.com/file/aoz3zppgbcvrbia/2019-11-13_13-49-35.rar/file

[guest]

Hey guys,

There was another auto update posted "overnight" (my time), for core & lsmash (lsmash from failed download yesterday).

Only ripbot264.exe was updated, however, sadly the DE problems persists :(

Better luck next time...

[Dhry]

I had to return to RB 1.24 (core 20190123) with encodingclient 1.12.10 and encodingserver 1.15.2 on the machines in my farm. It works. I have to run the mux.cmd etc stuff manually for every file I batch encode, but it works.
Will stay tuned to this thread in case the fix arrives. But one thing's for absolute certain, the latest RB has significant issues with DE. Whatever connectivity-oriented code that was updated in EC 1.16 pretty much needs to be rolled back. Thanks for your work Atak.

Dhry

[guest]

You might be done with me, but I'm done, here...

I have a suggestion for future updates, that should prevent situations like this, where more & more users are commenting on the DE problem, that I tried to help with.

There is very little control over how updates for RB work, you either get them, or you don't...simple as that.

The problem is, it all happens quite covertly in the background (if you're online), and the only noticable way you know there's been an update is the next time you start the app, and you see the little pop up window appear as the updates are being installed, and by that time it's too late to do anything about it.

Then, if there's a major problem (like now), the user has very limited options, either try to use the app as is, OR download the latest available FULL version from page 1, and leave it at that, as doing an autoupdate just takes you straight back to the problem build (vicious circle).

Unfortunately, the only available build is v1.24, which is way back in January '19, as you haven't bothered to post v1.25, for what ever reason, not that that would be much different, in this case, but better.

So my suggestion is, that you implement some "pop up" that tells the user that "an update is available, would you like to download it", that gives the user a heads up, and a choice, and gives them time to maybe backup their current configuration, so just incase theres a problem, they can be roll it back to the previous working state.

And another thing that might help, is that EVERY update has an incremental change to the version number...we've been on 1.25.0 for months, it should be 1.25.34, or 1.30 by now....

[byteshare]

You might be done with me, but I'm done, here...

I have a suggestion for future updates, that should prevent situations like this, where more & more users are commenting on the DE problem, that I tried to help with.

There is very little control over how updates for RB work, you either get them, or you don't...simple as that.

The problem is, it all happens quite covertly in the background (if you're online), and the only noticable way you know there's been an update is the next time you start the app, and you see the little pop up window appear as the updates are being installed, and by that time it's too late to do anything about it.

Then, if there's a major problem (like now), the user has very limited options, either try to use the app as is, OR download the latest available FULL version from page 1, and leave it at that, as doing an autoupdate just takes you straight back to the problem build (vicious circle).

Unfortunately, the only available build is v1.24, which is way back in January '19, as you haven't bothered to post v1.25, for what ever reason, not that that would be much different, in this case, but better.

So my suggestion is, that you implement some "pop up" that tells the user that "an update is available, would you like to download it", that gives the user a heads up, and a choice, and gives them time to maybe backup their current configuration, so just incase theres a problem, they can be roll it back to the previous working state.

And another thing that might help, is that EVERY update has an incremental change to the version number...we've been on 1.25.0 for months, it should be 1.25.34, or 1.30 by now....

I could see this being more user friendly, but you can disable auto update as it is to avoid your worries.

For anyone having issues with DE mode with the updated version try this one: https://mega.nz/#!loRCjSAQ!9TaUwv2yOPkBnN3M63C_ThEbON_jgyzNyONObQInsbQ
This is the first version since the change to allow suspend on a remote server. It works for me, and FYI, between this version and the one before it I was prompted by my Firewall to allow it.
If it doesn't work, I can upload the version just prior to it for testing.
With Lsmash 2019.11.16, Scripts 2019.11.13, MKVtoolnix 40.0.0, and Core 2019.11.16
It also works for me, and I believe those are the most recent versions.

[guest]

I could see this being more user friendly, but you can disable auto update as it is to avoid your worries.

For anyone having issues with DE mode with the updated version try this one: https://mega.nz/#!loRCjSAQ!9TaUwv2yOPkBnN3M63C_ThEbON_jgyzNyONObQInsbQ
This is the first version since the change to allow suspend on a remote server. It works for me, and FYI, between this version and the one before it I was prompted by my Firewall to allow it.
If it doesn't work, I can upload the version just prior to it for testing.
With Lsmash 2019.11.16, Scripts 2019.11.13, MKVtoolnix 40.0.0, and Core 2019.11.16
It also works for me, and I believe those are the most recent versions.

Hey byteshare,

Just noticed your post...

I know that you can disable auto update, but then you could fall a long way behind with updates...it would be nice if it wasn't "sneaky". lol.

I will download your "version" and see what it does, but the last one that DE work for me, was core 22-10-19, EC 1.15.2.

I was going to post the pre core 08-11-19, EC 1.16.0 version for people to fall back on.

edit: just tried your build, still doesn't work for me :(

[byteshare]

I will download your "version" and see what it does, but the last one that DE work for me, was core 22-10-19, EC 1.15.2.

I was going to post the pre core 08-11-19, EC 1.16.0 version for people to fall back on.
Yeah, you could post that.
I'm not sure what is causing issues for people because it works for me.
You could try running RipBot from a different folder name, and if you have a firewall or any thing else setup it should treat RB like it is a new program and prompt you to allow traffic and/or maybe if something else is blocking RB than that other thing blocking RB wont? Not sure, just trying to put some ideas out there.
I'm using FFMS2 as the decoder, but I think you and several other people are not using Lsmash as the default decoder for most things.
edit: just tried your build, still doesn't work for me :(
Okay, what ever changed it started with that version then for the people that are having issues with DE.
Does non-DE mode work?

[guest]

Yeah, you could post that.
I'm not sure what is causing issues for people because it works for me.
You could try running RipBot from a different folder name, and if you have a firewall or any thing else setup it should treat RB like it is a new program and prompt you to allow traffic and/or maybe if something else is blocking RB than that other thing blocking RB wont? Not sure, just trying to put some ideas out there.
I'm using FFMS2 as the decoder, but I think you and several other people are not using Lsmash as the default decoder for most things.

Isn't that almost a contradiction...I am using Lsmash, but that won't have any affect on DE.

I've got all the firewalls turned off...

Okay, what ever changed it started with that version then for the people that are having issues with DE.
Does non-DE mode work?

Haven't had any problems when not using DE !!

I don't really know why we're stuffing around with this, its clearly a problem that has to be resolved by the dev.

[Privateer5000]

@byteshare
Non-DE Mode is working for me with every Version, just DE Mode is broken.
What Firewall are you using? But shouldn't the Test with nmap make sure that the Firewall lets Traffic through?
I do not think that the choice of the Decoder ist causing the Problem because we never get that far that it is used. I will try your Version later that das, also your Suggestion to use a new Folder, maybe IT helps.

But there is something that must be said. @Pauly Dunne: you have eine good points and in some points i totally agree with you. Yes, IT would have been nice to get more Info about what was changed or even get es little hint If our testing ist helpfull or points in the wrong direction. Also your Idea with the PopUp Windows with an Update Notification ist good, wanted to make a Feature request myself after the actual Problem is solved. But i totally disagree with the way you are posting. Like Atak Said, Ripbot ist a free Software, i guess He ist making it Out of Passion and in his free time, because i do not believe he can live from the donations He may or may Not receive. No one of us has any right to ask for or request something. We all can be thankful that he shares his work with us instead of doing it only for himself. So please Stop your childish Kindergarten-like way of Posting ("better Lück next time"), it is not helpful. I would totally understand it when Atak Stop the Public support for Ripbot If everybody treats him Like you did.
Like i said, you have good ideas that i support, but not the way how you post here

[guest]

@byteshare
Non-DE Mode is working for me with every Version, just DE Mode is broken.
What Firewall are you using? But shouldn't the Test with nmap make sure that the Firewall lets Traffic through?
I do not think that the choice of the Decoder ist causing the Problem because we never get that far that it is used. I will try your Version later that das, also your Suggestion to use a new Folder, maybe IT helps.

But there is something that must be said. @Pauly Dunne: you have eine good points and in some points i totally agree with you. Yes, IT would have been nice to get more Info about what was changed or even get es little hint If our testing ist helpfull or points in the wrong direction. Also your Idea with the PopUp Windows with an Update Notification ist good, wanted to make a Feature request myself after the actual Problem is solved. But i totally disagree with the way you are posting. Like Atak Said, Ripbot ist a free Software, i guess He ist making it Out of Passion and in his free time, because i do not believe he can live from the donations He may or may Not receive. No one of us has any right to ask for or request something. We all can be thankful that he shares his work with us instead of doing it only for himself. So please Stop your childish Kindergarten-like way of Posting ("better Lück next time"), it is not helpful. I would totally understand it when Atak Stop the Public support for Ripbot If everybody treats him Like you did.
Like i said, you have good ideas that i support, but not the way how you post here

Fair enough Privateer5000, I will take your comments into consideration.

However, I don't really think it's childish to say "better luck next time", when you're waiting for something, and it doesn't happen.

[slalom]

I read about your problems
My DE works fine even after yesterdays update (win 7 everywere)

[Ronski]

Just like this :-

http://www.mediafire.com/file/aoz3zppgbcvrbia/2019-11-13_13-49-35.rar/file

Yes just like that.

I use Ripbot as is, no modifications apart from what's in the settings, and then it's only very minor things I change from default. Ripbot still works fine when not using DE, so my encodes currently take a little longer.

I have two encoding servers on the machine which hosts Ripbot, surely if it was a firewall issue they would still work? I also turned off my AV which made no difference. Just tried using the other machine (W7) as the host and it still doesn't work, so doesn't seem to be a Windows 10 thing.

A few years back I wrote some free software, and it's user base was very limited (unlike Ripbot), but support was hard and trying to keep up with every ones requests was time consuming. I did implement an auto update system, but the user had total control, there was also an option to backup the old version, and always a change log, there was also a beta version and release version

[guest]

Yes just like that.

I use Ripbot as is, no modifications apart from what's in the settings, and then it's only very minor things I change from default. Ripbot still works fine when not using DE, so my encodes currently take a little longer.

I have two encoding servers on the machine which hosts Ripbot, surely if it was a firewall issue they would still work? I also turned off my AV which made no difference. Just tried using the other machine (W7) as the host and it still doesn't work, so doesn't seem to be a Windows 10 thing.

A few years back I wrote some free software, and it's user base was very limited (unlike Ripbot), but support was hard and trying to keep up with every ones requests was time consuming. I did implement an auto update system, but the user had total control, there was also an option to backup the old version, and always a change log, there was also a beta version and release version

Yes, it's certainly strange how it's working for some, and not for others, and I guess that will be hard to diagnose, and fix.

And I have certainly been rubbing some people up the wrong way, but I'm just trying to get a point across....

[guest]

So I thought I'd post another "special" build of RB, which is v 1.25.0, core v 26-12-19, EC 1.17.0

It's the latest build, but has a couple of "handy" extra's

https://www.mediafire.com/file/96g4oa4mspostcq/Special_RipBot264.7z/file

I hope this will be useful for some....

I've had 24 downloads of this previous build I made available here:-

http://www.mediafire.com/file/vmd9rx70mmtdowi/RipBot264v1.25.0_%2528special%2529.rar/file

I think this was the build prior to the auto chunk combining (it worked for me)

I have removed these links, as they are really no longer relevant.

[Privateer5000]

Just double checked for the Firewall. I deactivated the Firewall and deleted the Rules concerning Ripbot but sadly no change. Running from another Directory did not change anything either. So i have to stick with 1.24 until this is fixed or perhaps Pauly is uploading his Version Core 22-10-19, EC 1.15.2. I do not know what else i could test for now.

Edit says: Pauly was faster :-) Thanks for the Upload

[Atak_Snajpera]

Let's investigate this issue STEP by STEP
1) Enable builtin system firewall and disable ALL 3rd party software like antivirus/antimalware
2) Open Firewall settings and remove all entries regarding encodingclient.exe and encodingserver.exe
https://i.postimg.cc/jtkFjZ22/Capture.png
3) Restart PC
4) Now when you click on EncodingServer.exe you should see this pop-up window
https://i.postimg.cc/02Ln0XKC/Capture2.png
5) Now run nmap.exe with this command line nmap.exe -Pn -p 1000 [YOUR IP HERE]
https://i.postimg.cc/v823cZQk/Capture6.png
Port is Open and EncodingServer also detected connection from nmap.

And here working connection between EncodingClient.exe and EncodingServer.exe

https://i.postimg.cc/nLx16skj/Capture5.png

[Privateer5000]

So, did Step 1-4.
This is Result for Step 5

https://i.ibb.co/WymysQR/Ripbot2.jpg (https://ibb.co/ncxcRTK)

It says Port 1000 is open, but the Encoding Server shows no reaction

[Atak_Snajpera]

Try this
nmap.exe -Pn -sT -p 1000 192.168.0.101

[Privateer5000]

This Command Line work and Server reacts:
https://i.ibb.co/LNZwVjv/Ripbot3.jpg (https://ibb.co/g4R1kq6)

But when i open the EncodingClient there is no reaction.

https://i.ibb.co/0jNmrH4/Ripbot4.jpg (https://ibb.co/7JcjKsM)

[Ronski]

Try this
nmap.exe -Pn -sT -p 1000 192.168.0.101

I'm getting the same results as Privateer, the above line caused the encoding server to react - this works for each encoding server when the port and IP address is changed as required, the previous one did not.

No reaction from the encoding client though.

[Atak_Snajpera]

I'm getting the same results as Privateer, the above line caused the encoding server to react, the previous one did not. No reaction from the encoding client.

That's still something.
This at least means that nothing is blocking connection and EncodingServer v1.16 is also ok. So it has to be some weird bug in EncodingClient...

[byteshare]

So it has to be some weird bug in EncodingClient...
Did you maybe put in a too broad of a variable for when you setup the block Pauly Dunne pc command ;)

[Atak_Snajpera]

Did you maybe put in a too broad of a variable for when you setup the block Pauly Dunne pc command ;)

Looks like my detection code is buggy... ;)
Ok. Jokes aside! I will post debug version of encodingclient for those reporting this issue. It should help me to track down where in code bad things happens...

[guest]

Did you maybe put in a too broad of a variable for when you setup the block Pauly Dunne pc command ;)

WOW, I saw what you did there.....

OMG, you're now my new BFF :)

[guest]

Looks like my detection code is buggy... ;)
Ok. Jokes aside! I will post debug version of encodingclient for those reporting this issue. It should help me to track down where in code bad things happens...

Not sure if you had a look at the screenshots I posted back at #17756, but I kinda thought back then, (even tho I was swapping and changing EC's & ES's around), that EC seemed to be looking for, and/or detecting the wrong ports.

[howzz]

i thought i'd report back to everyone that looks like another update came out over the weekend that updated Lmash and Core. looks like this latest update fixed the slow "gathering information" problem once again, and when you click on "start" encoding, it doesn't take forever for CPU cores to load up anymore.

i am going to image this version of RB and set it aside for backup.

but i agree with Paul Dunne in regards to version control, it would be a good idea to either post all the versions for users to download, or at the very least, have some kind of pop up that notifies user a new update is available and only upon clicking "yes", the update goes through. this way users can at least get a chance to backup their RB version prior to updating. otherwise we'll constantly run into downloading and updating to the broken version. obviously, everyone's setup is different. so what's broken for one person may very well work fine for others. but some kind of measure should be implemented regarding updates. we love updates and new features, and thank the author for that, but a layer of version control/protection is much needed.

[MCFish]

Atak, i see encodingclient/server uses ports 61200 and upwards (maybe) internally when it works (before the 1.16 update) maybe something with those ports...or the using of them.
https://i.postimg.cc/jjc8Vb16/rbcpold.jpg

[0gg]

Atak_Snajpera : thank you agin for this great job.

Could you be pleased to add these feature :

able to decode mxf files
adding custom timecode on mp4 or the timecode of the source

??

... to encode files from DSLR / Camera to lower resolution / proxy file but with the same timecode of the sources

0gg / augur.

[Atak_Snajpera]

Run this debug version and show me what messages you get
https://www.mediafire.com/file/9zic1q57t0gqqpt/client.exe/file

example screenshot from my machine
https://i.postimg.cc/1RZv7jXf/Capturex.png

[MCFish]

CheckIP(192.168.0.8:1000)=false
CheckIP(192.168.0.2:1000)=false
CheckIP(192.168.0.12:1000)=false
CheckIP(192.168.0.8:1000)=false
CheckIP(192.168.0.2:1000)=false
CheckIP(192.168.0.12:1000)=false
CheckIP(192.168.0.8:1000)=false
CheckIP(192.168.0.2:1000)=false
CheckIP(192.168.0.12:1000)=false
CheckIP(192.168.0.8:1000)=false
CheckIP(192.168.0.2:1000)=false
CheckIP(192.168.0.12:1000)=false

etc etc etc

[Atak_Snajpera]

CheckIP(192.168.0.8:1000)=false
CheckIP(192.168.0.2:1000)=false
CheckIP(192.168.0.12:1000)=false
CheckIP(192.168.0.8:1000)=false
CheckIP(192.168.0.2:1000)=false
CheckIP(192.168.0.12:1000)=false
CheckIP(192.168.0.8:1000)=false
CheckIP(192.168.0.2:1000)=false
CheckIP(192.168.0.12:1000)=false
CheckIP(192.168.0.8:1000)=false
CheckIP(192.168.0.2:1000)=false
CheckIP(192.168.0.12:1000)=false

etc etc etc

What happens if you enter 192.168.1.2:1000

[MCFish]

I assumed you meant i should enter it in 'Distributed Encoding Server IP'

it went so fast past me, but got something

CheckIP(192.168.0.8:1000)=false
CheckIP(192.168.0.2:1000)=false
CheckIP(192.168.0.12:1000)=false
IP="192.168.1.2:1000"
CheckIP(0.0.0.0:0)=false
CheckIP(0.0.0.0:0)=false
CheckIP(0.0.0.0:0)=false
CheckIP(0.0.0.0:0)=false
CheckIP(0.0.0.0:0)=false
CheckIP(0.0.0.0:0)=false
CheckIP(0.0.0.0:0)=false
CheckIP(0.0.0.0:0)=false
CheckIP(0.0.0.0:0)=false
CheckIP(0.0.0.0:0)=false
CheckIP(0.0.0.0:0)=false
CheckIP(0.0.0.0:0)=false
Starting workerthread
CheckIP(192.168.0.8:1000)=false
CheckIP(192.168.0.2:1000)=false
CheckIP(192.168.0.12:1000)=false
Connecting to "192.168.1.2:1000"
CheckIP(192.168.0.8:1000)=false
CheckIP(192.168.0.2:1000)=false
CheckIP(192.168.0.12:1000)=false
CheckIP(192.168.0.8:1000)=false
CheckIP(192.168.0.2:1000)=false
CheckIP(192.168.0.12:1000)=false
CheckIP(192.168.0.8:1000)=false
CheckIP(192.168.0.2:1000)=false
CheckIP(192.168.0.12:1000)=false

There was a timout further down, guess it was for 192.168.1.2

[Privateer5000]

https://i.ibb.co/87HYRFd/Ripbot5.jpg (https://ibb.co/S3zf1qd)

With correct IP it does not find it, with 192.168.1.101:1000 it seems to find something but Connection timed out

[Atak_Snajpera]

I have located a bug in my function CheckIP. This function basically checks if ip values entered by user are in valid range of 0-255. It also checks other things like number of dots and if port is divisible by 1000 but that was not a problem here. Problem was that if you had 0 in ip (for example 192.168.0.1) then function was returning FALSE and hence no connection to server. This explains why it worked for me since I have IPs without zero value (192.168.1.100)

[Atak_Snajpera]

This version should work now
https://www.mediafire.com/file/zat5jd4as3wa1jl/EncodingClient.exe/file

[MCFish]

YES, great man. Thx
https://i.postimg.cc/sXsPCYgG/rbworks.jpg

[Atak_Snajpera]

Ok then BRACE YOURSELF! AUTO-UPDATE IS COMING!