More > JRiver Media Center 20 for Linux

JRiver Media Center 20.0.129 for Debian (Wheezy) ARM

<< < (8/20) > >>

Mark_NL:

--- Quote from: mwillems on May 27, 2015, 10:02:54 am ---Are you seeing issues with Redbook files?  If so, then VLC is a good point of comparison.  For high res, however VLC generally just outputs to the system default output (usually pulse) which resamples everything to the system sample rate (typically 48KHz), so it's not really a good point of comparison for hi res files.  You may be playing a 192KHz file, but with VLC the system is quietly downsampling it to 48K before it ever hits the USB bus.  

--- End quote ---

Minnor issues with redbook but not flawless. Just payed 24/96 with VLC:

--- Code: ---DIYINHK DIYINHK USB Audio 2.0 at usb-bcm2708_usb-1.4, high speed : USB Audio

Playback:
  Status: Running
    Interface = 1
    Altset = 1
    Packet Size = 127
    Momentary freq = 96013 Hz (0xc.0068)
    Feedback Format = 16.16
  Interface 1
    Altset 1
    Format: S32_LE
    Channels: 2
    Endpoint: 1 OUT (ASYNC)
    Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000
    Data packet interval: 125 us

--- End code ---
BTW: I think "Feedback Format = 16.16" and "Data packet interval: 125 us" are indicators for dealing with a UAC 2 device, can you confirm??


--- Quote ---Let's get back to basics, have you tried choosing different ALSA outputs for your DAC in JRiver?  Specifically have you tried the hardware outputs (the ones with names starting with "front:")?  
--- End quote ---

The hardware output "Front:CARD=D20 DEV=0  [ALSA]" works best thus this is the one i use.


--- Quote ---Just for testing, have you tried using the system default in JRiver?  Does that work the same as VLC, or does that not work either?  That's not a desirable long-term solution, but will tell us something if it works.

--- End quote ---

In JRiver Sysdefault:CARD=D20 only plays material in the 48 kHz family Correction does not play 44,1 kHz and above 48 play's downsampled to 48 kHz. DSP seems to set this on the fly.
VLC samples verything to 48 kHz playing to ....USB.. DEFAULT AUDIO", playing 44.1 kHz:


--- Code: ---pi@raspberrypi ~ $ cat /proc/asound/card0/stream0
DIYINHK DIYINHK USB Audio 2.0 at usb-bcm2708_usb-1.4, high speed : USB Audio

Playback:
  Status: Running
    Interface = 1
    Altset = 1
    Packet Size = 67
    Momentary freq = 48007 Hz (0x6.0038)
    Feedback Format = 16.16

--- End code ---



--- Quote ---Do you have other USB peripherals plugged in?  Have you tried moving all peripherals to a powered USB hub?
--- End quote ---

Only the dac is plugged in. The USB receiver is partly powered by USB, the DAC it self (and some parts of the USB receiver) has  separate power supplies.

Chanh:
Bob,

I have repeated issue with "trail period expired" windows pops up, again. This had happened before and after many unsuccessfully restore, I made fresh installation.  It was working for few days, now the same registration issue appears. I only have three more restore left...!
How can I rectify this?
Many thanks.

JimH:
Bob has been on vacation.  He's returning tomorrow your time.  l've cleared your restores, so don't worry about using them.

Chanh:

--- Quote from: JimH on May 28, 2015, 06:36:42 am ---Bob has been on vacation.  He's returning tomorrow your time.  l've cleared your restores, so don't worry about using them.

--- End quote ---
Many thanks Jim. Really appreciate your supports! I wonder if I was single out from this weird "trail period expired" or there is a bug within 110-build? I upgraded from 20.0.91 to 20.0.110.
Btw, I use Banana Pro as all in one server with Built-in wifi as AP. JRiver is playing to my BeagleBone Black under UPnP protocol for I2S direct to my DAC via Miero Botic driver.

mwillems:

--- Quote from: Chanh on May 28, 2015, 08:40:50 am ---Many thanks Jim. Really appreciate your supports! I wonder if I was single out from this weird "trail period expired" or there is a bug within 110-build? I upgraded from 20.0.91 to 20.0.110.

--- End quote ---

I have several Pi's running 20.0.110 with no license issues, and so do several other folks, so it's not a general issue. 

Given that your license seems to "take" but is then "forgotten" it sounds a lot like a filesystem permissions issue.  If you need to restore the license whenever you reboot, it's definitely a permissions issue.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version