Harmon is a freaking joke. They still have no responded to ANY of our emails yet we paid them the enterprise license fee. Freaking mind blowing how much they botched this up. We managed to grab the OSX 31 SDK off the damn way back when machine since it's no longer published anywhere but there is a known bug on OSX that is killing us on that one. ~ JT
-----Original Message----- From: Gustavo Aquino <gustyaqu...@gmail.com> Sent: Thursday, January 14, 2021 7:02 AM To: users@flex.apache.org Subject: Re: Air SDK 33.1 F4M audio broken Hello friends, I'm sorry to barge in so delicate matter, just wanted to raise my voice on this. My apps don't require complex components as audio decoders, but we are all in a terrible situation nonetheless. I can't stop wondering what else is broken. I definitively fear for the future of Air while hoping Harman can continue working on fixing it. Gustavo Aquino Mantovani On Wed, Jan 13, 2021 at 7:44 PM Ramazan Ergüder Bekrek <e.bek...@yandex.com> wrote: > My advice is stick to AIR31 where everything worked just fine. All the > rest is broken since it is in Hartmanns hand thing just kept breaking. > Harmann are I think not well suited to take over the AIR SDK. > > That's why I am not going to make any more updates after AIR 31. > > 12.01.2021, 14:19, "Ramazan Ergüder Bekrek" <e.bek...@yandex.com>: > > My advice is stick to AIR31 where everything worked just fine. All > > the > rest is broken since it is in Hartmanns hand thing just kept breaking. > > > > 05:36, January 12, 2021, Jason Taylor <jtay...@dedoose.com>: > >> Meanwhile I have reached out to adobe.supp...@harman.com many times > with 0 response despite a enterprise license. This is an absolute shit show. > >> > >> -----Original Message----- > >> From: Jason Taylor <jtay...@dedoose.com> > >> Sent: Monday, January 11, 2021 2:58 PM > >> To: users@flex.apache.org > >> Subject: RE: Air SDK 33.1 F4M audio broken > >> > >> Hi Andrew, while 32 appears to actually work in Big Sur, 32 does > >> not > play audio/video from our f4m's encoded in h264 as well. Asking us to > reencode our entire library to VP6 is ridiculous. > >> > >> ~ JT > >> > >> -----Original Message----- > >> From: Frost, Andrew <andrew.fr...@harman.com.INVALID> > >> Sent: Friday, January 8, 2021 3:57 PM > >> To: users@flex.apache.org > >> Subject: RE: Air SDK 33.1 F4M audio broken > >> > >> I would echo this: it should be possible to continue to use AIR 32, > >> we > are aware of a number of companies that are still distributing their > apps using AIR 32 on Big Sur. If you use the ADT with options to > create a 'bundle', you can get this packaged up, sign and notarise it > for distribution. > >> > >> Internal codecs are Sorenson Spark or On2 VP6 for video, and Speex > >> or > MP3 for audio - i.e. the FLV formats. > >> > >> thanks > >> > >> -----Original Message----- > >> From: Alex Harui <aha...@adobe.com.INVALID> > >> Sent: 08 January 2021 21:31 > >> To: users@flex.apache.org; 'Frost, Andrew' > <andrew.fr...@harman.com.INVALID>; andrew.fr...@harmon.com > >> Subject: [EXTERNAL] Re: Air SDK 33.1 F4M audio broken > >> > >> CAUTION: This email originated from outside of the organization. Do > >> not > click links or open attachments unless you recognize the sender. > Please report any suspicious content by using the "Report Email" tool. > >> > >> Can you roll back to 32? > >> > >> On 1/8/21, 1:28 PM, "Jason Taylor" <jtay...@dedoose.com> wrote: > >> > >> Hello Harmon? Can anybody answer any of these questions please? > >> FFS > I'll pay dearly. Our company is dead in the water on OSX atm. > >> ~ JT > >> > >> -----Original Message----- > >> From: Jason Taylor <jtay...@dedoose.com> > >> Sent: Thursday, January 7, 2021 2:02 PM > >> To: users@flex.apache.org; 'Carlos Rovira' > >> <carlosrov...@apache.org > > > >> Subject: RE: Air SDK 33.1 F4M audio broken > >> > >> Additionally what codec do I need to convert our entire content > base of hundreds of thousands of hours of audio video to so this it > will play in the current SDK, which is our only version that works on > the latest version of OSX? Knowing this I can at least start the > process. I am livid that nowhere in the release notes that I reviewed > mentioned that some A/V no longer works on any version of the harmon > SDK I just paid a boat load of money for. Side note, we now have a > position open for a lead QA at Dedoose as our current one is currently > getting fired. I hope Harmon fires a few people over this debacle as well. > >> > >> ~ JT > >> > >> -----Original Message----- > >> From: Jason Taylor <jtay...@dedoose.com> > >> Sent: Thursday, January 7, 2021 11:05 AM > >> To: users@flex.apache.org; 'Carlos Rovira' > >> <carlosrov...@apache.org > > > >> Subject: RE: Air SDK 33.1 F4M audio broken > >> > >> Hi Andrew, F4M audio video does not work on any version of > >> windows > or mac big sur in the Air 33.1 SDK completely breaking our entire > application and company. You're telling me that your working on it, > were aware of this? Try this line of code in windows on the 33 sdk, > which is the only SDK that works on the newest version of OSX: > >> > >> <s:WindowedApplication xmlns:fx=" > https://clicktime.symantec.com/3AQv1qypuTFqhEaFZxGcLyJ7Vc?u=https%3A%2F%2Fnam04.safelinks.protection.outlook.com%2F%3Furl%3Dhttp%253A%252F%252Fns.adobe.com%252Fmxml%252F2009%26data%3D04%257C01%257Caharui%2540adobe.com%257C9130be11fa71493732b508d8b41c4617%257Cfa7b1b5a7b34438794aed2c178decee1%257C0%257C0%257C637457380820147846%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C1000%26sdata%3D0w%252BZzU4dvB7AJy%252F55JaH4sTh1KR%252FdfvbsofmEaPDIUM%253D%26reserved%3D0"; > xmlns:s="library://ns.adobe.com/flex/spark"> > >> <s:VideoPlayer autoPlay="true" width="100%" height="100%" > id="player" source=" > https://clicktime.symantec.com/36GwFyD134rQ7tMYcvoZLbG7Vc?u=https%3A%2 > F%2Fnam04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F% > 252Fapp.dedoose.com%252FHttpVideo%252F4648d742-d892-4d67-bae8-d7d005b4 > ef48%252FResourceAudioData%252F1cab9c27-73e6-4a1e-a8f7-6c9cabcbc2c6.f4 > m%252522%252F%26data%3D04%257C01%257Caharui%2540adobe.com%257C9130be11 > fa71493732b508d8b41c4617%257Cfa7b1b5a7b34438794aed2c178decee1%257C0%25 > 7C0%257C637457380820147846%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjA > wMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C1000%26sdata > %3DS8NC2HC9bSnDhkfMQhLbAYWLlgxOqYeRDjq6%252FCdznMg%253D%26reserved%3D0 > > > >> </s:WindowedApplication> > >> > >> -----Original Message----- > >> From: Frost, Andrew <andrew.fr...@harman.com.INVALID> > >> Sent: Thursday, January 7, 2021 3:38 AM > >> To: Carlos Rovira <carlosrov...@apache.org>; users@flex.apache.org > >> Subject: Re: Air SDK 33.1 F4M audio broken > >> > >> Thanks Carlos > >> > >> The latest AIR SDK 33.1 implements support for H.264/AAC on > Windows; we’re still working on this for the MacOS side though. The > challenge was that the software codecs used by Adobe in earlier AIR > releases were subject to patent licensing and royalties which are no > longer covered, so we’ve had to remove those. On Windows we can use > capabilities provided via the Media Foundation, although we’re aware > of a few issues existing in this.. We actually want to rework the > entire multimedia area as it’s all very complex internally, so will be > looking at that during the coming year; for the interim period we’re > aiming to just implement decoders within the existing frameworks via these OS > libraries.. > >> > >> thanks > >> > >> Andrew > >> > >> From: Carlos Rovira <carlosrov...@apache.org> > >> Sent: 07 January 2021 08:26 > >> To: users@flex.apache.org > >> Subject: [EXTERNAL] Re: Air SDK 33.1 F4M audio broken > >> > >> CAUTION: This email originated from outside of the > >> organization. Do > not click links or open attachments unless you recognize the sender. > Please report any suspicious content by using the "Report Email" tool. > >> > >> Hi Jason > >> I recommend to add HARMAN word so Andrew Frost is aware. > >> I'll add him in CCO so he is aware of the issue. > >> > >> El jue, 7 ene 2021 a las 1:52, Jason Taylor > >> (<jtay...@dedoose.com > <mailto:jtay...@dedoose.com>>) escribió: > >> As of the 33.1 SDK none of our audio in f4m files is able to > playback. Does anyone have any idea? This is now a critical issue for us. > >> ~ JT > > > > -- > > Sent from Yandex.Mail for mobile >
