08-11-2021, 05:28 PM
live wasn't the problem. the mrcc was the problem. Live was set up correctly, and i have always had success with the virtual ports there once the mrcc was 'seeing' the routing.
To sum up the problem - i have encountered now several times that setting up a routing using the host port did not work at first, and then 'magically' began working later on, despite (to the best of my knowledge) not engaging in anything different. I can't remember the first device in which i encountered this, but the second one was the Squarp Pyramid, where it was reported that others have reported issues. I now have a din connection set up there. In that case it really doesn't matter, since I realized (duh) that the pyramid can only send on one port/channel at a time.
But then I encountered the same symptoms with the ndlr. absolutely no luck at first I already understand and have used the basic routing tips that you have above, which is why this has been so puzzling. First (and why does the quick start say that you have to choose virtual usb port 1?) . What you describe is EXACTLY what i was doing. Holding down the left input button for the host part, and choosing the virtual port 1, then holding the right pc button. NOTHING. The port did not stay lit.
I can't remember now, so I suppose that I actually didn't do the 'second half' at first, but that wouldn't explain why the output light for the pc port would not stay lit.
After trying this out for quite some time, I noticed that it was staying lit, and all of the rest of it worked.
I should not have to select a din output port if I'm not using it, as my test didn't require it, and could easily yield a false positive, as at first (as has always been the case with the din outputs) it was simple to set up the host port input out through the din port. No problems there.
To sum up the problem - i have encountered now several times that setting up a routing using the host port did not work at first, and then 'magically' began working later on, despite (to the best of my knowledge) not engaging in anything different. I can't remember the first device in which i encountered this, but the second one was the Squarp Pyramid, where it was reported that others have reported issues. I now have a din connection set up there. In that case it really doesn't matter, since I realized (duh) that the pyramid can only send on one port/channel at a time.
But then I encountered the same symptoms with the ndlr. absolutely no luck at first I already understand and have used the basic routing tips that you have above, which is why this has been so puzzling. First (and why does the quick start say that you have to choose virtual usb port 1?) . What you describe is EXACTLY what i was doing. Holding down the left input button for the host part, and choosing the virtual port 1, then holding the right pc button. NOTHING. The port did not stay lit.
I can't remember now, so I suppose that I actually didn't do the 'second half' at first, but that wouldn't explain why the output light for the pc port would not stay lit.
After trying this out for quite some time, I noticed that it was staying lit, and all of the rest of it worked.
I should not have to select a din output port if I'm not using it, as my test didn't require it, and could easily yield a false positive, as at first (as has always been the case with the din outputs) it was simple to set up the host port input out through the din port. No problems there.