getDirectory returning fraction of all crosspoints

[thorsby]

I'm trying to subscribe to all crosspoints on a device with a matrix of 296 outputs.

Using the callback to getDirectory, I only receive crosspoints for the last 6 targets of the entire matrix. The subscription is working for these 6 crosspoints with updates on changes, but not initially or on changes I get the missing 290 crosspoints.

client.connect()
  .then(() => client.getElementByPath('1.11.2'))
  .then(node => {
    return client.getDirectory(node, update => {
      console.log(update.connections);
    });
  })

{
  '290': MatrixConnection { target: 290, _locked: false, sources: [ 2 ] },
  '291': MatrixConnection { target: 291, _locked: false, sources: [ 3 ] },
  '292': MatrixConnection { target: 292, _locked: false, sources: [ 4 ] },
  '293': MatrixConnection { target: 293, _locked: false, sources: [ 5 ] },
  '294': MatrixConnection { target: 294, _locked: false, sources: [ 6 ] },
  '295': MatrixConnection { target: 295, _locked: false, sources: [ 7 ] }
}

Am I missing something basic of Ember+?
On the same device is another much smaller matrix of 8x8, where same code yields all 8 crosspoints.

[thorsby]

I might add that this is a Lawo device, so I would presume their implementation is up to spec.

[Bencosterton]

I see this is an old issue, I see the same when trying to expose the audio matrix directory on a vpro.

• I note the node path is the same in the above example (1.11.2), possibly the above issue related to Lawo VPRO also..

const { EmberClient, EmberClientEvent } = require('node-emberplus');
const yargs = require('yargs/yargs');
const { hideBin } = require('yargs/helpers');
const argv = yargs(hideBin(process.argv))
    .option('host', {
        alias: 'h',
        type: 'string',
        demandOption: true,
        description: 'Lawo VPRO host IP address',
    })
    .option('port', {
        alias: 'p',
        type: 'number',
        demandOption: true,
        description: 'Lawo VPRO port',
    })
    .help()
    .argv;

async function runClient() {
    const { host, port } = argv;
    const client = new EmberClient({ host, port });

    try {
        await client.connectAsync();

        let matrix = await client.getElementByPathAsync("pro8/Video-Matrix/Matrix");

        await new Promise(resolve => setTimeout(resolve, 100));

        if (matrix.connections) {
            const formattedConnections = {};
            for (const [target, connection] of Object.entries(matrix.connections)) {
                formattedConnections[target] = {
                    target: connection.target,
                    sources: connection.sources
                };
            }
            console.log(JSON.stringify(formattedConnections, null, 2));
        }

    } catch (e) {
        console.error('Error:', e.message);
    } finally {
        await client.disconnectAsync();
        process.exit(0);
    }
}

runClient();

{
  "294": {
    "target": 294,
    "sources": [
      6
    ]
  },
  "295": {
    "target": 295,
    "sources": [
      7
    ]
  }
}

It seems as though the VPRO is offering up the matrix connections is groups of ten (output from EmberPlusView;

<Root Type="ElementCollection">
  <Matrix Path="1.11.2">
    <Contents />
    <Children />
    <Connections>
      <Connection Target="0">
        <Sources>176</Sources>
        <Disposition>1</Disposition>
      </Connection>
      <Connection Target="1">
        <Sources>177</Sources>
        <Disposition>1</Disposition>
      </Connection>
      <Connection Target="2">
        <Sources>178</Sources>
        <Disposition>1</Disposition>
      </Connection>
      <Connection Target="3">
        <Sources>179</Sources>
        <Disposition>1</Disposition>
      </Connection>
      <Connection Target="4">
        <Sources>4</Sources>
        <Disposition>1</Disposition>
      </Connection>
      <Connection Target="5">
        <Sources>5</Sources>
        <Disposition>1</Disposition>
      </Connection>
      <Connection Target="6">
        <Sources>6</Sources>
        <Disposition>1</Disposition>
      </Connection>
      <Connection Target="7">
        <Sources>7</Sources>
        <Disposition>1</Disposition>
      </Connection>
      <Connection Target="8">
        <Sources>8</Sources>
        <Disposition>1</Disposition>
      </Connection>
      <Connection Target="9">
        <Sources>9</Sources>
        <Disposition>1</Disposition>
      </Connection>
    </Connections>
  </Matrix>
  <Matrix Path="1.11.2">
    <Contents />
    <Children />
    <Connections>
      <Connection Target="10">
        <Sources>10</Sources>
        <Disposition>1</Disposition>
      </Connection>
      <Connection Target="11">
        <Sources>11</Sources>
        <Disposition>1</Disposition>
      </Connection>
      <Connection Target="12">
        <Sources>12</Sources>
        <Disposition>1</Disposition>
      </Connection>
      <Connection Target="13">
        <Sources>13</Sources>
        <Disposition>1</Disposition>
      </Connection>
      <Connection Target="14">
        <Sources>14</Sources>
        <Disposition>1</Disposition>
      </Connection>
      <Connection Target="15">
        <Sources>15</Sources>
        <Disposition>1</Disposition>
      </Connection>
      <Connection Target="16">
        <Sources>176</Sources>
        <Disposition>1</Disposition>
      </Connection>
      <Connection Target="17">
        <Sources>177</Sources>
        <Disposition>1</Disposition>
      </Connection>
      <Connection Target="18">
        <Sources>178</Sources>
        <Disposition>1</Disposition>
      </Connection>
      <Connection Target="19">
        <Sources>179</Sources>
        <Disposition>1</Disposition>
      </Connection>
    </Connections>
  </Matrix>
.....

  <Matrix Path="1.11.2">
    <Contents />
    <Children />
    <Connections>
      <Connection Target="294">
        <Sources>6</Sources>
        <Disposition>1</Disposition>
      </Connection>
      <Connection Target="295">
        <Sources>7</Sources>
        <Disposition>1</Disposition>
      </Connection>
    </Connections>
  </Matrix>

node-emberplus is only seeing the last 'group' of connections.

[thorsby]

• I note the node path is the same in the above example (1.11.2), possibly the above issue related to Lawo VPRO also..

Correct, it was a VPro. I have not worked with it since though.