Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by WayneH

  1. My first project after the update failed overnight with the dreaded -18771 error. Heavy sigh.
  2. WayneH

    New In 10.0.8

    ...other than removing the "expiring soon" warning?
  3. WayneH

    Hd Quality On Blu-Ray Vs Dvd?

    Keep an eye on your encoding settings. The bitrate settings can be no more than about 13/16 (average/max) for putting HD onto a DVD. These values work for my Sony BD player. If your player cannot tolerate settings this high, you'll suffer stuttering. The default bitrates in Toast are set MUCH lower, so that may explain why you saw a degraded result. Also be sure to use AVC, as this will give a somewhat better result for a given bitrate. I think the Toast default was MPEG-2. To be fair to Roxio, I think you WILL get the same result for a given setting. It's just that the default settings are different if you're doing a BD versus a DVD. Now a different angle on your topic: I've just compared my bluray-on-DVD project (HD video plus hi-quality photos) to the same content burned to a DVD using iDVD. A friend needed a DVD copy as they have no BD player. I wanted to see just how "bad" it was stepping back down to regular DVD. In iDVD, I was sure to use "professional" encoding to get the best possible result. Well. there is indeed a clear loss of resolution even on my 720 plasma. Score one for Toast. On the other hand, I was VERY pleased to be able to put my entire project onto a single slick looking DVD, instead of three separate not-so-slick disks as I get from Toast. The overall result from iDVD was quite nice and most folks probably wouldn't pick out the resolution difference, but it's clear if you're looking for it. PROBLEM: The iDVD version of my project was better saturated than the Toast version. I had noticed a "fogginess" to the Toast output and doing the comparison to iDVD made it clear. So now I'm wondering if there's something I can do to fix this on future projects.
  4. WayneH

    Jerky Blu-Rays From Toast 10

    When you say you made a blu-ray, do you mean a true BD or do you mean "blu-ray on DVD"? Jerkiness in the latter is often because the encoding bitrate is set higher than the red laser DVD technology can tolerate. You need to set max bitrate to ~16 and the average lower, say 13. And your results may depend on the particular player you use. My Sony BD player seems to tolerate the 16/13 setting pretty well but standard DVD bitrate is half that or even less. If you've made a true blu-ray and it's jerky, I have no clue.
  5. WayneH

    New User 18771 Error

    D'Oh! You're right - the image Toast produces is only as big as it needs to be. I was thinking it made an image as big as a disk, but of course that's not the case. I'll have to give your fix a try.
  6. WayneH

    New User 18771 Error

    Like others, I have struggled with the -18771 error. In my latest project just this week, I first tried to use 10.0.7 hoping once again it would "just work". It didn't, and I reverted to 10.0.2 which has been pretty reliable in getting through encoding. I'm VERY CURIOUS about your discovery. Please elaborate. When you get the saved disk image out of Toast, you said you burn that to disk using DU. But isn't the image from Toast much too large to fit a DVD? Sorry if that's a stupid question but I want to try to duplicate your success, and I need step-by-step details.
  7. WayneH

    Whoa! 10.0.7 on a PPC Does Chapters!

    Hmmm. I can confirm this does NOT work for me. I get chapters every 5 minutes, or whatever the duration, but no text showing chapter names and no use of chapters as assigned in iMovie. I've been passing my movies to Toast in AIC format. Perhaps your luck is a result of feeding Toast an mpeg-2 movie. Did Toast need to encode this movie or did it go directly to multiplexing?
  8. WayneH

    Error 18771

    It means you need to use version 10.0.2 to perform the encoding.
  9. WayneH

    Audio out of sync on Blu Ray

    Take a look at your source tracks. I found that when my movie ended with a fadeout, iMovie would export the movie with a sound track shorter than the movie. (Maybe FCP does this also?) The soundtrack did not extend all the way to the end of the fade. This doesn't cause a problem in iDVD (or DVDSP ?), but I think Toast expanded the soundtrack to fit the video. In my case this caused a growing sync gap that was over 5 seconds by the end of my movie. If this is your problem, it's very easy to fix. Just use Soundtrack Pro to set the audio track length to the same exact length as the movie. You can probably use QT pro to do this also.
  10. WayneH

    Toast 10 - menu text missing

    Wow, this is huge for us G5 folks. When you add in the -18771 error issues, it's clear that G5 users should stick to 10.0.2. I've asked before but I'll ask again - What are we missing by being "stuck" back at 10.0.2? I'm trying to weigh the advantages/disadvantages of 10.0.2 versus, say, 10.0.7.
  11. WayneH

    Does Toast 10 support 1920x1080?

    A "quicktime movie" could include anything playable using QT, so the term alone really doesn't mean anything. With all the codecs and settings combinations, the options are endless. MPEG-4 doesn't tell the whole story either, but in general it means H.264 compressed (=AVC). That's the best codec around and commonly appears on BDs, but it also allows for many settings. For instance it's often used for preparing iPod movies,and those wouldn't look so good if you're trying to get blu-ray quality. I've had luck exporting from iMovie to AIC and encoding that with version 10.0.2. Take care to be sure your encoding settings are "AVC" at an appropriate bitrate (<17 if you're going onto a DVD). Then take the .264 made by Toast and drag it into the Toast window of version 10.0.7 so that multiplexing and burning can continue in the newer version.
  12. WayneH

    Toast Error code -18711 What does it mean?

    It's maddening, but at least the tip I gave above has solved it for me ~90% of the time.
  13. WayneH

    error: -18768

    Try an experiment: Turn down your encoding bitrates to below 18 Mbps, which is the limit for the red laser technology of DVDs. Try anything less than 15 avg. and 17 max. I've had success with those values. This may or may not solve your error, but either way it will make for a smoother playing disc. Higher bitrate burns, even if they succeed, will cause jerky movement and other errors on playback.
  14. WayneH

    Toast Error code -18711 What does it mean?

    I responded to this question in another thread: http://forums.support.roxio.com/index.php?showtopic=64990
  15. WayneH

    Does Toast 10 support 1920x1080?

    I think you mean the dreaded error -18771. It's gotten a lot of attention in this forum. The only workaround I know of - and I can vouch for since it's what I've been doing - is to use version 10.0.2 for encoding. Save your Blu-ray DVD to a disk image and then rescue (without quitting Toast) the .264 and .ac3 files it makes in the Roxio Converted Items folder. By rescue I mean move them out of that folder, otherwise Toast will delete them. You can then drag the .264 file into the 10.0.7 window. It should find the audio file by itself, or you can help it if need be. Now when you save to disk, Toast will proceed directly to multiplexing and not re-encode. If it all goes smoothly, then go ahead and burn a DVD. You could skip 10.0.7 altogether if you're happy with the disk image from 10.0.2. But that version has "issues" with chapters that are addressed by the later versions. I don't know why, but the older version seems to give a much higher success rate at encoding. And I believe it may be faster also.
  16. WayneH

    Previewing Blu-Ray Video DVD

    I know you don't want to hear this, but maybe you should "just" rebuild your slideshows in iMovie or iPhoto or even iDVD. It's very easy in both and you have tons of control easily available; cropping, Ken Burns effect, straightening, music placement, various cross fades, etc. I've never used Roxio tools for making slideshows, so I can't really help with that. Hopefully someone here can. BTW, have you tried simply burning your project to a disk image? You could then mount the image and use DVD Player to play it just like any DVD. If the image works, burn it to disk. Otherwise trash it and make changes before trying again.
  17. WayneH

    Read this before updating to Toast 10.0.7

    Can you elaborate on specific differences (introduced bugs?) between 10.0.6 and 10.0.7 ?
  18. WayneH

    No relief from -18771 error with 10.0.7

    Aaarrrrgggghhh! The image was "burned" successfully but at 4.5 Gb, it's a rat hair too big to fit on a DVD (max 4.38 Gb, according to Toast). Why the heck will it allow saving a DVD disk image that it can't burn to a real disk? That's a cruel tease. Is there some trick I might use to squeak under this limbo bar? I guess I'll have to bring the bit rates down a little on one of the sections to squeeze it just a little bit more. So near and yet so far.
  19. WayneH

    No relief from -18771 error with 10.0.7

    Success at last !! At least I'm done multiplexing and proceeding to burning a disk. We'll see how it works on my BD player soon. As many have suggested, I retreated to 10.0.2 and encoding finished without a whimper. No -18771 error, and no re-encode at multiplexing. With identical settings that produced a failed file in 10.0.7, the older version produced a file about 6 Mb larger, out of 800Mb. Odd. I'm nearly certain that the encode with 10.0.2 was also quite a bit faster than with 10.0.7. Again, odd. Since I'm preparing my disk in 10.0.7, using a file or files encoded by 10.0.2, am I missing anything? I mean, I think I'm getting the best of both versions this way, and it's no bother because I'm pausing the process anyway on purpose, so I can add the surround .ac3 in place of the sound file encoded by Toast. This might be a good approach in general - encode in 10.0.2 and prepare the disk in 10.0.7 - to avoid encoding problems, for those folks plagued by this problem.
  20. WayneH

    No relief from -18771 error with 10.0.7

    Can you elaborate on your source material, source, resolution, codec, and so on? I'm looking very hard at poorly rendered titles prepared by iMovie 09 at high res as the major suspect in my problems. If I delete titles and re-export from iMovie, I'll often get a success. Testing takes so long it's hard to be definitive about anything.) I suspect, as tsantee suggested, that missing or damaged frames are at the root cause of the Toast encoder choking. In my case it's titling causing the problem, but I imagine there are other ways a video file could be seen as undigestible. Changing direction, what are the chances that Roxio simply bought the encoding engine and cannot really fix things that are internal to that code? I've seen this sort of thing in corporate software many times. A company pays a contractor to develop a solution. The developer meets the specs, gets paid and moves on. Any problems that later appear in the software are just tough nookies. You either have to live with it or try to re-hire the developer to come back and fix it.
  21. WayneH

    Re-encode frustration

    See this post for my workflow. http://forums.support.roxio.com/index.php?...mp;#entry328985
  22. WayneH

    Re-encode frustration

    I searched for quite a while - without success - for H.264 settings that Toast would accept without re-encoding. I was hoping to use Apple's Compressor to do the encoding instead of the Toast encoder in hopes that Compressor might do a better/faster/more reliable job of encoding. The only file I can get to work is the one produced by Toast itself and placed temporarily in the "Roxio Converted Items" folder. Many thanks to tsantee for that tip.
  23. WayneH

    No relief from -18771 error with 10.0.7

    Glad to hear it worked so well for you. It works for me too, just not reliably. I'm envious of your Intel-powered encode times!! FWIW, I re-ran overnight my encode that failed yesterday but this time I started with the same movie but without the audio. The encode finished and when paired with my .ac3 surround file, it went ahead thru multiplexing. So the cure for -18771 in this case was to remove the audio track. Maybe a coincidence, or maybe a clue.
  24. WayneH

    No relief from -18771 error with 10.0.7

    Hah! Well that made me chuckle! Coming from the approach that I want it to "just work", I think I'd rather have hemorrhoids than subject myself to any more testing than I've suffered already. Workflow details: I'm working on a dual G5 PowerMac, using Leopard 10.5.8 and iMovie '09 to edit HDV footage from my Canon camera. From iMovie, I've been exporting to AIC 1440 x 1080, with PCM Big Endian sound at 16 bit, 48kHz. (I haven't nailed it down, but in general it seems more likely to make it thru an encode if I delete the sound track first. That's fine for my workflow, read on.) The movie file is dragged into the Toast window, with the Green background and the Blu-ray to DVD options selected. I've set the encoding to AVC at 15 average, 17 max, because I'm trying to max out the quality. It may be borderline but it does work in general. I click on "save as disk image" and, when it works, rescue the .264 file that shows up in the "Roxio Converted Items" folder. Don't quit before you move it! Audio goes a different way. I drag the movie file into Soundtrack Pro and export the audio as a pair of mono .aif files, one for each channel. Oh, important step here, I make sure the audio timeline matches the video exactly in length. iMovie will actually export a shorter audio file when the move ends with a fade to silent background. In Toast, a short audio file will later be stretched to fit the video, and this causes havoc with sync. Been there, done that. Anyway, then I drag the L and R files into Compressor and let it prepare an .ac3 file surround mix. My "simple" mix is just duplicating the fronts to the surrounds, and letting Compressor make an LFE and center channel. I've also made a more complicated mix with music, which is what started this awful torture. The video and audio are reunited by giving them the same name, eg. movie.264 and movie.ac3, and placing them in the same folder. Then when you drag the .264 into the Toast window (same settings exactly as before), it will find the audio file and mate it up. If it doesn't see it, it'll ask. Then when you hit "save to image" again, and all goes as hoped, it will skip re-encoding and go straight to multiplexing. No sweeter feeling than when it works! My current project was one big movie and one smaller one. To isolate my problems, I ended up slicing the big piece into 3. So of the 4 total pieces, all 7-11 minutes now, 3 can be placed together on a disk image successfully using the process above. I'm struggling now with the 4th and final piece. FWIW, I do see timing issues where Toast sees the .264 as being a different duration than the movie file it started as. That seems likely to cause problems but the file with the worst discrepancy is working fine. I've also suspected that titling errors caused by iMovie might be mucking things up. iMovie seems to have trouble exporting titles at HD resolution (dropping down a bit in res clears it up). My one remaining problem piece does contain some "fancy" moving titles. They look OK when previewed in Quicktime (unlike some others I've removed) but I'm wondering about them. Deleting them is probably the next thing to try if the current encode fails. That's about all I can think of. It's a tough nut and I swear I've had success by simply re-trying a failed attempt. Hardly a solution. Oh, another wild idea: Is it possible a Toast encode can fail simply because it has taken so long? I mean, these things have sometimes gone two days just to quit unexpectedly at the end, but not before deleting the encoding .264 file. Could it be that the Mac's maintenance scripts are interfering, or the change in date is confusing Toast? Just grabbing at straws here, but it does see that the separate pieces are far more likely to succeed than one big file.
  25. WayneH

    Perplexing Multiplexing

    All correct. And the re-encode only starts when the movie-only is paired with the surround .ac3 file. I suppose the re-encode is triggered because Toast "thinks" the movie is 19:44 instead of the real length of 10:44. I have a clue: I just discovered a blotchy and flashing title exported from iMovie in this particular movie. (This is a known issue with HD exports from iMovie - some of the moving titles cause this.) This is one glitch unique to this clip compared to my other 3 that work fine. I've removed this offending title altogether and I'm re-exporting the project now. It will be tomorrow before I know if this cures the problem in Toast.