Mobile iOS Version does not load or save patches

[o-g-sus]

I quickly tested the mobile Version of Plugdata, here is my feedback:

• Load & Save Patches does not work yet. Browser window opens, but not Patch will open, nor you can save a Patch on Mobile
• Additionally it would be great, if we could use the handy OSX/iOS way to share an import documents (PD patches) via Airdrop, etc. ... share ... open in: https://stackoverflow.com/questions/3981199/adding-open-in-option-to-ios-app

[timothyschoen]

• Load & Save Patches does not work yet. Browser window opens, but not Patch will open, nor you can save a Patch on Mobile

Kind of, it does work, but iOS doesn't allow you to open/close files from any location for security reasons. It will only allow you to open/close patches if they are in the "plugdata" folder in documents.

So right now, the best workflow is to airdrop your patches over, save them in the "plugdata" folder, and work from there. You should also be able to save inside the plugdata folder. I'm not sure if there is any workaround for this, I couldn't find any.

• Additionally it would be great, if we could use the handy OSX/iOS way to share an import documents (PD patches) via Airdrop, etc. ... share ... open in: https://stackoverflow.com/questions/3981199/adding-open-in-option-to-ios-app

I agree, I'll work on that!

[o-g-sus]

Yeah, found out about the workaround already :)

"It will only allow you to open/close patches if they are in the "plugdata" folder in documents." - That's correct.

But with the "open in" function you can load PD files from other locations of the device then also

[timothyschoen]

I suppose this is kind of fixed? It was only that the label is named "move" right?

I agree that that's a weird name for the button, but I'm not sure how to solve it

[60-hz]

I guess that "save to" might be more meaningful.

[o-g-sus]

You can find no "move" Sting in the Project? iOS branch is in develop right?

[Carnarts]

Hi, thanks for the update today :) Definitely working better in the UI on iOS AUv3 (although still some of the dropdowns in the settings can't be opened it seems) But main issue is I'm having problems opening any pd patches which aren't self contained and need other files. Whatever I tried (also moving files further up the folder tree etc) doesn't work for me yet, I get a string of errors in the console. I don't think this was a problem before, the patches could be opened without those errors.

[timothyschoen]

Hi, thanks for the update today :) Definitely working better in the UI on iOS AUv3 (although still some of the dropdowns in the settings can't be opened it seems) But main issue is I'm having problems opening any pd patches which aren't self contained and need other files. Whatever I tried (also moving files further up the folder tree etc) doesn't work for me yet, I get a string of errors in the console. I don't think this was a problem before, the patches could be opened without those errors.

Correct, I still need to fix that. I only fixed files access in plugdata's own source code, but I didn't fix it yet within Pd itself. So actions that are handled by plugdata (like opening/saving patches) work on iOS, but everything handled from within Pd (like abstractions, audio, images) does not.

I wonder how PdParty is able to access patch resources from Pd? Maybe @danomatika knows?

[danomatika]

libpd_add_searchpath()?enohp ym morf tnes-----------Dan Wilcoxdanomatika.comrobotcowboy.comOn Jan 31, 2024, at 8:37 PM, Timothy Schoen @.***> wrote:

Hi, thanks for the update today :) Definitely working better in the UI on iOS AUv3 (although still some of the dropdowns in the settings can't be opened it seems) But main issue is I'm having problems opening any pd patches which aren't self contained and need other files. Whatever I tried (also moving files further up the folder tree etc) doesn't work for me yet, I get a string of errors in the console. I don't think this was a problem before, the patches could be opened without those errors.

Correct, I still need to fix that. I only fixed files access in plugdata's own source code, but I didn't fix it yet within Pd itself. So actions that are handled by plugdata (like opening/saving patches) work on iOS, but everything handled from within Pd (like abstractions, audio, images) does not. I wonder how PdParty is able to access patch resources from Pd? Maybe @danomatika knows?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>