true, actually I've rebuild the app to get its dimensions from XML, which is safe and reliable. Though this time it's offcourse a luxury to be able to do that, it would be great to get a method out which doesn't rely on external data, it seems wishful thinking in a way.
On Mon, Nov 10, 2008 at 7:26 PM, dr.ache <[EMAIL PROTECTED]> wrote: > Maybe this is not appropriate for you but since I also had this problem > I always put the dimensions in the xml file from which the application > gets its content. Its not dynamic but reliable. > > Mark > > sebastian schrieb: > > Hi, just a little comment, but if the size reported results in 0 by 0 >> pixels, you can always set a condition that sets it to a minimum/default >> size... hopefully the aspect-ratio is not also a variable. >> >> good luck! >> >> Seb. >> >> Meinte van't Kruis wrote: >> >>> I found the post. It would be nice to have standardised metadata, but it >>> seems to >>> be something that's a long way from now, espessially since nothing of the >>> sort >>> is beeing promoted or pushed by Adobe. >>> >>> Metadata aside though, I think it's a bit of a flaw to not have >>> dimensions >>> ready >>> when the buffer is full all the time, it seems quite illogical to me. I >>> mean >>> seriously, >>> how hard is it for Adobe to have a consistent and flawless way of >>> accessing >>> duration and dimensions, it seems such a basic requirement, but oh well.. >>> </rant> >>> >>> On Mon, Nov 10, 2008 at 4:44 PM, Juan Delgado <[EMAIL PROTECTED]> >>> wrote: >>> >>> I sent an email to the list not time ago regarding this issue. I was >>>> asking for a metadata standard with at least the most basic properties >>>> mandatory. Search the list for "flv metadata" it should appear (I've >>>> been trying to access the archive to give you a direct link, but >>>> doesn't work for me, I'm afraid). >>>> >>>> I haven't found any better way of solving the problem, to be honest. >>>> So I'm all ears. >>>> >>>> On Mon, Nov 10, 2008 at 3:22 PM, Meinte van't Kruis <[EMAIL PROTECTED]> >>>> wrote: >>>> >>>>> No, I'm actually using the Video object along with the Netstream class. >>>>> Wonder how that >>>>> ready event gets fired though, wouldn't be surprised if it's also fired >>>>> >>>> on a >>>> >>>>> buffer full, either >>>>> that or using timers (amuse yourself and watch the VideoPlayer and >>>>> FLVPlayback code >>>>> in the flash folder, count the number of timers used ;)) >>>>> >>>>> On Mon, Nov 10, 2008 at 1:57 PM, Muzak <[EMAIL PROTECTED]> >>>>> wrote: >>>>> >>>>> If you're using the FLVPlayback component, use the "ready" event: >>>>>> >>>>>> >>>>>> >>>> http://livedocs.adobe.com/flash/9.0/ActionScriptLangRefV3/fl/video/FLVPlayback.html#event:ready >>>> >>>>> >>>>>> >>>>>> ----- Original Message ----- From: "Meinte van't Kruis" < >>>>>> >>>>> [EMAIL PROTECTED]> >>>> >>>>> To: "Flash Coders List" <flashcoders@chattyfig.figleaf.com> >>>>>> Sent: Monday, November 10, 2008 11:56 AM >>>>>> Subject: [Flashcoders] FLV: reliable height&width dimensions >>>>>> >>>>>> >>>>>> >>>>>> Hi Folks, >>>>>> >>>>>>> I've been having trouble reliably getting FLV dimensions with both >>>>>>> progressive and streaming files. >>>>>>> I'm current using the buffer full event to resize the video >>>>>>> proportionally, >>>>>>> therefore needing videoHeight >>>>>>> and videoWidth. The problem is that once every now and again those >>>>>>> dimensions start out at 0 0, even >>>>>>> when the buffer is full. >>>>>>> >>>>>>> Furthermore the metadata has no dimension information, so can't use >>>>>>> >>>>>> that >>>> >>>>> either (plus I've heard onMetaData is unreliable as well). >>>>>>> >>>>>>> Any good solutions on this? >>>>>>> >>>>>>> Possible solutions would be to check on an interval wether the value >>>>>>> changes(this would really be unpreferable). Also, since I re-use the >>>>>>> Video object in the playlist, that video-object keeps remembering the >>>>>>> videoHeight/videoWidth of the previous video whenever the current >>>>>>> video >>>>>>> has not overridden it yet, making it impossible to do a simple >>>>>>> enterframe/timer kill whenever it is greater than 0 or has changed, >>>>>>> >>>>>> since >>>> >>>>> I >>>>>>> can't >>>>>>> be sure of that (next video might have same dimensions..). >>>>>>> >>>>>>> So I'm a bit stuck here, I really don't want to have an infinite >>>>>>> >>>>>> interval >>>> >>>>> checking the dimensions... Any suggestions? >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> M.A. van't Kruis >>>>>>> >>>>>>> _______________________________________________ >>>>>> Flashcoders mailing list >>>>>> Flashcoders@chattyfig.figleaf.com >>>>>> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders >>>>>> >>>>>> >>>>> >>>>> -- >>>>> M.A. van't Kruis >>>>> http://www.malatze.nl/ >>>>> _______________________________________________ >>>>> Flashcoders mailing list >>>>> Flashcoders@chattyfig.figleaf.com >>>>> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders >>>>> >>>>> >>>> >>>> -- >>>> Juan Delgado - Zárate >>>> http://zarate.tv >>>> http://dandolachapa.com >>>> http://loqueyosede.com >>>> >>>> _______________________________________________ >>>> Flashcoders mailing list >>>> Flashcoders@chattyfig.figleaf.com >>>> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders >>>> >>>> >>> >>> >>> _______________________________________________ >> Flashcoders mailing list >> Flashcoders@chattyfig.figleaf.com >> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders >> >> >> > _______________________________________________ > Flashcoders mailing list > Flashcoders@chattyfig.figleaf.com > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > -- M.A. van't Kruis http://www.malatze.nl/ _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
