6.1.4 Not ingesting at all - Windows - SDRTrunk

[noamlivne]

Hi @chuot,
I installed 6.1.4 now, imported the Config from 6.1.3, but nothing seems to be ingested.
As if the program is not going to the Dirwatch.
Strange.
AFAIK I did not do any change.
Windows10, SDRTrunk.
Thank you very much in advance.

[chuot]

Indeed, I just discovered a bug in the meta data parser. Working on a fix.

[chuot]

Two things to check:

1. Is your monitored folder exists prior to start Rdio Scanner?
2. Is you dirwatch definition is disabled? I wasn't checking this prior to v6.1.4. So if it is disabled, it will be ignored as of v6.1.4.

[noamlivne]

1. My monitored folder did exist prior to start Rdio-Scanner.
2. It is not disabled. I used the Config from 6.1.3 that did ingest well. And just to make sure, I also started now 6.1.4 from scratch. In both cases the dirwatch is not disabled, and in both cases there was no ingestion.

[chuot]

v6.1.5 is just out, please give it a try and let me know. Thanks

[chuot]

While debug4 is running, if you just manually copy a new MP3 file from SDRTrunk to the monitored folder, does it get ingested?

[noamlivne]

Nope. Not manually copying nor "live" helps. No ingestion.

[noamlivne]

I will have to disconnect now. Feel free to send me more (debug) versions to test. I hope I will get to it tomorrow.
If you want, you can start from 6.1.3 and step-by-step introduce the changes you made since then, to try and pin point the issue.
Thank you very much for your efforts.

[chuot]

Found it! You should be ok with v6.1.7.

[noamlivne]

WORKS! Thank you very much!
6.1.7 Started ingestion immediately.
Great work!
I did have two issues, but they are probably not related:

1. After 3 minutes of ingestion it stopped. I do not know why. (Maybe a glitch from SDRTrunk). I restarted the program and all was great again.
2. And, I swiped Tailscale and your Android app from my smartphone and got this error in the program:
   2022/01/27 19:02:25 client.conn.writemessage: write tcp 100.79.29.86:443->100.89.248.62:42762: wsasend: An existing connection was forcibly closed by the remote host.
   But besides those two one-time issues, till now, it seems to ingest excellent.

If I will encounter issues similar to those above again, or new ones, I will open a new thread.
Thank you again.