That's not good enough for a workstation that has high-end configurations costing over $8K, especially when it's split across two GPUs and not all apps can take advantage of that.Īpple made a bet on how GPU compute would evolve, optimized around that bet, and then got stuck for a while when it turned out they'd bet wrong. It would have been tricky for them to deliver much more GPU compute than a single 1080 Ti, a $700 card. But they didn't have the thermal headroom, with the current design, to do something that was actually compelling. I said this a month ago, and Federighi explicitly confirmed it at the meeting. I tend to give too much detail.They pushed the envelope a little too far on thermals, and ended up with no good options. Meanwhile, I'll have to use the free Audacity for all editing, and I really don't want to do that since I spent so much cash on Pro Tools.Īnd if I'm giving too much info, tell me. It has to be small and portable if external. If I should consider buying some kind of external sound interface, or replacing the internal sound card, and that would likely fix the problem, please let me know. If you need other specs, please tell me how to find the specs, step-by-step. Please see my signature for more specific system specs.
I've tried changing the bytes processing for the playback engine, but that does nothing. If that's true, the problem is likely w/ the asio4all driver. I believe Pro Tools is the only software using the asio4all driver. When I open Pro Tools again, the system cuts off playback audio to everything else except Pro Tools. I have to close Pro Tools in order for the other apps to playback audio. When I keep Pro Tools open and try to use another software, even YouTube on Firefox, playback of audio is impossible. In Pro Tools, I'm forced to use asio4all, as the native sound card does not support 44.1 sample. It's worth mentioning that I believe Audacity and Windows Media Player do not use the same audio driver that Pro Tools uses. That means that the static is not in the edited file and not added while editing. Upon export, however, when I test playback of exported file using simpler software (Audacity Windows Media Player), there's absolutely no static. (FYI, I've got same problem running Premiere Pro.) Maybe system can't communicate w/ Pro Tools software very well. My theory is the system has trouble keeping up w/ playback. I've also installed Quicktime to get support for mp3 exports. Previously, I've had to install asio4all in order to get support for 44.1 samples. For some reason I get random static on playback of simple file w/ 3 tracks. I've got new Windows computer, new install of Pro Tools.
0 kommentar(er)
