- #Iran iraq war fsx missions install
- #Iran iraq war fsx missions update
- #Iran iraq war fsx missions pro
- #Iran iraq war fsx missions software
It's not unusual to have a two or three year lead time on software development, then have a few suits decide overnight to change direction, with the software development getting stopped cold. I once worked on a $1 million dollar project that got cancelled at $750,000 in.Īlso, you have to consider the difference in "lead time" between software development and business decisions. They wouldn't be working on issues if they didn't want to release it.Ĭompanies can sometimes be short sided but to put man-hours toward a goal that the company never desired to achieve is a lesson in futility (as well as wasted man-hours) Woohoo! From where did you get "PT10 isn't dead"?
the point is that PT10 isn't dead and that's encouraging. I don't care if they call it ProTools Extreme 3000 "Macho Man" Randy Savage Edition (feat. In addition to the above, from where did you get "coming soon"?
#Iran iraq war fsx missions update
Might be 10.4.0 or 10.3.10, who knows and who cares, but the update is "coming soon" - that is absolutely great news. This is big news! Actually, he didn't even say there would be a release, so the rest of your post is moot.ĭTS we appreciate your comments however I hope those other issues that you're talking about are not related to tying this 10.4 update to the subscription model plan? In addition to the above, if there were going to be a release, why do you think it would be "10.4"? So there will be a 10.4, it will include a fix for input monitoring in TDM, AND it will include fixes for other issues (which are currently in progress) as well. Which yielded the following "interpretations".(And my comments)
Whats up with that? I'd love to see those issues addressed, rather than crippling functionality in upgrades.ĭigiTechSupt posted: We have actually made good progress on this issue but the release is dependent on other issues that are still in progress.
#Iran iraq war fsx missions pro
10.3.8 was working perfectly for me except for 2 things… every time I open pro tools it runs out of memory while scanning for plugins the first time I open it.(still not fixed in 10.3.9 and the main reason for the install) and even if check the box "do not automatically check for updates" the update manager still pops up and says "this is the most recent version of pro tools" even if it isn't. On a side note, I had the software running properly using my prism orpheus and HD authorization in my home studio for a couple days, so I didn't think there would be an issue when I booted the studio tower from my laptop internal in target disk mode (which I've been doing since 10.3.2). If the software isn't going to be properly tested on certain hardware, shouldn't you include that information with the release? I wouldn't have installed it. Plus I didn't even get time to make a proper pot of espresso before my client showed up ready to track so I was grumpy on top of being annoyed! Obviously, the software hadn't been put through the paces on a TDM rig before it was released.
#Iran iraq war fsx missions install
Really made my night stressful and had to revert to a previous system install to run a session the last night. I can't believe that this type of bug was included in an update. You should note that in order to delete some of these files, you have to "show hidden files":Īlso, in the instructions above, there is a small error:Īre in ~/username/Library/Preferences, NOT ~/Library/Preferences So I followed these instructions very carefully (they're halfway down the page): I also had the error of the Pro Tools logo just flashing for a second before disappearing after trying to uninstall 10.3.9 and then install 10.3.8. I'm using Mavericks, but as soon as I managed to downgrade to 10.3.8, it worked flawlessly, so clearly something broke between the two versions. So it's a real pain when you're trying to bounce down some processed tracks. It's most flakey when the input of the track you're trying to record to is set to a bus. Input monitoring is indeed broken in 10.3.9 Sometimes it works, usually it doesn't.
0 kommentar(er)
