Hello
I have a fully patched Windows 2003 R2 server in an Active Directory environment that is hosting two live, 24X7, flash streams using Adobe Flash Media Live Encoder 3.0.0.4743. The single capture card is an Osprey 700 HD with the latest drivers. A second Osprey 700 HD card will be added to the machine in the near future. The FMLE is configured precisely according to the Automating Startup Tasks section of the help PDF. The entire configuration works perfectly except for one small problem - the second encoding session does not start.
Since there are two live streams I registered the two encoding sessions using the /r option exactly as outlined in the help file. From an administrative command line the two commands I issued are:
fmlecmd.exe /p "C:\Program Files\Adobe\Flash Media Live Encoder 3\profiles\config1.xml" /ap username:password /r
fmlecmd.exe /p "C:\Program Files\Adobe\Flash Media Live Encoder 3\profiles\config2.xml" /ap username:password /r
Both commands reported they were successful. To verify I inspected the OsLaunch.dat file which properly showed the registration entries. Those entries are: (scrubbed for the public)
rtmp://url.1.of.destination.com/entrypoint+streaminformation1"C:\Program Files\Adobe\Flash Media Live Encoder 3\fmlecmd.exe" /p "C:\Program Files\Adobe\Flash Media Live Encoder 3\profiles\config1.xml" /ap username:password
rtmp://url.2.of.destination.com/entrypoint+streaminformation2"C:\Program Files\Adobe\Flash Media Live Encoder 3\fmlecmd.exe" /p "C:\Program Files\Adobe\Flash Media Live Encoder 3\profiles\config2.xml" /ap username:password
When the server boots the FMLELauncher.exe application starts properly. The issue is that only the first encoder session starts, not the second. The result is consistently reproducible with each system restart.
Once the system is started, a check of the task manager reveals that only one instance of FMLECmd.exe is running. I can also verify the first stream is working correctly by viewing the stream from the source. A check of the log files reveals that the second instance was not even attempted, or put another way, there is no log file created for the second instance.
If I manually run the FMLELauncher.exe task, it tries to start each encoder session properly. When it discovers that the first one is already running it simply errors out on that attempt but successfully starts the second stream. Also if, after a restart, I manually kill the single running FMLECmd.exe application, then manually run the FMLELauncher.exe task, both encoders start as expected and remain running until the next system restart.
The goal is to have both encoding sessions start when the system starts without user intervention, not just the first one.
I greatly appreciate any and all help regarding this issue.