onMetaData got 64 args instead of one

Forum|Forum|18 years ago
February 1, 2008
4 replies
405 views

Hi,

I tried this morning the new release of fms, fms3, but encounter an issue on the metadata.

I tried this :

dummy=new Object();
stream.client=dummy;
dummy.onMetaData=getMeta;

private function getMeta (mdata:Object):void
{
trace (mdata.duration);
}

Burt I got an error : ArgumentError: Error #1063: Non-correspondance du nombre d'arguments sur tt/getMeta(). 1 prévu(s), 63 détecté(s).

As you see, I got 63 args instead of 1.

Can you help me ?

Regards

This topic is closed to new replies. Start a new post to keep the conversation going.

N

namitagrawal

Inspiring

Can you please provide the log of Flash Media Encoder?

A

Anonymous

I dunno, it sure seems like a bug. I can't think of any other reason an internal method would give itself the wrong number of arguments.

I would try contacting support about this issue.

A

Anonymous

Good heavens!

The first thing I'd do is see what those args are:

private function getMeta (...args):void{
for(var a in args)
trace(a+': '+args)
}

P

PhiphouAuthor

Participating Frequently

Oups ! It's an idea ! I didn't know this "...args" syntax (the 3 dots).

But it doesn't solve the problem. I mean, now, I can see the 63 args are all numbers, all zeros.

If I try to play any flv encoded by flvencoder, everything is ok, I receive a MetaDataObject, and can access its info property. The same with a live recorded stream using Flash Media Encoder 2 and streaming it directly into FMS3.

But if I use Flash Media Encoder 2 to record an flv on the disk and then try to play it within FMS3, I receive these weird 63 args. I think (not yet tried) that recording the video directly with FMS using stream.publish would not cause this issue, but does it mean that I have to forget the idea of using Flash Media Encoder 2 to record ? And what do these 63 args are ? A bug ?

Please tell me more.

Regards,

Phiphou

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.