HiCrusher said:That kind of sucks..... This feature should be added.
it's your first attempt and it's telling you that it has an invalid path. Have you tried again inputting new paths you know are valid?0xdeadbeef said:IMHO having the possibility to process files on the HD is a MUST HAVE!
Not only because I prefer to rip manually, but because in case of crashes, it has to be possible to start processing without ripping again.
Target path was perfectly valid (D:\DVD) and contained no files, but only 4 directories. Amongst them an empty VIDEO_TS and AUDIO_TS. Creating an additional folder level (D:\DVD\DVDStripper) solved the problem, so I'm convinced that there's a bug in the folder creation routine or something similar. Maybe this only happens if there are no files in the target directory, but only (empty) folders.MackemX said:it's your first attempt and it's telling you that it has an invalid path. Have you tried again inputting new paths you know are valid?
can you describe the error a little more as I'm still at a complete loss as to what happened. It shouldn't crash but if you have managed to input invalid filepaths then it will crash. I have a feeling it may be to do with your backup path but I'm not sure yet
can you take a snapshot of the 1st screen and then attach it as an image here? (see below). If you cant then email me the picture and I will check it
I have just again tried it with the two empty folders in my backup folder and it works perfect0xdeadbeef said:Target path was perfectly valid (D:\DVD) and contained no files, but only 4 directories. Amongst them an empty VIDEO_TS and AUDIO_TS. Creating an additional folder level (D:\DVD\DVDStripper) solved the problem, so I'm convinced that there's a bug in the folder creation routine or something similar. Maybe this only happens if there are no files in the target directory, but only (empty) folders.
Hm, I dunno. The path was however correct. Maybe it's not easily reproducable. However it would be much easier to trace such things down and less annoying for the user if the ripping wasn't mandatory.MackemX said:I have just again tried it with the two empty folders in my backup folder and it works perfect
an invalid path could happen if these folder are modified after setting the paths but before processing
I'm still confused as to what happened or how you managed to do it
Ripping is necessary as it is with most software, how else are you going to modify the VOB's?0xdeadbeef said:Hm, I dunno. The path was however correct. Maybe it's not easily reproducable. However it would be much easier to trace such things down and less annoying for the user if the ripping wasn't mandatory.
can I ask what you not happy about?0xdeadbeef said:I do and that's exactly why I'm not very happy.
I have had success mounting my pre existing files on a virtual drive and using dvdstripper from there. I would also like to be able to use dvdstripper straight from the hard drive but i realize dvdstripper is a work in progress and takes time to implement all features.Bear263 said:You can not use files on your hard drive. You must go through dvdstripper to rip.
Screw that, I want a naked chic patch for it!0xdeadbeef said:BTW: would it be possible to have an icon that doesn't look like a porn dialer (yes, I know, the name's a pun, but the icon is ... err ... kinda cheap).
it does indeed , but I would like to think we have done well so far seeing as it's still less than a month since release and it's still around 7 weeks since the project first startedDysmyl said:I realize dvdstripper is a work in progress and takes time to implement all features.
I just ripped/processed X-Men using DS. Agreed, the result is perfect. However, I had some problems again.MackemX said:can I ask what you not happy about?
you said it works perfectly yet you are still unhappy which is what I cannot understand
And again there is a "but" (or in this case a "however"). I'm not sure what's confusing about this: I like the result, but not necessarily the way I get there. Imagine cleaning Lady Liberty with a toothbrush. The result might look perfect, but it would still be a painMackemX said:again you said the result is perfect
And again this sounds as if I was a complete idiot though the mistake is on the side of DS and not on mine (again). I'm adapting to an instable tool chain, that's something completely different than learning by mistakes.All of your 3 issues can be answered if you just read the guides or the forums but it looks like you are still missing vital information regarding information and basically are learning by your mistakes
Interesting though not very helpful. Doesn't change the fact that I need to analyze with DVDShrink however.1. Numerous people have had this issue and some have used different players and all is fine. I myself have played items I could not see yet others could but I blame my setup not the dvd player. This is one thread HERE
It's not that DS came up with an error because I left WinDVD open. The message box appeared as I _closed_ WinDVD. Usually WinDVD doesn't block read access to the VOBs.2. Sadly DS does not close the player but I have always recommended you close the player BEFORE processing. If a VOB is being used, how can it be modified?, therefore the user must manually close the player. I have just checked the htm guide and it's actually missing but it was in the PDF guide Make sure you CLOSE the DVD PLAYER before clicking Process. It will be corrected as soon as possible but you are the 1st to mention this (good spot)
I mean I can live with it, if you tell me "it is like it is". This is probably an issue of some kind of remote control over IfoEdit as there is no direct interface, right? However my PC is definitely not the limit, it's just that the constant popping up hinders me from doing anything serious.3. If you read the www.DVDStripper.com page it states:
You must be willing to allow control of the PC to Ifoedit while it is updating the IFO's which can take anything upto 15 minutes or so depending on your setup. You can still use the PC but you risk upsetting the process but after a few runs you will soon learn the limits of your PC
I'm sure I will soon be able to work around the instabilities of the DS tool chain. There are however no simple answers/solutions as you have to admit. You should also be aware that this way of treating these issues will not improve the stability or mass compatibility of DS.I am quite willing to tell you all the answers to your issues if it will help you on your way to fully understanding how DS works. Most issues have already been discussed or have the simplest of solutions so I would appreciate if you would take the time to hopefully get a better understanding of how the whole process works
but feel free to raise anything you are uncertain about or have issues with as I'm sure there will be a simple answer
cheers
#1. the simple fact is all the 3 errors you experienced are user inflicted (1 unwittingly). OK you did not know that you could leave the player running and that is all down to a simple typo. If a VOB is playing it cannot be modified no matter what and therefore will undoubtedly cause problems0xdeadbeef said:#1.And again there is a "but" (or in this case a "however"). I'm not sure what's confusing about this: I like the result, but not necessarily the way I get there. Imagine cleaning Lady Liberty with a toothbrush. The result might look perfect, but it would still be a pain
#2.And again this sounds as if I was a complete idiot though the mistake is on the side of DS and not on mine (again). I'm adapting to an instable tool chain, that's something completely different than learning by mistakes.
#3.Interesting though not very helpful. Doesn't change the fact that I need to analyze with DVDShrink however.
#4. not that DS came up with an error because I left WinDVD open. The message box appeared as I _closed_ WinDVD. Usually WinDVD doesn't block read access to the VOBs.
Besides, this recommendation is not part of the DVDStripper Guide and it's a bit optimistic to expect that I read each and every posting you made on this board or elsewhere.
#5. I mean I can live with it, if you tell me "it is like it is". This is probably an issue of some kind of remote control over IfoEdit as there is no direct interface, right? However my PC is definitely not the limit, it's just that the constant popping up hinders me from doing anything serious.
No chance of getting the author of IfoEdit to implement a real interface (maybe with some bribing? )?
#6. I'm sure I will soon be able to work around the instabilities of the DS tool chain. There are however no simple answers/solutions as you have to admit. You should also be aware that this way of treating these issues will not improve the stability or mass compatibility of DS.
I'm not sure what you mean as most issues you have raised do have simple solutions or have I missed something? . We are fully aware of most issues and the ones of main concern will be addressed first. Most users of DS will agree that this is the best way forward0xdeadbeef said:I'm sure I will soon be able to work around the instabilities of the DS tool chain. There are however no simple answers/solutions as you have to admit. You should also be aware that this way of treating these issues will not improve the stability or mass compatibility of DS.