-
Notifications
You must be signed in to change notification settings - Fork 14
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
Supporting DVSI chips / legal aspects #12
Comments
I suspect that using it is legal insofar as you're not using it to develop a commercial product that uses the AMBE Vocoder. However, supporting the hardware that exists to process it is a wise decision. |
This is the permutation needed to convert a 49-bit AMBE frame in DN-mode to something the DVSI chip can understand: 0 3 6 9 12 15 18 21 24 27 30 33 36 39 41 43 45 47 |
Is there a similar permutation for the 88 bit IMBE frame in VW-mode? The DVSI chip does not directly understand either the 88 bit sequence that mbelib decodes. I am using the AMBE3000 chip in 4400 bps rate with no FEC |
Hello. To the best of my knowledge, you cannot use the AMBE-3000 for VW mode. This is because they are using a rate that is simply not supported by the chip, see also issue #13. I think your best chance is to do it in software. Note that the osmocom op25 project has an IMBE de- and encoder which would probably work for this. If your goal is to just apply FEC and retransmit the packet (e.g. in a repeater), you can simply do that without the need of the DVSI chip at all. Does that answer your questions? |
Hello. Thanks for the information and mentioning the op25 project (useful when I will work on the encoding part). I'll stick with the software version and mention it as a limitation. So yes this answer the question thanks! |
It is not quite clear under what circumstances and in what parts of the world it is OK to use mbelib. Maybe there is need to support the actual DVSI products instead of using mbelib...
This probably involves legal insights from people who are not me. Preferably insights that are not restricted to the US, if possible.
The text was updated successfully, but these errors were encountered: