INTERACT FORUM
More => Old Versions => JRiver Media Center 20 for Linux => Topic started by: bob on March 27, 2014, 06:16:37 pm
-
http://files.jriver.com/mediacenter/channels/v19/latest/MediaCenter-19.0.124-5.deb
Would those of you having trouble with the main window resizing please give this a go and let me know?
It MAY also help with the moving of internal boundaries, it will not speed them up but they may work properly on platforms that were having trouble.
Thanks.
-
I moved the laptop to Suse 13.1 64-bit. Debian doesn't run very well on my laptop unfortunately.
This build installs, runs and plays fine on Suse.
Moving and resizing of the main window works fine too. Resizing the window turns white until you release the mouse button.
Moving separators for the tree or panes is still very slow to respond.
On my own pc with this build (Debian 7.4 64-bit) moving the main window still doesn't work very well, although its improved though, almost usable :P. Before, it would simply jump out of sight, now it moves in slow motion, but continues to move when I stop moving the mouse. It doesn't jump offscreen anymore unless I move it around faster. Moving slowy, it sort of works but lags and moves in directions I didn't want.
-
I moved the laptop to Suse 13.1 64-bit. Debian doesn't run very well on my laptop unfortunately.
This build installs, runs and plays fine on Suse.
Moving and resizing of the main window works fine too. Resizing the window turns white until you release the mouse button.
Moving separators for the tree or panes is still very slow to respond.
On my own pc with this build (Debian 7.4 64-bit) moving the main window still doesn't work very well, although its improved though, almost usable :P. Before, it would simply jump out of sight, now it moves in slow motion, but continues to move when I stop moving the mouse. It doesn't jump offscreen anymore unless I move it around faster. Moving slowy, it sort of works but lags and moves in directions I didn't want.
Thanks.
Would you type this in on your PC at a terminal command prompt?
glxinfo | grep rendering
and post the result?
What is the video hardware on that PC? (lspci -v)
-
glxinfo | grep rendering
# glxinfo | grep rendering
direct rendering: Yes
GL_NV_parameter_buffer_object2, GL_NV_path_rendering
What is the video hardware on that PC? (lspci -v)
01:00.0 VGA compatible controller: NVIDIA Corporation GF110 [GeForce GTX 580] (rev a1) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device 8385
Flags: bus master, fast devsel, latency 0, IRQ 59
Memory at f6000000 (32-bit, non-prefetchable) [size=16M]
Memory at e8000000 (64-bit, prefetchable) [size=128M]
Memory at f0000000 (64-bit, prefetchable) [size=32M]
I/O ports at e000 [size=128]
[virtual] Expansion ROM at f7000000 [disabled] [size=512K]
Capabilities: [60] Power Management version 3
Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Endpoint, MSI 00
Capabilities: [b4] Vendor Specific Information: Len=14 <?>
Capabilities: [100] Virtual Channel
Capabilities: [128] Power Budgeting <?>
Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
Kernel driver in use: nvidia
-
Ps. Now got tripple boot on my own pc and its running Suse 13 as well now. Installed Nvidia proprietary drivers.
Moving works, but it's flickering and the window jumps all over the place, but it always returns to the mouse. Resizing is slower but it works. Takes a second for the window to draw again after a resize.
Some funkyness with the videodriver perhaps?
-
Ps. Now got triple boot on my own pc and its running Suse 13 as well now. Installed Nvidia proprietary drivers.
Moving works, but it's flickering and the window jumps all over the place, but it always returns to the mouse. Resizing is slower but it works. Takes a second for the window to draw again after a resize.
Some funkyness with the videodriver perhaps?
Default desktop of Gnome 3?
Can you install gtkperf and run it?
Here are the results on my fairly modest core 2 quad with a Nvidia 8400
GtkPerf 0.40 - Starting testing: Fri Mar 28 14:49:52 2014
GtkEntry - time: 0.05
GtkComboBox - time: 0.48
GtkComboBoxEntry - time: 0.27
GtkSpinButton - time: 0.05
GtkProgressBar - time: 0.03
GtkToggleButton - time: 0.05
GtkCheckButton - time: 0.04
GtkRadioButton - time: 0.06
GtkTextView - Add text - time: 0.18
GtkTextView - Scroll - time: 0.09
GtkDrawingArea - Lines - time: 0.46
GtkDrawingArea - Circles - time: 0.63
GtkDrawingArea - Text - time: 0.36
GtkDrawingArea - Pixbufs - time: 0.08
---
Total time: 2.83
-
XFCE4.
GtkPerf 0.40 - Starting testing: Fri Mar 28 21:14:27 2014
GtkEntry - time: 0.03
GtkComboBox - time: 0.73
GtkComboBoxEntry - time: 0.44
GtkSpinButton - time: 0.03
GtkProgressBar - time: 0.03
GtkToggleButton - time: 0.04
GtkCheckButton - time: 0.04
GtkRadioButton - time: 0.05
GtkTextView - Add text - time: 0.32
GtkTextView - Scroll - time: 0.05
GtkDrawingArea - Lines - time: 0.24
GtkDrawingArea - Circles - time: 0.21
GtkDrawingArea - Text - time: 0.13
GtkDrawingArea - Pixbufs - time: 0.05
---
Total time: 2.40
Not sure what or how that tests but I would expect a Core i7 with GTX580 to do better ::)
-
It's difficult to explain your results.
At home I've got a Haswell Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz slightly overclocked using the internal video XFCE4 and Wheezy 32 bit (but multiarch booting a 64 bit kernel) and I get this:
GtkPerf 0.40 - Starting testing: Fri Mar 28 21:38:35 2014
GtkEntry - time: 0.01
GtkComboBox - time: 0.22
GtkComboBoxEntry - time: 0.17
GtkSpinButton - time: 0.02
GtkProgressBar - time: 0.02
GtkToggleButton - time: 0.02
GtkCheckButton - time: 0.03
GtkRadioButton - time: 0.04
GtkTextView - Add text - time: 0.11
GtkTextView - Scroll - time: 0.05
GtkDrawingArea - Lines - time: 0.24
GtkDrawingArea - Circles - time: 0.42
GtkDrawingArea - Text - time: 0.43
GtkDrawingArea - Pixbufs - time: 0.07
---
Total time: 1.86
I can move the window are as fast as I can move the mouse, resize the window as fast as I can move the mouse, move the dividers up and down as fast as I can move the mouse all with no issues.
-
Its probably something in my setup then, don't worry about it.
-
fwiw, It might be video driver related too. I notice on my desktop with the opensource AMD driver, when moving the window, it goes white. But on my laptop(old Llano) with the fglrx beta, it does not.
-
Not sure what it is, but on a fresh install of Linux Mint 16 Cinnamon, it works fine.
No more jumping around, it moves fluidly. It slightly lags behind the mouse but that's it.
Moving the dividers inside mediacenter is also quite slow but not nearly as bad as it used to be.
-
Mint LMDE (Debian Jessie) 64 bit with KDE
If you open the window for the first time, it is better first select a library view, instead of moving the window or resizing it
If you do that, the picture is very unstable (jumps, flickers).
Then you can resize the window without flickering. during the operation, the entire window is white.
Resizing only works well in one direction (long or short side of the window).
Resizing the window on the corners, it jumps across the screen flickers heavily.
Moving the window works well with any speed
GtkPerf 0.40 - Starting testing: Mon Mar 31 00:53:35 2014
GtkEntry - time: 0,02
GtkComboBox - time: 0,65
GtkComboBoxEntry - time: 0,64
GtkSpinButton - time: 0,04
GtkProgressBar - time: 0,01
GtkToggleButton - time: 0,04
GtkCheckButton - time: 0,03
GtkRadioButton - time: 0,05
GtkTextView - Add text - time: 0,15
GtkTextView - Scroll - time: 0,05
GtkDrawingArea - Lines - time: 0,37
GtkDrawingArea - Circles - time: 0,37
GtkDrawingArea - Text - time: 0,14
GtkDrawingArea - Pixbufs - time: 0,07
---
Total time: 2,63
hans@enp2so ~ $ glxinfo | grep rendering
direct rendering: Yes
GL_NV_parameter_buffer_object2, GL_NV_path_rendering,
GL_NV_parameter_buffer_object2, GL_NV_path_rendering,
hans@enp2so ~ $ lspci -v
01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 440] (rev a1) (prog-if 00 [VGA controller])
Subsystem: eVga.com. Corp. Device 1441
Flags: bus master, fast devsel, latency 0, IRQ 24
Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
Memory at d0000000 (64-bit, prefetchable) [size=128M]
Memory at d8000000 (64-bit, prefetchable) [size=32M]
I/O ports at e000 [size=128]
[virtual] Expansion ROM at fe000000 [disabled] [size=512K]
Capabilities: [60] Power Management version 3
Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Endpoint, MSI 00
Capabilities: [b4] Vendor Specific Information: Len=14 <?>
Capabilities: [100] Virtual Channel
Capabilities: [128] Power Budgeting <?>
Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
Kernel driver in use: nvidia
-
It would be interesting to pin down if certain views cause trouble.
I have mine set to start at Last Location which is usually an audio view of some kind or another.
I think geier22 what you are seeing on the jumping while resizing is if you try to resize MC below it's minimum size it appears to move at the minimum size in the direction you were trying to resize it. It seems to me that when the minimum size is reached we just should exit the resize state.
-
I think it has to do with window composition effects,
In Suse 13.1 (KDE) I made a window rule to disable composition for MediaCenter19 window and nearly generally all jumping around while moving is gone.I say generally because sometimes, it suddenly starts jumping around for a second and then goes back smooth again.
-
Can't believe I hadn't noticed this before but most of the major jumping around is when the window transitions from monitor 1 to monitor.2,
-
Can't believe I hadn't noticed this before but most of the major jumping around is when the window transitions from monitor 1 to monitor.2,
Thanks, that helps.
-
Bob ... I'm sorry but its erratic, I thought I fixed it by disabling Composition effects but now I can't reproduce and its jumping all over the place again.
:-[
-
correction:
upper corners: Resizing produces strong flickering. The window jumps around the screen.
lower corners: Resizing works well.
In all cases (corners, sides) during resizing the window is white
The behavior described above is when I start in audio
If I set the options for opening MC to "Start", the behavior of the window is unstable in all directions.
I have it tested several times - always with the same result
Open, Maximize, Minimize and mini view: MC never forgets its original size and works very well.
My monitor is a 30 inch screen with dual DVI - I do not know if that plays a role, because I can not explain the behavior described above
Generally for me this is the best version yet
-
Hi,
Just a quick note of what I have noticed. At this point my laptop that runs integrated HD4000 graphics has very few issues. However my PC with Nvidia 760 has flickering etc. All effects turned on, on the PC desktop, standard effects for the laptop. Running Mint 16 x64 Cinnamon on both.
Thanks
-
Howdy,
Assistance please!
I finally managed to set up a dual boot on my Brand New HP Envy 700-056-216 computer which has Windows 8.1 and Linux Mint Debian Edition.
The sound card is a Beats Audio; High Definition Audio, up to 7.1 channels
My Problem: It will not play the sound output from the Linux MC 19 and tells me that there might be a problem with the ALSA 44.1 KHz 2 ch settings and is advising me to go to the DSP studio to reset it.
At this point, I am completely lost.
What sound settings do you recommend? Or do you recommend my downloading another version of MC19 for the Linux Mint Debain Edition?
Since I have installed my Linux Distro this distro seems to be working fine and plays music from Banshee: ogg, wave, and mp3 files fine. It also plays Youtube video and sound without difficulty.
And when in the Windows 8.1 mode, it plays MJ8 music files on my Windows partition.
Thank you your patience and assistance. I realize that I can be a pest with my sub-literate knowledge of computers and as a physician do realize problems in communication when trying to explain things about which your audience's concepts are quite limited.
Thanks again,
Harmmoniously (I'm a barbershop singer),
tlcmd.
-
Look first in the System Settings to your sound card.
Then open MC and go to Options ---> Audio. Select ALSA driver.
Then Device Settings. There probably many "devices" appear (Linux problem). Here you have to try. It will probably be a device named dev = o (default soundcard)
Before you can listen to music, it is important to set in DSP-Studio all frequencies below 48 kHz to 48 kHz, as PCM in the rule can not reproduce frequencies below.
-
Geier22,
Thanks, It worked. Now all I have to do is create my playlists.
My songs are already categorized by genre, but I'd like to have a way to NOT play any Christmas Genre songs for most of the year, for obvious reasons. MJ8 allowed that, do you know if this is a feature in MC19 for Linux? Par example; Julie London, a torch singer did a lot of mood music and romance numbers and also a couple of Christmas ones. I have her "I'd Like You For Christmas" marked as Christmas and mood, but would like to exclude it from her usual mood numbers smartist. Any ideas?
Thanks,
tlcmd
-
Is there a much needed or pending help section (for me, at least) for setting up Linux MC19, or will I gain as much knowledge from using the Help in MC19 for Windows or Mac (if it exists). So far, I've been flying by the seat of my pants and help from this forum, but would like some specifics on setting up smartlists, etc.
Thanks,
tlcmd
-
For the basic operations of MC, a fair amount of which is platform agnostic, read any existing info on the Wiki or here on Interact (primarily in the Windows boards). Feel free to ask specific questions on this board if you want, and someone will move them if necessary.
I'm still awaiting your follow-up from:
http://yabb.jriver.com/interact/index.php?topic=85977.msg588345#msg588345
http://yabb.jriver.com/interact/index.php?topic=63786.msg604701#msg604701
:-)
-
There are several threads here with instructions for specific distros.
-
MC forgets the DSP - Settings
I do not know if this is a bug in this version, or if I've forgotten something. It is also the first time that I notice that.
My DSP Studio- Settings are as I described it in post 20.
When I play a song greater 48 kHz, MC resamples the song to 48 kHz. In DSP- Studio everything changed (see Pichture) I have tried this with all frequencies. Always with the same result. MC changes the DSP-Settings.
The songs with 44.1 kHz can not be played for this reason(playback - problem)
-
MC forgets the DSP - Settings
I do not know if this is a bug in this version, or if I've forgotten something. It is also the first time that I notice that.
My DSP Studio- Settings are as I described it in post 20.
When I play a song greater 48 kHz, MC resamples the song to 48 kHz. In DSP- Studio everything changed (see Pichture) I have tried this with all frequencies. Always with the same result. MC changes the DSP-Settings.
The songs with 44.1 kHz can not be played for this reason(playback - problem)
Hi geier,
I'm using two playback devices - one is the local onboard device, the second a Bose usb-stick. The local device will play only 44100 and 48000 HZ, the Bose only 48000Hz. It happened sometimes after installation, that the Bose will reset to 41000 and 48000. If I reset it to 48000, everything runs well. This problem might be tight to your sound system. If you just set the 44100 to 48000, it should play those songs. (see screenshot)
-
Hi bob,
the windows are still destroyed, when you move them around (see image)
-
The Linux sound system is a big clutter and chaos. ? ? :(
What had I done:
I have blacklisted the HDMI- Card in / etc / modprobe.d / alsa-base-blacklist.conf and uninstalled Pulse-audio. In the settings at MC I have not changed anything (I SWEAR). But the audio device was now set to "default card = Audiophile192", and not on "front:CARD=Audiophile192, DEV=0"
This card can play obviously only 48kHz.
Now everything is again as it should be. 192 kHz songs are played without downsampling.
Once again I get gray hair!
@ UDO.S: The output format is PCM in my Soundsyten (only ALSA). Music less than 48 kHz is not reproduced by MC. All songs below 48 kHz must be sampled to this format.
P.s.
it would be nice if the format *. jpeg would be allowed as an image attachment. No Linux application automatically saves an image in jpg - format. Every time I have to rename the images!
-
Just installed 19.0.124-5 on my Ubuntu 13.10 system (3.11.0-19-lowlatency) and it fixed the jittery resize window problem straight away. Thanks for a great product.
One question: I'd like to use a remote and/or the media control keys on my Saitek keyboard under Linux. Recommendations or know how would be much appreciated, please.
Thx in advance.
-
One question: I'd like to use a remote and/or the media control keys on my Saitek keyboard under Linux. Recommendations or know how would be much appreciated, please.
I don't know if MC remotes are supported in Linux. MC has a Media Key setting you could try. Gizmo on an Android will work. Tremote will also work. The wiki has a topic on remotes.
-
The Linux sound system is a big clutter and chaos. ? ? :(
What had I done:
I have blacklisted the HDMI- Card in / etc / modprobe.d / alsa-base-blacklist.conf and uninstalled Pulse-audio. In the settings at MC I have not changed anything (I SWEAR). But the audio device was now set to "default card = Audiophile192", and not on "front:CARD=Audiophile192, DEV=0"
This card can play obviously only 48kHz.
Now everything is again as it should be. 192 kHz songs are played without downsampling.
Once again I get gray hair!
@ UDO.S: The output format is PCM in my Soundsyten (only ALSA). Music less than 48 kHz is not reproduced by MC. All songs below 48 kHz must be sampled to this format.
P.s.
it would be nice if the format *. jpeg would be allowed as an image attachment. No Linux application automatically saves an image in jpg - format. Every time I have to rename the images!
Fixed the jpeg attachment thing.
Check your
Tools->Options->Audio->Advanced settings.
There is an item called: Auto configure audio output settings on playback error.
If it's set to yes, it will change your DSP studio output format settings upon playback error.
As far as the changing the device is concerned, if at any time you modified the device lists (by blacklisting for example) and then the chosen device doesn't exist, when you go into the settings dialog it will switch to something that does, I thought that was always default but that may be incorrect.
-
When connecting to a Media Server (in my case, Windows but I don't know if that matters) it looks like MC Linux tells the server it doesn't support anything so it all gets converted.
The reason I think this is the case is because I always get low bitrate lossy files until I configure the server to never convert. When I set it to convert only when needed, everything gets converted, always.
But now Gizmo won't play half my library :(.
-
When connecting to a Media Server (in my case, Windows but I don't know if that matters) it looks like MC Linux tells the server it doesn't support anything so it all gets converted.
The reason I think this is the case is because I always get low bitrate lossy files until I configure the server to never convert. When I set it to convert only when needed, everything gets converted, always.
But now Gizmo won't play half my library :(.
Actually we tell the server we support EVERYTHING (use device spy and look at MC's SinkProtocolInfo). A lot of DLNA servers are simply brain dead.
When MC connects to a library server as a client it should use the client options in the Media Network->Client Options->Audio Conversion.
When you PUSH to a renderer (MC or otherwise) with MC as the server as well, the settings used are the associated MC server settings.
WHen you PUSH to a renderer (MC or otherwise) with another Server and MC as controller, the other server determines the format.
-
Apologies for being unclear; the server in my case is JRiver MediaCenter 19 (just updated to the latest this morning) running on Windows. The client is JRiver MediaCenter 19 on Linux (build from this thread). In my attempt to make clear MC on the server is NOT on Linux, I failed to make clear it was actually MC.
So, with MC server (on windows :P) in convert only when necessary, MC on Linux receives lossy low bitrate. When set to never convert, it receives files natively. But, the latter setting prevents Gizmo from playing certain files (DSD for instance).
Oke you can stop laughing now ....
Not the first time I make this mistake :-X
I'm setting client settings on the server and expecting it to have an affect clients connecting to this server. I need to set these ON THE CLIENT.
Gizmo's problem was actually an issue related to the wifi network at the office.
Sorry ... :D