Skip to content
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

Open
d-j-a-y opened this issue Jun 28, 2019 · 4 comments
Open

Multicast connected but .... nothing happen. #233

d-j-a-y opened this issue Jun 28, 2019 · 4 comments
Assignees

Comments

@d-j-a-y
Copy link
Collaborator

d-j-a-y commented Jun 28, 2019

First question, is there supposed to have three kind of multicast in veejay ?

  • frame sender
  • vims control
  • osc control

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

I: TCP/IP unicast VIMS control socket ready at port 5000 (R:2097152, S:2097152)
D: env VEEJAY_SERVER_RECEIVE_BUFFER_SIZE=[num bytes] not set
D: env VEEJAY_LOG_NET_IO=logfile not set
D: env VEEJAY_NET_TIMEOUT=seconds not set
D: Port: 5001 [ receive buffer is 2097152 bytes, send buffer is 2097152 bytes ]
I: TCP/IP unicast VIMS status socket ready at port 5001 (R:2097152, S:2097152)
D: env VEEJAY_SERVER_RECEIVE_BUFFER_SIZE=[num bytes] not set
D: env VEEJAY_LOG_NET_IO=logfile not set
D: env VEEJAY_NET_TIMEOUT=seconds not set
D: Port: 5005 [ receive buffer is 2097152 bytes, send buffer is 2097152 bytes ]
I: TCP/IP unicast VIMS control socket ready at port 5005 (R:2097152, S:2097152)
D: env VEEJAY_SERVER_RECEIVE_BUFFER_SIZE=[num bytes] not set
D: env VEEJAY_LOG_NET_IO=logfile not set
D: env VEEJAY_NET_TIMEOUT=seconds not set
I: UDP multicast frame sender ready at (group '224.0.0.1')
I: UDP unicast OSC channel ready at port 5006

vj 2 : veejay -d -W 1024 -H 576 -v -a0

$ echo "246:5000 224.0.0.1;" |sayVIMS + [F2]

I: New Input Stream 'Multicast' with ID 2 created
I: Created new input stream [2] (multicast) to veejay host 224.0.0.1 port 5000
I: Playing stream 2 (FX=0) (Ff=50)
I:  ... Waiting for network stream to become ready [224.0.0.1]
I: Connecton established with 224.0.0.1:5005

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.

@game-stop
Copy link
Owner

frame sender
vims control
osc control

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!

@game-stop
Copy link
Owner

Took up issue

@game-stop
Copy link
Owner

First case:

Frame sender was not started
Before opening stream on veejay 3490, send "022:;"| sayVIMS -p 5000
--> Will make change to automatically start frame sender on veejay 5000

@game-stop
Copy link
Owner

Second case:

It appears that VIMS messages are not handled when received via multicast

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants