I had a similar situation once - it helped to enter the midi settings - selecting none - and re-selecting the midi in/out device
BECOME PART OF THE COMMUNITY - Sign up here
"The latest version of the code for Dot2 and APC Mini MK2.
Added support for Core Fader (wing = 0) with simultaneous use of B-Wing 1 on the top buttons."
In the code for apc mini mk2 I introduced some new features
The brightness of the buttons can be adjusted.
Additional dark mode (gray colors plus green and red)
And the page with the color palette (def page 5)
There is a page-switching part in your code - it's just marked as a comment/description... between /* and */.
Just remove lines 159 and 175 - and everything will work
the name of the page variable can be a bit misleading - because it is responsible for the page switching mode - for b-wing , and for b-wing and f-wing
I used to upload a MA3 fixture (GDTF) to the Fixture Share website and it would convert it to XML, but I'm not sure if it still works.
Unfortunately, the Release option (which you select by clicking on the encoder field) is no longer available in the Effects mode. Even selecting a preset with Release as a Low or High Value does not work, which is a shame.
As I mentioned earlier, switching between wings would make sense if the faders were motorized.
Unfortunately, I am not able to test your code because I got rid of my old APC Mini and switched to APC Mini MK2. Unfortunately, these new controllers have slightly different MIDI notes under the buttons and color control commands.
Fortunately, I have already managed to deal with it, and the updated code is on my GitHub.
Okay looks like I got it.
Store Time and remove option
I'm having trouble with the entry time. On the slider, as the master, I have one cue with an entry time of 5 seconds and an exit time of 5 seconds. Everything was okay until I briefly switched the slider's mode to Time (for test). Now, no matter what entry fade time is entered, the scene starts as if the time is 0. The offcue time still works correctly. How can I remove the information about changing to Time?
it looks a bit like this sequence has executortime set to 0.
Thank you - works -
It's a pity that it doesn't work when the executor is set to Swop or Flash - but it can also work with Temp
OnPC only supports one midi input - so no
But you have two choices - use midiox and loop midi - connect both midi devices to ox midi and send to loop midi - and set loop midi in onpc
In midi ox, if necessary, you can convert notes to other - when they will overlap in both devices.
The second possibility is to use your controller with software that will convert midi to OSC (e.g. chataigne)
I do not have access to the console to test it - but I hope that there is a chance to read everything - I suppose that the dot2 system is placed on linux - so it will be most convenient to connect this disk to a computer with linux - just run it even without installation from a flash drive - e.g. ubuntu or mint.
I hope you can fix the dot2 as soon as possible.
So the Coarse and Fine Resolution value changes while on Physical Readout (which is also the Natural Readout for Pan and Tilt) will be based on the Pan and Tilt ranges of the selected fixtures.
OK - but why is sometimes normal resolution and sometimes fine resolution - if I don't change it
I'm not sure what causes it, but sometimes the pan/tilt encoders add values that are either greater or less than expected. For example, when I move the PAN encoder, the value increases by 4.50, while the TILT encoder increases by 2.25. This might be related to the pan/tilt range, but why isn't the value increase consistent at 1?
There's also another issue - when I switch to controlling the RGB colors using an encoder, which increases the value by one, and then switch back to controlling the position, the value added is only 0.01????
Is there any way to fix this?
I will add that I use web remote and mouse wheel
I found a small bug - when calling Select EncoderPage # - the program doesn't highlight the appropriate tab.
This happens when, for example, we have fixtures in the patch without a certain attribute, such as a gobo.
Now, when I type in the command line:
Select EncoderPage 1 - the program correctly highlights DIMMER
Select EncoderPage 2 - the program correctly highlights POSITION
Select EncoderPage 3 is for gobo - so this command does nothing OK
Select EncoderPage 4 - the program highlights BEAM - and it should be COLOR - however, I can control the color encoders.
And now something interesting:
Select EncoderPage 5 - highlights BEAM (it's correct)
Select EncoderPage 6 - highlights CONTROL - but I can control FOCUS
Select EncoderPage 7 - highlights CONTROL, everything is OK
And now, when I choose again:
Select EncoderPage 5 - the system highlights FOCUS - but I can control the encoders for BEAM.
Of course, if I use a mouse or touch screen - everything works correctly - the error only appears when calling the command from the command line.
I don't have much experience with linux - maybe someone has more knowledge on this subject - unfortunately I didn't even manage to run 3d properly.