What files are in the broadcastify_calls directory?its scrolling the control channel and it shows recording still
What files are in the broadcastify_calls directory?its scrolling the control channel and it shows recording still
I’ve shut down. I’ll try to look tomorrow. Gotta work s little to support the fun. I did notice that it recorded for 30-45 seconds but the file on the site showed 2 seconds.What files are in the broadcastify_calls directory?
No worries. It’s working excellent except for combining calls. Which unless you’re looking at the screen you’re never going to notice. I did because I know some unit numbers that should be on a dispatch channel so I noticed it.What files are in the broadcastify_calls directory?
edit: I'm looking at your node. I don't see any long duration calls. It looks like it is working. I'll try to get a test up for P2 here tomorrow. It is probably going to take me a few days to get this figured out. The WA DOT system (P2) isn't very active unless there is snow.
Was just listening to your node. It does seem like there is an issue. The reported duration isn't matching actual duration in the wav file. I'll see what I can find.I’ve shut down. I’ll try to look tomorrow. Gotta work s little to support the fun. I did notice that it recorded for 30-45 seconds but the file on the site showed 2 seconds.
I have noticed that it follows perfect. Then it goes out and does what I’m reporting. Then corrects and tracks correctly again. I can save some logs tomorrow but it will be a huge amount of data that needs to be compared to the audio. A huge task. I don’t think it’ll be beneficialWas just listening to your node. It does seem like there is an issue. The reported duration isn't matching actual duration in the wav file. I'll see what I can find.
edit: Now it seems correct. Strange. I'll keep an eye on it.
Will do first thing tomorrow. Eastern time. Have a great night@epersson,
When you get back to it, please try 2022-07-14_1859 (untested). This version should detect if the TG ID changes during a call. This should terminate the current recording/call and cause it to move on to the new one. Let me know what you find.
Initial watching looks like it is working great, I haven't seen or heard any anomalies. It appears that its jumping between TGIDs like it's supposed to. I would give this one Two thumbs upWill do first thing tomorrow. Eastern time. Have a great night

@btt Strange but probably not so, but I found the link. if I shut scrolling off it holds the last displayed TGID for all TX. if I restart scrolling it works normally. But the scrolling caused lockups so I shut it off normally I can now repeat the issue with regularity.
It ran for about a week then locked up with scrolling enabled, then ran for 4 months with it shut off. So I shut it off.
Ok I'll try. I'm here for a week I'll let it run for the week. Ya, I asked back a while ago if it was required... I figured the data stream would be used.ThanksThat does make sense. The P25RX version of the software does parse the console stream, so you have to leave that enabled. Please try version 2022-07-15_0802. I made some changes that I believe may fix the issue that can cause the java software to become unresponsive over time.
I don't remember the question. Sorry if I answered that incorrectly. The latest versions of the software (scanning versions) don't parse the console output. Once I get the P25RX model firmware conversion to scanning done, then it will not require the console output.Ok I'll try. I'm here for a week I'll let it run for the week. Ya, I asked back a while ago if it was required... I figured the data stream would be used.Thanks
Not the end of the world, unless you are watching the screen for TGID you would never notice, and the only reason I am is to watch while testing.. just making it more great... I may shut it off when i leave no matter what just to feel more confident. but for next week I am here and can babysit it.I don't remember the question. Sorry if I answered that incorrectly. The latest versions of the software (scanning versions) don't parse the console output. Once I get the P25RX model firmware conversion to scanning done, then it will not require the console output.
Yes, you can feed as many receivers as you like into a single instance of BTT BCalls populating a single system. This has been tested. You want to configure them so that there aren't overlapping talk groups. (unique talk groups per receiver), then enable the "enable broadcastify calls output".@btt OK, sorry another question. Can the BTCalls handle the multitasking required to send what could amount to simultaneous calls from two BTConfig instances? Can I send calls from both P25rx systems without losing any calls.
OK, great, I have 1 duplicate TG as its the local pompano fire, its in both as others listen to both, I saw a dup call in the logs, so it's parsing them... In that case the stress test will steam full blast ahead... thanksYes, you can feed as many receivers as you like into a single instance of BTT BCalls populating a single system. This has been tested. You want to configure them so that there aren't overlapping talk groups. (unique talk groups per receiver), then enable the "enable broadcastify calls output".
You may want to look at 'background app refresh' in your iPhone settings to see if that helps.At least on my iPhone. If the phone locks or you move off the web browser to another app the audio halts as it appears the incremental stepping stops. If I go back to the web page stop and start it starts again.
There isn’t a setting for Safari but I’ll turn it on and see what happensYou may want to look at 'background app refresh' in your iPhone settings to see if that helps.