Hmm, interesting sketch. I like the idea of having the EQs and volume
fader adjacent to the waveforms. That is a more efficient use of space
than putting the mixer between the decks. However, in your mockup, I
think it would be easy to confuse which controls are for which deck. I
think moving
If I recall it correct, it should help.
This has also the benefit that you can see more tracks in the library.
Am 08.06.2015 um 23:10 schrieb re-cy...@hushmail.com:
Interesting re: CPU. What do you think about decreasing the height
but keeping the width re: CPU?
~RAWRR
On Mon, 08 Jun 2015
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Interesting re: CPU. What do you think about decreasing the height
but keeping the width re: CPU?
~RAWRR
On Mon, 08 Jun 2015 21:00:52 + Daniel Schürmann
dasch...@mixxx.org wrote:
Hi Markus,
Nice mock-up.
In the past we had issues with four
Oh, the three filter knobs next to each deck aren't meant to all be
filter knobs. They could be effect superknobs and/or effect parameters.
On 06/08/2015 05:13 PM, Be wrote:
Hmm, interesting sketch. I like the idea of having the EQs and volume
fader adjacent to the waveforms. That is a more
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So there's the space beneath the left deck - where the preview deck
lives. The space on the other side is empty. Can the micaux array
get shrunk a bit and fit over there? That would save some space,
plus be nice and symmetrical.
~RAWRR
On Mon, 08
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is there any framework currently or on the horizon for *any* of the
various scrollbars to be midi-scriptable?
In my fantasy world if this was ever implemented the rate would be
adjustable, and the track in the center of the window would always
be
Hi,
I did recently, as asked by RJ, added some coding style commit in a PR,
particularly on the following rule:
_Plain-text comments should be separated from the comment symbol by a
single space. Commented-out code should have no space between the
comment symbol and the code_
I'm not sure
Hi,
I have some good experience with the Eclipse Formatter:
http://www.mixxx.org/wiki/doku.php/eclipse?s[]=eclipse#eclipse_code_formatter
We have to be careful not to put clutter on a PR just because using an auto
formatter.
This may happens if an auto formatter changes code that already meets
On 06/08/2015 09:22 AM, Daniel Schürmann wrote:
Hi,
I have some good experience with the Eclipse Formatter:
http://www.mixxx.org/wiki/doku.php/eclipse?s[]=eclipse#eclipse_code_formatter
We have to be careful not to put clutter on a PR just because using an auto
formatter.
This may happens
Any thoughts on the general outline I proposed?
[master gain][balance][head mix][head gain][4/2 deck toggle]
[Deck 1][Deck 1/2 mixer][Deck 2]
waveform 1
waveform 2
waveform 3
waveform 4
[Deck 3][Deck 3/4 mixer][Deck 4]
I'm using Mixxx without controller without scratching and so on, just
10 matches
Mail list logo
