INTERACT FORUM

Please login or register.

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

Author Topic: Unusual behaviour while ripping discs  (Read 459 times)

EnglishTiger

  • Regular Member
  • Citizen of the Universe
  • *****
  • Posts: 1084
Unusual behaviour while ripping discs
« on: July 04, 2020, 09:13:02 am »

Over the last 2 days I've used MC to rip over 260 CD's whilst having it play tracks already in my library and encountered some odd behaviour.

Every now and then, but usually if I loaded a new CD to rip when MC was finishing the current track and loading in the next track, MC seemed to forget that it was supposed to Read the CD - the tree entry for the optical drive would change from "Compact Disc (E:)" to "Audio CD" and the only way I could get MC to read the disc was by "giving it a kick" - by making it read the disc. Incidentally since all of the discs I was ripping contain CDText the YADB Look-up was turned off to force MC to read the onboard CDText file. It also happened a couple of times whilst a track was playing but on one occasion after I gave MC a kicking the Status Line informed me it was "Saving Tag Changes".
Logged
Apple Mac Mini Desktop Computer with M4 Pro chip with 12 core CPU and 16 core GPU: 24GB Unified Memory, 512GB SSD Storage, Gigabit Ethernet, 3 Thunderbolt5 + 2USBC ports.

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72438
  • Where did I put my teeth?
Re: Unusual behaviour while ripping discs
« Reply #1 on: July 04, 2020, 10:02:26 am »

There are two possibilities I can think of. 

1.  A Windows update.

2.  Antivirus

CD-Text is not commonly used.  It also won't provide cover art.
Logged

EnglishTiger

  • Regular Member
  • Citizen of the Universe
  • *****
  • Posts: 1084
Re: Unusual behaviour while ripping discs
« Reply #2 on: July 04, 2020, 10:18:00 am »

Jimh - Over 80% of my CD's have onboard CDText. That odd behaviour was happening before the last 2 MS Win10 Updates. Also if it was the Antivirus why would it stop MC from automatically reading the CD but didn't interfere with it reading the disc when I told it to?

P.S. - I mainly raised this thread to alert others to the strange behaviour I was encountering since having to give MC an "occasional kick" is something I can live with. The world ain't gonna stop turning if it all it turns out to be something that can't be recreated under different circumstances or with a different hardware/software setup.
Logged
Apple Mac Mini Desktop Computer with M4 Pro chip with 12 core CPU and 16 core GPU: 24GB Unified Memory, 512GB SSD Storage, Gigabit Ethernet, 3 Thunderbolt5 + 2USBC ports.

mattlovell

  • Galactic Citizen
  • ****
  • Posts: 330
Re: Unusual behaviour while ripping discs
« Reply #3 on: July 04, 2020, 03:01:24 pm »

Quote
... It also happened a couple of times whilst a track was playing but on one occasion after I gave MC a kicking the Status Line informed me it was "Saving Tag Changes".

I had something vaguely similar occur...

I was updating tags in recently-ripped files.  I'm used to MC not wanting to update tags for a file currently being played.  This time, however, I got a "Tag updating almost done (just waiting for playback to stop)" status message (or words to that effect) at the bottom of the window when nothing was playing.  I double-checked both the player itself and all DLNA renderers; nothing was playing anyway.

I eventually just stopped the MC process and restarted things.
Logged
Pages: [1]   Go Up