Technical Support Incident (TSI) response time?

Hello StewMacLean, if you share your Follow-up or Case ID number, I'm happy to take a look.

Normal response times is "typically within three business days", which can vary depending on volume, complexity, and a variety of other reasons. While it's rare that you don't hear a response from a DTS engineer within that time, it does sometimes happen if the team is especially busy.

Thanks,

—Jason.

Hi Jason,

I appreciate that the team is no doubt very busy which is why I've interpreted "three days" to be "three weeks" - being typically realistic:)

My case number is 1583582 "Application (Logic) not responding to CGEventPostToPid when without focus".

I've also posted on the forum, https://developer.apple.com/forums/thread/724835 "CGEventPostToPid not posting to background app's open dialog".

Please also note, that I discovered this whilst implementing a work around with issues positioning the playhead via Logic's Control Surface Midi Device Plugin.

Here are my previous submissions related to this:

https://developer.apple.com/forums/thread/706826 "Logic Pro Position Playhead Controller Assignment Bug?"

FB11998352 Move playhead by bars doesn't take into account multiple time signatures

FB12009078 Move By Divisions Doesn't Work

FB12011386 Move By Ticks Doesn't Work

All of these issues, including the attendant one, would go away (for me at least!) if the following request is implemented:

FB11998414 Midi Device Plugin - Go To Position (Bars, Beats, Divisions, Ticks) Command Request

This functionality is what I'm cludging via posting events to the UI version of this function. Given that the UI functionality (and by implication Logic's engine) exists, it should be trivial to implement this.

It would be nice to know if someone is "scratching their head", on any of these.

Thanks for looking into this.

Cheers

Stew

Hi Stew, thanks for the Case ID and the additional context.

I can confirm that the case is assigned to a DTS engineer, and it's a matter of making their way through the rest of their requests to get to yours. My apologies for it taking as long as it has, but as I alluded to, the team is very busy right now.

That said, I'm unsure if it's a question DTS will be able to help you address, as the issue seems to be specific to Logic (rather than your code). Of course, this is a preliminary look, and I'm not by any stretch a CG expert, so there may be something you can do differently or instead. A DTS engineer will make that determination once they get to your case.

As an aside, I also took a look at your feedback reports, and all of them are with the appropriate MIDI teams. I wouldn't expect a "near term" resolution; it could be several months, a year, maybe more before it's resolved (assuming it is at all).

—Jason.

Hi Jason,

Thank you for following this/these up. I've had a response from a DTS engineer, who has confirmed the issue and passed it on to the CG team.

With regard to the other reports, as I mentioned, I can workaround the move bugs in mixed meter if the absolute positioning by bars, beats, divisions, ticks command is implemented in the device interface. This should be trivial as the functionality already exists in the UI, and by implication in the engine. This is the ideal resolution to all these issues, for me at least.

I have spent years on the development of my product part time, and over the last few months I've dedicated myself full time to this to give it the last push to get into production. I appreciate these things don't happen overnight, but to hear that it could take years or not at all is disappointing.

Thanks again for looking into this for me.

Cheers,

Stew