It is clear that if you comment out the whole code, you won’t have your custom display anymore. This was just for testing purposes to confirm that the script is not responsible from that fact that you don’t have the values display when acting on the knobs.
Now you can remove the comments characters.
The question is now why you don’t have the knobs displaying values when you move them. If you had the proper display before it means that you changed something. But what?
Are you sure the Arturia’s spécial MIDI ports are still not open by GP? (ports unchecked)
i know…
i have to have arturia midiport active , there are two 1 is standard midi, if i turn this one off nothing at all happpens.
the second one is for daw control wich is disabled,
what id did in arturias midiprogamming (separate programm on win) is i changed the pads from notes to PC thats all.
i tried now by loading a default arturia user preset - same thing.
i can go on user mode (on the mkII) the sliders and knobs show values
but only the names of the slider and the value it sends
but not the corresponding names to the active synth therefore it is useless.
i believe i have to go “second small computer screen” mode with a
“make-a-button-to-open-close-the- vst” widget @schamass is fiddling around with - so the keyboarder see`s it there,
not to forget cover arturias display with ducktape (hunderttausendjaulendehöllenhunde 
)
There is not much I can do to help you to recover the original display of knobs values… this is not related to Gig Performer, but I could imagine replacing any original display by a custom GP one. But doing so, you would need to customize each of the knobs you use…
1 Like
exactly, therefore i go for a “small secondary” screen version, so the computer can be “hidden” just a small screen next to the ipad where my keyboarder has his sheets…
with my rig it is pretty cool as i have a lenovo yoga with touchscreen - and he works with pianoteq plus 5 arturias loaded very well (cpu load round 50-60%)
what is interesting my studio workstation (win 8.1) with rme babyface pro:
i can run pianoteq standalone and have GP open “only” with synths and it is less cpu hungry than having pianoteq within GP…
thank you very much for your help!!
during this “workshop” i learned a lot!!
1 Like
Maybe because Pianoteq uses a core and GP uses a different core.
Same advantage you should have when you are using different instances of Gig Performer
xactly - and pianoteq is “clean” on opening midiports (my numa only active on midi in pianoteq)
probably interesting for a “all songs programmed” setup, in our case not, as our keyboarder indeed wants different synth setups but straight access to pianosounds (all pianoteq) from the keyboard buttons themseves (two grands,one cp80,one rhodes clean,one wurly barky,one clavinet) does it for him.
Further developments of this topic here…
4 posts were split to a new topic: Displaying text on a text reader for visually impaired users