DSP Robotics Support

Hello!

I wanted to hear your oppinion what way would be the best if i want to provide my knowlege of FlowStone to other users.
There are 4 persons her at my area that might understand what they are able to do with it.
So i wnat to provide some basics so that they are able to use Flowstone.

But how schould i built up those lessons, which subjects should i do with them first?

Regards

Run while you still can!!

Run while you still can!!

Id say mimic the user guide but explain in more detail with examples. . . dont forget Tro's trigger tut but i think its quite alot to grasp

that really depends on what background they have and what they want to use it for, but for the beginning i would show how to build some simple schematics and show how the programm works ( linkorder, wireless links, triggering and stream, ruby ,dsp & assembler, modules and primitives + gui ), and how to build clean and readable schematics - like in programming lessons its always the first thing, to learn a good programming style - all this basics i think should be enough for 8 -16 hours depending how detailed it will be and how much time u want to spend to answer questions...

That's a great idea Chackl!

I would sure everyone starting out in FS and ruby would really appreciate your efforts! i would also love a learning resource since, although Ive used SM for years I still have a hell of a lot to learn!

I would agree with Nubeat7, all the basics first, building up over time getting further in depth as you go, you could even liaise with the likes of Togg and some of the other guys who have provided excellent tutorials in the past and perhaps incorporate their works as well, you could open a youtube account dedicated to SM/FS tutorials and link in video demonstrations! this would be great for teaching the code aspects of the environment and would save on a hell of a lot of writing, step by step tutorials on building a basic osc or filter from FS code or assembly etc!(not just the how to's but also the why's) 7 years I have been a user and have never delved into SM/FS code because there is no learning system for it. where as i am slowly picking up ruby because there is a mass of learning available on the web.

Wish you all the best in your en devour!

Excellent initiative. Surely there is room for supplementary training material, next to the User Guide and Component Reference available from http://www.dsprobotics.com/support/viewforum.php?f=18

Especially about Ruby, the way it connects on the schematic.

I warmly recommend reverse-engineering the STEM Storage Scope, which is incorporating Ruby.
http://www.dsprobotics.com/support/viewtopic.php?f=11&t=1136&p=3442
Would be fantastic to have a STEM Storage Scope.pdf, as supplementary training material.
Possibly illustrated by a YouTube video.

One can extend such approach to all Flowstone STEM Example Projects.

They are listed here http://www.dsprobotics.com/support/viewtopic.php?f=82&t=1211&p=3853#p3853
Would be fantastic to have a STEM Audio FFT.pdf, as supplementary training material.
Possibly illustrated by a YouTube video.
Possibly improved, because at the moment the vertical scale (dB) looks weird. There should be a TOP parameter (like -20 dB) and a RANGE parameter (like 80 dB).
Also, the horizontal scale labels (LIN or LOG) could be improved. In LOG mode, the horizontal scale labels could obey the 1-2-5-10 progression, displaying the 20 Hz, 50 Hz, 100 Hz, 200 Hz, 500 Hz, 1 kHz, 2 kHz, 5 kHz, 10 kHz, 20 kHz labels.

chackl wrote:Hello!

I wanted to hear your oppinion what way would be the best if i want to provide my knowlege of FlowStone to other users.
There are 4 persons her at my area that might understand what they are able to do with it.
So i wnat to provide some basics so that they are able to use Flowstone.

But how schould i built up those lessons, which subjects should i do with them first?

Regards

Hi chackl, that is a great idea. As I am also absolutely new to FS, thus in my opinion one should firstly enhance on what the FS User Guide and Component Reference does not fully cover. On this topic I would suggest that one take each component/module [which is not fully covered or explained by FS] and build a step-by-step 'real-world' full working schematic to show how and what it can be used for - for example, the component/Module which is used for opening/storing/copying/multi-selection of files; or how to use the preset manager module fully and correctly etc. Then use these [and others you have selected] as further building blocks to build a working project to show how the basic schematics work together. You don't have to cover each and every component/module in the FS Component Reference but only those that will get a newbie [like myself] quickly 'up and running'. After this the programming style, code etc can follow as mentioned by the other members here on this thread.

I wish I could have those lessons of yours as well.

Regards.