Alludo USER to USER Web Board

I am using VS11.5+ and have recently returned from a trip with footage from a Sony SR12. Until I get a chance to edit I'm combining all clips from each day into single files so I can view them on the TV, streaming through the PS3, as the PS3 only displays each clip separately and doesn't appear to have any play all continuously type option. I'm rendering the files to the "Blu-ray PAL HDMV-1920" setting and this is working successfully with most of my files except for files from one particular day, when I get an error after rendering to approx 25% saying "Frame 158 is unreadable" with error code "(18005:1:1)". I have no idea which clip is causing the problem and have tried removing several clips without success. I removed clip 158 in the project but that wasn't causing the problem.

I've also tried rendering to the "AVCHD H.264 (1920 x 1080 25.00 fps)" setting but it hangs at 25% and doesn't go any further.

I have just bought a new PC (details in my profile) but I had the same problem with this error message on the same set of clips on my old PC too.

I have a Blu-ray burner in the new PC and have made several test discs in VS11.5+ but I've now found out that the PS3 won't play burnt BD-RE discs. It will play AVCHD data discs recorded onto BD-RE or DVD-RW so I can play my combined files that way or by streaming from the PC. Unfortunately it doesn't appear that I can make an AVCHD disc with chapters onto a BD-RE disc. I only see options in VS11.5+ for AVCHD 1.4G, 2.6G, 4.7G & 8.5G.

I would appreciate any suggestions on how to find the clip that would be causing the problems.

Am relatively new to AVCHD editing in VS11.5+ and have just experienced the same problem although had to date have successfully rendered several hours of video (albeit rather slow even on a quad with 4GB of RAM.) The output format is PAL DVD 16:9.

My render failed with the same error 18005:1:1 at frame 693. What I did eventually figure out (after much messing about as the problem didn't occur until clip 60 in the sequence), was that the frame counter refers to the frame number in the current clip i.e. clip 60, not the clip number. This clip was about 30s long, and so at 25fps, the bad frame occurs at frame 16 in the 28th second (as 691 = 27 secs x 25fps plus 16).

Just to prove the point if I step through the clip frame by frame at position 27:16, the picture in the edit view disappears.

So in your case, unreadable frame 158 will be at position 06:08 in the "bad" clip

The only way around this appears to be to watch the render to see which clip the error message appears at, and then remove the offending frame.

Fortunately this was the only bad frame in over 3 hours of footage taken on holiday, so I suspect it may be a bad sector on the card (The source files are from a Sony CX6 memory stick camcorder).

It is very frustrating that the programme can't tell you which clip has the problem, or the clip filename, and I would be interested to know if you¡¦d had any further feedback on this, as more frequent repetitions will make editing simply too cumbersome. It took me all day to produce a 7 minute movie !!!