Cacophony Forums
Unofficial Mackie User Forums => DL1608/DL806/DL32R/ProDX Mixers => Topic started by: gtrdudes on June 10, 2018, 04:06:41 PM
-
I won’t be specific. I don’t want to get anyone in trouble. Let’s just say Mackie is finally going to give us what a lot of people have asked for.
-
Without getting anyone into trouble do you have a guess on the time frame?
-
I asked if it was 3rd quarter. Sooner than that I’m told. I’m thinking weeks.
-
The reason I asked is that Mackie and most other companies usually announce product at one of the major shows. Nothing major until NAMM 2019. This would break with tradition.
-
I hear ya. But...
-
http://mackie.com/blog/master-fader-and-dl-series-live-stream
-
June 20th at 10 AM PST
Live stream on Mackie's FB page
-
Yawn V5.0 after 3 years of waiting!
V1.0 Oct 2012 (release of DL1608),
V2.0 Nov 12 2013,
V3.0 Nov 18 2014,
V4.0 Dec 9 2015 and now
V5.0 Nov-Dec 2018??
The usual carrot routine for product announcement by Mackie.
What other DL series? Can't wait! :)
-
If we can throw around conjecture, based on the top voted things on the Mackie Uservoice - probably MF will finally port over to systems other than iOS. New DL products - I would say Mackie is sorely missing a "stage-box" type device in the DL family. I use my 1608 solely as an interface, the iPad has never been docked. I'd love to see a 16-channel rackmount or compact box style setup with an internal power supply!!!
-
That will only happen if Uli lets the X-Air series be re-branded by Mackie. ;D
-
Facebook event: https://www.facebook.com/events/1847364518661101/
-
They've had some pretty lackluster rollouts the past year. I'll tell you one thing. If any of the new DL line don't have recallable preamps and fall into a price point near the Behringer XR or Midas ML18, forget it. It's a non-starter. I have to say, that XR18 is the best $600 investment I've made. I use the thing all the time and have had zero problems with it.
-
Sounds like a MF software release only. Maybe a hint on the next DL series like the DL32 intro.
-
They appear to be giving away an Android tablet during the live event which implies ... :eek:
-
I missed that tidbit. It's not on their official site AFAIK. Maybe the Android is for their ProDX16 ;D
-
They appear to be giving away an Android tablet during the live event which implies ... :eek:
Hopefully that they tested it, realized what a PITA Android support is across all the different manufacturers and flavors of Android OS, and are giving it away because they're staying focused on iOS...
I know it's not a popular hope, but having worked on cross-platform development, Android sucks for developers. Would rather they double down on iOS.
-
I missed that tidbit. It's not on their official site AFAIK.
In the event itself:
"During the live stream, we will give you all the details on how you can win a brand new tablet!"
If it wasn't an Android it would say 'iPad" not "tablet" ;) .
-
Would rather they double down on iOS.
As long as they still support the iPad2 I really have no need for android tablet support. It would be nice to have an Android phone app though so people could mix their own in-ears...
-
(http://mackie.com/sites/default/files/styles/half_page/public/dls_header2_1.jpg?itok=L3_SGJ3r)
-
Stage Boxes. With internal power supplies! Yes!
-
The time line for Master Fader Road map indicates that 5.0 will have DL16S and DL32S. and in 5.1 (Winter) it has DL1608 etc and Mac and PC compatibility. Does this mean there is nothing for DL1608 in the master fader 5.0? Do we(DL users) wait for 5.1?
-
The time line for Master Fader Road map indicates that 5.0 will have DL16S and DL32S. and in 5.1 (Winter) it has DL1608 etc and Mac and PC compatibility. Does this mean there is nothing for DL1608 in the master fader 5.0? Do we(DL users) wait for 5.1?
That's how I'm reading it, too.
-
Well, just as I thought. The surprise is that they bit the bullet for other than iPad control. To be sure it comes with restrictions as stated.
"DL16S and DL32S are compatible with iOS 10 or later, Android OS 6 or later, macOS 10.2 or later, and Windows 10 or later." So much for old iPads. At a MSRP of 999.99 for the Dl16S it should be in the high end (MAP) of the shelf. Oh the name should be interesting as well since the DL16 is a Midas product!
-
WiFi ONLY 2.4Ghz talk about useless!!
-
It looks like some big improvements to me. But I think I'll still prefer to bring my own router. :)
-
As I've stated many times before "the Devil is in the details". Time will tell. Sounds like their sales are in the dumpster and they needed to float the carrot to stop the bleeding. Their position in the past has been not to pre-announce except at major shows.
-
MSRP on the DL16 is $1k. So street will be $700-$800. 2 less inputs than the Behringer/Midas XR/MR. Did Mackie ever improve their FX algorithms? If not, this is a non-starter. For the same price, you can get the Midas MR18 or the Behringer XR18 for $500-600. Looks like Mackie copied Behringer on the design, that's a reversal. The Mackie app might be nicer, but it's not worth it at that price point.
-
Sweetwater has the DL16S listed for preorder at $699.99.
-
"DL16S and DL32S are compatible with iOS 10 or later, Android OS 6 or later.
Interesting - I just got a "you're forked" notice today from Box cloud drive- no longer supports KitKat as of 6/25 so my two 9" tablets are on their way to obsolescence :( . It's implied that MF 5.1 for the DL1608 won't run on any of my three iPads (two iPad 2's plus an original iPad Mini stuck on iOS 9.x) and my two tablets (that I use with my XR12) won't be supported :( . I did just get in today a $40 (shipped) 11" Android tablet that's running Nougat (and even has 5GHz :eek:) so maybe I'm not totally forked :) .
-
$700 DL16R vs. XR18 at $600 for most it won't fly. Mackie needs to adjust this. Add to this untried software and it will be awhile before reliability is established.
-
"DL16S and DL32S are compatible with iOS 10 or later, Android OS 6 or later.
Interesting - I just got a "you're forked" notice today from Dropbox - no longer supports KitKat as of 6/25 so my two 9" tablets are on their way to obsolescence :( . It's implied that MF 5.1 for the DL1608 won't run on any of my three iPads (two iPad 2's plus an original iPad Mini stuck on iOS 9.x) and my two tablets (that I use with my XR12) won't be supported :( . I did just get in today a $40 (shipped) 11" Android tablet that's running Nougat (and even has 5GHz :eek:) so maybe I'm not totally forked :) .
I know this sucks for you, but on iOS 81% of devices are on iOS11, 14% on iOS10 and 5% on iOS9 or earlier. As a developer, it doesn't make sense to cater to 5% knowing that number will drop far lower in September with iOS12 launching. However, it's a testament that older phones and tablets like an iPad Air 2 or an iPhone 5s are running 11.4. I'm including the links from Apple and Android below, as these are what developers are looking at when they look to see minimum OS to support. In addition, Mackie now has years of data showing them how many (or few) iOS9 devices are being used; my guess is it's a lot lower than 5% and not worth supporting code that was last updated 2 years go - especially when you have 95% of devices running iOS 10 or higher. https://developer.apple.com/support/app-store/
Android, on the other hand, is a scattered S&*t show. Only 5.7% of Android phones are on Oreo, and only 62% are on Marshmallow or higher - but partially because Android didn't specify what needed to be included in phones and tablets to make them more future proof, and partially because the android team doesn't understand hardware and consumers - people aren't upgrading their phones/tablets yearly. https://developer.android.com/about/dashboards/
KitKat and Lollipop is/was a pain in the ass as code needed to be different for each and every flavor of Android by each tablet and phone manufacturer. It's also only 10.3% of installed Android users. So Mackie is being smart and realizing that if they're going to support Android, they need to support the majority of users on the OS version that is easier to code across all Android-powered tablets and phones.
Blame Android, not Mackie on this. I had to work on KitKat compatibility for app-enabled products, and it sucks. While it sucks for us with older tablets, this is the right thing for them to do to keep development costs from spiraling out of control.
-
So, for DL16S, the usb to hard drive recording is not there (that's what I saw in the matrix).. then I read that it should be recorded in a pc/mac connected to the mixer on the usb port. If my pc is far from the stage -then do we need a longer usb cable to connect? How long cables are available? Any thing I missed here?
-
USB mixer connection is for desktop recording, so short distances.
If you want to record from afar, you can do it either via WiFi or more likely a CAT 5e cable connected to your Mac/PC.
I also noticed that direct recording from the stage box a la the DL32R is no more, which seems odd, but they may have wanted to keep that as a way to differentiate between the DL32R and the new one. Or just they didn't want to add another port and add more cost...
-
>>you can do it either via WiFi or more likely a CAT 5e cable connected to your Mac/PC.
Are you saying we can record 16 tracks using wifi? I thought it has to be directly connected to USB port of the mixer.
The second point about cat 52 cable... you are suggesting connecting to the DAW on pc from the ethernet port of the mixer. Can we record 16 tracks using this interface as well?
I thought recording is only from usb port.
-
I stand corrected - it looks like the only way you can record is with a long USB cable, which is dumb. Ethernet cable appears to only extend range for using airport Express or direct connection to a laptop for Master Fader, but may not be carrying audio. Which it easily could...
Feels like they took the one feature on the DL32R that people liked and instead of adding it to both new ones, took it out for no apparent reason.
-
"DL16S and DL32S are compatible with iOS 10 or later, Android OS 6 or later.
Interesting - I just got a "you're forked" notice today from Dropbox - no longer supports KitKat as of 6/25 so my two 9" tablets are on their way to obsolescence :( . It's implied that MF 5.1 for the DL1608 won't run on any of my three iPads (two iPad 2's plus an original iPad Mini stuck on iOS 9.x) and my two tablets (that I use with my XR12) won't be supported :( . I did just get in today a $40 (shipped) 11" Android tablet that's running Nougat (and even has 5GHz :eek:) so maybe I'm not totally forked :) .
I know this sucks for you, but on iOS 81% of devices are on iOS11, 14% on iOS10 and 5% on iOS9 or earlier. As a developer, it doesn't make sense to cater to 5% knowing that number will drop far lower in September with iOS12 launching. However, it's a testament that older phones and tablets like an iPad Air 2 or an iPhone 5s are running 11.4. I'm including the links from Apple and Android below, as these are what developers are looking at when they look to see minimum OS to support. In addition, Mackie now has years of data showing them how many (or few) iOS9 devices are being used; my guess is it's a lot lower than 5% and not worth supporting code that was last updated 2 years go - especially when you have 95% of devices running iOS 10 or higher. https://developer.apple.com/support/app-store/
Android, on the other hand, is a scattered S&*t show. Only 5.7% of Android phones are on Oreo, and only 62% are on Marshmallow or higher - but partially because Android didn't specify what needed to be included in phones and tablets to make them more future proof, and partially because the android team doesn't understand hardware and consumers - people aren't upgrading their phones/tablets yearly. https://developer.android.com/about/dashboards/
KitKat and Lollipop is/was a pain in the ass as code needed to be different for each and every flavor of Android by each tablet and phone manufacturer. It's also only 10.3% of installed Android users. So Mackie is being smart and realizing that if they're going to support Android, they need to support the majority of users on the OS version that is easier to code across all Android-powered tablets and phones.
Blame Android, not Mackie on this. I had to work on KitKat compatibility for app-enabled products, and it sucks. While it sucks for us with older tablets, this is the right thing for them to do to keep development costs from spiraling out of control.
Sorry but all that is a load of propaganda bollocks. Most of the musicians i know seem to have ipad2s. I've got a 3 and a mini and despite their age(!!!) they still work fine and the batteries are holding up. These forced upgrades are a disgrace. We have been brainwashed into thinking that anything digital has a half-life of about 1 year after which we are shamed into updating at great expense. As far as I'm concerned Mackie can stuff their updates, they started with a market leading product with the best software and squandered their advantage with penny pinching support and some spectacular bugs. Now they are bringing out an overpriced Behringer clone. AH here i come.....
-
Nedorama:>>Feels like they took the one feature on the DL32R that people liked and instead of adding it to both new ones, took it out for no apparent reason.
They may be thinking if they provided all the good stuff that DL32R offered, then then there will be not much differentiation and will have to discontinue DL32R model!
I am not defending their position- but guessing what their thinking might be !!
-
$700 DL16R vs. XR18 at $600 for most it won't fly. Mackie needs to adjust this. Add to this untried software and it will be awhile before reliability is established.
If they had made it a 2U I'd be interested...
-
A 24 channel with 12 ouputs would have filled the gap
-
A 24 channel with 12 ouputs would have filled the gap
Yah, I was hoping to see a DL2412 to fill the niche that Behringer skipped over...
-
A 24 channel with 12 ouputs would have filled the gap
Yah, I was hoping to see a DL2412 to fill the niche that Behringer skipped over...
If Behringer isn't offering it, there must not be a market for it. :facepalm:
-
A 24 channel with 12 ouputs would have filled the gap
I was told it was gonna be a 16 and a 24. Seems logical. Why another 32?
-
Nedorama:>>Feels like they took the one feature on the DL32R that people liked and instead of adding it to both new ones, took it out for no apparent reason.
They may be thinking if they provided all the good stuff that DL32R offered, then then there will be not much differentiation and will have to discontinue DL32R model!
I am not defending their position- but guessing what their thinking might be !!
I think you could be right, but given the price point and product similarity, I see these killing off the DL32R at some point due to cannibalization - but I look at that and get excited because down the road the DL32R will get discounted, and may make sense to purchase for me.
-
"DL16S and DL32S are compatible with iOS 10 or later, Android OS 6 or later.
Interesting - I just got a "you're forked" notice today from Dropbox - no longer supports KitKat as of 6/25 so my two 9" tablets are on their way to obsolescence :( . It's implied that MF 5.1 for the DL1608 won't run on any of my three iPads (two iPad 2's plus an original iPad Mini stuck on iOS 9.x) and my two tablets (that I use with my XR12) won't be supported :( . I did just get in today a $40 (shipped) 11" Android tablet that's running Nougat (and even has 5GHz :eek:) so maybe I'm not totally forked :) .
I know this sucks for you, but on iOS 81% of devices are on iOS11, 14% on iOS10 and 5% on iOS9 or earlier. As a developer, it doesn't make sense to cater to 5% knowing that number will drop far lower in September with iOS12 launching. However, it's a testament that older phones and tablets like an iPad Air 2 or an iPhone 5s are running 11.4. I'm including the links from Apple and Android below, as these are what developers are looking at when they look to see minimum OS to support. In addition, Mackie now has years of data showing them how many (or few) iOS9 devices are being used; my guess is it's a lot lower than 5% and not worth supporting code that was last updated 2 years go - especially when you have 95% of devices running iOS 10 or higher. https://developer.apple.com/support/app-store/
Android, on the other hand, is a scattered S&*t show. Only 5.7% of Android phones are on Oreo, and only 62% are on Marshmallow or higher - but partially because Android didn't specify what needed to be included in phones and tablets to make them more future proof, and partially because the android team doesn't understand hardware and consumers - people aren't upgrading their phones/tablets yearly. https://developer.android.com/about/dashboards/
KitKat and Lollipop is/was a pain in the ass as code needed to be different for each and every flavor of Android by each tablet and phone manufacturer. It's also only 10.3% of installed Android users. So Mackie is being smart and realizing that if they're going to support Android, they need to support the majority of users on the OS version that is easier to code across all Android-powered tablets and phones.
Blame Android, not Mackie on this. I had to work on KitKat compatibility for app-enabled products, and it sucks. While it sucks for us with older tablets, this is the right thing for them to do to keep development costs from spiraling out of control.
Sorry but all that is a load of propaganda bollocks. Most of the musicians i know seem to have ipad2s. I've got a 3 and a mini and despite their age(!!!) they still work fine and the batteries are holding up. These forced upgrades are a disgrace. We have been brainwashed into thinking that anything digital has a half-life of about 1 year after which we are shamed into updating at great expense. As far as I'm concerned Mackie can stuff their updates, they started with a market leading product with the best software and squandered their advantage with penny pinching support and some spectacular bugs. Now they are bringing out an overpriced Behringer clone. AH here i come.....
the iPad 2 is 7 years old - while your musician friends may be using them, overall few people are, and I'm sure Mackie looked at the % of OS on Master Fader and realized OS10 was the farthest back that made reasonable sense.
These aren't forced upgrades - no one is putting a gun to your head to upgrade to 5.0, which may or may not have any to-die-for features that aren't in the current version. If you don't want to upgrade from your iPad 2, you still have a great mixing solution with MF 4.x and the DL1608. Asking for 7 year old anything to be compatible with the latest and greatest software is unreasonable and doesn't make financial sense for Mackie, Apple or other manufacturers. I know at some point my iPad Air that I bought in 2014 will be unable to run iOS13 or work with other apps, but I've already gotten 4 years out of it. Same with my 2013 MacBook Pro, that's rocking Pro Tools 2018 well -- but I know that at some point, Avid will drop support as they try to push forward.
-
Can someone explain to me how this '4 stereo FX processors' is useful and how it can be used?
Thanks..
-
I see these killing off the DL32R at some point due to cannibalization.
don't hold your breath,
the DL32R is necessary to operate the Axis DC16.
None of the (soon to be released) products have Dante ability and therefore, it would make no sense for Mackie to ditch the DL32R anytime soon since a DC16 requires a DL32R connected via Dante.
-
Can someone explain to me how this '4 stereo FX processors' is useful and how it can be used?
Thanks..
Each channel has 4 stereo FX processors. You can select which FX to use for each of the 4 processors. For example, you can choose large room reverb for one, delay for another, and so on. You can also adjust the parameters for each FX.
-
Each channel has 4 stereo FX processors.
Not quite - this is about the "send effects", not the channel effects.
@Ram: Think of these as the classic 19'' effect processors you used to use with your mixing desk. They are common to all channels; you can control how much of your signal you send to the effect box ("effect send"), then the signal from all channels will be mixed, processed by the FX processor and returned back to the main mix (usually).
Currently, the DL32R has two dedicated reverb processors and one delay; the DL1608 only has one of each. These are fixed, so processor 1 is ALWAYS a reverb (although you can set the parameters differently between reverb 1 and reverb 2 on the DL32).
The new system, as I understand it, means that:
a) we get more parallel send effecs (4 instead of 3 on the DL32R)
b) we can freely choose what type of effect each slot will be, so if I want three different reverbs, I can have them; if I want one reverb and three different delays - presto! Or any kind of other effect that Mackie will provide (chorus, flanger, exciter, whatever...)
The one limitation however remains: these will still be SEND effects only AFAIK. So no plug-in-effects that you can use as insert on a specific channel. But of course you can abuse a send effect as an insert (send a channel to it pre-fader, mute the channel's main output and use the effect return faderinstead of the channel fader to set volume), but that's a bit convoluted and counter-intuitive.
Cheers,
Torsten
-
@Michael: the lengthy and basic explanation wasn't aimed at you, but at Ram who asked the original question.
I know that you know all about send and insert effects ;D
-
Thanks Toreston,
It was really helpful.
So -in DL16S, i could use :(just an example)
for channel 1:hall reverb from fx1
for channel 2:plate reverb from fx2
for channel 3:medium room reverb from fx3
for channel 4:small room reverb from fx4
Other channels can use any of the above four?
Is this right?
-Ram
-
So -in DL16S, i could use :(just an example)
for channel 1:hall reverb from fx1
for channel 2:plate reverb from fx2
for channel 3:medium room reverb from fx3
for channel 4:small room reverb from fx4
You COULD do that, but that's not how you'd normally go about things.
In normal mix practice, I have a "universal" reverb (medium length, not too bright) that I can use to "flesh out" some sounds, plus a room reverb to create depth in my mix (more room = sound further back in the mix). So I usually have these two in my reverb slots. Then, I normally have a stereo delay with different delay times for left and right and without any repeats for my lead vocals.
So the idea about send effects is that you can add a little dose of them to any number of channels. E.g. my snare drum and tom toms all get a little bit of "universal reverb" (toms more than snare, usually); all my vocal channels get a bit of the stereo delay, and all percussion channels get quite a bit of the room reverb, so they're not so up-front in the mix. Essentially, you have different "flavors" of effects you can add to all your channels to taste via the "send" sliders (or via the effect channel mix view). So it could be useful to add BOTH a bit of delay AND room to some channels - no problem!
So with the DL16S, ALL channels can use ANY combination of the four effects slots; the effects are not allocated to channels at all.
Hope that clarifies things!
Cheers,
Torsten
-
Torsten,
Thanks. That explains my question very well!
-Ram