INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Problem Starting Playing  (Read 1305 times)

BradC

  • World Citizen
  • ***
  • Posts: 207
Problem Starting Playing
« on: January 27, 2011, 10:25:39 pm »

HI

Since build 171, MC has had a problem on my system when starting to play files. The issue may have appeared earlier than that though as I don't install every build
I have 'start on add to playing now' enabled, and the first file added to playing now in a new session, requires a press of stop, then play, to get the file playing.

I am using ASIO, and reading files over gigabit ethernet.

I hope this issue can be addressed soon, as it's quote annoying
Logged

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 42032
  • Shoes gone again!
Re: Problem Starting Playing
« Reply #1 on: January 27, 2011, 10:32:10 pm »

Could you describe a little more what you're seeing?  What happens when you start playback the first time?

Could you try a different soundcard or files from a local drive to see if that makes a difference?

Thanks.
Logged
Matt Ashland, JRiver Media Center

HiFiTubes

  • Citizen of the Universe
  • *****
  • Posts: 1123
Re: Problem Starting Playing
« Reply #2 on: January 29, 2011, 07:51:52 pm »

Are you using Library Server, sounds like it.

I rolled back to .136 because i couldn't get playback starting or it would lag for a minute. Sometimes the file just played could then not be replayed.

http://yabb.jriver.com/interact/index.php?topic=61296.0
Logged

BradC

  • World Citizen
  • ***
  • Posts: 207
Re: Problem Starting Playing
« Reply #3 on: January 30, 2011, 01:26:17 am »

Hi

When I start playing by double clicking a file to add to playing now, after the display of 'opening' in the status bar, it says 0:00/x.xx and stays like that indefinitely.
Pressing stop, then play gets the file playing.

The problem only reappears on a reboot.

I tried a different sound card and it worked fine.

So I reverted the RME fireface drivers to ver 3.016 and it seems to have fixed the problem

Thanks for the assistance
Logged
Pages: [1]   Go Up