[svn:osmf:] 16888: Fix bug FM-934 and add a corresponding unit test.

Revision: 16888
Revision: 16888
Author:   [email protected]
Date:     2010-07-12 14:13:49 -0700 (Mon, 12 Jul 2010)
Log Message:
Fix bug FM-934 and add a corresponding unit test. DVRCastNetLoader does not only checks streamType but also checks corresponding metadata under keys of DVRCastConstants.RECORDING_INFO_KEY and DVRCastConstants.STREAM_INFO_KEY
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-934
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/net/dvr/DVRCastNetLoader.as
    osmf/trunk/framework/OSMFTest/org/osmf/net/dvr/TestDVRCastNetLoader.as

Similar Messages

[svn:osmf:] 11205: Fix bug FM-169: Trait support for data transfer sample doesn' t display bytes loaded and bytes total for SWF element

Revision: 11205
Author:   [email protected]
Date:     2009-10-27 15:04:26 -0700 (Tue, 27 Oct 2009)
Log Message:
Fix bug FM-169: Trait support for data transfer sample doesn't display bytes loaded and bytes total for SWF element
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-169
Modified Paths:
    osmf/trunk/apps/samples/framework/PluginSample/src/PluginSample.mxml
    osmf/trunk/apps/samples/framework/PluginSample/src/org/osmf/model/Model.as

The bug is known, and a patch has been submitted: https://bugs.freedesktop.org/show_bug.cgi?id=80151. There's been no update since friday, so I wonder what the current status is, or if it's up for review at all.
Does anyone know how we can be notified when this patch hits the kernel?

[svn:osmf:] 14928: Fix bug FM-468: Initial and max indices not being respected for RTMP MBR.

Revision: 14928
Revision: 14928
Author:   [email protected]
Date:     2010-03-22 17:35:43 -0700 (Mon, 22 Mar 2010)
Log Message:
Fix bug FM-468: Initial and max indices not being respected for RTMP MBR.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-468
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/net/NetStreamSwitchManager.as
    osmf/trunk/framework/OSMFTest/org/osmf/net/TestNetStreamSwitchManager.as

[svn:osmf:] 16166: Fix bug FM-857: VAST impression and tracking events broken.

Revision: 16166
Revision: 16166
Author:   [email protected]
Date:     2010-05-17 16:44:55 -0700 (Mon, 17 May 2010)
Log Message:
Fix bug FM-857: VAST impression and tracking events broken.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-857
Modified Paths:
    osmf/trunk/libs/VAST/org/osmf/vast/media/VASTImpressionProxyElement.as
    osmf/trunk/libs/VAST/org/osmf/vast/media/VASTTrackingProxyElement.as
    osmf/trunk/libs/VASTTest/org/osmf/vast/media/TestVASTImpressionProxyElement.as
    osmf/trunk/libs/VASTTest/org/osmf/vast/media/TestVASTTrackingProxyElement.as

[svn:osmf:] 16975: Fix bug FM-964, add media factory item for RTMFP multicast and remove the item from OSMFPlayer

Revision: 16975
Revision: 16975
Author:   [email protected]
Date:     2010-07-19 15:20:00 -0700 (Mon, 19 Jul 2010)
Log Message:
Fix bug FM-964, add media factory item for RTMFP multicast and remove the item from OSMFPlayer
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-964
Modified Paths:
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/OSMFPlayer.as
    osmf/trunk/framework/OSMF/org/osmf/media/DefaultMediaFactory.as

Welcome guy -
Unless you are using Spry menus as a learning experience, you should move forward to a menus system that will display properly on the millions of portable devices that won't work with Spry which was deprecated 2 years ago.
Many are using JQuery menus or pure HTML/CSS menus.
If you wish to continue your Spry for learning experience, we'll be glad to assist; please let us know.
By the way, your submenus are not showing because you need to add the red value to this rule in your vertical CSS
ul.MenuBarVertical ul.MenuBarSubmenuVisible{
    width: 220px;
    left: 180px;

[svn:osmf:] 13027: Fix bug in SerialElement where the durationReached event was dispatched on a child-to-child transition due to the base class thinking that the duration had been reached (since the second child didn't have a duration yet).

Revision: 13027
Revision: 13027
Author:   [email protected]
Date:     2009-12-16 18:09:46 -0800 (Wed, 16 Dec 2009)
Log Message:
Fix bug in SerialElement where the durationReached event was dispatched on a child-to-child transition due to the base class thinking that the duration had been reached (since the second child didn't have a duration yet). Injection from trait refactoring.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/osmf/composition/CompositeTimeTrait.as

http://ww2.cs.fsu.edu/~rosentha/linux/2.6.26.5/docs/DocBook/libata/ch07.html#excatATAbusErr wrote:
ATA bus error means that data corruption occurred during transmission over ATA bus (SATA or PATA). This type of errors can be indicated by
ICRC or ABRT error as described in the section called “ATA/ATAPI device error (non-NCQ / non-CHECK CONDITION)”.
Controller-specific error completion with error information indicating transmission error.
On some controllers, command timeout. In this case, there may be a mechanism to determine that the timeout is due to transmission error.
Unknown/random errors, timeouts and all sorts of weirdities.
As described above, transmission errors can cause wide variety of symptoms ranging from device ICRC error to random device lockup, and, for many cases, there is no way to tell if an error condition is due to transmission error or not; therefore, it's necessary to employ some kind of heuristic when dealing with errors and timeouts. For example, encountering repetitive ABRT errors for known supported command is likely to indicate ATA bus error.
Once it's determined that ATA bus errors have possibly occurred, lowering ATA bus transmission speed is one of actions which may alleviate the problem.
I'd also add; make sure you have good backups when ATA errors are frequent

[svn:osmf:] 10991: Fix bug FM-119, where the playhead time doesn' t get updated until after the seek has completed.

Revision: 10991
Author:   [email protected]
Date:     2009-10-17 22:52:28 -0700 (Sat, 17 Oct 2009)
Log Message:
Fix bug FM-119, where the playhead time doesn't get updated until after the seek has completed. The bug is actually in Flash Player (FP-1705), and the workaround is to wait until NetStream.time gets updated before dispatching the seek completion event. This changelist also updates the unit tests and NetMocker to verify the fix.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-119
    http://bugs.adobe.com/jira/browse/FP-1705
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/osmf/net/NetStreamSeekableTrait.as
    osmf/trunk/framework/MediaFramework/org/osmf/traits/SeekableTrait.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/audio/TestAudioSeekableTrait.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/media/TestMediaPlayer.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/net/TestNetStreamSeekableTrait.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/traits/TestISeekable.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/traits/TestSeekableTrait.as
    osmf/trunk/libs/adobe/NetMocker/org/osmf/netmocker/MockNetStream.as
    osmf/trunk/libs/adobe/NetMockerTest/org/osmf/netmocker/TestMockNetStream.as

Revision: 10991
Author:   [email protected]
Date:     2009-10-17 22:52:28 -0700 (Sat, 17 Oct 2009)
Log Message:
Fix bug FM-119, where the playhead time doesn't get updated until after the seek has completed. The bug is actually in Flash Player (FP-1705), and the workaround is to wait until NetStream.time gets updated before dispatching the seek completion event. This changelist also updates the unit tests and NetMocker to verify the fix.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-119
    http://bugs.adobe.com/jira/browse/FP-1705
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/osmf/net/NetStreamSeekableTrait.as
    osmf/trunk/framework/MediaFramework/org/osmf/traits/SeekableTrait.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/audio/TestAudioSeekableTrait.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/media/TestMediaPlayer.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/net/TestNetStreamSeekableTrait.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/traits/TestISeekable.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/traits/TestSeekableTrait.as
    osmf/trunk/libs/adobe/NetMocker/org/osmf/netmocker/MockNetStream.as
    osmf/trunk/libs/adobe/NetMockerTest/org/osmf/netmocker/TestMockNetStream.as

[svn:osmf:] 14823: Fix bug where canPause was not set to false for live streams.

Revision: 14823
Revision: 14823
Author:   [email protected]
Date:     2010-03-17 10:51:40 -0700 (Wed, 17 Mar 2010)
Log Message:
Fix bug where canPause was not set to false for live streams.
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/net/NetStreamPlayTrait.as
    osmf/trunk/framework/OSMFTest/org/osmf/elements/TestVideoElement.as

Thanks for looking at this post. We have resolved the issue for ourselves by working with our DBAs to narrow down where the problem actually started. We found that the particular SQL we were looking at was not the issue. In a chart on a subsequent page (via a click through), we were actually running into where apex was starting to consuming memory but we were catching it later.
What we found was that when we had a chart query that was SQL containing a pipeline function, the memory usage went up. And within 10 minutes, the server would crawl to a halt. To release the memory, the DBAs would have to bounce the Apex instance. When I changed the query to be a function returning SQL, the problem stopped. I don't know what the correlation was between SQL and moving to a PL/SQL function returning SQL.
I am not even 100% positive of the pipeline function being the cause. I only know that this started happening about the same time as when I implemented the pipeline function. I understand you are leery of a one-second function/query running up that kind of utilization. No one here believed me either (including me really). We figured it HAD to be a coincidence. But once I changed the query from SQL to a function returning PL/SQL, our problem went away.
Thanks to all who looked at and thought about this.
Walter

[svn:osmf:] 15196: Fix bug FM-621: SerialElement dispatches READY event twice.

Revision: 15196
Revision: 15196
Author:   [email protected]
Date:     2010-04-01 21:16:48 -0700 (Thu, 01 Apr 2010)
Log Message:
Fix bug FM-621: SerialElement dispatches READY event twice. Fix inconsistency between MediaPlayer.stop implementation and ASDoc (i.e. the method should always rewind). Temporarily disable DurationElement test, needs some investigation as to why it behaves so different from the other MediaElement-in-MediaPlayer tests.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-621
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/elements/compositeClasses/SerialSeekTrait.as
    osmf/trunk/framework/OSMF/org/osmf/media/MediaPlayer.as
    osmf/trunk/framework/OSMFTest/org/osmf/OSMFTests.as
    osmf/trunk/framework/OSMFTest/org/osmf/media/TestMediaPlayer.as

[svn:osmf:] 15121: Fix bug related to validation of plugin versions.

Revision: 15121
Revision: 15121
Author:   [email protected]
Date:     2010-03-29 17:33:12 -0700 (Mon, 29 Mar 2010)
Log Message:
Fix bug related to validation of plugin versions. The fix is to load a dynamic plugin SWF twice. The first time it's loaded into a separate ApplicationDomain, so that the class types are not merged (and Version.version will not have identical values for player and plugin). If the version types are consistent, then the plugin is loaded a second time, this time into the same SecurityDomain (so that class types are merged). The second load should pull the SWF from the cache, minimizing the overhead. The downside is that the SWF will be initialized twice.
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/elements/SWFLoader.as
    osmf/trunk/framework/OSMF/org/osmf/elements/loaderClasses/LoaderUtils.as
    osmf/trunk/framework/OSMF/org/osmf/media/pluginClasses/DynamicPluginLoader.as
    osmf/trunk/framework/OSMF/org/osmf/media/pluginClasses/PluginLoader.as
    osmf/trunk/framework/OSMFIntegrationTest/org/osmf/media/pluginClasses/TestPluginManagerIn tegration.as
    osmf/trunk/framework/OSMFIntegrationTest/org/osmf/utils/IntegrationTestUtils.as

Hi sebasvideo, Did you ever find a solution to this? I've been having the same problem for a few months now and it's maddening. Seems to be specific to the GPU like you say above. I noticed it most when using Element 3D. I thought maybe there was some sort of read/write interference as I have 2 SSDs and one HD with assets spread across all of them. But even when I consolidated all of my data to one drive the flickering kept happening. Not sure if it's an After Effects problem specifically... or windows 8.1? Or nVidia? Super frustrating thoguh.

[svn:osmf:] 13028: Fix bug where NetStream would continue playback upon completion ( due to our not handling the new STOPPED state).

Revision: 13028
Revision: 13028
Author:   [email protected]
Date:     2009-12-16 18:10:28 -0800 (Wed, 16 Dec 2009)
Log Message:
Fix bug where NetStream would continue playback upon completion (due to our not handling the new STOPPED state). Injection from trait refactoring.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/osmf/net/NetStreamPlayTrait.as

My daughter has had her Razr for about 9 months now. About two weeks ago she picked up her phone in the morning on her way to school when she noticed two cracks, both starting at the camera lens. One goes completely to the bottom and the other goes sharply to the side. She has never dropped it and me and my husband went over it with a fine tooth comb. We looked under a magnifying glass and could no find any reason for the glass to crack. Not one ding, scratch or bang. Our daughter really takes good care of her stuff, but we still wanted to make sure before we sent it in for repairs. Well we did and we got a reply from Motorola with a picture of the cracks saying this was customer abuse and that it is not covered under warranty. Even though they did not find any physical damage to back it up. Well I e-mailed them back and told them I did a little research and found pages of people having the same problems. Well I did not hear from them until I received a notice from Fed Ex that they were sending the phone back. NOT FIXED!!! I went to look up why and guess what there is no case open any more for the phone. It has been wiped clean. I put in the RMA # it comes back not found, I put in the ID #, the SN# and all comes back not found. Yet a day earlier all the info was there. I know there is a lot more people like me and all of you, but they just don't want to be bothered so they pay to have it fix, just to have it do it again. Unless they have found the problem and only fixing it on a customer pay only set up. I am furious and will not be recommending this phone to anyone. And to think I was considering this phone for my next up grade! NOT!!!!

[svn:osmf:] 13308: Fixed bug in mast sample.

Revision: 13308
Revision: 13308
Author:   [email protected]
Date:     2010-01-06 10:39:53 -0800 (Wed, 06 Jan 2010)
Log Message:
Fixed bug in mast sample.
Modified Paths:
    osmf/trunk/apps/samples/plugins/MASTSample/src/MASTSample.as

I do not think you need a testcase to reproduce the bug. This is well documented bug and I know a lot of people having the same problems with DateFormat. Sun's SimpleDateFormat class is typical and often seen example for threading problems, and this is documented in the JDK APIDOCs.
It must be fixed. As Tomcat had fixed it, the simpliest would be to replace the CookieUtils CLASS file in SJSWS's JAR, this is not much work for Sun, I think!

[svn:osmf:] 15068: Fix bug FM-603: Need to signal complete event when live stream is unpublished.

Revision: 15068
Revision: 15068
Author:   [email protected]
Date:     2010-03-26 10:10:58 -0700 (Fri, 26 Mar 2010)
Log Message:
Fix bug FM-603: Need to signal complete event when live stream is unpublished.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-603
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/net/NetStreamCodes.as
    osmf/trunk/framework/OSMF/org/osmf/net/NetStreamTimeTrait.as

I have at least now managed to narrow down the problem.
I took a guess at the packages that were causing problems, and seems I guessed right.
By following this guide: http://wiki.archlinux.org/index.php/Downgrade_packages
I downgraded both libgl to version 7.7-1 and ati-dri to 7.7-1, and now I can X starts correctly.
I guess I'll need to figure out how to file a bug on those packages.

[svn:osmf:] 15527: Fix bug FM-696: Capability change events being dispatched after the trait to which they refer has been modified .

Revision: 15527
Revision: 15527
Author:   [email protected]
Date:     2010-04-16 17:21:06 -0700 (Fri, 16 Apr 2010)
Log Message:
Fix bug FM-696: Capability change events being dispatched after the trait to which they refer has been modified. Updated unit tests.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-696
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/media/MediaPlayer.as
    osmf/trunk/framework/OSMFTest/org/osmf/media/TestMediaPlayer.as

Major Update: The G-Keys can now be edited without recompiling by editing shell scripts at "/usr/share/g15daemon/macros/"
Each button has it's own script file named by it's label (e.g. to edit the functionality of G1, open the script named G1.) The button will try to execute the scripts as programs, so make sure they are executable (chmod +x) and as long as the name remains the same, if you want to replace the files with something different, know that the arguments currently given to the files ($1 and $2) are ($1)on/off and ($2)0-2 (where 0 is M1 and 2 is M3)
To download the updated sources, go here (only the g15daemon source/patch was updated). This thread's OP has been updated.
Last edited by rabcor (2015-02-12 04:46:48)

[svn:osmf:] 14592: Fix bug in ProxyElement's blockedTraits implementation.

Revision: 14592
Revision: 14592
Author:   [email protected]
Date:     2010-03-04 16:13:02 -0800 (Thu, 04 Mar 2010)
Log Message:
Fix bug in ProxyElement's blockedTraits implementation. Blocked traits take precedence over overridden traits. The bug was that events would still be dispatched for an overridden trait being added even when the trait was blocked. Update unit tests.
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/elements/ProxyElement.as
    osmf/trunk/framework/OSMFTest/org/osmf/elements/TestProxyElementAsDynamicProxy.as

(Removed)

[svn:osmf:] 16888: Fix bug FM-934 and add a corresponding unit test.

Similar Messages

Maybe you are looking for