PDA

View Full Version : Problem with mov123 on Win2K Server



Phil Fernandez
2004-09-11, 11:35
On Win2KServer, with mov123.exe from 5.2.x, I get "Failed at line: 316;
Conversion failed with error: -3000" when testing with .wav, .aiff,
..m4a, or .mp3.

With mov123.exe from 5.1.x, it works clean with .wav, .m4a, and .mp3,
and for .aiff gets "Failed at line: 221; Failed at line: 339; Conversion
failed with error -50".

I'm happy to dig into the code and try to figure out what changed
between 5.1 and 5.2 if someone that knows mov123 wanted to give me a
nudge in the right direction.

pmf

-----Original Message-----
From: discuss-bounces (AT) lists (DOT) slimdevices.com
[mailto:discuss-bounces (AT) lists (DOT) slimdevices.com] On Behalf Of dean
blackketter
Sent: Wednesday, September 08, 2004 10:36 PM
To: Slim Devices Discussion
Subject: [slim] Problem with mov123 on Win2K Server


Sorry for being vague. Try running mov123.exe standalone again, but
instead of one of the m4a files, use another file type like mp3 or
AIFF.

-dean

On Sep 8, 2004, at 12:01 AM, Phil Fernandez wrote:

> Dean -- Sorry if I'm being dense, but I'm not sure exactly which other

> file types you mean. I'm glad to test out and report anything that is

> helpful...what types should I test?
>
> pmf
>
> -----Original Message-----
> From: discuss-bounces (AT) lists (DOT) slimdevices.com
> [mailto:discuss-bounces (AT) lists (DOT) slimdevices.com] On Behalf Of dean
> blackketter
> Sent: Tuesday, September 07, 2004 7:39 AM
> To: Slim Devices Discussion
> Subject: [slim] Problem with mov123 on Win2K Server
>
>
> Phil,
>
> Will other file types open with that version of mov123.exe on that
> machine? That error indicates that specific QuickTime component
> failed to open.
>
> -dean
>
> On Sep 6, 2004, at 3:52 PM, Phil Fernandez wrote:
>
>> I'm running Server 5.2.1 on Windows 2000 Server, with Quicktime 6.5.1

>> and a current LAME. Trying to play UNprotectected .m4a files.
>> Having
>
>> a problem with conversion failure. If I run mov123 standalone, I get

>> an error saying conversion failed with error -3000.
>>
>> A while back, June I think, there was a discussion about this same
>> problem, but the conversation died when the original poster mentioned

>> that he got things working by using the mov123.exe from 5.1.
>>
>> This is the same situaiton for me...if I replace the mov123.exe from
>> 5.2.1 with the old mov123.exe from 5.1, all works fine. I also tried

>> the mov123.exe from the 9/6/04 nightly, and have the same problem
>> with
>
>> the -3000 error.
>>
>> At some level, I have everything working fine by using the old
>> binary, but it would be really nice if this worked correctly under
>> current distributions of the server. Does anyone have any idea
>> what's going on? Why this broke between 5.1 and 5.2?
>>
>> (Note that the mov123 from 5.2 *does* work correctly for me under
>> WinXP and QT6.5.1, so this appears to be somehow related to Win 2000
>> (server)).
>>
>> pmf
>>

dean
2004-09-14, 11:53
Phil,

Check out the evolution of this code in the CVS repository:

<http://cvs.slimdevices.com/~cvs/viewcvs_0.9.2/cgi/viewcvs.cgi/slim/
tools/mov123/mov123.cpp>

There was a major rewrite between those two versions.

Let's move the rest of this discussion to the developer list...

-dean

On Sep 11, 2004, at 11:35 AM, Phil Fernandez wrote:

> On Win2KServer, with mov123.exe from 5.2.x, I get "Failed at line: 316;
> Conversion failed with error: -3000" when testing with .wav, .aiff,
> .m4a, or .mp3.
>
> With mov123.exe from 5.1.x, it works clean with .wav, .m4a, and .mp3,
> and for .aiff gets "Failed at line: 221; Failed at line: 339;
> Conversion
> failed with error -50".
>
> I'm happy to dig into the code and try to figure out what changed
> between 5.1 and 5.2 if someone that knows mov123 wanted to give me a
> nudge in the right direction.
>
> pmf
>
> -----Original Message-----
> From: discuss-bounces (AT) lists (DOT) slimdevices.com
> [mailto:discuss-bounces (AT) lists (DOT) slimdevices.com] On Behalf Of dean
> blackketter
> Sent: Wednesday, September 08, 2004 10:36 PM
> To: Slim Devices Discussion
> Subject: [slim] Problem with mov123 on Win2K Server
>
>
> Sorry for being vague. Try running mov123.exe standalone again, but
> instead of one of the m4a files, use another file type like mp3 or
> AIFF.
>
> -dean
>
> On Sep 8, 2004, at 12:01 AM, Phil Fernandez wrote:
>
>> Dean -- Sorry if I'm being dense, but I'm not sure exactly which other
>
>> file types you mean. I'm glad to test out and report anything that is
>
>> helpful...what types should I test?
>>
>> pmf
>>
>> -----Original Message-----
>> From: discuss-bounces (AT) lists (DOT) slimdevices.com
>> [mailto:discuss-bounces (AT) lists (DOT) slimdevices.com] On Behalf Of dean
>> blackketter
>> Sent: Tuesday, September 07, 2004 7:39 AM
>> To: Slim Devices Discussion
>> Subject: [slim] Problem with mov123 on Win2K Server
>>
>>
>> Phil,
>>
>> Will other file types open with that version of mov123.exe on that
>> machine? That error indicates that specific QuickTime component
>> failed to open.
>>
>> -dean
>>
>> On Sep 6, 2004, at 3:52 PM, Phil Fernandez wrote:
>>
>>> I'm running Server 5.2.1 on Windows 2000 Server, with Quicktime 6.5.1
>
>>> and a current LAME. Trying to play UNprotectected .m4a files.
>>> Having
>>
>>> a problem with conversion failure. If I run mov123 standalone, I get
>
>>> an error saying conversion failed with error -3000.
>>>
>>> A while back, June I think, there was a discussion about this same
>>> problem, but the conversation died when the original poster mentioned
>
>>> that he got things working by using the mov123.exe from 5.1.
>>>
>>> This is the same situaiton for me...if I replace the mov123.exe from
>>> 5.2.1 with the old mov123.exe from 5.1, all works fine. I also tried
>
>>> the mov123.exe from the 9/6/04 nightly, and have the same problem
>>> with
>>
>>> the -3000 error.
>>>
>>> At some level, I have everything working fine by using the old
>>> binary, but it would be really nice if this worked correctly under
>>> current distributions of the server. Does anyone have any idea
>>> what's going on? Why this broke between 5.1 and 5.2?
>>>
>>> (Note that the mov123 from 5.2 *does* work correctly for me under
>>> WinXP and QT6.5.1, so this appears to be somehow related to Win 2000
>>> (server)).
>>>
>>> pmf
>>>