MixControl Pro Discontinued, V2 TBA.

[Nielzie]

Some good points made there Agreed. Agreed

[rlahalla]

While these are good points, looking back on this thread, you'll notice that I no longer have contact with the original developer or the codebase. I'm discontinuing it because I absolutely need a way of fixing bugs. Without the developer, I cannot do so.

[RexXx]

Bought MixControl some days ago and happy with it.
Love the two skin options and the layout. Fits very well with my screen resolution in Studio One. Hope to see something similar or a scalable gui in MC2.

I like also, that the developer speaks so open about the current status. Very sympathetic.

MC1 is a great intro offer for MC2! Thanks!

[Agreed]

While these are good points, looking back on this thread, you'll notice that I no longer have contact with the original developer or the codebase. I'm discontinuing it because I absolutely need a way of fixing bugs. Without the developer, I cannot do so.

I can respect that, and I look forward to the release of 2. Don't be afraid to charge for it, either, you put out something worth paying for, people will buy it

Edit: I'm just glad that as far as I can tell, not bug one in Reaper 4 64-bit. The only thing I wish I could change is the spectrum analyzer's speed - even at its fastest setting it's a bit slower than I'd like. But there are great tools, commercial and free, for metering, and it provides a plenty clear picture of what the general frequencies are to EQ effectively.

Everything about this is remarkably feature complete, easy to work with (the tooltips plus the immediate data displayed when hovering over knobs is extremely pro!) and, somewhat importantly, great sounding . I wish that you did still have access to the development and codebase proper because it would be incredible if you could do a feature update on it that lets you use modules independently; when T-Racks 3 Deluxe went Singles. I know under present circumstances that just can't happen and totally understand. And for what it's worth the resource hit is quite low per-instance, really seems like thought was put into feasibly having Mix Control Pro on each track for a "console" flavor/experience ITB. (I guess, anyway - was that a consideration? It worked out, regardless, love it, just curious if it was ground-up or something that's a happy accident )

Man, I don't even know what I'd want to see in MC2 compared to MC1 apart from the really minor kvetch that the spectrum analyzer. I suppose those who do experience bugs with their DAWs will appreciate a new release to correct those. As for me, just... More and better, you came up with some great ideas the first time that are very friendly to workflow and easy on the ears, so I trust your sophomore Mix Control Pro release will be exceptional.

[rlahalla]

Man, I don't even know what I'd want to see in MC2 compared to MC1 apart from the really minor kvetch that the spectrum analyzer. I suppose those who do experience bugs with their DAWs will appreciate a new release to correct those. As for me, just... More and better, you came up with some great ideas the first time that are very friendly to workflow and easy on the ears, so I trust your sophomore Mix Control Pro release will be exceptional.

I have some cool ideas that are included. I won't mention anything until I know that they are definite, but I'm open to suggestions as well

[Nielzie]

While these are good points, looking back on this thread, you'll notice that I no longer have contact with the original developer or the codebase. I'm discontinuing it because I absolutely need a way of fixing bugs. Without the developer, I cannot do so.

But Reason, don't you have the right to use the codebase? I assume that TeamDNR owns the product rights, although it was developed by a 3rd party developer.

[cyphersuit]

donation ...complete

[Agreed]

Man, I don't even know what I'd want to see in MC2 compared to MC1 apart from the really minor kvetch that the spectrum analyzer. I suppose those who do experience bugs with their DAWs will appreciate a new release to correct those. As for me, just... More and better, you came up with some great ideas the first time that are very friendly to workflow and easy on the ears, so I trust your sophomore Mix Control Pro release will be exceptional.

I have some cool ideas that are included. I won't mention anything until I know that they are definite, but I'm open to suggestions as well

Well since you asked...

Add more options to the Saturation section, maybe a drive parameter to really nasty things up?

Add a soft and a hard clipper as options to the Limiter section?

More sidechain, you've got a really cool sidechain functionality and I'd love it on every module in the software. Seriously. Sidechain on the limiter with the ability to clip what's chained - that'd make bass hit like a train.

Eh, more and better, and sincerely, wishing you good luck getting it taken care of in a timely fashion with the level of professionalism and polish that it has now. Love to see a great tool made better.

[el-bo (formerly ebow)]

- double-click to add new eq frequency point

- 'singles' versions, even if only the eq

[Compyfox]

Another vote for "singles".

The EQ is definitely cool. Though I'd love to see a 7 band EQ with additional LP/HP, like the PT EQ. Or at least 5 bands with additional LP/HP.


Then, what about reference levels?
For the meters, the compressor and saturation stages, etc. A 0dBFS/-18dBFS switch would do the trick for most I think.

[el-bo (formerly ebow)]

additional LP/HP

yes

[rlahalla]

While these are good points, looking back on this thread, you'll notice that I no longer have contact with the original developer or the codebase. I'm discontinuing it because I absolutely need a way of fixing bugs. Without the developer, I cannot do so.

But Reason, don't you have the right to use the codebase? I assume that TeamDNR owns the product rights, although it was developed by a 3rd party developer.

No, Michael owns the codebase outright. Buying a codebase such as that would be beyond my financial control.

[saintjohnbaxter]

Just chipped in a bit (got a $225,000 bill to fix house so can't spare much just yet - imagine how much lovely gear that would buy!). Looking forward to v2, however long it takes you.

[Nielzie]

While these are good points, looking back on this thread, you'll notice that I no longer have contact with the original developer or the codebase. I'm discontinuing it because I absolutely need a way of fixing bugs. Without the developer, I cannot do so.

But Reason, don't you have the right to use the codebase? I assume that TeamDNR owns the product rights, although it was developed by a 3rd party developer.

No, Michael owns the codebase outright. Buying a codebase such as that would be beyond my financial control.

Ahh ok I didn't know that. I always thought that final product and underlying code where to be seen as one, in the view of product and copy "rights".

[rlahalla]

While these are good points, looking back on this thread, you'll notice that I no longer have contact with the original developer or the codebase. I'm discontinuing it because I absolutely need a way of fixing bugs. Without the developer, I cannot do so.

But Reason, don't you have the right to use the codebase? I assume that TeamDNR owns the product rights, although it was developed by a 3rd party developer.

No, Michael owns the codebase outright. Buying a codebase such as that would be beyond my financial control.

Ahh ok I didn't know that. I always thought that final product and underlying code where to be seen as one, in the view of product and copy "rights".

Yeah, if he was my actual "employee" it would have all been considered as DNR property, but he was a contractor, and a gracious one at that. He didn't even really get any money for the last update and unconditionally helped me out to get MCP to a usable state. He's definitely one of the best developers I have ever worked with.