DSDPLUS dont display correct data in DMR

Status
Not open for further replies.

Forts

Mentor
Database Admin
Joined
Dec 19, 2002
Messages
6,951
Location
Ontario, Canada
You will likely need to post a recording for them to investigate this. Hit R when DSDPlus is running and capture some voice activity, then upload it for analysis.
 

KevinC

The big K
Super Moderator
Joined
Jan 7, 2001
Messages
12,944
Location
I'm everywhere Focker!
I seem to recall that would be correct. The subscriber will receive on TS 1 and transmit on TS 2 (or receive on 2 and transmit on 1)...but I could be wrong.
 

Forts

Mentor
Database Admin
Joined
Dec 19, 2002
Messages
6,951
Location
Ontario, Canada
No... there shouldn't be any crossing of timeslots. What's on 1 stays on 1 no matter what.
 

DSDPlus

Member
Joined
Jul 24, 2014
Messages
377
Incorrect. Recent Fast Lane builds do not display any slot number for simplex or repeater input traffic.

Edit: You even linked to a screen shot showing this...
 
Last edited:

racingfan360

Member
Joined
Dec 19, 2005
Messages
1,190
Incorrect. Recent Fast Lane builds do not display any slot number for simplex or repeater input traffic.

Edit: You even linked to a screen shot showing this...

Yes but the incorrect slot number still shows in the wav file information when per transmission recording is enabled. See post #10 of that thread. While displaying slot info has now been suppressed I assume the same underlying bug still exists in later builds. In comparison, DMRdecode decodes the slots correctly.
 

DSDPlus

Member
Joined
Jul 24, 2014
Messages
377
No, just tested the same DSD+ 1.092pt that all FL members have and it created a file with the exact name 034253_008_DMR__DCC1_GC_302260_35001.wav
 

racingfan360

Member
Joined
Dec 19, 2005
Messages
1,190
No, just tested the same DSD+ 1.092pt that all FL members have and it created a file with the exact name 034253_008_DMR__DCC1_GC_302260_35001.wav

Ok, my bad. The slot number does now not show in the per sample recording wav file for 1.092pt, as you say. I hadn't seen any mention of that in the release notes. Thanks for the fix.

It looks like the problem was present in each of the earlier releases up to and including 1.090 - that would explain why ronenp was seeing the issue he describes.

Thanks again for all the continued development of DSDPlus.
 
Status
Not open for further replies.
Top