DSD 1.3 and mbelib 1.2 released

Status
Not open for further replies.

tripleplay905

Member
Joined
Jan 5, 2006
Messages
86
Location
Summit Co, Ohio
How about VMWare? That might be a way to work DSD on Windows. Just a thought.

I've used DSD in a VM on a windows host; I was getting very bad decoding from DSD. I was using Backtrack 4 as the guest though, so not sure if that had anything to do with it. Never tried with a clean install of Ubuntu 10.04 as guest. Although I'm get almost perfect decoding when booting directly to Ubuntu 10.04. Possibly the transition of audio to/from guest/host?
 

KC1UA

Scan New England Janitor/Maintenance
Database Admin
Joined
Oct 27, 2002
Messages
2,148
Location
Marstons Mills, Cape Cod, Massachusetts
What might be helpful as a reference is a compilation of what hardware is working for people. I see numerous people stating they are getting near-perfect decoding, which is fantastic. Many of us are not however. Such a list should include:

Scanner or Receiver being used for source of discriminator audio
Whether discriminator tap has resistors, capacitors, etc in line or if the tap goes directly to the sound card.
Line in or mic in on the sound card.
Type of sound card for input.
Type of sound card for output.
Which Linux OS is being used.
Basic specs of computer being used (processor, RAM)
Type of signal being successfully decoded. (P25 conventional, trunked, ProVoice, MotoTRBO, etc.)

Just a thought. I've used numerous combinations of hardware without success thus far to include discriminator taps from an AOR AR5000A+3 (which I assume is too weak to be useful), an Icom IC-PCR1000, and a "self-tapped" Uniden BC246T. For sound I've used the 99 cent specials, numerous on-board (AC97 type) devices, a Soundblaster Live! 24 bit USB device, and another generic eBay special USB sound device, all to no avail other than a rare blurb of intelligible audio. I think it would be helpful to compile a list of stuff that does work in one easy-to-find location. I have no intention of giving up on this at all, it's fascinating, fun to play with, and I know I'll eventually find the right combo of hardware.

EDIT: I took the liberty of adding a section to the DSD Wiki page to facilitate listing of successful equipment setups.
 
Last edited:

mrscanner2008

Member
Premium Subscriber
Joined
Jun 21, 2008
Messages
333
Location
Canada
I have great succes with dsd, this is what I use:

Pro-2067 direct tap (no resistor or capacitor)
direct to line in
computer: Dell GX520 with inboard sound card.(Analog Devices ADI 198x Integrated Audio)
onboard sound card for input and output
Linux Ubuntu 10.4
success decoding: mototrbo and provoice

Mrscanner2008
 

gariac

Member
Joined
Feb 1, 2004
Messages
252
Are you using this card for input, output, or both? I just found one on eBay for $19.99 and ordered it for the hell of it.
.

One card will do input and output, at least on P25. That is the only digital I have locally. The ProVoice testing was done by feeding what I suppose were wave files to the decoder.

For the longest time, Diamond had a $10 rebate on these cards, I got 3 that way, just buying them at Fry's. It's a great card if you want to run multiple cards in one system. I suggest using the KDE mixer. I see have 3 running now, and have run 4 doing acarsd. The 8 bit mode is really critical if you want to run multiple cards since it keeps the bandwidth low.

I'm using opensuse 11.2. I never really understood all these people flocking to Ubuntu. Seems to me like a lot of work when opensuse and fedora are well established distributions with a paying user base (Novel Suse or Red Hat) to force bugs to get fixed. Ubuntu just has some wealthy South African paying the freight. Almost any time you have the choice, I always go business grade, or at least insure the vendor has a business grade product.
 

mancow

Member
Database Admin
Joined
Feb 19, 2003
Messages
6,908
Location
N.E. Kansas
that doesn't make sense to me. You say you have no luck with decoded speech then you say it decodes perfectly. What's the issue?


i got a pro-163
disc tap no resistior
ac97 onboard sound card
ubuntu 10.04
no success with decoded speech it pops, cracks and it decodes perfect
 

MattSR

Member
Joined
Jul 26, 2002
Messages
407
Location
Sydney, Australia
If its decoding perfectly (ie showing a high percentage) but theres no audio, then the issue is probably somewhere in the audio output stages..
 

KC1UA

Scan New England Janitor/Maintenance
Database Admin
Joined
Oct 27, 2002
Messages
2,148
Location
Marstons Mills, Cape Cod, Massachusetts
If its decoding perfectly (ie showing a high percentage) but theres no audio, then the issue is probably somewhere in the audio output stages..

I guess I'm a bit confused by this statement. It was my impression that the shown percentage is audio input level, which should be in the 40% range according to what I've read. Am I mistaken?
 

KC1UA

Scan New England Janitor/Maintenance
Database Admin
Joined
Oct 27, 2002
Messages
2,148
Location
Marstons Mills, Cape Cod, Massachusetts
3% and decode correctly. 40% is more stable.

When you say "decode" are you referring to screen display, or audio recovery? It was my understanding for audio recovery the input percentage should be in the vicinity of 40%, that a higher percentage may result in clipping, and a lower percentage may result in nothing. :)

I realize that experimentation is key and that no two setups are likely to work the same. I've been all over the place with the input percentage and I'm just not quite getting audio recovery. Close...but no cigar. I'm also back to using just one sound device (onboard AC97) for both input and output. This seems to be providing the best results yet.
 

G225

Member
Joined
Mar 1, 2009
Messages
28
Audio recovery is correct has 3% but the sound il not equal.

Sorry for my anglish, my first language is french.
 

offsite

Member
Premium Subscriber
Joined
May 3, 2003
Messages
169
Location
DM12JQ
A guy in our area who seems to be getting good results reports the following in an email:

/Quote/
Audio 'goodness' is related to having minimal error bars, not high percent input level indications.

Here is a comm segment that was perfectly audible. There is some initial settling, but once the quiescent level of 3% is reached, the error bars disappear and the audio is crystal clear.

Note: this is from a strong nearby system.

35%..e:=RRR=RR
25%..e:===
8%....e:
4%....e:=
3%....e:
3%....e:
3%....e:
3%....e:
3%....e:
3%....e:
3%....e:
3%....e:
3%....e:=========R========R==R=============

In my system, if the input signal gain is increased to cause readings much beyond 20%, major error bars start appearing that are filled with Rs, and the audio becomes unintelligible or absent altogether.

Again, the above sequence is from a strong, nearby system. For weak, distant systems the best decode and audio out still are obtained at 3% levels, but the error bars are considerablly longer and audio can be really ragged most of the time.

Decoding success also seems to depend on quality of the discriminator output. Also, inserting a series 100 k resister and 10 uF cap ahead of the audio adapter seems to stop signal sag and greatly improve decoding, Presumably, a buffer amp would be even better, but perhaps not worth the additional complexity.
/EndQuote/

So, from these comments, it looks like the lower the % level, the better, and that unloading the receiver's discriminator output is a good thing.

-rb-
 
Status
Not open for further replies.
Top