Sie sind nicht angemeldet.

Lieber Besucher, herzlich willkommen bei: krpano.com Forum. Falls dies Ihr erster Besuch auf dieser Seite ist, lesen Sie sich bitte die Hilfe durch. Dort wird Ihnen die Bedienung dieser Seite näher erläutert. Darüber hinaus sollten Sie sich registrieren, um alle Funktionen dieser Seite nutzen zu können. Benutzen Sie das Registrierungsformular, um sich zu registrieren oder informieren Sie sich ausführlich über den Registrierungsvorgang. Falls Sie sich bereits zu einem früheren Zeitpunkt registriert haben, können Sie sich hier anmelden.

61

Montag, 18. Januar 2010, 13:21

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

Anfänger

Beiträge: 31

Wohnort: USA

Beruf: Professional Photographer

  • Nachricht senden

62

Dienstag, 26. Januar 2010, 05:00

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

Dienstag, 26. Januar 2010, 10:13

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

Anfänger

Beiträge: 31

Wohnort: USA

Beruf: Professional Photographer

  • Nachricht senden

64

Dienstag, 26. Januar 2010, 15:15

That's what I was missing.
Thanks.

Amedee

Anfänger

Beiträge: 33

Wohnort: Brussels - Belgium

  • Nachricht senden

65

Samstag, 6. Februar 2010, 00:32

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

Dienstag, 9. Februar 2010, 10:07

Hello Everyone,

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

661

67

Dienstag, 9. Februar 2010, 10:36

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

Dienstag, 9. Februar 2010, 10:52


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

Montag, 15. Februar 2010, 21:06

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)


Zitat

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

Montag, 15. Februar 2010, 21:45

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

71

Montag, 15. Februar 2010, 22:15

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

when you put in the HTML

Quellcode

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

Montag, 15. Februar 2010, 22:27

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

74

Montag, 15. Februar 2010, 23:01

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

Anfänger

Beiträge: 31

Wohnort: USA

Beruf: Professional Photographer

  • Nachricht senden

75

Samstag, 20. Februar 2010, 04:56

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

Montag, 22. Februar 2010, 11:27

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