MAKE VTOUR (NORMAL) droplet has a limit of panos to process ?

  • Yes, I experienced this issue many times. Seems that it depends on the computer utself and size of the source images. With big amounts of panos I just processed them in several bunches and then just added new panos to the "tour/panos" folder and scenes into the first "tour.xml'.

  • Hi,

    this has nothing to do with the available memory or the size of the images - that's an OS limitation related to the length of an application call.

    For example - when dropping 3 images from the folder 'c:\panos\' on a droplet, then the resulting call of the krpano tools that will be sent to the OS might look like this:

    Code
    c:\path-to-krpano\krpanotools64.exe makepano -config=templates\vtour-multires.config c:\pano\image1.jpg c:\pano\image2.jpg c:\pano\image3.jpg


    and the total length (count of characters) of that call is limited by the OS (the exact limit can differ from OS to OS and OS version to OS version). Once this limit will be exceeded the OS will skip/ignore the call.

    Ways to bypass this limitation can be either using 'shorter paths' to the images or call the krpano tools from command-line and use 'wildcards' for the image selection, then there is no limit for the number of input images.

    E.g. when using the '*.jpg' as input, all jpeg files in the given folder will be used:

    Code
    c:\path-to-krpano\krpanotools64.exe makepano -config=templates\vtour-multires.config c:\pano\*.jpg

    Best regards,
    Klaus

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!