You are not logged in.

Dear visitor, welcome to krpano.com Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

61

Monday, January 18th 2010, 1:21pm

Hi,
I'm curious. The krpano.swf in the krpano tools beta 9 package = 106.469 bytes
while the krpano.swf in the krpano beta 8 package = 100.834 bytes

Is this just compression or did you add some new stuff/fixed bugs? Which one is the best to use?
the changes in the filesize are the new features (and bugfixes)

but there are also a lot of optimizations to keep the swf as small as possible,
I'm hunting for every byte! normally without constant code optimizations and
improved swf compression, the swf would be already over 250kb

best regards,
Klaus

myuhanna

Beginner

Posts: 31

Location: USA

Occupation: Professional Photographer

  • Send private message

62

Tuesday, January 26th 2010, 5:00am

License

I'm checking out the beta 9 but I'm getting a "DEMO Krpano" on the screen.
Shouldn't my license i bought for earlier version work with beta 9?
I have krpano.license in the same folder as the generated files.
Please advise.
Thanks

63

Tuesday, January 26th 2010, 10:13am

Hi,
I'm checking out the beta 9 but I'm getting a "DEMO Krpano" on the screen.
Shouldn't my license i bought for earlier version work with beta 9?
I have krpano.license in the same folder as the generated files.
are you maybe using the SINGLESWF droplets?

these droplets are embedding the license into the generated swf,
that means the krpano.license must be also in tools folder during swf generating,
when not - only a DEMO swf will be generated,

best regards,
Klaus

myuhanna

Beginner

Posts: 31

Location: USA

Occupation: Professional Photographer

  • Send private message

64

Tuesday, January 26th 2010, 3:15pm

That's what I was missing.
Thanks.

Amedee

Beginner

Posts: 33

Location: Brussels - Belgium

  • Send private message

65

Saturday, February 6th 2010, 12:32am

Accents in path...

Hi Klaus!

Just hitting a small bug here...

The encrypt part of the kprotect GUI will fail if you have a non-ascii character in the path of the file you want to encrypt (e.g. a directory with an accentuated character in its name).

Not a real problem once you know that, but took some time to understand what was happening...
Phil.

66

Tuesday, February 9th 2010, 10:07am

Hello Everyone,

Noob user here. I am having some trouble with this build. Is there a list of known bugs/issues somewhere?

661

67

Tuesday, February 9th 2010, 10:36am

Hi,
The encrypt part of the kprotect GUI will fail if you have a non-ascii character in the path of the file you want to encrypt (e.g. a directory with an accentuated character in its name).
thanks for this note! should be fixed in the next release.


Noob user here. I am having some trouble with this build. Is there a list of known bugs/issues somewhere?
what troubles do you have?

best regards,
Klaus

68

Tuesday, February 9th 2010, 10:52am


Noob user here. I am having some trouble with this build. Is there a list of known bugs/issues somewhere?
what troubles do you have?


Oh all sorts of things - mainly due to being a noob I think. But I wanted to check if there was a list of bugs before asking for help.

I take it the answer is 'no'. I will post my problems later. Thanks for the quick response.

661

69

Monday, February 15th 2010, 9:06pm

Hi,

there is a new bugfix update for the tools - build 2010-02-15:
- improved/bugfixed memory handling on low memory situations (all systems, but especially Mac and Linux)
- paths bugfixes for embedded files (kprotect)
- license path bugfixes (kprotect)
- maxcubesize speedup (downsampling already during remapping)
- updated and bugfixed viewer (krpano.swf)
- updated html/xml templates (default skin buttons now non-transparent, updated context menu)


Quoted

The encrypt part of the kprotect GUI will fail if you have a non-ascii character in the path of the file you want to encrypt (e.g. a directory with an accentuated character in its name).
sorry, this part is still unfixed - paths with accent or special characters don't work, it's a Mac only issue, I'm still looking for a solution for this...

best regards,
Klaus

70

Monday, February 15th 2010, 9:45pm

Thank's a lot for your fantastic job Klaus *thumbsup*

71

Monday, February 15th 2010, 10:15pm

I think a bug on the new update with the krpano.swf

when you put in the HTML

Source code

1
var so = new SWFObject("../krpano.swf","krpanoSWFObject","100%","100%","9.0.28","#000000");

krpano.swf want to take images on the same path


or %SWFPATH% don't work

72

Monday, February 15th 2010, 10:27pm

Hi,

do you have more informations? (xml? example?)
the %SWFPATH% should be path of the krpano.swf, isn't it in your example?

best regards,
Klaus

73

Monday, February 15th 2010, 10:57pm

With %SWFPATH% don't work

74

Monday, February 15th 2010, 11:01pm

Hi,

thanks, I see now...
I have switched the downloads back to build 2010-01-19 for the moment,
I will get back when fixed,

edit: it should be fixed now, the downloads for build 2010-02-15 are up again...

best regards,
Klaus

myuhanna

Beginner

Posts: 31

Location: USA

Occupation: Professional Photographer

  • Send private message

75

Saturday, February 20th 2010, 4:56am

64bit Tools

Using the 64 bit version of the tools and Thumbnail template. For some reason generating multires pano creates all the tiles just fine and when
viewing the html file the pano is great.

However when using the Thumbnail template(by Shanti) and using loadpano to call the xml file, the pano is being displayed "bowed" ie" fisheye effect.

Please advise.
Thanks

76

Monday, February 22nd 2010, 11:27am

Hi,
However when using the Thumbnail template(by Shanti) and using loadpano to call the xml file, the pano is being displayed "bowed" ie" fisheye effect.
check the xml for - version="1.0.7" - or - fisheye="##",
in the old versions the fisheye effect was enabled by default,

best regards,
Klaus

Rate this thread