Kudos to Avid for 2022.9

[JFreak]

Originally Posted by BobbyDazzler

To answer some observations about the windows side of the coin; Sure there are some new features there and the system is mostly stable at its core, but you aren't getting the same level of service that the MacOS gets.

Pro Tools and Windows has always been like a marriage that should have never happened... enjoy while it works.

[massivekerry]

Originally Posted by JFreak

Pro Tools and Windows has always been like a marriage that should have never happened... enjoy while it works.

Agreed. That was a product of "Hey, Apple is leaving Motorola for Intel chips. We can probably use the SAME MACHINE CODE!"

Plus, Apple wasn't exactly kicking it back then. But the consistency of hardware made for an easier testing a compatibility process.

[audiolex1]

Originally Posted by massivekerry

Agreed. That was a product of "Hey, Apple is leaving Motorola for Intel chips. We can probably use the SAME MACHINE CODE!"

Plus, Apple wasn't exactly kicking it back then. But the consistency of hardware made for an easier testing a compatibility process.

It was actually IBM chips, and it made sense as IBM was way behind Intel at the time.
It was a bit of a growing pain moving to Intel. Silicon isn't so bad though.

[Darryl Ramm]

Originally Posted by audiolex1

It was actually IBM chips, and it made sense as IBM was way behind Intel at the time.
It was a bit of a growing pain moving to Intel. Silicon isn't so bad though.

I'm not following the technical claim of what Apple leaving the MC68000 family for PowerPC has to do with Windows.

Reusing "machine code" has little to do with making ports of software like Pro Tools easier, it's having to deal with whole new OS and library interfaces that create the complexity, and Windows sucked for audio before ASIO was developed by Steinberg. And to help reduce that porting work Pro Tools was ported off of Mac using Altura's Mac2Win graphics compatibility library, and as far as I know still relies on that (but I've not poked around recently). That's the reason you get both the Pro Tools edit and mix windows within a parent window on Windows. Altura immolated long ago and I assume Avid got to maintain that themselves from source.

And the success at the time of PowerPC in Macs was not purely IBM. Yes Power started at IBM, but Apple was extremely smart to bring themselves and Motorola into the three way AIM design/build partnership. Motorola contributed lots to the design and both Motorola and IBM fabed power chips. Ultimately that alliance had problems, and all three individual companies were having serious problems. And Apple again made a smart decision to bail to Intel. I remember laughing at their Power struggles though my (short lived) MIPS R10000 colored glasses at Silicon Graphics. Apple's long term pragmatism and ability to see through architecture changes is super impressive, combined with some lucky timing.

[smurfyou]

But PT was available for Windows years before Apple moved to Intel. It did always seem inferior on Windows, at least until v9.

[nednednerb]

MIPS R10000 colored glasses

[noiseboyuk]

Can’t believe we’re doing the mac/windows thing here. I use PT on both, and it works fine on both. I’m unaware of any operational differences (except that I always get the modifiers wrong for the first hour when switching!)

I don’t feel hard done by as a Windows user. Aux I/O is I think the first thing I’m aware of where there is a functional discrepancy, but I can understand that this is to do with Core Audio so there’s a pretty obvious reason why.

[LDS]

The fact that Windows has two audio interface protocols(?) while MacOS has just one is enough to piss me off every time I need to use a PC... which is pretty regularly, but not for anything Pro Tools related. There are plenty of trade-offs because of it. You can't use DVS in the same way on PC as you can on Mac, for example.

[MIKEROPHONICS]

You can use Source Nexus on a PC and have the same functionality as AUX IO

[ZerglingPhilosophy]

Please Windows 11 aux io next!!