error calculator. After increasing the gain for symbol timing, this
new symbol evaluator class seems to track the signal very accurately
despite lots of noise and ISI.
timing error calculation with symbol decision. In the process of
changing over to this new class and remove the previous implementations
for the 3 values. This commit includes the partial implementation
so I can access from another dev machine.
based on the P25 LSM decoder using a costas loop and a gardner detector.
Updates the Demodulator Viewer FX application to add in a symbol chart
and a phase error chart. The decoder won't lock on yet ... still a wip.
ordering to each channel configuration to provide the user with greater
control over initial application startup configuration.
Adds new dialog window that displays on startup that allows the user to
invoke/cancel auto-start, or simply allow the timer to expire whereby
the channels will be auto-started.
Updates channel table model to include an auto-start column and relabels
the 'Enabled' column to read 'Playing'.
Updates channel editor to change the 'Enable/Disable' button to read
'Start/Stop'.
Changes the 'enabled' property of the channel configuration to indicate
the current 'processing' status - isProcessing().
Channel's XML configuration re-purposes the 'enabled' property to indicate
auto-start and adds a new (optional) auto-start 'order' attribute.
so that on startup, the application attempts to source the channel from
the preferred tuner.
If the tuner is currently not available, or if the tuner cannot source
the channel, then the next available tuner is selected.
Updates wave writer to add the metadata LIST and ID3 chunks to the end
of the recording so that the file contains the final/complete set of
metadata that was accumulated over the call lifecycle.
Updates Icecast TCP broadcaster to correctly handle content type:text/html
message that normally follows mount point in use error received from
broadcastify.
Changes mount point in use broadcast state to be a temporary error so that
the stream will attempt to reconnect after receiving this error.
Updates logging to include memory allocation/usage metrics with each
logging entry in order to support debugging issues related to high
memory usage situations. Updates initial application logging to better
identify the host system operating environment.
occured when the ChannelProcessionManager was allocating a new channel
causing the tuner to invoke the updateLOFrequency() method that was
trying to find a center tune frequency that would accommodate all of the
channels, specifically in the instance where the distance between the
highest channel and the middle channel was exactly one-half of the
tuner's bandwidth. This situation would cause the calculated adjustment
to be zero and would cause an infinite loop, locking all channels from
accessing the any channel startup/teardown events and causing running
channels to block with buffer overflows. Added 1 to the adjustment to
ensure that the initial adjustment placed the center overlapping channel
fully to the left of the center DC spike so that on the next iteration
that channel would no longer be overlapping.
state and replaces it with a processing chain heartbeat that is generated
by the sample source.
Previously, the state monitor was running on a separate thread and this
was causing multi-threading issues. With this update, all channel state
operations (and all module operations) occur on the source's buffer
processing thread.
Tweaked buffer size limits and buffer handling to attempt to avoid overflow situations in the first place.
Resolved an issue where the tuner processor was not deregistering correctly from the LIBUSB tuner processor during tuner shutdown.
detect encrypted audio state so that encrypted audio is not (incorrectly)
decoded and played back to the user.
Processes HDU and LDU2 messages to identify encrypted call state. Once
established, all subsequent LDU1/2 messages are decoded only if the call
is unencrypted. If an LDU1 message is received out-of-sequence, meaning
that the initial HDU message was missed, then the LDU1 is cached until
we receive an LDU2 message and correctly determine the call encryption
state.
