 |
|
|
|
|
|
 |
| ||||||||
 |
 
|
|
|
|
|
|
|
|
|
| ||||||||
|
|
| 
| User list | Rules | You are not logged in.
Enjoy 
Everything described here :
http://en.wiki.autopano.net/Latest_Beta
Offline
What's about bugs (SIFT quality, HDRI color)?
Offline
When do you think a Macintosh version will be available?
Offline
Mac, next week. We needed a little more time to finish it.
Offline
AlexandreJ wrote:
Mac, next week. We needed a little more time to finish it.
Written on 2/16. +7 days for one week, 2/23, pad a bit for good measure - any news?
Again, say "two weeks" or "three months" if you don't think you can deliver, but don't say "next week" and then simply quietly drop it. Basic marketing / customer support.
Offline
True. Sorry about that. The mac was really planned for end of last week, but we get into some trouble here ( unplanned stuff with no link at all with development ).
I should have written something friday, my apologize.
I hope everything will went okay this week and everybody will get the alpha 2 end of this week. If not, I'll promise to write about schedule once a week.
Offline
phototrek wrote:
AlexandreJ wrote:
Mac, next week. We needed a little more time to finish it.
Written on 2/16. +7 days for one week, 2/23, pad a bit for good measure - any news?
Again, say "two weeks" or "three months" if you don't think you can deliver, but don't say "next week" and then simply quietly drop it. Basic marketing / customer support.
I think Alexandre and the APP team make a lot of thing for customer support (MAC, PC or LINUX Version on this forum. Do you think it's more important to have the right release date on the forum, than having a new version with new stufs in it ? 
i think 'next week' = 'very soon', no ?
be patient ! 
Offline
taf wrote:
be patient !
I am very patient, actually. As a Mac user I have to be However, it's a matter of principle. If you give a date, you can expect to be quoted by it. Otherwise, simply use "soon". Or say 2 weeks and then over-deliver. Maybe I am simply biased because I work for a company where this whole "under-promise, over-deliver" when it comes to dealines is key, and if it doesn't work out then some *serious* shit happens to people. Come up with a doable deadline, but then don't even think about moving it. It's all about credibility, really.
Offline
I am delighted to see Autopano continue to progress!
But, like "phototrek," I agree that being vague is better than being wrong when it comes to promises. I have worked in software development environments and I well understand that making accurate predictions can often be nearly impossible. There is a reason that "The Big Boys" habitually target quarters (three month spans) in their announcements.
Not that a small developer needs quite such a wide safety net.
If the developer(s) here hope that something will be done in a week, I urge them to say in public "3 to 8 weeks." If they think (feel confident) that something will be done in a week, I urge them to say in public something like "If all goes well, this may be ready in 2 weeks. But if unforeseen problems come up, it could be as long as 6 weeks or even more."
Then, most important: post a "course correction" update if necessary. Post it early, not at week three when "2" weeks was promised.
If the earliest was said to be "2 weeks," and as you approach 14 days it becomes clear that that will NOT happen... PLEASE TELL US. Even if you've said "2 weeks to 2 months" surely you must know that all us eager people will have marked on their calendar not the 2 month point, but the earlier one!
Thanks.
Last edited by ericob (2007-03-03 06:06:53)
Offline
We try to keep our schedule. There are not so complicated as big company, but sometimes, it can happen that some unplanned delay is added to initial estimation.
Planning and scheduling is really a hard job in software development.
Anyway. Normally, Monday we should release the alpha 2 for Windows, Mac and Linux. If we cannot I'll update the wiki (that's what I already did as we weren't able to release it yesterday, our initial plan).
Offline
pas de panique Alexandre, on reste cools et patients, ne stresses pas !
Offline
Quand on voit la réactivité de l'équipe d'APP et leur devouement/disponobilité, et quand on lit certaines remarques, ca fait un peu halluciner....
Désolé pour le francais, mais j'aurais eu du mal a retranscrire exactement cela en anglais...
Allez les gars, faites votre boulot tranquillement, on attendra...
Offline
J'ai fini par essayer la version 1.3.1 Alpha 1, sur PC. (et pourtant mon PC est bruyant)
Un vrai bon en avant 
J'ai enfin pu refaire des panos avec des trous dans le ciel, super !!
La colorimétrie a vraiment avancé. Le développeur de raw est nettement amélioré.
J'ai aussi été surpris pas la vitesse de correction des couleurs, rendant les essais d'ancres moins frustrant.
J'adore les nouvelles ancres, beaucoup moins de dérapages de couleurs, je sens que je vais refaire des panos dont j'étais pas content.
Merci beaucoup Alexandre, j'attendrai la version Mac corrigée avec impatience
Offline
I have finally tried version 1.3.1 Alpha 1, on a PC.
Really great improvements.
I have been able to remake panos with wholes in the skies, worked great.
Color management is really improved, raw developer also.
I was amazed by the speed of color change switching different anchor options.
I love those new anchors, a lot less color shift than before.
I think I'm going to re-stitch some panos I was not happy with colors.
Thanks a lot Alexandre, I'll wait until the improved Mac version goes out.
Offline
ssprengel wrote:
I have one request:
Please increase the maximum number of control-points in the CP-cleaner options from 100 to something larger, perhaps 500. With an initial detection maximum of 200, it seems wrong to have the CP-cleaner maximum of 100.
Ssprengel... this is not the right forum to post such request...
you have a forum for new feature request.
Offline
