To find out .net version, follow the following article:

http://support.microsoft.com/kb/318785

vMix needs at least ".net 3.5", while vMixControler needs at least ".net 4.0". Maybe that's the culprit. The only difference between v0.3.0.0 and v0.3.0.1 is one additional dependency, that's a system library called "System.Web.dll" which should be part of your .net installation (usually found here: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.Web.dll".

Normally an installer would check all dependencies and fix them if some are missing, but i've been to lazy to create an installer package for the alpha releases, so you'll have to check the dependencies yourself... sorry.

The programs are compiled for 32 bit, but i've tested them on win7 64 bit, so this shouldn't make any difference. Still: what windows are you running on?

Ok, that might explain the problems. vMixScheduler needs .net 4.0, even if it starts on .net 3.5 there will be some functions that don't work, or not the way you'd expect. I hope updating to .net 4.0 will solve the problems!

Glad to hear at least some of the issues are resolved.

Now can you please explain those other problems a little further? What do i have to do to reproduce the situation? What happens, and what do you expect that should happen?

@ Damn2Good4U:
See posts 41 & 42 above, you likely have to update to Framework .net 4.0 (worked for me after that)

@ macjaeger:
Issue 1 - Scheduled events are input OK (as per settings 5 sec. default) but are only loaded into preview window just milliseconds before scheduled time (flash and straight to Program) This is not a functional problem as everything plays on time, just different from the behavior demonstrated in your video.
Issue 2 - Any schedules that have either an "Operator" or "Blackness" event somewhere in the list, once loaded into the controller will immediately close out the frontmost input (input 1) of a vMix set-up.
Issue 3 - "Blackness" event inputs do not close out after expired time but rather close out the frontmost input (input 1) of a vMix set-up.
In other words, if I had a vMix preset set-up with 3 Camera inputs and loaded a schedule that had several videoclip events separated by 2 "Blackness" events and ending with an "Operator" event so that I could go straight to a live camera at desired time, I would be SOL. All three camera inputs would have closed out, camera 1 upon loading the schedule to the controller, camera 2 after the first "Blackness" event, and camera 3 after the second "Blackness" event. (Obviously, inputs can be re-added, so it's not the end of the world but a more complex profile preset could be severely compromised after a lengthy schedule with multiple "Blackness" events)
I hope this better explains the behavior I am seeing, I'm not sure if it can be reproduced on another system as it may be something on my end that causes this behavior... but what?

Maybe that's a vMix setting - i'm at work and can't check right now, but maybe you can change that behavior somewhere... vMixControler doesn't actively load the settings to preview, so it's vMix' own doing.


Thank you for your thourough (misspelled, i'm sure...) explanation, now i can go hunting for the bugs! Of course "operator mode" shouldn't close any inputs, and blackness only closes "blackness.jpg" (workaround until v10, then we'll have a new api-function to add solid colors). I'll try to reproduce and trace the problem! A camera (or other user-defined input) should never be closed by vMixControl!

For the record: which version of vMix are you running?

Running latest version of vMix 9.1.0.31
Also my update to .net 4.0 seems to have cured the disruption of program out when adding or removing events to the up-coming schedule and reloading (major bonus in my eyes, as theoretically you could now edit the playlist while running the scheduler perpetually uninterrupted).

Ice

So it seems that client profile isn't enough, maybe because the "UrlEncode"-Function is only available in full profile... if it's the same to you, could you please update to full profile and try if that removes the problem?


I'm curious what you might come up with!

@Mac

How r u? Hope u r doing well, quite a long time.

I am having issues at the moment trying to schedule 2days at a time talk less of a whole week, adding one day is no problem, it works like charm, but the moment u add another day, it stops working. I do understand we r still in alpha version. I am only updating you on the current situation.

Regards,
Rottimmy

I wish you all the best in your exams...

Lets talk then from next week

Regards,
Rottimmy

I won't merge the two applications, there's a reason why they were separated. I created vMix Controller to be run on the same machine as vMix itself, while a manager could run on any machine (not my manager, as it relies on absolut paths). I will enhance the applications in a way so that someone else could build a much more comfortable manager application, e.g. add a NLE-like timeline, or a drag'n'drop slot system. To achieve that goal, i must seperate the functionality and define a clean interface - at the moment the interface is the xml-file, but i might rework that part now.

Anyway: i'm going to test vMix 10 next weekend, and will adapt controller & manager to the new possibilities then. I hope i can get a good way ahead before summer holidays.