Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Auto Start Encoding With Windows startup!?

195 views
Skip to first unread message

David Rad

unread,
Jul 21, 2003, 7:21:25 AM7/21/03
to
Hi Guys :
is that possible to start encoding with windows media encoder when server
start ....?
i save my configeration to a file ( *.WME ) so i put the file in startup
and the encoder starts fine , how can i auto START ENCODING... ?

maybe i should Develop something with SDK .


Shrivel

unread,
Jul 23, 2003, 2:00:53 PM7/23/03
to
create a .bat file that starts the command-line encoder that references your
.WME file.

put that .bat file into your startup group

"David Rad" <Da...@skynet.co.il> wrote in message
news:eoma8o3T...@tk2msftngp13.phx.gbl...

Rolf Andersen

unread,
Jul 29, 2003, 11:59:39 AM7/29/03
to
This is exactly the problem I am faced with. The WME9
interface does not support "auto start". This would be a
great check box when creating unique wme files. Currently
I can only insert the wme files in the "start up" folder
which goes so far as loading each encode session.
However, you need to click the "start encode" button for
each broadcast, which is what I am doing. I ran across
several referneces to creating an auto start file using
the the command line sdk. Command line control is
probably more suited to my application as I want as little
overhead as possible as I'm running 8 separate WMV streams
from one box. I am wading through the documentation, but
hoped someone had already written something. An auto start
check box added to the media encoder would be a nice
feature.

>.
>

Jeff Woiton

unread,
Jul 29, 2003, 3:55:10 PM7/29/03
to
That's a good suggestion, Rolf. I'm not one of toe product's designers, but I think a problem they're up against is that
when WME is set to autostart, how does it know which settings to load? You can easily pass that information to WME
through a configuration file, which is associated with WME and will auto launch WME with those settings in place, so I
think that either using the Startup group or Task Scheduler seem reasonable to me.

--------------------
From: "Rolf Andersen" <sup...@gordoncross.com>
Subject: Auto Start Encoding With Windows startup!?
Date: Tue, 29 Jul 2003 08:59:39 -0700


This posting is provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use. © 2003
Microsoft Corporation. All rights reserved. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
~~~~~~~~~~~~~~~~~~~
I regret that I cannot reply to you if you email me directly. It is better that you post your question back to the newsgroup
- more people will see your question and be able to offer help, and to learn from it as well.
~~~~~~~~~~~~~~~~~~~
Also, if your issue is too complex to resolve easily in a newsgroup, it might be time to open a support incident and get
live phone support from Microsoft. See http://microsoft.com/windows/windowsmedia/support.asp for other support
options.

Mark J

unread,
Aug 5, 2003, 8:14:17 AM8/5/03
to
You can use scheduled tasks to start mutiple encoders at
log on. The line you need is somthing like:

C:\PROGRA~1\WINDOW~4\Encoder\wmenc.exe
C:\profiledir\profilename.wme /start

Mid

unread,
Aug 28, 2003, 10:02:23 AM8/28/03
to
I agree with Rolf. an auto start check box would be nice.
Even better yet, how about a built in scheduler to start
and stop that becomes a part of the wme config. This
would allow for bandwidth conservation in an unsupervised
environment. For those of us with reoccuring streaming
schedules this would be great. I'm not a developer but
I'm curious to know if this is something that can be done
with the SDK?
0 new messages