Air 3.6 Roadmap?

Any Information when Air 3.6 Beta will begin, and what will be included in it ? Thanks for the greate work on AIR

Also interested in the release notes of the new Air Beta.

Similar Messages

AIR 1.1 Roadmap

Hello,
I've just visited this website and would like to share with
those who have not yet seen it:
http://www.flashmagazine.com/News/detail/air_roadmap/
There are some cool things being planned for AIR 2.0. I would
love to see the USB device support so designers can write usb
drivers for hardware.
Keep up the good work

I see lots of heated debates about future features, and the usual answer from Adobe is to have us read the whitepaper to find out what the current situation is.
With regard to Windows 8 Modern UI, it says (at http://www.adobe.com/devnet/flashplatform/whitepapers/roadmap.html ):
"Adobe and Microsoft are working closely together, and are investing in continuing to deliver Flash Player for Windows 8 and future versions of Windows on both Windows desktop and Modern UI."
That's as of Jan 30th.
I had got slightly confused by your original question, and was thinking more about Windows mobile. There's no information in the whitepaper about that.

AIR h.264 encoding support

Is h.264 encoding in AIR at the roadmap of Adobe? I know Adobe is working hard on delivering the requested features, and thanks for the Echo Cancellation. It works great. H264 is now in flash player, but can we expect classes H264VideoStreamSettings, H264Profile, H264Level be available on the AIR in the future as well? I can't think of any technical issues regarding this, but is there any legal issues? It would be very important for us to know, to make a business decisions now.
Thank you.

I'll ask around and see if I can find any info about this, in the mean time, if you haven't voted already I'd like to encourage you to cast your vote for this feature request over at ideas.adobe.com
H.264/AAC encoding from AIR/Flash player
Thanks,
Chris

Adobe AIR product Roadmaps

Does anyone happen to know if Adobe publish product roadmaps, as in planned release dates, OOC patching etc. In particular for Adobe AIR but am also after all products.
Thanks

Moved to AIR Installation Issues

How do you use AIR's WebKit/htmlloader?

Hi everyone,
A long standing issue in AIR has been the inclusion of an older version of WebKit. The request to update this library has come up many times in the forum and is in the top 10 on the community driven Uplist feature page. As with the recent and ongoing physics discussion, we're not committing to any changes purposed below at this time, as we're purely in an investigation mode at this time. We realize that this is an important feature and we need further clarification on what you're looking for. Please read on for questions from our development team.
We are exploring updating WebKit, but due to our modification of the WebKit source, this will be difficult, and updating WebKit will change the HTML DOM, possibly breaking content authored for our existing DOM.
So we are also exploring leaving HTMLLoader alone, for now, but providing a reasonable alternative.
StageWebView was originally written as a replacement for HTMLLoader on mobile (because we could not use our WebKit on mobile, StageWebView took advantage of the browser provided by the platform).
But it was extended to the desktop as an unsuccessful solution to this problem.
On mobile, content was probably newly written (so it could be tested with StageWebView), and the browsers were similar enough to our WebKit that the DOM impact was minor.
But on the desktop, forcing older content written for our WebKit to run on Internet Explorer 8 (as an example) was a disaster due to the differences in the DOM’s. We resolved this by making HTMLLoader versus StageWebView on the desktop a choice.
Which gets to the questions (for desktop development only).
Which is more attractive, an embedded web browser or using the system browser? Is it valuable to provide both?
For instance, using the native browser can save on code size (perhaps 6 MB), but you must create and test portable HTML, and you face the risk that future updates to the system browser breaks your content.
How much interop do you need between AS and JS?
Hearsay suggests another problem with StageWebView is there is no interop between ActionScript and JavaScript, whereas HTMLLoader had a lot of support.
Would StageWebView be sufficient if it exposed an ExternalInterface, or sandbox bridge, level of functionality? For instance, if AS could register a list of functions which could be called from JS (and vice versa), would that be enough? Or is there something else that HTMLLoader does that is essential?
For instance, one of the ideas being explored is to provide an entirely new class (perhaps as an ANE) which links an unmodified version of the latest WebKit source as a static library. By using unmodified source, we can more readily update to newer versions of WebKit. As well, if we leave the existing classes unchanged, we don’t risk breaking existing content. But if we use unmodified WebKit source, we may find some of HTMLLoader’s functionality impossible to match, which is why I’m interested in understanding the essential functionality, so we can decide if a sufficient, minimal (so it’s easier to support without customizing Webkit) interface for it.
Thanks,
Chris

Hey Chris,
Thank you for reaching out to the community! Our team has been working on AIR apps for a while now. It has been frustrating to say the least, trying to integrate sophisticated HTML5 apps into our different AIR apps.
The existing solutions on mobile and desktop are not very satisfying. Mobile has gotten better because of the StageWebView, but there are still several flaws that make the platform unpredictable. On desktop it is even worse and we are facing a tough decision.
We want to integrate an HTML5 app into an already existing AIR app. The two applications will have to communicate in some form with each other. The StageWebView approach with a simple ExternalInterface would suffice, as long as we could pick from the browsers that are installed. The ANE class approach also sounds good, but only if there is a similar way of communication.
We think that keeping the component (WebView or ANE class) as lean as possible is one of the most important things. We don't want to face the same issues in the near future. There is also a need to update that underlying layer fast. Browser vendors (with some exceptions of course ) have much faster release cycles nowadays. They will keep pushing the boundaries and we need to adjust accordingly.
The HTML5/JS should take care of the DOM manipulation, event handling and communicate back to Actionscript in a simple way. There is no need for Actionscript to worry about these things. And if there is, create a simple JS layer using the interface to do the job.
Here is a list of features that are essential to us:
Accessing the local file system (xhr requests on the local file system):
Worst case scenario: Using the ExternalInterface to feed files to the HTML application.
Configure the cache or at least manipulate cache handling
Much better HTML5 / CSS3 support: Video, Audio, SVG, CSS3 Animations, etc.
Easier and faster way to update the underlying WebKit/Chromium (relevant for ANE)
Are there any plans yet? Is it on your roadmap? Are we talking about years or months? Answers to these questions are very crucial for us. Only with those answers will we know, whether we can keep working on the AIR platform or if we have to look for alternatives and migrate our entire application.
We are looking forward to your answers.
Thanks

I have built a android application using adobe flex, and i have exported it with native air. The application is working fine on samsung phones whereas it is getting crashed on Moto Phones, which runs on android kitkat, is there any compatibility issue ?,

I have built a android application using adobe flex, and i have exported it with native air. The application is working fine on samsung phones whereas it is getting crashed on Moto Phones, which runs on android kitkat, is there any compatibility issue ?, I have built a android application using adobe flex, and i have exported it with native air. The application is working fine on samsung phones whereas it is getting crashed on Moto Phones, which runs on android kitkat, is there any compatibility issue ?, I have built a android application using adobe flex, and i have exported it with native air. The application is working fine on samsung phones whereas it is getting crashed on Moto Phones, which runs on android kitkat, is there any compatibility issue ?

Thanks, Flex harUI, for the direction in regards to isolating build changes. That aside (still working on it), can you offer any direction in regards to my original question on SDK and AIR compatibility? I'm specifically looking for a version compatibility mapping or anything that definitively states, "Flex SDK x.y.z works with the following versions of AIR". This information is crucial for us in order to more specifically plan our own roadmap built upon these two frameworks as we consider both existing installations of our software and future distributions.

RoboHelp 9 Closing while building AIR

Hello,
I've been pulling my hair out trying to fix this, and I'm getting dangerously close to switching to that other app that rhymes with Glare, so hopefully someone can save us.
When we try to build the AIR version of our project, RoboHelp starts the build process, then just closes. No error message, doesn't appear to be a crash...just exits.
It worked fine in this same project a few hours ago. Tried it again just now and no luck.
This happened to me earlier on a different project and I started the project over, which fixed it again for awhile...until I encountered it yet again.
I've put the entire project into a zip folder and uploaded it to ftp://ftp.kinematics.com/pub/SA/Install/SA%20Roadmap/Roadmap.zip. Can someone help?
Here's the output from the log right before it closes:
Using RoboHelp HTML (RH9) with Windows 7, 64-bit.
Thanks,
Todd

Jeff, thanks for the feedback. I figured out what was happening and do believe it is a bug.
Since printing from AIR looks awful, we were generating individual PDFs for each chapter in our project, then including hyperlinks to those PDFs in our AIR project (via the file: type hyperlink).
Steps would be:
1) Create the Individual chapter PDFs.
2) Create the AIR, which would link to the latest version of the PDFs.
This works fine initially (works like a charm in fact). However, if I would update a topic and re-build the PDF files, that's what would introduce the problem. After the PDF files were updated, building the AIR output caused RoboHelp to close. The PDF files themselves did not change file names or directory locations--just the content of the PDF was updated.
This is a bug that should be fixed, since this is the only viable solution I've found to circumventing the terrible printing from AIR.

Adobe AIR for Video Wall project - the right tool?

I need to decide whether Adobe AIR is the right tool for a Video Wall project. The Video wall would be one of only 4 installations.
It would need good offline capability.
The application would play back both canned video as well as twitter feeds.
The other option is to go all HTML with perhaps the Canvas element to display video, graphics.
I'm biased towards using Flash, AIR but am open to new ideas.
What are the pros, cons of each approach?

Pros of the Adobe route would be a little more control and reliability. You can easily go fullscreen, preload other videos easily in the background and display them on the hardware GPU decoded StageVideo (with the right video card, almost all of them at this point). Twitter feed loading would have some robust error handling to assure it goes smoothly but if you need offline capability you'll need some canned material for the feeds in that situation.
HTML can go fullscreen but the caveat would be drawing your twitter feed over the video at that point. Because it's fullscreen I don't believe you can have your text over it from a <video> element but you'd need to use <canvas>'s fullscreen and actually mux the text into the video.
The long haul of Adobe's roadmap clearly states video and games are the future of FP and AIR. I've done tons of kiosks in Flash and AIR, many of which just act as a video wall, attracting people to very large screens. I've had nothing but success doing this. I'd only even approach HTML5 if you have some reason to desire to put this on the web, and even then, Flash is still fine in that situation too.

[AIR 3.0] AIR app crash on attachCamera()

edit:
I'v changed the topic because the App chrashes on the attachCamera() function, not during Camera.getCamera()
Hi,
I'm developing an AIR App using Flash CS4 on windows 7 (64 bit), macbook pro. I catch the built In webcam (iSight...) with Camera.getCamera() and apply it to a Sprite on the stage.
All works fine when I run the app using "control+enter" in Flash CS4.
But when I install the published AIR package and run the standalone AIR app it crashes at Camera.getCamera() videoContainer.attachCamera(camera) and the usual windows error message appears. VideoContainer is a object from the class Video.
any idea?

Chris,
it's a simple call to Camera.names , as pretty most everyone in this post (and many others on the web) reported.
The AIR application just closes. No RTE, no crash report, nothing.
I've found people reporting this issue since 2010. This is a Critical issue, IMHO, and I'm surprised the issue is still out there after being reported for such a long time.
I've logged the bug here: https://bugbase.adobe.com/index.cfm?event=bug&id=3609470
When Adobe changed all it's roadmap for AIR and FP, I lost access to the pre-releases so I can't really pressure the AIR team. Could you do that for me, Chris?
I have asked one of our clients for the dxdiag report:
System Information
Time of this report: 8/8/2013, 14:02:41
Machine name: NT-PT-045
Operating System: Windows 7 Enterprise 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130318-1533)
Language: Portuguese (Regional Setting: Portuguese)
System Manufacturer: CLEVO CO.
System Model: W150HNM/W170HN
BIOS: Default System BIOS
Processor: Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz (4 CPUs), ~2.7GHz
Memory: 8192MB RAM
Available OS Memory: 8100MB RAM
Page File: 7973MB used, 8224MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode
DxDiag Notes
Display Tab 1: No problems found.
Display Tab 2: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Input Tab: No problems found.
DirectX Debug Levels
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)
Display Devices
Card name: Intel(R) HD Graphics 3000
Manufacturer: Intel Corporation
Chip type: Intel(R) HD Graphics Family
DAC type: Internal
Device Key: Enum\PCI\VEN_8086&DEV_0126&SUBSYS_51401558&REV_09
Display Memory: 1696 MB
Dedicated Memory: 64 MB
Shared Memory: 1632 MB
Current Mode: 1600 x 900 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: unknown
Monitor Id: LGD020C
Native Mode: 1600 x 900(p) (59.978Hz)
Output Type: Internal
Driver Name: igdumd64.dll,igd10umd64.dll,igd10umd64.dll,igdumd32,igd10umd32,igd10umd32
Driver File Version: 9.17.0010.2932 (English)
Driver Version: 9.17.10.2932
DDI Version: 10.1
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 12/14/2012 03:42:34, 12615680 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B78E66-4266-11CF-6673-4D71B4C2C435}
Vendor ID: 0x8086
Device ID: 0x0126
SubSys ID: 0x51401558
Revision ID: 0x0009
Driver Strong Name: oem67.inf:Intel.Mfg.NTamd64:iSNBM0:9.17.10.2932:pci\ven_8086&dev_0126
Rank Of Driver: 00E02001
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C
Deinterlace Caps: {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
D3D9 Overlay: Supported
DXVA-HD: Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
Card name: Intel(R) HD Graphics 3000
Manufacturer: Intel Corporation
Chip type: Intel(R) HD Graphics Family
DAC type: Internal
Device Key: Enum\PCI\VEN_8086&DEV_0126&SUBSYS_51401558&REV_09
Display Memory: 1696 MB
Dedicated Memory: 64 MB
Shared Memory: 1632 MB
Current Mode: 1280 x 1024 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: DELL 1708FP
Monitor Id: DEL4023
Native Mode: 1280 x 1024(p) (60.020Hz)
Output Type: HD15
Driver Name: igdumd64.dll,igd10umd64.dll,igd10umd64.dll,igdumd32,igd10umd32,igd10umd32
Driver File Version: 9.17.0010.2932 (English)
Driver Version: 9.17.10.2932
DDI Version: 10.1
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 12/14/2012 03:42:34, 12615680 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B78E66-4266-11CF-6673-4D71B4C2C435}
Vendor ID: 0x8086
Device ID: 0x0126
SubSys ID: 0x51401558
Revision ID: 0x0009
Driver Strong Name: oem67.inf:Intel.Mfg.NTamd64:iSNBM0:9.17.10.2932:pci\ven_8086&dev_0126
Rank Of Driver: 00E02001
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C
Deinterlace Caps: {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
D3D9 Overlay: Supported
DXVA-HD: Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
Sound Devices
Description: Speakers (Realtek High Definition Audio)
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0269&SUBSYS_15585140&REV_1001
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RTKVHD64.sys
Driver Version: 6.00.0001.6233 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 10/29/2010 12:20:54, 2533352 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
Description: Realtek Digital Output (Realtek High Definition Audio)
Default Sound Playback: No
Default Voice Playback: No
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0269&SUBSYS_15585140&REV_1001
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RTKVHD64.sys
Driver Version: 6.00.0001.6233 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 10/29/2010 12:20:54, 2533352 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
Sound Capture Devices
Description: Microphone (Realtek High Definition Audio)
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: RTKVHD64.sys
Driver Version: 6.00.0001.6233 (English)
Driver Attributes: Final Retail
Date and Size: 10/29/2010 12:20:54, 2533352 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF
DirectInput Devices
Device Name: Mouse
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: Keyboard
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: Controller (Wireless Gamepad F710)
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC21F
FF Driver: n/a
Device Name: USB Receiver
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
FF Driver: n/a
Device Name: USB Receiver
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
FF Driver: n/a
Device Name: USB Receiver
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
FF Driver: n/a
Device Name: Cordless Receiver
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
FF Driver: n/a
Device Name: Cordless Receiver
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
FF Driver: n/a
Poll w/ Interrupt: No
---

Is Adobe Air 3.5 compatible with 7 starter ?

Hello,
We recently developped a Webbapp in our company using adobe air.
But, customers using Windows 7 starter are not able to open it.
Could it be link to a compatibility issue between Windows 7 starter and Adobe Air 3.5?
Thanks a lot for your help,
Cordially
Julie

Using the latest AIR build will be beneficial for your app because it usually comes with updates and less bugs. I'm currently using Adobe AIR 3.7 for iOS and Android games and it has not been an issue with development or during runtime.
About the question on AIR 3.5 being compatible with iOS 7, I think it should not be a problem because AIR is backward compatible. However Adobe recently announced some key features on their Flash Player and Adobe AIR roadmap (with no definate release dates), and one of them does include support for iOS 7.
Mariam

I am really touched to see Air 2.6... but dear Adobe...

Question #1
This 2.6 brought so many amazing features into packager, it will be really cool if Adobe can hint about it earlier! Can Adobe shares with all the fans what are their roadmaps or priorities when they are improving the product? No obligation, we wont blame Adobe if the team delayed it, some hints on what the Adobe team is working on in the next version can save many lives. Is this a mission impossible?
For example, is Adobe working on native video player support? Or the team has met obstacles so that it is technically not feasible? Dun be shy to tell us -_-
Question #2
I have stopped monitoring this forum for quite awhile, but i remember when i was relatively active here, official responses in this forum is almost negligible - actually i cant remember i see any staff response. In contrast, when i joined the Adobe Digital Publishing Tool forum, staff responses is EVERYWHERE, questions are answered there... overhere it looks like a bunch of fans holding each other's hand and trying to save each other... my question is, should there be an official voice here?
hellloo..... any staff hear me me me me me (echo...............).

I agree on both of Terrence's points. No doubt, there are some seriously helpful people in these forums (Colin especially), but we're collectively navigating a jungle. It feels like Adobe's putting in the effort to make AIR/Android-/iOS-deployment work well, but if us devs have so much trouble figuring out all the large-scale and small-scale mechanics, it's (a) frustrating, and (b) time-consuming, and (c) giving me the feeling that I am missing a lot of possibilities / best practices.
At the very least, could Adobe please dedicate a half a day a week of an employee's time to charge through here and answer the big headaches?
I'd love to know if native video support is on the roadmap. It'd be great to switch my answer to clients / employer from "I can't make the video perform anywhere near as well as a native Obj-C program" to "it looks like that may be solved in the near future." I'm getting a lot of pressure to drop Flash because it's "not as good," though personally I believe the platform will get there and continue to be the best choice for multiscreen deployment.
It's great to read blog posts after you come out with something, but.. the more we know what's ahead, the better we can plan. (how about WebOS? Any intention there?)

Analytics For Adobe AIR

Hello all,
We have recently lauched a AIR App entitled "TweetNewz" and we would like to get some analytical data such as engagement, user tracking, etc. We are aware that Google Analytics has AIR integration on their roadmap, but are there any solutions that currently work?
Thanks,
Ryan

Hey Ryan,
I just attended a WebTrends webcast a few weeks ago regarding tracking flash files using their dcMultiTrack script. You (or your client) will need a WebTrends accounts which can be very costly but they even walk you through creating an ActionScript file for the purposes of tracking clicks within the SWF file.
https://webtrendsevents.webex.com/ec0605l/eventcenter/recording/recordAction.do;jsessionid =vxxRKqGRvGwJ2yp3zXns33t1hwrn2JVyWl75mT2X1R6vjlcvLw9g!1458672443?theAction=poprecord&actna me=/eventcenter/frame/g.do&apiname=lsr.php&renewticket=0&renewticket=0&actappname=ec0605l& entappname=url0107l&needFilter=false&&isurlact=true&entactname=/nbrRecordingURL.do&rID=151 5422&rKey=a90ac2b1a9e8480d&recordID=1515422&rnd=1730811328&siteurl=webtrendsevents&SP=EC&A T=pb&format=short
I haven't yet had time to try this out in AIR for a client who has a WebTrends account. I'll get back when I do - however, thought this might be of some use. WebTrends is definitely an Enterprise solution, but one that is extremely flexible and powerful.
I'm toying with keeping some simple stats stored in the apps local SQLite database when the user is not connected to a network in order to send those stats when they are connected. What does the community think of that idea?
Regards,
Jason
NWM

Is AIR 3.5 compatible with iOS 7?

title says it all

Using the latest AIR build will be beneficial for your app because it usually comes with updates and less bugs. I'm currently using Adobe AIR 3.7 for iOS and Android games and it has not been an issue with development or during runtime.
About the question on AIR 3.5 being compatible with iOS 7, I think it should not be a problem because AIR is backward compatible. However Adobe recently announced some key features on their Flash Player and Adobe AIR roadmap (with no definate release dates), and one of them does include support for iOS 7.
Mariam

The Future of AIR for Mobile.... ? Uncertain?

Just wondering what everyone elses thoughts are on this. There's a lot of chatter going on about this.
Looking at Adobe's roadmap for Flash ( http://www.adobe.com/devnet/flashplatform/whitepapers/roadmap.html )
ActionScript "Next" development has been cancelled
Flash Player "Next" development has been cancelled
AIR for Windows 8 "Modern UI" has been cancelled
Kevin Lynch (Adobe CTO) has left Adobe to go to Apple ( didnt see that one coming )
The thing I don't get about Adobe is how they are pimping out that AIR be used only for gaming. You don't ever hear them say that AIR is a great platform for developing Multiplatform Mobile Apps.... which it is! I would argue its the best simply because of how easy it is to develop multi-platform apps with ease.
I work in corporate marketing in a billion dollar+ company and I'm using AIR for mobile apps and it's awesome!
Now looking at my own personal roadmap moving forward... do I want to keep AIR on the radar ?
I've also built apps using PhoneGap, etc.. and its a nightmare. It's tedius, performance is mediocre. I really felt that AIR was moving in the right direction.
I'm going to Adobe MAX in May.. I'm hoping that they announce something enlightening.
What are your thoughts ?

I think opposite. I think Adobe is failing to see what a potential it is. I agree with all of your points about how great Flash Pro is to work in. I just created a game for an arcade cabinet, iPhone, iPad, Android & BB10 all in a single build. That's pretty amazing.
However I think the writing is on the wall at this point.
ActionScript4 "Next" development has been cancelled
Flash Player "Next" development has been cancelled
AIR for Windows 8 "Modern UI" has been cancelled
These 3 are huge.
Also Adobe's CTO and biggest advocate for Flash leaves Adobe to go to Apple.
Adobe is betting on HTML5. I hope that in the future Adobe releases a tool like Flash Pro that does everything the same except uses JavaScript. This would be nice.
It's really confusing to me though .. Adobe says "To build mobile apps use PhoneGap" .. but to build mobile games use AIR.
Why not promote how powerful AIR is at building Mobile Apps?
Adobe MAX this year is going to be very interesting that's for sure.

When will Adobe AIR 2 be out?

Will it be out this year? If so, what major functionality will be introduced? Especially, will it allow an AIR program to launch other programs?
I wish we know more about AIR's roadmap so we can make decisions on how we will develop our products. Right now it's like a black box and we have to guess what will happen.

As far as I know, the only publicly-announced details about the next major version of AIR are the limited details that Arno Gourdol (Engineering manager for AIR) shared at "Flash Camp" in San Francisco last May.
I summarized the announcements in a blog post:
"New features in the next Adobe AIR 'Athena'"
You can also watch the video of his entire presentation on Adobe Labs:
"FlashCamp San Francisco: Update on Adobe AIR"
Admittedly there aren't many new features described/shown, and one of the features has actually already shipped in the dot release (1.5.2) that came out a couple of weeks ago.

Air 3.6 Roadmap?

Similar Messages

Maybe you are looking for