INTERACT FORUM
More => Old Versions => JRiver Media Center 18 for Mac => Topic started by: laerm on May 09, 2013, 03:59:20 pm
-
Hi all –
I thought I'd start a new thread for an issue I mentioned in http://yabb.jriver.com/interact/index.php?topic=80441.msg547459#msg547459 (http://yabb.jriver.com/interact/index.php?topic=80441.msg547459#msg547459) with Matt.
MC is unclickable after running for 30 minutes or so. It's not frozen. It's like the window is "invisible" to the mouse but visible to the eye. Clicking on it will actually be a click on whatever is underneath the window. (Right-clicking lets you figure out what is beneath.)
Audio is good and no other issues, but this has been an issue since .179. It also will not respond to any keyboard commands EXCEPT play/pause from the media keys.
OS X 10.8.3
MC 180
Thanks!
Micah
-
So, sort of a bump. I still have this issue. Anyone else seeing this? I am now on .182 and it's still here. Really annoying to find that the app is essentially unusable within 20 minutes. :(
Thanks...
Micah
-
It went away for me but it has come back 3 times when using 181 and 182. Don't know what is triggering it.
-
Thist started happenning for me with v82, it was never there until I went from v76 to this one. I'll try going back to an earlier version if it persists. This is weird behavior that I haven't encountered before in any program.
OSX 10.8.3
2.53mgz core 2 duo
-
This sounds exactly like the issue I am having with the latest build (.191), it hasn't hung or crashed I just can click anywhere in the UI and have it do anything and the menu at the top reflect the program UNDER MC. Tracks that are playing keep playing and the highlighted track changes in the UI as the tracks change.
I 'quit' and the UI closed but the app remained in the dock until I forced quit.
-
Happening with me too. Started with v190 still there is v191. Never happened before, so gone back to v187 which is fine.
OSX 10.8.3 with all versions of MC
-
I see this periodically as well. On a side note, this time it just happened I couldn't even right-click on the dock icon / Quit or go to the upper menu / Quit. Neither did anything, so I had to force quit.
-
Hello all -
Just so I don't leave a topic I started after it picks up steam... I am away for the next week and have not updated since before I left 9 days ago. I was still having this problem, though. I look forward to see if the new version solves anything.
Micah
-
I too have seen this exact same, very frustrating problem, intermittently but quite frequent with .191.
-
We're still trying to solve this. We can reproduce it.
-
In certain cases, the program was making itself "topmost" window so that if a dialog window popped up (i.e. the Options dialog), it would be below Media Center and not visible. Media Center would appear to be totally unresponsive.
We've fixed this issue for tonight's build, so please test it out. It's possible there are other window "focus" issues remaining.
If problems remain, please try to figure out a series of steps that reproduce the problem so we can try it here.
-
Still does for me using the latest beta.
-
I confirm,
I still have this issue with .193.
Below one reproducible method to get it:
1) Output mode is set to Display Audio (it is a thunderbolt display) instead of M2Tech as usual
2) I select a track which is a FLAC file with 24bit/96KHz
3) I get the warning box Playback Problem: Playback could not be...using the format '96kHz 24bit 2ch'. Up to now nothing wrong.
4) I close the box with ok and that's it, focus is lost, MC has become unclickable!!!
Cheers,
Etienne
Macbook Pro Retina 15"
Thunderbolt Display
OS X 10.8.3
Hiface 2 +Micromega MyDAC
-
With version 193, similar to Taz_er88, I can make MC unresponsive to mouse clicks.
It seems to happen by provoking the display of an error message and then dismissing the dialog box. The focus goes somewhere, but not back to the main MC window. The playback problem dialog is usually the one that does it when I not trying to make MC fall over.
Paul
-
I think we've got this fixed. Please try tonight's build when it's posted (194 or greater).
-
I think we've got this fixed. Please try tonight's build when it's posted (194 or greater).
Lookin' good!
-
This seems to be ok for me now....thanks!
Micah