Forum rss-feed

Forum

General Discussion: Need documentation

Most Recent

written by: prstorms

Foveus... help a brother physician out. Please see my "Trilian 101" beg post for info on how to get rolling with this AU.

All: sorry to highjack the topic for an off-topic personal request. Now returning to your local programming....

I posted on this topic a LONG time ago. The lack of documentation can be frustrating and the apparent need for a PhD in computer engineering/sound engineering/some kind of engineering has been frustrating as well. Did ANYONE have the impression upon seeing a demo of this instrument on YouTube that it would be a cinch to pick up and play? Not me! I'm looking at a blank palette of 120 keys that can be configured in more ways than I can conceive of. I can run a number of sounds simultaneously and manage all that swapping around LIVE. I keep coming back to the instrument because it's interesting, pure and simple. Sometimes I take a break and pull out my analog instruments to give my brain a rest, but I always find myself coming back to the Eigenharp... frustrations and all.

Regards,
Pat

written by: carvingCode

Tue, 2 Nov 2010 09:52:53 +0000 GMT

It is difficult for someone just starting out with EigenHarp and EigenD to get a good understanding of its capabilities and functions. The documentation is minimal and spread out across forum and wiki posts, both of which are poor examples of their genre of software applications.

When can we expect to see appropriate unified documentation? I think the EigenHarp is the most intriguing instrument I have played. So, I apologize if this seems negative.

Randy Brown


written by: john

Tue, 2 Nov 2010 10:28:36 +0000 GMT

Hi Randy

The EigenD UI is about to go through some very large changes. We've spent the last year working on both Stage and Workbench and over the next few months we think these will transform the way that people interact with the software in very significant ways. This change is so profound that any existing documentation, while remaining valid (as the Belcanto language remains at the heart of the system) will become largely irrelevant to the normal player. Knowing that this change is coming has meant that it really hasn't been worthwhile producing a structured manual, it would be going out of date at a rate that we would struggle to keep up with..

At the heart of the changes is the strong desire to make the whole system (which is considerably richer than most people are aware of) more discoverable in itself by providing a graphical overview of all the components and they ways they are connected, reducing the need for documentation in general. As soon as we've done some proper field testing of both Stage and Workbench, and allowed them to evolve a little in this environment then I think it will be time to start to document these properly with a formal manual. The cost of producing nicely written and formatted docs is high, and we won't be doing this for the new style of UI until it is sufficiently stable, probably early next year. By that point we will also be reshooting all our tutorial videos as well, which is also a very expensive process and one we only want to do once as a result.

An early version of Stage is due to make it into the current 1.2.X series (Unstable at the moment) in the next week or two, so these changes are not as far away as you might imagine. All feedback will be appreciated when it does, and if you're interested in signing up for the iPhone/iPad tester group please let Aaron know in customer services in the next week or so as this will be a restricted group of people due to the rather insane way that Apple apps work - we can't have more than a few testers at one time and we have to know who they'll be in advance of compiling the app. Workbench will be a little longer as it's scheduled for the 2.0.X series, late this year or early 2011. We are about to start testing it internally for real though, so it has now moved beyond the status of vaporware.

In the longer run we envisage that the principal way that people will learn the Eigenharp, how to play, change and adapt it to suit themselves will be through lessons rather than a manual. There is a subset of people who are very happy to self teach using documentation (and it sounds like you're in that group) but this is not as common as you'd imagine. Quite a lot of our effort has been going into developing the teaching side of Eigenlabs over the last couple of months. The online seminars are our first foray, and you will see further things happening on this front over time.

So, in short, please bear with us. We know that the current documentation is unstructured but there are very good reasons for this. In the next few months you will experience some large changes in EigenD that will make this apparent, changes that I think you'll really enjoy.

John


written by: mikemilton

Tue, 2 Nov 2010 14:50:16 +0000 GMT

John, Thanks for that answer it is great news.

The seminars have been quite helpful. I think this is particularly true because they focus on some activity or outcome and, as a result, they bring additional structure to the WIKI reference by bringing facts together for a purpose

cheers, m


written by: dhjdhj

Tue, 2 Nov 2010 14:48:56 +0000 GMT

I am VERY excited to see this new version

john said:
The EigenD UI is about to go through some very large changes.....



written by: carvingCode

Tue, 2 Nov 2010 22:01:38 +0000 GMT

Hi -

Like others, I'm also interested in the visual interface coming in EigenD upgrades. I'm sure there will be many things that will be intuitive and easier to use.

I still do want to lobby for appropriate documentation even with the GUI. I use a number of software apps with high GUI, i.e.: Reason, Ableton are two music apps I use. Yet, both have 500+ page manuals (PDF format), plus extensive in application help (Help menu).

On the other hand, ALL hardware controllers I own have sparse documentation.

I think it may be a mistake to rely solely on a GUI, no matter how well-designed, to expose all of the features of a deep piece of software, which it seems EigenD may be (or is becoming).

Thanks,

Randy Brown


written by: Lowdene

Wed, 3 Nov 2010 13:55:47 +0000 GMT

First I think it's completely understandable why there hasn't been formal documentation up until now (and for a while yet still). I would though like to take issue with the statement Apart from the fact that it must be very difficult to collect relevant and accurate statistics to support such a statement, I think it oversimplifies how people actually learn. I don't have any supporting statistics on this either, but my experience is that it is generally through a number of different approaches running together, not an 'either / or'. I can speak about my own approach to learning and it involves variously: professional lessons, video lessons, self-teaching and reading documentation. Yes, the last of these is still an important component. I stick pdfs of relevant documents on my ipad and read them on planes and trains etc., but just because I find this useful, does not classify me as one of the 'subclass of people who are happy to self-teach'.

Personally I think the present wiki documentation is an incredibly poor form of communication and in sharp contrast to the quality of the instruments and the support offered by the Eigenlabs team. I think it is an understandably weak point at the moment, but I think it would be disappointing if it was perpetuated long beyond the point when reasonably stable documentation became feasible.

Nick


written by: Lowdene

Wed, 3 Nov 2010 13:58:32 +0000 GMT

In the post above I was referring to John's statement:

There is a subset of people who are very happy to self teach using documentation (and it sounds like you're in that group) but this is not as common as you'd imagine.

For some reason it didn't paste.


written by: john

Wed, 3 Nov 2010 14:26:14 +0000 GMT

Hi Nick

You are of course quite correct that the broader the range of available learning tools the better. A structured, formal manual will be an important component of that and we will be developing one as we stabilise the new UI's. I would however stick by my statement that the availability of tuition is probably more important for many musicians than any amount of written material. It is not something we can ignore as a company. In the early days we didn't have much choice, we had to ignore it as there were simply no teachers or even players around (and I have to tell you that I have been asked about tuition many, many more times than I've been asked about written documentation over the last year). This is now changing and I think this will become a very significant part of the learning experience for new players.

But as you point out, the learning experience also varies dramatically from person to person. When I put you in the 'happy to self teach using documentation' bracket, I was actually lumping you in with me (which I hope doesn't constitute an insult!). I play the guitar reasonably well and have never had a single lesson on that instrument. I personally always prefer to disappear off somewhere and figure things out for myself rather than seek tuition. I do dislike most documentation though, it's nearly always rubbish and for me the best software is discoverable software, software that is in effect self documenting. And here I must accept all criticism sent my way, because EigenD is not good at that at the moment. With the advent of Stage and Workbench I think you will see this start to change in a very positive way.

By the way, all help is always appreciated on the Wiki front. If you can contribute to it to help make it better, that's always seriously appreciated. We're a small company and we don't have infinite resources - any help at all from you guys is a big plus in making the Eigenharps easier to learn.

John


written by: filulilu

Wed, 3 Nov 2010 15:10:30 +0000 GMT

What John says is true with traditional instruments where the talent and inventiveness of many musicians in the past give us an acquired wisdom so sophisticated that it is best communicated with teaching. The Eigenharp on the other hand is a baby (and I do hope that it will become a grandmother with lots of grandchildren) and it is designed in a very open way. It is my understanding that a lot of effort went into making it able to be used not in one particular way.

The Eigenharp is very complicated and lessons will be useful, but a good manual is more important because it supports this very important design approach.

I read somewhere that Moog's modular synth didn't have a manual when it first came out and had its users too completely confused. And they had no Wiki's and stuff then, so consider ourselves lucky.

Yorgos


written by: Lowdene

Thu, 4 Nov 2010 07:46:24 +0000 GMT

John

Yes I guess we're saying the same thing. I hate manuals but consider them a necessary evil. That's why I read them when I've got dead time like when I'm traveling. I also completely understand why the documentation is in fluid form right now. I do think though that to supplement whatever learning approach different poeple take, a manual will become important. We shouldn't get into the kind of false dichotomy so beloved by politicians - lessons are good so manuals are bad. They do different things and both are important. As for the wiki, I don't like the format because it lacks a narrative structure, and it''s not really portable, but maybe that's just me.

Nick


written by: barnone

Sat, 6 Nov 2010 22:25:36 +0000 GMT

This is great news (stage + workbench).


+1 vote for more online seminars.


written by: prstorms

Sun, 7 Nov 2010 15:37:43 +0000 GMT

Welcome to the wonderful world of being on the bleeding edge of technology. I jumped into the pool knowing that the level of documentation was suboptimal and that the user community would be growing and learning right along with me. That's part of the adventure. I look forward to the next version of the UI, and being able to access control functions without an in-depth knowledge of Belcanto!

Thanks for everything!
Pat


written by: Tenebrous

Wed, 10 Nov 2010 11:58:35 +0000 GMT

As an iPad owner I'm very excited by this :) Please add me to the list of testers if you have a space :)


written by: dkah

Mon, 15 Nov 2010 09:32:21 +0000 GMT

For the instrument part lessons may be the best way. But the Eigenharp is also a piece of hardware and a piece of software and these need manuals. I like seminars, but lets face it if you have a certain level of knowledge you want a reference to look things up quickly and not a video where somebody explains almost, but not quite the thing you need. Also I read faster than most people talk. Also I can skim documentation for keywords. But for a 20 minutes video I need 20 minutes (uninterrupted) time to at least know what it is about. With all the hello, how are you and nice to see you again and stuff like that.
I hate the 4 Pico tutorial videos, because it is quite cumbersome to find the place again where the feature I am currently interested in is explained, there is no table of content, no index, not much indication in which video it may be. So I have to write stuff down, to have my manual. Because I need one.
By the way you are aware that there are and will be more non-native-English speaking Eigenharp users, who will have more problems understanding a person talking English quite fast like the tutorial guy or mumbling like the guys in the justin.tv videos, but are quite capable of reading English text?
Oh and yes concerning lessons, how much chance do I have to get a certified teacher in Zurich, Switzerland any time soon? Probably not likely, so until Eigenharps are as established as pianos, maybe a manual? Yes I know about the lessons over skype, but that's not an adequate instrument lesson either.
So the short of it: You need manuals, there is no way around it. It is ok not to have them now at the bleeding edge, but please do not talk yourself out at providing them some time in the future (soon).


written by: dhjdhj

Mon, 15 Nov 2010 13:56:33 +0000 GMT

I would like to strongly second dkah's comment. I can read and absorb info far faster than watching a video. The latter can never impart as much information in the same time frame. Live videos are great for Q&A but I would like to see either comprehensive documentation that doesn't require extra research to understand.


written by: BobThDog

Wed, 26 Jan 2011 16:13:46 +0000 GMT

Hi Guys,

I have to stick up here for the idea of a technical manual.

My Pico sits unused, If I had a manual I could peruse I am absolutely sure the Pico would be used.

When I got it I watched the videos, struggled with the booklet and then just gave it up as a bad deal.

The Pico itself I love, it feels nice, the level of control is good etc.

Unfortunately when trying to set things up to work differently I just hit a wall, I re-watched the videos and then immediately forget everything again, after a while this was soul destroying and the poor little thing got placed on a shelf.

I am hoping one day a manual appears and I can dust it off, you never know if I got used to it I may but one of it's bigger brothers then.

Cheers

Andy




written by: carvingCode

Thu, 27 Jan 2011 01:26:10 +0000 GMT

Re-reading this thread (which I started) and in light of some things I've written on this topic, I do want to give Eigenlabs time to finish some development and get the 'core; software in place.

I'm still concerned that Eigenlabs doesn't understand what users need in terms of a proper manual and reference. It's odd to me; as extensive as the hardware and software is, they've held to the principle that users should just be able to mindmeld with it. May be true for some, but not most.

Randy


written by: Lowdene

Fri, 28 Jan 2011 12:06:56 +0000 GMT

I rarely read or post these days - just in an idle moment. The instruments are brilliant, but Eigenlabs stands out as pretty much the only music software company I can think of that doesn't produce a reference manual. Many go to great lengths, and take great pride, in making these as user-friendly as possible. However, I conclude from his postings the chairman has a philosophical antipathy to the idea (I'm sure he'll correct me if I'm wrong!) and that will probably mean it won't happen whatever the clamour from users.
Nick


written by: 0beron

Fri, 28 Jan 2011 12:44:13 +0000 GMT

I think the discussion about avoiding manuals has in the past been centred around the internals of the system ( belcanto, instrument setups etc.). The logic is that these are still subject to rapid change and therefore any manual would go out of date quickly.

I've seen many users asking for guidance to do with the operation of the eigenharp and playing instruments, i.e. the interface presented to you by a particular harp and how to navigate all the LEDs on it. This hasn't changed in any dramatic way for a long time, and unless a really big shake up in the interface is planned (even if belcanto is in for some overhauls in version 2 I would hope that the effect on how the factory setups behave would be minimal), then writing and maintaining a manual for this should be easier as it is not such a moving target.

Those of us interested in scripting and deep customisation will have to get used to the evolving nature of EigenD and the resulting lack of documentation, but players of the instrument rightly expect a little more than the quickstart guides and video tutorials offer.


written by: keyman

Fri, 28 Jan 2011 15:20:19 +0000 GMT

@0beron
This time you summed the whole thing about the manuals, I agree with you 100%.

keyman



Please log in to join the discussions