Hi all
I am trying hard to get my new ICOM 7100 going and altough I have a issues with my ISP / Connectivity for some reasons my radio developed an USB Disconnect while TXing on HF (suspecting RF into USB). Question is why it wasnt there for 2-3 days and suddenly all above 40W triggers COMx port disconnect. Funny thing is only VCP Port, not an audio interface…I might opt fot using an SERIAL pur CI-V interface I have somewhere.
Anyway, on the server I was playing with settings like - QtAudio - works initially but after a minute or two, TX audio just gets garbled / slowed down / seems like its trying to correct timing but fails. Only disconnect and connect to radio works.
When Setup using PortAudio - it seems to work slighlty better but only in combination of - PortAudio server and QtAudio on client.
RT Audio doesnt work on server as it doesnt advertise CODEC voice interface. It only works on client. Can someone explain differences in Qt,RT and PortAudio on Windows Enviroment?
Now question is - I am lucky to have a spare Raspberry PI4 with 4GB RAM on the table plus I also have on in my remote shack (RPi 4 - 2GB RAM). Both are connected to 1gbps ethernet btw.
Question is - shall I move the WFVIEW onto linux / raspberry or having a windows server is the way to go? I am not sure I am only one on Windows 11, but since I do have a UDP loss , sometimes the SERVER side wfview instance just crashes and end itself up - hence the raspberry question.
I am familliar with networking and port FWD and also understand the principles of the ICOMs USB audio interfaces, I just cant get thing to set up right and when it occasionally works, i get complains on my TX Audio. Thanks a lot and 73
Jiri
I have uploaded client side and server side LOGs with WAV to onedrive
and here is latest log from server side…interesting to see timestamps - same time multiple same messages?
https://termbin.com/60c8