RE: Adobe Air  33 SDK - update and pricing email and PDF  2019-06-20 From email The model of a subscription is one that was strongly suggested on various web forums and from individuals we were in contact with prior to this. The subscription model has a major flaw.(at least as implemented by Adobe). If you need to update an old client application that requires an old version of the product, you are out of luck if the license doesn't let you use the old version. My case: Developed visitor center touch screen applications in 2009 with Flash CS4 Professional (pre-subscription prcing). Am currently working on minor updates. The way we did Arabic text doesn't work under CS5 or CS5.5. To avoid re-write we have to use CS4 which runs mostly okay under Windows 10 (I worked around issues with labels and multiple scenes) and I have to publish the projector on old Vista system from 2009--but it works. With subscription pricing we would not be allowed to use the old software--as was pointed out by a recent Adobe email warning against using older subscription version of Photoshop as their licenses (and hence my license) was no longer active. My customer would not be happy with complete re-write pricing--customer would probably jump ship. This isn't really a complaint, because HARMAN picking up AIR and offering subscription pricing is much much better than no option at all, but for me, I refused to go with subscription pricing for Animate because of fears related to this (I went to AIR/FlashDevelop), and now I am in a situation where had I been required to use subscription pricing in 2009, I wouldn't be able make simple inexpensive updates for my client. If HARMAN can somehow address that issue, that would be great. I really appreciate HARMAN's/Andrew's responsiveness and communications, but for me, and I realize that I am pretty much an oddball, I will have to look at the dwindling non-subscription options. ... View more

Phasor1  wrote : Adding features to desktop is not a priority right now (it is very powerfull as it is). It will be necessary in the future, and  Harman has announced that they will also take care of that part in the future. : I imagine you are correct, but for Windows captive runtime application developers, it would be good to have the ability to debug 64-bit applications as soon as possible. The recent ability to create 64-applications is great to have, but ADT/debugger (I use FlashDevelop) is only 32-bit. You really have to jump through hoops to debug an application that needs to greatly exceed the 32-bit memory limitation. ... View more

Flipline​, thank you for your post. In the forum you referenced I found this excerpt, I believe from an Andrew email, about platforms. In terms of platforms supported, we are just starting off with Android, but are internally now ramping up on iOS as well so we will include that in the SDK later in the year; desktop platforms are slightly less of a priority as Adobe are continuing to support these but they are on the plan for the end of the year. We’ll look into whether there are any changes needed for iPadOS, and – while we can’t yet promise anything – we can also see if it’s viable to bring back a Linux version of AIR. So I take that as there being a quite reasonable possibility that Harman will support Windows in the future. A good bit of information to have while deciding whether I need to jump ship or not. ... View more

@rewb0rn,  Where did you find Harman publishing:      - Continued, long term support for Air on the currently supported platforms I haven't found anything on support for Windows other than Adobe's basic security (limited to security fixes). Thanks, ... View more

So why does it work for me? I created a simple program to list the connected cameras on the stage using FlashDevelop. I created a new project of type: AIR AS3 Projector. I use SDK 32.  I package it as a 64-bit captive runtime application and it runs fine under Windows 10, listing my connected cameras. It runs fine with the adl debugger (32-bit) too. I did run a firmware update on the camera about a year ago using BRIOFWUpdate_2.0.17.exe. I also have used LogiCameraSettings_2.3.117.exe. Let  me know if want any .bat files or want me to try anything. package {     import flash.display.Sprite;     import flash.media.Camera;     import flash.text.TextField;        /**      * ...      * @author BBartonW      */     public class Main extends Sprite     {                public function Main()         {             var textBox            :TextField;               var i                :uint;                        trace("Main Camera names   " + Camera.names);             textBox            = new TextField();             for (i = 0; i < Camera.names.length; i++)             {                 textBox.text    += Camera.names + "\n";             }             stage.addChild(textBox);             stage.color    = 0xbbffbb;         }            }    } ... View more

itlancer, have you solved this yet? A while back I created a 64-bit captive runtime application (similar to a photo booth) that uses a Logitech BRIO camera. Runs on 64 bit Windows 10. That project used AIR SDK 28, but I just built a version using SDK 32.0.0.116 and that worked fine too. I am definitely not an AIR compiler expert, so in your crash output, I don't understand line 08 having "\Versions\1.0\" instead of version 32. ... View more