audiocommander

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 120 total)
  • Author
    Posts
  • in reply to: Procoding for OSX preview issue on certain computers #1400

    audiocommander
    Keymaster

    Procoding for Mac is updated and will be available on the Mac App Store within the next 24 hours.

    in reply to: Procoding for OSX preview issue on certain computers #1391

    audiocommander
    Keymaster

    I found the issue. It only happens on older/slower computers. A fix will be submitted within the next days (probably on this weekend).

    in reply to: Procoding for OSX preview issue on certain computers #1390

    audiocommander
    Keymaster

    Temporary workaround:
    – Go to Procoding > Preferences and deactivate “Web Server Preview”. Note that (unfortunately), this will break processingjs loading mechanisms, but all other JS based document types will preview again.

    in reply to: Paper JS drawing disappears #1387

    audiocommander
    Keymaster

    Hi Andy,

    hm, not sure. Hard to tell without checking.

    It might also be that the Paper.js version coming with Procoding is too old. You can update your paper.js version if you put the latest file in Procoding’s iTunes File Directory.

    Sorry for not being more helpful on this,
    regards,
    Michael

    in reply to: Adding JS files (iPad) #1386

    audiocommander
    Keymaster

    Hi Andy,

    thanks, that’s great to hear!
    To add resources, you have to just open the resources window (top right in the toolbar), tap the “+” and import any .js file from Dropbox or your iTunes files. They are loaded automatically.

    Injecting script tags should also work (I’ve done it).

    Cheers!
    Michael

    in reply to: Minim in Processing / Procoding #1383

    audiocommander
    Keymaster

    Hi again,

    as mentioned before, you are already using processing.js when using Procoding. It’s key to understand that Java and JavaScript are really two completely different things: JavaScript’s real name is actually ECMA Scripting Language. Java and JavaScript have as much in common as “car and carpet” (so it’s really just the “Java” in their names).

    Processing.js is basically a new implementation in JavaScript/ECMA to provide a basic compatibility with Processing (which is written in Java).

    Looking at the latest developments of Java and its removal from all major browsers (that used to run as Java Applets) and the recent patent issues raised by Oracle, I think it’s safe to assume that Java (and thus Processing) is about to become obsolete.

    Based on these facts, here are a couple of links/resources that should help you getting on the right track with audio:

    1) previous forum topic: http://www.audiocommander.de/blog/forums/topic/what-to-use-instead-of-processing-minim-lib/

    2) question on Stackoverflow with a link to a possible alternative for minim to be used with processing.js
    http://stackoverflow.com/questions/16879981/exporting-a-processing-sketch-with-audio-to-javascript
    and
    https://github.com/Pomax/Pjs-2D-Game-Engine/blob/master/minim.js
    (that might be the quickest option to just “make it work” quickly, by adding minim.js to your sketch resources)

    3) consider switching to a more modern JavaScript environment. I recommend to check out P5.js, which comes with P5.audio: https://p5js.org/libraries/ and provides a familiar interface for former Processing users.
    However, that would mean rewriting large parts of your code, but will be future forward and have better performance.
    In general, audio support is much better on the latest browser platforms from simple Audio playback to the quite complex and advanced HTML5 WebAudio API.

    Hope this helps,
    Best, Michael

    in reply to: Minim in Processing / Procoding #1381

    audiocommander
    Keymaster

    Hi Madeline,

    sorry – if nothing changed in the past year, then minim is still a JAVA library for Processing. Procoding uses a JavaScript version with Processing.js (JavaScript and Java are two totally different programming languages).

    While it’s true that you can add any JavaScript resource, you can’t add Java Resources. Thus, to my knowledge there’s no way to add minim as it is.

    However, it’s actually quite easy to add audio with JavaScript but not so straightforward to mix this in with Processing.js.

    I’m currently on the way and typing on my mobile, but I can provide you with some infos about alternatives the next days if that would be helpful. (IIRC there should also be an older topic about this here)

    Sorry for not having better news :(

    in reply to: Resources on iOS #1160

    audiocommander
    Keymaster

    Just FYI: there’s a version submitted for review since last week that addresses this issue.
    Thanks again for notifying me about this!

    Michael

    in reply to: tinylog #1132

    audiocommander
    Keymaster

    as a workaround:
    can you test adding this line somewhere at the top of your sketch and see if it works:

    window.tinylog = Processing.logger;

    A fix will also be included with the upcoming updates!

    in reply to: tinylog #1131

    audiocommander
    Keymaster

    Hi Ian,

    I’m guessing at some point in your code there might be a javascript console warning or error raised. I just saw that there might be an issue in Procoding’s processing.js template to prevent these messages from being routed to the processing.js version of tinylog… will look into that.

    Thanks again for reporting this.

    Best,
    Michael

    in reply to: tinylog #1129

    audiocommander
    Keymaster

    Oh: it just occurred to me in the other thread: do these sketches maybe have many (or some big) resources?

    Resources are loaded and injected dynamically (all with JavaScript), and if you have too many of them, that’s when things might go wrong, because timing is crucial and there might be some overlaps, e.g. when the loading and DOM injection of resources takes too long. Note that there are also time- and memory-related limitations on iOS like script running times.

    Does this message disappear when you reload the affected sketch a couple of times?
    If yes, you should reduce the amount of resources you are using.

    in reply to: Resources on iOS #1128

    audiocommander
    Keymaster

    Hi Ian,

    Procoding definitely has its strength in handling smaller, well defined sketches and less in managing big projects with many resources. There are definitely better ways to handle huge projects. At some point, there are also device limited restrictions on how many resources you can add dynamically before something goes wrong. These kind of projects should then probably be compiled before publishing them. That’s what you cannot do with Procoding.

    I usually have four to five early experiments in Procoding, and only when I’m certain these encapsulated functionalities work as expected, I’m moving them into a resource.
    Or I have some common.js files and third party libraries that I can add as a resource on a as-needed basis.

    I would publish this bugfix asap, but I’m currently working on supporting iCloud Drive and I need to make sure everything works all right before I send out this update.

    Thanks for the report, though!

    Best,
    Michael

    in reply to: tinylog #1127

    audiocommander
    Keymaster

    Hi Ian,

    that’s hard to answer without further information. What do you mean with “a certain class of processingjs sketches”?

    Does it happen with all processing.js sketches or just with some of them?

    tinylog is the console that shows up with logs and it’s built into processing.js.
    Did you maybe change the processing.js version by having a newer processing.js in your documents folder?

    I just checked just to be absolutely certain, and for me it works with the provided examples and the bundled processing.js version.

    Best,
    Michael

    in reply to: Resources on iOS #1124

    audiocommander
    Keymaster

    Hi Ian,

    thanks for contacting me about this: this is a bug affecting all iPads with iOS 8. Usually it should present the sharing screen that you also know from Dropbox, but the presentation inside the popover is not working. Apple changed the way how actionSheets are presented with iOS8, so I think this is broken since the latest iOS 8 updates (and I did not notice because I’m using my iPhone more frequently than my old iPad and it works fine on the iPhone).

    Will fix this asap with the next update, sorry for the inconvenience.

    As a temporary workaround: exporting seems to work; if you selected Dropbox, the resource should be exportable to Dropbox and can be then imported back after editing.

    And by the way: editable code resources is #2 on my top priority list, but there are a couple of issues in regard how the app is designed, that make this quite a complicated task.

    All best,
    Michael

    in reply to: Using Fonts #1121

    audiocommander
    Keymaster

    Hi Ian,

    sorry, not sure if I get everything of what you’re saying,
    but just to make sure:

    – ttc is not supported on the browser (as far as I’m aware of)
    – processingjs cannot convert a font that it doesn’t know. So, you first have to make sure that this font is available to the browser (.ttf is not supported by all browsers!)

    Dealing with fonts in processing/processingjs is really a little more complicated than it could be (IMHO).

    I forgot to add another quite important link that explains a bit more how creating a PFont in processingjs works:
    http://processingjs.org/reference/font/

    Best,
    Michael

Viewing 15 posts - 1 through 15 (of 120 total)