Topic: JRiver Media Center 19.0.60 for Debian (Read 10113 times)

bob · « **on:** October 22, 2013, 05:42:27 pm »

http://files.jriver.com/mediacenter/channels/v19/latest/MediaCenter-19.0.60.deb

Purchase link

19.0.60 (10/22/2013)

1. Changed: Better ALSA device enumeration, should help to coexist with pulseaudio.

19.0.59 (10/21/2013)

1. Fixed: SSDP discovery stopped working after a short time.

19.0.57 (10/17/2013)

1. Changed: Prevent message boxes from popping up in /mediaserver mode.
2. Fixed: DLNA, problems with some http 1.1 devices.

19.0.56 (10/10/2013)

1. Changed: Attempt to back off requirements to SSE2.
2. NEW: If the default lucida font isn't found will fall back to a different font (requires the xfonts-100dpi package)

19.0.54 (10/08/2103)

1. NEW: Added support for 24-bit ALSA devices.
2. Fixed: When playback failed to start, it could lead to a crash.
3. Fixed: Mouse move tracking was not working, causing many UI issues.
4. Fixed: Typing in an edit control that showed suggestions could segfault.

19.0.53 (10/07/2013)

1. Fixed: Window minimize, maximize, and restore work.
2. NEW: Compiled without SSE support. Need Feedback.

19.0.52 (10/4/2013)

1: NEW: Fallback to S16_LE sound if the ALSA driver doesn't support S32_LE.
2: Fixed: Font spacing and switched to Lucinda.
3: Fixed: Added more package dependencies.

19.0.51 (10/3/2013)

1. NEW: First build.

RemyJ · « **Reply #1 on:** October 22, 2013, 06:45:45 pm »

Seems to be working well with pulse. Thanks.

Somewhere along the way Pause doesn't work anymore.

Matt · « **Reply #2 on:** October 22, 2013, 06:48:40 pm »

Quote from: RemyJ on October 22, 2013, 06:45:45 pm

Somewhere along the way Pause doesn't work anymore.

I don't think it has ever really worked right.

It's near the top of our list.

Mike Noe · « **Reply #3 on:** October 22, 2013, 07:17:07 pm »

Quote

1. Changed: Better ALSA device enumeration, should help to coexist with pulseaudio.

Not very user-friendly, compared to the other list options, though certainly more detailed. What I think might confuse people is....

Code: [Select]

mike@linux-30ty:~/bin/lib> aplay -L
null
    Discard all samples (playback) or generate zero samples (capture)
default
    Default ALSA Output (currently PulseAudio Sound Server)
sysdefault:CARD=SB
    HDA ATI SB, VT1708S Analog
    Default Audio Device
front:CARD=SB,DEV=0
    HDA ATI SB, VT1708S Analog
    Front speakers
surround40:CARD=SB,DEV=0
    HDA ATI SB, VT1708S Analog
    4.0 Surround output to Front and Rear speakers
surround41:CARD=SB,DEV=0
    HDA ATI SB, VT1708S Analog
    4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=SB,DEV=0
    HDA ATI SB, VT1708S Analog
    5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=SB,DEV=0
    HDA ATI SB, VT1708S Analog
    5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=SB,DEV=0
    HDA ATI SB, VT1708S Analog
    7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=SB,DEV=0
    HDA ATI SB, VT1708S Digital
    IEC958 (S/PDIF) Digital Audio Output
hdmi:CARD=Generic,DEV=0
    HD-Audio Generic, HDMI 0
    HDMI Audio Output

...shows the same device (CARD=SB,DEV=0) for the "formats" it supports. So, what would be the difference in selecting surround71:CARD=SB,DEV=0 vs. surround51:CARD=SB,DEV=0 from a device playback standpoint to MC?

Seems like distinct devices works better....

Code: [Select]

mike@linux-30ty:~/bin/lib> aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: SB [HDA ATI SB], device 0: VT1708S Analog [VT1708S Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: SB [HDA ATI SB], device 1: VT1708S Digital [VT1708S Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
  Subdevices: 0/1
  Subdevice #0: subdevice #0

Edit:
Also, I'm getting a hard crash when going to devices. Click options/audio/devices, ok or cancel out, then start playback, then go back into options/audio/devices *crash*
From the console...

Code: [Select]

pure virtual method called
terminate called without an active exception

bob · « **Reply #4 on:** October 22, 2013, 07:29:08 pm »

More recent ALSA docs say not to use the card enumeration method.
It prevents the use of pulse (if you have it) and userland audio drivers like bluetooth.
I'm thinking we need to open the devices in multichannel mode if that's what we want to use. Now I'm for sure not the expert here on that.

Thanks for the feedback, still feeling our way through this.

Mike Noe · « **Reply #5 on:** October 22, 2013, 08:02:39 pm »

Gotcha.

Quote

I'm thinking we need to open the devices in multichannel mode if that's what we want to use.

THere might be something to this. I've noticed that multi-channel PCM playback to my HDMI device (AMD HD6570) has messed up channel-mappings. Happens with speaker-test, VLC, mplayer and MC so far. BItstream passthrough seems to work in VLC and mplayer but not in MC. Haven't tested the analog device for multi-channel yet. However, I'm running a patched RC alsa/kernel that I built from git...so....it's hard to know at this point. I've been depending on speaker-test for verification and it does not seem to handle the 5.1 and 7.1 channel mappings.

Matt · « **Reply #6 on:** October 22, 2013, 08:09:51 pm »

Quote from: Mike Noe on October 22, 2013, 08:02:39 pm

THere might be something to this. I've noticed that multi-channel PCM playback to my HDMI device (AMD HD6570) has messed up channel-mappings. Happens with speaker-test, VLC, mplayer and MC so far. BItstream passthrough seems to work in VLC and mplayer but not in MC. Haven't tested the analog device for multi-channel yet. However, I'm running a patched RC alsa/kernel that I built from git...so....it's hard to know at this point. I've been depending on speaker-test for verification and it does not seem to handle the 5.1 and 7.1 channel mappings.

Channel mapping can be tricky on all platforms, because when you go from 5.1 to 7.1, the surrounds move from 5+6 to 7+8.

We fought through this just a couple years ago on Windows:
http://yabb.jriver.com/interact/index.php?topic=63724.0

tlcmd · « **Reply #7 on:** October 22, 2013, 10:34:07 pm »

Please keep working the install aborted here:
b773a000-b773c000 rw-p 00000000 00:00 0
b773c000-b773d000 r-xp 00000000 00:00 0 [vdso]
b773d000-b775c000 r-xp 00000000 08:02 274345 /lib/i386-linux-gnu/ld-2.17.so
b775c000-b775d000 r--p 0001f000 08:02 274345 /lib/i386-linux-gnu/ld-2.17.so
b775d000-b775e000 rw-p 00020000 08:02 274345 /lib/i386-linux-gnu/ld-2.17.so
bf92f000-bf950000 rw-p 00000000 00:00 0 [stack]
Aborted
dick@music ~ $

Thanks for all the work you are putting into this project!!
tlcmd (AKA Dick)

bob · « **Reply #8 on:** October 22, 2013, 10:58:47 pm »

Quote from: tlcmd on October 22, 2013, 10:34:07 pm

Please keep working the install aborted here:
b773a000-b773c000 rw-p 00000000 00:00 0
b773c000-b773d000 r-xp 00000000 00:00 0 [vdso]
b773d000-b775c000 r-xp 00000000 08:02 274345 /lib/i386-linux-gnu/ld-2.17.so
b775c000-b775d000 r--p 0001f000 08:02 274345 /lib/i386-linux-gnu/ld-2.17.so
b775d000-b775e000 rw-p 00020000 08:02 274345 /lib/i386-linux-gnu/ld-2.17.so
bf92f000-bf950000 rw-p 00000000 00:00 0 [stack]
Aborted
dick@music ~ $

Thanks for all the work you are putting into this project!!
tlcmd (AKA Dick)

Seems like there is something wrong with your machine. It works fine on the current version of 32 bit mint here.

tlcmd · « **Reply #9 on:** October 23, 2013, 04:28:15 am »

Bob,
I am not running plain Linux Mint, but 32 bit Linux Mint Debian Edition (mate), a rolling distro). And so far as I can tell, there's nothing wrong with my machine or OS, but if you think it will run on LMDE, I'm willing to re-install. I do have the option if I re-install to go with mate or cinnamon. Would you have a preference here. I personally prefer mate. I have an older machine ( 6 -7years old) with 2 Gig or RAM, a 320 Gig HDD, and a 2.66 MHz dual core Pentium chip.

I am running the latest updates for LMDE from the latest and current update package 7.

Note,
As I have just re-installed LMDE on Oct 1, I have the latest dvd for both and all my files are backed up to an ext HDD. Before I re-install, your thoughts on MC 19 and LMDE, please.

MC 19 is the primary reason I have not completely switched over to LMDE and am running Windows XP on a separate 160 Gig HDD.

FYI, I have an even older machine, some 12 years old running updated LMDE (mate) with a dual boot with Windows XP and it will not run MC 19 either.

I am downloading the latest LMDE updates to an old IBM Thinkpad which has only LMDE 32 Bit on it. I'll try MC 19 on it also.

tlcmd (aka Dick)

RemyJ · « **Reply #10 on:** October 23, 2013, 09:58:02 am »

Quote from: tlcmd on October 23, 2013, 04:28:15 am

Bob,
I am not running plain Linux Mint, but 32 bit Linux Mint Debian Edition (mate), a rolling distro).

I just did a clean install of "mate" 32 bit in a VM on a core i7 platform.
All I did after the install completed was...

apt-get update
apt-get install lame
dpkg -i Mediacenter-19.0.60.deb

and I had a working Media Center.

Maybe it IS a hardware or OS install issue.

bob · « **Reply #11 on:** October 23, 2013, 10:25:42 am »

I had results just like Remy except on older hardware (core 2 quad).

Now perhaps I'm not understanding Mint properly. I thought everything they have are rolling distros. The only difference between Mate, Cinnamon, whatever are they are different desktops and we don't care about the desktop.

From a prompt.
uname -a
cat /proc/cpuinfo
cat /proc/meminfo
cat /etc/issue

Also, how about a URL for the installer you used to create the machine in the first place?

Post the results. Thanks.

leezer3 · « **Reply #12 on:** October 23, 2013, 10:59:25 am »

From tlcmd's description of his machine, I get the nasty suspicion that it's actually likely to be a P4 with HT, not actually a dual core machine.
This leads me to wonder whether there's a stray bit of SSSE3 code somewhere that's slipped the net, so that things work on AMD64 boxes, but the older P4s don't like.

Having reinstalled this recently and with everything else working OK, IMHO probably rules out a OS misconfiguration (Unless you went and slimmed all and sundry off the default install?)

-Leezer-

tlcmd · « **Reply #13 on:** October 23, 2013, 11:26:16 am »

Baseball, Linux Mint has the current release Mint 15 which is NOT a rolling distro, and LMDE 201303. Here's the word on 201303:

Linux Mint Debian Edition (LMDE) is a semi-rolling distribution based on Debian Testing.
It’s available in both 32 and 64-bit as a live DVD with MATE or Cinnamon.
The purpose of LMDE is to look identical to the main edition and to provide the same functionality while using Debian as a base.

FAQ
1. Is LMDE compatible with Ubuntu-based Linux Mint editions?

No, it is not. LMDE is compatible with Debian, which isn’t compatible with Ubuntu.
2. Is LMDE fully compatible with Debian?

Yes, 100%. LMDE is compatible with repositories designed for Debian Testing.
3. What is a semi-rolling distribution?

Updates are constantly fed to Debian Testing, where users experience frequent regressions but also frequent bug fixes and improvements. LMDE receives “Update Packs” which are tested snapshots of Debian Testing. Users can experience a more stable system thanks to update packs, or switch their sources to follow Testing, or even Unstable, directly to get more frequent updates.
4. How does LMDE compare to the Ubuntu-based editions?

Pros:

You don’t need to ever re-install the system. New versions of software and updates are continuously brought to you.
It’s faster and more responsive than Ubuntu-based editions.

Cons:

LMDE requires a deeper knowledge and experience with Linux, dpkg and APT.
Debian is a less user-friendly/desktop-ready base than Ubuntu. Expect some rough edges.
No EFI, GPT or secureBoot support.

Additional notes:

About the installer: The live installer is developed from scratch with Debian in mind. It’s configurable and it can be re-used by other Debian-based distributions. We noticed a lack in live technologies and in live Debian installers, so we’re happy to take the lead on this. If you’re a developer and you’re interested in using it, have a look at its source repository and don’t hesitate to contact us so we can help you fork it and merge upcoming changes between our two projects.
About bugs: Please use this blog to report bugs.
Dedicated chat room: #linuxmint-debian is open to LMDE users on irc.spotchat.org.

Download links:

tlcmd · « **Reply #14 on:** October 23, 2013, 11:56:17 am »

Bob,
Prior to my re-install of LMDE (Mate), I did delete the entire hard drive so started with a blank totally unformatted partition on about Oct 1. Gave my swap 2.1 Gigs, My "/" 20 Gigs and made the rest of the 320 HDD my Home. "/" and "home" were formatted to ext 4.

The rest of my system runs very well and is fast. Since I'm not a gamer and use my computer primarily for music (connected to my stereo system), email, and surfing (research), this unit will do everyghing I want it to if I can get MC 19 installed and use Crossover Linux to install one other program (MovieOrganizer 2.8.6) which is a Windows only program.

My current hardware configuration is :

An Intel(R)
Pentium(R) D CPU 2.66GHZ
2.67GHZ 1.96 RAM

I was told that this was a Dual Core Processor.

Description: Mobile Intel(R) 4 Series Express Chipset Family
  HardwareID = iCNT0,PCI\VEN_8086&DEV_2A42
  Description: Mobile Intel(R) 4 Series Express Chipset Family
  HardwareID = iCNT1,PCI\VEN_8086&DEV_2A43
  Description: Intel(R) 4 Series Internal Chipset
  HardwareID = iEGL0,PCI\VEN_8086&DEV_2E02
  Description: Intel(R) 4 Series Internal Chipset
  HardwareID = iEGL1,PCI\VEN_8086&DEV_2E03
  Description: Intel(R) Q45/Q43 Express Chipset
  HardwareID = iEGL0,PCI\VEN_8086&DEV_2E12
  Description: Intel(R) Q45/Q43 Express Chipset

However, as I have mentioned previously, I'm only semi-computer literate, so really need help here. I do have a post graduate degree (MD), so I can figure out most things, but then, I only had 2 models with which to work in my business (male and female).
Thanks for any help. I did try the suggested terminal install and still got aborted when I hit the last step.
tlcmd (AKA Dick)

tlcmd · « **Reply #15 on:** October 23, 2013, 12:22:05 pm »

Baseball,
I used the site listed at the beginning to this topic from which I downloaded MJ 19 for Linux:
http://files.jriver.com/mediacenter/channels/v19/latest/MediaCenter-19.0.60.deb

I did use the deb installer in LMDE and it told me that MC19 was installed, but it was not listed on my programs and when I entered "mediacenter" into the terminal window, it ran only so far and aborted.

And to all y'all, I really appreciate the thought and attempts to help me get MC 19 installed into Linux Mint Debian Edition. LMDE is supposed to have all the advantages of both Mint and Debian in a rolling distro.

Please keep working with me and I'll do the best I can to get it up and running.

Thank you again.
tlcmd (AKA Dick)

tlcmd · « **Reply #16 on:** October 23, 2013, 12:27:53 pm »

Baseball,
Here's some more results from your latest post suggestions:

dick@music ~ $ sudo su
[sudo] password for dick:
music dick # uname -a
Linux music 3.10-2-486 #1 Debian 3.10.5-1 (2013-08-07) i686 GNU/Linux
music dick # cat /proc/cpuinfo
processor   : 0
vendor_id   : GenuineIntel
cpu family   : 15
model      : 4
model name   : Intel(R) Pentium(R) D CPU 2.66GHz
stepping   : 7
microcode   : 0x3
cpu MHz      : 2666.528
cache size   : 1024 KB
fdiv_bug   : no
f00f_bug   : no
coma_bug   : no
fpu      : yes
fpu_exception   : yes
cpuid level   : 5
wp      : yes
flags      : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pebs bts pni dtes64 monitor ds_cpl tm2 cid cx16 xtpr lahf_lm
bogomips   : 5333.05
clflush size   : 64
cache_alignment   : 128
address sizes   : 36 bits physical, 48 bits virtual
power management:

music dick # cat /proc/meminfo
MemTotal: 2039584 kB
MemFree: 1339400 kB
Buffers: 43672 kB
Cached: 412260 kB
SwapCached: 0 kB
Active: 390560 kB
Inactive: 275004 kB
Active(anon): 210236 kB
Inactive(anon): 33124 kB
Active(file): 180324 kB
Inactive(file): 241880 kB
Unevictable: 0 kB
Mlocked: 0 kB
HighTotal: 1152584 kB
HighFree: 521672 kB
LowTotal: 887000 kB
LowFree: 817728 kB
SwapTotal: 2047996 kB
SwapFree: 2047996 kB
Dirty: 404 kB
Writeback: 0 kB
AnonPages: 209636 kB
Mapped: 81452 kB
Shmem: 33736 kB
Slab: 20236 kB
SReclaimable: 10480 kB
SUnreclaim: 9756 kB
KernelStack: 2384 kB
PageTables: 3500 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 3067788 kB
Committed_AS: 1443604 kB
VmallocTotal: 122880 kB
VmallocUsed: 38648 kB
VmallocChunk: 83736 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 4096 kB
DirectMap4k: 16376 kB
DirectMap4M: 892928 kB
music dick # cat /etc/issue
LMDE MATE Edition \n \l
music dick #

This is somewhat like Sandskrit to me, but I'm sure you gurus know what it means. You ask the questions and tell me what to try and I'll give it a shot.

Thanks again,
tlcmd (aka Dick)

leezer3 · « **Reply #17 on:** October 23, 2013, 12:44:32 pm »

Yep, I thought it was probably a P4

Sadly, it's a single core Socket 478 beastie:
http://ark.intel.com/Products/Spec/SL8B3

The initial builds of MC19 for Linux required SSE3 & SSSE3, which were only introduced in the Core2 microarchitecture, and your chip doesn't support.
They attempted to back off this requirement to SSE2 in build 19.0.57, but it looks very much to me as though something has been missed

What that basically means is that each processor has a lot of functions implemented in it, a bit like your calculator, each of which allows it to do something faster or easier.
Older processors have 'less' of these functions implemented, and calling a 'missing' function from an application will cause errors like you've just seen.

-Leezer-

tlcmd · « **Reply #18 on:** October 23, 2013, 12:57:38 pm »

Leezer,
Thanks for the reply. Here come the questions:
1)Now, is there a fix or workaround?
2) Or will JRiver eventually come up with a MC19 that will run on this processor??
3) And will plain Linux Mint 15 (Olivia) rather than LMDE run MC 19 with my hardware configuration??
4) Does anyone know of another rolling distro on which MC 19 will run with my hardware configuration?

Thanks,
tlcmd (aka Dick)

bob · « **Reply #19 on:** October 23, 2013, 02:12:44 pm »

As Leezer noted, the CPU is not SS(S)E3 however that's supposed to not be necessary any more.
The build was checked carefully but I'll check it again.
I really don't think the rolling distro should make any difference.
We'll see if we can dig out a 478 p4 to check it on.

From the command prompt do this (and reply with the results)
dpkg -l | grep xfonts
dpkg -l | grep curl
dpkg -l | grep lame
dpkg -l | grep libx11

You can try deleting your .jriver directory (wipes the settings).
Go to a terminal prompt and do:
cd
rm -rf .jriver
then start mediacenter again.
mediacenter

tlcmd · « **Reply #20 on:** October 23, 2013, 04:03:19 pm »

Once again, thank you so much for working with me on this problem. Here is the results from the first set of commands. (I had to run an errand or would have replied earlier)>

dick@music ~ $ sudo su
[sudo] password for dick:
music dick # dpkg -l | grep xfonts
ii xfonts-base 1:1.0.3 all standard fonts for X
ii xfonts-encodings 1:1.0.4-1 all Encodings for X.Org fonts
ii xfonts-mathml 6 all Type1 Symbol font for MathML
ii xfonts-utils 1:7.7~1 i386 X Window System font utility programs
music dick # dpkg -l | grep curl
ii curl 7.32.0-1 i386 command line tool for transferring data with URL syntax
ii libcurl3:i386 7.32.0-1 i386 easy-to-use client-side URL transfer library (OpenSSL flavour)
ii libcurl3-gnutls:i386 7.32.0-1 i386 easy-to-use client-side URL transfer library (GnuTLS flavour)
ii libcurl3-nss:i386 7.32.0-1 i386 easy-to-use client-side URL transfer library (NSS flavour)
ii python-pycurl 7.19.0-7 i386 Python bindings to libcurl
music dick # dpkg -l | grep lame
ii lame 1:3.99.5-dmo2 i386 Open source MP3 encoder.
ii libmp3lame0:i386 1:3.99.5-dmo2 i386 Shared libraries for MP3 encoding.
ii libtwolame0 0.3.13-1 i386 MPEG Audio Layer 2 encoding library
music dick # dpkg -l | grep libx11
ii libx11-6:i386 2:1.6.1-1 i386 X11 client-side library
ii libx11-data 2:1.6.1-1 all X11 client-side library
ii libx11-dev:i386 2:1.6.1-1 i386 X11 client-side library (development headers)
ii libx11-xcb-dev 2:1.6.1-1 i386 Xlib/XCB interface library (development headers)
ii libx11-xcb1:i386 2:1.6.1-1 i386 Xlib/XCB interface library
music dick #

tlcmd · « **Reply #21 on:** October 23, 2013, 04:19:01 pm »

Here's the next set of commands and results:

I did get the message that
There was a problem loading the library 'Main Library'.
Please ensure that you have access to the library folders
/root/.jriver/Media Center 19/Library/

And the choices were to
retry
restore
clear the library 'Main Library' and start over

I did the latter and was told to "select a valid library to restore."
My only choice was jriver /Media Center 19/ Library Backups/

Now I am lost. My home folder contains a Music Folder with some 11000 music files in it.
Where do I go from here?

Thank you for your patience and help!!! It is much appreciated.

tlcmd (aka Dick)

bob · « **Reply #22 on:** October 23, 2013, 05:16:48 pm »

Quote from: tlcmd on October 23, 2013, 04:19:01 pm

Here's the next set of commands and results:

I did get the message that
There was a problem loading the library 'Main Library'.
Please ensure that you have access to the library folders
/root/.jriver/Media Center 19/Library/

You are running as root. Don't do that!
After installing (as root which is necessary to install a package).
Open a terminal, NOT a root terminal

Quote

And the choices were to
retry
restore
clear the library 'Main Library' and start over

I did the latter and was told to "select a valid library to restore."
My only choice was jriver /Media Center 19/ Library Backups/

Now I am lost. My home folder contains a Music Folder with some 11000 music files in it.
Where do I go from here?

Thank you for your patience and help!!! It is much appreciated.

tlcmd (aka Dick)

Once you have a terminal as your user (not root), run mediacenter.
You can do
Tools->Import->Import a single folder (or configure auto import)
Hit next and put in the path to your Music folder (mine is /home/bob/Music for example).
MC will create a new library.

BTW, I mentioned in the past that you must install the fixed fonts.
These are called
xfonts-75dpi and
xfonts-100dpi

tlcmd · « **Reply #23 on:** October 23, 2013, 07:13:18 pm »

Bob,
You are dealing with a real Linux dummy here.
1) I searched help, the forums, and my search engine and all of the answers to my question, "How to install fonts?" assume that I have a much greater Linux knowledge base than I do. I don't mind looking it up, but I'm not sure which question to ask?
2) I made it to having a terminal as my user (not root) and running mediacenter.
3) When I entered: Tools->Import->Import music (which is the folder where my music files are located, I was told that Music is a directory.
4) At that point I got lost again. My music folder is /home/dick/music

In summary, I seem to need to Know how to either configure auto import or which "file" to go to in the Tools->Import "whichever single folder I need in order to go to the next step" (Hit next and put in the path to your Music folder which is /home/dick/Music)

I'm sure this is a Mickey Mouse questiononce you know what you are doing, but right now it is completely beyond me.

Again, thank you for your patience and assistance. Being a physician, I've had to do my share of Keeping It Simple For Stupid in order to deal with someone who dissolved an oral diuretic tablet in water and soaked her feet in that solution instead of swallowing the tablet and letting her kidneys do the job. We are all guilty of assuming that people know more than we think they do when we give instructions which are simple to us, but not quite comprehensible to them.

Thank you for your continuing patience and assistance. I really want MC 19 to run properly on my computer.
tlcmd (aka Dick)

tlcmd · « **Reply #24 on:** October 23, 2013, 08:34:09 pm »

Bob,
I used the package manager and got the xfonts 75 and 100, then opened mediacenter via the terminal and got to the MC 19 screen, hit tools and then imported a single folder: /home/dick/Music (audio file types). Then the MC 19 screen vanished and left me with this in the terminal. Help, please?

tlcmd (AKA Dick)

Code: [Select]

dick@music ~ $ mediacenter
JRiver install path (process: 8281): /usr/lib/jriver/Media Center 19/
CJRSharedToolsHelper::AuthenticateJRSharedLib
JRFileSystem::GetDirectoryAppdataCommon
CJRSharedToolsHelper::AuthenticateJRSharedLib
JRFileSystem::GetDirectoryDocuments
JRFileSystem::GetDirectoryDesktop
JRTools checking thread
CJRSharedToolsHelper::AuthenticateJRSharedLib
CJRSharedToolsHelper::AuthenticateJRSharedLib
JROs -- analyze operating system
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JROs -- analyze operating system
Setting focus: 09E8B968
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
CJRSharedToolsHelper::AuthenticateJRSharedLib
JROs -- analyze operating system
JRFileSystem::GetDirectoryDocuments
JRFileSystem::GetDirectoryDocuments
GetDiskStatistics
JRFileSystem::GetDirectoryWindows
JRFileSystem::GetDirectoryProgramFiles
GetAvailableDrives
GlobalFunc: RunProgram
Setting focus: 09E3EDA0
Setting focus: 0A426798
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Setting focus: 0A427C90
Setting focus: 0A426798
Setting focus: 0A427C90
Setting focus: 09E3EDA0
JRFileSystem::GetDirectoryDocuments
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDirectoryDocuments
JRFileSystem::GetDirectoryDocuments
GetDiskStatistics
Setting focus: 0A4C4118
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Setting focus: 09E3EDA0
Setting focus: 0A3B4388
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Setting focus: 09E3EDA0
Setting focus: 09E886D0
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Setting focus: 09E3EDA0
Setting focus: 0A3B4388
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Setting focus: 09E3EDA0
Setting focus: 0A3B4370
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Setting focus: 09E3EDA0
Setting focus: 09E88908
JRFileSystem::GetDirectoryWindows
JRFileSystem::GetDirectoryProgramFiles
GetAvailableDrives
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Destroying font (32840 bytes)
Destroying font (32840 bytes)
JRBasicWnd::SetCapture
JRFileSystem::GetDirectorySystem
GetDiskStatistics
JRBasicWnd::SetCapture
Setting focus: 09E3EDA0
JRFileSystem::GetDirectorySystem
CJRSharedToolsHelper::AuthenticateJRSharedLib
*** Error in `mediacenter': double free or corruption (!prev): 0x09f4b808 ***
======= Backtrace: =========
Aborted
dick@music ~ $

bob · « **Reply #25 on:** October 24, 2013, 09:43:06 am »

Dick,
The last line indicated a crash.
I'll be checking the cpu stuff today.
Other possibilities could be a corrupt file in your import folder (you could try making a smaller one, say just one album to test)?
or perhaps your machine memory might be questionable? You could download a cd image from http://memtest86.com to test it out.
On the platforms I've tested on, MC's imported my entire music collection without trouble. This includes mp3, flac, m4a, ape, and wav files.

RemyJ · « **Reply #26 on:** October 24, 2013, 09:50:13 am »

Bob, I get those double free exceptions as well usually when pressing stop or closing the app.

Code: [Select]

*** Error in `mediacenter': double free or corruption (out): 0x48484e60 ***
======= Backtrace: =========
/lib/libc.so.6[0x42d46cf2]
/lib/libstdc++.so.6(_ZdlPv+0x20)[0x483e3160]
/lib/libstdc++.so.6(_ZNSs4_Rep10_M_destroyERKSaIcE+0x1c)[0x484496dc]
/lib/libstdc++.so.6[0x48449723]
/lib/libstdc++.so.6(_ZNSsD1Ev+0x30)[0x48449790]
/lib/libc.so.6(__cxa_finalize+0xba)[0x42d0310a]
/usr/lib/jriver/Media Center 19/Plugins/libout_Main.so(+0x2598f3)[0xeda908f3]
/lib/ld-linux.so.2[0x42cc248c]
/lib/ld-linux.so.2[0x42cc2ed1]
/lib/libdl.so.2[0x42e92dc2]
/lib/libdl.so.2(dlclose+0x28)[0x42e92df8]

bob · « **Reply #27 on:** October 24, 2013, 10:12:41 am »

Remy,
Are you playing a local file or over the network when that happens (crash on stop)?

RemyJ · « **Reply #28 on:** October 24, 2013, 10:50:31 am »

Quote from: bob on October 24, 2013, 10:12:41 am

Remy,
Are you playing a local file or over the network when that happens (crash on stop)?

All local files. Actually, I may not have checked before now on build 60 but I can't get into Options either. Same crash.

tlcmd · « **Reply #29 on:** October 24, 2013, 11:12:48 am »

Bob,
Great idea. I'll give it a try since i am well backed up with my music files on an external hard disk and report back. I'll delete those files from my internal HDD and add a cd with only .wav ones.

Thank you once more for your patience with this Linux semi-literate. At least I'm learning a bunch. I'll get back to you later. have a few "honeydo's" on the front burners.

Harmmmmmmoniously (I'm a barbershopper and we've district chorus and quartet competition in Myrtle beach this weekend so you'll be shed of me after this evening until late Sunday.)
tlcmd (aka Dick)

tlcmd · « **Reply #30 on:** October 24, 2013, 02:25:20 pm »

Bob,
Once more, Thanks a bunch!!! I now have high hopes.

I moved all of the files from my music folder to a separate folder within my documents file and then imported one MP3 file from music via Tools, single folder. And it played!!! And after exiting from the program and terminal window, it played the one song in my Library again, several times!!!

Problems exist and I'm not sure how to handle them.

I can move my other 11+k files back into /home/dick/Music, easily, but how do I find the "problem file(s) that screwed up this process before. Obviously, importing 11+k files one at a time is darned near impossible. I have about 40% ogg files, 50% MP3 files, and the others are .wav or possibly even other types including some Windows Media Files. These all played on my old MJ8 on Windows XP SP3 and I had, at one time, actually used WINE to put MJ8 onto LMDE, but it wouldn't recognize my dvd/cd drive. But it would play my files which I could import via Banshee or some other Linux media player.

Questions:

1) How do I determine which files will not import and delete or use Banshee or some other program to convert them to a format which will play on MC 19?

2) MC 19 still does not show up on my LMDE programs list, I can only get to it via the terminal and "mediacenter" so how do I get MC 19 to show up on my program list or at least put it onto my task bar?

3) How do I get MC 19 to import from my cd/dvd drive?

4) At what point do I add my MC 19 license since this MC 19 "expires" on 7 November.

Remember, I'll probably not be checking on this site again after this evening until Sunday evening as i will be out of town.

Here is the terminal window after I played my one mp3 file and then stopped it:

Code: [Select]

dick@music ~ $ mediacenter
JRiver install path (process: 5341): /usr/lib/jriver/Media Center 19/
CJRSharedToolsHelper::AuthenticateJRSharedLib
JRFileSystem::GetDirectoryAppdataCommon
CJRSharedToolsHelper::AuthenticateJRSharedLib
JRFileSystem::GetDirectoryDocuments
JRFileSystem::GetDirectoryDesktop
JRTools checking thread
CJRSharedToolsHelper::AuthenticateJRSharedLib
CJRSharedToolsHelper::AuthenticateJRSharedLib
JROs -- analyze operating system
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JRFileSystem::GetDriveType
JROs -- analyze operating system
Setting focus: 0A999E00
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
CJRSharedToolsHelper::AuthenticateJRSharedLib
JROs -- analyze operating system
JRFileSystem::GetDirectoryDocuments
JRFileSystem::GetDirectoryDocuments
GetDiskStatistics
Setting focus: 0A94C258
Setting focus: 0C00DFE8
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
GlobalFunc: RunProgram
Setting focus: 0A94C258
Setting focus: 0C026F80
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Setting focus: 0A94C258
Setting focus: 0B016428
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Destroying font (32840 bytes)
JRFileSystem::GetDirectoryWindows
JRFileSystem::GetDirectoryProgramFiles
GetAvailableDrives
Setting focus: 0A94C258
Setting focus: 0B016428
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Setting focus: 0A94C258
Setting focus: 0B016428
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Setting focus: 0A94C258
Setting focus: 0C026EC0
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Setting focus: 0A94C258
Setting focus: 0B016428
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Setting focus: 0A94C258
Destroying font (32840 bytes)
Setting focus: 0AA36C38
JRBasicWnd::SetCapture
Destroying font (32840 bytes)
GetDiskStatistics
Setting focus: 0AA35A58
JRBasicWnd::SetCapture
Destroying font (32840 bytes)
Setting focus: 0B016428
JRBasicWnd::SetCapture
Setting focus: 0BCDA690
JRBasicWnd::SetCapture
Setting focus: 0A94C258
JRWndTools::StringFromWindowClass
Setting focus: 0B19D4A8
Setting focus: 0B60CEE8
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Setting focus: 0B19D4A8
Setting focus: 0B60CEE8
Setting focus: 0A94C258
GetDiskStatistics
Setting focus: 0B016428
JRBasicWnd::SetCapture
JRBasicWnd::SetCapture
Setting focus: 0A94C258
Setting focus: 0B611730
Setting focus: 0A94C258
Setting focus: 0B620180
Setting focus: 0A94C258
Setting focus: 0C9094E8
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Setting focus: 0A94C258
Setting focus: 0B620180
Setting focus: 0A94C258
Setting focus: 0B620180
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Setting focus: 0A94C258
Setting focus: 0B620180
Setting focus: 0A94C258
Setting focus: 0B620180
Setting focus: 0A94C258
Setting focus: 0C909910
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Setting focus: 0A94C258
Setting focus: 0B1B0D78
JRBasicWnd::SetCapture
GlobalFunc: RunProgram
JRFileSystem::GetDirectoryDocuments
Destroying font (32840 bytes)
Destroying font (32840 bytes)
Destroying font (32840 bytes)
Destroying font (32840 bytes)
Destroying font (32840 bytes)
Destroying font (32840 bytes)
Destroying font (32840 bytes)
Destroying font (32840 bytes)
Destroying font (32840 bytes)
Destroying font (32840 bytes)
dick@music ~ $

Thank you again for your time, putting up with this semi-Linux old f*rt, and your and the rest of the JRiver gurus who are making running MC 19 on Linux possible.

tlcmd (aka Dick)

JimH · « **Reply #31 on:** October 24, 2013, 02:49:03 pm »

Your posts would be easier to read if you could put code and /code tags around the part you're pasting. Add square brackets around the code tags. I've done it for you a couple of times. Thanks.

Try MP3 first, then WAV. Ogg may not be working yet. WMA might be "protected".

bob · « **Reply #32 on:** October 24, 2013, 04:03:28 pm »

Quote from: JimH on October 24, 2013, 02:49:03 pm

Your posts would be easier to read if you could put code and /code tags around the part you're pasting. Add square brackets around the code tags. I've done it for you a couple of times. Thanks.

Try MP3 first, then WAV. Ogg may not be working yet. WMA might be "protected".

Yes, testing one filetype at a time would be good.
I'm pretty sure the wma's aren't supported at all.

INTERACT FORUM

Author Topic: JRiver Media Center 19.0.60 for Debian (Read 10113 times)