@rodizio1 : I have just tested the awesome new RC5 and tried to port some of my changes to the latest Version.
However I noticed that invoking tx_rawsock and rx with something else than the Standard Port 0 will result in error messages:
tx_rawsock
tx_rawsock invoked with -p x (where x > 0):
root@wifibroadcast(rw):~/wifibroadcast# nice -n -9 gst-launch-1.0 videotestsrc ! video/x-raw,framerate=10/1 ! omxh264enc control-rate=1 target-bitrate=600000 ! h264parse config-interval=5 ! fdsink fd=1 | nice -n -9 /root/wifibroadcast/tx_rawsock -p 1 -b 8 -r 4 -f 1024 -t 1 -d 11 -y 0 24050faab379
tx_rawsock (c)2017 by Rodizio. Based on wifibroadcast tx by Befinitiv. GPL2 licensed.
using standard DATA frames
Could not open wifibroadcast tx status - retrying ...
Could not open wifibroadcast tx status - retrying ...
Could not open wifibroadcast tx status - retrying ...
Could not open wifibroadcast tx status - retrying ...
Could not open wifibroadcast tx status - retrying ...
Could not open wifibroadcast tx status - retrying ...
Could not open wifibroadcast tx status - retrying ...
Could not open wifibroadcast tx status - retrying ...
Could not open wifibroadcast tx status - retrying ...
Could not open wifibroadcast tx status - retrying ...
Could not open wifibroadcast tx status - retrying ...
root@wifibroadcast(rw):~/wifibroadcast#
tx_rawsock invoked with -p 0 (everthing works fine)
root@wifibroadcast(rw):/wifibroadcast# nice -n -9 gst-launch-1.0 videotestsrc ! video/x-raw,framerate=10/1 ! omxh264enc control-rate=1 target-bitrate=600000 ! h264parse config-interval=5 ! fdsink fd=1 | nice -n -9 /root/wifibroadcast/tx_rawsock -p 0 -b 8 -r 4 -f 1024 -t 1 -d 11 -y 0 24050faab379
tx_rawsock (c)2017 by Rodizio. Based on wifibroadcast tx by Befinitiv. GPL2 licensed.
using standard DATA frames
50 blocks sent, injection time per block 1200us, 0 fecs skipped, 0 packet injections failed.
rx
rx invoked with -p x (where x > 0 )
shm_open: No such file or Directory
shm_open: No such file or Directory
shm_open: No such file or Directory
Can you confirm this is a bug? Is there any way to bypass/solve this problem?
Best regards! Keep up the excellent work!
Thomas
P.S: I copied tx_rawsock and rx from RC3 over to RC5 (renaming them tx_rawsock_rc3 and rx_rc3) and changed the according lines in .profile - now it is working again. However I think this is not a permanent solution ;-)
@rodizio1 : I have just tested the awesome new RC5 and tried to port some of my changes to the latest Version.
However I noticed that invoking tx_rawsock and rx with something else than the Standard Port 0 will result in error messages:
tx_rawsock
tx_rawsock invoked with -p x (where x > 0):
tx_rawsock invoked with -p 0 (everthing works fine)
rx
rx invoked with -p x (where x > 0 )
Can you confirm this is a bug? Is there any way to bypass/solve this problem? Best regards! Keep up the excellent work!
Thomas
P.S: I copied tx_rawsock and rx from RC3 over to RC5 (renaming them tx_rawsock_rc3 and rx_rc3) and changed the according lines in .profile - now it is working again. However I think this is not a permanent solution ;-)