-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multicast connected but .... nothing happen. #233
Comments
Yes, supposedly, all three should work in multicast; incl. VIMS messages up to VIMS ID 400 If it's broke, I'll fix it - Thanks a lot! |
Took up issue |
First case: Frame sender was not started |
Second case: It appears that VIMS messages are not handled when received via multicast |
First question, is there supposed to have three kind of multicast in veejay ?
updated systemd multicast setup (no sure of this also :-( ):
firewall accept all traffic (debian default) checked with
# iptables -L
# /sbin/ip link set lo multicast on
# /sbin/ip link set lo up
# /sbin/ip route add 224.0.0.0/4 dev lo
# echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts
# echo 1 > /proc/sys/net/ipv4/ip_forward
$ ping 224.0.0.1
---> OK$ export VEEJAY_MCAST_INTERFACE="lo"
In all terminals (vj1 / vj2 / sayVIMS)First Case
vj1 : veejay TreeStomper.avi -T 224.0.0.1 -p 5000 -v -a0
vj 2 : veejay -d -W 1024 -H 576 -v -a0
$ echo "246:5000 224.0.0.1;" |sayVIMS
+ [F2]but vj2 screen remain black (and did not respond to keyboard)
Second Case
vj1 : veejay -g video01.avi --multicast-vims 224.0.0.1 -v -a0
vj2 : veejay -g video02.avi --multicast-vims 224.0.0.1 -v -a0
sayVIMS -g 224.0.0.1 -m "600:;"
Nothing happen.
The text was updated successfully, but these errors were encountered: