A bug in ReAuthorist ?

[p4t0z3u]

Hi, and thanks for trying to help me.

I'm trying to backup the Hulk movie.
Here is my problem (as well as for the X-Men 2 movie, the 25th hour): I have my main movie within DIF4U that lengths for 2h12m...

http://www.m4el.org/pic/1.jpg

I have a duplicate PGC for this VTS (which IS NOT MY PROBLEM, I've been through other posts to resolve that problem) but when DIF4U finishes its work, and launches RA, i can only see a 15 frames-long movie within my PGC window :eek: !

http://www.m4el.org/pic/2.jpg

I've already used that method many times (on episodic dvds), but can someone explain what i did / didn't do that get that 15 frames (00:00:00:15) for the movie ?
Obviously, RA detects this as an extra and encodes @ my extras bitrate (which i change from DoCCE4U).

So far, i couldn't find what was the cause of all this. Has someone ever encountered that problem ?

Thanks.
If this problem seems to have already been treated within this forum, please tell me where because i've been though it and couldn't find anything related to this.

p4t0z3u

[Eyes`Only]

that occurs when RA couldn't read the .avs. Did you recently change your version of avisynth?

[arlsair]

Or did you use the DVD2AVIdg/Mpeg2Dec3dg ?

[p4t0z3u]

Eyes`only:

I indeed changed my AviSynth version to switch to 2.5.3 (i had 2.5.2) after i backed up some dvds.

What is very strange though is that only the main movies VTSs seem to be touched by this problem.
For the same movie but another VTS (that lenghts 22 mns), I don't have this problem.

I also tried to change to a more recent AviSynth version (2.5.4) but the problem was the same.
I think i should try with an older version to see if i'm still stuck with this problem.

Or else, do you have another solution in mind ?

arlsair:

I downloaded these special versions from http://neuron2.net/fixd2v/decodefix.html. I'm now running tests to see if these versions will make it.

I keep you informed.

Thanks a lot.

[Eyes`Only]

Ahh that explains it. DVD2AVIdg's .d2v files won't work with RA in it's current state. It is coded to only read older .d2v files properly.

In beta version 1.4.1 I added a subroutine that actually goes into the .d2v files and tweaks them so that they work with RA, and implemented full DVD2AVIdg compatibility along with a button to use DVD2AVIdg if you choose (all files included).

VIP users have been using the newest builds (1.4.4 now, see the revision history on my site for all the other additions/changes) and have been testing the dvd2avidg integration and report that it works perfectly now.

[p4t0z3u]

Here are the results:

Actually, it seems that the problem of all this comes from the AviSynth/DVD2AVi duet.

I turned back to a 2.5.2 version and the DVD2AVI version that came along with RA. I'm now re-ripping the whole thing to see the changes.

Hey man, are you trying to get my bucks ? :eek:

In fact, your hard work deserves them i would say.

You may find me soon in the ViP section :p

Thanks again for helping, it seems that my post wasn't that useless actually.

[Eyes`Only]

Originally posted by p4t0z3u
I turned back to a 2.5.2 version and the DVD2AVI version that came along with RA. I'm now re-ripping the whole thing to see the changes.Unneccessary, 2.5.3 and 2.5.4 are fine, it's just the .d2v file that's the issue.

Originally posted by p4t0z3u
Hey man, are you trying to get my bucks ? :eek:
In fact, your hard work deserves them i would say.Of course, I'd love to increase donations, but I was also pointing out the benefits that VIP members are experiencing, and the fact that it's already working without issues in the betas :D

You may find me soon in the ViP section :pLooking forward to it!

[p4t0z3u]

In fact, i just realised that you thought i was using DVD2AVIdg and MPEG2DECdg.

I do not !

I'm just using all the tools coming along by default with ReAuthorist and DoItFast4U!

That is really where the strange part is.
Do i have any chance to find the light.

:confused:

[Eyes`Only]

no idea. now i'm confused :(

[p4t0z3u]

It seems that i've found the slution to my problem.

The partition i was using for my destination folder was a FAT32 type !

The moment i switched the demuxing to a NTFS type, the problem was solved :eek: :confused: !

So it may be the same for other people, but in the future, really warn pepople about that fact ("Warning: it seems that some lamahs using a FAT32 partition their destination folder partition had problems with DIF4U!. Change to NTFS in order to see is this solves the problem").

Anyway, thanks for trying to help me. ;)

p4t0z3u.

[Eyes`Only]

Hmm.. please don't go around spreading that rumor. I know for a fact that I have coded DoItFast4U! to work fully even with FAT32 partitions. However, ReAuthorist may not be... but my app IS!

[p4t0z3u]

Hey Eyes`Only, do not misunderstand please ! :(

I never said that your software was the cause of this problem !
I even hardly see how it could be. I just think that it may be a windows/RA problem.

The funny thing is that i asked a friend of mine if i could use his PC for testing the whole Big3 method. (he didn't have any of these apps installed on his computer)
It just happens that the result was exactly the same ! (i mean 15 frames movie). Now i just have to check again for partition type on his PC.

I will run further tests and conditions (partition type, etc...) to see where this problem could come from.

And again, i'm grateful for your work, don't ever think the contrary. You just did a great work. :D

Furthermore, what language did you use to code your piece of software ?

Thanks again.

p4t0z3u

[Eyes`Only]

Don't get me wrong, I wasn't upset or anything, just pointing out that personally took a LOT of time to make my app work with FAT32 (It wasn't quick nor easy!). The .d2vs and .avs files from DoItFast4U! are perfectly correct even if you demux from a FAT32 partition.

Also, I can definitely tell you that it's not a Windows issue, since I have it working just fine in my app. It's something the author of RA just didn't take into consideration I guess when he coded RA. :(

My entire app is coded in Visual C++ 6, using little third-party classes (only CListboxST and CXPStyleButtons). I even wrote the entire IFO parsing portion by hand myself. Which may or may not be a good thing :D

Credit must be given to Aquabubble and BBWoof for their coding help/lessons during this project!

[redbaron2]

hi,

i had this problem too, the problem is that when dvd-decrypter demuxes the videostream, and this stream is larger then 4 gig, it splits at 4 gig and there are 2 video-files in the avs-script, which reauthorist doesn't recognise. maybe this could be fixed in a future version. but of course you can expect that users convert to ntfs to solve the problem ;-)

[Eyes`Only]

There shouldn't be 2 video files in the AVS script. Instead, there should be one .d2v file. In other words, AVS scripts will look no different in FAT32 vs. NTFS.

The problem is that in the .d2v file, all parts of the demuxed .m2v (filename_1.m2v, filename_2.m2v) are referenced. ReAuthorist parses the .d2v file by itself to determine certain bits of data, and it seems to only work with standard .d2v files from the 1.76 CLI version of DVD2AVI. This is why I had to write the code that is currently in the betas to convert the d2v so that DVD2AVIdg could be used and ReAuthorist would still work. Unfortunately, it's not possible for me to alter .d2v files from a FAT32 partition that reference 2 .m2v files to work, because the resulting AVS script that references those .m2vs would then only see one.

[Trahald]

honestly, unless your running win98, there isnt a real compelling reason to run fat32. the MFT generally takes up the same amount of space as the FAT by the time the drive is near full. (factoring in lost space on small files in a fat partition that you gain with a ntfs partition)

i used to feel comforted that i could always access fat32 with a dos boot disk where as with ntfs there really isnt an option. however, ive never had it be an issue since. i suffered way more corruption in fat partitions, where as no issues with ntfs(except for 100% hd failures which were just maxtors fault) . you can convert freely to ntfs and then back to fat32 (with partition magic as long as you dont use encryption or compression) just back up your stuff first obviously.