Pro Tools has become a nightmare (Windows)

[TNM]

Originally Posted by grayter1

Not to hijack the thread, but are you running the UAD's on your PC? I'm looking to get 1 or 2 cards for my Windows rig and what to know how they run.

tg

they are running in bootcamp on the imac pro in my sig, using components that are not supported from UA at all (bootcamp for one, the apple thunderbolt 2 to 3 adapter for another). I put it down to the proper implementation of thunderbolt 3 on the hardware side from apple which makes it work so well. I am getting better performance at 32 buffer in windows on the very same imac pro than OSX, using the very same chain of UA devices on the very same thunderbolt ports and thunderbolt adapters.. I even recommend macs to people who want to run windows and UA thunderbolt devices now. The DPC latency is astounding and better than any result I have seen on native windows builds.. (it's just one green segment down the whole latencymon page, its incredible). It must just be the really high quality motherboard components apple are using on their pro line, it has to be. PS the reason windows is performing better is because there is no speed-stepping when i activate windows high performance power plan, i.e, all 8 cores stay at the maximum intel rated turbo speed at all times without any fluctuation.When the Catalina pro mode comes out, this should neutralise that issue on OSX once and for all, IF they offer it to imac pro owners as well.
You can PM me for any other info rather than going more OT here. PT runs like a dream in bootcamp on the imac pro in any case.

[TNM]

Originally Posted by atticmike

Well I'm running PT Ultimate natively without cards through Lynx Aurora USB ports or UAD Apollo via Thunderbolt.

The system is a very compatible 9900k system with 64 Gigabytes of ram and NVME drives with 3000mb read and write speeds.

W10 is also the latest version but PT is very finicky lately.

Gesendet von meinem SM-G965F mit Tapatalk

That's not even close to everything i asked.. so.. I asked if it passes latencymon DPC latency tests which is THE most crucial element on any windows machine for good DAW performance. It could also be a faulty plugin that is causing spiking which I also tried to say.. how can it work here perfectly? That means there is something on your end that is bothering it, and I was trying to help you narrow that down.

"a 9900K very compatible system" means nothing. Apollos are known to have issues with MANY windows systems and it entirely depends on the motherboard.. the gigabyte designare with built in thunderbolt is known to be a good one, for example.

[cwsand]

Originally Posted by thebeatless

#2: Learning new key commands hasn't been fun. I've been using Pro tools on macs since the late 90's, and I'm definitely fumbling around some to find the right key combinations occasionally.

I ran into the exact same issue. I found this little registry editor called SharpKeys that allows keys in Windows to act like other keys. I just remapped the Ctrl, Windows and Alt keys to behave like a Mac keyboard and now I can go back and forth between computers a lot more easily.

[TNM]

Originally Posted by cwsand

I ran into the exact same issue. I found this little registry editor called SharpKeys that allows keys in Windows to act like other keys. I just remapped the Ctrl, Windows and Alt keys to behave like a Mac keyboard and now I can go back and forth between computers a lot more easily.

Thanks for the heads up, as that has been a real issue for me when using bootcamp with the mac keyboard.. the only real complaint I have had.

I am also trying to find an EASY way to create my own PT custom shortcuts in bootcamp like I do in OSX to no avail so I keep on trying to do the shortcuts when i am working in Windows and they do nothing LOL. I must do it 100 times a day or more, as all the custom powerclaw shortcuts I created are ingrained in my memory.

[seanmccoy]

Originally Posted by thebeatless

#2: Learning new key commands hasn't been fun. I've been using Pro tools on macs since the late 90's, and I'm definitely fumbling around some to find the right key combinations occasionally.

Originally Posted by cwsand

I ran into the exact same issue. I found this little registry editor called SharpKeys that allows keys in Windows to act like other keys. I just remapped the Ctrl, Windows and Alt keys to behave like a Mac keyboard and now I can go back and forth between computers a lot more easily.

Originally Posted by TNM

Thanks for the heads up, as that has been a real issue for me when using bootcamp with the mac keyboard.. the only real complaint I have had.

I am also trying to find an EASY way to create my own PT custom shortcuts in bootcamp like I do in OSX to no avail so I keep on trying to do the shortcuts when i am working in Windows and they do nothing LOL. I must do it 100 times a day or more, as all the custom powerclaw shortcuts I created are ingrained in my memory.

This is all quite the brain-twister, huh? Between running PT on my PC and on my Macbook Pro (with the smaller keyboard), and Logic on my Mac Pro, where I've been gradually changing all the key commands to match PT on my PC, I think I'm developing a stutter.

[TOM@METRO]

Crashes and errors have been extremely rare here on Windows. I run many long days without a glitch.

(HDX without Hyperthreading. Fully optimized.)

[grayter1]

Originally Posted by guitardom

Some interfaces Pro Tools will run, though very badly when the interface is still set in Windows as the the default playback devices. I have seen this fix quite a problem systems.

This was my one and only issue when I moved from Mac to PC. Core Audio was/is a thing of beauty when it comes to system vs interface sounds/priority. Once I switched the system sounds to run through the MB, it was smooth sailing.

tg

[TNM]

Originally Posted by grayter1

This was my one and only issue when I moved from Mac to PC. Core Audio was/is a thing of beauty when it comes to system vs interface sounds/priority. Once I switched the system sounds to run through the MB, it was smooth sailing.

tg

yep, i set the windows audio interface to the imac pro's. They are great for watching movies or gaming anyway, no issue at all. Apollos are only used via asio. I do know the UA WDM driver is broken, so *everyone* with a windows system should be using motherboard audio for system sounds/youtube etc ANYWAY. Apparently UA have even confirmed it now that the WDM driver is a joke in it's current state.

[TNM]

Originally Posted by TOM@METRO

Crashes and errors have been extremely rare here on Windows. I run many long days without a glitch.

(HDX without Hyperthreading. Fully optimized.)

I really need to ask... why no hyperthreading on just a 6 core? Why disable it?

[basehead617]

Originally Posted by TNM

Thanks for the heads up, as that has been a real issue for me when using bootcamp with the mac keyboard.. the only real complaint I have had.

I am also trying to find an EASY way to create my own PT custom shortcuts in bootcamp like I do in OSX to no avail so I keep on trying to do the shortcuts when i am working in Windows and they do nothing LOL. I must do it 100 times a day or more, as all the custom powerclaw shortcuts I created are ingrained in my memory.

BTW.. I have had a terrible time in bootcamp win10 on my mac book pro with much worse audio app/driver performance than in macOS. But my MBP is a few years old and not a newer one. So it depends..