Behringer CMD Series

[Karlos Santos]

I just don't understand why anyone here thinks that Behringer owes them anything. It is up to Behringer when they will release their products and at what state they will be in. If you have a problem with waiting for things and you are over eager to have certain products in your hand, maybe this is not the hobby/industry for you.

I have waited for many products from the S4 to push, and most have been delayed in some state, way or form. Just remember that there are a lot of things worse then waiting. An epic fail of producing junk that no one will buy is the biggest problem. The way I see it, is this is the hottest thing since sliced bread here right now, everyone seems to be waiting to spend anywhere from $150 to several hundreds on their magical setup and there are no other controllers out there by any company who have created this much buzz and a following.

Be gracious they are creating a modular solution, wait your turn and stop the whining. If it is too much to handle, stop following this thread and go buy an S2, Z2 or a VCI-400

This is just bait for the people that want to bash on Behringer etc.

As I have said already... drop it. This means bashing and defending because it's just two sides of the same tatty argument.

So what's an example of a controller that you do like for library navigation and why?

Better. I'd be interested in nem0nics perspective. Personally I don't have to much issue with browser navigation, I have more of an issue with the browsers themselves. I have said many times that the most overlooked and the weakest aspect of Traktor is the Browser. Virtual DJ wipes the floor with Traktor with its one window browser.
But that's another topic for another day.

[MrPopinjay]

You think Traktor has a weak browser, you should try xwax some time

[Karlos Santos]

You think Traktor has a weak browser, you should try xwax some time

Me? Open Source? I'm not a hippy

Seriously though, is it good ? Or is my hangover preventing me see the irony in your post ?

[nem0nic]

Even though it was designed for the Ableton Live browser, the more I use the DC-1 nav section for DJ software the more I like it. The problem with X1 style browsing is it typically doesn't allow the user to easily toggle views to maximize browser space.

Virtual DJ wipes the floor with Traktor with its one window browser.

I think the browser in the Trattor iPad app is pretty sweet (I really like the effects implementation in it as well). I'm betting that these workflows make it into a new Traktor version.

[Karlos Santos]

I think the browser in the Trattor iPad app is pretty sweet (I really like the effects implementation in it as well). I'm betting that these workflows make it into a new Traktor version.

I have been pushing for such a browser in Traktor Pro for a long time. I actually made a photoshop mock up of a split browser during the Traktor DJ Studio 3 days (a long time before my involvement with NI).

I have made a lot of browser related requests for the app. I agree that TDJ should be the starting point for improved browsing in TPRO.

[MrPopinjay]

Me? Open Source? I'm not a hippy

Seriously though, is it good ? Or is my hangover preventing me see the irony in your post ?

It's just the worst. You give it a list of directories to scan and (with the default scan script) it parses artist, title and BPM from the file name (yes, currently we mostly write BPM to the filename) and then it just gives you a list of directories to select from and then the browser displays the tracks within the selected directory (or you can select a meta crate which displays all tracks). You can also type in words and it'll filter out all the tracks that don't have that word in the parsed title or artist name.
Playlists consist of a plain text file containing a list of paths to tracks. There's no writing to tracks from xwax, no editing playlists, no rescanning the library, no reading metadata, no album art, no BPM detection, nuffink. Vanilla xwax is really quite bad in this respect.

When I don't suck at programming I'm going to make a frontend for xwax that does all this library stuff better.

[Stewe]

I found the CMD MM-1 browsing section is great.

Untitled 24.jpg

The push encoder feels pretty nice and large load buttons makes loading tracks quick and easy for me. Only thing that's missing is velocity settings... Would be nice to map those buttons to display when deck is loaded.

Nem0nic, I assume that DC-1 browser is supported with this feature?

PS... Some red DJTT Chroma Caps should be here in day or two... I'll check them with MM-1 and share a pic for all if they fit nicely

[MrPopinjay]

Stewe, try sending the same midi note back to that button with a velocity of 01 or 02. Think of of those will be what you're after

[Stewe]

Nope. I'm aware of all velocity values since I have them both MM-1 and PL-1 completely mapped out in Traktor.

[nem0nic]

I found the CMD MM-1 browsing section is great.

Those 2 buttons bracketing the browse knob on the MM-1 were never meant to indicate a loaded track, because it's only capable of indicating status of 2 decks on an obviously 4 deck device. But yeah, it would be good for them to have indicator states. Not going to happen with the first version though. The MM-1 is really meant to be paired with the PL-1 (which handles track loading and deck state indication).

There are a couple things I would change on a new MM-1 type product. I feel like the top of the MM-1 is a little crowded. I originally wanted to keep all of the controls on the top of the device, but the more I look at it, the more I feel like moving the CUE section to the side (as is typical with DJ mixers). This would give me room to make the NAV section a little better, and to separate the 2 outputs.