Mods: Please update the title to indicate this is the final beta (version 0.9) thanks!
Edited by mxb, 08 June 2011 - 10:18 PM.
Jump to content
Posted 01 November 2010 - 09:16 PM
Edited by mxb, 08 June 2011 - 10:18 PM.
Posted 02 November 2010 - 11:39 AM
Edited by Airjob, 02 November 2010 - 11:57 AM.
Posted 02 November 2010 - 01:07 PM
Thanks for the kind comments about the code. I have some spare time at the moment.
wow, you're quick indeed .
great to see your work is going on, nice code.
I thought in last two days about a more generic / genereal approach for compact "one-fader" - DAW controllers.
E.g. there is the cubase and Cakewalk hardware, too. Or think about e.g. the iPhone iPad - you could easily write a midi controller which simulates
a FaderPort or Frontier Alphatrack
So what do you think:
is there a chance to find a common interface / architecture which
a) covers the common subset: transport, manual and automatic(!) / device track selection ?
B ) can be massively modified for specific device implementation (like e.g. your status line display and specific buttons) ?
c) can maybe be married with Duplex in some way ? E.g. we could take advantage of the controller simulation features
For example right now I guess it was possible to derive a new Class from FaderPort and just override the Midi handler functions
in order to easily create adapters for new devices easily.
Posted 02 November 2010 - 02:11 PM
Posted 02 November 2010 - 06:10 PM
Edited by mxb, 03 November 2010 - 04:52 PM.
Posted 03 November 2010 - 12:18 AM
That was quick indeed. AlphaTrack owners rejoice!
About the Duplex implementation, I honestly don't think it's that important now, now that a dedicated tool is available. This kind of controller is very compact and specialized tool, and would always benefit from a closer integration - Airmanns sophisticated tool is a good example of this.
Somewhere down the road we might be able to have such a complete integration, but I don't think this is important for the Alphatrack owners out there? In the short term, I think it's much more beneficial to establish a common set of features between the Alphatrack & Faderport like you point out.
* Button class
* LED class
* Illuminated button (inherits from Button and LED)
* Fader class
* Motorised fader class (inherits from Fader)
* Display class
* Encoder class
* PushEncoder class (inherits from Encoder and Button)
* Transport class (<<, >>, STOP, PLAY, REC, REC LED) inherits from multiple IlluminatedButton classes
* TouchScroll (inherits from PushEncoder?)
* etc. etc.
* Encoder 3 will set the song groove amount
Edited by Airmann, 03 November 2010 - 12:30 AM.
Posted 03 November 2010 - 05:01 PM
Edited by mxb, 15 November 2010 - 06:53 PM.
Posted 15 November 2010 - 06:54 PM
Posted 15 November 2010 - 11:32 PM
Edited by Airmann, 15 November 2010 - 11:41 PM.
Posted 15 November 2010 - 11:39 PM
Another thing: my impression regarding DAW controllers so far is, that we are doing pioneer stuff here. It seems that almost no Renoise users own DAW controllers like Alphatrack, FaderPort et al. In fact it's the classical "chicken or the egg" problem: without driver it makes not much sense to buy an Alphatrack or FaderPort for Renoise. A common MIDI controller like the Nanokontrol was maybe the better choice before 2.6. Maybe there are some guys out there who come from other DAWs and already own a DAW controller, but so far I've received no real responses from serious users. Guess we need patience.
Posted 16 November 2010 - 12:01 AM
Have you guys considered posting in the PreSonus and Fronteir Design forums?
It's probably easier to get someone who owns the same hardware to give Renoise a try than it is for a Renoiser to buy the hardware to give your scripts a try, know what I mean?
Keep up the good work, the both of you!
Posted 16 November 2010 - 01:34 AM
Posted 16 November 2010 - 10:24 AM
Very exciting features. Sample editor mode is really interesting. I thought about that too, but my focus was more mixing related.
Interesting: it seems that you focused anyway more on song creation than me (pattern mode, vsti mode...), so your driver has a slighly different flavour than mine. But that's a good thing: long live innovation :-D.
The guy called "sauli" had a question regarding "automation envelope recording". I think his feature request of loop recording is already covered by
the usual DAW's write, touch, latch modes. These modes are also implemented in my driver, and are also implemented in Reaper - also for the Alphatrack.
Another thing: my impression regarding DAW controllers so far is, that we are doing pioneer stuff here. It seems that almost no Renoise users own DAW controllers like Alphatrack, FaderPort et al. I guess it's the classical "chicken or the egg" problem: without driver it makes not much sense to buy an Alphatrack or FaderPort for Renoise. A common MIDI controller like the Nanokontrol was maybe the better choice before 2.6. Maybe there are some guys out there who come from other DAWs and already own a DAW controller, but so far I've received no real responses from serious users. Guess we need patience here.
BTW: I think you have improved your button mapping. Everything looks very cleaned up, now.
Posted 24 November 2010 - 11:41 PM
DSP automation recording is not in this version. I had trouble trying to get it to work, I will look over the code for your tool to see the approach required.
Indeed, I don't know what the motivation for yourself was, but mine was definately a case of I already owned the hardware and simple MIDI mapping seemed so limited compared to the integration in other software.
Also, while on my travels around the Internet I found this PDF document which has an appendix describing the full MIDI specification of Mackie Control Universal (MCU) devices. This is the protocol used by all the larger (usually 8 channel) DAW control surfaces (e.g. MCU Pro, M-Audio ProjectMix and Euphonix MC Control 2). That would make a nice project....
Posted 02 December 2010 - 10:15 PM
Edited by niNja_pWn3d, 03 December 2010 - 04:04 AM.