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

sayVIMS : something broken ? #57

Closed
d-j-a-y opened this issue Nov 16, 2015 · 9 comments
Closed

sayVIMS : something broken ? #57

d-j-a-y opened this issue Nov 16, 2015 · 9 comments

Comments

@d-j-a-y
Copy link
Collaborator

d-j-a-y commented Nov 16, 2015

i try the first example of the man page

$ sayVIMS -h localhost -p 3490 255:;
I: Link: 0 connected with 127.0.0.1 on port 57735
I: Link: 0 connected with 127.0.0.1 on port 43232

 ^E: Invalid VIMS instruction 'V001D '

got that.... something broken doctor ?

@game-stop
Copy link
Owner

not reproducable, did you do a clean build before you encountered this issue? status mechanism changed one or two days ago which could explain this issue if you did not recompile sayVIMS

D: VIMS (v) Message too small
D: Message content
D: msg [V000D255:;] (4 bytes) at position 0
 ^D: VIMS (v) - dropped message
E: Invalid VIMS instruction 'V000D255:;'

And no such VIMS event:

I: VIMS selector 251    'Request shared resource from another veejay'
I:      FORMAT: '%d', where:
I:              Argument 0 is Port number
I: VIMS selector 254    'Suspend Veejay (caution!)'
I: VIMS selector 300    'Set audio volume'
I:      FORMAT: '%d', where:
I:              Argument 0 is Volume 0-100
I: VIMS selector 301    'Enable / Disable Fullscreen video output'

@d-j-a-y
Copy link
Collaborator Author

d-j-a-y commented Nov 20, 2015

still the same problem even for 017 event ...
$ sayVIMS -h localhost -p 3490 017:;
i may do something wrong.

@game-stop
Copy link
Owner

the ';' might get interpreted by bash, and sayVIMS like that would start it in interactive mode (reading from stdin), try:

sayVIMS -h localhost -p3490 -m "017:;"

@d-j-a-y
Copy link
Collaborator Author

d-j-a-y commented Nov 21, 2015

yep ! that's working now. Have done that mistake copy/pasting from manpage sayVIMS manpage ....
I will do some change there because in bold, double quote " character is not displayed (and need to be escaped ??? \*(lq )

So : Is it normal that take so much time ~1700 ms ?

#!/bin/bash

START_TIME=`echo $(($(date +%s%N)/1000000))`

sayVIMS -h localhost -p3490 -m "017:;"

END_TIME=`echo $(($(date +%s%N)/1000000))`
ELAPSED_TIME=$(($END_TIME - $START_TIME))

echo $ELAPSED_TIME

@d-j-a-y
Copy link
Collaborator Author

d-j-a-y commented Nov 21, 2015

So : Is it normal that take so much time ~1700 ms ?

because of connect and disconnect time i guess ?
for reactivity... interactive mode !

@d-j-a-y d-j-a-y closed this as completed Nov 21, 2015
@game-stop
Copy link
Owner

1700 ms is too long, sayVIMS should depend on veejay's frame period (so if rendering takes 2 seconds, sayVIMS will take 2 seconds as well)

This is with veejay -d and no FX ?

Also, for timing just issue 'wall' in front of sayVIMS for accurate measurement

@d-j-a-y
Copy link
Collaborator Author

d-j-a-y commented Nov 22, 2015

This is with veejay -d and no FX ?

i have redone the test with -d and it's quite the same result.

@game-stop
Copy link
Owner

what is the output from wall sayVIMS -h localhost -p3490 -m "017:;" ?

i'll look at this tomorrow

@d-j-a-y
Copy link
Collaborator Author

d-j-a-y commented Nov 25, 2015

$man wall

wall - write a message to all users

wall ???

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