That is some weird problems you are having Macker, I have not much I can add as I am not using Big Sur nor LogicPro. Too many tricky hassles with LogicPro and I don't want to move to Big Sur or Monterey for at least a couple more years. Its part of why I am moving on to Digital Performer. I'll spare you my current thoughts and feelings about the 'developers' working on Logic at Apple Park in Cupertino. And that means I've effectively lost many, many hours of work since mid-July on developing older projects and creating new ones. I've done some radical "disinfecting" by deleting all versions of the Logic app later than 10.4.8 from my Big Sur boot volume, and by using Time Machine to restore all my Logic projects from backups done before I updated Logic 10.4.8 and created my Big Sur boot volume. Hence I'm now treating Logic 10.7.1 as if it's malware.įurthermore, if you use a VEPro AU2 workaround multiport Logic template, I strongly suggest you treat it as potentially at risk from Logic 10.7.1. Even worse, if I'm not badly mistaken, the corruption also happens in 10.4.8 projects opened specifically with 10.4.8 and never having been opened in 10.7.1 - while 10.7.1 is merely there lurking in the Applications folder. Moreover, this Environment corruption occurs even after a previously tested and working Logic 10.4.8 project file has been opened in Logic 10.7.1 but never saved in 10.7.1, then subsequently re-opened in Logic 10.4.8. In Big Sur, not only does Logic 10.7.1 not work on half the ports when used with my VEPro AU3 Template, but it also visibly corrupts my previously tested and working constructions in Logic's Environment.
0 kommentar(er)
