PDA

View Full Version : Error in v1.27.0 -- Download v1.27.1 Instead


jdobbs
15th February 2008, 15:32
NOTE TO ALL:

I just realized a last minute change caused a serious audio muxing error in v1.27.0 -- PLEASE DON'T UPGRADE YET.

I'm working the issue and should get it fixed today -- and will mail it out. In the meantime -- stick with v1.26.6.

Sorry -- this isn't my finest moment. :eek:

Carpo
15th February 2008, 15:36
now you tell us :p - is this anything to do with the other thread i started about a mem error? because if it is then you are to go to your room without dinner :D

blutach
15th February 2008, 15:44
It's a demux/remux error Carpo. If you do a backup, listen to the audio after about 5 minutes. :)

Regards

jdobbs
15th February 2008, 15:53
As a programmer you know never to make a last minute change to your software before posting. In this case I declared a local variable name that made a global variable not recieve it's correct value. Essentially it screwed up the entire audio muxing mechanism.

Bad Dobbs!

I removed the files to prevent further downloads. I've already fixed it -- but I'm doing a couple of tests before I post and send out. It should be later today.

Sigh... :mad: I hate it when something bad happens and its my fault. I can't yell at anyone.

Not related to a memory error. I'll have to look at that as a separate issue.

Video Dude
15th February 2008, 15:59
No problem jdobbs. Thanks for trying to fix it so soon.

The audio and video seemed sped up. I thought my fast forward button was stuck. :)


If we already did an encode with 1.27 can we just go back to 1.26.6 and do a rebuild? Or should should I do prepare/encode over?

laserfan
15th February 2008, 16:01
Sigh... :mad: I hate it when something bad happens and its my fault. I can't yell at anyone.I think you should do it anyway, if only to feel better. I vote for blutach! He never gets yelled at! ;) :D

jdobbs
15th February 2008, 16:12
No problem jdobbs. Thanks for trying to fix it so soon.

The audio and video seemed sped up. I thought my fast forward button was stuck. :)


If we already did an encode with 1.27 can we just go back to 1.26.6 and do a rebuild? Or should should I do prepare/encode over?Yes. If you just do the REBUILD with v1.26.6 it should be ok.

Also, I just did a quick fix and reposted. If you download v1.27.0 again you'll actually get v1.27.1. It should rebuild correctly. I'm just trying to prevent problems with anyone who hadn't downloaded yet...

Wombler
15th February 2008, 16:18
As a programmer you know never to make a last minute change to your software before posting. In this case I declared a local variable name that made a global variable not recieve it's correct value. Essentially it screwed up the entire audio muxing mechanism.

Bad Dobbs!

I removed the files to prevent further downloads. I've already fixed it -- but I'm doing a couple of tests before I post and send out. It should be later today.

Sigh... :mad: I hate it when something bad happens and its my fault. I can't yell at anyone.

Not related to a memory error. I'll have to look at that as a separate issue.

I know how you feel but perfection is a hard thing to achieve and it's good to be reminded of reality every once in a while.

Not the end of the world though. :)

BTW I find yelling at myself can be extremely theraputic. :D


Wombler

archaeo
15th February 2008, 16:37
Essentially it screwed up the entire audio muxing mechanism.



Perhaps you should let this flawed version 'accidentally' leak out to the DVDRB crackers. :devil:

jdobbs
15th February 2008, 16:55
Funny you'd say that. Actually there was a cracked version I know of that does exactly what this one does because that area of memory had been incorrectly patched...

archaeo
15th February 2008, 16:57
Funny you'd say that. Actually there was a cracked version I know of that does exactly what this one does because that area of memory had been incorrectly patched...

there is justice in this world:)

jdobbs
15th February 2008, 17:55
This fix has been posted as v1.27.1 and is being mailed to registered users (slowly).

You can also download it from this link (http://www.jdobbs.com/Pages/DVDRebuilder/DVD-RB_Pro_download.htm).

My apologies for the inconvenience anyone may have experienced.

urvieh
15th February 2008, 20:10
jdobbs, thanks again for your work.

There seems to be a minor hazzle: As soon as I turn on the multiple instances feature the nosmp flag seems to be set (according to the fps' shown during encoding), but only one instance is running. Is there another switch to turn on for this?

TIA for your reply.

jdobbs
15th February 2008, 20:19
If you see only one instance running that usually means the next segment is going to be extracted. I did some tests and found that doing extraction and encoding simultaneously slowed the system down -- so I modified this release to wait until encoding was complete before extracting.

dialysis1
15th February 2008, 20:35
I had problems with the audio and video with 1.27.0. I'll try it again with 1.27.1.

jdobbs
15th February 2008, 21:31
If you still have the working directory on your hard drive all you have to do is the REBUILD in three click mode.

urvieh
15th February 2008, 22:15
If you see only one instance running that usually means the next segment is going to be extracted. I did some tests and found that doing extraction and encoding simultaneously slowed the system down -- so I modified this release to wait until encoding was complete before extracting.

I see. Thanks again.

blutach
15th February 2008, 22:58
Thanks for the quick fix Jerry.

@laserfan (and anyone else who's interested) - my wife yells at me quite sufficiently (and regularly), thank you very much! :)

Regards

dialysis1
16th February 2008, 03:51
Everything seems good now.
Thanks

mc2man
18th February 2008, 01:37
Possibly for the few that run rb in wine the latest - 1.27.1 is a no go. I see it though maybe it's a local issue. Attempting to run rb produces a 'debugger detected [304]' error

oelewapper
18th February 2008, 06:33
1.27.1 doesn't work with Procoder3 !
I have to give in the program by hand after phase1 and it starts, but it doesn't encode and comes back with an errormessage : one or multiple sources from the project file couldn't be loaded.

I didn't have this problem with 1.26 !

(Although I still had to start Procoder3.exe by hand..... It's not supported yet in Rebuilder. Renaming Procoder3.exe to procoder.exe doesn't help : Procoder won't start at all then !)

I'm completely lost.....
I uninstalled 1.27.1 and re-installed 1.26.6 .
And............. Procoder doesn't work anymore !
That is : with Rebuilder. A quick test showed the problem is not within Procoder because it still converts......

oelewapper
20th February 2008, 13:24
1.27.1 doesn't work with Procoder3 !
I have to give in the program by hand after phase1 and it starts, but it doesn't encode and comes back with an errormessage : one or multiple sources from the project file couldn't be loaded.

I didn't have this problem with 1.26 !

(Although I still had to start Procoder3.exe by hand..... It's not supported yet in Rebuilder. Renaming Procoder3.exe to procoder.exe doesn't help : Procoder won't start at all then !)

I'm completely lost.....
I uninstalled 1.27.1 and re-installed 1.26.6 .
And............. Procoder doesn't work anymore !
That is : with Rebuilder. A quick test showed the problem is not within Procoder because it still converts......

I tried it with HC and ReJig.... both don't work either !
I edited the ini file to use Porcoder3 : doesn't work.
At Phase 1 I get the message : AVISYNTH UNKNOWN.

I tried it with 3 different DVD9's but all didn't work anymore....

In short :
- initial install of 1.26.6 : everything worked
- installed 1.27.1 in same directory : nothing works
- uninstalled and re-installed 1.26.6 : nothing works (with "YourUnInstaller, so registry is cleaned too !)

AviSynth is present on the PC......

Please help !! (registered user !)

jdobbs
20th February 2008, 17:23
Please don't cross-post, you know the rules.

Unistall everything, including AVISYNTH. Then run the DVD-RB full installer and let it configure everything. There obviously something hosed in your configuration.

TomBrooklyn
21st February 2008, 04:28
I guess that explains why the audio got garbled on the last two backups I made in the last couple of days starting after about 5 minutes into the disk. I came here to see if there was an issue w/ 1.27 or whatever and sure enough...

Well, I'm glad that's cleared up.

blutach
21st February 2008, 07:54
Note, your m2vs are OK. jdobbs showed a simple procedure to fix this without re-encoding:

1. In one directory, do a prepare against the original.

2. In another directory, do a prepare with "No Compression" selected against the new (screwed) disc. Then do an ENCODE (it just renames all the .MPV files to M2V).

3. Copy all the M2V files to the first directory.

4. Edit the REBUILDER.INF file in the first directory, and set Progress=2

5. Do just a REBUILD on the first directory. It will get the audio (correctly) from the original.
Regards