Android App Troubles

[Traxus]

Realizing there is only official support for the Nexus 7, I've hit some issues and was wondering whether they are on the radar/slated to be addressed.

After seeing Darren Wood's 23" touch screen monitor running on Android TV a few weeks ago I immediately threw about $400 at a similar setup; did some resizing work on the Traktor template, and have been decently pleased with the results.

Most of the issues are superficial display problems, however I am having one hell of a time maintaining consistent Midi Clock data. Sometimes Lemur receives and slaves to it just fine, other times it will go haywire for awhile and then for some reason it will go back to normal. Below is a screen shot of an issue, where Lemur seems to think the BPM is greater than 10,000

bpm.jpg (61.34 KiB) Viewed 1841 times

Are there any Midi Clock bugs on the radar?


Another anomaly I've had is in regards to the skins. I accidentally switched the skin from Pixel to Flat within the Lemur app itself, and then switched it back. Strangely, the knobs retain the display of the flat skin:

platter.jpg (87.89 KiB) Viewed 1841 times

I've tried switching stuff around again, and it is doing this for all versions of the template (even if i upload a new one), not a deal breaker functionality wise but very bizarre. It was displaying properly at first (this is before I had sorted screen resolution and template scaling).

platter2.jpg (65.57 KiB) Viewed 1841 times

Lastly, and I think this is on the radar, is the font readout issue. Lemur (almost comically) selects various letters within various objects and offsets them way to the right while leaving the rest of the string alone; the amount they are offset by seems to be a consistent percentage, related to the size of the font. Looks to be about 50 or so white spaces of the given font size. In particular, it seems to dislike letters with angles in them (A, V, X, Y, W) but this is not exclusive.

[Traxus]

Some updates

I was able to alleviate the knob display issue with the following routine (i think)

In Lemur editor, i disabled the 'force project skin' check box
In Lemur on android, within the template I changed from pixel skin, to shaded, and then switched back to pixel, this caused the knobs to remain in the display of the shaded skin (on switching to the pixel skin, knobs were sustaining whichever display their last skin was).
Closed lemur with a hard exit, re opened, and knobs were displaying as pixel skin again.


Played with the template for some time last night without so much as a hiccup in midi clock... starting to wonder if this is a network latency issue... Such that packets are being delayed and lemur is receiving a whole boatload of ticks every so often rather than a steady stream; I was getting the error while also streaming my computers monitor to another tablet of mine...

[wphantom]

Hi Traxus !

I have also the problem with letters that are translated to the right. not all letters but nearly one in each label... Not very critical bug but quite annoying in the begining...


Sylvain

[ChiLam]

I think your Midiclock problems are similar to those I and other users have experienced. Wired or not, using an external midi interface or not, using very large templates or very small ones it is the same story - sooner or later Lemur will spray a whole bunch of duplicate midi notes out from the StepNote objects and ruin your music.

It can stay tight and smooth for long periods of time but then suddenly it will do the old duplicate note thing.

I have this happpening using the wired midi interface which Liine reccomend (iConnectmidi4+)
Others have posted here and on the Lemur Facebook users blog about it happening even when triggering apps on the same iPad too - so the interface is not to blame. Most have given up entirely using the sequencers and reccomend instead using other programs like Max or Max4Live for sequencing.

I have been in contact with Nick from Liine about this issue for a long long time now. I haven't heard any news about it for a while though. I'm not even sure that Liine accept it to be a Lemur fault and instead seem to suggest it could be hardware or OS issues. I have pretty much given up myself now - after hours and hours of creating templates and troubleshooting the problem it is a bit maddening to give up but hey, what can you do?

Best of Luck