Experiencing Difficulty Using DVD RB and CCE? If So, Then Ask Your Questions Here.
|
|
Staff Member
2 product reviews
|
7. August 2004 @ 12:22 |
Link to this message
|
Edited to remove some unproductive crap
This message has been edited since posting. Last time this message was edited on 7. August 2004 @ 18:26
|
Advertisement
|
|
|
64026402
Senior Member
|
7. August 2004 @ 13:43 |
Link to this message
|
Happyuser
I have read your posts as well as Vurbals and Sophocles and jdobbs.
It was made apparent to me that deinterlacing is not a way to improve the quality of a DVD backup.
Why do you keep posting in a thread dedicated to helping improve backup quality when you have no such recommendations.
Do you not yet understand what you are doing?
Try reading all of the posts again. If I can figure it out by reading them you should be able to also.
Thanks Vurbal, Sophocles, and jdobbs.
Your posts have been very educational in this arguement.
Donald
|
jdobbs
Senior Member
|
7. August 2004 @ 13:44 |
Link to this message
|
Quote: In DVD-Rebuilder, if I disable "Interlaced" for a particular VTS-set, this DVD-Rebuilder will encode all the AVSs ( segments ) in this VTS-set as Progressive, no matter what these AVSs ( segments ) maybe be pure interlaced or not. So pure interlaced AVSs ( segments ) are being encoded as Progressive.
That feature isn't meant for NTSC. There are some PAL sources that are reported to be actually Progressive -- but were encoded as interlaced. I added that option as the result of a request from a PAL user. If you want to use it, go for it. But I want to make it clear to anyone else reading -- it is my opinion that converting interlaced to Progressive is a very bad idea.
|
AfterDawn Addict
1 product review
|
7. August 2004 @ 14:54 |
Link to this message
|
Just keeping it clean.
" Please Read!!! Post your questions only in This Thread or they will go unanswered:
Help with development of BD RB: Donations at: http://www.jdobbs.com/.
This message has been edited since posting. Last time this message was edited on 7. August 2004 @ 16:36
|
happyuser
Suspended permanently
|
7. August 2004 @ 14:55 |
Link to this message
|
jdobbs
Your advice is very helpful to me. I want to teach others on how to use this DVD-Rebuilder. So I have to learn thoughly this DVD-Rebuilder: even the bad way to handle encoding procedures. Please allow me to say a few things about the 29.976 fps ( interlaced ) ==> 23.976 fps interlaced encoding as follows:
64026402 and others.
In DVD-Rebuilder, somehow, all the AVSs ( video segments ) being fed into CCE at 23.976 fps: what this means is CCE will encode these at 23.976 fps. After the encoding process has completed, the reauthoring engine in DVD-Rebuilder will "Flagged" ( add pull down or other methods ) to bring these AVSs ( video segments ) back to its original state.
Even the Progressive 23.976 FILM will be added pulldown and the result will be interlaced to the DVD player that will display this onto the TV.
And so, if I CORRECTLY deinterlace those pure interlaced ( 23.976 fps ) AVSs ( video segments ) and then encode them as Progressive at 23.976 fps, the pulldowns that are applied to these AVSs after the encoding process will bring them back into the state of interlaced as the dvd player will see them as such.
Besides, you have already lost 6 frames ( 29.976 - 23.976 = 6 ) per second before the CCE has a chance to encode these pure interlaced segments, then why not take advantage of the Progressive 23.976 fps specification to encode these pure interlaced as Progressive to take advantage of the Progressive ENCODING instead of the interlaced encoding. We all know that Progressive encoding is more efficient than interlaced encoding.
According to DVD and video specification, pure NTSC interlaced are 29.976 fps ( and within one frame, there are two fields ). DVD-Rebuilder had already truncated 6 frames out of the original 29.976 frames: and this is a 6 frames lost before feeding into the CCE encoding engine.
You used to hear people saying that:
1. 29.976 fps NTSC interlaced ( pure interlaced ).
2. 29.976 fps NTSC Progressive FILM ( 23.976 Progressive film being telecined into 29.976 fps ).
3. 25 fps ( PAL ) either interlaced or Progressive.
Up until the presence of this DVD-Rebuilder, you have the new term and this new term is 23.976 fps interlaced.
You had already lost six frames per second: then why not take this opportunity of the standard specification of 23.976 Progressive film to encode these pure interlaced 23.976 into Progressive 23.976 fps. Unless this will be a problem if the DVD-Rebuilder can not add the proper "FLAGS" for a Progressive 23.976 back into the interlaced state.
|
AfterDawn Addict
1 product review
|
7. August 2004 @ 14:57 |
Link to this message
|
happyuser
You can't teach anyone because no one will listen to you anymore. You've proven yourself to be anything but a teacher. If you'd been more considerate then you would have been welcomed whether you are wrong or right but you chose instead to try and subdue us by calling us down.
_
_
" Please Read!!! Post your questions only in This Thread or they will go unanswered:
Help with development of BD RB: Donations at: http://www.jdobbs.com/.
This message has been edited since posting. Last time this message was edited on 7. August 2004 @ 15:09
|
Staff Member
2 product reviews
|
7. August 2004 @ 15:08 |
Link to this message
|
According to jdobbs (on this very thread last night):
Quote: Don't worry about the frame rate. DVD-RB always sets the NTSC rate to 23.976 when it goes through CCE -- that's just part of the method and its necessary. The frame rate will be reset correctly during rebuild.
This message has been edited since posting. Last time this message was edited on 7. August 2004 @ 15:09
|
happyuser
Suspended permanently
|
7. August 2004 @ 15:10 |
Link to this message
|
Sophocles, you dishonsty !
Your childish behavior only offends other people.
Look into your conscience and see if you have been an enough responsible person.
Sophocles
I rather be "loud mouth" and "ignorant" than be not knowing anything about specifications and video encodings and even about this DVD-Rebuilder like you had been and are.
|
happyuser
Suspended permanently
|
7. August 2004 @ 15:16 |
Link to this message
|
vurbal and jdobbs
As I had already said, this DVD-Rebuilder truncated six ( 6 ) frames out of the original 29.976 frames per second before feeding the new 23.976 fps into CCE. If you have already lost six ( 6 ) frames per second, then why not take advantage of the standard video specification of 23.976 Progressive film to encode these new ( pure interlaced ) 23.976 fps as Progressive after properly deinterlacing them.
|
Staff Member
2 product reviews
|
7. August 2004 @ 15:17 |
Link to this message
|
You've said lots of things. You just haven't proven anything. I'd be willing to bet you won't get around to it before getting banned either.
|
AfterDawn Addict
1 product review
|
7. August 2004 @ 15:34 |
Link to this message
|
wasted space!
" Please Read!!! Post your questions only in This Thread or they will go unanswered:
Help with development of BD RB: Donations at: http://www.jdobbs.com/.
This message has been edited since posting. Last time this message was edited on 7. August 2004 @ 16:35
|
Senior Member
|
7. August 2004 @ 16:01 |
Link to this message
|
I'm going to try to move this along ... as I can't possibly see where happyuser has anything of substance to add at this point. IMO, all I see now is an effort to have the last word...
So, moving along, I'd like to get some clarification on the Batch feature of Rebuilder...which is quite nice. I ran 3 consecutive files. Each had a separate source and working path folder. RB gave each project a .rbd file extension, and I placed these 3 .rbd's in a folder I named Batch. All 3 movies processed without error. After all was done, only the last movie had any files in its designated working path folder.
QUESTION: I am wondering if each working path folder needs to have its own separate directory folder in order to make batch processing work?
This message has been edited since posting. Last time this message was edited on 7. August 2004 @ 16:03
|
Staff Member
2 product reviews
|
7. August 2004 @ 16:07 |
Link to this message
|
I'm not sure if I'm following you. Do you use a single common folder for your working path (ie all projects use C:\Working or something like that)? If so, then yeah that's you're problem. You'd have to change it to something like C:\Working\Movie1, C:\Working\Movie2, etc,... Otherwise each new encode will just overwrite the previous one.
|
happyuser
Suspended permanently
|
7. August 2004 @ 16:15 |
Link to this message
|
Sophocles
Your still childish behavior only make people more offending.
Or maybe your inferior knowledge level about the subject being discuss makes you jealous of other people.
|
Senior Member
|
7. August 2004 @ 16:16 |
Link to this message
|
As I said...he's gotta get the last word...
Anyway, for a working path file, I create folders with a shorthand name of the movie and essentially a note of what is in it.
Source: C:\Ben-DeC, Cool-DeC, Romeo-DeC
Working: D:\Ben-cce, Cool-cce, Romeo-cce
Batch file: C:\Batch
As you can see, each movie had a corresponding working path folder. All 3 .drb file extensions went into the same Batch folder, however. Then I launched the app.
This message has been edited since posting. Last time this message was edited on 7. August 2004 @ 16:24
|
Staff Member
2 product reviews
|
7. August 2004 @ 16:26 |
Link to this message
|
Hmmm, that doesn't seem right. Unfortunately I can't help you much there since I use RBFarm for all my encodes, partly because it has its own batch capabilities.
|
Senior Member
|
7. August 2004 @ 16:29 |
Link to this message
|
Thanks. I'll play with it some more.
|
jdobbs
Senior Member
|
7. August 2004 @ 17:15 |
Link to this message
|
@happyuser
Quote: As I had already said, this DVD-Rebuilder truncated six ( 6 ) frames out of the original 29.976 frames per second before feeding the new 23.976 fps into CCE. If you have already lost six ( 6 ) frames per second, then why not take advantage of the standard video specification of 23.976 Progressive film to encode these new ( pure interlaced ) 23.976 fps as Progressive after properly deinterlacing them.
Quote: Even the Progressive 23.976 FILM will be added pulldown and the result will be interlaced to the DVD player that will display this onto the TV.
And so, if I CORRECTLY deinterlace those pure interlaced ( 23.976 fps ) AVSs ( video segments ) and then encode them as Progressive at 23.976 fps, the pulldowns that are applied to these AVSs after the encoding process will bring them back into the state of interlaced as the dvd player will see them as such.
Your really need to listen more carefully and get your facts straight. Pretty much everything you've said here is incorrect. DVD-RB never truncates anything. The total number of frames stays the same. Also, if a source is interlaced it is encoded as interlaced at 23.976 fps. Encoding at 23.976 does not imply progressive.
I don't care who gets the last word -- but I also don't want these types of fallacies perpetuated.
I am very confident I know what I'm talking about and I am intimately familiar with the standards as I have them on a shelf before me.
This message has been edited since posting. Last time this message was edited on 7. August 2004 @ 17:32
|
64026402
Senior Member
|
7. August 2004 @ 17:18 |
Link to this message
|
I thought you needed seperate folders in batch mode or else the last movie would be the only one to survive. I think jdobbs referenced this some posts back.
Donald
|
jdobbs
Senior Member
|
7. August 2004 @ 17:20 |
Link to this message
|
@Doc409
Quote: QUESTION: I am wondering if each working path folder needs to have its own separate directory folder in order to make batch processing work?
Before saving the project files, make sure the output directory is unique for each project. Before DVD-RB processes a unit, it clears the specified output directory.
This message has been edited since posting. Last time this message was edited on 7. August 2004 @ 17:20
|
64026402
Senior Member
|
7. August 2004 @ 17:24 |
Link to this message
|
jdobbs
I was confused about the frame rate previously but your explanation was clear. I don't undestand why happygilmore doesn't just admit he's wrong and go away.
Rebuilder has been working flawlessly for me.
Thanks.
Donald
|
AfterDawn Addict
1 product review
|
7. August 2004 @ 17:35 |
Link to this message
|
jdobbs
Am I ever glad you guys posted the information regarding batch mode, because I was preparing one tonight, my first, and I might have selected a single folder for my files.
" Please Read!!! Post your questions only in This Thread or they will go unanswered:
Help with development of BD RB: Donations at: http://www.jdobbs.com/.
This message has been edited since posting. Last time this message was edited on 7. August 2004 @ 17:36
|
Moderator
|
7. August 2004 @ 17:44 |
Link to this message
|
happyuser - Quote: I rather be "loud mouth" and "ignorant" than be not knowing anything about specifications and video encodings
are you kidding me, you'd rather know about video encoding than be known as a loudmouth or ignorant??
I dont know the first thing about video encoding but from what I can see, you're an idiot and very inconsiderate of others who are only here to help. I've had 2 senior members request you be banned and thats good enough for me. buh bye.
http://www.Lonero.net - friend of the forums, great guitar player
#afterdawn (well i have no idea where it is anymore)
|
64026402
Senior Member
|
7. August 2004 @ 17:53 |
Link to this message
|
Party time:)
Donald
|
Advertisement
|
|
|
jdobbs
Senior Member
|
7. August 2004 @ 18:08 |
Link to this message
|
@sophocles
Quote: Am I ever glad you guys posted the information regarding batch mode, because I was preparing one tonight, my first, and I might have selected a single folder for my files.
I'd like to say I've learned this lesson from experience... but since I still forget sometimes (and I wrote the code) "learned" probably wouldn't be accurate.
|