I am not sure what exactly makes the “syntax” of C++ difficult for you? There are obviously design approaches that can make the code look extremely verbose and difficult and that’s usually for reasons of maximum performance and flexibility. (PD might be slightly better though, as it can also be used as a code library.) Not many people are going to volunteer to do that kind of stuff for cheap. Or finding someone to do it for your for money. You will be in big trouble trying to “convert” your Max/MSP or PD patches into C++ later.
If your end goal is to produce native C++ plugins or applications, it’s best to just bite the bullet now and learn C++. And if you’re going for option 2 you don’t need to pay as much per hour, but since it will take 5 to 10 times longer, you will probably need to fork out even more money than option 1, to make it worthwhile for them If you’re going for option 1, then you need to offer a very nice hourly rate of pay, because a person with those skills probably already has access to well paying jobs. Or (2) you’re looking for an amateur DSP coder to deal with the first and second problems by spending a few dozen hours on a task for you. Either (1) you’re seeking the help of an expert DSP coder to spend several hours dealing with the second problem that I mentioned.
#Learn max msp Patch
Second problem is that a sophisticated Max patch can have so many connections going all over the place that it can get quite confusing to figure out the structure of the logic.ĭSP is pretty hard and you’re either asking for one of two things here.
#Learn max msp how to
In the past I have attempted to convert other people’s Max patches into C++ code, and it can be a nightmare depending upon the complexity of the patch.įirst problem, is that a lot of the Max components are high level and you can’t find out what the internal logic is for those, which meant that I needed to do research into my text books and online to find out how to write the code for those bits.
0 kommentar(er)
