on Linux CD specific calls are used to get status of drive/door and CD disk type in drive - better user feedback)Ĭdda2wav is a ripper not a player - once started it does not provide the capability to "pause" a track rip but it can started at a timepoint in a track. The plugin aimed to be simple by using a common exe to handle CDs across Windows, Linux and OSX and keep OS specific system calls to minimum (e.g. position.The plugin starts a separate instance of cdda2wav for each track. 'Pause' with LMS on Linux/CDPlayer stops playing (don't know if the disk kept spinning) and after 'play' spinning speeds up with max. 'Pause' with Win10/VLC just stops playing (DVD-Drive keeps disk spinning on slow speed (guess x1) and 'play' starts playing w/o delay. skip x secs) and to do control and each time cdda2wavis called, it does its own thing - such as reread the disk. OS and/or CDdrive will cache tracks and do readahead to keep disk spinning.ĬDplayer is not efficient because cdda2wav is used to find track (e.g. No idea what the Muscibrainz speculation is about - it has nothing do with CD handling - IIRC it is just looking up an id based on track lengths from info on CD TOC.ĭon't understand pause/play comment. #WIN10 CHANGE DEFAULT CD PLAYER WINDOWS#Handlign CD from Windows API is horrible. In CDplayer context Windows CD handling is crude and CDplayer could only use cdda2wav and be less informative about state of CD drive. I did test with a CD-Text CD.ĬD reading is mainly handled at OS level so VLC will probably be similar to cdd2wav on same OS. LMS/ CDplayer seems to be to seek the position again and load/cache data.ĬD with CD-Text are rare but CD-Text should not be the cause of the delay. Especially Pause/Play doesn't have any delay. #WIN10 CHANGE DEFAULT CD PLAYER PC#But finally I guess the easiest is to skip this CD Nevertheless, I'm wondering how VLC and the Win 10 PC handles it (also using MusicBrainz and the same Internet connection). I just noticed - the differences between this CD and others seems to be CD TEXT. (guess that are my 2 to 3 sec.) and radio station timeout is set. Btw, radio station buffer is set to 3sec. I just tested wit V1.10 before I read you answer and you are right. I can do nothing about it - it is between CD, cdda2wav and OS.Ahh - OK thanks for explanation! Make sense. I have one CD which the drive hates and takes over 20 secs to get going - sometimes never), what the OS has cached about the CD and the speed of the CD drive. In this case, the delay before and audio stream starts will depend on the CD (e.g. a very slow internet stream, high sample rate and radio station buffer seconds has been set large). This is true for all sources but is only noticed when there are long delay to start (e.g. I can do nothing about it - it is between CD, cdda2wav and OS. The clock is reset once acctual playback has started. The WebUI will start a clock once play has been pressed on the basis that it will take no time to start playing (e.g. Will try it within the next days with v1.10.This is normal. Can't see any related debug messages but the same DVD-Drive did not show the behavior connected to a Windows 10/VLC PC. before streamingĮdit: Other CDs shows a similar behavior but only with 2 to 3 sec. to play something (Start playing/ Start from pause/ Jump to next track, etc.) The time counter starts until 15 sec. With this CD (OASIS/ Definitely Maybe - ) it always needs about 15 sec. But I've an odd behavior with one CD which I guess also occurred with V1.10 but I never took notice about.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |