Re: Big Sur warnings
scott-y6qSm6YX8/[email protected] Wed, 30 Sep 2020 14:26:59 +0200
| Newsgroups | gmane.comp.audio.supercollider.devel |
|---|---|
| Message-ID | <CANmfHJ8Rk6966=BhivydVBcP_bsD-R0fN1XpbRSdwKkRys=A2w@mail.gmail.com> |
--000000000000b9f6a005b087043c Content-Type: text/plain; charset="UTF-8" Current develop builds <http://supercollider.s3.amazonaws.com/builds/supercollider/supercollider/osx/develop-latest.html> work (apart from notarization issues) on the Big Sur drop from a week or two ago. Big Sur support issues that I forsee: - [critical] Supernova needs to switch it's realtime thread setup to use audio workgroups rather than manually scheduling threads via the lower level API's it's using now. This is likely a small engineering change, but will require some pretty extensive testing ... and god forbid we find a problem / performance regression.... Without this change, Supernova may have some degraded performance, or may simply not work. - [minor] Audio Units v2 support on Big Sur has seen some substantial changes (all AU plugins are now run out-of-process, and the thread calling semantics have changed significantly). SuperColliderAU will need to be tested pretty extensively, and may need some changes - though we may be in the clear since we're engine-only and don't implement any proper UI. - [cosmetic] We list QT >= 5.11 as a minimum requirement. No Big Sur fixes will be backported to 5.11, so we'll have to bump to at least 5.12. Big Sur backports *seem* to be a guaranteed part of 5.12 LTS, but it's still worth testing 5.12 to see if it is, in fact, fully supporting Big Sur. Due to some of the Audio Units changes, I predict that Big Sur will have a VERY long tail of work required by audio apps in general. Even more than usual, I think audio users will be staying on Catalina for a long time - so very possibly SC could actually come out ahead of the curve here. On Wed, Sep 30, 2020 at 2:44 AM <[email protected]> wrote: > On Wed, Sep 30, 2020 at 8:28 AM <[email protected]> wrote: > > It did - I sent to both. > > That's good -- I saw only one (with [sc-dev] in the header) and > wondered about it. > > hjh > > _______________________________________________ > sc-dev mailing list > > info (subscription, etc.): > http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx > archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/ > search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/ > --000000000000b9f6a005b087043c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Current <a href=3D"http://supercollider.s3.amazonaws.= com/builds/supercollider/supercollider/osx/develop-latest.html">develop bui= lds</a> work (apart from notarization issues)=C2=A0on the=C2=A0Big Sur drop= from a week or two ago.</div><div><br></div><div>Big Sur support issues th= at I forsee:</div><div><br></div><div>- [critical] Supernova needs to switc= h it's realtime thread setup to use audio workgroups rather than manual= ly scheduling threads via the lower level API's it's using now. Thi= s is likely a small engineering change, but will require some pretty extens= ive testing ... and god forbid we find a problem / performance regression..= .. Without this change, Supernova may have some degraded performance, or ma= y simply not work.</div><div><br></div><div>- [minor] Audio Units v2 suppor= t on Big Sur has seen some substantial changes (all AU plugins are now run = out-of-process, and the thread calling semantics have changed significantly= ). SuperColliderAU will need to be tested pretty extensively, and may need = some changes - though we may be in the clear since we're engine-only an= d don't implement any proper UI.</div><div><br></div><div>- [cosmetic] = We list QT >=3D 5.11 as a minimum requirement. No Big Sur fixes will be = backported to 5.11, so we'll have to bump to at least 5.12. Big Sur bac= kports *seem* to be a guaranteed part of 5.12 LTS, but it's still worth= testing 5.12 to see if it is, in fact, fully supporting Big Sur.</div><div= ><br></div><div>Due to some of the Audio Units changes, I predict that Big = Sur will have a VERY long tail of work required by audio apps in general. E= ven more than usual, I think audio users will be staying=C2=A0on Catalina f= or a long time - so very possibly SC could actually come out ahead of the c= urve here.</div><div><br></div></div><br><div class=3D"gmail_quote"><div di= r=3D"ltr" class=3D"gmail_attr">On Wed, Sep 30, 2020 at 2:44 AM <<a href= =3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>= > wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px = 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-col= or:rgb(204,204,204);padding-left:1ex">On Wed, Sep 30, 2020 at 8:28 AM <<= a href=3D"mailto:[email protected]" target=3D"_blank">josh@realizedsou= nd.net</a>> wrote:<br> > It did - I sent to both.<br> <br> That's good -- I saw only one (with [sc-dev] in the header) and<br> wondered about it.<br> <br> hjh<br> <br> _______________________________________________<br> sc-dev mailing list<br> <br> info (subscription, etc.): <a href=3D"http://www.birmingham.ac.uk/facilitie= s/ea-studios/research/supercollider/mailinglist.aspx" rel=3D"noreferrer" ta= rget=3D"_blank">http://www.birmingham.ac.uk/facilities/ea-studios/research/= supercollider/mailinglist.aspx</a><br> archive: <a href=3D"http://www.listarc.bham.ac.uk/marchives/sc-dev/" rel=3D= "noreferrer" target=3D"_blank">http://www.listarc.bham.ac.uk/marchives/sc-d= ev/</a><br> search: <a href=3D"http://www.listarc.bham.ac.uk/lists/sc-dev/search/" rel= =3D"noreferrer" target=3D"_blank">http://www.listarc.bham.ac.uk/lists/sc-de= v/search/</a><br> </blockquote></div> --000000000000b9f6a005b087043c-- _______________________________________________ sc-dev mailing list info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/ search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/