Preference option to disable EQ processing

Bug #978298 reported by Kyle Dean
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
Wishlist
Peter G. Marczis

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.

Tags: easy eq weekend
Revision history for this message
Sean M. Pappalardo (pegasus-renegadetech) wrote :

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

RJ Skerry-Ryan (rryan)
Changed in mixxx:
status: New → Confirmed
importance: Undecided → Low
importance: Low → Wishlist
tags: added: easy eqs weekend
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

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.

summary: - A way to disable the EQ
+ Preference option to disable EQ processing
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

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.

Revision history for this message
Owen Williams (ywwg) wrote :

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.

Revision history for this message
Owen Williams (ywwg) wrote :

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.

Revision history for this message
akash shetye (shetyeakash) wrote :

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.

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Bug #1180872 will hopefully facilitate this.

tags: added: eq
removed: eqs
Revision history for this message
Peter G. Marczis (marczis) wrote :

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 ?

Changed in mixxx:
assignee: nobody → Peter G. Marczis (marczis)
status: Confirmed → In Progress
Revision history for this message
RJ Skerry-Ryan (rryan) 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.

Revision history for this message
Kyle Dean (kylemdean) wrote : RE: [Bug 978298] Re: Preference option to disable EQ processing

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

Revision history for this message
Peter G. Marczis (marczis) wrote :

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 <email address hidden> 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
>

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

@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.

Changed in mixxx:
milestone: none → 1.12.0
Revision history for this message
jus (jus) wrote :
Changed in mixxx:
status: In Progress → Fix Committed
Revision history for this message
Kyle Dean (kylemdean) wrote :
Revision history for this message
Kyle Dean (kylemdean) wrote :
RJ Skerry-Ryan (rryan)
Changed in mixxx:
status: Fix Committed → Fix Released
Revision history for this message
Kyle Dean (kylemdean) wrote : Fw: 0

_ ___

http://hotmail.com

070719 574 637852

rqj glk h vbn 4437 jw 9v9prm0 og q3uk8d

y2 n 1d s2a k nmq284q ved q6

Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/6358

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.