That’s very interesting, thanks for flagging. I’ll have our QA team look into it.
Why did you do this??? Who asked for it??? You have completely ruined the usefulness of LeiaPlayer! I know you want everyone to use your patented 4V mode, but it totally ruins my stereo pairs with its extra interpolated views. The result is a fuzzy mess with very little depth, instead of a crisp stereo image. It even ruins the photos I’ve taken with LeiaCam! How is this an improvement??? Two or three versions ago, LeiaPlayer was useful. Now it’s a piece of crap. How many more months are we going to have to wait for you to add a simple option to keep ST mode on, like it used to be? Who is running your software development process? It’s a failure and totally out of control. You should be ashamed of it. I used to have some faith in your company, but it is becoming harder and harder to recommend your product!
I think by default LeiaPlayer should open 3D as ST and 4V as lightfield, but I think your comment is too exaggerated, they’re constantly working hard on new features, no other company about 3D is doing so much work for their released devices. I also have this and other complaints about their compatibility with existing 3D content, but they are making changes to better from time to time. If you want a pure stereoscopic 3D tablet, you should look the King tablet.
So that there is a consistent behavior for all files. All 3D files open in Lightfield view mode, all 2D files open in 2D view mode.
We had multiple users reach out and ask why sometimes their files were in Lightfield view mode and other times they Stereo view mode, not realizing that they set the files themselves. You can simply jump back to ST view by pressing the button when you want to see files in Stereo view mode.
I’m the one who runs the decisions made for LeiaPlayer. We are developing each version towards a larger goal. Sometimes we need to make architectural changes to lead to this goal. For example, the app was storing view mode states in its cache, so when you delete and reinstall the app, or clear it’s storage and cache, those states would be lost and you’d have to manually go and switch them all again. With this new method, this state is persistent regardless of the Player’s state, and you can even send files to people on other devices or apps and it will be in Stereo view by default.
@David_in_VA would you like to return to version 3.2? That seems like it will solve your problem.
No, that version had the top/bottom banner bug (which I reported to you in December, and I appreciate you fixing it). What I want is to be able to hand my Lume Pad to someone and let them swipe through my stereo photos without them (or me) having to do anything to reset the mode to ST on each photo. This is the way LeiaPlayer used to work, and I think it was easier for “the masses”.
In general, our data shows that most users don’t have any (or many) SBS or MPO files. So this issue only affects 3D enthusiasts. The change was made to be easier for the masses who are often confused about the difference between Lightfield and Stereo mode. Often when I show people and they switch between them, they can’t tell any difference, they just mention that they “can’t move as much” when in ST mode. Of course, this is dependent on content.
For full context, there was also another critical bug that was caused by having the view state saved per-content with the addition of the 2D to 3D video conversion. That would have taken much longer for us to fix, so we decided to make this change one version early so we could get this out to users faster and move on to the next one as I know everyone has been waiting for this release for quite some time. In fact, part of the reason we pushed hard to get it out faster was because you had pushed for it.
Your feedback has been heard, and a solution will come, but if you want to set your files into ST view mode, your two options are to revert to 3.2, or wait for 3.4.
Okay, I understand. It’s your product and you can listen to whomever you choose. But don’t any of “the masses” use the LeiaCam? Don’t you want them to use it? All of my LeiaCam photos look better in ST mode. The interpolation reduces the depth and gives a fuzzy look to the images.
LeiaCam shoots in LIF format, but I can understand that when you shoot high disparity close-ups, it will look better in ST view mode. It’s currently optimized for taking mid-range shots of people, pets, etc. which should generally always look better or the same with a wider viewing angle in Lightfield view mode.
Either way, LIF photos will be able to be set to show in ST by default starting with the next version of LeiaPlayer. But your feedback has been heard, and I’m going to spend some time on exploring a solution that doesn’t require us pulling engineers off their other critical projects for too long.
@Nima ,Thank You for this Great Release!
Love the new Video Conversion and that you keep improving the Software Suite.
@David_in_VA , that was rude and Not very polite, If you want a feature then ask for it, I am pretty sure if it is beneficial for a lot of users then the Leia Team will try to implement it, just be nice, rudeness doesn’t get you very far with anything, we are all just human after all.
As a Support-Agent in Software I know how things are handled usually and it is always good to have some opinions to be able to further improve a Software.
@Nima do you think it would be possible to set the Default Viewing mode in the Settings or is this hard to do programming-wise?
@David_in_VA would that be an Option?
Long-term we want to have a variety of options. Short-term we have to make trade-offs. Right now, re-enabling the prior behavior will cause a large bug that will take a long time to resolve. Building a new feature like what you propose by having it as an option in Settings will also take a long time. I think me and my team can come up with something that will be quick and will ensure we’re all happy at least until the version 3.4 comes out.
Thank you, @Nima . I look forward to the next release of LeiaPlayer.
No hurry, take your time,
I already love it as it is right now,
4V is Superior to traditional stereo anyways.
Thank you for all your efforts and have a great Weekend!
I guess I fall under the category of 3D enthusiast, but the change does negate the principal reason I use the pad, which is a digital repository of my grandparents’ stereoscopic photography.
It’s probably too soon to inquire about a roadmap/timeline for 3.4, but if you have any info to share I’d appreciate it. If I wanted to roll back to the previous version, how would I go about doing so?
If you’d like to roll back to 3.2 just DM me and we’ll see what we can do.
Well, IF the “suddenly stopping” bug is fixed in 3.3, it seems that I have a choice between the infinitely preferable 3.2 where the images are viewed as their author intends or 3.3 where everything is viewed in the view that artificially generates the views, losing massive amounts of detail on the way unless the viewer DELIBERATELY chooses the sharper, better ST method EVERY TIME THAT AN IMAGE IS DISPLAYED. This is a nonsense approach. If I CHOOSE the ST method of viewing, Leia should not DELIBERATELY decide that I must go through the process of making my choice EVERY TIME.
Sorry, Nima, but you’ve got this one wrong. By all means default LIF files to the LIF view, but DO NOT default JPG SBS files to a view designed for a different type of file! There is no logic for this. Default them to ST - surely that is the viewing method that was designed for SBS pairs?
You said “For example, the app was storing view mode states in its cache, so when you delete and reinstall the app, or clear it’s storage and cache, those states would be lost and you’d have to manually go and switch them all again. With this new method, this state is persistent regardless of the Player’s state, and you can even send files to people on other devices or apps and it will be in Stereo view by default.” Could you explain this for me? I don’t understand how stripping out the desired viewing method makes the “state” persistent? And how can you assert that, if I send a file to “people on another device” and have any certainty of how their device will behave?
I suspect that there is more to this decision than I can understand. But it does mean that, until it’s “corrected” my Lume Pad is useless as a 3D image viewer.
Sure. We’re going to be adding a new feature to LIF that allows you to flag them as stereo by default, so you can send it to any app or other Leia device and it will show in ST view by default.
We’ve heard the feedback and are looking into what we can do. But surely both rolling back to 3.2 in the meantime or just tapping the ST view button when you want to view content in stereo view mode are both incredibly simple solutions to this problem.
Maybe a switch in settings to select favorite viewing mode? User choice is always the best option
Definitely, and many more options and features are coming. Still, there’s always a juggle between adding features, fixing bugs, and how much time we spend on each version. Hopefully we’ll have a stopgap stereo solution ready for users by next week.
“Sure. We’re going to be adding a new feature to LIF that allows you to flag them as stereo by default, so you can send it to any app or other Leia device and it will show in ST view by default.” You’re going to add a feature to return the behaviour to what it was before you decided to make it useless? Sounds like it was really well thought out, doesn’t it?
“We’ve heard the feedback and are looking into what we can do. But surely both rolling back to 3.2 in the meantime or just tapping the ST view button when you want to view content in stereo view mode are both incredibly simple solutions to this problem.”
No! Thy might be “simple” tou you, but to me having to use a buggy version because you DELIBERATELY introduced an equally bad bug into the new version doesn’t really sound like progress! Oh, and having to tap on the ST button EVERY TIME THAT AN IMAGE IS DISPLAYED is NOT “simple”! It is INTENSELY irritating!
I think you’re misunderstanding. I suggest you reread the thread. No, the LIF format has never had this feature. And the behavior users want us to roll back is primarily for native stereo files (SBS, MPO, JPS).
Ultimately the behavior was changed one version early due to a critical bug as mentioned above. The estimated time to fix the bug was over a week of engineering time. If we would have done that it seems you’d be in the exact same boat today: everyone would be using version 3.2. However instead now 3.3 is out for all of our users who don’t primarily use Lume Pad for viewing content in stereo 3D.
As I mentioned before, the crashing bug you mentioned in 3.2 is not normal and has not been seen by anyone on our side. Have you reached out to customer service at email@example.com so we can try to get to the bottom of why that’s happening to you on your device?