I strongly agree that there should be a little better support for external editors. Similar to @Simon and @oskarsh I have really fought the built in editor when it comes to just getting code written. I seem to gravitate back to the built in when debugging and working in UI.

The auto-autocomplete is also extremely unreliable for me. It feels like it stops working completely pretty often.

Honestly, being able to avoid overwrite-on-compile and watching for script changes / auto compile would be enough for me. The regular JS syntax highlighting in Sublime, Atom, VS Code are all much better for me but could easily be community addressed if someone wanted something more robust.

Very nice @aaronventure ! Thanks for sharing.

Sorry to be an annoying thread-bumper, but I really could use some assistance with this. Is this a bug - or is there any other workaround?

@Christoph-Hart Help!!

@d-healey in KT you can designate a portion of a flex envelope to loop repeatedly (the sustain portion essentially). The portion between the two vertical yellow lines can be looped in absolute time or synched to clock.

@bendurso Had the same issue. Open the Projucer file and try enabling x86 for the Xcode project :

@clevername27 Thank you.

Just for clarity, in case anyone else is making rookie mistakes like myself. The main issue for me (just using embedded webview) was:

WebView1.set("enableCache", false);

This had to be set to true in builds or you otherwise end up with just a blank webview in your app/plugins. To be fair, this is in the docs.

@Christoph-Hart I was simply trying to load similar to your example code:

const var f = FileSystem.getFolder(FileSystem.AudioFiles).getParentDirectory().getChildFile("Images/index.html");
 WebView1.set("enableCache", false);
 WebView1.reset();
 WebView1.setIndexFile("Images/index.html");

Working in editor, but blank white screen on all build types (on mac anyway).

Or is that still wrong on my end?

Finding the same thing here using latest development branch. Tried standalone and plugin builds on macOS.

Is this feature still supported?

@TNTHM I've done some testing with AU synths and other stuff on the iOS store and it does work well. I'm not yet sure how well the roundtripping with desktop works when it comes to third parties though. That's on my list to explore for both Cubasis and Logic as it would probably dictate approach a bit.

@d-healey Called "Cubasis" it's actually pretty decent and supports AU. Logic for iPad is also very usable (and I know there are other players in mobile DAW space I don't have much experience with).

Hi Christoph,

I think getting iOS/iPadOS/(VisionOS) compiling again is worth your time.

I have read through the last couple years of posts regarding iOS support, the large annoyances/challenges, etc. I'm also keenly aware of the limited development time when you're a solo or small operation. However, I do think there are emerging platform opportunities with some decent (mobile) DAWs (Logic, Cubasis, etc) and notation software (Dorico) all capable of audio unit support.

Just one dude's opinion. :beaming_face_with_smiling_eyes: