Octolapse gcode question

Octolapse supports custom start and end gcode that starts, stops, and triggers directly a snapshot. Do these triggers work correctly when the print is started from the printer's SD card? I wasn't easily able to find clarification, and am currently unable to test it myself.

Most gcode-reacting plugins have no idea what is going on with SD card prints, we don't get much information back from the printer. So no, for OctoLapse to be able to do anything then OctoPrint must be controlling the print.