But quality must be preached to them with enough certainty that they own their mistakes, no matter how much of a hot-shot they are.Īnd even more important than that is ensuring the managers themselves don't adopt too cavalier an attitude regarding bugs they find low-priority and deny the developers the opportunity to fix them. Yes you lose them you lose a year or more, so it's terrifying to challenge them. Most importantly, star developers shouldn't be over-coddled. The source control system should allow for easy branching and merging for agility in applying fixes to released and future versions. Developers should own their bugs rather than relying on second rate maintenance engineers to repair them. A software project manager needs to get everyone to buy into a culture of quality, where the major problems of a release are fixed before work begins on the next, and important bugs that are discovered late are fixed quickly. This is a matter of managerial discipline. Besides, it's more fun to discuss missing features and improved user interface etc. Major bug fixes and stability issues should be fixed before major releases like Logic 10. For now, 16 tracks are ok, because the Beatles also made it with 16 tracks. Sure, I am looking forward to get 64 cores and 254 Gb/s bandwidth bidirectional, protected by the Grand Central and 48 physical in and output with zero latency. I wonder if Apple would be ready to build an "Mac Pro Audio", rack mountable, with DSP, more PCI-e slots, SAS drives. Ordered my first (high quality) analog mixing desk, cause hybrid rocks. Higher quality, higher price, saving some plugin instances. Anyway, for these reasons, to save CPU power and bandwidth, I return after 20 years of virtual studio, to hybrid production. The problem is also that the plugins demand more and more - the more they can get. If we have to stick to the now common architecture that Mac Pro's are built on, we have to wait another 10 years to get the CPU bandwidth that is really needed. Sure, Apple could build an audio oriented architecture without such a bottleneck, but this would mean a partial departure from the normal Office PC architecture. In a native systems all streams, even when they come from DSP boards, need to get into the CPU. The in and output capacity seems to be limited by things like CPU IO bandwidth and cache. The problem of todays native architecture is the in and output capacity and the scalability of the numbers of CPUs (Cores). They could also build it without buying Digidesign, by building a dedicated Audio path, similar to TDM, directly into the Mac. Stability: if Apple would buy Digidesign, they could build the most solid hybrid system. That is the simple truth and if some of you want to convince yourself otherwise, knock yourself out. ALL major apps on the Mac have issues using large libraries and software instruments due to 32 bit limitations and therefore require strategizing and for some of us using a supplementary host like VE Pro or Plogue Bidule. " In fact, not one of them has gone back, period.īut I am sure there are Logic users who switched to Cubase who are not going back also.ĪLL the major native apps have bugs, ALL native rigs are stable/unstable depending on what hardware, third party software, state of the OS on the drive, etc. They all miss certain Cubase features, like its superior folder use, but not one of them has gone back to Cubase because "it was more stable. and btw Notator's "midi overflow" problem was never fixed Asher! hehI did a TV series for 4 years with Notator and never had that problem or heard of it and I belonged to a Notator user's group here in LA.Īnd I personally have helped several Cubase users switch to Logic obver the last few years. Exactly.and I'll add Cubase 5 to the list.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |