I definately think it's time for one maybe a sub-forum along w/ the nero, shrink, and similar all chat could have they're own sub-forum as well as several other "topics" this site is definately having growing pains and I think this would make ppl do searches and at least think about they're question a little longer and maybe just maybe post it in the right forum because every body here has there own talents and would feel better about helping ppl if it was easier to fink the ppl you could help!!!
Well... if Nero, DVD2One, Shrink, and ratDVD can have their own sections, then I think DVD-RB is a worthy candidate for it's own. The app has proven it's merit as one of the premiere encoding tools available. It's made some difficult encoding tools usable by beginners and offers quality second to none. The help thread for DVD-RB has run over a hundred pages and it's a constant complaint that it's difficult to search. By no means should anyone contemplate ending that thread as it is well known for the help it gives to RB users. However, I feel it would be better housed in an RB section. As RB is useful with apps besides CCE, there could be a few other threads devoted to the RB app and different encoders instead of all in one thread.
@brobear, I agree completely. I use Rebuilder Pro/CCE Basic as my #1 back-up software, yet I have also used each of the Free encoders and the Rejig transcoder. For those who want free...Rebuilder with HC or QuEnc is fantastic. People really need to know just how powerful this prog. really is and also how easy it is to use it (once it is set up properly). I believe many will contribute to this new Rebuilder option and be able to navigate to find what they need. MovieDud
If there is enough support for it, maybe the staff will create a new section. As it now stands, I think it is doing the members a disservice not giving RB its own section. jdobbs has taken RB from a basic encoder app to a multifunction program that now supports a burner and gives options on file types, along with increasing editing capabilities and increased control for setting up personal preferences. All in all RB has developed into a very powerful encoding app with a wide variety of options. Hopefully CopyToDVD and Nero will be supported soon (shameless plug for favorite burners to be included). So, [bold]everyone should speak up if they would like to see Rebuilder have a section of its own. Would it be asking too much for the staff to see the need without a mass outpouring of support and add the needed section because it's the right thing to do?[/bold]
thnx drd now we have to get topics started for each of the encoders, filters, dot&deen but the new forum is a big step in the right direction!!thnx for giving us a home of our own
Thanks to dRD for the quick action. Goes to show why AD is such a good forum. Something needs doing and it gets done. Guess there's little need for this thread now, except as a thank you area. Thanks also go to L8nights for bringing up the suggestion.
That's up to the mods, tidying up that is. Luckily I don't have the responsibility; I just get to post in the various sections, not control them.
Has anyone ever tried using rebuilder (pro or free) on a 2hr. TV episode? I estimated it would take me about 36 hours just to do the Phase II encoding.
RB with one of the supported encoders has no problem compressing a 2 hr movie. The input files have to already be in DVD format for the job to be done with RB. So the job entails the RB compression time plus the time you need to convert the captured files to the right format. The purpose of RB is to encode (compress) DVD9 size files around 8GB to fit the DVD5 media, 4.37 GB. It's not for converting files.
discussion on this question has been started here but no further answers provided http://forum.digital-digest.com/showthread.php?t=55702
Decent questions there UncasMS. When they mention phase II processing, are they referring to the encode process of RB with the input files already loaded and through the Prepare stage? I've always heard that referred to as just encode or step or stage, I guess phase works. Something is sure off for the times to be that slow. First I'd take a look at the DMA settings. If all was alright there, I'd run a comparison using a freebie like Shrink or one of the trials such as CloneDVD2 or DVDCopy4 from InterVideo. Both are full function trials. As long as the input files are DVD compliant, the transcoders should do the task. That will show if the problem is software related or a problem with the system itself. Nictoe For use with the RB, you're better off using the HC encoder or the CCE. CCE is the quickest of the lot so far if time is an issue. Running 2 passes with an average PC takes about 2 to 3 hours normally. So, the extended encoding time mentioned (if already in RB processing) indicates something is seriously off.
Nothing more to do at this point until someone says they've done something. As you say, we're waiting for input.
Well, my 'average pc' is a HP 1.6 ghz p4, and it took 10 hours to encode the 4 hour movie with 2 pass CCE. I have to admit, there hardly was any difference at all in the movie quality as compared to DVD Shrink. Then again, you really can't expect miracles with a 52% DVD compression to begin with. Still I wonder why the scripts couldn't at least use MP2 audio to reduce compression even further.As for ProCoder 2, having a hyperthreaded multi-proccessor system, would be the way to go. But of course, I'm waiting for the Blu-ray systems to come out.
How long did it take with DVD Shrink or one of the other transcoders I suggested? Or did you not want to try the comparison? UncasMS and I both consider the time to be a bit long, even for a smaller processor. You're not trying to do any multitasking during the encode are you? Before you do anything further, I'd suggest checking the DMA settings for the drives. If okay, then try Shrink using the "Quality Settings" and let us know how that turns out. Who knows, you may just have an exceptionally slow system.
that's absolutely fine and 10hrs for your 4hr title is ok, too there must have been something wrong with the procoder encoding but your latest details give no reason for worries