Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Patatorz]

Hello I use JRiver v19.0.144 to manage my library (mainly AIFF files) on a NAS and to stream to a network player (Ayon NW-T or Lumin). I can use my PC, JRemote or the Ayon NW-T interface to launch the music.
I have a DLNA profile created on the basis of the "24bit DAC". If I select "original mode" in audio (and not transcoding) I'm not able too launch the music from the PC and JRemote : I have a "file format error" on the Ayon screen.
If i launch the same mucic from the ayon interface choosing the same DLNA server on my PC, I can play the music !
If I change the DLNA settings and move the mode from original to transcoding (24 bits PCM for example) : I can launch the music from my JRiver on the PC or JRemote.

Everything is working fine with FLAC files. Only this problem with AIFF when I try to launch the music in original format from JRiver PC or JRemote.

If you have any clue to fix this problem, you are more than welcome !!! (don't tell me to put everything in FLAC !)

Best regards

[AndrewFG]

I would just set MC to convert to PCM and forget about it...

I say this because an AIFF is anyway a PCM file, so the "conversion" is very trivial and just involves stripping the first 40..50 bytes containing the AIFF headers; all the remaining bytes are anyway passed to the player unchanged.

[Patatorz]

I would agree. But it is a kind of bug somewhere no ? How to make JRiver take it into account ?

[AndrewFG]

I would agree. But it is a kind of bug somewhere no ? How to make JRiver take it into account ?

The following is just an idea, with no guarantee, but please let us know if you succeed.

In the MC folder look for a file called FileAssociations.xml and open it with a text editor. In it you will see an entry for aiff files that looks like audio/aiff or audio/x-aiff. If it has the x- prefix then try deleting the prefix, and if it does not have the x- prefix try adding it. Keep a safe copy of FileAssociation.xml in case you screw things up...

[Patatorz]

I confirm that it works with transcoding but....it should with the "original" as it works when I can access the Dlna server from my ayon !

[AndrewFG]

I confirm that it works with transcoding but....it should with the "original" as it works when I can access the Dlna server from my ayon !

Did you try editing the file associations xml file as I suggested?

[AndrewFG]

^

Hmm. I looked in FileAssociations.xml myself just now. As you can see below, it already has both the x- form and the non x- form mime-type in its  database. So my idea will not solve your problem.

Code: [Select]

<MimeAssociations>
  <Audio>
    ..
    <Item Name="aif">audio/aif</Item>
    ..
    <Item Name="aiff">audio/aiff;audio/x-aiff</Item>

PS In case you are interested. The reason why I had originally made this suggestion was, (based on a similar experience with another file type), that there seem to be some renderers which can download music tracks where the ContentType = audio/x-something (the x- form), but which fail to download if the ContentType = audio/something (the regular form). And furthermore, there seem to be some players where the x-form works on push and not on pull, and vice-versa. So I suspected that perhaps your renderer is one of those that behaves this way for audio/aiff resp. audio/x-aiff ..

[stevemac]

Not sure if this is related or will help

When pushing to a renderer MC will use the first defined DLNA server (& therefore its settings) unless you associate the DLNA server with the renderer.  To associate, in the playing now section, right click on the DLNA zone and select Associate with DLNA Server & then select the DLNA Server.  If you only have one server defined MC will indicate this with Only one server, used by default

regards,

Steve

[AndrewFG]

Not sure if this is related or will help
When pushing to a renderer MC will use the first defined DLNA server (& therefore its settings)

Probably not    -- the possible solution that I was hypothesizing about, is to do with the overall global behavior of MC in total; so it would not be specific to the individual settings of any one server...