Cacophony Forums

Unofficial Mackie User Forums => DL1608/DL806/DL32R/ProDX Mixers => Topic started by: Keyboard Magic on April 29, 2015, 01:11:08 AM

Title: Master Fader 3.1 Bug
Post by: Keyboard Magic on April 29, 2015, 01:11:08 AM
I just emailed BenO at Mackie about this problem I found tonight at home with the updated MF. Here is the excerpt from my email describing it.

I found one major bug, with both my iPad Air 2 and iPad 2, running MF 3.1 connected to the DL wired, wirelessly or un-connected. I open the recording screen and if I touch either the L or R level controls MF crashes and minimizes to the background. Double tapping the home button on the iPad shows the app is minimized. Touching the app restores MF and it re-syncs and a “Bug report” Window opens up. This happens everytime  you try this without exception.

Everything else seems to be okay other than this. I don't record with the DL much, but this could be annoying if not addressed by Mackie soon. 

Oh yes, MF has access to the built in microphone on both my iPads as well. just in case any one was going to ask.  8)
Title: Re: Master Fader 3.1 Bug
Post by: RoadRanger on April 29, 2015, 03:19:13 AM
I wouldn't have thought to try to tweak those on a disconnected iPad - but yup, pukes right out :( . I'll have to checking out on the docked iPad tomorrow...
Title: Re: Master Fader 3.1 Bug
Post by: Michael Welter on April 29, 2015, 04:48:27 AM
Oh yes, MF has access to the built in microphone on both my iPads as well. just in case any one was going to ask.  8)
What can you do with that?
Title: Re: Master Fader 3.1 Bug
Post by: ijpengelly on April 29, 2015, 06:29:43 AM
Yup, confirmed... does it on an iPad2 docked. Oddly, the minimised version is the last 'snapshot' it was restored from, rather than it taking you back to the same page...
Title: Re: Master Fader 3.1 Bug
Post by: Keyboard Magic on April 29, 2015, 10:13:53 AM
Oh yes, MF has access to the built in microphone on both my iPads as well. just in case any one was going to ask.  8)
What can you do with that?

Just in case the app crash was caused by "no access to the mic". If you try to record audio with access turned off, you will get a blank very small audio file. I thought this might be causing MF to crash. Obviously that's not the case.

I don't have any gigs this week, but have 3 with the DL for the school next week. I hope a bug fix is released pretty darn quick or I will have to go back to MF Classic until it's fixed or just use my old reliable backup mixer.  :( On the plus side, it was a smart move by Mackie to re-release MF 2.X.

Come on Mackie, let's get a bug fix patch out A.S.A.P! Please?
Title: Re: Master Fader 3.1 Bug
Post by: JohnMHoyt on April 29, 2015, 12:21:05 PM
I just emailed BenO at Mackie about this problem I found tonight at home with the updated MF. Here is the excerpt from my email describing it.

I found one major bug, with both my iPad Air 2 and iPad 2, running MF 3.1 connected to the DL wired, wirelessly or un-connected. I open the recording screen and if I touch either the L or R level controls MF crashes and minimizes to the background. Double tapping the home button on the iPad shows the app is minimized. Touching the app restores MF and it re-syncs and a “Bug report” Window opens up. This happens everytime  you try this without exception.

Everything else seems to be okay other than this. I don't record with the DL much, but this could be annoying if not addressed by Mackie soon. 

Oh yes, MF has access to the built in microphone on both my iPads as well. just in case any one was going to ask.  8)

Can confirm it happens on our iPad 2.  Haven't checked on the new iPad we have.
Title: Re: Master Fader 3.1 Bug
Post by: WK154 on April 29, 2015, 02:08:55 PM
This is typical of what happens when maintenance level programmers take over and developers are off doing another project. Be prepared for a few more along this line until they get their feet wet if ever. :)
Title: Re: Master Fader 3.1 Bug
Post by: Keyboard Magic on April 29, 2015, 02:27:52 PM
This is typical of what happens when maintenance level programmers take over and developers are off doing another project. Be prepared for a few more along this line until they get their feet wet if ever. :)

I wonder what the turn around time on a bug fix will be? Already creating scenes in MF Classic for just in case.  ;)
Title: Re: Master Fader 3.1 Bug
Post by: WK154 on April 29, 2015, 06:18:09 PM
Well we'll find out since it's a reproducible bug it should take a savvy programmer about an hour to fix. Then it has to go thru Apple's little game and if you're lucky you'll see it by the weekend. If this was a Linux app a couple of hrs and you'd be up and running. Love all that bureaucratic BS. On second thought they wouldn't release something like this. :)
Title: Re: Master Fader 3.1 Bug
Post by: beno on April 29, 2015, 11:02:50 PM
Thanks for reporting this. We are testing a fix now and submit to the app store ASAP. I'll keep you posted on the status.
Title: Re: Master Fader 3.1 Bug
Post by: Keyboard Magic on April 29, 2015, 11:09:33 PM
Thanks for reporting this. We are testing a fix now and submit to the app store ASAP. I'll keep you posted on the status.

Thank you so much for responding so quickly to this issue!  :thu: :thu:
Title: Re: Master Fader 3.1 Bug
Post by: beno on April 30, 2015, 03:16:15 PM
OK we fixed this bug and submitted a fix to Apple. It will post automatically when Apple approves.
Title: Re: Master Fader 3.1 Bug
Post by: JohnMHoyt on April 30, 2015, 03:47:19 PM
OK we fixed this bug and submitted a fix to Apple. It will post automatically when Apple approves.

That was easy...
Title: Re: Master Fader 3.1 Bug
Post by: Michael Welter on April 30, 2015, 04:01:56 PM
Ben, you rock! Thanks.
Title: Re: Master Fader 3.1 Bug
Post by: Keyboard Magic on April 30, 2015, 04:20:11 PM
OK we fixed this bug and submitted a fix to Apple. It will post automatically when Apple approves.

Excellent!  8)
Title: Re: Master Fader 3.1 Bug
Post by: Keyboard Magic on May 01, 2015, 12:22:56 AM
Well we'll find out since it's a reproducible bug it should take a savvy programmer about an hour to fix. Then it has to go thru Apple's little game and if you're lucky you'll see it by the weekend. If this was a Linux app a couple of hrs and you'd be up and running. Love all that bureaucratic BS. On second thought they wouldn't release something like this. :)

Just doing a little research on the average time it takes to get an app approved by Apple's little game. Here's a link to the App Marketing Lab that explains the process. Is this pretty much accurate?

http://www.appmarketinglab.com/long-apple-review-app/

Or do they adjust their approval rates depending on who or whom submits an App?
Title: Re: Master Fader 3.1 Bug
Post by: JohnMHoyt on May 01, 2015, 01:01:59 AM
Well we'll find out since it's a reproducible bug it should take a savvy programmer about an hour to fix. Then it has to go thru Apple's little game and if you're lucky you'll see it by the weekend. If this was a Linux app a couple of hrs and you'd be up and running. Love all that bureaucratic BS. On second thought they wouldn't release something like this. :)

Just doing a little research on the average time it takes to get an app approved by Apple's little game. Here's a link to the App Marketing Lab that explains the process. Is this pretty much accurate?

http://www.appmarketinglab.com/long-apple-review-app/

Or do they adjust their approval rates depending on who or whom submits an App?

One of my clients regularly releases updates to their apps 3-5 days average cycle from the time it is the queue to when it is available for download.  Except times of high activity, such as after the release of a new iOS, then it has taken them as long as a week and some change (7-10 days).
Title: Re: Master Fader 3.1 Bug
Post by: Keyboard Magic on May 01, 2015, 01:13:03 AM
Wow! Probably won't have the update before my next gig this coming Monday for sure.  :( I can probably use 3.1 as it is since I won't be going anywhere near the recording screen at all. On the other hand maybe it would be wise to "downgrade" to MF Classic to avoid any potential major Oops moments.  I have 2 more gigs right after this one the same week.  :facepalm:

Thanks for the info just the same though.  :thu:   8)
Title: Re: Master Fader 3.1 Bug
Post by: beno on May 01, 2015, 03:38:22 PM
This bug was very localized so you shouldn't have any issues with 3.1.

Also, for up to the minute app review times, we use this site:
http://appreviewtimes.com/

A bit longer than normal right now but 3.1 was approved in less than a week so who know.
Title: Re: Master Fader 3.1 Bug
Post by: Keyboard Magic on May 01, 2015, 04:05:22 PM
This bug was very localized so you shouldn't have any issues with 3.1.

Also, for up to the minute app review times, we use this site:
http://appreviewtimes.com/

A bit longer than normal right now but 3.1 was approved in less than a week so who know.

Thanks Ben, I realize these things do take some time. I won't be using the recording feature, so I do feel fairly secure with 3.1 as it stands.  :)
Title: Re: Master Fader 3.1 Bug
Post by: Keyboard Magic on May 04, 2015, 05:35:59 PM
Used the DL this morning at the school. For Music Monday. Running MF 3.1 on the iPad Air 2 wirelessly. No hiccups whatsoever.  :thu: I did stay away from the recording page though.  ;)
Title: Re: Master Fader 3.1 Bug
Post by: beno on May 06, 2015, 11:09:44 PM
OK looks like Apple approved 3.1.1. This should be rolling out to App Stores now. It fixes this bug as described in the release notes in the App Store.

"Master Fader 3.1.1 fixes a crashing bug when trying to adjust the recording levels for a DL1608 or DL806. Whoops."

Let me know if anyone uncovers any other new issues. Thanks.
Title: Re: Master Fader 3.1 Bug
Post by: Keyboard Magic on May 06, 2015, 11:27:33 PM
OK looks like Apple approved 3.1.1. This should be rolling out to App Stores now. It fixes this bug as described in the release notes in the App Store.

"Master Fader 3.1.1 fixes a crashing bug when trying to adjust the recording levels for a DL1608 or DL806. Whoops."

Let me know if anyone uncovers any other new issues. Thanks.

Thank you Ben, it is really appreciated that it got rectified so soon.  :thu:  Haven't seen it yet on the Canadian or US App store yet, but will keep my eyes peeled for it. I suspect it will show up tomorrow morning our time.   8)