Jul 9, 2013 at 5:58am
I’ve posted separately about the glitchiness of the live.dial and the live.slider which appears as a single multislider style slider.
I’d like to point out that the kslider will not render the top or left edges on the ipad 1 – this is irrespective of the actual or relative sizes of the mira.frame object or kslider object. Indeed the Frame of the kslider is so thin it needs to be ‘on’ to discretize between adjacent ‘white’ keys. This is in part a Max6 issue because with 4/5 (from memory) you could easily use kslider without a frame. Either way, those two edges are not rendered on my ipad 1
The slider also renders differently than in max (again like a bar multislider style) – not sure why this has to be so – some interfaces work better with the line
On the ipad 1 usability front, for those interested, apart from a few incompatibility issues (regarding lack of compass etc) the updating speed (even with the help file examples) can be very slow (there may be network issues, but they don’t blight other apps!) – it can take quite a few seconds to populate the screen
Most objects appear live (as if by magic) but i’ve found the fpic object to be hit and (mostly)miss
Hopefully we can have a ‘mira compatible’ object filter in the Max object explorer soon (the little (m) is handy, but you still need to hunt a bit too hard)
FWIW, I hope the dev(s) work mostly on fixing what we already have (efficiencies) before getting distracted by additional bling ….. it crashes too often !!!!!!!!!!!!!!!!!
Nov 17, 2013 at 5:58pm
Here’s another (on the ipad 1)
When mira is set to mirror the presentation mode, the orientation of live.tab will switch based on whether presentation mode is enabled on the host computer.
– Pasted Max Patch, click to expand. –
Copy all of the following text.Then, in Max, select New From Clipboard.
Nov 17, 2013 at 10:15pm
@avantronica Thanks for pointing out these discrepancies and even more so your patience as we try to fix all this stuff. Hopefully it’s reassuring to know that “bling” is right at the bottom of my list of priorities. Many of the issues you’re seeing, especially the slow network speed, creaky drawing and occasional crashing are all caused by certain inefficiencies in the way Mira handles drawing. Unfortunately these are going to be at their worst on the iPad 1. But this is my current focus, and I’m hoping that tweaking here will improve the Mira experience across the board.
In the mean time, you can get the most out of Mira by trying to work within memory constraints. Simple UI’s, while less interesting, will load faster and use less memory.
I’ll be sure to keep you in the loop as things hopefully improve. Nah, forget that ‘hopefully’. I’ll keep you in the loop as things _inexorably_ improve.
Nov 20, 2013 at 12:53am
Nov 20, 2013 at 3:51am
Thanks for being so frank with me, it’s really great to be able to talk openly about the whole development process. I get the sense that you’re expressing what a lot of Mira users are feeling, so I’m doubly glad that you’ve taken the time to lay it all out.
People have been calling for a central discussion place for Mira for a long time, so I’ll put some thought towards what that should look like. Part of the delay in getting something like that together is that I don’t think a forum thread is exactly the right place. One big thread is just going to get unwieldy, and a forum topic for Mira, while great, is better for managing a bunch of small topics than one central Mira wishlist/roadmap.
As for bpatcher, I can at least say that it’s quite high on my list. As I alluded to in the last post, memory issues are the biggest focus for me right now. These issues flare up especially in the case of really large patches. I’m worried about releasing bpatcher without addressing these core problems, in that I don’t want to enable this feature without really being able to support it. Hopefully that makes sense.
Thanks again for your patience! I’m hoping that not having bpatcher for now isn’t spoiling your Mira experience too much.
You must be logged in to reply to this topic.