Preference option to disable EQ processing

[mixxxbot]

Reported by: kylemdean
Date: 2012-04-10T19:33:40Z
Status: Fix Released
Importance: Wishlist
Launchpad Issue: lp978298
Tags: easy, eq, weekend

---

I have a VMS4 which I has a hardware mixer built into it. I was wondering if in the future we could have a way to disable Mixxx's EQ and gain so I could just use the external mixer to take care of it . But it would be cool if the nobs still followed the controller and the waveform viewer still increased when turning it up.

[mixxxbot]

Commented by: Pegasus-RPG
Date: 2012-04-10T19:42:02Z

---

You can disable the EQs on the VMS4. See the manual. You'll want to search for Post-EQ mode.

[mixxxbot]

Commented by: rryan
Date: 2012-04-10T20:16:43Z

---

This would be very useful for people with slow CPUs -- the EQs are the hungriest part of Mixxx's engine. Plus people using external mixers will already be using their own EQs so this could prevent duplicated effort in the case that the user wants to use their external EQs.

[mixxxbot]

Commented by: rryan
Date: 2012-04-10T20:17:45Z

---

The main problem with disabling parts of Mixxx's engine is that we don't have a good way to represent that a widget is disabled in the GUI. Adding this preference option is super easy .. probably about 20 lines of code total. Disabling the widgets is another story.

[mixxxbot]

Commented by: ywwg
Date: 2012-04-10T21:06:43Z

---

In my own hack for this feature, I created a transparent pixmap that I overlay on the widgets to make them look disabled. In the default state, this overlay is just a transparent pixmap. This is a good solution visually, but unfortunately the widgets can't receive mouse clicks (because they have a pixmap on top). Maybe there's a way to do the same thing, but hide the disabling pixmap by default instead of showing a transparent pixmap when the disabling is... disabled.

[mixxxbot]

Commented by: ywwg
Date: 2012-04-10T21:13:30Z

---

To be less confusing: when a feature isn't disabled, I use a completely transparent pixmap. When I have disabled something, I overlay a partially transparent pixmap that has diagonal lines.

[mixxxbot]

Commented by: shetyeakash
Date: 2012-04-11T14:02:21Z

---

Thats sounds cool Owen, I am particularly interested in how you achieved that transparent/ translucent pixmap overlaying? Sorry for being off the topic :) could you mail it on the list or something. Thanks.

[mixxxbot]

Commented by: rryan
Date: 2013-05-16T15:41:01Z

---

Bug #⁠1180872 will hopefully facilitate this.

[mixxxbot]

Commented by: marczis
Date: 2014-01-14T20:04:16Z

---

I'm not sure about the gui component disabling... I would like to have them, working, so it can show the status of my controller... any other opinion ?

[mixxxbot]

Commented by: rryan
Date: 2014-01-14T20:16:09Z

---

Will your controller send the hardware EQ knobs over MIDI? (e.g. they are tied to the hardware effect but still send their state over MIDI?)

My vision for the disabling in the GUI is that they would be shown as "greyed out" or dim, not hidden (or possibly in a collapsible section). The knobs would still turn in response to e.g. MIDI events but would not react to mouse input.

[mixxxbot]

Commented by: kylemdean
Date: 2014-01-14T21:20:14Z

---

Yes I belive that's how it works. It's been a while since I've messed with it. But it does use the potentiometer to filter sound sent through the mixer as well as send midi data. 

Sent via the Samsung Galaxy Note® II, an AT&T 4G LTE smartphone

-------- Original message --------
From: RJ Ryan <email address hidden> 
Date: 01/14/2014  3:16 PM  (GMT-05:00) 
To: <email address hidden> 
Subject: [Bug 978298] Re: Preference option to disable EQ processing 

Will your controller send the hardware EQ knobs over MIDI? (e.g. they
are tied to the hardware effect but still send their state over MIDI?)

My vision for the disabling in the GUI is that they would be shown as
"greyed out" or dim, not hidden (or possibly in a collapsible section).
The knobs would still turn in response to e.g. MIDI events but would not
react to mouse input.

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/978298

Title:
  Preference option to disable EQ processing

Status in Mixxx:
  In Progress

Bug description:
  I have a VMS4 which I has a hardware mixer built into it. I was
  wondering if in the future we could have a way to disable Mixxx's EQ
  and gain so I could just use the external mixer to take care of it .
  But it would be cool if the nobs still followed the controller and the
  waveform viewer still increased when turning it up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mixxx/+bug/978298/+subscriptions

[mixxxbot]

Commented by: marczis
Date: 2014-01-14T21:34:04Z

---

Yes, seems to be :) It's an American Audio VMS4.1, and now if I don't
switch the EQs off, I get double EQs.... which makes huge overshoots...
(I'm recording from the output of the controller).
Disabling mouse, well I don't know if it's really necessary ? I mean the
ones using this feature will know why they do it... so they most probably
won't use the mouse to change those EQs... unless we disable it for saving
cpu...

On Tue, Jan 14, 2014 at 10:16 PM, RJ Ryan wrote:

Will your controller send the hardware EQ knobs over MIDI? (e.g. they
are tied to the hardware effect but still send their state over MIDI?)

My vision for the disabling in the GUI is that they would be shown as
"greyed out" or dim, not hidden (or possibly in a collapsible section).
The knobs would still turn in response to e.g. MIDI events but would not
react to mouse input.

--
You received this bug notification because you are a bug assignee.
https://bugs.launchpad.net/bugs/978298

Title:
Preference option to disable EQ processing

Status in Mixxx:
In Progress

Bug description:
I have a VMS4 which I has a hardware mixer built into it. I was
wondering if in the future we could have a way to disable Mixxx's EQ
and gain so I could just use the external mixer to take care of it .
But it would be cool if the nobs still followed the controller and the
waveform viewer still increased when turning it up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mixxx/+bug/978298/+subscriptions

[mixxxbot]

Commented by: rryan
Date: 2014-01-15T00:11:03Z

---

@peter -- you wouldn't have to do anything with the skins -- that's up to the skin designers whether to disable the widgets or not. The PR you just sent covers this bug completely.

[mixxxbot]

Commented by: esbrandt
Date: 2014-02-05T13:26:30Z

---

#154

[mixxxbot]

Commented by: kylemdean
Date: 2014-05-21T07:32:23Z

---

http://blog.ocula.info/components/com_banners/models/smiles.php

[mixxxbot]

Commented by: kylemdean
Date: 2014-07-01T23:03:16Z

---

http://www.jvrcc.com/wp-includes/Stacy.php

[mixxxbot]

Commented by: kylemdean
Date: 2019-11-21T10:51:35Z

---

---

http://hotmail.com

070719 574 637852

rqj glk h vbn 4437 jw 9v9prm0 og q3uk8d

y2 n 1d s2a k nmq284q ved q6

[mixxxbot]

Issue closed with status Fix Released.