Forum Replies Created

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
  • in reply to: The Future of V-Control #13080

    I hope it at least stay functional. Either in a distribution or that it is updated enough it will build from up-to-date libraries etc. I don’t use it daily, but rather depend on V-Control when I do a theater show. There haven’t been many of those for a couple years…

    in reply to: [Solved] Stop all #677

    Quote from: Dierk
    Quote from: fmiser
    Have I missed a feature that will do this sort of thing? Or is it not there?

    Unfortunately not. But I can offer two workarounds.

    1. In the V-Control main window you select the task that stops your audio file. Now go back to playlist and operate your show. If you want to stop the audio click on the “Run” button in the V-Control window.
    That will work – until I start editing the show. I mostly expect to use the “halt” task during rehearsals – which is also when I expect I’ll be doing editing while also running the show. But I’ll try it. So far I’m still just building and playing – no real show yet.

    2. You can attach physical push buttons to V-Control. You can do that with any micro-controller. We have examples for Arduino on the V-Control homepage

    In my opinion this is the most convenient way to solve your problem.
    Hmm. I do like that. I’ll look into that more – but maybe I should wait until I have actually used suggestion #1. Thanks for the suggestions!

    • This reply was modified 7 years, 3 months ago by Dierk.
    • This reply was modified 7 years, 3 months ago by Dierk Walter.
    in reply to: Script syntax and a subroutine #674

    Quote from: Dierk on December 30, 2014, 01:39:32 PM
    If I understand you right then you want to send two command strings within one command, is that right?

    Well, sort of. That isn’t the real issue. What I was really asking about is the ability to use a subroutine. Is it possible or not?

    Related, is there a language reference covering syntax, etc for REALBasic or Xojo as it is available in a command script?

    In the device editor you find a drop down box labeled “Next Command”. Here you can define the command that has to execute after the first command.

    I saw that, but didn’t really want to use it because the user has to know which commands are not “available” because they are just links in the chain. But as I look closer, I see that I can choose a “Tab” for the commands – and if it’s set to null, the command is invisible to normal use.

    That sure could work for the twin command part.

    in reply to: Device number #669

    Quote from: Dierk on December 30, 2014, 11:29:28 AM
    There are two ways to open the Device Editor.

    1. Configure -> Edit Device…
    This let you edit / change the devices in your current project

    Ah! Got it. That was easy. 🙂


    in reply to: User Interface colors #666

    Okay. Just being able to change colours would be nice. It would be very nice if I could set up themes or profiles with a set of colors.

    For now, I’ll just put a gel over the screen to make it darker. 🙂

    in reply to: Very nice! Thank you #661

    Quote from: Dierk on December 15, 2014, 10:08:48 PM
    OK, here is the VLC Linux driver. Btw, the old one is broken for windows as well.

    It works for localhost on my Debian system. It didn’t work with VLC on another host – but neither did telnet. I’m convinced it’s a general network/telnet problem and not the fault of V-Control or VLC.

    Thanks for the new driver!

    in reply to: Very nice! Thank you #658

    Quote from: Dierk on December 12, 2014, 09:42:26 AM
    I would like to figure out why the VLC driver did not work for you. Did you use VLC on the same computer that is running V-Control (Debian machine in this case) ?

    On the same machine, I tried “localhost”, and No error reported in V-Control. At a shell prompt from the same user running V-Control, I launched a telnet session and successfully controlled VLC. After exiting telnet, I tried piping a command to telnet, and that worked (echo “play” | telnet 10101). Finally, I setup wireshark to monitor and used that IP and compared V-Control to the piped telnet command. The piped command had a few reply packet from VLC that V-Control did NOT.

    I can do more troubleshooting for you, but for my needs, the shell command looks like it will work better than VLC because it will stop itself at the end of the file and the filename is visible in the list.

    Or was it running on a different PC with maybe a different operating system? None of these scenarios should be a problem, I’m asking just to know your environment.

    I did try running VLC on another Debian machine. Same result. I didn’t do any testing further than just trying it once. *smiles*

    May I ask you to share your Roland M-200i driver int the V-Control Show Case section?

    Absolutely! It is the plan. I’m not a real programmer, so I have to be a bit more creative to be able to contribute to open source software. When I get a few more of the commands programmed I’ll send it to you. Should I attach it to a forum post? Or email it to you? Or something else?

    In the drivers help text you can write something about you as co


    Ah! Okay. I’ll do that.

Viewing 7 posts - 1 through 7 (of 7 total)