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.

 

Go Back   Doom9's Forum > (HD) DVD, Blu-ray & (S)VCD > DVD & BD Rebuilder

Reply
 
Thread Tools Search this Thread Display Modes
Old 10th June 2012, 02:05   #15221  |  Link
jdobbs
Moderator
 
Join Date: Oct 2001
Posts: 20,973
Quote:
Originally Posted by dfsooner View Post
I re-ripped the disc and still got the same error. I'm trying to get hold of another copy of the disc. I'll rip it using a different drive (& manufacturer) and see if I get the same problem.

In the meantime I've pulled out the offending LPCM audio track, run BDRB and muxed the audio back in and it seems to work ok.
What did you use to pull the audio?
__________________
Help with development of new apps: Donations.
Website: www.jdobbs.net
jdobbs is offline   Reply With Quote
Old 10th June 2012, 06:00   #15222  |  Link
dfsooner
Registered User
 
Join Date: Nov 2009
Location: North Las Vegas, NV
Posts: 112
Quote:
Originally Posted by jdobbs View Post
What did you use to pull the audio?
I used tsmuxer and deselected the audio stream. However, it created a .wav file during the process that I plugged back into the compressed version of the m2ts, also using tsmuxer. That was on a version compressed to 21000.

Interestingly, when I did the same thing to a version compressed to 6500, tsmuxer failed when trying to insert the LPCM stream. I expected either both to succeed or both to fail. Not sure what is going on.

Still trying to get another copy of the disc, however to try a distinctly different rip. I'm hoping to pin it down to either a bad disc or a problem with my original drive.
dfsooner is offline   Reply With Quote
Old 10th June 2012, 11:30   #15223  |  Link
colinhunt
Registered User
 
Join Date: Dec 2002
Posts: 1,022
Quote:
Originally Posted by jdobbs View Post
Ok then, I'm confused.
Sorry, my bad, I'm sure.

Quote:
I thought the extracted track was missing -- and you corrected it by copying/renaming the first track for the encode. I guess that apparently isn't the case. So I have no idea what is happening.
Yes, the extracted track was missing and that caused the ReencodeAudio() error. In other words, tsmuxer was unable to extract the track during BD-RB processing.
I corrected the problem by making a copy of 4352.ac3 (which BD-RB had successfully created) and renaming it 4353.ac3, then resuming BD-RB.

Everything I did and posted about after that was to test & prove that 00043.m2ts does in fact contain two PCM tracks. I ran TSMUXER, dropped 00043.m2ts into it, selected both PCM tracks, chose Demux as output and tsmuxer extracted two PCM tracks.

In other words, tsmuxer failed to extract one of the two PCM tracks during BD-RB operation -- but extracted both fine when I operated tsmuxer as a stand-alone app.
colinhunt is offline   Reply With Quote
Old 11th June 2012, 17:06   #15224  |  Link
asiafan
Registered User
 
Join Date: Dec 2010
Posts: 9
Hi i am poiting this question to Jdobbs i got 1st time ever problem with lastest Rebuilder. Since this version my reencoding is finishing @ 25,5 GB (27 451 559 936)
doesnt matter if i choose target 25GB or manuall it ends @27GB. Even after removing LPCM audio still same. Best way its to use 2 previous versions but as usuall expired
asiafan is offline   Reply With Quote
Old 11th June 2012, 17:50   #15225  |  Link
Yordan5
Registered User
 
Join Date: Aug 2010
Posts: 76
With this version my encodings seem to finish between 0.5 and 1.5Gb smaller (depending on the size of the original movie - the larger it is the bigger the difference is between target size and actual size BDRebuilder produces) than what I specify in the Custom Target Size option. This was not the case with previous versions. If a log is needed I'll do another back up and will provide it. I did Transformers 3 (original size just over 38Gb) and set the Custom target size to 20Gb. The eventual back up was 18.5Gb. Next I did Planet Earth disk 1 (original size just over 22Gb) and set the Custom target size to 16.1Gb the eventual back up ended up 15.6Gb. The settings were Two Pass, High Quality, keeping original HD Audio.
Yordan5 is offline   Reply With Quote
Old 12th June 2012, 01:29   #15226  |  Link
jdobbs
Moderator
 
Join Date: Oct 2001
Posts: 20,973
@asiafan
@Yordan5

Nothing has changed in this version that affects sizing in any way (except possibly the new version of X264 -- but that is very, very unlikely). I would suggest you uninstall/reinstall FFDSHOW, HAALI, and AVISYNTH.
__________________
Help with development of new apps: Donations.
Website: www.jdobbs.net
jdobbs is offline   Reply With Quote
Old 12th June 2012, 04:53   #15227  |  Link
dfsooner
Registered User
 
Join Date: Nov 2009
Location: North Las Vegas, NV
Posts: 112
Quote:
Originally Posted by dfsooner View Post
I used tsmuxer and deselected the audio stream. However, it created a .wav file during the process that I plugged back into the compressed version of the m2ts, also using tsmuxer. That was on a version compressed to 21000.

Interestingly, when I did the same thing to a version compressed to 6500, tsmuxer failed when trying to insert the LPCM stream. I expected either both to succeed or both to fail. Not sure what is going on.

Still trying to get another copy of the disc, however to try a distinctly different rip. I'm hoping to pin it down to either a bad disc or a problem with my original drive.
OK. Here's an update:

I have now ripped this 5 times with two different original discs on three different blu-ray drives from two different manufacturers. I get exactly the same error in every case.

Because the error is generated from tsmuxer, I have to assume that either there is a bug in tsmuxer or an authoring anomaly in the title itself. Not sure there is any way around it at this point. I even tried converting the LPCM track to AC3 using Audacity but had some sound gaps that made it unusable. Ideas anyone?
dfsooner is offline   Reply With Quote
Old 12th June 2012, 10:46   #15228  |  Link
asiafan
Registered User
 
Join Date: Dec 2010
Posts: 9
Quote:
Originally Posted by jdobbs View Post
@asiafan
@Yordan5

Nothing has changed in this version that affects sizing in any way (except possibly the new version of X264 -- but that is very, very unlikely). I would suggest you uninstall/reinstall FFDSHOW, HAALI, and AVISYNTH.

i will be reencoding few others BDs so i will inform you if this is just matter or single BD or matter of x264 version


this last BD was 27GB so i done quickly BD25 fast two pass
mode + DTS HD => ac3 .





PS can i put x264 files older to new version or its pointless?
asiafan is offline   Reply With Quote
Old 12th June 2012, 13:06   #15229  |  Link
laserfan
Aging Video Hobbyist
 
Join Date: Dec 2004
Location: Off the Map
Posts: 2,461
Quote:
Originally Posted by dfsooner View Post
I have now ripped this 5 times with two different original discs on three different blu-ray drives from two different manufacturers. I get exactly the same error in every case.

Because the error is generated from tsmuxer, I have to assume that either there is a bug in tsmuxer or an authoring anomaly in the title itself...Ideas anyone?
Only time I've seen txmuxer fail is with a "bad" subtitle track, so (long shot) try muxing w/o a sub and see if that works.
laserfan is offline   Reply With Quote
Old 12th June 2012, 14:43   #15230  |  Link
jdobbs
Moderator
 
Join Date: Oct 2001
Posts: 20,973
Quote:
Originally Posted by asiafan View Post
i will be reencoding few others BDs so i will inform you if this is just matter or single BD or matter of x264 version


this last BD was 27GB so i done quickly BD25 fast two pass
mode + DTS HD => ac3 .





PS can i put x264 files older to new version or its pointless?
Please follow the advice about reinstalling the helper apps before trying other things (as I recommended). It is the likely source of your error.
__________________
Help with development of new apps: Donations.
Website: www.jdobbs.net
jdobbs is offline   Reply With Quote
Old 12th June 2012, 19:47   #15231  |  Link
colinhunt
Registered User
 
Join Date: Dec 2002
Posts: 1,022
Bumped into a peculiar disc: Thin Ice (http://www.amazon.com/Thin-Ice-Blu-r.../dp/B007RKFY0W). It's 46GB in total and contains two large .m2ts files. 00000.m2ts is 18.9GB and 00034.m2ts is 21GB. The latter, when played in MPC-HC, has a running time of 109 minutes. 00000.m2ts, while a smaller file, has a running time of more than 200 minutes -- but when one tries to skip ahead, MPC-HC crashes.

I tried to create a full backup of the disc while blanking 00034.m2ts (and trailers):

Code:
[06.12.12] BD Rebuilder v0.40.10 (beta)
[19:23:51] Source:  THIN_ICE
  - Input BD size: 23,35 GB
  - Approximate total content: [04:15:08.634]
  - Target BD size: 23,78 GB
  - Windows Version: 6.1 [7601]
  - Quality: Highest (Very Slow), Two Pass
  - X264 Tweak(s) enabled
  - Decoding/Frame serving: DGDecNV
  - Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[19:23:53] PHASE ONE, Encoding
 - [19:23:53] Processing: VID_00000 (1 of 28)
 - [19:23:53] Extracting A/V streams [VID_00000]
 - [19:29:32] Reencoding video [VID_00000]
 - [19:29:32] Keeping original video (no reencode)
 - [19:29:32] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [19:29:32] Multiplexing M2TS
 - [19:29:38] Processing: VID_00024 (2 of 28)
 - [19:29:38] Extracting A/V streams [VID_00024]
 - [19:29:49] Reencoding video [VID_00024]
 - [19:29:49] Keeping original video (no reencode)
 - [19:29:49] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [19:29:49] Multiplexing M2TS
 - [19:29:54] Processing: VID_00025 (3 of 28)
 - [19:29:54] Extracting A/V streams [VID_00025]
 - [19:30:02] Reencoding video [VID_00025]
 - [19:30:02] Keeping original video (no reencode)
 - [19:30:02] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [19:30:02] Multiplexing M2TS
 - [19:30:06] Blanking: VID_00026 (4 of 28)
 - [19:30:06] Blanking: VID_00034 (5 of 28)
 - [19:30:06] Processing: VID_00035 (6 of 28)
 - [19:30:06] Extracting A/V streams [VID_00035]
 - [19:30:15] Reencoding video [VID_00035]
 - [19:30:15] Keeping original video (no reencode)
 - [19:30:15] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [19:30:15] Multiplexing M2TS
 - [19:30:19] Processing: VID_00101 (7 of 28)
 - [19:30:19] Extracting A/V streams [VID_00101]
 - [19:32:53] Reencoding video [VID_00101]
 - [19:32:53] Keeping original video (no reencode)
 - [19:32:53] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [19:32:53] Multiplexing M2TS
 - [19:34:20] Processing: VID_00102 (8 of 28)
 - [19:34:20] Extracting A/V streams [VID_00102]
 - [19:35:42] Reencoding video [VID_00102]
 - [19:35:42] Keeping original video (no reencode)
 - [19:35:42] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [19:35:42] Multiplexing M2TS
 - [19:35:56] Processing: VID_00104 (9 of 28)
 - [19:35:56] Extracting A/V streams [VID_00104]
 - [19:36:16] Reencoding video [VID_00104]
 - [19:36:16] Keeping original video (no reencode)
 - [19:36:16] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [19:36:16] Multiplexing M2TS
 - [19:36:27] Processing: VID_00105 (10 of 28)
 - [19:36:27] Extracting A/V streams [VID_00105]
 - [19:36:39] Reencoding video [VID_00105]
 - [19:36:39] Keeping original video (no reencode)
 - [19:36:39] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [19:36:39] Multiplexing M2TS
 - [19:36:44] Processing: VID_00106 (11 of 28)
 - [19:36:44] Extracting A/V streams [VID_00106]
 - [19:36:58] Reencoding video [VID_00106]
 - [19:36:58] Keeping original video (no reencode)
 - [19:36:58] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [19:36:58] Multiplexing M2TS
 - [19:37:03] Processing: VID_00107 (12 of 28)
 - [19:37:03] Extracting A/V streams [VID_00107]
 - [19:37:15] Reencoding video [VID_00107]
 - [19:37:15] Keeping original video (no reencode)
 - [19:37:15] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [19:37:15] Multiplexing M2TS
 - [19:37:20] Processing: VID_00108 (13 of 28)
 - [19:37:20] Extracting A/V streams [VID_00108]
 - [19:37:32] Reencoding video [VID_00108]
 - [19:37:32] Keeping original video (no reencode)
 - [19:37:32] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [19:37:32] Multiplexing M2TS
 - [19:37:38] Processing: VID_00109 (14 of 28)
 - [19:37:38] Extracting A/V streams [VID_00109]
 - [19:37:49] Reencoding video [VID_00109]
 - [19:37:49] Keeping original video (no reencode)
 - [19:37:49] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [19:37:49] Multiplexing M2TS
 - [19:37:54] Processing: VID_00110 (15 of 28)
 - [19:37:54] Extracting A/V streams [VID_00110]
 - [19:38:05] Reencoding video [VID_00110]
 - [19:38:05] Keeping original video (no reencode)
 - [19:38:05] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [19:38:05] Multiplexing M2TS
 - [19:38:11] Processing: VID_00111 (16 of 28)
 - [19:38:11] Extracting A/V streams [VID_00111]
 - [19:38:24] Reencoding video [VID_00111]
 - [19:38:24] Keeping original video (no reencode)
 - [19:38:24] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [19:38:24] Multiplexing M2TS
 - [19:38:31] Processing: VID_00112 (17 of 28)
 - [19:38:31] Extracting A/V streams [VID_00112]
 - [19:38:43] Reencoding video [VID_00112]
 - [19:38:43] Keeping original video (no reencode)
 - [19:38:43] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [19:38:43] Multiplexing M2TS
 - [19:38:48] Processing: VID_00113 (18 of 28)
 - [19:38:48] Extracting A/V streams [VID_00113]
 - [19:39:00] Reencoding video [VID_00113]
 - [19:39:00] Keeping original video (no reencode)
 - [19:39:00] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [19:39:00] Multiplexing M2TS
 - [19:39:05] Processing: VID_00114 (19 of 28)
 - [19:39:05] Extracting A/V streams [VID_00114]
 - [19:39:19] Reencoding video [VID_00114]
 - [19:39:19] Keeping original video (no reencode)
 - [19:39:19] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [19:39:19] Multiplexing M2TS
 - [19:39:24] Processing: VID_00115 (20 of 28)
 - [19:39:24] Extracting A/V streams [VID_00115]
 - [19:39:37] Reencoding video [VID_00115]
 - [19:39:37] Keeping original video (no reencode)
 - [19:39:38] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [19:39:38] Multiplexing M2TS
 - [19:39:43] Processing: VID_00116 (21 of 28)
 - [19:39:43] Extracting A/V streams [VID_00116]
 - [19:40:01] Reencoding video [VID_00116]
 - [19:40:01] Keeping original video (no reencode)
 - [19:40:01] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [19:40:01] Multiplexing M2TS
 - [19:40:10] Processing: VID_00318 (22 of 28)
 - [19:40:10] Extracting A/V streams [VID_00318]
 - [19:40:23] Reencoding video [VID_00318]
 - [19:40:23] Keeping original video (no reencode)
 - [19:40:23] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [19:40:23] Multiplexing M2TS
 - [19:40:29] Blanking: VID_00325 (23 of 28)
 - [19:40:29] Blanking: VID_00326 (24 of 28)
 - [19:40:29] Blanking: VID_00327 (25 of 28)
 - [19:40:29] Blanking: VID_00328 (26 of 28)
 - [19:40:29] Processing: VID_00340 (27 of 28)
 - [19:40:29] Extracting A/V streams [VID_00340]
 - [19:40:41] Reencoding video [VID_00340]
 - [19:40:41] Keeping original video (no reencode)
 - [19:40:41] Processing audio tracks
 - [19:40:41] Multiplexing M2TS
 - [19:40:46] Processing: VID_00343 (28 of 28)
 - [19:40:46] Extracting A/V streams [VID_00343]
 - [19:40:57] Reencoding video [VID_00343]
 - [19:40:57] Keeping original video (no reencode)
 - [19:40:57] Processing audio tracks
 - [19:40:57] Multiplexing M2TS
[19:41:02]PHASE ONE complete
[19:41:02]PHASE TWO - Rebuild Started
 - [19:41:02] Rebuilding BD file Structure
[19:41:37] - Encode and Rebuild complete
[19:41:37] JOB: THIN_ICE finished.
At some point during the process, BD-RB popped up a dialog window to report that an audio type is different from reported, asked me to choose which audio type to use. (Can't remember the exact wording of the dialog window, but I'm sure jdobbs knows which one I mean.)

Here's where things go weird: 00000.m2ts and 00034.m2ts are not in the same playlist, so BD-RB lets me blank 00034.m2ts -- and you can see from the log BD-RB processes 00000.m2ts by keeping original video and audio -- but the final output is less than 5GB in size.

Yes, I'm using custom size but I don't think this is related to that. Just a guess, mind you

Last edited by colinhunt; 12th June 2012 at 19:49.
colinhunt is offline   Reply With Quote
Old 12th June 2012, 20:13   #15232  |  Link
dfsooner
Registered User
 
Join Date: Nov 2009
Location: North Las Vegas, NV
Posts: 112
Quote:
Originally Posted by laserfan View Post
Only time I've seen txmuxer fail is with a "bad" subtitle track, so (long shot) try muxing w/o a sub and see if that works.
Tried to remux with only the video and the primary LPCM audio - no other audio and no subtitles. Tsmuxer failed. Thanks for the suggestion though.
dfsooner is offline   Reply With Quote
Old 12th June 2012, 21:00   #15233  |  Link
jdobbs
Moderator
 
Join Date: Oct 2001
Posts: 20,973
Quote:
Originally Posted by colinhunt View Post
Bumped into a peculiar disc: Thin Ice (http://www.amazon.com/Thin-Ice-Blu-r.../dp/B007RKFY0W). It's 46GB in total and contains two large .m2ts files. 00000.m2ts is 18.9GB and 00034.m2ts is 21GB. The latter, when played in MPC-HC, has a running time of 109 minutes. 00000.m2ts, while a smaller file, has a running time of more than 200 minutes -- but when one tries to skip ahead, MPC-HC crashes.

I tried to create a full backup of the disc while blanking 00034.m2ts (and trailers):

[06.12.12] BD Rebuilder v0.40.10 (beta)
[19:23:51] Source: THIN_ICE
- Input BD size: 23,35 GB
- Approximate total content: [04:15:08.634]
- Target BD size: 23,78 GB
- Windows Version: 6.1 [7601]
- Quality: Highest (Very Slow), Two Pass
- X264 Tweak(s) enabled
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
...
[19:41:02]PHASE ONE complete
[19:41:02]PHASE TWO - Rebuild Started
- [19:41:02] Rebuilding BD file Structure
[19:41:37] - Encode and Rebuild complete
[19:41:37] JOB: THIN_ICE finished.

At some point during the process, BD-RB popped up a dialog window to report that an audio type is different from reported, asked me to choose which audio type to use. (Can't remember the exact wording of the dialog window, but I'm sure jdobbs knows which one I mean.)

Here's where things go weird: 00000.m2ts and 00034.m2ts are not in the same playlist, so BD-RB lets me blank 00034.m2ts -- and you can see from the log BD-RB processes 00000.m2ts by keeping original video and audio -- but the final output is less than 5GB in size.

Yes, I'm using custom size but I don't think this is related to that. Just a guess, mind you
The message you mentioned is actually coming from DGDecNV. I think it is telling you that the PAT/PMT of the M2TS doesn't match the MPLS & CLPI files.
__________________
Help with development of new apps: Donations.
Website: www.jdobbs.net
jdobbs is offline   Reply With Quote
Old 12th June 2012, 21:15   #15234  |  Link
colinhunt
Registered User
 
Join Date: Dec 2002
Posts: 1,022
Quote:
Originally Posted by jdobbs View Post
The message you mentioned is actually coming from DGDecNV. I think it is telling you that the PAT/PMT of the M2TS doesn't match the MPLS & CLPI files.
I'm pretty sure that's the one, yes. Does that have any bearing on the very small output size?
colinhunt is offline   Reply With Quote
Old 12th June 2012, 22:09   #15235  |  Link
colinhunt
Registered User
 
Join Date: Dec 2002
Posts: 1,022
Thin Ice is an interesting specimen for another reason: the Director's Cut playlist includes an additional bit shown before the movie.. which messes up audio sync if one tries to do a movie-only backup.
colinhunt is offline   Reply With Quote
Old 12th June 2012, 23:11   #15236  |  Link
jdobbs
Moderator
 
Join Date: Oct 2001
Posts: 20,973
Quote:
Originally Posted by colinhunt View Post
I'm pretty sure that's the one, yes. Does that have any bearing on the very small output size?
Actually it's more likely that it is telling you the PAT/PMT tables don't match the actual stream. I doubt that the DGDecNV driver looks at the MPLS/CLPI.
__________________
Help with development of new apps: Donations.
Website: www.jdobbs.net
jdobbs is offline   Reply With Quote
Old 13th June 2012, 11:52   #15237  |  Link
colinhunt
Registered User
 
Join Date: Dec 2002
Posts: 1,022
Quote:
Originally Posted by jdobbs View Post
Actually it's more likely that it is telling you the PAT/PMT tables don't match the actual stream. I doubt that the DGDecNV driver looks at the MPLS/CLPI.
OK. When I have a moment, I'll run the backup again the same way to see what it's actually telling me.
colinhunt is offline   Reply With Quote
Old 13th June 2012, 16:55   #15238  |  Link
ttringle
Registered User
 
Join Date: Nov 2003
Posts: 13
I have a motherboard with Virtu support, is there a way to enable virtu support in FFDShow to speed up the re-encoding process, or enable CUDA on my main video card for the same purpose?

Thanks

TimT
ttringle is offline   Reply With Quote
Old 13th June 2012, 18:48   #15239  |  Link
jdobbs
Moderator
 
Join Date: Oct 2001
Posts: 20,973
Quote:
Originally Posted by ttringle View Post
I have a motherboard with Virtu support, is there a way to enable virtu support in FFDShow to speed up the re-encoding process, or enable CUDA on my main video card for the same purpose?

Thanks

TimT
I'm not that familiar wiht Virtu, but CUDA is supported through DGDecNV decoding, assuming you have it installed (see the SETUP dialog). As some point in the future it might also be available through support of LAV filters.
__________________
Help with development of new apps: Donations.
Website: www.jdobbs.net
jdobbs is offline   Reply With Quote
Old 13th June 2012, 19:08   #15240  |  Link
ttringle
Registered User
 
Join Date: Nov 2003
Posts: 13
jdobbs,

Quick question, can I use DVD Rebuilder Pro to upscale a 480p DVD to 720p or 1080p? I know there wouldn't be any improvement in video quality other than bypassing my televisions scaler but I'm just curious.
ttringle is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 00:55.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.