Re: [hugin-ptx] Re: multiblend - a faster alternative to Enblend (Win x86/x64 binaries and source code) - v0.2 with JPEG support + bugfixes

[Terry Duell]

Hullo Bart,

On Wed, 08 Feb 2012 03:05:44 +1100, Bart van Andel   
wrote:



Hey everybody,

I've downloaded the source files to try and see if I could compile it for
my own purposes. Attached is a modified version (source code) with a  
number of changes compared to David's current version:



[snip]
Code is tested only through the cross-compile build and works fine for  
me.
If anyone is interested I can post the binaries to this list or some  
other place.
Compiling natively on Linux works fine too, but I haven't actually   
blended
anything with it (it does run though). Compiling natively on Windows  
hasn't been tested.


Comments welcome!


It compiles here on Fedora 16 x86_64 using your build.sh.
I have run a simple test blend without any options, and blends OK.
I'll try to do a bit more rigorous testing when I have a bit more time,  
and report if I find any problems.


Thanks for your work on this.

Cheers,
--
Regards,
Terry Duell

--
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: [hugin-ptx] Re: Celeste remove my control points

[Alberto Garcia]

On Monday 06 February 2012 10:49:27 kfj wrote:
> Do you know you can use celeste already when the automatic control
> points are generated? You can tell cpfind to do so, and this is even
> more efficient than doing it later. See

Oh, I did not know the "cpfind", 
I will get an overview , thank you.

-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] Re: multiblend - a faster alternative to Enblend (Win x86/x64 binaries and source code) - v0.2 with JPEG support + bugfixes

[Bart van Andel]

Oh, by the way, when installing mingw-cross-env, it is not required to 
build the whole system (which takes ages). After unpacking the .tar.gz 
archive or "hg clone"ing the system, a mere "make tiff jpeg" should do. 
This will automatically build the dependencies required for libtiff and 
libjpeg (e.g. the compiler itself).

--
Bart

-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] Re: multiblend - a faster alternative to Enblend (Win x86/x64 binaries and source code) - v0.2 with JPEG support + bugfixes

[Bart van Andel]

Hey everybody,

I've downloaded the source files to try and see if I could compile it for 
my own purposes. Attached is a modified version (source code) with a number 
of changes compared to David's current version:

   - The software can now be cross-compiled on a Linux system targeting 
   Win32, using mingw-cross-env (MCE) . 
   This took some effort, because this compiling environment is slightly 
   different from both native Linux and WIN32, e.g. it doesn't come with a 
   memalign-implementation, so I had to import one (not my own code).
   - Source code structure has been restructured slightly: all source code 
   has been moved into a src/ directory.
   - Build script provided (build.sh), capable of building natively, or 
   using MCE, both in release and debug flavors. Binaries will be placed in 
   bin/ directory.
   - Code reformatted. Mixed spaces and tabs were being used, now the code 
   more or less follows the Linux standard with the exception that longer 
   lines were kept. GNU indent was used for this (indent.sh script provided).
   - Most importantly, I needed to be able to provide my own seam masks 
   instead of having multiblend compute one for me. So I've implemented a 
   function to load a PGM mask file. This file should use gray values [0..n-1] 
   corresponding to images 0 to n-1, and have dimensions equal to the input 
   span (may need --nocrop argument to prevent multiblend from modifying the 
   output size; in my case it did). However a function to "unstretch" palettes 
   from [0..255] back to [0..n-1] has also been implemented 
   (--loadseams-unstretch).
   - Mask saving (already present) is now a command line argument 
   (--saveseams). This file can be edited and used again as an input mask. In 
   this case, --loadseams-unstretch is required because the current 
   implementation of saving the seams stretches the palette.
   - I suppose the other functions for saving intermediate files (pyramid 
   for example) could be exposed similarly, but I haven't implemented that 
   (yet).
   - NB: the default behavior hasn't been changed.
   - NB: this is a work in progress, therefore, YMMV when using it.

Code is tested only through the cross-compile build and works fine for me. 
If anyone is interested I can post the binaries to this list or some other 
place.
Compiling natively on Linux works fine too, but I haven't actually blended 
anything with it (it does run though).
Compiling natively on Windows hasn't been tested.

Comments welcome!

@Monkey: Feel free to put this file on your site! What about putting the 
source code on github for example?

-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx


multiblend-v0.2-bart.7z
Description: application/7z-compressed

Re: [hugin-ptx] Re: Attitude in EXIF?

[Carlos Eduardo G. Carvalho (Cartola)]

Uau :) lol! I really didn't realize that! And it has also the gear
reduction as long as I know, so they are in general strong. The only
"problem"/feature that don't allow them to be used to rotate the horizontal
axis is that they only rotate 180º as long as I've seen till now.

I think this one can maybe do the job on the vertical movement:
http://www.dealextreme.com/p/mg996r-metal-gear-digital-torque-servos-with-gears-and-parts-35763

Some of them don't have the specification of kg/cm but instead something
like a "9g" specification like this one:
http://www.dealextreme.com/p/dynam-9g-mini-servo-translucent-black-17988

What does that mean?

Thanks!

Carlos E G Carvalho (Cartola)
http://cartola.org/360



2012/2/7 paul womack 

> Carlos Eduardo G. Carvalho (Cartola) wrote:
>
>> Hi,
>>
>> I am probably going to make a robot tripod head controled by an arduino.
>> I already the arduino and I am going to test some motors soon. Using
>> this kind of thing can't you put some kind of position sensors in the
>> tripod head to get the ypr parameters? I thought about some axial
>> sensor, like some based on resistance or something like that. Don't
>> really know how precise they can be. They could be connected to the same
>> arduino on the robot to register the movement. Another possibility is
>> using step-motors. I also don't know how precise they are, but they do
>> preset known step rotation. I also don't know if they would be strong
>> enough to be used on the arm that moves the camera vertically. I was
>> thinking about using a servo there.
>>
>
> A motor+sensor+feedback combination IS a servo!
>
>  BugBear
>
>
> --
> 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 hugin-ptx@googlegroups.com
> To unsubscribe from this group, send email to hugin-ptx+unsubscribe@**
> googlegroups.com 
> For more options, visit this group at http://groups.google.com/**
> group/hugin-ptx 
>

-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: [hugin-ptx] Re: Attitude in EXIF?

[paul womack]

Carlos Eduardo G. Carvalho (Cartola) wrote:

Hi,

I am probably going to make a robot tripod head controled by an arduino.
I already the arduino and I am going to test some motors soon. Using
this kind of thing can't you put some kind of position sensors in the
tripod head to get the ypr parameters? I thought about some axial
sensor, like some based on resistance or something like that. Don't
really know how precise they can be. They could be connected to the same
arduino on the robot to register the movement. Another possibility is
using step-motors. I also don't know how precise they are, but they do
preset known step rotation. I also don't know if they would be strong
enough to be used on the arm that moves the camera vertically. I was
thinking about using a servo there.


A motor+sensor+feedback combination IS a servo!

 BugBear

--
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx