MacOS error Result = -111 when encoding

[nharknett]

When trying to encode a DVD the progress bar gets to 99% encoded then stops with a dialog box stating there has been a MacOS error. Result = -111. This happens if I try to burn to DVD or create a .dmg. 

I still have Toast 15 installed but am reluctant to uninstall it in case I can't reinstall it and end up without any burning software.

Cheers Neil H.

Mac Mini (2018), Mojave 10.14., 3.2GHz i7, 32GB RAM.

[nharknett]

I have now uninstalled both Toast 15 & 17, re_installed Toast 17 but the problem persists.

[Tony Seddon]

I'm getting the same message, but only for one particular file. I've run tests with other video clips (MP4 files straight off the GoPro without any editing) and they've worked perfectly well.

I can't find anything wrong with the file that won't burn, so any ideas would be most welcome.

iMac (late 2015), Mojave 10.14.2

[nharknett]

Yes, have tested it and found the same. I have a support ticket with Roxio open so I'll see if I can send them a copy of a failing movie to them for analysis.

[MattL]

I had the same -111 error trying to burn some files to blue ray. New iMac with latest software. Movie files from iMovie set to Best quality. I could burn movies less than ten minutes. 20 minute ones give me the error. The shorter ones were made from same photo and head cam video as the longer ones used. I could add three short movies to one blu Ray disc. One work around I didn’t try was to split the longer movies and just set the encoder to auto play them in series. I may try that yet. I didn’t have the time to keep wasting so I just bought leawo’s Software and it worked first try and I didn’t have to split anything.  hopefully Roxio fixes their product. I will say of the movies I got to encode using both Leawo and Roxio, I definitely prefer the video quality produced by Roxio. Smoother video and more accurate reproduction of the original file.

Edited February 10, 2019 by MattL
Add info

[MattL]

So as a follow up to my last post... I figured I’d go ahead and try splitting the larger movie files and burning. After all the 100 bucks I spent on toast 17 pro included Splice which is supposed to be able to split movies. Well.. first, the only option is ‘auto splice’ which doesn’t seem to have options. Ie how many files, size, minutes etc. so I went ahead and hit the auto split button... it ran for a few minutes and then crashed. 

[Tony Seddon]

Hmmm, that doesn't sound great. It's kind of weird as I've run another test with a fairly long file that was recorded recently and it worked perfectly well. Run time was about 40 minutes.

The file giving me trouble was recorded by someone else about 12 months ago on a different camera, an older GoPro model. I've burned DVDs of the material previously using basic burner software (Burn, free software that was quite capable) but had to upgrade to Toast as older software is gradually stopping working, presumably because of the switch to 64-bit only on the Mac. It's frustrating but the problem does seem to be related to one particular file. I'll try splitting it and see what happens as it has a long runtime of well over an hour.

[h2oflyer]

I'm having the same problem! I opened a support ticket with Roxio on the Feb 5...no response as of yet. I can burn shorter files just fine, but I have a couple of files 1:28, and 1:32 long. They both fail after encode prior to multiplexing. IDK if the encode fails to complete or the multiplexing fails to start. I am using Toast Titanium 17.3 on a Macbook Pro with macOS Mojave 10.14.3. I can burn the same files with my iMac OSX High Sierra using Toast 12. What's changed? 

[nharknett]

I've tried several files, even down to 30 minutes that fail. Others that are longer burn ok. I have a support ticket open, they replied that they have not heard from there engineers as of yet. They did ask if I can burn a DVD via MyDVD Pro (which also fails). Maybe these problems are related?

As soon as I hear back from them I'll update here.

 

h2oflyer,

Toast 17 is now 64 bit. Apart from that I see no difference though I haven't used it because of the ongoing problem. 

[MT-Mike]

Yes, I am also having the same problem. 2012 Mac Pro Mac OS 10.12.6 64GB Ram, 5 TB HD. I question my Sierra (32 bit) and do I have to go up to High Sierra (64) ? Suggestions are welcome. Thanks

Edited February 15, 2019 by MT-Mike

[MT-Mike]

7 minutes ago, MT-Mike said:

Yes, I am also having the same problem. 2012 Mac Pro Mac OS 10.12.6 64GB Ram, 5 TB HD. I question my Sierra (32 bit) and do I have to go up to High Sierra (64) ? Suggestions are welcome. Thanks

If you keep on doing what you are doing... You will keep on getting what you got. Something has to change.

[Pastor Rick]

I am also receiving the same error code when I try to burn the DVD.   My file encodes completely, but then will not burn.  I was trying to burn it in High Definition.  Any help would be greatly appreciated.  Thanks!

[Macrossroads]

I have used TOAST for many years and have never had such an annoying problem when trying to encode/burn a DVD. Successful encoding results in an OS error -111. File size makes no difference, iMac, laptop, two different burners - same error message. Looks like a lot of people need help here.

[Jimmy R]

I am also encountering the same problem with result code -111. The blu-ray will get all the way through encoding and then bring up the same error message posted by MTMike above.  I need to deliver a blu-ray to a client by Monday so I need a solution to this ASAP. Has anyone figured it out?

 

Running on a 2017 iMac with a 4.2 GHz Processor and 64 GB of RAM. OS is Mojave 10.14.

[nharknett]

After a lot of experimenting I found that trimming a movie to a certain time would enable a file that would not burn to burn. Here's what I did.

The movie (a .mov exported from a .m4v) lasts for 23 mins 37 seconds and is 452.5 MB.

Using Quicktime i experimented with trimming the file to see if size mattered.

I eventually I found that if I trimmed it to 23m 17s it would burn. If it was trimmed to 23m 18s it would not. The .mov files are 449.2 MB & 449.4 MB respectively.

Can anyone replicate this?

Edited February 22, 2019 by nharknett

[Macrossroads]

Yikes! I hope 23 minutes isn't some kind of threshold! Seriously, I'm about to trash 17 and revert back to earlier versions that actually worked. 

 

[nharknett]

I feel the same Macrossroads. Though I'd want my money refunded by Roxio. Does anyone know if Toast 16 is still available and is it 64 Bit?

 

I'm going to try other files to see if the results are the same. I've emailed Corel support about my tests and am yet to hear back from them.

Edited February 23, 2019 by nharknett

[nharknett]

Ok, I have tested two more videos. Each are .m4v over 27 minutes long. 

Neither would save as a disc image, they reached 99% encoded then failed with the -111 error. I trimmed each in iMovie to 23m 17s and saved them as .mp4 before attempting again. Each saved as a disc image successfully. I then trimmed the original files to 23m 18s and tried again. The videos did not save, -111 error. So it seems that Toast cannot burn a video over 23m 17s long.

I'll inform Corel/Roxio of this and see what they say, if anything.

If you haven't already could all that are having this problem raise a support ticket as the more people that report this problem the more seriously they'll take it, thanks.

https://www.roxio.com/en/support/

[Debecc]

Same Problem and have tried multiple configurations. Have started a ticket with no reply. 

[Franky11]

The support told me today that they already know about this problem and the developers are informed . But they do not know how long it takes until an update comes out :-( 

The software is really unusable with this annoying bug. 

[nharknett]

Thanks for the info Franky11.Would be nice if Support would have told me that. All I got from them was "We regret to inform you that we have not yet heard from our Engineering team regarding this issue, so I am assuming their investigation into the problem is still ongoing.". That was 20 days ago and I've had no further contact even though I've sent them two additional emails with the information about the movie length I posted above.

Just to check I'm doing it right, to reply to them I just need to reply to their email they sent after I put in a ticket?

Edited February 25, 2019 by nharknett

[Franky11]

Yes I think you can reply to their email . I have reported another problem too and hope to get an answer. The app crashes too sometimes if you want to drag a folder into the app (creating a new data disk but no new disk is created yet). Maybe there is a problem with long folder names. But this problem does not exist on all folder names. 

Here is the answer from Corel  for the -111 error:

25. Feb., 06:07 EST Thank you for contacting Corel Customer Service. We apologize for the inconvenience! The problem could be reproduced and passed on to our developers. They are already working on a solution, but unfortunately we have no date for it. We apologize for the inconvenience caused! For further information we are at your disposal. Yours sincerely,

[nharknett]

At least it could be reproduced but having no timeline is not good. They are basically saying 'We have no idea when we are going to be able to fix this.'. In the meantime we have a piece of software we paid good money for that is all but unusable.

[Tony Seddon]

Does anyone know if it's possible to download an older version that still works (even if it does throw up the occasional "this will need an update to 64-bit" message every so often? I bought this version new (not an upgrade) so I don't have older installers and don't know if my serial would work for older versions.

[h2oflyer]

Tony,

After a few replies to my support ticket I was contacted by Angel Babon from Corel. Use this email address mycasesupport@corel.com to contact Angel. Corel provided me with Toast 16, serial number included, to use until a fix for Toast 17 is found. I hope this helps.