Ifighter quick rtpMidi question
Ifighter quick rtpMidi question Posted on: 20.07.2011 by Santos Louderback ok i've pretty much gone thru hell for two weeks trying to get it to work and i FINALLY got it working right, but now just one thing is getting in my way.On rtpMidi it keeps from what i believe to be losing signal, the latency meter about every 20 seconds after connecting goes to a "???" status, then it goes back and activates. Pretty annoying just don't know what it could be ? can anyone elaborate | |
| Santos Louderback 20.07.2011 | ok i've pretty much gone thru hell for two weeks trying to get it to work and i FINALLY got it working right, but now just one thing is getting in my way. On rtpMidi it keeps from what i believe to be losing signal, the latency meter about every 20 seconds after connecting goes to a "???" status, then it goes back and activates. Pretty annoying just don't know what it could be ? can anyone elaborate |
| Santos Louderback 21.07.2011 | ping test reading test is alot longer but for the sake of keeping it short, otherwise it was the same pretty much throughout the test. Reply from 192.168.2.101: bytes=32 time=235ms TTL=64 Reply from 192.168.2.101: bytes=32 time=830ms TTL=64 Reply from 192.168.2.101: bytes=32 time=3ms TTL=64 Reply from 192.168.2.101: bytes=32 time=325ms TTL=64 Reply from 192.168.2.101: bytes=32 time=825ms TTL=64 Reply from 192.168.2.101: bytes=32 time=4ms TTL=64 Reply from 192.168.2.101: bytes=32 time=3ms TTL=64 Reply from 192.168.2.101: bytes=32 time=9ms TTL=64 Reply from 192.168.2.101: bytes=32 time=5ms TTL=64 Request timed out. Reply from 192.168.2.101: bytes=32 time=4ms TTL=64 Request timed out. Request timed out. Reply from 192.168.2.101: bytes=32 time=1936ms TTL=64 Reply from 192.168.2.101: bytes=32 time=3ms TTL=64 Request timed out. Reply from 192.168.2.101: bytes=32 time=1509ms TTL=64 Reply from 192.168.2.101: bytes=32 time=3ms TTL=64 Reply from 192.168.2.101: bytes=32 time=1937ms TTL=64 Reply from 192.168.2.101: bytes=32 time=2ms TTL=64 Request timed out. Reply from 192.168.2.101: bytes=32 time=1514ms TTL=64 Reply from 192.168.2.101: bytes=32 time=3ms TTL=64 Reply from 192.168.2.101: bytes=32 time=1948ms TTL=64 Reply from 192.168.2.101: bytes=32 time=2ms TTL=64 Request timed out. Reply from 192.168.2.101: bytes=32 time=1517ms TTL=64 Reply from 192.168.2.101: bytes=32 time=7ms TTL=64 Reply from 192.168.2.101: bytes=32 time=1947ms TTL=64 Reply from 192.168.2.101: bytes=32 time=5ms TTL=64 Reply from 192.168.2.101: bytes=32 time=5ms TTL=64 Reply from 192.168.2.101: bytes=32 time=1047ms TTL=64 Reply from 192.168.2.101: bytes=32 time=3ms TTL=64 Request timed out. Reply from 192.168.2.101: bytes=32 time=982ms TTL=64 Reply from 192.168.2.101: bytes=32 time=3ms TTL=64 Request timed out. Reply from 192.168.2.101: bytes=32 time=1023ms TTL=64 Reply from 192.168.2.101: bytes=32 time=3ms TTL=64 Reply from 192.168.2.101: bytes=32 time=1954ms TTL=64 Reply from 192.168.2.101: bytes=32 time=3ms TTL=64 Request timed out. Reply from 192.168.2.101: bytes=32 time=1525ms TTL=64 Reply from 192.168.2.101: bytes=32 time=3ms TTL=64 Reply from 192.168.2.101: bytes=32 time=1966ms TTL=64 Reply from 192.168.2.101: bytes=32 time=5ms TTL=64 Reply from 192.168.2.101: bytes=32 time=5ms TTL=64 Reply from 192.168.2.101: bytes=32 time=1021ms TTL=64 Reply from 192.168.2.101: bytes=32 time=3ms TTL=64 Request timed out. |
| Santos Louderback 21.07.2011 | bump anyone??? |
<< Back to MIDIfighter Resources and DiscussionReply