Alternative control and recording.

[WK154]

I'm not sure if you have knowledge of the following sites and the work being done.

http://puredata.info/
http://vvvv.org/propaganda
http://cycling74.com/products/max/
http://www.youtube.com/watch?v=bHuIL9wYjxA

Any news on the contact you can share?

[nottooloud]

Update: Ported the code to the DL, written the android loader app, in testing phase now. Coming soon to an App store near you

Do I understand you to be saying that the Android app is just needed to load code into the DL, and then we can go directly there with OSC? If so, is the code in the DL permament, or does it need to be loaded each boot?

If all you accomplished was to give me access to a hardware MIDI fader bank, with reasonable latency, I would be delighted. MF has all the functionality that I need. At least until it loses sync.

[metacom]

I'm not sure if you have knowledge of the following sites and the work being done.

http://puredata.info/
http://vvvv.org/propaganda
http://cycling74.com/products/max/
http://www.youtube.com/watch?v=bHuIL9wYjxA

Any news on the contact you can share?

I'm familiar with a few of these but will dig deeper.

RE: contact... had a good conversation, now under NDA, so.. umm... cant really say! Thanks for the hook up!

Update: Ported the code to the DL, written the android loader app, in testing phase now. Coming soon to an App store near you

Do I understand you to be saying that the Android app is just needed to load code into the DL, and then we can go directly there with OSC? If so, is the code in the DL permament, or does it need to be loaded each boot?

If all you accomplished was to give me access to a hardware MIDI fader bank, with reasonable latency, I would be delighted. MF has all the functionality that I need. At least until it loses sync.

What I'm saving is in a couple of hours I will be releasing the beta version

The major change in the release plan is that it will no longer be an android app. A more cross platform solution is in place as a jar file. It's freely downloadable, but actually getting the patch/my app requires $$.. Also means avoiding Google/Amazon's 30%.

Right now I've tested interfacing with TouchOSC and python on the rasPi with a hardware fader, some wires and a single capacitor.  Also tested using perl.  My iTunes account is on the fritz so I cant seem to grab a copy of Lemur right now, but I'm trying to work around that now. Cant post a video as I only have 2 camera devices, which both need to be filmed.. short of an intricate series of mirrors I cant see how to achieve that!

Untested, by should probably work out of the box:
Lemur
C++/C/Python/Perl/node.js/javascript/MaxMSP/puredata etc etc etc...

What I'm saving is that any OSC implementation can contorl the DL1608 now. Android, arduino, iPad, iPhone, Mac, Windows, Linux, RasPi. Could also do serial, but requires dissasembly. Heck, bluettoth could even work! Have some way outta left field ideas for a way to record, ultimately, unlimited channels in a novel way. Just need to find someone with a hell of a lot steadier soldering hand than me!

As I hope you can understand, there is a charge. I've decided to set this at $49.99. This will allow me to stop freelancing for a while to solely focus on the development of this. I can see some really cool things happening with this. Plus, it's a $1000 mixer.. what's another 5%?

Case in point, it took 20 minutes from idea to implementation for the raspi fader demo. (excluding the time it took to find the famn fader, which would make it 2 hours...)


The major thing NOT working in the v0.01b release is feedback/2 way comms. i,e, there are no signals back from the 1608 yet, so if you change something on the iPad, it will not be reflected in touchOSC etc. This is the next major feature, and will be released in v0.02 . This means it is not production ready, however I'm lloking for feedback and bug reports as at this point the code seems stable enough.

Support wise I will be watching these forums like a hawk.

Time to put on the coffee.. watch this space!

[WK154]

Check your PM.

[RoadRanger]

Hmm... asking alpha testers to pay you 50 bucks for the privilege isn't likely to net you many...

[metacom]

Ok the feedback so far on the price isn't good.... How does this sound?
Alpha price of $15, will full beta and final access.
Beta price of $25 with final acces.
Final release at $35.

P.S Confirmed Lemur and node.js work fine. Wrangling with pd install... waiting for another arduino in the mail, will see what I can get it to do..

[metacom]

Release time!

http://app.metacom.gd/

Feedback and support in this thread. WKD check your PM!

[sam.spoons]

TBH, I'd love this if it'll work with, say, a Behringer BCF2000 but I'd be seriously reluctant to pay a fee for a beta release, never mind an alpha version (I've been burned on so called "final" releases before now). And I would expect it to have templates for BCF2000, X-Touch and others so I didn't have to do any setting up. Given the above $30 is would be acceptable for a full working and proven version but only if I could try first and be sure it does what it claims.

[metacom]

As per the video, a hardware fader can be used with a raspi and a simple circuit. a single raspi could support up to 16 faders with this method, although there is some jitter. A proper ADC would do a lot better job.
In this case, I used the circuit from here
http://www.raspberrypi-spy.co.uk/2012/08/reading-analogue-sensors-with-one-gpio-pin/

(swicthing out the LDR for the fader, the 2.2k is optional);

and adapted the code to suit my fader/cap combo. I used a 1uf cap and a 10k log fader (ALPS 10KA). The code is here:

http://app.metacom.gd/fader.py
You may need to adjust the coefficents according to your specific fader. Essentially you want a value between 0 and 1.

Requires python 3 on the raspi plus a pythonosc and  raspi.gpio.

Could do up to 16 on a raspi, more with multiplexing.

[metacom]

TBH, I'd love this if it'll work with, say, a Behringer BCF2000 but I'd be seriously reluctant to pay a fee for a beta release, never mind an alpha version (I've been burned on so called "final" releases before now). And I would expect it to have templates for BCF2000, X-Touch and others so I didn't have to do any setting up. Given the above $30 is would be acceptable for a full working and proven version but only if I could try first and be sure it does what it claims.

That is certainely an option in the future. One of the major feature milestones is bidirectional midi<-> osc support, as this really opens up what is possible. I dont have access to either model right now, but I believe it's easy enough to support a wide range of things once the midi milestone is passed.


EDIT: Put  up an example layout for touchOSC. Sized for Galaxy S3, but should work fine elsewhere.

http://app.metacom.gd/lay1.touchosc

[WK154]

Please remember that the DL target market is for 99%+ a non tech market. Check their advertisements. What you have here is the other 0.001% of mostly tech savvy people. See David Schumann's approach and at present with a usable app is still not charging although some of his users are in fact encouraging him to do so. I was trying to get a handle on the # of DL's in the field and to date have not seen a serial # over 0500 with an alpha of A-Z that adds up to 12,000 units (24x500) in the field. If someone has better verifiable figures please speak up.

Update: they are using two alpha fields for their serial number bringing the above total to 288,000 which I doubt they are even close to.

[sam.spoons]

EDIT: Put  up an example layout for touchOSC. Sized for Galaxy S3, but should work fine elsewhere.

http://app.metacom.gd/lay1.touchosc

That appears to be a dead link

[WK154]

Metacom any updates you can talk about or did you vanish into that NDA rabbit hole?

[JMC89]

Website (still) under construction:

http://www.metacom.gd/