I recently set out to use Custom Controller and Editor to create a setup for volunteers in a church setting to have access to only the main fader of a Dlive board we use for our overflow and youth room. I unfortunately am stuck and can’t seem to find any information on the issue I’m experiencing which is that I am able to successfully upload my config from editor to the board (made known by a positive pop up message in the editor), but when I connect the CC app on the Ipad to the board, it connects but says “No Layout found”. I know that the Ipad is fully connected however because when I have it open and upload my config to the board again, it refreshes on the Ipad as well, but still finds no layout, despite a positive message on my laptop. Has anyone else experienced this or have any thoughts on what the issue might be? I was trying to find a way to verify that the layout lives somewhere on the board but didn’t find a way. Also, I don’t believe it has to do with user permission either, unless I am misunderstanding something which is very possible.
Did you assign a specific user to the layout in the CC editor? (This option is on the first screen that appears when you start a new layout - but is also available for editing at anytime). If you did and the user trying to load the layout isn’t the same user specified in the editor, it obviously won’t work.
I don’t know if that is the problem or not, but it would be an easy thing to check and fix if it is the problem.
I also thought it may be this issue but today sat and looked through everything and don’t think I’m missing anything? Where all do these settings need to be lined up? Currently in my Custom Control editor I have the name of the user set with the layout. On my board I have a user with that name and a password, and then I’ve logged in on the Custom Control Ipad with that user and password. Is that everything user related? If it’s not user related, I wondered if it may be a version compatibility issue?
Normally when you’re unexpectedly seeing “No layout found” it’s because you’ve added some limitation under Layout Manager → Details (bottom right of the layout selection)
If you’re limiting by device type, it could be that the app is incorrectly identifying your tablet as some other device (possibly if the display resolution is very high)
Alternatively, if you’re using preset-based switching you may need to check the latching option which will make that layout “sticky” if the preset requirement is not true.
Finally, you can also sometimes get this happen if you’ve set Screensaver to true in Config Options but not set a layout as a screensaver in the layouts. Either create a layout and check then screensaver box on its Details pane, or uncheck screensaver on Config Options.