Hello, I see since 1 month ago that to much post it is ignored, What happen?
I think about the experts developers!
They have to much work and a little time for share his knowledge with the beginners.
Please
Have sympathy with me!
For solidarity developers!
IMO from a salesman point of view, official 3rd party may not throw their cards on the table just like that. As long as it's common ground it wouldn't be held back intentionally, but some of the stuff asked for here asks loads of research - if it's already discovered at all!!
_________________
<FONT SIZE="-1">More has been done with less</FONT>
<font size=-1>[ This Message was edited by: at0m|c on 2004-12-06 09:12 ]</font>
_________________
<FONT SIZE="-1">More has been done with less</FONT>
<font size=-1>[ This Message was edited by: at0m|c on 2004-12-06 09:12 ]</font>
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
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
-
irrelevance
Thats a great post astroman.
I'm currently studying electronic engineering and have always had the idea that aswell as using all the wonderful equipment out there that help realise and touch the deepest parts of the psyche, that I would actually like to be involved in the production of them aswell.
It may be a long time before I'll ever get to do this as I'm still not even at degree level and the maths is already VERY heavy and looking into dsp books is like reading some kind of gnostic esoteric coding!!
Also knowledge is forever fluctuating turn your back and it goes, only willing to show itself when you've looked good, long and hard.
But I guess it's not supposed to get any easier otherwise how would we learn to appreciate.
I'm currently studying electronic engineering and have always had the idea that aswell as using all the wonderful equipment out there that help realise and touch the deepest parts of the psyche, that I would actually like to be involved in the production of them aswell.
It may be a long time before I'll ever get to do this as I'm still not even at degree level and the maths is already VERY heavy and looking into dsp books is like reading some kind of gnostic esoteric coding!!
Also knowledge is forever fluctuating turn your back and it goes, only willing to show itself when you've looked good, long and hard.
But I guess it's not supposed to get any easier otherwise how would we learn to appreciate.
the lion.
he was the sidekick of superchicken, an enhanced fowl(he drank a supersauce). if they were pinned down by bad guys, fred would have to stick his head out to see if they were still there(or do any other dangerous task that needed to be done). if fred complained, he would be informed that he should stop because "you knew the job was dangerous when you took it".
that cartoon seems to have affected me...
he was the sidekick of superchicken, an enhanced fowl(he drank a supersauce). if they were pinned down by bad guys, fred would have to stick his head out to see if they were still there(or do any other dangerous task that needed to be done). if fred complained, he would be informed that he should stop because "you knew the job was dangerous when you took it".
that cartoon seems to have affected me...
Hi all
I am thinking of taking the SDK plunge, are there any manuals anywhere to check it out a bit? I have a programmming background (from Cobol to AS) and have just finished an MA in Electronic Arts... so I imagine I might get something working eventually. I am interested in midi processing / step sequencers etc, not synth sounds as such. As there are so many synths / filters etc out there already.
But perhaps the Mod III environment would be an easier way?
Any tips anyone?
Thanks!
I am thinking of taking the SDK plunge, are there any manuals anywhere to check it out a bit? I have a programmming background (from Cobol to AS) and have just finished an MA in Electronic Arts... so I imagine I might get something working eventually. I am interested in midi processing / step sequencers etc, not synth sounds as such. As there are so many synths / filters etc out there already.
But perhaps the Mod III environment would be an easier way?
Any tips anyone?
Thanks!