Cacophony Forums
Unofficial Mackie User Forums => DL1608/DL806/DL32R/ProDX Mixers => Topic started by: RoadRanger on August 26, 2013, 07:49:49 PM
-
https://itunes.apple.com/us/app/mackie-master-fader/id511500747
Dunno why Mackie didn't just make Master Fader a universal app that works on both iPad and iPhone - that way they'd stay in sync and not "break" each other when one goes live before the other :).
-
Hey, it looks like they may have fixed the 24-bit wav recording bug I sent them (several months ago).
As for the single sourcing of iPad/iPhone code, that would be too obvious ... there must be a rational technical reason why they chose to keep different code lines.
-
Even with 4 months between updates that's still 3 a year :) .
-
Wow that makes me incontinent (look it up). This is the delay tactic for V1.5 which I predicted will be out in October/November with a smokescreen of iOS V7 to blame the feature shortfall on. What tremendous new features will they dump on us? Can't wait. Since V1.5 should have already been finalized why won't they let users know all the goodies we will get? Are they afraid of the disappointment V1.5 will bestow upon us? Fortunately I will be without a DL by then.
-
It's pretty common to have to "hide" a new feature or two in a release that didn't make it through final testing. I'd guess that's why they won't release the list of new features in V1.5 until it actually goes live in the app store. The releases today seem to indicate that lightning connector support is imminent. Musician's Friend had the DL1608 listed as the "DL1608 Lightning" for a while but they seemed to have fixed that ;) . On Facebook Mackie posted:
Q: "Will the new lightning connector be able to be installed on old 1608's or is it going to be a whole new mixer?"
Mackie: "Both. We are planning further communications near the end of september. There will be a cost to change over, but I don't have pricing yet."
-
https://itunes.apple.com/us/app/mackie-master-fader/id511500747
Dunno why Mackie didn't just make Master Fader a universal app that works on both iPad and iPhone - that way they'd stay in sync and not "break" each other when one goes live before the other :).
About 10 Megs of code for starters and probably some lib functions that don't play the same way.
-
It's pretty common to have to "hide" a new feature or two in a release that didn't make it through final testing. I'd guess that's why they won't release the list of new features in V1.5 until it actually goes live in the app store. The releases today seem to indicate that lightning connector support is imminent. Musician's Friend had the DL1608 listed as the "DL1608 Lightning" for a while but they seemed to have fixed that ;) . On Facebook Mackie posted:
Q: "Will the new lightning connector be able to be installed on old 1608's or is it going to be a whole new mixer?"
Mackie: "Both. We are planning further communications near the end of september. There will be a cost to change over, but I don't have pricing yet."
Hacks will leave broken code in a release most reputable companies will get it fixed. The Lightning connector just needs a new paddle board and no analog lines. Making a "new mixer" should be interesting. Installing a paddle board takes all of 10 minutes. Code changes will no doubt be required.
-
snore :(
this is depressing.
-
Check out the Mackie enhancement page ... http://mackie.uservoice.com/forums/97035-dl1608?filter=top&page=1 ...
Beno just marked "Channel Linking/Grouping" with status "Started". Another top 10 feature - stereo channels - is also marked as started.
Those are the only two I could find on the list, but it's at least an indication of what they are working on now ... better than nothing!
-
Those two are just one feature depending on the implementation. One note on the Lightning connector. It's a Apple screwed up design that allows shorting out the power by the exposed connector. Goes against any connector design I'm aware of. A six pack and an impatient operator will make short work of it.
-
From Mackie's Facebook page:
(https://sphotos-b-lga.xx.fbcdn.net/hphotos-prn1/1157544_10151844836706145_39501133_n.jpg)
-
Nice concept car but were are the wheels and the engine? Didn't Sam draw this up about a year ago?
-
Any problems with the update?
-
It's working fine for me :) .
-
Last night was my first gig using the v1.43 software
I have had my dl1608 for ages and all previous updates had been fine.
After locking the ipad into the cradle it did the firmware update, then it went downhill from there.
The physical mixer seemed to be working fine, the led's would light up as I turned the gain knob but there was no sound! The master fader app appeared to be running fine but there was no input channel metering and no audio out not even from ipad/iPod channel. It appeared as though the mixer and the ipad/MF app were just not talking to each other. Someone once said in a post on the old forums that if your ipad dies the mixer will still work as it remembers the last state it was in, maybe so, but what does any self respecting sound engineer do at the end of the show? You turn the master faders down, don't you?
I removed the ipad and rebooted it, still no luck the MF app just appeared to be dead. I loaded other stored shows but no luck , changed the sample rates around, no luck.
Then finally I decided to turn off and then back on the mixer itself. Finally it decided to work YEAH !!!
It might be nice to warn us of this in the future please, as it almost got my gig cancelled last night.
I was 100 klm's from home and I don't usually carry a spare mixer with me, the car is totally full with all my gear, the bass amp has to sit on the front seat! Might have to buy a new car so I can carry a spare mixer with me in future :-(
Keggles
-
So lesson number one Never load a new version of anything without testing the results especially before a paying job.
-
I had simelar problems with 1.43
For me not at a gig luckely
But during a rehearsel
After a while the ipad stops the input metering, the ipad needed to be set on the correct wifi network again
Luckely i didnt need to power the mixer on off,
First ithought it was the lan cable
Today the fist gig with 1.43 will see how it goes
Hope for no prolems!
Before 1.43 no problems
-
Would be helpful to know iPad version and iOS version.
-
So lesson number one Never load a new version of anything without testing the results especially before a paying job.
Good advice. Lesson number two - always carry a spare mixer. It will almost ensure that your main mixer will never fail. But leave that spare at home and you're asking for trouble.
Well I don't always follow my own advice as I don't carry a spare if I am close enought to home. Fortunately the only time my mixer failed I had a backup with me.
I hope that's the only time you have a problem with 1.43!
Cheers
-
Hello Fellow DL'ers,
Been snooping around here for a while and reading posts. That got me to purchasing a DL1608. So far love the capabilities.
However I just recently upgraded to 1.43 and have experienced the same issues. Luckily I run a 1st Gen iPad docked in my DL and have an iPad mini setup wirelessly using an new version Airport Express.
Thankfully I was still able to access my DL using the mini and was able to tweak with no issues and make it through my gig without loosing too much sleep.
I also noticed that I was getting booted out of the Master Fader app on the docked 1st Gen iPad when I was trying to start a song in iTunes. I would escape Master fader, open iTunes, start a song, return to Master Fader and within a few seconds Master Fader would minimize (not close out). Of course the song didn't start and I was unable run any tunes. However I could start the iTunes and then access the iPad channel in Master Fader using my wireless iPad mini. Anyone experiencing that issue?
Unfortunately I have not tried to use my 1st Gen iPad wirelessly to see if the issue reared its ugly head.
Mackie Support mentioned that I should Delete the Master Fader App for the 1st Gen and then reinstall it. The only problem there is I will lose my pre-sets. Not sure I am ready for that.
Thanks for the forum guys and gals.
ART
-
I guess we'll be seeing V1.44 shortly if they care. Please post specifics for problems including iPad version and iOS version.
-
I know when I turn on my DL1608 that the docked iPad often doesn't "see" it. I have to undock and redock it and then go into the connections and choose wired. Thereafter all is well. There's a rumor that turning on the iPad first and them the DL1608 might make things happier. As for wireless issues make sure yous guys read through the FAQs here!
-
I thought that it was well understood that the sequence of turn on was iPad first then DL otherwise the DL code could take forever or simply hang trying to establish sync. Yes Mackie screwed up a rather well tested Linux project set of code or maybe AD did. In any case turn on your iPad and MF app before turning on the DL. I think that came out of trying to find a reliable cable extension for the DL.
-
I have experienced a few instances where the iPad lost it's connection with the mixer after it was docked and connected. Anyone else see anything like this?
-
Well. I got really gun shy with the new 1.43 update. Luckily I still had my older 1.4 still saved on the laptop and everything is back to stability heaven. Lost my presets. But I guess that's a price you got to pay. At least for now.
I am amazed that there isn't a better system through iTunes that will let you downgrade your versions at your leisure. It gives you at least an option if something just doesn't work right out of the box.. Especially when most of us rely on this gear to work night after night. And it takes iTunes about two weeks to approve a version. A lot can happen in two weeks in the computing business..
For now I would recommend to everyone to keep a copy of your working version (.ipa) on your cloud or desktop so you can always get back to the way it was..
I guess I'll wait until V2 comes out and nail bite a bit until I start seeing the flame wars die down or V2.1 becomes available before I'll upgrade again..
Good luck and keep making music.
-
I thought that it was well understood that the sequence of turn on was iPad first then DL otherwise the DL code could take forever or simply hang trying to establish sync. Yes Mackie screwed up a rather well tested Linux project set of code or maybe AD did. In any case turn on your iPad and MF app before turning on the DL. I think that came out of trying to find a reliable cable extension for the DL.
The whole sequence of turning on the mix control system for those that are new to this is:
1. Turn on your access point (Air... or whatever) and wait till it's ready to play DHCP server nicely (unless your using fixed IP addresses). Wait anyway until the lights tell you to go.
2. Turn on your iPad and start MF.
3. Lastly turn on the DL1608 and wait patently until it sync's (message block pop's up).
If any of these fail you have a problem that needs attention.
Shutdown has no sequence.
-
I had updated my iPad with version 1.4.3, but only got around to actually docking it with the DL last night. In testing I had no issues, I tried docked, wireless, cycling the power and closing and re-opening the MF application and it all seemed to behave as normal. I'm running the lastest official version of iOS on an iPad 2.
-
The whole sequence of turning on the mix control system for those that are new to this is:
1. Turn on your access point (Air... or whatever) and wait till it's ready to play DHCP server nicely (unless your using fixed IP addresses). Wait anyway until the lights tell you to go.
2. Turn on your iPad and start MF.
3. Lastly turn on the DL1608 and wait patently until it sync's (message block pop's up).
This is only the requirement for upgrading software, no? And also assuming the iPad is docked, which means a network connection for the DL isn't even needed.
As for regular boot ups, I don't think I have ever had an issue starting the DL before MF ... The router always comes before the DL though or else it won't connect properly to the network.
-
So is the consensus that 1.4.3 is a bad release and we should not upgrade?
Or is it just more temperamental on the booting sequence than prior releases?
Or are these the same problems people have with every release due to clunky usability of the product?
-
So is the consensus that 1.4.3 is a bad release and we should not upgrade?
Consensus? Oy vey, have you got the wrong forum :facepalm:.
-
Oops, sorry --
So is the CACOPHONY that 1.4.3 is a bad release and we should not upgrade?
Or is it just more temperamental on the booting sequence than prior releases?
Or are these the same problems people have with every release due to clunky usability of the product?
-
LOL!
I've had no major problems with it. If the docked iPad doesn't connect when you power up just undock and dock it, then go into "connections" and choose "wired".
-
The consensus is that the jury is still out on this one. Clue number one. Some users are having issues and not during boot up. Unfortunately this usually happens when you least expect it and the exact sequence of events is usually lost. Is it repeatable? No. Clue number two. .. The router always comes before the DL though or else it won't connect properly to the network. This is a known automatic reconnect flaw in DL's logic bypassed by a manual reconnect request. This one has been around since day one. Clue number three. The V1.4.3 list of new features includes the "smaller footprint and speed improvements" or something like that. This means that they compiled the app with a different set of switches to remove debug links and optimize the code. This will bring out the nasty bugs. Depending on the quality of regression testing this may or may not show up. Is it a good release? If it works for you, yes otherwise no, your gamble.
-
If you are not using the wireless make sure you turn "airplane mode" on. If you will be using the wireless make sure you do all of this:
http://cacophony.aspinock.com/index.php?topic=193.0
Otherwise you will get what you deserve x( .
-
This means that they compiled the app with a different set of switches to remove debug links and optimize the code. This will bring out the nasty bugs.
Ouch ... depending on whether or not the development language is memory safe, removing debug from the compilation could expose memory pointer overruns ... ran into this years ago in C development. iOS dev is in "Objective C" ... is it subject to the same issues?
-
That and hundreds more. Murphy can have a field day with any of this. Remember that the code also has to run on single core as well as a multicore processor. Probably not much utilization of A5X, A6 capabilities being used due to backward compatibility being necessary. As I recollect the ARM uses a virtual memory system (mapped) and Harvard architecture (separate instruction and data space) but remember that compilers are just another piece of software with all the same problems as any other app (bugs).
-
Did a gig last night with this version and had no issues during the night. I had an acoustic set on first followed by two rock bands. 14 channels and four monitors sends were used and a fifth aux was used to provide an output to the subs, using the EQ on the mains and fifth aux as a makeshift crossover. (the band who's gear we were supposed to be using had blown tweeters in their Peavey tops, so I had to use my active RCFs and their bins for front of house)
The whole thing was stable, my wireless connection remained available throughout.