Using the StageVideo and Adobe AIR 3.2 SDK for an iOS app brings a strange zoom when the video starts, anyone any ideas of how to solve this problem?, is this a new bug in 3.2 SDK?
Also a few months ago we post an issue concatenating videos using the StageVideo where trying to play videos one after each other shows a flashing (video clears itself making impossible to play them seamlessly):
Anyone is experiencing this 2 issues, any workarounds?
Here there is a video demosntration of the problem:
Could you please reply back about the video which we had shot in which we had tried to reproduce the issue and sent to you for review.
We could then take proceed with further steps.
Hello, I also posted this same "zooming" issue a few months ago:
However, I never received any helpful responses, and nothing from Adobe.
I am still encountering this "zooming" issue, and the latest version of iOS 6 seems to break my rather ugly workaround.
Have there been any developments in this issue?
Hi gordogre or anyone else affected by this issue,
If you haven't already, please take a minute and create a bug report at http://bugbase.adobe.com. Once entered, please post back with the bug number or URL so that others impacted can add their comments and votes.
I'll ask the iOS team to take a look and see where we are at with this issue.
I have submitted a bug report here:
As noted in my report, I have a rather delicate workaround that broke with the introduction of iOS 6, unless I rolled back my AIR SDK to 3.1... I am sincerely hoping that the iOS team is able to look into this issue to avoid the work-around completely.
As I've already mentioned, I submitted a bug on this issue:
I also noted that the original poster of this forum topic also submitted a similar bug back in March:
I see that this older bug is still in the "Open"/"Unverified" state/status, with 4 votes, but no evidence that the bug has been reviewed by the iOS team. One of the votes also mentions this "zoom" issue.
I have a new urgency regarding this issue, because my workaround effectively broke with the introduction of iOS 6, so I am sincerely hoping to get some new information on whether the iOS team is in fact aware of the issue, and whether there is any chance that this defect will be addressed any time soon.
I do appreciate any information or assistance that can be provided.
Thanks for entering the bug. I've forwarded this along to the iOS and video teams so they can take a look. We have an internal bug against this issue (3286399) but we had to defer it back in July due to lack of time for that release. I've let the teams know that your workaround (is this described in your project's code?) has stopped working in iOS 6. When you get a chance, could you update the bug with this information?
I provided some details about my workaround when I submitted the bug, including the fact that it is now broken using the latest AIR SDK when using iOS 6.
It is encouraging to know that there is an "internal bug against this issue", but I guess that makes me curious about how I may continue to seek the status of the internal bug, because I notice that when I enter 3286399 in bugbase.adobe.com, nothing comes up...
I don't mean to be difficult, but I'd like to know how to set my expectations as to timing, in part because I'd like to start using some of the new features of the recent SDK's, such as the background worker threads, but I won't be able to do so while this video bug remains in place.
Thanks for your help.
We actually created a new bug on this (cloned the older, deferred issue with a new internal bug, #3337746). I've linked this internal bug to your public bug. This should trigger us to update the public bug once the internal bug is marked fixed. As an FYI, development is actively looking at this issue right now.
It was close, but unfortunately the fix we had implemented for this bug injected a more severe bug that was found close to the end of the 3.6 development cycle. The fix was rolled back and the bug was deferred as we ran out of time. I'd recommend making some noise on the external bug report so we get an idea of how many people this is impacting.
Europe, Middle East and Africa