pucho812
Well-known member
yeah lets do that. wonder what it smells like ;D
pucho812 said:Sadly no update here... Discussion shifted from trying to play with eucon and all that could potentially happen with lawyers from avid to a more streamlined idea of a plugin controlling hardware. It would be much easier to update a plugin then to have to reinvent the wheel when avid switches gears.
mulletchuck said:grab 'em before they're gone, folks.
Biasrocks said:Got em, although a couple of crucial things are missing.
Two included files.
#include "EuDefinitions.h"
#include "EuWrapperFactory.h"
I suspect those two files hold a lot of the clues.
gyraf said:Only google references are:
ftp://quarante.dynalias.com/FTPpublic/E/Euphonix/Softs/Artist%20series/EuConDocumentation/GettingStartedWithEuCon.pdf
http://pastebin.com/LLiPbK75
http://pastebin.com/sdzmjwqj
..that's not much, I would have thought you'd find much more pieces of ancient software out there after 12 years..
Jakob E.
obrandts said:Thanks. After you mentioned it, I found this
http://forum.cockos.com/showthread.php?t=122509
Has it been stopped by Avid? I actually found the reaper modules too. Haven't looked at them yet, but will do.
With this *I might be able to figure out how to control Protools too. I myself will rather use Reaper actually, but I'm building an automation tool that might be useful for PT users and I'd like to keep that option open if possible.
Anyone know if the legal/patent issues might suggest that it is illegal to implement a software control module that can control PT via Eucon, so Avid might come in and have a say in this at a later stage?
this project went right into the following: Eucon hardware cannot be made by anyone other then avid who owns euphonix. When you get a development kit from avid, you sign paperwork to that. so they allow you to put eucon in your software but you cannot make eucon hardware. To fight avid so was deemed to expensive by the bean counters I was reporting to at the time when I made the original OP. So, the project was abandoned. Instead they opted for a plugin controlling hardware which was more feasible but was also abandon as things quickly changed. who needs console automation on a desk when you can mix in the box and have results that the industry is happy with especially now with atmos. It's only a matter of time when consoles are a thing of the past.Did this project ever go any further? Interested to hear what occurred or whether it got relegated to the too hard basket?
would need companies like avid to adapt to it. something they are not interested in doing as it would affect sales of controller hardware.Has anyone considered developing an opensource counterpart to eucon?
Enter your email address to join: