Save Bug
Issue #607
new
When files skirt the 4GB size I have been getting errors that say “The file is bigger than 4 GB, but it was created with 32bit data chunk offset. Select 64bit data chunk offset in the save panel.” Well it already is selected.
I’ve not had this issue before and have transcoded files this big before. Not sure what else to post.
Source files have been
4.01 GB, 5.42 GB, 4.04 GB, and 3.81 GB that have given me issues. I successfully transcoded a 4.13 GB file though.
Please let me know where I should look for data that can help you solve this (or if it’s mine entirely). Thanks for the great program.
Comments (5)
-
reporter
-
repo owner
How are you saving those files? Do you add some tracks to them and then use “save as”?
-
I’m seeing this with all files on the last two Subler updates. Despite checking (and uncheck/re-checking the boxes) the error occurs (but not immediately). Perhaps associated with running an older OSX (10.13.6) with the new universal version?
-
The error reported occurs when the destination volume is full. After clearing space, Subler v1.6.7 completes the process successfully.
Subler incorrectly attributes the disk error to the offsets.
-
“The error reported occurs when the destination volume is full. After clearing space, Subler v1.6.7 completes the process successfully.
Subler incorrectly attributes the disk error to the offsets.”
Can confirm this bug. I encountered the same bug a long time ago. Hope can be fixed in the future.
- Log in to comment
