Evan

Does anyone know where this might be located, or what Component it would be?

All the other components are preset, but I can't find the SpecialSessionComponent in the Push script. All the other scripts have this, and I am using it to allow MIDI notes to trigger scenes of the session 'redbox' depending on what script you have selected. I have successfully done this with the Launchpad, APC etc. but I can't find any session component in the Push script.

Does anyone know where this might be located, or what Component it would be?
All the other components are preset, but I can't find the SpecialSessionComponent in the Push script. All the other scripts have this, and I am using it to allow MIDI notes to trigger scenes of the session 'redbox' depending on what script you have selected. I have successfully done this with the Launchpad, APC etc. but I can't find any session component in the Push script.


cannot-find-the-sessioncomponent-in-the-push-script

Try just looking for SessionComponent...?

Give me a little credit Lee. I wouldn't ask if it was that simple.

The script uses a SpecialSessionComponent per the script. I also went through the 100 + components by hand using gettype into live.object, none returned a name of SessionComponent or SpecialSessionComponent.

Give me a little credit Lee. I wouldn't ask if it was that simple.
The script uses a SpecialSessionComponent per the script. I also went through the 100 + components by hand using gettype into live.object, none returned a name of SessionComponent or SpecialSessionComponent. 

lol, I wasn't trying to be funny... Push is organised somewhat differently from the other scripts and has a grab/release mechanism for accessing different controls on the surface... Not quite sure how your patch works, but normally you would use the m4l api to fire scenes - is that what you are doing? Are you using the session component to figure out where the red box is? is that what you're after?

Yeah, I'm familiar with the grab/release functionality, I don't need to be doing anything like that. I just need to get the scene offset of the selected script. I'm working on a foot controller patch for a dude, and I thought it'd be cool to add support for all the major control surfaces. All the others were cakewalks, but I couldn't find any info on a SessionComponent after poking in around the script through the API for a good while.

You want the 'Session_Control' component and then issue a 'call scene_offset' to it

Where exactly did you find that? That doesn't appear in either the component or control list through querying with the API. Also searching the Push.py file for 'Session_Control' turns up nothing. Thanks for your help in this, it's proving to be my white whale for the day.

Found the following in SessionComponent.py file in the Framework, so thought it was worth a try :)

Seems this is what it gets called unless it's explicitly provided by the script (as in the older ones...)

    def _auto_name(self):
        self.name = 'Session_Control'

Seems this is what it gets called unless it's explicitly provided by the script (as in the older ones...)


Alright, so after combing through the github with all the decompiled scripts I stumbled upon something:

self._c_instance.set_session_highlight(0, 0, 8, 8, True)

self._session_mode = LazyComponentMode(self._create_session)

self._zooming_mode = LazyComponentMode(self._create_zooming)

The session is initialized in a this LazyComponentMode call. This in the framework, and basically it means that the object is only created when this mode is entered. So I entered session mode, and lo and behold, the SpecialSessionComponent appears in the component list at position 113, right after the HandshakeComponent.

Now the challenge will be initializing this device properly if the Push script is the one they want to watch.

Alright, so after combing through the github with all the decompiled scripts I stumbled upon something: 

def _init_session(self):
        self._c_instance.set_session_highlight(0, 0, 8, 8, True)
        self._session_mode = LazyComponentMode(self._create_session)
        self._zooming_mode = LazyComponentMode(self._create_zooming)

The session is initialized in a this LazyComponentMode call. This in the framework, and basically it means that the object is only created when this mode is entered. So I entered session mode, and lo and behold, the SpecialSessionComponent appears in the component list at position 113, right after the HandshakeComponent.  

Now the challenge will be initializing this device properly if the Push script is the one they want to watch.


You can listen to the press of the Session Button at start up after its been pressed then go and get the SessionComponent for calling the get _scene_offset it's not observable so you'll need to observe the bank buttons... These are named different things on lots of different control surfaces so you've got a long job ahead of you!

Thanks for the info! I actually found that you can get the call the 'scene_offset' function on the SessionComponent to get the offset. I'm using a metro to poll it every 50 ms, and it seems to be doing a fine job. The challenge for this device,like you've noticed, is that if I want this to initialize properly for all the scripts that have a redbox functionality, I need to create a section of the patch that is particular to Push, using the Session_Button as the gatekeeper.

[SOLVED]Cannot find the SessionComponent in the Push script.