-
Notifications
You must be signed in to change notification settings - Fork 11
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
Comments
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' |
still the same problem even for 017 event ... |
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:;" |
yep ! that's working now. Have done that mistake copy/pasting from manpage sayVIMS manpage .... So : Is it normal that take so much time ~1700 ms ?
|
because of connect and disconnect time i guess ? |
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 |
i have redone the test with -d and it's quite the same result. |
what is the output from i'll look at this tomorrow |
wall ??? |
i try the first example of the man page
got that.... something broken doctor ?
The text was updated successfully, but these errors were encountered: