RoJeC wrote:You shouldn't have trouble with the Android version. However new devices may have new features that interfere with Cross.
Galaxy S5 is a 1 generation old Samsung flagship phone... so its not that new.
Did you test the various options in settings for audio playback.
Yes, I played around with settings including the recommended Async for OpenSL mode on Samsung devices.
You mention s5 and s6 in your posts. Might be right but pretty important to know what's happening on which device.
My bad on that reference (typo). The Android phone is Galaxy S5. The iPhone I tested with is iPhone 6.
Keylock function uses cpu capacity continuously. It can't take away drops and clicks. They are just less noticeable.
Okay, but why are they even less noticeable on the iPhone? Does this mean that iPhone wins again for all things multimedia and that if you want good keylock functionality you have to use an Apple device?
Delay in response could be by the setting for quantize. Disable to see if there's a difference.
So here's more info:
Remember that I uninstalled pro and reinstalled free to compare with the free version on iPhone.
So now I re-installed pro and noticed that the sampler now shows the various FX which wasn't there before. I didn't think much of the sample banks being blank before and thought maybe I just didn't understand yet how to use them. So I notice also that reinstalling Pro delivered a new version
2.3.3 vs. the 2.3.2 version I had before. Did stuff get fixed?
I'm not noticing the pops and clicks so far. So I don't know if some things got fixed in 2.3.3... but we'll see how it holds up to my rigorous testing.
New observation on Android and iOS:
1.)
When you set a hotcue, if the deck is
not playing, you can stutter the hotcue and it is accurate on beat. When the deck is playing, it is not so accurate or you can detect a delay. This performance is a little better on iPhone, but on both platforms, stutter while deck is playing is unusable with Quantize ON. I suppose this is expected because of what Quantize does, but sure would be nice if things could stay accurate all the time.
2.)
If a track is playing, the 1st time to touch CUE, it does only that... (cue). This may be ok, but if I touch and hold the CUE button it should continue playing regardless of whether its the 1st touch.
[/list]