- #SOUND SIPHON QUICKTIME SOFTWARE#
- #SOUND SIPHON QUICKTIME CODE#
- #SOUND SIPHON QUICKTIME MAC#
- #SOUND SIPHON QUICKTIME WINDOWS#
Because I sit in it all day staring at the mighty clone. Sure, there's a browser on it, but it sits in the corner, and when I need to work, which is all day, every day, I go over there and work. And dang, if the whole thing wasn't cheap. I just finished building a silent tower workstation with 14 swapable drives, an overclocked six core cpu (for 12 ht cores), SSD boot drive. No 99,999 proggies all running services in the background. There's also no reason to have your "computer" be the same as your workstation, and, indeed, a lot of reasons not to.
#SOUND SIPHON QUICKTIME WINDOWS#
Many of my colleagues have macs and boot into windows for editing-problem solved. No reason not to have a dual boot machine, either, if you just want to have a Mac. Because I'm not running Mac, I'm not running PC, I'm running Adobe.
No matter, I would switch over, and if it went the other way, I would switch back.
#SOUND SIPHON QUICKTIME MAC#
First in line at the mac store, at the genius bar which is characterized by a complete lack of geniuses of any variety. If the mac were cheaper, faster and more reliable, I would switch over. I don't really care which computer I use, and for me there is really no difference, but if I was building a workstation, I would build a windows machine for my audio and video because it will be cheaper, faster and more reliable. Sure, there may be a fix but you might spend a month trying to find it.
Sometimes when you have an awful bug you just need to swap out your hardware until it goes away. They've got most but not all of those issues fixed judging by forum posts. some had issues but they could find a work-around, and some basically puked. SOME Mac's with the oft-affected cards worked fine. and for a bit they had a hell of a time as Apple wasn't particularly interested in helping with the problem.
#SOUND SIPHON QUICKTIME SOFTWARE#
The problems came about because of changes in the OS software that hadn't been "shipped" to Adobe to know about. Like when Mac just released their latest OS, which caused a lot (but certainly not all) Mac users with AJA, Kona, & Blackmagic & high-end Nvidia (especially Quadro's) video cards to have mega-issues, which they were demanding that Adobe fix. Not because Adobe's ignoring the problem, but because they can't guarantee a fix. So sadly, you might need to consider switching software. and as yes, it's been a long-time hanger-on issue for some, no one can guarantee a fix. So all this is to say it's a huge bummer for those like you that have one or several of the problem "childs" on your computer. And when they've found one bit that they can isolate, it's frequently been a very "local" issue that only appears with the right mix of several different (and some very puzzling) factors.
#SOUND SIPHON QUICKTIME CODE#
If you can't replicate, you can't isolate the code or other issues to fix. This is why they've frequently asked for complete log reports & that sort of thing, including wanting to remote-task with users with the problem as most of the time NONE of their 'staff' computers can be even caused to develop this. Very few (proportionally) computers have this problem. And as noted by several above posts in this thread, they're not having the issues, or have had it intermittently and or had it go away. This is apparently something that's a mix of hardware/combinations, codecs/combinations, and which Tuesday your mother's aunt washed her clothes. They've constantly tried to fix whatever things they can find that can be fixed. Yes, "a few" can be several hundred in the kinds of numbers they are talking about. as the staffers on the Adobe forums (who, btw, participate there on their own time as that is a useruser forum) have acknowledged over and over.
Adobe is clearly quite aware that a few out of the several thousand users have the problem.
0 kommentar(er)
