Well, I built the 2018-05-04 snapshot found here: https://sourceforge.net/p/minidlna/git/ci/799e6cf505ec470b2bf0ae4118143380aa16b837/ on my FreeBSD system and it does support my DSD files now but I still see that it is limited to only 65535 tracks with my Yamaha receivers DLNA clients. I plan to try a couple of other clients next to see if they see all of the tracks. Edit: Ok, it appears the the Yamaha AVR DLNA client is the one that is having problems with more than 65535 tracks. I used my Oppo...
Well, I built the 2018-05-04 snapshot found here: https://sourceforge.net/p/minidlna/git/ci/799e6cf505ec470b2bf0ae4118143380aa16b837/ on my FreeBSD system and it does support my DSD files now but I still see that it is limited to only 65535 tracks with my Yamaha receivers DLNA clients. I plan to try a couple of other clients next to see if they see all of the tracks.
Thanks, the thing I was missing was to click on the Git link where it allowed me to download the snapshot.
Can someone tell me how to download the latest source for minidlna that contains the DSD changes?
I just now followed the link that you provided above. So am I correct in believing that dsf file support is now included? That is super great if so! Edit: Since I am running FreeBSD I checked the latest FreeBSD port of minidlna which is at version 1.2.1 and it doesn't contain any of the .dff or .dsf file type changes. So what is the version of the current minidlna?
I just now followed the link that you provided above. So am I correct in believing that dsf file support is now included? That is super great if so!
Hmm, well another issue that I have is that I need to be able to stream DSD (filetype .dsf) files. Does the latest version of minidlna support them? I've been running a patched version 1.1.4 for several years now, waiting for DSD support to offidially be added. Has that occurred?
Once again I am over 65,535 in track count. Here is what I get in my log file when over: sql.c:117: warn: sql_get_int_field: step failed: SQL logic error SELECT count() from OBJECTS where PARENTID = '0'; I'm not sure if that is connected/related to anything, but it does seem like it shouldn't occur. Oh, and why does this brain-dead GUI editor switch to italics whenever I type an astrisk? There should be an astrisk between the two parentheses but I couldn't type one there without having the rest of...