Forum Replies Created
5. January 2017 at 20:30 in reply to: Procoding for OSX preview issue on certain computers #1400
Procoding for Mac is updated and will be available on the Mac App Store within the next 24 hours.24. November 2016 at 21:30 in reply to: Procoding for OSX preview issue on certain computers #1391
I found the issue. It only happens on older/slower computers. A fix will be submitted within the next days (probably on this weekend).20. November 2016 at 20:08 in reply to: Procoding for OSX preview issue on certain computers #1390
– 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.
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,
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).
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
(that might be the quickest option to just “make it work” quickly, by adding minim.js to your sketch resources)
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,
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 :(
Just FYI: there’s a version submitted for review since last week that addresses this issue.
Thanks again for notifying me about this!
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!
Thanks again for reporting this.
Oh: it just occurred to me in the other thread: do these sketches maybe have many (or some big) resources?
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.
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!
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.
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.
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: