7 ms·

In general, thanks for the feedback, I appreciate. But to respond to your points: 1) Perhaps you were watching it at low resolution? It's at a bigger font th

by aure 11y ago

In general, thanks for the feedback, I appreciate. But to respond to your points: 1) Perhaps you were watching it at low resolution? It's at a bigger font than Xcode's standard. 2&4) It wasn't necessarily meant to be a self-contained video. AudioKit has an extensive website with documentation at http://audiokit.io/ http://audiokit.io/ and specifically for playgrounds at http://audiokit.io/playgrounds/ http://audiokit.io/playgrounds/ 3) I'm sorry, that is my Ohio mumble. :) Thanks again!

gecko39 11y ago
Would also be worth saying this is for iOS / osx somewhere obvious on the homepage. looks like a cool project!
- aure 11y ago
  Done. Thanks!
  - gtani 11y ago
    just curious, is there something missing from platforms/libs like csound, max for live, supercollider etc you were aiming for?
    - aure 11y ago
      Yes, a lot, too much to write in a comment box though: http://audiokit.io/features/ http://audiokit.io/features/
      - gtani 11y ago
        excellent, i'm willing to learn swift or obj-C for this, are they API-equal? (actually i don't know much about M4L, supercollider or those others, but i do have a bunch of HW synths: kurzweil, DSmith, emu, kawai etc
        aure 11y ago
        Either one is fine for AudioKit. Swift is still evolving a bit, might want to stick to Objective-C if you're learning.
sgk284 11y ago
Just to balance out the feedback. 1) That font was plenty large. I don't see how it could have reasonably been larger without being comical. 2) It seemed kind of self-evident what a playground was. 3) Your voice was plenty loud. I don't know what he was referring to re: mumbling. 4) Not sure what he's looking for there. In short, I think the video was incredible. I wouldn't change a thing. Thanks for sharing, and don't dwell too much on one user's feedback :)
graycat 11y ago
> 1) Perhaps you were watching it at low resolution? It's at a bigger font than Xcode's standard. My screen is a razor sharp 14" monitor with 1024 x 768 pixels. Resolution is not the issue, just size. All the text on the screen used for the demo is just a total blur -- I can't make out even a single character. I'm a long time, full-time computer user, and that text was by far the worst I ever saw that was intended to be read. 2)-4). Your video doesn't have to be "self contained". Instead, just say in broad terms what you are talking about. I've never heard of AudioKit before, nor should I have. I have no idea at all what the purpose of AudioKit is, nor should I. I have no idea if there is a Web site for AudioKit or if it has tutorial material, nor should I. If all such things are true, then make that clear. E.g., could I get the orchestral score to the R. Strauss Einheldenleben and use AudioKit to do a good synthetic orchestral performance? The score to the Bach Chaconne? The Bach solo violin version? The Busoni piano version? Say enough to make answers to such questions clear. 3) Ohio. Ohio should be fine. My mother was from Columbus, grew up just south of the OSU campus. I was a prof in the B-school there. My father went to Ohio State, BA and MA. My wife was from not far away, about 50 miles SW of Fort Wayne, IN. It's not about Ohio. Instead, just do what I said: Don't drop your voice at certain words or at the ends of sentences. When you say a word, go ahead and actually pronounce it. Your Ohio version of English speaking is fine; just use it. As it is, mostly I couldn't understand what you were saying, totally lost maybe 1/3rd of your words and more of your content. Since I couldn't read your screen text and couldn't understand your speech, I gave up, and I'm someone really interested in music, really interested. You may have some good work. If so, then good. In that case, speak up, describe your work, show clear screen images. BTW, I have no idea, none at all, zip, zilch, zero, nichts, nil, nada, what the heck "Xcode" is. None. I doubt that Xcode is in Webster's. So, Xcode is undefined jargon. I know quite a lot about both music and computing, but I don't know what Xcode is, and likely I should not. Lesson: If you want to communicate, don't use undefined jargon. Computing: I've published peer-reviewed original research in artificial intelligence from the IBM Watson lab. I've taught computing at both Georgetown U. and Ohio State U. At Ohio State, I was a leader in computing in the B-school and more generally on campus. I've programmed significant software for decades. My Ph.D. dissertation was heavily based on software that I wrote. I recently finished typing in software for a Web site with 4 back-end servers, 80,000 lines of typing, about 18,000 programming language statements, for Windows with the Microsoft software .NET, ASP.NET, and ADO.NET and for the Microsoft calls for TCP/IP, etc. Still I never heard of Xcode. Fonts? I'm quite good at D. Knuth's TeX, still have never heard of Xcode. I'm not attacking you. Instead I'm giving you constructive feedback so that you can communicate better about your possibly quite good work so that many more people can like your work. Main lesson: Just speak up.

by aure 11y ago

gecko39 11y ago

Would also be worth saying this is for iOS / osx somewhere obvious on the homepage. looks like a cool project!

aure 11y ago
Done. Thanks!
- gtani 11y ago
  just curious, is there something missing from platforms/libs like csound, max for live, supercollider etc you were aiming for?
  - aure 11y ago
    Yes, a lot, too much to write in a comment box though: http://audiokit.io/features/ http://audiokit.io/features/
    - gtani 11y ago
      excellent, i'm willing to learn swift or obj-C for this, are they API-equal? (actually i don't know much about M4L, supercollider or those others, but i do have a bunch of HW synths: kurzweil, DSmith, emu, kawai etc
      - aure 11y ago
        Either one is fine for AudioKit. Swift is still evolving a bit, might want to stick to Objective-C if you're learning.

sgk284 11y ago

Just to balance out the feedback. 1) That font was plenty large. I don't see how it could have reasonably been larger without being comical. 2) It seemed kind of self-evident what a playground was. 3) Your voice was plenty loud. I don't know what he was referring to re: mumbling. 4) Not sure what he's looking for there. In short, I think the video was incredible. I wouldn't change a thing. Thanks for sharing, and don't dwell too much on one user's feedback :)

graycat 11y ago

> 1) Perhaps you were watching it at low resolution? It's at a bigger font than Xcode's standard. My screen is a razor sharp 14" monitor with 1024 x 768 pixels. Resolution is not the issue, just size. All the text on the screen used for the demo is just a total blur -- I can't make out even a single character. I'm a long time, full-time computer user, and that text was by far the worst I ever saw that was intended to be read. 2)-4). Your video doesn't have to be "self contained". Instead, just say in broad terms what you are talking about. I've never heard of AudioKit before, nor should I have. I have no idea at all what the purpose of AudioKit is, nor should I. I have no idea if there is a Web site for AudioKit or if it has tutorial material, nor should I. If all such things are true, then make that clear. E.g., could I get the orchestral score to the R. Strauss Einheldenleben and use AudioKit to do a good synthetic orchestral performance? The score to the Bach Chaconne? The Bach solo violin version? The Busoni piano version? Say enough to make answers to such questions clear. 3) Ohio. Ohio should be fine. My mother was from Columbus, grew up just south of the OSU campus. I was a prof in the B-school there. My father went to Ohio State, BA and MA. My wife was from not far away, about 50 miles SW of Fort Wayne, IN. It's not about Ohio. Instead, just do what I said: Don't drop your voice at certain words or at the ends of sentences. When you say a word, go ahead and actually pronounce it. Your Ohio version of English speaking is fine; just use it. As it is, mostly I couldn't understand what you were saying, totally lost maybe 1/3rd of your words and more of your content. Since I couldn't read your screen text and couldn't understand your speech, I gave up, and I'm someone really interested in music, really interested. You may have some good work. If so, then good. In that case, speak up, describe your work, show clear screen images. BTW, I have no idea, none at all, zip, zilch, zero, nichts, nil, nada, what the heck "Xcode" is. None. I doubt that Xcode is in Webster's. So, Xcode is undefined jargon. I know quite a lot about both music and computing, but I don't know what Xcode is, and likely I should not. Lesson: If you want to communicate, don't use undefined jargon. Computing: I've published peer-reviewed original research in artificial intelligence from the IBM Watson lab. I've taught computing at both Georgetown U. and Ohio State U. At Ohio State, I was a leader in computing in the B-school and more generally on campus. I've programmed significant software for decades. My Ph.D. dissertation was heavily based on software that I wrote. I recently finished typing in software for a Web site with 4 back-end servers, 80,000 lines of typing, about 18,000 programming language statements, for Windows with the Microsoft software .NET, ASP.NET, and ADO.NET and for the Microsoft calls for TCP/IP, etc. Still I never heard of Xcode. Fonts? I'm quite good at D. Knuth's TeX, still have never heard of Xcode. I'm not attacking you. Instead I'm giving you constructive feedback so that you can communicate better about your possibly quite good work so that many more people can like your work. Main lesson: Just speak up.