D
DaveNF2G
Guest
Has anyone tried ARC536?
Has anyone tried ARC536?
To follow up on my previous, I just poked around in a raw recording header again. For trunked systems, frequencies are not captured in the header (unless in binary form and I haven't found them).
There is a field that I've played with (ICOP) which I finally just figured out is the "Copyright" field/column in Windows Explorer. Unfortunately, the field length is set to 16 which only allows you to view those 16 characters (a string of ****************). Changing the field length in the raw header data doesn't help much because, like most of the fields, the data the follows contains lots of nulls which truncated the data in many viewers.
This field (to me) has always looked like some type of "scratch pad" but probably has other purposes. The field changes alot depending upon what (system type, etc.) created the recording.
Also - I now recall that like the talkgroup names vs. values, the unit ID seems to be an either/or as well. In the display below, I ended up adding an external "lookup table" to map the units.
....it seems like Uniden leaves in place what was in that field for the previous recording and just writes a null character (ASCII 255) at the end of the currently-being-written string....
If you ever figure out where they store the data that is displayed on a DMR conventional channel when the channel name is blank/default (on an x36HP), let us know. It has to be somewhere in the file, because I moved (copied & deleted) all the files from my scanner to the computer, then copied a couple of DMR files back to the scanner, and the items still displayed on playback on the scanner - but I can't locate them in the file at all.
The data I was talking about in our PM is what shows up at 031B (the beginning of the word "Net") in your hex dump, and continues to, I presume, the '0' at 0347 (the '0' before '.1'). I hadn't been able to find that data in headers before, but I haven't been looking using a hex editor; I was just opening them in Notepad++ and looking for ASCII strings.
If that consistently appears at that position in the file, and someone writes a decoder that will display that on a computer as it 'reads' the files, that would be a big deal.![]()
BTW - I've asked on more than one occasion if Uniden could provide the details on recording header formats to no avail. Apparently, it is a state secret so I hope the Uniden police don't show up at my house now....Oh, well. Without the documentation, I guess it is a fun thing to play with from time to time.
Edited...
Nope - incomplete.
This only seems to provide the "easy to figure out" section... We're talking about the data structures in the "data" section of/after ICOP.
Does Uniden really need to specify the "data structure"? There are a lot of references on that. After ICOP is the fmt subchunk which describes the audio such as samples per sec., number of channels, bits per sample, etc. The data structure is plain ole PCM audio.
If the branch of this thread about decoding data structures is going to continue, might I suggest breaking it off into a new thread where it would not be so far from the original topic?
This is not a complaint. The discussion is fascinating, but goes far beyond the OP's question about labeling recordings. I am making the suggestion here rather than using the Report function because I think the participants should ask for a fork if they plan to continue. If the discussion is finished, or already restarted elsewhere, then there is no real need to mess with this thread.
However that player doesn't display the data after ICOP starting with "unid" that troymail pointed out. It would be nice to know the format so any of us hobbiest can whip something up.