Sometimes, when i turn an existing PD patch into a Bela version, the IDE screen shows graphic representation of an uploaded patch at all, screen stays empty, however the patch actually does run.

I've tried removing parts from the patch then, especially subpatches. However i found no other way to get the IDE screen back, than completely building exactly the same patch from scratch.

Does anybody know the reason for the blank screen, is there an easy fix?

I fixed something like this in the past where [declare] was breaking the viewer. Maybe it isn't fully fixed and/or there is something else (similar and/or related or not) that breaks it?

    i noticed that as well, but since there's no way (or need) of controlling the pd patch from the IDE i never bothered to find out what was going on.. as long as the patch was running, i never really worried 🙂

    come to think of it, that might happen when using objects from external libraries. would make sense in light of the [declare] issue.

      Remork since there's no way (or need) of controlling the pd patch from the IDE i never bothered to find out what was going on.. as long as the patch was running

      Absolutely. However, as i don't use git for versioning i sometimes use the IDE to confirm, that my PD patch and the one used by Bela are actually the same.

      giuliomoro [declare] was breaking the viewer

      I am pretty sure i haven't used [declare] anywhere or at any time yet 😃
      I'll have to check, which object/s are exactly the culprit here.

        10 days later

        jayrope I am pretty sure i haven't used [declare] anywhere or at any time yet

        me neither, at least not literally.
        i have used stuff from external libs though, w/ syntax like [cyclone/degrade~] .
        not sure if that is the same as the [declare] object.

          Remork i have used stuff from external libs though, w/ syntax like [cyclone/degrade~] .
          not sure if that is the same as the [declare] object.

          I use pure Vanilla only, mainly for compatibility reasons. But i guess i should check the files in a text editor for quicker finding. I'll keep watching this while programming.

          the browser's inspector's console may even tell you where the error is.

            giuliomoro To the extent of what i can see during loading i can say there isn't. But yes, I'll keep watching, thank you for looking into this.