imho Nitri's demands are way out of reach for a beginner's project - it just doesn't work this way.
It's the 2nd step before the first. You cannot study a system on a complex 'industrial strength' implementation like driving a Logic or Mackie Control.
Today everything has to be rushed out overight, there's a lack of patience to work out the basics and understand what's going on.
Instead a page of source here and a link there are mixed together with a lot of trust in chance that 'it may work some way'.
It's a very typical attitude and the reason for the horrible overall software quality we experience (imho).
I've been through more than a dozen programming languages and developement systems of all flavours - and honestly I admit I've had to grin a couple of times about those 'unsolvable problems' sometimes metioned in the context with CWA's SDK.
These obstacles are a natural matter of fact - YOU have to work that out, it's what the job of a developer is about.
I'm currently in the middle of a project with a language I haven't used for > 10 years. My last project (years ago) was classical 'C' and I swore I'd never program a line of code again - it was just so stupidly complicated and uninspiring.
The current project is in a language which is 180 degrees opposed to C, with not even the slightest bit in common.
Yes, I had to start again at point zero.
Grabbing my beginners books from the shelf and studying stupid examples - philosophing about a handful lines of code for a complete afternoon.
I had underestimated the challenge - or the reliability of the mellow disk in my head
Well, it's commercial stuff - there's a deadline, there are people expecting to WORK with this system. It HAD to replace an outdated one, very soon.
And I'm sitting in front of the screen, thinking 'holy sh*t - there were times you could fluently write that stuff...'
One might panic in this situation - then you've lost the game. Or accept the inevitable and wade through all the fundamentals again - until the feeling that one is in control (and the system reacts predictable) reappears.
At first it's not exactly fun, but it quickly becomes once the afforementioned feeling of control sets in.
From that moment on you deal with design ideas like notes on a piano (or synth).
But you'll never get there if you let others do the challenging part
So heads up Nitri - confusion is not unusual in this biz, and it can easily be sorted out if you're willing to accept the rules.
The rules already exist, it's not you defining them - that's probably the most difficult part in the whole process
cheers, Tom