OOPS

[Kalman Tarr]

Hi guys,

A new Ventura vs Monterey (or below) issue I experienced.

(Maybe or maybe not.)

I am using a QLab 4 project, it is contains some video cue.
The first is special one, Let's call it to 'defCue'. 

I change its surface setup and I tried to set others to this surface. 

I get 'defCue' surface name using the next OSC command put it to the notes field:
/cue/getName/notes "#/cue/selected/surfaceName#".
'getName' is the q number of this OSC cue.

After all, I am using a script to give others the new surface name.
I wrote the next script on Ventura (M1) machine:

tell application id "com.figure53.QLab.4" to tell front workspace

set theSelected to last item of (selected as list)

set theCue to cue "getName"

start theCue

--delay 0.1

tell current cue list

set allCues to cues whose q type is "video" and armed is true

end tell

repeat with i from 2 to count of allCues

set qNumber to q number of item (i) of allCues

set oscCmd to "/cue/" & qNumber & "/surfaceName " & (notes of theCue)

do shell script "echo " & the quoted form of (oscCmd) & " | nc -u -w 0 127.0.0.1 53535"

end repeat

display dialog "Task completed!" buttons "Quit" default button 1

end tell

Nothing happens! I tried to run several times, and nothing.
The other's surface Names remains in their  original state.
OOPS
I airdropped the script onto my old Monterey Macbook Air machine.
It runs without any problem. Does the job.
I have no any idea, and yours? 

Help needed!
Maybe just for me.

I know there is a simple way to set others surface name. ctrl+A and ...

But the above is a challenge, isn't it?

I look forward to your good ideas. :-)

Best,

Kalman

[micpool]

No reason it shouldn't work

I only have an Intel Ventura Machine but it ran fine on that and my M1 Monterey

Mic

[Kalman Tarr]

Hi Mic,

As I mentioned, my new machine is M1 Ventura.
You have an Intel Ventura machine. 

This difference, big or small, I can not decide.
The older machine I have, is an Intel Monterey, the script runs fine.
I think the best option I can choose, to downgrade to Monterey on my M1 MAC.
Unfortunately, the latest MACOS is not a winner for me.
Thanks for your reply Mic.
Best,

Kalman

[micpool]

I'm not clear whether the script is running on your M1 Machine, or whether it runs and doesn't do anything. Do you get a Red Cross when it runs?

As all it is doing is copying doing an OSC query and copying the result to a few other cues, I can't see that the processor would make any difference.

Mic

[Kalman Tarr]

Mic, I do not get Red Cross or anything else.
Sorry, I guess I wasn't precise. Excuse me! 

In the script everything working but these two or just one line will not be implemented.

set oscCmd to "/cue/" & qNumber & "/surfaceName " & (notes of theCue)
do shell script "echo " & the quoted form of (oscCmd) & " | nc -u -w 0 127.0.0.1 53535"

(I learned from you before using do shell script technique.)

The best I go down to Monterey.

Thanks again for your reply.

Good night

Kalman

[Rich Walsh]

Downgrading the OS is a bit of an overreaction without at least running the script in Script Editor first to see what’s going on…

Works fine on my M1 Ventura machine.

You should also test the shell command raw in Terminal and see what happens:

echo '/cue/1/surfaceName yourSurface' | nc -u -w 0 127.0.0.1 53535

Rich

[micpool]

I think I was wrong stating that the processor shouldn’t make a difference, as there seem to be many documented instances where shell commands cease to function with Ventura on M1 and possibly M2.

I have some ideas  of what might fix this, but don’t know enough about it to feel comfortable making suggestions, that could potentially have serious consequences for anyone following advice that I am not really qualified or sufficiently knowledgeable  to give.

Presumably you have contacted Figure 53 support with the issue.

[micpool]

Hi Rich

Could this be an issue with granting full disk access to QLab in security preference.

I know I have visited this particular setting on a few occasions to get things working, but have been a bit negligent in noting when and why!

Mic

[micpool]

Leaving aside the ever increasing security hurdles with each  OS release, dealing specifically with what you are trying to achieve.

The script seems a very longwinded way of doing little more than what a single network cue, with a wildcard and a query could do (apart from checking if they are armed)

/cue/*/surfaceName "#/cue/selected/surfaceName#"

Will set all video cues to the same surface as the selected.

Mic

On Tuesday, May 23, 2023 at 7:14:03 PM UTC+1 tarr....@gmail.com wrote:

[Rich Walsh]

I don’t think so as I haven’t granted that permission to QLab. Also, QLab doesn’t need to access the disk to send a network message via AppleScript. I can’t find a relevant setting for network access; even fiddling with the firewall to prevent incoming connections to QLab doesn’t seem to stop the script from working.

It would be useful to know what Script Editor records; there will be an irrelevant -10004 error each time as QLab itself can’t run a shell script and has to pass that up the chain to the script runner (correct form would be “tell me to do shell script”).

Rich

[micpool]

Kalman,

Have you checked you are on the latest version of Ventura. There seems to have been some fixes for shell script issues in 13.3 (which may be entirely unrelated, but you never know)

On Tuesday, May 23, 2023 at 7:14:03 PM UTC+1 tarr....@gmail.com wrote:

[Kalman Tarr]

Hi Rich and Mic,

Today is a little bit busy for me.

But in the evening, I get home, I will check your advices.

Kalman

--
Contact support anytime: sup...@figure53.com
Follow QLab on Twitter: https://twitter.com/QLabApp
User Group Code of Conduct: https://qlab.app/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/5bb7aedb-0ed1-4d0b-9773-08e4013e71f3n%40googlegroups.com.

[Kalman Tarr]

Hi Mic and Rich,
First response to Mic, I checked the Os version: 13.3.1. OK
Noticeably the most fresh one.
I read Rich advice, took it, tried. See a miracle.
 IT WORKS. 

tell me to do shell script "echo " & quoted form of (oscCmd) & " | nc -u -w 0 127.0.0.1 53535"

I run the script outside the QLab in Script Editor.
I try to place a copy of the lines in the Qlab Script cue...
They are in it. I Run the Script and and and IT WORKS.
In the solution of this issue Rich has winning idea. !!The solution!!
Thanks guys.
I'll sleep well tonight!

Sincerely,
Kalman

[micpool]

Are you saying if you add 'tell me to' to that line it works, and if you now delete it , it stops working?

Mic

[Kalman Tarr]

Hi Mic,

The answer is YES!

But I have to say I did not try to delete that part of full command line.

It is too late today but tomorrow I will do. 

After trying I will inform you.

Good night.

Kalman

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/f6b444a1-bdbd-4d8a-b0ea-cf9ed3449672n%40googlegroups.com.

[Kalman Tarr]

Good morning Mic,

I deleted the “tell me to” as you advice.
And see wonder, it is working.
I understand nothing.
Trust me, it did not do the job to me before.
This was the reason I opened this conversation. 

You know, I mentioned several times, I’m not a pro scripter. 

I just want to do scripts I need for me. I never learned this method (the script). 

I just like to do.

I wanna to learn different, good methods from you and other pros.  excuse me I didn’t want to hurt anybody in this forum. 

I don’t really know what caused this.

I'm happy that I learned something new again.

Sincerely,

Kalman

[Kalman Tarr]

Hi guys,

I am back with a related problem in Q4.
A little thing I noticed.
A very small but really interesting problem.
In the list of surfaces there is a base surface called 'Surface 1'.
There is a space character in the name.
I would like to choose this one. I setup the frist "video" cue to this surface. I run the script to carry it out the setup on others.
That cues will not be adjusted. see Fig. no 1.
Maybe it's my imagination again? I think NO.
In that instant as I choose an other surface from the list or I delete the space character from the SF name everything runs  well.
What could be causing this issue?

Thanks in advence

Sincerely,

Kalman

[Kalman Tarr]

Hi guys,

I must apologize, this was a sad game of delusion.

It is working, change the surface to "surface 1".

Sometimes yes sometimes no.
Kalman

[Kalman Tarr]

Hi Mic and Rich,

I thought about 'tell me to' question for days.
Is it possible that the Silicon M1 proc is able to learn. OOPS
I mean, I showed it the 'solution' once. 

From that point it knows I skip (delete) the 'solution' in the future. 

Solution = tell me to
I just ask.

Best,

Kalman