Open wtvRecorder.ini, set “Ports=6121”...
See log…
“Setting new filter expression: port 6112 or port 6121 or port 1 or port 23585”...
Why?
And after all of that its not the end…
Next messages at recorder log is…

[21:23:31:388] [r] [00] Send: local Server: ‘my_ip:6119’, game:‘Game 1’
[21:23:31:388] [r] [ERROR] Cannot record game without observer. Please activate ‘observer’-settings!
[21:23:33:404] [r] [00] Send: local Server: ‘my_ip:6117’, game:‘Game 2’
[21:23:33:404] [r] [ERROR] Cannot record game without observer. Please activate ‘observer’-settings!

So…Then for what that setting?
I have 3 ghost bots at differents ports and I configure wtv only on one of them…

Pls fix this so if i set ports=need_port then recorder try to record games only from need_port…

Thx anyway…

does the ghost bot at that port have observers enabled? the recorder might actually try to record the correct game, but it cannot do that if there are no observers. wtv works by “cloning” the traffic which is sent to one observer, so if there is no observer there is no traffic that can be cloned, and hence it does not work.

for the technical stuff with port selection you’ll have to wait for someone who knows the internals of the recorder, i don’t ;)

Ofc I have observer in game at ghost on port 6121…
When the game starts on port 6121 I see at log “Ready for game start” and “Recording” after the game started, but after random time recorder begins mixing(also mixing may start before I will see “Ready for game start”/“Recording” state)...
He tries to read from another ports and receives a error(bcz there is no observers at games on other ports and I dont need observers in these games)...

well okay then first of all please notice that our software so far simply is not considered to be used with multiple games on one computer as that usually never happens when playing with the normal client. So the first “official” reply is, that we simply do not support that. The port setting in the ini file was originally considered to be a “additionally, check this port” setting i think, which explains the behavior you are experiencing.

You may be lucky and if volker checks in here some time soon, and considers this to be a easy change, he might implement it or just compile you a special version or something. But if that does not happen, you will have to live with “we don’t support such an application scenario”.

If suitable you can try a couple of workarounds, for instance the observer could run the recorder, but that might be all we can offer you.

>You may be lucky and if volker checks in here some time soon, and considers this to be a easy change, he might implement it or just compile you a special version or something.

I would really hope so…
Anyway, thx for reply.