View Full Version : Adjusting Beta Viewer percentage slider
Rippraff
7th September 2006, 23:14
Read my edit in Post #45 (we were typing at the same time).
As I already said, confusing... ;)
Could you try a different disc then... I can't imagine why it would not react to your click... in fact it uses the same subroutine as the "<" button...
Will do.
One thing.. It may not allow the bitrate to go above the original.
No that isn't the case (reduction 75 %) and by the way then also the slider wouldn't work I guess, but it does.
Cu Rippraff
jdobbs
7th September 2006, 23:27
Anybody else out there who can report problems with the ">" on the slider not working?
Rippraff
7th September 2006, 23:39
Anybody else out there who can report problems with the ">" on the slider not working?
I hope so, don't want to be the only person on the planet with this problem. :p
Okay, 2nd attempt with 2nd disc:
Full backup mode, reduction 64.4%
">" still doesn't work
If I hit and hold > the value jumps to 64.1% and after unholding the mouse it switches back to 64.0%.
I can move the slider up and down, the behaviour of > is allways the same. :confused:
The "<" button works fine and will result in 1% steps.
"Reset to defaults" by the way results in 64.0%. Seems so as the original decimal value will be ignored too.
Cu Rippraff
nashcity
8th September 2006, 00:24
The ">" works perfectly for me.
Where is this "Allocate saved space to feature" button???
Rippraff
8th September 2006, 00:26
Where is this "Allocate saved space to feature" button???
Upper left corner under Actions.
Cu Rippraff
Sharc
8th September 2006, 07:35
New size adjustments work great for me, in both directions < or >.
The slight back-spreading of gained space to the credits that were intentionally reduced isn't really an issue I believe. It will not noticeably affect the final quality of the feature. In case I would just recommend to reduce the credits slightly more initially, knowing that some of the gained space will be re-allocated to the credits when hitting the "Allocate saved space to feature".
casperse
8th September 2006, 09:57
I have the same problem < works but > dosent....
Could this be bacuse I have updatet my version and not reinstalled it?...Since someone have this problem and others doset?
I use the scale slider and then the < to get the precise value...for now.
I love the new feature:
Again
Quote:
This will work also for the credits, except that it will increase the bitrate again a little by clicking "Allocate saved space to feature". Example: Credits original (75% reduction) BR 3,717 => move the slider to 31% BR 1,536 => "Allocate saved space to feature" BR rises up again to 1,621 for the credits cell.
You can decrease the values for the last cell (credits), after pushing "Allocate saved space to feature" it will be increased again, but only a little as the presaved bitrate will be allocated to all cells of the feature.
This is GREAT always wanted this! :D
jdobbs
8th September 2006, 11:50
There's not a lot I can do about the backspreading to the credits, because that's what it's supposed to do. When you say "Allocate to Feature" it means just that -- and the credits are part of the feature. Like I said, I could always add a "Lock Settings" checkbox. That would prevent any resetting of any of the values in that segment for any reason.
This ">" problem is really puzzling. Why does it work on all but a couple of computers? Even worse is the fact that both buttons call the same routine... the only difference is that one says to subtract .1 % and the other says to add .1%.
jdobbs
8th September 2006, 12:32
@Rippraff & casperse
Could you capture the screen and post a jpg of just the area in the editor that shows the buttons and percentage. I'd like to see if anything is different.
Thanks.
Could this be bacuse I have updatet my version and not reinstalled it?...Since someone have this problem and others doset?No. Same thing. I'm wondering if it might have something to do with screen size/spacing...
Rippraff
8th September 2006, 12:48
There's not a lot I can do about the backspreading to the credits, because that's what it's supposed to do. When you say "Allocate to Feature" it means just that -- and the credits are part of the feature. Like I said, I could always add a "Lock Settings" checkbox. That would prevent any resetting of any of the values in that segment for any reason.
Well, maybe this is all a big misunderstanding.
When I've first tested the new feature last night I wrongly thought "Allocate saved space to feature" is a check box. After I've made some more tests i realized, how it works and thought it's a good idea to edit my post make this clear and also give an advice how it works, if you want to lower bitrates for the credits.
Obviously I've failed. :(
I'm not complaining about anything, the new feature does exactly what it should and I like it a lot! :)
There is IMHO no need to implement a lock settings checkbox, you should only keep in mind that bitrate rises again slightly after "Allocate saved space to feature" if you lower bitrate inside the feature that's all. ;)
jdobbs, thanks a lot for another useful function!
This ">" problem is really puzzling. Why does it work on all but a couple of computers? Even worse is the fact that both buttons call the same routine... the only difference is that one says to subtract .1 % and the other says to add .1%.
Does it subtract in 0.1% steps?
If yes, then it again works different in my case, as I already wrote, "<" gives reduction in 1.0% steps.
Cu Rippraff
Rippraff
8th September 2006, 12:56
Could you capture the screen and post a jpg of just the area in the editor that shows the buttons and percentage. I'd like to see if anything is different.
Of course.
http://www.rippraff.de/Pics/RB_beta_editor.jpg
Cu Rippraff
jdobbs
8th September 2006, 13:09
I think I know what it is... I'm guessing that the "," decimal place marker is causing the issue... interesting it would, though.. since I'm actually letting the system do the string conversion for me.
Same for you too, eh, casperse?
Rippraff
8th September 2006, 13:10
I get it! :)
It has something to do with the differences how you handle "," and "." in different countries. The decimal separation is "," in Germany and a lot of other (european?) countries. "." we use for 1000 separation.
If I change country settings in windows from german to english (US) everything is working as it should. :)
Cu Rippraff
Edit: Synchronous posting should be olympic, we would win... :p
jdobbs
8th September 2006, 13:13
I confirmed it. I set my regional settings to "German (Germany)" and I can repeat it. I'll change my code so I do the conversion myself.
Rippraff
8th September 2006, 13:20
Great! :thanks:
Cu Rippraff
jdobbs
8th September 2006, 13:21
Hmmm... that may also have an affect in a couple of other areas of the Viewer/Editor.
Rippraff
8th September 2006, 13:31
Can you have a look as well at the "Reset to Defaults" code, why it kills the decimal value?
You can check this with every source, say RB gives 64.9 % reduction after prepare, when you open the beta editor and click on "Reset to Defaults" it will result in 64.0 %.
Cu Rippraff
jdobbs
8th September 2006, 14:41
Same newbie-ass error... I've already fixed it. :o
You'd think I just started my first programming job when I make errors like that... I guess I was in a hurry.
Rippraff
8th September 2006, 14:47
You'd think I just started my first programming job...
I would never ever think that! ;)
Cu Rippraff
Voodoochild
8th September 2006, 15:19
Same newbie-ass error... I've already fixed it. :o
You'd think I just started my first programming job when I make errors like that... I guess I was in a hurry.
5 years in the programming business and I'm still makes stupid errors that amaze me sometime ;)
blutach
8th September 2006, 15:45
Darn good birddogging guys!
Regards
jdobbs
8th September 2006, 17:24
Just a note to try an avert problems... I'd not recommend anyone switch back-and-forth between country settings in their windows settings to test this too much... There are a lot of values written to INI, INF and other files that use your local formats... So if you ran a PREPARE, for example, in one country's format and tried to use ENCODE in another you're liable to get lots of sizing and other errors.
Not a big deal -- but something to watch...
Rippraff
8th September 2006, 21:10
Thanks a lot Jerry, I can confirm that everything (">", decimal value) is working fine with the new version. :)
Edit:
@casperse or anyone else who might have the same problem
I'm talking about this version (http://www.jdobbs.com/test/DVD-RB_v1.10.6b_test.zip).
Cu Rippraff
casperse
9th September 2006, 11:04
Sorry for the late respons....
http://img135.imageshack.us/img135/3712/dvdrebuilderrv9.th.png (http://img135.imageshack.us/my.php?image=dvdrebuilderrv9.png)
But i have one more problem maybee its related to the "./," issue
When i choose the movie to "No reencode" except the End credits then I cant do a Save & exit...its greyed out for some reason.
Love the new feature reallocate space works great...Could it also work the other way Reallocate to extra when you have a very small movie that dont need reencoding?
Cheers:D
blutach
9th September 2006, 14:18
Could it also work the other way Reallocate to extra when you have a very small movie that dont need reencoding?Simply mark the movie as no-re-encode and all that will be encoded will be the extras.
There will be a demux/remux however.
Regards
casperse
10th September 2006, 14:53
Yes but what about this:
"When i choose the movie to "No reencode" except the End credits then I cant do a Save & exit...its greyed out for some reason."
I really need the extra 100MB use from the endcredits to the extras...
jdobbs
10th September 2006, 16:02
That only occurs when for some reason the actions would end up creating a feature sector count that is less than zero. I'll have to check it out and see how it could have happened.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.