Regarding the automated naming on Harrison Daw

Your insistence that our workflow is wrong is getting exhausting, and you keep refusing to understand the reasoning behind it: this is a venue with a different event every day, run by different people.

If I say I don’t want to route the patch through the surface, there’s a valid reason for it. So it makes no difference to me whether I patch via Direct Out or Record Send.

I send whatever is connected to the stage box to the recording, because I don’t want the house tech to have to analyze and understand the visiting engineer’s show file. I know which channels come in from the stage, and if I patch the entire box, I know for certain that every channel is recorded and there’s no room for human error.

You keep saying the option to name stage box inputs doesn’t exist, but this is a feature request forum. Obviously it doesn’t exist, otherwise I wouldn’t be posting here. This feature exists on DiGiCo, which belongs to the same parent company, so I assume it’s technically feasible. If they want to implement it, they will. If not, they won’t.

Also, your suggestion doesn’t work. Just checked it.

With record send enabled, Harrison still takes the channel names by its order on the surface and not by the patch

Record send is not a direct out, it’s a tie line.

But it wouldn’t change any of your problem. Still there can be wrong named sockets, still you have to control that, still names will likely end up wrong.

So is my venue. :wink:

1 Like

In the hipothetical situation where names can be pulled from the socket, why would it likely end up wrong?

OK FELLAS, I was able by 15 mins of vibe coding on claude to create this feature and it works perfectly.
it pulls the input data from the csv file, arranges it by order of socket inputs and creats a new organized csv file that you can pull to LiveTracks.

to be honest, even I didn’t thought it would be that easy, so now all I have to do is to download the csv file from Dlive Director to a designated folder, and then pull the new adapted file (that was automatically create) from that folder to Live tracks (I had to do it Via the SSL Live control Surfaces option because it has the option to select "Import track names from a csv file)
so if I was able to do it with Vibe Coding, I’M SURE that the A&H developers can manage to work a way of doing it!

1 Like

An example of How it works:

New show means new names. If your system is a new show every day, it will be new names every day.

Again, check out record sends.

Well…

Of course not. But it could be a defined starting point.

That’s silly. You do your setup again and again …

1 Like

No, I don’t.

I make sure the patch is correct and that’s it.

Checking could be done in Harrison as well then. :winking_face_with_tongue:

There is no do it all solution here unfortunately. I think grabbing the channels ordinary and then checking the recording deleting all unassigned stuff is the quickest solution. Nevertheless cool workaround, I did program scripts for reaper to use in conjuction with the dLive. :blush: