Hoi Harry and all OSX users, Harry van der Wolf wrote: >> Harry van der Wolf wrote: >>> Specific items for OSX: >>> - You cannot use GPU on MacOSX yet >> what is blocking this? >> >> I really don't know. It compiles fine but doesn't run. I already posted > twice a log in the nona-gpu thread [1] but I had no response yet. I miss the > coding skills to see what is going on and to solve it.
oh, sorry, I forgot to answer your question [0] this is an error that many of us experience, also on Linux and Windows. It does not mean that it does not work. It means that it does not work *for you*. It may or may not work for others and we need more tests to know. The problem(s) we are dealing with are likely to be dependent on the combination of nona-gpu code; video card; driver. We need a quantity of tests that only the general public can generate, so please OSX users: do try out GPU stitching. We are likely to see many errors, of which the "Framebuffer incomplete" is one. These will help us understand what combinations of driver/card work; and maybe also to find workaround for those that do not. This is bleeding edge not only for Hugin but also for the hardware and drivers. [0] http://groups.google.com/group/hugin-ptx/msg/1e3d8dd4c963b67a >>> - The images pane now has a setting for the AutoControlPoint creator. >>> However, the new solution is useless for OSX >> >> if the new method is more flexible, why is it useless for OSX? any >> chance to bring this new solution to OSX and simplify code maintenance >> (one solution for all platforms)? >> >> > It is currently useless for OSX as the current implementation does not take > into account that "things" work differently on OSX. > On OSX a bundle expects everything to be inside the bundle available for the > user. Earlier we did this by packaging the CPgenerators inside the bundle. > However, to prevent license problems Ippei developed another solution which > "connects" the CP plugins to the bundle without having to deliver the CP > generator with or inside the bundle. OSX has a "Library/Application Support" > directory structure inside the /Users (home) directory. You can couple > things like templates, plugins, application scripts and so on, to a bundle > without needing to install these on every update of the bundle (Hugin in > this case) itself. > Ippei's solution (OSX's solution) is very elegant in the way that you simply > "install" a plugin. From that moment on the application, Hugin in this > case, automatically knows that it can use it. The disadvantage of Ippei's > implementation is that you can't change parameters which you can with Thomas > solution. (I describe this as an elegant solution. It's an elegant solution > to end users as Apple tries to keep it as simple as possible for the > users, but for developers it is cumbersome). On Linux it has always worked like Ippei's solution (no bundle). And on Windows it is a matter of making different installers, and it will work well with Thomas' solution. > It just would have been > more efficient if Thomas had contacted Ippei and/or me as the OSX solution > could have been combined with Thomas' solution. sure. how did he know to contact you? the basic assumption of those who have never seen Hugin on another platform is that it is *exactly* the same. I recently installed your Hugin bundle on a friend's mac to show him how to use Hugin and I must say that while I recognized the program, many things are different. > W.r.t. my resources: After my "return" on the mac I worked on making the > "post 0.8" Hugin compile again on OSX and fix/update the XCode > project/bundle. Now I'm planning to spend some time again to both ImageFuser > and Avidemux. > I also want to add some small changes to KImageFuser and than leave that one > on low profile. understand. this is all volunteer work and you have been volunteering more than a fair share. I hope that those folks who developed their building skills during your forced OSX absence will step in. If not, the OSX users community will have to live with a delay. Thank you for all of your contributions, Harry! Yuv --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx -~----------~----~----~----~------~----~------~--~---
