| Author |
Message |
Ave Wrigley
Guest
|
Posted:
Tue Oct 19, 2004 2:49 pm Post subject:
.prx profiles and wmcmd.vbs |
|
|
I am trying to set up a batch process to encode video using WME. The
profile I want to use is not represented in the standard WME list, so
I created my own using the handy "Windows Media Profile Editor" and
saved it as a .prx. So ... the next step was - how do I load this
profile to do an encoding? I thought the easiest way was to use the
VBScript command line tool, so I tried:
C:\Program Files\Windows Media Components\Encoder>cscript.exe
WMCmd.vbs -loadprofile test.prx
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Invalid profile: 0x80004005
So maybe there is something wrong with my profile, so I thought I
would try one of the standard ones:
C:\Program Files\Windows Media Components\Encoder>cscript.exe
WMCmd.vbs -loadprofile Settings\d0_cbr_audio_cd.prx
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Invalid profile: 0x80004005
Hmmm (useful error message, though!). Finally, I though, heck, why not
just use the GUI - at least I can do a sample encoding, and work out
how to do the command line version later, but I couldn't see any
obvious way to load a .prx profile from the GUI. Finally, since the
profiles are all nice XML files, I thought maybe I can install my
profile with the default ones. The default ones appear to be in a
"Settings" folder, and have a SettingsMap.xml file which appears to
define the GUI options in terms of .prx files in that folder. However,
the settings map file, although fairly straightforward, contains
scarey looking stuff such as:
<WMENCAUDIO_CONFIG id="GUID {7BCE4D7E-E1E9-4254-AC4D-488323F48E31}"
File="d0_vbr_audio_hdcd.prx" Destination="0"/>
and I though I was getting a bit out of my depth with these GUIDs.
Anyone have any experience with loading profiles from the CLI?
Ave.
|
|
| Back to top |
|
 |
Neil Smith [MVP Digital M
Guest
|
Posted:
Tue Oct 19, 2004 3:57 pm Post subject:
Re: .prx profiles and wmcmd.vbs |
|
|
Err, what happens when you provide WMCmd.vbs with the full path to the
profile rather than a relative path (relative to what ?!)
Cheers - Neil
On 19 Oct 2004 03:49:55 -0700, ave.wrigley@itn.co.uk (Ave Wrigley)
wrote:
| Quote: | I am trying to set up a batch process to encode video using WME. The
profile I want to use is not represented in the standard WME list, so
I created my own using the handy "Windows Media Profile Editor" and
saved it as a .prx. So ... the next step was - how do I load this
profile to do an encoding? I thought the easiest way was to use the
VBScript command line tool, so I tried:
C:\Program Files\Windows Media Components\Encoder>cscript.exe
WMCmd.vbs -loadprofile test.prx
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Invalid profile: 0x80004005
So maybe there is something wrong with my profile, so I thought I
would try one of the standard ones:
C:\Program Files\Windows Media Components\Encoder>cscript.exe
WMCmd.vbs -loadprofile Settings\d0_cbr_audio_cd.prx
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Invalid profile: 0x80004005
Hmmm (useful error message, though!). Finally, I though, heck, why not
just use the GUI - at least I can do a sample encoding, and work out
how to do the command line version later, but I couldn't see any
obvious way to load a .prx profile from the GUI. Finally, since the
profiles are all nice XML files, I thought maybe I can install my
profile with the default ones. The default ones appear to be in a
"Settings" folder, and have a SettingsMap.xml file which appears to
define the GUI options in terms of .prx files in that folder. However,
the settings map file, although fairly straightforward, contains
scarey looking stuff such as:
WMENCAUDIO_CONFIG id="GUID {7BCE4D7E-E1E9-4254-AC4D-488323F48E31}"
File="d0_vbr_audio_hdcd.prx" Destination="0"/
and I though I was getting a bit out of my depth with these GUIDs.
Anyone have any experience with loading profiles from the CLI?
Ave. |
|
|
| Back to top |
|
 |
Ave Wrigley
Guest
|
Posted:
Tue Oct 19, 2004 8:37 pm Post subject:
Re: .prx profiles and wmcmd.vbs |
|
|
You mean like this?
C:\Program Files\Windows Media Components\Encoder>cscript.exe wmcmd.vbs
-loadprofile "C:\Program Files\Windows Media Components\Encoder\test.prx"
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Invalid profile: 0x80004005
"Neil Smith [MVP Digital Media]" wrote:
| Quote: | Err, what happens when you provide WMCmd.vbs with the full path to the
profile rather than a relative path (relative to what ?!)
Cheers - Neil
On 19 Oct 2004 03:49:55 -0700, ave.wrigley@itn.co.uk (Ave Wrigley)
wrote:
I am trying to set up a batch process to encode video using WME. The
profile I want to use is not represented in the standard WME list, so
I created my own using the handy "Windows Media Profile Editor" and
saved it as a .prx. So ... the next step was - how do I load this
profile to do an encoding? I thought the easiest way was to use the
VBScript command line tool, so I tried:
C:\Program Files\Windows Media Components\Encoder>cscript.exe
WMCmd.vbs -loadprofile test.prx
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Invalid profile: 0x80004005
So maybe there is something wrong with my profile, so I thought I
would try one of the standard ones:
C:\Program Files\Windows Media Components\Encoder>cscript.exe
WMCmd.vbs -loadprofile Settings\d0_cbr_audio_cd.prx
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Invalid profile: 0x80004005
Hmmm (useful error message, though!). Finally, I though, heck, why not
just use the GUI - at least I can do a sample encoding, and work out
how to do the command line version later, but I couldn't see any
obvious way to load a .prx profile from the GUI. Finally, since the
profiles are all nice XML files, I thought maybe I can install my
profile with the default ones. The default ones appear to be in a
"Settings" folder, and have a SettingsMap.xml file which appears to
define the GUI options in terms of .prx files in that folder. However,
the settings map file, although fairly straightforward, contains
scarey looking stuff such as:
WMENCAUDIO_CONFIG id="GUID {7BCE4D7E-E1E9-4254-AC4D-488323F48E31}"
File="d0_vbr_audio_hdcd.prx" Destination="0"/
and I though I was getting a bit out of my depth with these GUIDs.
Anyone have any experience with loading profiles from the CLI?
Ave.
|
|
|
| Back to top |
|
 |
Neil Smith [MVP Digital M
Guest
|
Posted:
Tue Oct 19, 2004 9:57 pm Post subject:
Re: .prx profiles and wmcmd.vbs |
|
|
Bummer !
On Tue, 19 Oct 2004 09:37:03 -0700, "Ave Wrigley"
<AveWrigley@discussions.microsoft.com> wrote:
| Quote: | You mean like this?
C:\Program Files\Windows Media Components\Encoder>cscript.exe wmcmd.vbs
-loadprofile "C:\Program Files\Windows Media Components\Encoder\test.prx"
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Invalid profile: 0x80004005
"Neil Smith [MVP Digital Media]" wrote:
Err, what happens when you provide WMCmd.vbs with the full path to the
profile rather than a relative path (relative to what ?!)
Cheers - Neil
On 19 Oct 2004 03:49:55 -0700, ave.wrigley@itn.co.uk (Ave Wrigley)
wrote:
I am trying to set up a batch process to encode video using WME. The
profile I want to use is not represented in the standard WME list, so
I created my own using the handy "Windows Media Profile Editor" and
saved it as a .prx. So ... the next step was - how do I load this
profile to do an encoding? I thought the easiest way was to use the
VBScript command line tool, so I tried:
C:\Program Files\Windows Media Components\Encoder>cscript.exe
WMCmd.vbs -loadprofile test.prx
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Invalid profile: 0x80004005
So maybe there is something wrong with my profile, so I thought I
would try one of the standard ones:
C:\Program Files\Windows Media Components\Encoder>cscript.exe
WMCmd.vbs -loadprofile Settings\d0_cbr_audio_cd.prx
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Invalid profile: 0x80004005
Hmmm (useful error message, though!). Finally, I though, heck, why not
just use the GUI - at least I can do a sample encoding, and work out
how to do the command line version later, but I couldn't see any
obvious way to load a .prx profile from the GUI. Finally, since the
profiles are all nice XML files, I thought maybe I can install my
profile with the default ones. The default ones appear to be in a
"Settings" folder, and have a SettingsMap.xml file which appears to
define the GUI options in terms of .prx files in that folder. However,
the settings map file, although fairly straightforward, contains
scarey looking stuff such as:
WMENCAUDIO_CONFIG id="GUID {7BCE4D7E-E1E9-4254-AC4D-488323F48E31}"
File="d0_vbr_audio_hdcd.prx" Destination="0"/
and I though I was getting a bit out of my depth with these GUIDs.
Anyone have any experience with loading profiles from the CLI?
Ave.
|
|
|
| Back to top |
|
 |
|
|
|
|