DVD Rebuilder not Compatible on VISTA

[CCE]

Hi! JDOBBS I test Vista RTM today DVD ReBuilder got error on registering look the picture.

http://img112.imageshack.us/img112/9287/dvdrberrorlk5.jpg


Will there be soon a vista compatible?

Tnx

[Fishman0919]

you need to run the rebuilder.exe as admin.... go into the dvd-rb pro dir, right click on rebuilder.exe and click run as administrator.

[canadian guy]

works perfect for me,i had that error to and i uninstalled and reinstalled rebuilder,, that fixed it,,,cheers

[jdobbs]

You didn't have to set it up for "admin"?

[MCFish]

I dont have to. Runs great as is

[jdobbs]

Maybe they've fixed that...

[Jon1166]

I've been running DVD Rebuilder since 1.12.0 on VISTA and have updated every release since without a hitch. Though I did have an issue with the first time I installed it... got some sort of error... not sure what. I re-installed and it's been running perfectly since. I too haven't had to set it on admin to run it.
Try a re-install CCE and good luck.

[jdobbs]

Does anyone know of any documentation around that outlines the programming constraints in Vista? Is there some rule as to when an application is or isn't allowed to update the registry?

[Fishman0919]

I only got this error with vista build 6000 (RTM) and final from Gateway.
None of the other builds did this.... you can turn it off.

[wmansir]

Developer Best Practices and Guidelines for Applications in a Least Privileged Environment (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnlong/html/AccProtVista.asp)

Vista includes a stop gap measure called Virtualization to help legacy apps function in the non-admin envirmoment. The basic idea is that whenever a non-admin app tries to write to a system file/registry space it is redirected to a user specific space. For example, if you write to:

HKEY_LOCAL_MACHINE\Software\AppKey1

the system really writes to:

HKEY_USERS\<User SID>_Classes\VirtualStore\Machine\Software\AppKey1

This should be transparent to most apps, but it's not perfect. Problems usually occur when a program writes to a file in a protected space and then call an external program with the path. Since the second program is only reading the protected space it doesn't trigger virtualization and accesses the original location, which was never written too.

Also, Vista has a new way of managing file associations called "default programs", but from what I've read it's designed as a supplemental way for users/programmers to fight over common file types and is shouldn't be necessary for proprietary extensions like .rbk

[kbello]

@all

i just reinstall my computer with vista rtm and the preview window didn't work, reason xvid 1.1.2 koepi's build cause a conflict with codecs in vista, unistalling that xvid and works again.

Maybe help to someone with same problem.

[nicolati]

It says me, instead, that the component MSCOMCTL.OCX is not registered, but I reinstalled all. I'll try to run as Admin.
Bye.
nicolati

[wmansir]

I just noticed that the preview window in both the standard and Beta Segment Viewer/Editor does not work unless you set Rebuilder.exe to 98/ME compatibility mode. You can do that by right-clicking on the file and going to properties. I haven't yet tested it in compat mode enough to see if this causes other errors.

I already mentioned in the mobile encoding test thread that you may have to also do this with FFMPEG.exe if you plan on doing mobile encoding with vista.

[nicolati]

It works in Admin Mode.
Bye
nicolati

[wmansir]

It looks like setting Rebuilder.exe to 98/ME compat isnt' a solution for the directshow issue. Halfway through the first segment encoding with ProCoder an ECLPro "could not launch ProCoder" error popped up, plus ProCoder seemed to be having it's own issues with the speed jumping between 8x and 0.5xRT, plus it was only using 1 core and no real output was produced. It looks like 98/ME compat is inherited and those programs don't like it.

[betard]

I just noticed that the preview window in both the standard and Beta Segment Viewer/Editor does not work unless you set Rebuilder.exe to 98/ME compatibility mode. You can do that by right-clicking on the file and going to properties. I haven't yet tested it in compat mode enough to see if this causes other errors.

I already mentioned in the mobile encoding test thread that you may have to also do this with FFMPEG.exe if you plan on doing mobile encoding with vista.


I am having the same issue a couple of you posted, where the screen in the standard and beta segment viewer is blank.

Does anyone know of a solution to this issue in Vista? kind of a pain in the ass to install and uninstall my xvid codecs everytime I want to use dvd-rb.

[jdobbs]

I would have to say the problem is not in DVD-RB -- but in XviD. DVD-RB simply calls the windows standard libaries for display.

[betard]

I would have to say the problem is not in DVD-RB -- but in XviD. DVD-RB simply calls the windows standard libaries for display.

naturally I know nothing about programming, but is it possible that the calls for the "windows standard libraries for display" are different in Vista, and therefor not called properly? If that makes sense at all. Just wondering since I don't quite know how to solve an xvid problem if that is not the case.

[wmansir]

Since you mentioned Xvid I thought perhaps a different colorspace would avoid invoking Xvid. I got preview kind of working but I haven't quite nailed it down yet. Perhaps jdobbs can figure it out since he knows more about how the preview process works and I'm not exactly a directshow expert.

First I tried just adding CovertToRGB() at the end of a script and it worked. So then I tried commenting out ConvertToYUY2(Interlaced=true) and that worked. So I thought it must be something to do with the YUY2 colorspace, since YV12 and RGB worked. I disabled ConvertToYUY2() under Options->AVS Options, and re-PREPed the disc.

The odd thing is the script now has ConvertToyV12(Interlaced=true) but for some reason preview doesn't work. If I comment out that line it does work, but I really don't see why it should matter. I don't think AVS even executes that line because it's already in YV12.

[betard]

Since you mentioned Xvid I thought perhaps a different colorspace would avoid invoking Xvid. I got preview kind of working but I haven't quite nailed it down yet. Perhaps jdobbs can figure it out since he knows more about how the preview process works and I'm not exactly a directshow expert.

First I tried just adding CovertToRGB() at the end of a script and it worked. So then I tried commenting out ConvertToYUY2(Interlaced=true) and that worked. So I thought it must be something to do with the YUY2 colorspace, since YV12 and RGB worked. I disabled ConvertToYUY2() under Options->AVS Options, and re-PREPed the disc.

The odd thing is the script now has ConvertToyV12(Interlaced=true) but for some reason preview doesn't work. If I comment out that line it does work, but I really don't see why it should matter. I don't think AVS even executes that line because it's already in YV12.

You make any additional findings with this?? Ive tried uninstalling and re-installing various xvid releases/builds and I'm still having the same issues.

[jdobbs]

The display is presented using the MCI routines. It makes calls via WINMM.DLL (the MCI API interface). Pretty much all that DVD-RB does is send a command to the interface telling it what file to play and where to display it -- and then might follow up with positioning commands.

[ruedas]

I have been testing dvd-rb in vista ultimate 64 bit version. You are not able to see previews in both new editor and old one. If you run it in compat mode for win98 it works great without any problem.
I have k-lite code pack 3.01 running the cyberlink mpeg 2 option for playback.

Works great but I'll rather be running it in normal mode. Is there some fix to run it and see the previews?