puschi
31-12-13, 12:21
Hi.
I'm using 3.0.806 and have a little problem with recording a HD movie.
On every (!) HD movie i record, there is a gap (and fragmentation), exactly 6-7 seconds after the start of a new record.
The gap takes than 7-9 seconds. After this the record is perfect, without any problem.
This problem is there since 3.0.64x i think.
The problem (possible bug) is, that the vix image isn't waiting long enough, for spinning up the sleeping HDD.
Older versions of vix didn't had this problem (perhaps using a other way to check if the hdd is spinning up?)
Background:
- HDD is connected over USB.
- HDD is a WesternDigital
- The problem isn't occur, if i record with a running HDD (first play a movie and than record before the hdd goes to sleep)
- The problem isn't occur, if i record a SD movie.
- Sleep time is set to 2 Minutes.
- Using a swap file on a usb-stick didn't change this problem (vix swap 1MB of memory, but didn't access the usb stick/swap-file in the moment he is recording a movie)
- The problem occur on a direct recording (with sleeping HDD)
- The problem also occur on timer recording (with the vix spinner is there some seconds before starting a record, so the vix is waking up the hdd)
I think, vix starts the record in this moment, the hdd is accessible the first time. But the HDD takes a little time too, to be full accessible (writable), perhaps with calibration of the head's and so on (it sounds so)...
So the record is starting (eating the whole cache? ) and has a problem to write the stream, becouse the hdd isn't ready in this moment.
If the hdd is ready after some additional second, the recording is continuing with this gap.
Is it possible to change the detection of a successfully spinnig up hdd (dummy read or write of a sector, that isn't in cache)?
Perhaps it is a good idea to adding a new variable setting: max. wait time for spinning up the HDD??
Thanks and a happy new year.
I'm using 3.0.806 and have a little problem with recording a HD movie.
On every (!) HD movie i record, there is a gap (and fragmentation), exactly 6-7 seconds after the start of a new record.
The gap takes than 7-9 seconds. After this the record is perfect, without any problem.
This problem is there since 3.0.64x i think.
The problem (possible bug) is, that the vix image isn't waiting long enough, for spinning up the sleeping HDD.
Older versions of vix didn't had this problem (perhaps using a other way to check if the hdd is spinning up?)
Background:
- HDD is connected over USB.
- HDD is a WesternDigital
- The problem isn't occur, if i record with a running HDD (first play a movie and than record before the hdd goes to sleep)
- The problem isn't occur, if i record a SD movie.
- Sleep time is set to 2 Minutes.
- Using a swap file on a usb-stick didn't change this problem (vix swap 1MB of memory, but didn't access the usb stick/swap-file in the moment he is recording a movie)
- The problem occur on a direct recording (with sleeping HDD)
- The problem also occur on timer recording (with the vix spinner is there some seconds before starting a record, so the vix is waking up the hdd)
I think, vix starts the record in this moment, the hdd is accessible the first time. But the HDD takes a little time too, to be full accessible (writable), perhaps with calibration of the head's and so on (it sounds so)...
So the record is starting (eating the whole cache? ) and has a problem to write the stream, becouse the hdd isn't ready in this moment.
If the hdd is ready after some additional second, the recording is continuing with this gap.
Is it possible to change the detection of a successfully spinnig up hdd (dummy read or write of a sector, that isn't in cache)?
Perhaps it is a good idea to adding a new variable setting: max. wait time for spinning up the HDD??
Thanks and a happy new year.