Ich ziehe ein equi. Bild auf das Droplet "MAKE PANO (NORMAL)". Das Ausgangsbild hat das sRGB-Profil (sRGB IEC61966-2.1) eingebettet. Folgende Dateigrößen werden druch krpano erstellt, ich nehme ein erstelltes Würfelbild als Vergleich:
Option "skip" (praktisch ohne Profil): pano_b.jpg - Dateigröße: 957 KB
Option "sRGB": pano_b.jpg - Dateigröße: 1095 KB (hier wird ein sRGB-Profil eingebettet, welches sRGBz heißt)
Option "copy": pano_b.jpg - Dateigröße: 902 KB (hier wird das korrekte Profil weitergereicht)
Komischerweise wird die Dateigröße bei der Option "copy" gegenüber der Option "skip" kleiner und nicht wie von Dir beschrieben größer. Ich finde das wunderbar, denn genau diese Funktion habe ich in den letzten krpano-Versionen vermisst. Aber warum wird die Datei kleiner?
Sorry, es war tatsächlich eine Demo-Version, da ich zum Zeitpunkt an meinen Zweitrechner saß und nicht darauf geachtet hatte...Oder es wurde eine Demo-Version getestet - durch die zufälligen Wasserzeichen und die JPEG-Kompression kann sich die Dateigröße bei jedem Durchlauf um einiges unterschieden...
Benutzerinformationen überspringen
Wohnort: Mexico City
Beruf: Virtual tours, Krpano coding, Graphic Design, Photographer, Panographer
Zitat
Klaus: Sorry, not sure what you mean - and related to the event processing nothing had been changed. With which version do you compare your case?
|
|
Quellcode |
1 |
<events name="test_event" keep="true" onnewscene="trace(hello!);"/> |
|
|
Quellcode |
1 2 3 4 5 |
INFO: krpano 1.19-pr14 (build 2017-12-01) INFO: HTML5/Desktop - Firefox 57.0 - WebGL INFO: Registered to: Imagen360.com INFO: hello! INFO: hello! |
Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »360boy« (9. Dezember 2017, 20:08)

Sorry, but as written by mail I disagree here (and I have two 4K passive 3D TVs here for testing) - many TVs are processing the input signal in the one or the other way, e.g. in my tests the TVs were always converting the 4K RGB signal internally to YUV420 - and for 'software-side-interlaced' pictures this is a bad thing! And it's also bad when the PC resolution doesn't exactly fit the screen resolution or when the TV does some scaling or overscan processing.And for 4K passive 3D TV (which will soon be the standard for home theater) the interlaced format is much the best.
Which browser and devices do you use?On various Android Tablets, the Gyroscope icon won't load at all for me.
Thanks for the report, I can confirm that - in WebGL-rendered hotspots without zoom=true or distorted=true some offsets (align and ox/oy) were not stage-scaled. In the next release this will be fixed.HI, there is a bug in pr14, whe mobilesacle is not set (so 0.5 by default) then hotspots width edge different than center are offset by 25% the height or width of the hotspot on mobile.
Actually, toureditor.html is still working by using Safari for windows (with windows seven)My virtual tour has about 150 panoramas and the new VTourEditor very slowly loads when adding a new hotspot.
toureditor.html was much faster, but now it does not work anymore (flash problem). Is there a way to speed up a new VTourEditor, or make the old one with flash is working for me again?
Thanks in advance,
midhat
The options.swf plugin is a Flash plugin and works only in the krpano Flash Viewer.hi, Klus, I've added code to xml file and put options.swf in plughin folder as usual, but the options interface doesnt show up at the right corner when I load the tour.xml to krpano Tools.exe , please advise. ths!
I will look to make that faster.My virtual tour has about 150 panoramas and the new VTourEditor very slowly loads when adding a new hotspot.
toureditor.html was much faster, but now it does not work anymore (flash problem). Is there a way to speed up a new VTourEditor, or make the old one with flash is working for me again?
Thank you.
I will look to make that faster.
Using the Flash vtoureditor.swf plugin is still possible, just use a Browser with Flashplayer support. All desktop browsers are basically still supporting Flash, but you might need to enable/whitelist it manually in the browser settings.
Best regards,
Klaus
That's a core xml limitation - line-breaks inside xml attributes are getting automatically normalized to one space character by the browser. That means the krpano HTML5 viewer itself never receives line-breaks inside attributes.I have been trying to use // inside an event without success, it breaks the action at this point. Maybe here once krpano execute it became a single line, and that's the reason ? not sure.
In previous versions there was no official or real '//' comment support - but there was only a 'little' one - there the '//' characters were not filtered or marked and so they become a part of the action-call name and action calls with '//' were simply skipped. So these could be used so comment-out one action call. But now with the real // support that's not possible anymore.In previous version it was not supposed to work but if you ended the line with a semicolon it worked.
|
|
Quellcode |
1 |
set(style[skin_hotspotstyle].loadscene_flags, KEEPVIEW); |
|
|
Quellcode |
1 |
set(style[skin_hotspotstyle].scale, 0.5); |
|
|
Quellcode |
1 |
<action name="skin_webvr_setup"> if(webvr.isenabled, copy(skin_settings.loadscene_flags_backup, skin_settings.loadscene_flags); set(skin_settings.loadscene_flags, KEEPVIEW); |
Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »tonesh« (7. Januar 2018, 11:52)
Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »vope« (3. Januar 2018, 12:22)