ReAuthorist making images too big...

[Buckaroo Banzai]

Hello all,

When Using ReAuthorist I will use the auto-size option *but* - then I have to manually adjust to bring the total size down to about 4,300 MB.

If I don't do this then it will be over the 4,700 that Nero will allow me.

Am I the only one burning this small? (If so, can I fix this?)


Do other people have to make the adjustment as well? (If so, could we change ReAuthorist to reflect this [just add another size option in the drop-down box]?)

Pioneer A05
Ritek Media

Thanks!

=BB=

[KungFuCow]

Ive only had this problem when ReAuhorist doesnt recognize the subtitles correctly. If they come up as "Unknown" then it usually overshoots by a small amount.

[Master Yoda]

If the subs are comming up as unknown, in Doitfast4u go Global Options > Other Options > then tick suppress aspect ratio in subtitle filenames.

Also reauthorist and dif4u come up with a different avg. some times. If the reauthorist on is higher than dif4u change it to the avg. dif4u gave.

[Eyes`Only]

If I don't do this then it will be over the 4,700 that Nero will allow me.You're comparing apples to oranges (or as the case may be-- Gigabytes to bytes)

DVDR actually holds 4,704,317,440 bytes, which is approximately 4.381 Gigabytes. Slightly less if you use DVD+ media, which is only one of the reasons I don't.

[Buckaroo Banzai]

Originally posted by Eyes`Only
You're comparing apples to oranges (or as the case may be-- Gigabytes to bytes)


Ummmm,

The comparison is 4,300 MB and 4,700 MB.

ReAuthorist must say the final size will be 4,300 MB or less.

Nero will not burn if the image is larger than 4,700 MB.

If ReAuthorist says the final size will be great than 4,300 MB - than it will actually be greater than 4,700 MB. There is an additional few hundred megs added to the 4,300 ReAuthorist is claiming - this is the problem.

Both applications are claiming to be measuring in MB - do you think one is actually measuring bytes/GB?

Originally posted by KungFuCow
If they come up as "Unknown" then it usually overshoots by a small amount.

ReAuthorist is listing two subpicture streams as "not specified" - is this what you mean?

About how much does it overshoot?


Thanks all for you help!

=BB=

[Eyes`Only]

The comparison is 4,300 MB and 4,700 MB.

The first MB is Megabytes, the second MB is Million Bytes. Software designers can choose to go any ol' way they want, and Ahead obviously decided 4700MB sounded and looked more enticing. In reality that's 4700 Million Bytes (approx. 4.381 GB) though. You really don't want to keep arguing with me on this one. Reauthorist is more true to form, sticking with the idea of not exaggerating the true size.

[Buckaroo Banzai]

Sorry Eyes Only.

I was too focused on what the problem was with ReAuthorist, I automatically discounted something relating to nero - completely idiotic considering I know my bits and bytes, and what you said made perfect sense... Sorry.

Considering the bitch font-end Ahead threw on top of thier latest release it's no surprise thier developers are annoying like that.

I still would like to know why I have to manually set the sizing on ReAuthorist, but I'll keep my eye on the subpicture streams to see if that gives me a pattern...

=BB=

[Tobytl]

Ok, heres a solution. If you want to be safe in reauthorist, change the size in the reauthorist settings box. You can just select the byte count and type a new one, the tag will change to custom as well. I am not 100% sure it works, but it appeared to half the bitrate when I halfed the size on that settings pop up.

So if there is a real problem here, you can always keep a custom setting in there. But it will only keep one custom...

[Eyes`Only]

Glad to see you're understanding the difference now.

If the subs are comming up as unknown, in Doitfast4u go Global Options > Other Options > then tick suppress aspect ratio in subtitle filenames.

Master Yoda hit it on the nail.. this needs to be done until we get a new version of RA (don't ask, I don't know when it'll be hehe) because as of now it balks when it sees aspect ratios in the filename. I implemented this feature to help with future RA development, not anticipating it would mess things up, but then I added this workaround rather than removing the feature entirely.