[svn:osmf:] 18069: Fix FM-1035: Stream reconnect fails to timeout when reconnectTimeout is zero.

Revision: 18069
Revision: 18069
Author:   [email protected]
Date:     2010-10-07 11:28:56 -0700 (Thu, 07 Oct 2010)
Log Message:
Fix FM-1035: Stream reconnect fails to timeout when reconnectTimeout is zero. This is similar to the other (recent) stream reconnection bugs, in that it only seems reproduceable when NetStream.bufferLength is non-zero upon receipt of the Buffer.Empty event.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-1035
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/net/NetLoader.as

"Is it intended to cope with NetConnection.Connect.IdleTimeOut of FMS disconnecting clients after some time of inactivity?"
The answer is no. Stream reconnect is all about trying to reconnect in the event of a dropped network connection. For the IdleTimeOut scenario, listen for the MediaErrorEvent.MEDIA_ERROR event on the MediaPlayer and check for an error of MediaErrorCodes.NETCONNECTION_TIMEOUT. You can handle that however you wish in your player.
- charles

Similar Messages

[svn:osmf:] 11359: Fixing MetadataWatcher not invoking a value change callback when the parent facet of the target value is added or removed .

Revision: 11359
Author:   [email protected]
Date:     2009-11-02 05:20:01 -0800 (Mon, 02 Nov 2009)
Log Message:
Fixing MetadataWatcher not invoking a value change callback when the parent facet of the target value is added or removed.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/osmf/metadata/MetadataWatcher.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/metadata/TestMetadataUtils.as

mikeporter wrote:
I'm sorry I'm not aware of any "cumbersome" subpanels - unless of course you don't know what you're doing. There is this wonderful invention called a "subVI" that can be used to organize and simplify your code, or are they too "cumbersome" as well? You should really learn a bit about what you are pontificating over before you start running off at the mouth.
Mike...
I didn't want to step on your toes. No need to get personal.
Subpanels make some additional code necessary that hasn't got to do anything with the actual program. And I AM using subIVs as I wrote in my first post, which is exactly the root of the problem.
Nevertheless I now solved it in a way that comes close to what I wanted. I don't know if some of you meant your suggestions to be understood that way (at least I didn't ). The subVIs will now "insert" themselves (via invoke node) into a subpanel on the main vi, which they are given a reference of at call. This adds minimal aditional code, especially on the main VI which I want to keep as clean as possible. By clustering the panel reference into the parameters the subVIs are already given (not used in the example I attached below), there isn't even a change on the terminals of the subVIs.
I got to check now if this works well with event structures within the subVIs or if it can create the same problems like multiple event structures within a single VI.
So no global variables anymore and no writing values by property node. I don't know if this just wasn't possible in previous Labview versions I had a try at that (I guess it was 8.6 and/or 2009) or I just didn't come up with the idea back then.
And if the text wasn't that helpful, here are two screens:
Parent VI:
SubVI:
Attachments:
main.png ‏2 KB
subvi.png ‏5 KB

[svn:osmf:] 18047: Fix FM-1076: Reconnect timeout doesn't always work.

Revision: 18047
Revision: 18047
Author:   [email protected]
Date:     2010-10-06 16:29:01 -0700 (Wed, 06 Oct 2010)
Log Message:
Fix FM-1076: Reconnect timeout doesn't always work.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-1076
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/net/NetLoader.as

"Is it intended to cope with NetConnection.Connect.IdleTimeOut of FMS disconnecting clients after some time of inactivity?"
The answer is no. Stream reconnect is all about trying to reconnect in the event of a dropped network connection. For the IdleTimeOut scenario, listen for the MediaErrorEvent.MEDIA_ERROR event on the MediaPlayer and check for an error of MediaErrorCodes.NETCONNECTION_TIMEOUT. You can handle that however you wish in your player.
- charles

[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:] 14601: Fix bug where parsing of stream that gets passed to NetStream.play doesn' t take urlIncludesFMSApplicationInstance into account, resulting in stream not found error.

Revision: 14601
Revision: 14601
Author:   [email protected]
Date:     2010-03-05 09:47:28 -0800 (Fri, 05 Mar 2010)
Log Message:
Fix bug where parsing of stream that gets passed to NetStream.play doesn't take urlIncludesFMSApplicationInstance into account, resulting in stream not found error.
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/net/NetStreamPlayTrait.as
    osmf/trunk/framework/OSMF/org/osmf/net/NetStreamUtils.as
    osmf/trunk/framework/OSMF/org/osmf/net/dvr/DVRCastNetConnectionFactory.as
    osmf/trunk/framework/OSMFTest/org/osmf/net/TestNetStreamUtils.as

I had a while ago similar problem with USB memory stick. At the end, I don't know why, just formatting it using WinXP helped me.
S-
Last edited by StenM (2011-07-22 17:56:32)

[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:] 17761: Fix FM-1049: OSMFAIRTest compile errors.

Revision: 17761
Revision: 17761
Author:   [email protected]
Date:     2010-09-17 17:05:15 -0700 (Fri, 17 Sep 2010)
Log Message:
Fix FM-1049: OSMFAIRTest compile errors. OSMFAIRTest (& OSMFIntegrationTest) now default to 10.1, and to AIR 2.0. To run this on AIR 1.5, you need to make sure you're using a compatible SDK and a compatible set of FLASH_10_1 flags.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-1049
Modified Paths:
    osmf/trunk/framework/OSMFAIRTest/.actionScriptProperties
    osmf/trunk/framework/OSMFAIRTest/OSMFAIRTest-app.xml
    osmf/trunk/framework/OSMFIntegrationTest/.actionScriptProperties

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:osmf:] 14067: Fixed a bug in DynamicStreamingSample that Ivonne found.

Revision: 14067
Revision: 14067
Author:   [email protected]
Date:     2010-02-09 11:09:35 -0800 (Tue, 09 Feb 2010)
Log Message:
Fixed a bug in DynamicStreamingSample that Ivonne found.
Modified Paths:
    osmf/trunk/apps/samples/framework/DynamicStreamingSample/src/DynamicStreamingSample.mxml

I just noticed that for some reason the project is using an old path to my SVN repository. I recreated it and reimported the project but for some reason Xcode didn't realize that. I'm betting there's some little file somewhere that's causing my problem.

[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:] 15505: Fix image smoothing, which had been broken as a result of some changes to how the display object of an ImageElement is exposed .

Revision: 15505
Revision: 15505
Author:   [email protected]
Date:     2010-04-16 09:29:26 -0700 (Fri, 16 Apr 2010)
Log Message:
Fix image smoothing, which had been broken as a result of some changes to how the display object of an ImageElement is exposed. Add integration test.
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/elements/ImageElement.as
    osmf/trunk/framework/OSMFIntegrationTest/org/osmf/elements/TestImageElementIntegration.as

That's a comment in the file. It has no effect at all.

[svn:osmf:] 13806: Fix a bug with the handling of drm metadata/ additional header

Revision: 13806
Revision: 13806
Author:   [email protected]
Date:     2010-01-27 10:00:06 -0800 (Wed, 27 Jan 2010)
Log Message:
Fix a bug with the handling of drm metadata/additional header
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/net/NetStreamPlayTrait.as

(Removed)

[svn:osmf:] 10751: Fix a bug with the ReferenceSample project.

Revision: 10751
Author:   [email protected]
Date:     2009-09-30 10:57:34 -0700 (Wed, 30 Sep 2009)
Log Message:
Fix a bug with the ReferenceSample project.
Modified Paths:
    osmf/trunk/apps/samples/framework/ReferenceSample/org/openvideoplayer/model/ReferenceSWFE lement.as
    osmf/trunk/apps/samples/framework/ReferenceSample/org/openvideoplayer/view/MainWindow.as

(Removed)

[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:] 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:] 17708: Fix FM-932: Scaling of parallel elements is not consistent.

Revision: 17708
Revision: 17708
Author:   [email protected]
Date:     2010-09-14 16:32:29 -0700 (Tue, 14 Sep 2010)
Log Message:
Fix FM-932: Scaling of parallel elements is not consistent.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-932
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/elements/compositeClasses/ParallelDisplayObjectTrait.a s
    osmf/trunk/framework/OSMFTest/org/osmf/elements/TestParallelElementWithDisplayObjectTrait .as

[svn:osmf:] 18069: Fix FM-1035: Stream reconnect fails to timeout when reconnectTimeout is zero.

Similar Messages

Maybe you are looking for