on the djtechtools forum the RMX was always discussed quite a bit which is
the same internals as the "control steel" i think? so my vote would be for
that one.
could also always add native hid support within mixxx which can give extra
resolution to the various pots/faders etc
On 15 March 2013 01:
>
> When you use their own latching mode you can set values for lights that
> are on the inactive page. When you switch to that page, they'll already
> be on. It's a really nice system because it means the host app doesn't
> need to know anything about the latching system.
>
yep, that is quite c
>
> >
> > it might also be nice to have a builtin layer system with led recall.
>
> I definitely think this would be useful. I'm working with the Xone K2
> right now and although it has its own latching system there is also a
> mode where the lights and buttons are completely driven by software.
we definitely need them, which is basically part of the modifier system we
have been discussing:
http://mixxx.org/wiki/doku.php/modifier_system
so you'd be able to map a control to change or query a modifier from xml,
javascript or the gui.
it might also be nice to have a builtin layer system wi
owen,
pegasus_rpg said you may find a cross-platform high resolution timer useful
for calculating elapsed times. i've used this code and seems very good:
http://www.songho.ca/misc/timer/timer.html
i'm using that in my experimental midi clock code to calculate elapsed time
and work out when to se
On 28 May 2012 23:13, Max Linke wrote:
> Also what do you think of the option to view the library with a grid of
> Album Covers? I've read in some Bug reports that people miss the
> possibility to search through your library by picture when they use
> DJ-Software and I've thought this could be a
On 28 May 2012 21:11, Owen Williams wrote:
> I'll see if I can get master_sync in slightly better shape.
>
> Right now when it starts up, all decks are set to slave mode and the
> master block is set to 124 bpm (and you can't change it). the "beat"
> message is the master clock reporting each do
>
> What do you mean by clock offset value?
>
an offset, either positive or negative, that is applied to every clock tick
and start/stop messages. even with zero jitter it takes a non-zero amount
of time for the code to realise it needs to send a clock message and for
the other end to receive it a
>
> Midi clock in/out is (hopefully) going to be part of my master sync
> work. Master sync should be in by 1.12 although I don't know if midi
> will be done in time for it. It should be fairly easy to implement,
> though. Mixxx will have a master sync object that not only knows what
> bpm mixxx
On 27 May 2012 09:17, Sean M. Pappalardo - D.J. Pegasus <
spappala...@mixxx.org> wrote:
> I started thinking of how to implement this while creating that, and we're
> going to have a problem with clock drift because we don't currently have a
> timing source with microsecond precision. (Since there
you sure the xponent isn't sending out an 0xEx pitchbend message for pitch
control?
i remembered i also had an issue with that script.pitch() helper function
when i wrote my djtech cdj101 script so i ended up rolling my own too - but
i think i've just noticed the real reason...
script.pitch = fun
>
>
> On 05/20/2012 11:51 PM, zestoi wrote:
>
>> callbacks would be very nice... RtMidi supports them and i've found it
>> much better than polling for incoming events (that i was originally
>> using for my own projects)
>>
>
> It's straightforward
callbacks would be very nice... RtMidi supports them and i've found it much
better than polling for incoming events (that i was originally using for my
own projects)
PortMIDI does support blocking reads - so in theory shouldn't be hard to
implement? or the reader thread could just block instead of
also in case anyone is interested, here's the wiki page i put together with
a summary of what me and hile have been discussing on irc re: the hid api
http://mixxx.org/wiki/doku.php/hid_device_api
and my own hid script for the hercules mk2 from before we tried to merge
ideas:
http://djism.com/mi
On 10 May 2012 02:25, ewan colsell wrote:
> i suppose i didn't explain myself well enough, simple midi mapping is
> fine, but i'm not getting anywhere making a mapping with shift key that
> lets me use the jog wheel to select tracks in the file browser.
>
>
my first attempt at a mapping for mixxx
On 2 May 2012 18:36, William Good wrote:
> Considering the number of requests we get for "can I use my trackpad
> for $x" (where $x tends to be scratching but who knows what else) I'd
> say no.
i've used my touchpad as an XY pad for effects before. no need for any
blacklists... tho not all hid
On 1 May 2012 01:09, Ilkka Tuohela wrote:
> for hid devices i've found that just matching on dev->product_string is
> enough. if someone has two controllers of the same type plugged in the 2nd
> instance just has to make sure it doesn't try to open a device that has
> already been opened. the ser
On 30 April 2012 06:02, Sean M. Pappalardo - D.J. Pegasus <
spappala...@mixxx.org> wrote:
> As RJ said, that's an unintended-consequences bug that I need to examine
> more closely when I get back to my controller pile at home. (Still
> traveling at the moment.) I added that so the serial number wo
On 29 April 2012 05:17, RJ Ryan wrote:
> Sorry for the segfaults -- that was a general bug with the controller
> branch which I already fixed in trunk but hadn't merged those fixes into
> the branch. If you pull/update now you should get them.
>
excellent ;) pulled in the updates and all those i
just built features_point_and_click. a few issues, tho i am coming to this
as a total noob - so please excuse any stupidness:
* had to copy res/schema.xml to /usr/share/mixxx before it would run
* connected my icon idj, went into enable the controller but the wizard
button isn't clickable until i
On 27 April 2012 19:13, S.Brandt wrote:
>* To make the Wizard useful for the max. number of features the
> possibility to use a shift modifier is missing.
> Some Controllers (i.e Vestax) have double assignments of buttons
> but send the same midi for that particular button even
>
> If you want to try it out before merge, the code is here
> https://code.launchpad.net/~mixxxdevelopers/mixxx/features_point_and_click
>
this all sounds like great stuff :) i'll grab that from bzr and give it a
go later.
> * (*Please give me feedback on this one) *I think our rule to not proc
On 27 April 2012 06:59, Philip Whelan wrote:
>
> I disagree here, VDJ's syntax is horrible and the language itself is
> probably not very feature complete. I know that is not as relevant for
> normal (or even most power users), but no reason to re-write our own
> just for that. The Javascript eng
m keen to help with coding if i can - only recently started looking thru
source code tho.
/zestoi
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has ch
24 matches
Mail list logo
