Please provide more information so that we can help you out in a better way.
- Are you using Windows or Mac?
- At what point do you get the error?
- Is this happening with a specific project or with all the projects.
Refer to the below article for troubleshooting burning issues.
Please reply if you need further help.
Thank you for posting on Adobe Forums.
Meantime, please do not repost the same question several times to this forum. You've posted the exact same question at least three times in the last day.
To avoid confusion, I've removed your duplicate threads.
Answers will be in the details.
What version of Premiere Elements are you using and on what computer operating system is it running?
Are you burning to DVD-VIDEO on DVD disc or AVCHD format on DVD disc?
Although the following usually comes with Vobulator message rather than Transcoding message, I will ask anyway "Do you have
a stop marker at the end of the last item of your Timeline content? Do you have menu markers on that Timeline and have you checked the spacing between them? If applicable, check menus for overlapping buttons.
Also, please expand your Timeline to the max with the -+ slider above the Timeline and look for very thin vertical black lines scattered among the track(s) content. These are fragments of clips which need to be deleted. Also, look for other irregularities in transitions, audio, titles placements.
We will be watching for your results.
Also, please review the link posted in post numbered 1.
Please try Burn to Folder (Burn to folder is under DVD burn options). Is this working fine? this will isolate that problem is not with timeline and markers.
Many troubleshooting suggestions including the burn to folder part of the troubleshooting have already been brought to the attention of souphiemay.for the "transcoding error" issue.
However, without details from souphiemay and follow up by this user, none of us can help. We have not heard from souphiemay beyond the original message
cannot burn to dvd massage says transcoding error
and that was back on February 28, 2014. It is now March 21, 2014.
We look forward to further information from souphiemay - either problem solved and how or the information needed for troubleshooting to a successful conclusion.