Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

On Sun, Jul 9, 2017 at 9:22 PM, Radu Suciu wrote: > Just want chime in that mapping controllers in Mixxx by binding to Ctrla > callbacks and outputs directly in JS, without having to map midi signals in > XML beforehand would make for a great experience. > Thanks for the

Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

On Sun, Jul 9, 2017 at 9:23 PM, Daniel Schürmann wrote: > Hi Harry, > > Ok, you are probably right. > > I did not follow the early discussion, but I would agree to the Linux > Audio developers, that relying on those profiles will just not work. > A powerful mapping system is

Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

On Sun, Jul 9, 2017 at 7:04 PM, Daniel Schürmann wrote: > Hi Harry, > > thank you for pointing me to ctlra_info_get_name. > That is a good help to locate the event on the controller. > Yep, and together with the layout info, it is enough to provide good UX on what it is, and

Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

Hi Harry, thank you for pointing me to ctlra_info_get_name. That is a good help to locate the event on the controller. However, I think we have the chance here to also represent the intended use of a control in machine readable way and be also OSC compatible. For example I have two gain

Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

I agree with Harry, assigning meaning to each event should be out of the scope of Ctlra. There is far too much variability between controllers for that to be useful, hence why no such system has been invented for MIDI DJ controllers and why device-specific mappings exist. One nice thing about

Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

On Sun, Jul 9, 2017 at 1:23 PM, Daniel Schürmann wrote: > Hi Harry, > > > At no point to I think Ctlra will *require* also using TCC. It just so > happens that they complement each other well for my use-cases. > > That seams to be a good approach. If the architecture allows

Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

Hi Harry, > At no point to I think Ctlra will *require* also using TCC. It just so happens that they complement each other well for my use-cases. That seams to be a good approach. If the architecture allows to put Ctlra drivers into runtime loaded object files, it does not matter which

Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

On Sun, Jul 9, 2017 at 11:21 AM, Daniel Schürmann wrote: > Hi Harry, Hi Be, > > here some comments: > > IMHO arguing about If C or JS is easier will not lead us ahead in this > discussion. > Good point - apologies for the rat-hole. > > As noted above, we can take TCC off

Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

Hi Harry, Hi Be, here some comments: IMHO arguing about If C or JS is easier will not lead us ahead in this discussion. Both are easy and hard in different aspects. It is all an issue about "Know your tools". The embedded developers in the controller companies will be most likely C-Natives.

Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

Hi Harry, I read the paper for the presentation at LAC 2017 that you linked on IRC: http://musinf.univ-st-etienne.fr/lac2017/pdfs/01_C_E_137795.pdf Going along with what I mentioned in my previous post, I do not think Ctlra should be aware of the "userdata". IMO that should be left to the

Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

On 07/08/2017 06:51 PM, Harry van Haaren wrote: 3. The programming language. It is a lot easier to find someone who knows JavaScript, or at least kinda knows JavaScript enough to get by for a small project, than it is to find someone who knows C. For people with minimal or no

Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

On Sat, Jul 8, 2017 at 10:32 PM, Daniel Schürmann wrote: > I share Be's concerns about TinyCC compiler. On one hand it is available > in the Ubuntu repos, on the other hand it is "not recommended for > production use" in the explaining text. > > But that is not a big problem.

Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

On Sat, Jul 8, 2017 at 9:00 PM, Be wrote: > Thanks for taking up this project! Reading your proposal on the wiki page, > the way you intend to integrate into Mixx's ControllerManager and > Controller classes makes more sense now. > Thanks, and glad to hear it. > The big question

Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

On 07/07/2017 11:37 AM, Daniel Schürmann wrote: In terms of am everage use, a library is updated by the various Linux distros in a two years cycle. If someone chooses a distro with a slow release cycle like Ubuntu LTS or Debian stable they should understand that access to the latest software

Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

On 07/08/2017 04:32 PM, Daniel Schürmann wrote: I think we have to distinguish between two areas of device depended code. 1. The driver part, which presents the controller in a generic way like it already happens with midi controllers 2. The application mapping, to adapt application features to

Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

Hi Be, Hi Harry, I share Be's concerns about TinyCC compiler. On one hand it is available in the Ubuntu repos, on the other hand it is "not recommended for production use" in the explaining text. But that is not a big problem. For me it makes no difference if we dynamic ling a device.so file

Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

Thanks for taking up this project! Reading your proposal on the wiki page, the way you intend to integrate into Mixx's ControllerManager and Controller classes makes more sense now. The big question I am wondering about is the process of creating the mappings from Ctlra events to Mixxx's

Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

On Sat, Jul 8, 2017 at 10:39 AM, Sébastien Blaisot wrote: > Le 08/07/2017 à 03:00, Harry van Haaren a écrit : > > On Fri, Jul 7, 2017 at 8:45 PM, Sébastien Blaisot > wrote: > > >> Mixxx is a cross-platform application (Linux, MacOS, Windows). >> > Is ctrla

Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

Le 08/07/2017 à 03:00, Harry van Haaren a écrit : On Fri, Jul 7, 2017 at 8:45 PM, Sébastien Blaisot > wrote: Mixxx is a cross-platform application (Linux, MacOS, Windows). Is ctrla also a cross-platform library ? Currently nope, it is a

Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

On Fri, Jul 7, 2017 at 8:45 PM, Sébastien Blaisot wrote: > Hi Harry, > Hey! > Mixxx is a cross-platform application (Linux, MacOS, Windows). > Is ctrla also a cross-platform library ? > Currently nope, it is a WIP library developed and tested on Linux only. The APIs are

Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

Hi Harry, Mixxx is a cross-platform application (Linux, MacOS, Windows). Is ctrla also a cross-platform library ? If this is not the case, it is a show stopper IMHO. As far as I can see, it only seems to be documented under linux. Regards, sb Le 06/07/2017 à 23:57, Harry van Haaren a écrit

Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

On Fri, Jul 7, 2017 at 5:37 PM, Daniel Schürmann wrote: > Hi Harry, > Hi! > I have looked a bit closer to the concepts of Ctlra > Thanks for looking! > and it has a strong issue: "The device specific files are written in c." > Yes it written in C. This is a deliberate

Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

Hi Harry, I have looked a bit closer to the concepts of Ctlra, and it has a strong issue: "The device specific files are written in c." In terms of am everage use, a library is updated by the various Linux distros in a two years cycle. I am in doubt that the manufacturer a will ship a Ctlra

Re: [Mixxx-devel] [Feature Proposal] Ctlra Controller Hotplug Support

Hi Harry, welcome to Mixxx. That is awesome. :-) A BIG thank you to make this real! I have just skimmed over the linked resources and it looks like this closes exactly the gap between Mixxx and HID controllers. Currently Mix has HID controller support, but it requires scripting, and a lot