Events Log in DSD plus where are the groups?

[kb5udf]

Hi all,

I'm revisiting toying with DSDplus (latest public release, NON-fastlane).
I've been monitoring one channel of a DMR system, trying to log talkgroups. After a few days,
DSDplus, while running, in the event log window/screen advises 9 groups have been logged.

If I quit the program and relaunch it, it still knows that it has logged 9 groups. Where do I find a list of these groups that have been so logged? My DSDPlus.event file contains only useless information that I can see; each time it is run, it simply logs the about 7-8 voice procotols that are to be decoded (p25 nxdn, etc).


Thanks,

JB

 

[mtindor]

Where do I find a list of these groups that have been so logged?

How about in a file called DSDPlus.groups ?

Mike

 

[kb5udf]

DSDPlus.groups not updating

Yep found that file, but has date of 2016. There is nothing being updated to it that I can see; last modified is 2016.

Yet, somehow DSDplus, knows about a number of groups. Is there some magic string/parameter I have to set on program launch?

 

[mtindor]

Yep found that file, but has date of 2016. There is nothing being updated to it that I can see; last modified is 2016.

Yet, somehow DSDplus, knows about a number of groups. Is there some magic string/parameter I have to set on program launch?

Make sure you are looking in the correct directory. Sounds like might have DSDPlus in multiple directories, running it out of one and looking in another. Or maybe you have DSDPlus installed in some directory that it isn't allowed to write to -- although I would think if that were the case it wouldn't start as it couldn't write a DSDPlus.bin either.

When DSDPlus is active, in the directory it is run from you should see various files that get updated during the course of running DSDPlus.

DSDPlus.bin (nothing you can do with this file -- DSDPlus uses for internal things)
DSDPlus.groups
DSDPlus.radios
DSDPlus.event
DSDPlus.wav (if you are saving decoded audio output)
DSDPlus.srt (if you are decoded audio output)

There is also DSDPlus.networks, DSDPLus.sites and DSDPlus.frequencies -- but you edit those manually, and if you never have then they may not exist.

Mike

 

[kb5udf]

No luck yet

It's a fresh windows install, and fresh installation of DSDplus. The groups, networks, radios and site files are all 2016, so not being updated, permissions look ok on them.

The DSDPlus.event file is updated, but only when the program is first run, so it just has this useless stuff:

2018/09/08 15:52:19 DSD+ 1.101pt [Public Release]
2018/09/08 15:52:19 D-STAR decoding enabled
2018/09/08 15:52:19 NXDN4800 decoding enabled
2018/09/08 15:52:19 NXDN9600 decoding enabled
2018/09/08 15:52:19 DMR/MotoTRBO decoding enabled
2018/09/08 15:52:19 P25 Phase 1 decoding enabled
2018/09/08 15:52:19 X2-TDMA decoding enabled
2018/09/08 15:52:19 ProVoice decoding enabled

 

[kb5udf]

may have found it

Stupid windows likes to default read only when copying directories. I bet this fixes it thanks. Now I just have to wait for some activity.

Thanks for the extremely rapid replies.

 

[mtindor]

Stupid windows likes to default read only when copying directories. I bet this fixes it thanks. Now I just have to wait for some activity.

Thanks for the extremely rapid replies.

You're welcome. You just caught me at the right time I guess. I'm fading away now, til evening

As for Windows, in newer versions of Windows, there are specific directory structures that you don't necessarily want to install DSDPlus in. I forget what they are. I typically just install in c:\dsdplus all the time and avoid anything crazy like c:\program files\dsdplus.

Hopefully whatever you have done fixes your problem.

Mike

 

[mtindor]

It's a fresh windows install, and fresh installation of DSDplus. The groups, networks, radios and site files are all 2016, so not being updated, permissions look ok on them.

The DSDPlus.event file is updated, but only when the program is first run, so it just has this useless stuff:

2018/09/08 15:52:19 DSD+ 1.101pt [Public Release]
2018/09/08 15:52:19 D-STAR decoding enabled
2018/09/08 15:52:19 NXDN4800 decoding enabled
2018/09/08 15:52:19 NXDN9600 decoding enabled
2018/09/08 15:52:19 DMR/MotoTRBO decoding enabled
2018/09/08 15:52:19 P25 Phase 1 decoding enabled
2018/09/08 15:52:19 X2-TDMA decoding enabled
2018/09/08 15:52:19 ProVoice decoding enabled

Ok, read-only shouldn't be an issue then, if it is writing the DSDPlus.event file.

Are you using FMP24 + DSDPlus? Or are you using SDR software or a discriminator tap (line input) ?

I use SDRSharp and Virtual Audio Cable and DSDPlus. My SDRSharp output goes out on VAC line 1, and my input for DSDPlus is VAC line 1 (audio input device 2) and my output for DSDPlus is audio output device 1 (my speakers).

So a real simple command line for me is just:

dsdplus -i2 -o1 -v4

- where -v4 just adds some verbosity

Mike

 

[kb5udf]

hmm command line

I have some overly complex command line generated by an a sdrsharp plugin. I'm using SDR# with airspy.

It could be this fancy command line that the plug in generated to screwing up the logging; this fancy command line has alot of parameters to initiate DSDplus

Thanks, I'll try your command line manually.

 

[slicerwizard]

If you're using that stupid SDR# DSD+ plugin, then your DSD+ data files are in the SDR# folder, because that's the folder that the stupid plugin runs DSD+ in. Never would've imagined that it was so hard for a developer to start a process in the correct folder...