2 monthes since last version
-
- KVRian
- 830 posts since 13 Oct, 2003
because i can't think of a reason mackie would hold up bug fixes, i must come to the conclusion, that jules isn't putting all his workingtime into tracktion anymore. maby he has another project running because tracktion doesn't make enough money. please proof me wrong anybody or tell me other reasons for that.
i need a lunch break
-
- KVRAF
- 1615 posts since 28 Mar, 2005
on Jules' website he says he's working on some secret projects. And he seems to do a lot of work on JUCE too. Hopefully Mackie can afford a programmer to help out.
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
This post is simple speculative trolling. It's annoying. And the source is no surprise, either. 2 months? Are you ill?
-
- KVRAF
- 1617 posts since 2 Dec, 2003
well there's soundbasket, juce, and who knows what all else. he's a busy guyaldi wrote:i must come to the conclusion, that jules isn't putting all his workingtime into tracktion anymore.
-
- KVRAF
- 2750 posts since 2 Feb, 2005 from Raincoast of Grayland
Yeah, we only want certified trolling with all the proper credentials. 
perception: the stuff reality is made of.
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
But is it really... or is that just what it says when it loads up? 
In any case, I can assure you that it's being worked on, if that's what you twuwy need.
In any case, I can assure you that it's being worked on, if that's what you twuwy need.-
- KVRAF
- 26984 posts since 3 Feb, 2005 from in the wilds
It may be that it will be different that it has been. My impression (since I am new to this forum) is that Tracktion was having regular updates and more direct feedback with the developer (Jules). That is common with software developed by one person.
Now it is under the auspices of Mackie and it may be more along the usual lines of software development from larger companies. (There are exceptions so it may stay more like it was) That appears to be the case, so some users may feel frustrated with such changes cause it is nice to feel more directly in contact with development and feel like one has some influence over ones tools of choice.
Now it is under the auspices of Mackie and it may be more along the usual lines of software development from larger companies. (There are exceptions so it may stay more like it was) That appears to be the case, so some users may feel frustrated with such changes cause it is nice to feel more directly in contact with development and feel like one has some influence over ones tools of choice.
-
- KVRAF
- 2009 posts since 9 Apr, 2003 from Cornwall, UK
'We want bug fixes, we want bug fixes, we want bug fixes"
[all chant]
[all chant]
-
- KVRAF
- 16154 posts since 2 Dec, 2003 from Nashville, TN
Jules has been working on Soundbasket and his "secret" project for a long time now. That's been on the website forever. So I doubt that he's just not really working with Tracktion right now. It wouldn't make sense to do that with a new deal with Mackie, just develop version 2 and leave it for a while.
I have always defended the fact that Jules is the one and only developer here. However, I do agree that it would be really helpful IMO to add a second one or maybe even a third. Not to program the app itself. I think Jules should be SOLELY responsible for workflow, etc, and even what gets added. But I think it would be nice to have another dev or two that would just focus on things like algorithms, improving the sampler, stuff like that. Just little chunks of code within the project, but not the project itself. I think that if that happens, we would truly see some good times. However, the more devs you get, the more cost you may be creating for future versions. But who knows, maybe there is a way to get things going like that.
Koolkeys
I have always defended the fact that Jules is the one and only developer here. However, I do agree that it would be really helpful IMO to add a second one or maybe even a third. Not to program the app itself. I think Jules should be SOLELY responsible for workflow, etc, and even what gets added. But I think it would be nice to have another dev or two that would just focus on things like algorithms, improving the sampler, stuff like that. Just little chunks of code within the project, but not the project itself. I think that if that happens, we would truly see some good times. However, the more devs you get, the more cost you may be creating for future versions. But who knows, maybe there is a way to get things going like that.
Koolkeys
My host is better than your host
-
- KVRist
- 317 posts since 13 Mar, 2003 from San Diego
pdxindy wrote:It may be that it will be different that it has been. My impression (since I am new to this forum) is that Tracktion was having regular updates and more direct feedback with the developer (Jules). That is common with software developed by one person.
Now it is under the auspices of Mackie and it may be more along the usual lines of software development from larger companies. (There are exceptions so it may stay more like it was) That appears to be the case, so some users may feel frustrated with such changes cause it is nice to feel more directly in contact with development and feel like one has some influence over ones tools of choice.
I agree,
it is funny that the 'one man show' software companies can update their software on a near daily basis if wanted, yet the bigger the company, the longer you wait. You would think it would be the opposite. I don't think T2 is any more complicated than T1, in that a few fixes could be delt with in the same timely fasion as when Jules was solo. He used to have them up within 24 hours. I guess we were spoiled.
Lance
-
- KVRAF
- 2427 posts since 13 Sep, 2004
Jules may have actually sent Mackie fifteen updates, We dont know.
If he was updating on a daily basis then mackie wouldn't release them all it just wouldn't make sense, Too many downloads and so on, When a bugfix version is stable it will be released but this will have spent at least a couple of weeks at mackie being checked i suspect.
The hey days of Jules updating daily was to be honest an easy way to build a good reputation with users and has stood him well, Jules no longer needs to do this and Bug fixes will be fewer i suspect, T2 is just in need of a few small tweaks to make it very nice indeed ($20
)
If he was updating on a daily basis then mackie wouldn't release them all it just wouldn't make sense, Too many downloads and so on, When a bugfix version is stable it will be released but this will have spent at least a couple of weeks at mackie being checked i suspect.
The hey days of Jules updating daily was to be honest an easy way to build a good reputation with users and has stood him well, Jules no longer needs to do this and Bug fixes will be fewer i suspect, T2 is just in need of a few small tweaks to make it very nice indeed ($20
)Omerta
-
- KVRAF
- 16154 posts since 2 Dec, 2003 from Nashville, TN
I agree that upgrades COULD probably still come quick. However, there are a couple problems.
Back in the day when this DID happen, an update would be released, but almost immediately someone would find something not working quite right, and not even an hour or two later Jules had another update available. Yeah, it sounds great, but for a big company like Mackie, it just would not make sense to do this. For the most "professional" image, you want to only release fairly stable versions. Before, it didn't matter as much. But now, as the user base has gotten much larger, it would be a mess just releasing every fix that was made right away. Instead, there needs to be testing. So it just won't work the same way any more. It's nobody's fault, just the way it goes when your product grows to a particular size.
I will agree on one thing. It would be nice to have an idea of what is planned for the initial bug fix release or whatever, so that we don't waste many posts on things that we aren't sure are being addressed. Then we can know what is being worked on. Not even a time frame is needed, just a word on what is being planned.
Koolkeys
Back in the day when this DID happen, an update would be released, but almost immediately someone would find something not working quite right, and not even an hour or two later Jules had another update available. Yeah, it sounds great, but for a big company like Mackie, it just would not make sense to do this. For the most "professional" image, you want to only release fairly stable versions. Before, it didn't matter as much. But now, as the user base has gotten much larger, it would be a mess just releasing every fix that was made right away. Instead, there needs to be testing. So it just won't work the same way any more. It's nobody's fault, just the way it goes when your product grows to a particular size.
I will agree on one thing. It would be nice to have an idea of what is planned for the initial bug fix release or whatever, so that we don't waste many posts on things that we aren't sure are being addressed. Then we can know what is being worked on. Not even a time frame is needed, just a word on what is being planned.
Koolkeys
My host is better than your host
-
- KVRian
- 1222 posts since 6 Jul, 2004
Well, in many cases that would entail releasing a "whoops" +0.01 update the week after a product hits the shelves, just to make it will work at all on 50% of the hardware base...pdxindy wrote:Now it is under the auspices of Mackie and it may be more along the usual lines of software development from larger companies.
-
- KVRist
- 246 posts since 13 Apr, 2004 from Hertfordshire, UK
I can understand why that wouldn't happen, it would simply start the Groundhogging speculation immediately. Whilst hoping there's a fix-pack out soon, I totally accept the radio silence as a feature of T moving on.koolkeys wrote:I will agree on one thing. It would be nice to have an idea of what is planned for the initial bug fix release or whatever, so that we don't waste many posts on things that we aren't sure are being addressed. Then we can know what is being worked on. Not even a time frame is needed, just a word on what is being planned.
Koolkeys