Problem loading OCIO package in V2 apps

[DM1]

I have an aces_1.0.3.ocio package that previously loaded in V1 but after navigating to the folder there is no option available to select/install this packe in V2. 
I don’t know if this is an Affinity issue or an ios16 issue.

[Demys]

Exact same problem here. The folder is seen by iOS as a ocio config, so it should be straightforward.

The app is supposed to be compatible with iOS 16 as stated on the website. But it looks like not everything is.

[Demys]

Still not working on the new 2.0.2 updates.

[BiteDXH]

On 11/19/2022 at 2:54 AM, Demys said:

Still not working on the new 2.0.2 updates.

Me too. Common software can generally choose ocio. config file, I wonder why affinity always needs to be imported in the form of a package.

[Chris B]

I'm not sure what's going wrong as it's working fine for me. How I set it up:

1. Download the aces_1.0.3.ocio on macOS
2. Rename to include .ocio if necessary
3. Move to iCloud
4. On iPad go to Preferences > Colour > Choose OCIO package > iCloud > aces_1.0.3.ocio > config.ocio
5. As soon as I tap config.ocio the app loads it in—exactly the same process as V1

[DM1]

39 minutes ago, Chris B said:

exactly the same process as V1

V1 - downloaded package to iPad. Use Files app to rename folder  .OCIO. Navigated from AP to package and loaded  (as per help file). Now it no longer loads that way in V1 or V2.

Same directions in help file v2. They don’t work and don’t suggest using Mac and iCloud 😟

[Chris B]

I don't think using a Mac is essential. I just find it easier to use. I'll try the entire process on iPad. Perhaps something is going wrong at the rename stage.

[DM1]

9 minutes ago, Chris B said:

I don't think using a Mac is essential. I just find it easier to use. I'll try the entire process on iPad. Perhaps something is going wrong at the rename stage.

Thanks Chris. This may be something to do with ios16. I tried uplaong the package to iCloud and installing from there but no go.

I suspect it may be the config.OCIO file. I can’t open/read it on my iPad just 142kb file size.

[Chris B]

Ah https://discussions.apple.com/thread/253014170

[DM1]

@Chris B I’m not sure how accurate that it. iPad Files app changes file/folder names. After renaming,  the folder is even idifified as a config not as a folder. I know it worked prior to iOS 15 as I did it all on my iPad in APv1.

If you copy the Aces config folder to iPad will it load from there.

Are you able to open the config.OCIO file on iPad? Mine won’t display any content.

[Chris B]

6 minutes ago, DM1 said:

Are you able to open the config.OCIO file on iPad? Mine won’t display any content.

Nope.

We really need to hear from Dev tbh. I'm still waiting on a reply. You don't have a desktop that you use for Affinity, do you? 

[DM1]

21 hours ago, Chris B said:

Nope

Unfortunately no.

Files Quickview won’t open config file but Documents viewer does open it and the content looks fine.

So I have a folder whose info states it’s a config (not folder) and the contents all there but AP won’t see the config file to install. Given AP uses Files app to navigate maybe Quickview is the issue as Quickview seems unable to read the file.

Edit: copying the files to iCloud and trying to load from there didn’t work either.🙁

[Demys]

One month later and this is still not working.

Everything is done like explained in the help, which does not work.

renaming the folder on a Mac is not a solution, I don’t own one, and you should not have to use workaround like this to use a full feature for a software advertised as fully compatible with iOS 16.

I’m starting to regret having bought the full v2 package to support you, one month with a broken main feature, not a small bug, is not acceptable.

[DM1]

1 hour ago, Demys said:

I’m starting to regret having bought the full v2 package to support you, one month with a broken main feature, not a small bug, is not acceptable.

Yes, it’s annoying. To be fair, Serif staff are flat out and I suspect it’s more related to Apple changing something in iPadOS. It worked in V1 for iOS14 but won’t reinstall on V1 in iOS 15/16. What changed? IOS. In the meantime I'll wait and see what mods report back🙂

[Demys]

Can we please at least get some info about this, is the issue know by the dev ?

So far we only had the answer of one of the team member who was unable to help us at all, only giving us non working solution.

[Chris B]

On 12/28/2022 at 5:47 PM, Demys said:

is the issue know by the dev ?

Yes it is. I have updated the bug report numerous times. I absolutely appreciate that using a desktop to do the renaming is not a viable option for all. As DM1 suggested, I suspect it may be a iPadOS change. I'll bump the report again.

[Elka_]

Hello guys, just as you I'm struggling with this problem, I don't have a mac to change the file in an OCIO config, and everything I tried doesn't work. But I was wondering, if someone would send me an OCIO config coming from a folder and transformed in a file with a mac, would it work ? I don't know if it's clear, but my point is : doesn't it work because I'm unable to change the extension of my folder to make it a file, or because for some reason affinity doesn't want of my file ? Sorry if the question has already been answered, I'm trying to make things more clear in my mind. Thanks !

[DM1]

15 hours ago, Elka_ said:

coming from a folder and transformed in a file with a mac, would it work ?

I don’t think so. I had a working copy in V1 that I inadvertently unloaded. Now in won’t load in either version 1 or version2. I think the issues is that iOS Files app no longer reads the config.OCIO file format. I can open the config file in Files app (the way Affinity accesses files), but it appears empty. I can open the same file in Documents reader and see the content. 

[Elka_]

On 1/14/2023 at 7:23 AM, DM1 said:

I don’t think so. I had a working copy in V1 that I inadvertently unloaded. Now in won’t load in either version 1 or version2. I think the issues is that iOS Files app no longer reads the config.OCIO file format. I can open the config file in Files app (the way Affinity accesses files), but it appears empty. I can open the same file in Documents reader and see the content. 

 

 

Hmm yeah that could explain. I asked a friend wha has a mac to try changing the extension for me, we tried different ways of doing but nothing worked... I guess I'll have to wait for the fix then. Thanks for the answer !

[Habs]

So it's been a long time now, does this issue solved.

Why doesn't affinity build the .ocio file into the App?

[Leigh]

2 hours ago, Habs said:

So it's been a long time now, does this issue solved.

Why doesn't affinity build the .ocio file into the App?

Welcome to the forum. It's still an issue but it's logged with our developers

[Demys]

6 month later and still not fixed, a simple file loading issue breaking one of the main feature...nice !

it's a very good way to say that you don't care to a part of your user base.

 

I took the universal license for the possibility of using it on the go professionnally, but as all of my work use OCIO managed pipeline i just can't.

You know that seeling product with non-working advertised feature became illegal in some country if it's not fixed after certain amount of time ?

I was ok with the bug at launch, but 6 month is too much, how can i ask for a refund of my license ?

 

[Leigh]

On 5/5/2023 at 2:08 PM, Demys said:

6 month later and still not fixed, a simple file loading issue breaking one of the main feature...nice !

it's a very good way to say that you don't care to a part of your user base.

 

I took the universal license for the possibility of using it on the go professionnally, but as all of my work use OCIO managed pipeline i just can't.

You know that seeling product with non-working advertised feature became illegal in some country if it's not fixed after certain amount of time ?

I was ok with the bug at launch, but 6 month is too much, how can i ask for a refund of my license ?

 

I'm sorry that you're still having this issue. I will try and get an update from our developers about this - i've also updated the internal bug report.

[DM1]

On 5/11/2023 at 5:44 PM, Leigh said:

I'm sorry that you're still having this issue.

I think this is an iOS issue. Files app is unable to read the config file. Documents app can read it. Apple need to fix Files app’s viewer. Perhaps Serif can persue this with Apple as they don’t respond to individuals.

[Demys]

On 5/12/2023 at 12:48 PM, DM1 said:

I think this is an iOS issue. Files app is unable to read the config file. Documents app can read it. Apple need to fix Files app’s viewer. Perhaps Serif can persue this with Apple as they don’t respond to individuals.

To be honest, i don't care if it's on apple or serif side, it's not my problem, i'm sorry if it sound rude, but i paid for a license AND a working software.

The website claim that it is fully compatible with IOS 16, wich is not. At this pace IOS 17 will be out before they even look at the issue.

 

I was patient, waited for a fix after this post was created and the issue acknowledge, but 6 month without even ONE workaround ? come on...

Imagine if i made my clients wait 6 month to clean an error coming from my side ? I could actually get sued for this and that's not even a joke

 

One of the needed feature for me doesn't work, without this one i wouldn't have bought it in the first place.

That's all i care, because while this issue is still not fixed i can see some new "useless" feature for the 2.1 beta, i feel betrayed and that's kind of sad, you lost my trust and while at the time of the V1 i talk about affinity in a positive way, that's no longer the case.