Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Jack: data not valid" when NetJack1 using higher channels count (MTU bound?) #93

Open
lapsio opened this issue Mar 31, 2020 · 0 comments

Comments

@lapsio
Copy link

lapsio commented Mar 31, 2020

Hi

I'm using Scarlett 18i20 which (as name suggests) is 18/20 channels ADAT interface. Unfortunately I can't seem to successfully connect it over network using more than 6/6 channels. When I bump MTU to 9000 (max jumbo supported by my physical network) and use -m 9000 flag I can reach 8/8 channels. If I use virtualized network (with no real MTU limit) I can reach 10/10 channels with 18k jumbo (which is realistically not supported by real world hardware). It's quite weird limitation.

As result It's quite problematic to use this interface via netjack. Even though I have actually 10G network backbone which should be easily able to pull off such scenario.

I tried increasing -n and even adding -R and -D but nothing helped. My JACK package is crashing with segmentation fault when I try to use CELT compression but honestly I wouldn't accept this as solution anyways so I guess it doesn't really matter.

@lapsio lapsio changed the title "Jack: data not valid" when using higher channels count (MTU bound?) "Jack: data not valid" when NetJack1 using higher channels count (MTU bound?) Mar 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant