Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
20th May 2014, 22:18 | #20321 | Link | |
Moderator
Join Date: Oct 2001
Posts: 20,973
|
Quote:
As always... I'm not positive which is worse, viruses or anti-virus software. They both prevent your computer from working they way it should. I keep mine disabled most of the time. Not only are they always interfering with other software -- they also slow your system down to a crawl. Last edited by jdobbs; 20th May 2014 at 22:31. |
|
20th May 2014, 23:01 | #20322 | Link | |
Registered User
Join Date: Aug 2006
Posts: 164
|
Quote:
Thanks for taking the time to respond. Feel much better, I will make sure I get it from Doom9. G! |
|
21st May 2014, 03:47 | #20324 | Link | |
Registered User
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
|
Quote:
Jdobbs, try to get working but no go in this case.
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it. |
|
21st May 2014, 07:36 | #20325 | Link |
Registered User
Join Date: Aug 2005
Posts: 1,100
|
Chapter stops disabled...
Mr. Dobbs,
I recently used BDRB to import 3 Blu-ray folders and create one playable disc, which worked perfectly fine. But, for some odd reason, in playing back the resulting disc, only one of the 3 movies allowed me to use chapter stops; the other 2 would not. Is there anything that BDRB would do while importing that would somehow remove the chapter functionality, or do you think that that would more likely have been caused by TSMuxer which I used to create the Blu-ray folders before importing? This was really odd, because in using TSMuxer hundreds of times, this was the very first time ever that I had seen ANY Blu-ray created that would not allow chapter stops on playback. Thank you JDobbs! |
21st May 2014, 14:12 | #20326 | Link |
Guest
Join Date: Jan 2002
Posts: 21,901
|
@Lathe
This appears to be a crosspost of an issue you raised in another thread. http://forum.doom9.org/showthread.php?t=170644 Therefore, I ask you again: What is your source file please? An original bluray disk? Why do you need TSMuxer? Note that crossposts can incur strikes. I recommend that you carefully read and follow our forum rules. Last edited by Guest; 21st May 2014 at 14:18. |
21st May 2014, 22:19 | #20327 | Link | |
Moderator
Join Date: Oct 2001
Posts: 20,973
|
Quote:
|
|
22nd May 2014, 02:56 | #20328 | Link | |
Registered User
Join Date: Aug 2005
Posts: 1,100
|
Quote:
Thanks! |
|
23rd May 2014, 18:43 | #20329 | Link |
Registered User
Join Date: Jul 2009
Posts: 15
|
Quick rant
I have been using BD-Rebuilder to make backups of my Blu-ray collection for years so I am not a complete novice. Having said that, trying to backup a 3D movie has become way to complicated for my feeble brain. Do I need to modify the ini file when using the latest build or do the automatic settings work "as is"? What are the correct settings anyway? I have tried to configure the settings but it takes 15 hrs. to complete a trial run. That's too long to find out the encode has failed in some way. (so I just abort each attempt).
I have an old i7 processor. Can I enable Quick Sync and how exactly do I do that? I am not lazy. I have read hundreds of posts, but I cannot figure out what the current "working" configuration is. If someone could just post step by step instructions on how to back up 3D movies for dummies like me, I would be truly grateful and I bet alot of other people would be grateful as well. Before ending this quick rant I would like acknowledge the great work that JDobbs has done over the years to develop this software. I am not complaining, I appreciate having this software....just a little frustrated right now that I can't figure this out on my own. |
23rd May 2014, 20:19 | #20330 | Link | |
Moderator
Join Date: Oct 2001
Posts: 20,973
|
Quote:
But... it does take quite a bit longer since you can't use X264 for the encoding. You are also encoding twice as many frames (left and right views). If you have an older processor it is unlikely you have quick-sync. Last edited by jdobbs; 23rd May 2014 at 20:23. |
|
24th May 2014, 00:33 | #20331 | Link | |
Registered User
Join Date: Feb 2009
Location: Toronto, Ontario, Canada
Posts: 1,059
|
Quote:
__________________
If you fail to plan; you plan to fail, would you not agree? Think about it. |
|
24th May 2014, 09:14 | #20333 | Link | |
Registered User
Join Date: Jan 2010
Posts: 40
|
Quote:
I have only recently started playing with the import feature, so I'm not sure I really know what I'm doing. But, as a test, a tried to import an MKV file that is 1912x1072, using BDRB version 47.06. The resulting output is just a gray screen. Further digging led me to look at the pseudo BD created during the process, prior to backup and re-encode. Looking at the stream created from the MKV, for some reason, it is converted to 720x480. It plays fine, it's just small. Then when the re-encode takes place, BDRB thinks it's 1280x720. I believe this is where the fail occurs and the result is the gray screen. Since tsmuxer was mentioned earlier, I back-revved it to a different version I had on my system from Aug of last year. (1.10.6) Using that version, the pseudo BD has a stream from the MKV that is now 1912x1072. It also plays fine, and is now the same size as the original. Wondering if it had something to do with the slightly off resolution of the input file, I have tried with several different MKV files, of varying resolutions, and it always makes them 720x480. However, when I used a MKV file create by BDRB from a blu-ray source, that is exactly 1920x1080, the intermediate step creating the pseudo BD works fine, and I get a stream that is 1920x1080. I then tried a video shot with my DSLR, which is 1920x1080, and it works fine also in spite of being an odd .mts file, and the BD created from it also plays fine, no grey screen. So it would seem there is some oddity with the 2.6.12 version of tsmuxer included with the 47.06 build. It seems to resize the video, if it isn't 1920x1080, while creating the pseudo BD structure. And that resize seems to cause the re-encode to fail with a gray screen. I don't have any 1280x720 sized MKVs readily available to test if they import ok, or any slightly off sized ones in the same 720 range. So I can't say if that has an issue or not. |
|
24th May 2014, 12:12 | #20334 | Link |
Guest
Join Date: Jan 2002
Posts: 21,901
|
@Chuckwagon
Where do you get these MKV files? And did you not see jdobb's statement: "I'm sorry, but please review the thread and the criteria for bug reporting. I don't accept bug reports on preprocessed sources. Experience has proven that almost ALL reports using preprocessed sources were shown to have issues before being presented to BD-RB for backup." |
24th May 2014, 13:31 | #20335 | Link | |
Registered User
Join Date: May 2014
Posts: 4
|
Quote:
It seems either tsmuxer or MKVToolNix(or both) cut/add something from/to the elementary stream, so that after making a MKV out of AVCHD muxed m2ts source, there is seeking problem in software players(mpc-hc). So I'm staying with old version for now, until I figure the cause. Also MediaInfo does not show 'Writing library' & 'Encoding settings' entries in Video section anymore... Someone know why this is? (I liked being able to see x264 version & settings) Gesendet von meinem Nexus 7 mit Tapatalk |
|
24th May 2014, 16:26 | #20336 | Link | |
Moderator
Join Date: Oct 2001
Posts: 20,973
|
Quote:
But... why on earth would anyone create a source that is 1912x1072? That's just silly. I could understand 1920x1072 (to remove an upper/lower border). I could understand 1912x1080 (to remove a left/right border)... but when would you ever need to create something that is that far from any kind of standard? [Edit] I just looked at the code, and it will add borders to the top/bottom and left/right to make the source 1920x1080. I see no possible way that it will be resized to 720x480/576 unless you have checked an alternate output of that size (told it to do so). Last edited by jdobbs; 24th May 2014 at 16:38. |
|
24th May 2014, 22:53 | #20337 | Link | |
Registered User
Join Date: Jan 2010
Posts: 40
|
Quote:
All of my MKVs are created by BDRB, and I haven't had a problem with them. But since I was just playing around with this, and I thought resolution might have an impact, I grabbed a bunch of MKVs off the net, and ended up with several different resolutions. I'd bet anyone running into this issue has odd sized files, for whatever reason. When the files are "normal" resolutions there doesn't seem to be any trouble. The 2.6.12 version of tsmuxer seems to dislike the odd sized files, but the older tsmuxer doesn't. Why I couldn't say. I didn't think you did any resizing until the final re-encode. I assumed tmuxer would just grab the video as is and put it into the pseudo BD structure without making adjustments, and any resizing would be done as part of the re-encode. But that isn't how it's working with the 2.6.12 version. The process goes far too fast for it to be encoding the files, so is there some way for tsmuxer to just alter the res? Is tsmuxer supposed to resize when extracting to the pseudo structure, or is that an unexpected behavior? In any case, there's an easy work around. The older version of tsmuxer did complete an import of 7 of these 1912x1072 resolution MKVs, each around 2GB, and BDRB created an ISO with them and they all play nicely. So, if someone hits this, they can use the older tsmuxer to get around it. Though I have also encountered files that encode the video fine, but pork the audio. So clearly it's best to use well conforming sources in the first place. But folks don't often do what's best. So, for future reference, next time someone has a gray screen issue, maybe it's from this. Cheers, Last edited by Chuckwagon; 24th May 2014 at 22:58. |
|
24th May 2014, 23:01 | #20338 | Link | |
Moderator
Join Date: Oct 2001
Posts: 20,973
|
Quote:
|
|
24th May 2014, 23:01 | #20339 | Link | |
Moderator
Join Date: Oct 2001
Posts: 20,973
|
Quote:
It would make sense that TSMUXER might have issues importing odd resolutions. It has to determine how to set the parameters in the MPLS and CLPI files (and they are limited to legal BD resolutions). I'm guessing these files are just to weird for it. Last edited by jdobbs; 24th May 2014 at 23:04. |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|