Trying to burn a blu-ray here with a Lacie burner and Toast 9 software.
the file "oooo1.m2ts' could not be accessed. (Data fork, -39)
and then:
Couldn't complete the last command because of a Mac OS error. result code = -39
What is this all about?
Weird Error -39 On Mac Burning Bd In Lacie Bd Burner
Started by
dolph
, Mar 25 2008 06:47 PM
6 replies to this topic
#1
Posted 25 March 2008 - 06:47 PM
#2
Posted 27 May 2008 - 09:32 AM
Did you find out a solution to this?
I have exactly the same issue but can't get around it.
I have exactly the same issue but can't get around it.
#3
Posted 27 May 2008 - 11:01 AM
Have a look at my reply here:
*link removed*
*link removed*
#4
Posted 30 May 2008 - 08:57 AM
QUOTE (John at Roxio @ May 27 2008, 12:01 PM) <{POST_SNAPBACK}>
Have a look at my reply here:
http://forums.support.roxio.com/index.php?...st&p=206040
http://forums.support.roxio.com/index.php?...st&p=206040
I'd like to know too, please.
That link, http://forums.support.roxio.com/index.php?...st&p=206040, is broken
#5
Posted 30 May 2008 - 10:22 AM
Sorry about that, you are right, it was broken.
Basically we are going to release an updated version of Toast that has a fix for this issue. I don't yet have a firm ETA on it, but I am told it should be out soon.
Basically we are going to release an updated version of Toast that has a fix for this issue. I don't yet have a firm ETA on it, but I am told it should be out soon.
#6
Posted 30 May 2008 - 10:33 AM
QUOTE (John at Roxio @ May 30 2008, 11:22 AM) <{POST_SNAPBACK}>
Sorry about that, you are right, it was broken.
Basically we are going to release an updated version of Toast that has a fix for this issue. I don't yet have a firm ETA on it, but I am told it should be out soon.
Basically we are going to release an updated version of Toast that has a fix for this issue. I don't yet have a firm ETA on it, but I am told it should be out soon.
John, Great. Thanks. It's an encoding error, isn't it?
No workaround?
#7
Posted 30 May 2008 - 01:51 PM
Yeah, it does seem to be an encoding error with certain types of MPEG4 or H.264 files. Right now, I am not aware of any work around so the patch may be your only hope. I'll keep looking for any work around though, at least until we release the patch.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users





