Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

4480MB split creates 4.7GB files under Mac OS 10.12.5 #49

Closed
rcosgrove opened this issue Jul 1, 2017 · 7 comments
Closed

4480MB split creates 4.7GB files under Mac OS 10.12.5 #49

rcosgrove opened this issue Jul 1, 2017 · 7 comments
Assignees
Labels
Milestone

Comments

@rcosgrove
Copy link

@rcosgrove rcosgrove commented Jul 1, 2017

Keka: v 1.0.9 (1756)
OS: Mac 10.12.5

When I used Keka to create a 7zip archive, using the pre-set 4480MB split option, it created a 4.7GB file that OS X reported as being too large to burn to DVD or disc images.

@aonez
Copy link
Owner

@aonez aonez commented Jul 1, 2017

The result file is 4.700.372.992 bytes?

@aonez
Copy link
Owner

@aonez aonez commented Jul 1, 2017

DVD+R and DVD+R are set to this size. I'm seeing that DVD- has lees space at 4.700.000.000 and 4.700.307.456. Are you using a DVD- device?

I'll adjust the size to 4.700.000.000 so it's compatible with all devices.

Some sizes: http://www.osta.org/technology/dvdqa/dvdqa6.htm

@rcosgrove
Copy link
Author

@rcosgrove rcosgrove commented Jul 1, 2017

@aonez
Copy link
Owner

@aonez aonez commented Jul 1, 2017

Meanwhile you can set the split to custom 4.7g. As soon as I have access to a Mac with superdrive I'll test that issue with Burn (by the way my defecto burner since I own a Mac).

@aonez aonez self-assigned this Jul 3, 2017
@aonez aonez added the core label Jul 3, 2017
@aonez aonez added this to the 1.1.0 milestone Jul 3, 2017
@aonez
Copy link
Owner

@aonez aonez commented Jul 3, 2017

I'll set the fixed size to 4698500000 bytes so a 4.7 DVD will have at least 1.5 MB "free".

@aonez aonez closed this Jul 3, 2017
@aonez
Copy link
Owner

@aonez aonez commented Jul 5, 2017

Next version 1.0.11 will have a quick fix of that. A better implementation will come in version 1.1.0.

@rcosgrove
Copy link
Author

@rcosgrove rcosgrove commented Jul 5, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants