One man doing the coding? How do you know that? I guess I missed a post somewhere...Breakpete wrote:Hmm well, it didn't take much longer than 6 - 8 months. It is one man doing the coding, and I can imagine a lot of it required a substantial overhaul to the original code, such as the new midi.
i err on the side of cliche myself ...Sicklecell666 wrote:profound.pHz wrote:if something flies below your radar its easy to miss ...
slainterob
robTracktion has always been 1 man. When Mackie became involved, we all said, "Hey, get some Mackie people in on the coding to speed stuff up" and were told that RMS products were going to continue being the love and work of one man, Julian Storer.HansM wrote:One man doing the coding? How do you know that? I guess I missed a post somewhere...Breakpete wrote:Hmm well, it didn't take much longer than 6 - 8 months. It is one man doing the coding, and I can imagine a lot of it required a substantial overhaul to the original code, such as the new midi.
--HansM
Totally. I wish more users understood this from a programmer's point of view. It's a fact that the more features you demand of the app, the more time it takes to slot in those features properly and still keep the code clean and the structure of the program coherant. When users demand new features "OMG! I MUST HAVE TIME STRETCHING/PDC/LIVE RECORDING etc. NOW!!! OTHERWISE THIS APP IS A PIECE OF CRAP AND I CAN'T WORK WITH IT!!!" (despite the fact you pay for it on the basis of what it _has_ when you purchase it, not what it on the feature request list...), it means that the programmer must look through the code, look at all the dependencies, see whether it can be implemented. And then users complain when the new release has bugs! No shit! I'm amazed the programmers have time to bug-test before the lions devour it and take it apart.BONES wrote:You can see that pattern with anything - Fruity, ORION and lately even eXT. As the code-base becomes larger and larger and more things become inter-related it takes longer and longer to add things and keep the app stable. There are also fewer and fewer things that can be done easily so everything slows down over time, its just a sign of the maturity of an app. As for the tpic, Traktion seems to me to be getting as much discussion as it ever did.
i did a search on the forum, didn't find anyone mentioning tracktion supports altivec now or T2 in the future- only tracktion adepts saying you don't need altivec or dual processor support "cause it's so effective"...Panda wrote:(not that i don't believe you, i'd like to see it)
Tracktion was a one man project from the start. Jules designed and programmed it. If Mackie hired some more people to help with the code for v2, I guess I must have missed a post.HansM wrote: One man doing the coding? How do you know that? I guess I missed a post somewhere...
ttoz wrote: Did you see the tracktion 2 update list? all that time for THAT? it's appalling, really.
Its Always been altivec optimized. So if you still find it slow blame this guy.Panda wrote:i did a search on the forum, didn't find anyone mentioning tracktion supports altivec now or T2 in the futurePanda wrote:(not that i don't believe you, i'd like to see it)
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026
