This is for everyone on this particular topic...
Please excuse my rant, it was just a rant and I have removed it. I apologize. But I do stand by my feelings on MF3 right now. As everyone obviously (unfortunately) knows I was burned by an MF update last year on my own DL. So you can or hopefully understand my reluctance in updating to MF3 right now.
For the amount of time I use the school’s DL and the penny ante’ gigs I run for them, it’s also not a big necessity to update. I’m not quite in the same league as most of the pro’s here are. I am humbled and blown away by the vast knowledge and experience I’ve found here.
And I personally apologize to Alex H. You needed help with your issues and everyone was caught up in my silly issues with MF3. I hope someone can come up with a solution for you.
Thank you all for reading.
Keyboard Magic, I didn't see your rant so I don't know what you are apologising for, but accepted anyway. As ijpengelly says the problem did exist prior to MF3, but I updated in the hope that the problem may go away, and yes, now I have the syncing problem when the iPad is docked as well, but otherwise MF3 seems to be working OK.
I am convinced that the problem is related to IOS8. Prior to IOS8 we had no problems with MF2.1. The iPad1 running IOS5 was as solid as a rock - the problem was that this iPad has the old style connector and the 1608 has the new lightning connector, and I cannot dock, otherwise the problem would be solved.
One other issue I that under IOS7 when I undocked the iPad from the 1608, the wireless connection was made almost instantly and automatically. Now, under IOS8, the wireless 1608 device simply remains greyed out 4 times out of 5 and indeed, its often quicker for me to switch off the 1608 and then switch it on again to get it to connect.
Its not the iPad either, as we have been able to replicate the problem on multiple IOS devices all running variations of IOS8; including both on our 1608 and a brand new one out of the box. To add to the confusion, our suppliers were able to replicate the problem at our location (with the brand new 1608 and iPad) but state that when they set the same up at their offices, they have no problems (although i have no way of verifying this).
Although I have a copy of the IOS7.1.2 ipsw file, I am reluctant to try and revert the iPad3 back to IOS7 in case I brick it. Its all very frustrating, and I am having to spend far too much time on this, and of course the Church Council wont release the funds for the rdest of our sound system upgrade until this problem is resolved.
Alex