[svn:osmf:] 14625: Reworked fix for FM-506.

Revision: 14625
Revision: 14625
Author:   [email protected]
Date:     2010-03-08 10:37:29 -0800 (Mon, 08 Mar 2010)
Log Message:
Reworked fix for FM-506. Current time == duration once the video stops, and seek(0) goes to 0.   Handles incorrect duration metadata, as well as audio delay offsets.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-506
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/net/NetStreamTimeTrait.as

Similar Messages

[svn:osmf:] 17499: Partial fix for FM-990: prevent RTE when attempting smoothing for an image where a policy file was not available

Revision: 17499
Revision: 17499
Author:   [email protected]
Date:     2010-08-27 11:05:22 -0700 (Fri, 27 Aug 2010)
Log Message:
Partial fix for FM-990: prevent RTE when attempting smoothing for an image where a policy file was not available
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-990
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/elements/ImageElement.as

Revision: 17499
Revision: 17499
Author:   [email protected]
Date:     2010-08-27 11:05:22 -0700 (Fri, 27 Aug 2010)
Log Message:
Partial fix for FM-990: prevent RTE when attempting smoothing for an image where a policy file was not available
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-990
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/elements/ImageElement.as

[svn:osmf:] 13002: Some fixes for the composite view trait.

Revision: 13002
Revision: 13002
Author:   [email protected]
Date:     2009-12-16 13:04:30 -0800 (Wed, 16 Dec 2009)
Log Message:
Some fixes for the composite view trait. Integrated some of the unit tests (though some still break and are commented out).
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/osmf/composition/CompositeViewTrait.as
    osmf/trunk/framework/MediaFramework/org/osmf/composition/ParallelViewTrait.as
    osmf/trunk/framework/MediaFramework/org/osmf/composition/SerialViewTrait.as
    osmf/trunk/framework/MediaFramework/org/osmf/layout/LayoutContextSprite.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/MediaFrameworkTests.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/composition/TestParallelElement.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/composition/TestSerialElement.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/utils/DynamicMediaElement.as
Added Paths:
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/composition/TestParallelElementWithV iewTrait.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/composition/TestSerialElementWithVie wTrait.as

It's important to understand what traits are and what they're not:
Traits are not intended to be generically extensible: there's a fixed set within the framework (although we may add additional traits in the future, to support new Flash/FMS capabilities). We experimented with making them fully extensible, but it turned out to be not worth the cost, particularly since there shouldn't be that many traits in a media system.
Traits represent fundamental characteristics or capabilities of the media in its context. For example, some media is playable (videos), other media is not (images).
A trait cannot apply to all media types. If it could, then there would be no reason to model it as a trait, instead we would model it as part of the MediaElement. Metadata is a good example of this, in that any MediaElement might have some metadata associated with it, so it wouldn't make sense to make metadata a trait. Similarly, any MediaElement has the ability to go into fullscreen mode, so I wouldn't model the ability to go fullscreen as a trait.
On a semi-related note, I'm often asked (inside Adobe and elsewhere) for a technical overview of OSMF. I've posted the slides that I use for this purpose here:
https://sourceforge.net/adobe/osmf/wiki/_discuss/thread/d6c3d719/1962/attachment/OSMF%20Ar chitectural%20Building%20Blocks.pdf
The slides cover the fundamental building blocks of OSMF, things you are likely to use over and over if you're building complex media experiences. They might shed some light on which different parts of OSMF should be used in which situations.

[svn:osmf:] 15899: Attempted fix for unit tests failure.

Revision: 15899
Revision: 15899
Author:   [email protected]
Date:     2010-05-04 17:21:06 -0700 (Tue, 04 May 2010)
Log Message:
Attempted fix for unit tests failure.
Modified Paths:
    osmf/trunk/framework/OSMFTest/org/osmf/OSMFTests.as

[svn:osmf:] 14007: Partial fix for FM-383: ProxyElement needs to dispatch traitRemove/ traitAdd event pairs when the proxy adds or removes a trait that also exists on the proxied element .

Revision: 14007
Revision: 14007
Author:   [email protected]
Date:     2010-02-05 11:54:43 -0800 (Fri, 05 Feb 2010)
Log Message:
Partial fix for FM-383: ProxyElement needs to dispatch traitRemove/traitAdd event pairs when the proxy adds or removes a trait that also exists on the proxied element.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-383
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/media/MediaElement.as
    osmf/trunk/framework/OSMF/org/osmf/proxies/ProxyElement.as
    osmf/trunk/framework/OSMFTest/org/osmf/proxies/TestProxyElementAsDynamicProxy.as

[svn:osmf:] 16270: Recommitted fix for FM-857: VAST and MAST impressions and tracking events are broken.

Revision: 16270
Revision: 16270
Author:   [email protected]
Date:     2010-05-20 19:19:57 -0700 (Thu, 20 May 2010)
Log Message:
Recommitted fix for FM-857: VAST and MAST impressions and tracking events are broken.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-857
Modified Paths:
    osmf/trunk/libs/samples/VAST/org/osmf/vast/media/VASTImpressionProxyElement.as
    osmf/trunk/libs/samples/VAST/org/osmf/vast/media/VASTTrackingProxyElement.as
    osmf/trunk/libs/samples/VASTTest/org/osmf/vast/media/TestVASTImpressionProxyElement.as
    osmf/trunk/libs/samples/VASTTest/org/osmf/vast/media/TestVASTTrackingProxyElement.as

[svn:osmf:] 10683: Bug fix for SWFElement drawing outside of its bounds causing layout havok.

Revision: 10683
Author:   [email protected]
Date:     2009-09-29 09:29:55 -0700 (Tue, 29 Sep 2009)
Log Message:
Bug fix for SWFElement drawing outside of its bounds causing layout havok.   FM-87 and FM-77
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-87
    http://bugs.adobe.com/jira/browse/FM-77
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/openvideoplayer/content/ContentElement.as

FYI - This regression has been filed here: http://bugs.adobe.com/jira/browse/SDK-31989

[svn:osmf:] 15607: Partial fix #2 for FM-719.

Revision: 15607
Revision: 15607
Author:   [email protected]
Date:     2010-04-20 12:37:41 -0700 (Tue, 20 Apr 2010)
Log Message:
Partial fix #2 for FM-719. This fix ensures that when seeking in and out of the child of a parallel element, that the play state is updated according to the play state of the composition. For example, if there are two parallel children of duration 10 and 20 seconds, and the parallel element is playing, and you seek from 15 to 5, then the shorter child should resume playback. (And similar for when paused.) Bug detected when verifying the (soon to be checked in) fix for FM-719, and seeking in and out of the section of video where the image should be displayed. Added unit tests for these cases as well.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-719
    http://bugs.adobe.com/jira/browse/FM-719
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/elements/compositeClasses/ParallelSeekTrait.as
    osmf/trunk/framework/OSMFTest/org/osmf/elements/TestParallelElementWithSeekTrait.as

[svn:fx-trunk] 14139: Fix for Player classes not code hinting to framework FB projects.

Revision: 14139
Revision: 14139
Author:   [email protected]
Date:     2010-02-11 16:36:39 -0800 (Thu, 11 Feb 2010)
Log Message:
Fix for Player classes not code hinting to framework FB projects. Changed all the $ tokens to use $ instead. While the compiler understands $, Flash Builder's code model does not.
No code changes.
QE notes: N/A
Doc notes: N/A
Bugs: None
Reviewer: Pete
Tests run: checkintests
Is noteworthy for integration: No
Modified Paths:
    flex/sdk/trunk/frameworks/projects/airframework/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/airspark/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/flex/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/framework/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/osmf/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/rpc/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/spark/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/sparkskins/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/textLayout/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/wireframe/.actionScriptProperties

[svn:fx-trunk] 12962: Fix for ASDoc not saving event type for [Bindable] metadata tag

Revision: 12962
Revision: 12962
Author:   [email protected]
Date:     2009-12-15 10:32:23 -0800 (Tue, 15 Dec 2009)
Log Message:
Fix for ASDoc not saving event type for metadata tag
QE notes: None.
Doc notes: None
Bugs: SDK-24706
Reviewed By:Corey
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24706
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGenerator.ja va

aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 3: NVIDIA HDMI [NVIDIA HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0
Which correspondents fine with the
device "hw:0,3"
in my mpd.conf alsa section.
Also sound worked fine withh this config before I started installing ffmpeg-svn and alikes
hokasch:
I tried changing the mixer to "Master" but that did not change much.

[svn:fx-trunk] 7473: Fix for 'ant asdoc' does not work.

Revision: 7473
Author:   [email protected]
Date:     2009-06-01 12:09:26 -0700 (Mon, 01 Jun 2009)
Log Message:
Fix for 'ant asdoc' does not work.
It should now work from both svn and package zip.
Bugs: SDK-15306
QE Notes: None.
Doc Notes: None.
tests: checkintests
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-15306
Modified Paths:
    flex/sdk/trunk/asdoc/build.xml
    flex/sdk/trunk/build.xml

[svn:fx-trunk] 13136: Fix for FLEXENT-1196 ( Replay of click on NavigatorContent does not close the combobox)

Revision: 13136
Revision: 13136
Author:   [email protected]
Date:     2009-12-21 17:40:28 -0800 (Mon, 21 Dec 2009)
Log Message:
Fix for FLEXENT-1196 (Replay of click on NavigatorContent does not close the combobox)
We need not record OPEN event when it is triggered from a KeyBoard event that types a character. Replaying the type event would automatically open the drop down.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FLEXENT-1196
Modified Paths:
    flex/sdk/trunk/frameworks/projects/automation_spark/src/spark/automation/delegates/compon ents/SparkComboBoxAutomationImpl.as
    flex/sdk/trunk/frameworks/projects/automation_spark/src/spark/automation/delegates/compon ents/supportClasses/SparkDropDownListBaseAutomationImpl.as

[svn:fx-trunk] 10898: Fix for a bug: After playing a hide effect, a window wouldn't be visible again.

Revision: 10898
Author:   [email protected]
Date:     2009-10-06 13:54:04 -0700 (Tue, 06 Oct 2009)
Log Message:
Fix for a bug: After playing a hide effect, a window wouldn't be visible again.
The issue here is that all effects that occur because of HIDE end up calling setVisible() (see EffectManager.effectEndHandler). Window/WindowedApplication was basically left with two concepts of setVisible...the displayObject one and the native application one, and they were out of synch. So setting visible=true on the window wasn?\226?\128?\153t calling setVisible(true) which controls the display object visibility. Now instead of doing our work in the visible setter, we override setVisible() and do it in there.
QE notes: -
Doc notes: -
Bugs: SDK-23263
Reviewer: Darrell
Tests run: checkintests, Rob ran mustella window/windowedapplication
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23263
Modified Paths:
    flex/sdk/trunk/frameworks/projects/airframework/src/mx/core/Window.as
    flex/sdk/trunk/frameworks/projects/airframework/src/mx/core/WindowedApplication.as
    flex/sdk/trunk/frameworks/projects/airframework/src/spark/components/Window.as
    flex/sdk/trunk/frameworks/projects/airframework/src/spark/components/WindowedApplication. as

I run Suse 9.1 Linux, and Suse has a package called lmsensors which by default on my machine gives readings like this:
Code: [Select]
temp1: +27°C (high = +0°C, hyst = +22°C) sensor = thermistor
temp2: +41.0°C (high = +80°C, hyst = +75°C) sensor = PII/Celeron diode
Now that 41C is pretty high for an idle AMD643000+ running at 1000Mhz, 1.08V. Too high, I would say. temp 1 in this case is the SYS temp, temp2 is the CPU temp.
Now, using lmsensors I can duplicate your little trick and tell it that temp 2 is in fact a 3904 transistor. Having done this can I get readings like this:
Code: [Select]
temp1: +27°C (high = +0°C, hyst = +22°C) sensor = thermistor
temp2: +16.0°C (high = +80°C, hyst = +75°C) sensor = 3904 transistor
Problem is, I'm not sure that the sensor is actually a 3904 transistor! The number's lower, but I was pretty sure that the sensor in the AMD64 is in fact a diode. Also, surely the CPU temp can't actually be that much lower than the SYS temp.
So, I think your fix succeeds in giving lower temps and that's great in that it will tell your system software that the CPU is not overheating, but I don't think it's the solution to high temp reporting. Anyway, as you say, its a solution for people who can't run with system shutdowns due to bogus high temps.
I've been looking at these temp issues with the MSI K8T, and I was thinking the problem was simply a miscalibration. The Winbond sensor chip on my board (maybe the K8N is the same, maybe not) has a sensor temp offset that gets added to the temp coming from the sensor. On the K8T this number is +54C. Funny number I know, but I've "fixed" the problem while I wait for a real bios fix on the K8T by simply reducing this offset to give me a CPU temp that matches SYS temp when idle. This enables cool'n'quiet fan control to work properly on my system, which is my main practical concern.

[svn:fx-trunk] 12982: Fix for issue with exposing accessible names for combobox list items

Revision: 12982
Revision: 12982
Author:   [email protected]
Date:     2009-12-15 20:44:23 -0800 (Tue, 15 Dec 2009)
Log Message:
Fix for issue with exposing accessible names for combobox list items
QE notes: none
Doc notes: none
Bugs: n/a
Reviewer: Gordon
Tests run: checkintests
Is noteworthy for integration: no
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/accessibility/ComboBoxAccImpl.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/accessibility/ListBaseAccImpl.as

Add this to the end of your nav p CSS selector at Line 209 of your HTML file, after 'background-repeat...':
margin-bottom: -2px;
Your nav p will then look like this:
nav p {
          font-size: 90%;
          font-weight: bold;
          color: #FFC;
          background-color: #090;
          text-align: right;
          padding-top: 5px;
          padding-right: 20px;
          padding-bottom: 5px;
          border-bottom-width: 2px;
          border-bottom-style: solid;
          border-bottom-color: #060;
          background-image: url(images/background.png);
          background-repeat: repeat-x;
          margin-bottom: -2px;

[svn:fx-trunk] 12994: * Fixes for two issues that were showing up in FB.

Revision: 12994
Revision: 12994
Author:   [email protected]
Date:     2009-12-16 06:44:45 -0800 (Wed, 16 Dec 2009)
Log Message:
Fixes for two issues that were showing up in FB.
QE notes:
Doc notes:
Bugs: SDK-24669, SDK-24686
Reviewer: Corey
Cycloner: George
Tests run: checkintests
Is noteworthy for integration: yes, fixes two FB issues.
Code-level description of changes:
modules/compiler/src/java/flex2/tools/PreLink.java
    Modified postRun() to swap in the root CompilationUnit's Logger
    when validating it's StyleContainer. This allows the warnings
    from StylesContainer.validate() to be persisted across incremental
    compilations. This fixes SDK-24686.
modules/compiler/src/java/flex2/compiler/Source.java
    Made getLogger() public, so it could be called from PreLink.
modules/compiler/src/java/flex2/compiler/CompilerAPI.java
    Modified compile() to check forcedToStop() after each PreLink
    batch. This fixes SDK-24669.
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24669
    http://bugs.adobe.com/jira/browse/SDK-24686
    http://bugs.adobe.com/jira/browse/SDK-24686
    http://bugs.adobe.com/jira/browse/SDK-24669
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilerAPI.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/Source.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/linker/CULinkable.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/tools/PreLink.java

[svn:osmf:] 14625: Reworked fix for FM-506.

Similar Messages

Maybe you are looking for