03-05-2020, 05:37 AM
Hello Holger,
The only thing that has changed with chord pro processing in the last 20 updates or so is that I now have to read through the document multiple times as I calculate the original key of the document on the fly instead of having it stored as a separate value in the database. This should require barely any processing time though, so I'd be really surprised if that is the cause of the display flickering for you. Nothing has changed even in the last 8 updates related to chord pro processing that would cause flickering, so I don't think the updates are responsible for that.
Display formatting across multiple tablets in book mode is not something I can synchronize at the moment. It would be incredibly complex for the slave device to have to wait for the master device to tell it how the pages are structured and what it should render on its screen. In fact, the master would have to render page 1, then the slave page 2, then the master 3 before the slave can know how it should render page 4, and so on. MobileSheetsPro is not set up for that at all - the "Connect Tablets" feature expects that each device has its own independent library and the communication between devices is very simple (i.e. message to turn pages, load this song or setlist, or trigger this pedal action). You will have to format your documents appropriately so that they are displayed on each screen as you desire. This is why it is fairly important to use two identical tablets if you need the rendering to be the same on each display. I can't promise I'll be able to modify the "Connect Tablets" feature with book mode so that it considers multiple devices when laying out chord pro files. That would basically require a completely new implementation of not only the messaging between the tablets but the actual rendering of the chord pro file itself.
Mike
The only thing that has changed with chord pro processing in the last 20 updates or so is that I now have to read through the document multiple times as I calculate the original key of the document on the fly instead of having it stored as a separate value in the database. This should require barely any processing time though, so I'd be really surprised if that is the cause of the display flickering for you. Nothing has changed even in the last 8 updates related to chord pro processing that would cause flickering, so I don't think the updates are responsible for that.
Display formatting across multiple tablets in book mode is not something I can synchronize at the moment. It would be incredibly complex for the slave device to have to wait for the master device to tell it how the pages are structured and what it should render on its screen. In fact, the master would have to render page 1, then the slave page 2, then the master 3 before the slave can know how it should render page 4, and so on. MobileSheetsPro is not set up for that at all - the "Connect Tablets" feature expects that each device has its own independent library and the communication between devices is very simple (i.e. message to turn pages, load this song or setlist, or trigger this pedal action). You will have to format your documents appropriately so that they are displayed on each screen as you desire. This is why it is fairly important to use two identical tablets if you need the rendering to be the same on each display. I can't promise I'll be able to modify the "Connect Tablets" feature with book mode so that it considers multiple devices when laying out chord pro files. That would basically require a completely new implementation of not only the messaging between the tablets but the actual rendering of the chord pro file itself.
Mike