demux errors with ripbot ...

[zero7404]

lately some of the movies i've tried to encode with ripbot 1.16.5 have spit out demux errors ... not sure why, but here is the contents of the file test.log, maybe someone can tell why it's failing ?

DirectShowSource: couldn't open file D:\Temp\RipBot264temp\job6\video.mkv:
The system cannot find the file specified. 
(D:\Temp\RipBot264temp\job6\getinfo.avs, line 2)

[Baldrick]

Upgrade to ripbot 1.17.

How do you rip?

[zero7404]

i would like to find out why its spitting this error out with some movies .... trying to find out if i have a problem with the drive or with software.

i use anydvd hd to decrypt. then i pick the m2ts from the disc directly using ripbot. i don't use anydvd to rip to hard disk or rip to image .... so ripbot is demuxing directly from the disc itself.

lately, while demuxing, i notice that anydvd hd starts over and scans the disc, that results in the error as well. so maybe my drive is cheap or dirty or something. i have an internal bd rom slot-loader on a laptop (12.7mm).

.....
sent via android

[redwudz]

Most laptop drives have the laser lens exposed at the top of the tray, so easy for it to get dirt or grease on it. I would try cleaning it.

The error itself shows up at times with RipBot. Usually if you rip to the same drive you are encoding to. It's most often associated with losing data between drives. If it did it with all your discs, then I would try re-installing RB as that sometimes helps. I usually rip the whole disc to the drive, but with limited space, not so easy.

[zero7404]

i have a slot loader, no access to the lenses ....

.....
sent via android

[redwudz]

There are DVD cleaning discs, though with a slot loader, not as likely to get debris on the lens as with a tray type drive.

[zero7404]

There are DVD cleaning discs, though with a slot loader, not as likely to get debris on the lens as with a tray type drive.

i have one for blu-ray lenses ... the cleaning disc has clearance pockets next to each brush, because the distance from the lens to the disc surface is so small, the brushes go into this pocket as they spin over the lens.

anyway, it doesnt do much good. i think i have a cheap drive ... its an optiarc bc-5600 ....

.....
sent via android

[zero7404]

Most laptop drives have the laser lens exposed at the top of the tray, so easy for it to get dirt or grease on it. I would try cleaning it.

The error itself shows up at times with RipBot. Usually if you rip to the same drive you are encoding to. It's most often associated with losing data between drives. If it did it with all your discs, then I would try re-installing RB as that sometimes helps. I usually rip the whole disc to the drive, but with limited space, not so easy.

i've been experiencing this ever since i started using ripbot ... and and i don't think jumping to a different version of the software will change things. is this a bug or limitation ? i have a high end laptop slot-loader bd-r/rw drive (teac 6x with bd-xl capability) .... it plays the movies fine however i can never tell whether it will demux fully until i try. sometimes a tiny microscratch on the surface is enough.

but i'm not following what you mean about losing data between drives when you refer to using the same drive for the source and where the encode will be saved....

i typically demux directly from the disc and this happened so far with about 1/5 of the movies i've tried to encode. so sometimes i try something different and do a rip to harddisk with anydvd to do the demux from the hdd as the source rather than the bd.
can't remember if the last time i did this it worked or not, but i just encountered a movie that errored on me when i demuxed from the disc, so i'm ripping to the hdd right now using anydvd hd, hopefully the ripped m2ts file will demux.

but i have no choice except to store the m2ts on the same drive as i need to demux because my other drives don't have enough space for demuxing.