Why am I losing my marker comments in Premiere Pro CS6?

I'm working on a project that has a ton of interviews.  Typically I go through them and set markers for each answer to a question.  I'll type notes for each marker in the "Markers Panel" so I can easily go back and know what was said without having to re-watch.  When I'm done for the day, I'll save my project (which I do quite frequently throughout) and close down.
When I return and open my project, my comments are completely gone.  And my marker in and out points are reset.
Has anyone every come across this issue before?  I've tried to save as a new project but still have the same problems.  Please let me know.
I'm running Premiere Pro CS6.  The footage is Canon 5D Mark ii.

Okay, that's good to know.  A little surprised that's not fixed in CC.  Thanks for the help!  Hopefully there's an update to resolve this for everyone.  It's just weird because the history panel notes that I have made comments.  Oh well.  Looks like this will just take a little longer than expected.

Similar Messages

  • Why do I get choppy playback in Adobe Premiere Pro cs6?

    The playback is really choppy.
    What I am using:
    (Brand New) iMac
    Processor  3.2 GHz Intel Core i5
    Memory  16 GB 1600 MHz DDR3
    Graphics  NVIDIA GeForce GTX 675MX 1024 MB
    Nikon D5100 DSLR
    Shot in 1080i 30 fps
    Thanks

    I cannot believe how bad the playback is in Premiere Pro CC, and, how little help there is out there. Raw MOVs from a 5D plays back like garbage on my laptop or 8 core Mac Pro. Its ridiculous. I'm better off transcoding to ProRes and using FCP which works, or God forbid, go back to using Avid like its 1999. Unfortunately It has nothing to do with the two graphic cards or 32 gigs of memory I have either, it just plays back like garbage. Using the JKL keys is completely awkward because the lag between hitting the key and playback is excruciating. I'm at 1/2 resolution and it cant play back footage without being choppy. no FX, and the footage and hardrive is on a 6g SSD. This should be screaming.
    Adobe, seriously, live up to your other products standards, they are so good, why does this one just bomb?

  • Why are Adobe Premiere Pro CS6 source and program monitors playing each others footage?

    Why are Adobe Premiere Pro CS6 source and program monitors playing each others footage? I import my footage into the project like normal. I drag it to the source monitor on the left hand side to set in and out points then I drag it to the time line. The footage drops into the time line with no problem but when I go to play the footage in the time line it plays back on the source monitor and not on the program monitor like it is suppose to. Other times ill drag the clip to the time line and trim it there and it will be fine and show up on the program monitor.  Then ill go try to set a clip to have in and out points (which is suppose to show up in the source monitor) but it shows up in the program monitor. The clip is not even in the time line it should not be on that monitor! I have updated the program to the late update. I have re installed the program numerous times and I have even ran the Adobe Clean up program. Couldn't find much on this problem. Please help thank you! I have a PC. My computer is also way over the recommended minimum specifications to have the program installed on.

    Definitive Answer (I believe): It's all about this setting, "Write XMP ID To Files On Import" - which confirms that Adobe Premiere Pro is deliberately modifying the .mov file: http://helpx.adobe.com/premiere-pro/using/preferences.html#WSE3BD4A43-7022-4fe6-97F5-95313 935347B
    These posts give some background as to why having this setting enabled would be beneficial: one benefit being to be able to skip conforming files by matching the conformed file with the original using the embedded XMP tag :-
    http://helpx.adobe.com/premiere-pro/using/preferences.html#WSE3BD4A43-7022-4fe6-97F5-95313 935347B
    http://www.dvinfo.net/forum/adobe-creative-suite/498627-why-premiere-modifying-video-files .html
    https://forums.creativecow.net/thread/205/876064
    (Found using Google search term "adobe premiere pro date modified")

  • Why Do I get Choppy Playback in Premiere Pro CS6

    Before upgrading from CS5.5 to CS6 I wiped my computer and started from scratch. When editing 4 angles in CS5.5 I never had any problems with playback... even after adding titles, effects..
    In CS6 I have my 4 files set into a multicam sequence but when I play back and start cutting from cam to cam it gets choppy.
    I am running:
    Windows 7 64bit
    On a Dell Studio XPS 9100
    Intel Core i7 930 @ 2.80GHz
    12.0 GB Ram
    ATI Radeon HD 5800
    I have my memory preferences in PR set to 12 GB Installed, Ram for other aps = 3 Ram fpr PR 9GB, and it set to performance
    Any help to speed up and render this proper would be great, Still have to add color correction, titles, logo.

    The 1st update came out today. Downloading now. Looks like it should fix my old problems... fingers crossed
    What's new in Adobe Premiere Pro CS6 6.0.1:
    May 26th, 2012
    Features added or changed in this update:
    · Improved performance using OpenCL, especially when used on Mac OSX v10.7.4 or later.
    · Added encoding presets with additional bit-rate settings for XDCAM HD.
    · Added Automatic Peak File Generation preference in the Audio category for turning off automatic peak file generation for imported audio. By default, this preference is enabled and matches the behavior of Premiere Pro CS6 (6.0.0).
    · When this preference is disabled, importing audio or opening projects will not cause peak files to be generated. If peak files were already generated, then waveforms will be visible. Files imported before the preference was disabled will continue to generate peak files.
    · Enabled “smart rendering” and added Enable Smart Rendering Codec setting to the Video tab of the MXF OP1a exporters for XDCAM HD and XDCAM EX to enable or disable smart rendering for these formats. This option defaults to the off/disabled state. We’ll have more information about this feature in a post on this blog within a day.
    Bugs fixed in this update:
    · Start timecode was not imported or exported correctly when working with AAF files.
    · Some files from the Canon 5D Mark III camera were imported with the wrong timecode.
    · Playing/viewing waveforms in the Source Monitor caused audio dropouts with some XDCAM HD clips.
    · NTSC MXF OP1a files that were exported with drop-frame timecode had video data that was tagged as non-drop-frame.
    · Switching the Renderer project setting from Mercury Playback Engine Software Only to Mercury Playback Acceleration GPU Acceleration on a computer using OpenCL caused Premiere Pro to crash under some circumstances. Switching between the two settings on a computer using CUDA would in some cases cause problems with video and/or audio playback.
    · Crash when using full-screen, cinema mode on some computer systems.
    · Tape capture was not working correctly with some third-party systems.
    · Crash when capturing from tape using some BlackMagic hardware.
    · An extra, black frame was included at the end of the output when exporting to P2 MXF in some circumstances.
    · First two frames were being played twice on external monitor using Matrox MXO2.
    · Crash when using “hover scrub” with Matrox MXO2.
    · Audio/video synchronization was off by a few frames when playing video on external monitor.
    · The Export Frame button was not exporting the correct frame, instead exporting a frame one or two frames away from the current frame.
    · Some audio files and some MXF files would go offline or have their audio reconformed when the project was re-opened or when Premiere Pro was minimized or lost focus.
    · Crash when modifying an effect property while playback was occurring.
    · Hang/freeze when using a dissolve transition on an adjustment layer.
    · Dropped frames and audio/video synchronization issues when exporting to tape using some third-party hardware.
    · Information about dropped frames on output to tape was not accessible to third-party systems.
    · Some QuickTime files were imported with the wrong field order.
    · When audio was sent through a Mercury Transmit plug-in, any number of channels that was not 2 or 6 was treated as mono.
    · In HDV editing mode, File > Export > Tape could not be used with third-party hardware.
    · The current-time indicator (playhead) was not returning to the current time after using the Play Around command.
    · Last several frames of output when exporting to tape were black.
    · When encoding a 23.976 fps video to H.264, the duration of the video in the output .m4v file was too short, and audio drifted out of synchronization with the video.
    · Transparency (alpha channel) information from a dynamically linked After Effects composition was rendered incorrectly in Premiere Pro.
    · Importing some QuickTime OP1a files caused Premiere Pro to hang.
    · The duration of the audio track sent to SpeedGrade using the Send To SpeedGrade command was the length of the entire Premiere Pro sequence, not the length of the work area.
    · Timecode written to trimmed clips using the Project Manager did not match the source timecode for some QuickTime files.
    · Various other crashes.

  • Why can't see the timeline audio waveform on sequences inside another sequence in Premiere Pro CS6? Can I fix this?

    Does anyone know why I can't see the timeline audio waveform on sequences inside another sequence in Premiere Pro CS6? Can I fix this?

    PERFECT!!! THANK YOU, Ann!!!

  • Why is Premiere Pro CS6 crashing during render at 50% completion?

    I am running Premiere Pro CS6 on MacBook Pro, flash drives. The Mac is brand new. Nothing else is running. No other non-factory programs are installed.
    Regardless of what I do, during export to any output type, Premiere crashes when it's rendered to 50%.  I take the same project and only render part; crash at 50%. I try another new project, with nothing but a single video file, crash at 50%.
    <frustration>I am about to run to Final Cut, and I really don't want to. I am losing money and time that I don't have.</frustration>
    Any feedback would be majorly appreciated.
    Thanks,
    Aaron

    ...MacBook Pro, flash drives....I take the same project and only render part; crash at 50%. I try another new project, with nothing but a single video file, crash at 50%.
    Make sure you are not running out of available space
    on your target drive for the export.

  • Why will Premiere Pro CS6 only import to mpeg format?

    Hello, so I've been using Premiere Pro CS6 now for only a few months and when I imported (using "capture" or F5) and tested some footage  from a HDV camera using a miniDV tape, I noticed that Premiere Pro would only import to mpeg format. I looked up ways to change this but couldn't find anything. So in short I'm asking if there is a way to change import format so that whenever I do import from DV tape, it isn't mpeg?
    Thanks!

    ...footage  from a HDV camera...
    ...only import to mpeg format.
    HDV capture will always be mpeg.
    whenever I do import from DV tape, it isn't mpeg?
    DV capture will be .avi (pc) or .mov (mac).
    note:
    Capture from tape, import file based media.
    Capturing and digitizing
    Also, what's the problem with mpeg?
    Why are you determined to change it?

  • Why is Premiere Pro CS6 (perpetual) reverting to Trial Mode?

    I purchase 11 copies of Premiere Pro CS6 over a year ago. This is not a subscription!
    I have had to "re-license" these copies for the third time as they continue to revert to trail mode.
    This is accomplished by signing into my adobe account.
    This is very annoying......
    Can anyone explain why this is happening?
    Cedric Jefferson
    Wheaton College

    Bewildered14,
    Sorry you're encountering this problem. See if this document helps explain your situation: http://helpx.adobe.com/creative-suite/kb/trial--1-launch.html
    Stefan

  • Mercury Engine in After Effects CS5.5? Or, why is After Effects so much slower the Premiere Pro?

    Take this quote :
    "by Todd Kopriva on Apr 25, 2010 at 8:08:14 am
    'Mercury' is a marketing name for these performance improvements in Premiere Pro: - multiprocessing
    - multithreading
    - 64-bit application
    - use of CUDA to to some processing on supported hardware 
    The first three of these are in After Effects CS5. (The first two have been in After Effects for much longer.)"
    However, if I drop my Canon 5D Mark II footage (h264) into Premiere Pro it plays back SO MUCH better then the exact same footage in After Effects. Why is that? I DO NOT have an NVideo card and I have NOT applied any effects or scaling to the clip, just raw footage dropped into each program.
    I do notice that After Effects has to render to play back (green bar being generated above footage). But it does slow very slowly, like 9fps. Premier Pro seems to cruise right along at near realtime. This is 24fps 1080p footage. One other point of interest, I have encoded the clip into Cineform codec as well. On Premier Pro I can tell a difference, the cineform scrubs a lot smoother then the original H264 clip. But, again, in After effects both the h264 and Cineform clips are very slow to render and scrub.
    Any improvements along these lines for CS5.5?
    Am I just missing something obvious?
    Thanks for any info,
    --greg.

    Gregory Seattle wrote:
    I think the problem is that hitting the space bar and hitting '0' (ram preview) both draw that green bar, and both seem to use it if it is already there. I guess the real difference is how that green bar gets generated. It does seem to get generated faster when I ram preview as opposed to hitting the space bar. Using both cores I have I guess (early 2009 24" iMac).
    When you hit the space bar, AE TRIES to play back as it renders each frame.  Imagine what happens if it's a comp with 120 3D layers that all accept lights and cast shadows.  That's why you don't use the space bar.
    In a RAM Preview, AE fills up the memory available to it with rendered frames, then plays them back from RAM.  Depending on processor speed, dimensions of comp & frame rate, this may or may not be real time, but there are ways to get real time.  With the space bar, you don't stand a chance at real time.
    Gregory Seattle wrote:
    From what I hear new iMacs are due out soon with the new Thunderbolt (!) and Sandy Bridge processors/chipsets. Should be a LOT faster then what I have now.
    For AE work I'd say maybe yes, maybe no.  To make AE REALLY speedy, you need a lot of processor cores and a boatload of RAM.  iMacs aren't known for either of those things.

  • Import of Shot Marks / Essence Mark possible with Premiere Pro CC?

    Shooting news is a matter of time! I shot outside by using the button "shot mark" on my Sony PMW 320
    It would be very helpful to see this marks in Premiere Pro to find the important frames quickly like Sony Vegas or AVID does.
    I do have made a feature request.
    Any hints or workarounds?

    I am having the same issue.
    Your best bet is to logon to Adobe website and go to customer support. If you chat with someone they can go on your computer and trash all your preferences. Your computer will be stable again. It worked great for me, but I just imported an XML from Resolve and it is crashing the system again.
    Good luck. 

  • P2/MXF Footage in Premiere Pro CS6 constantly losing its linkage.

    P2/MXF Footage in CS6 constantly losing its linkage.  I'll relink the clips as the 'locate footage' box pops up, then a couple of minutes later, all the clips in the bin are showing the question mark and asking me to locate the clips again. It does this over and over.  This happens on both my desktop machine and on my laptop.
    Not having this problem with any of the file types at this point.

    Just saw an official reply on another similar question asked at the same time as mine and that Adobe is aware of it and it's being worked on. 
    Thanks.

  • Premiere Pro CS6 Warp Stabilizer not using GPU/CUDA why?

    Hi,
    I installed CS6 and tried the Warp Stabilizer, I undestand that only part 2 of the process (stabilize part) is GPU accelerated, but I can't get any acceleration from GPU, my GPU is idle at 1% usage (GTX580) and all the processing is going to CPU. The renderer/playback is marked CUDA so its not that.
    Is there anything I'm missing?
    Thanks

    OK, this surprised me a bit. I have a state-of-the-art new PC with plenty of RAM, a fast processor and lots of cuda cores. See the specs here: http://www.stevengotz.com/
    It took over 10 minutes to stabilize one minute of video - 1800 frames. It wasn't all that shaky to begin with, but it was handheld and therefore looks better after using Warp. There was one section that was so bad, I sliced the clip up and chose not to stabilize that part after the fact. So I thought that it might have added a little to the problem. But no. I tried just 180 frames of reasonably stable hand held video from the same clip and it took almost a minute.
    Now, once the process was finished, I had no problem playing it back in realtime without rendering. But what is taking so long? I understand that there is a lot of work to do, but why isn't it using the power I have provided?
    This is a screen shot of my resources about two minutes into the process.
    I would love to know what I need to do to speed up this process. I get that it is working in the background. Is it possible to make it work in the foreground? I would not mind if it maxed out the RAM or the CPU or both if it would help.
    edit: I just submitted a Feature Request to let Warp run in the foreground using every available resource.
    Steven
    Message was edited by: Steven L. Gotz to include additional information.

  • Cannot install Premiere Pro CS6 and Prelude - Losing my mind

    I've been trying for 3 days to find a solution to this problem. I know a lot of other people have had this problem but the solutions all seem different based on the interpretation of the summary report generated by the installer. I've tried dealing with Customer Support over the phone and they have absolutely no idea how to fix this. I've downloaded and installed the CS6 Production Premium. All apps install successfully except for Premiere Pro and Prelude. One option I read was to remove a few Adobe fonts (which I tried) and the problem still exists. Adobe Suport suggested uninstalling then reinstalling Air. Tried it and things still aren't working. I even tried installing in Safe Mode. I'm on a Mac running 10.6.8
    This is the summary:
    Exit Code: 6
    Please see specific errors and warnings below for troubleshooting. For example,  ERROR: DF015, DW063 ... WARNING: DS013, DW066 ...
    -------------------------------------- Summary --------------------------------------
    - 0 fatal error(s), 18 error(s), 6 warning(s)
    WARNING: DS013: Payload {298CF0B0-8B47-46DF-B726-8E4BFAD5432E} AdobeHelp 1.0.0.0 is already installed and the session payload {AA0D312F-1570-4E7E-9A7D-E191E0090FEC} AdobeHelp 4.0.0.0 has no upgrade/conflict relationship with it.
    WARNING: DS013: Payload {CD693E49-C5EF-4FA6-9037-9B636931C02B} AmericanEnglishSpeechAnalysisModels 1.0.0.0 is already installed and the session payload {C5CA53A2-E722-4D76-B5AC-71522CC48AB3} AmericanEnglishSpeechAnalysisModels 3.0.0.0 has no upgrade/conflict relationship with it.
    WARNING: DS013: Payload {A8798E04-96FF-4564-9157-0D4C89CB794C} DynamiclinkSupport 5.0.0.0 is already installed and the session payload {DE88AA40-6766-43D3-A755-8FC374B3D2C3} DynamiclinkSupport 6.0.0.0 has no upgrade/conflict relationship with it.
    WARNING: DS013: Checking payloads upgrade/conflict relationships : Failed with code 1
    WARNING: DW066: OS requirements not met for {42CED1DA-1C36-45D2-88C0-C32DB6B82B49} Adobe Premiere Pro CS6 6.0.0.0
    WARNING: DW066: OS requirements not met for {D094CE41-D4F5-473E-8915-B1D026CB193E} Adobe Premiere Pro CS6_AdobePremierePro6.0en_USLanguagePack 6.0.0.0
    ----------- Payload: {CC006FD6-00EF-46FC-ACA0-7A28EFF44D20} Adobe Media Encoder CS6 6.0.0.0 -----------
    ERROR: DF015: Unable to delete symlink "/Applications/Adobe Media Encoder CS6/Adobe Media Encoder CS6.app/Contents/Frameworks/AdobeXMP.framework/Resources"(Seq 647)
    ERROR: DW063: Command ARKDeleteSymlinkCommand failed.(Seq 647)
    ERROR: DW050: The following payload errors were found during install:
    ERROR: DW050:  - Dynamic Link Media Server: Install failed
    ERROR: DW050:  - Adobe CSXS Infrastructure CS6: Install failed
    ERROR: DW050:  - Adobe Premiere Pro CS6: Failed due to Language Pack installation failure
    ERROR: DW050:  - Adobe Prelude CS6 Support: Install failed
    ERROR: DW050:  - Adobe ExtendScript Toolkit CS6: Install failed
    ERROR: DW050:  - Adobe Extension Manager CS6: Install failed
    ERROR: DW050:  - Adobe Bridge CS6: Install failed
    ERROR: DW050:  - AdobeHelp: Install failed
    ERROR: DW050:  - Adobe Prelude CS6_AdobePrelude1en_USLanguagePack: Install failed
    ERROR: DW050:  - AmericanEnglishSpeechAnalysisModels: Install failed
    ERROR: DW050:  - Adobe Media Encoder CS6: Install failed
    ERROR: DW050:  - Adobe Premiere Pro CS6 Support: Install failed
    ERROR: DW050:  - Adobe Premiere Pro CS6_AdobePremierePro6.0en_USLanguagePack: Install failed
    ERROR: DW050:  - Recommended Common Fonts Installation: Install failed
    ERROR: DW050:  - Adobe CSXS Extensions CS6: Install failed
    ERROR: DW050:  - Adobe Prelude CS6: Failed due to Language Pack installation failure

    Hi Mylenium. Yes it's me. I didn't want to pull Steve into this just yet hoping that there was an easier solution. I've gone 2 rounds now with Tech Support. The last advice they gave me was to uninstall all Adobe applications from my system, delete all the files that don't get removed when uninstalling (they gave me a whole list), run the Cleaner Tool, log in as the Root user and run the installer again. The same error came up so I'm starting to think that the problem may be more than an Adobe issue. Support told me to call back if the last solution didn't work and they would "send me to the next level". What a pain....

  • Why Do Both Photoshop CS5 (64 Bit) and Premiere Pro (64 Bit) Crash on Start up.

    Both Photoshop CS5 (64 Bit) and Premiere Pro (64 Bit) Crash on Start up. 32 bit version of Photoshop works fine.
    Here is the problem signature when they crash.
    Problem signature:
      Problem Event Name:          APPCRASH
      Application Name:          Photoshop.exe
      Application Version:          12.0.0.0
      Application Timestamp:          4bbc5b10
      Fault Module Name:          CoolType.dll
      Fault Module Version:          5.7.82.7602
      Fault Module Timestamp:          4b980c97
      Exception Code:          c0000005
      Exception Offset:          0000000000073a92
      OS Version:          6.1.7601.2.1.0.256.48
      Locale ID:          1033
      Additional Information 1:          7c82
      Additional Information 2:          7c821a1fc13b00b508d1bb6ee7ecaf44
      Additional Information 3:          019c
      Additional Information 4:          019cb6db15489631b8a43faf27e30830
    Problem signature:
      Problem Event Name:          APPCRASH
      Application Name:          Adobe Premiere Pro.exe
      Application Version:          5.0.3.0
      Application Timestamp:          4ce382d1
      Fault Module Name:          CoolType.dll
      Fault Module Version:          5.7.82.7449
      Fault Module Timestamp:          4b7b1af3
      Exception Code:          c0000005
      Exception Offset:          00000000000739ea
      OS Version:          6.1.7601.2.1.0.256.48
      Locale ID:          1033
      Additional Information 1:          889a
      Additional Information 2:          889afed61eb6ddf1c1c3419adc6026b6
      Additional Information 3:          8235
      Additional Information 4:          823549a371dff618695395cc0a8514ee
    Both are referencing cooltype.dll. I ran Font Doctor on all system and non-system fonts and found no errors. Booted without Extensis Suitcase loading. Nothing works. All 32 bit programs work fine. Any clues would be appreciated.

    It does not necessarily mean a "corrupt" font, but can be a font that PrPro, and PS, cannot handle.
    Though I have read that changes have been made, Open Office's DejaVu font would crash PrPro's Titler - every time. There are quite a few others. Font Dr, and similar utilities, will not see the font(s) as corrupt, but they are so poorly designed, that PrPro and PS cannot deal with them.
    Though it can be a long, drawn out process, one can often zero in on the problem font(s), with a little work. This is accomplished by first defining the "System Fonts," and not touching them. Then, uninstall half of the remaining fonts, and testing PrPro and PS. If they launch fine, you know that somewhere in that list of fonts, the problem exists. If there is still a failure to launch, chances are good that the problem font(s) reside in that half, that are still installed. Note: because the problem still exists, does not guarantee that there are NOT problem fonts in that uninstalled group, so keep that in mind.
    Repeat the proces, by uninstalling half of the remaining fonts and testing.
    If necessary, repeat by removing half of the now remaining fonts and testing.
    When you get to a point, where you are no longer getting problems, reinstall fonts, in small groups, testing in between. The smaller the groups, the easier it will be to pinpoint the problem font(s).
    Keep notes on which fonts you are uninstalling and reinstalling, until you narrow it down to the problem font(s).
    I would start by uninstalling any "free fonts," and then commercial, 3rd party fonts. A lot of free fonts are just poorly designed, and can cause issues, though they might work fine in some other programs.
    I use a font manager, so that I only have ~ 350 fonts installed at one time, and then dynamically install fonts, as needed for Projects. That keeps my machine clean, and if, upon installation, I get a crash/hang, I know that at least one font in that Set is causing it. This helps, as my workstation has ~ 19,000 fonts on it, and some are free fonts, and many are from 3rd parties. Some are also very, very old.
    Good luck,
    Hunt
    PS - one common cause for hangs on loading PrPro can be from VST's, used in Audio-editing. If you also have a lot of VST's, you could have two issues with two separate programs, i..e. PS hanging on fonts, and PrPro hanging on VST's. The results would be the same, but the causes could be different. That leads to even more work. For PrPro, also see this ARTICLE. If you get PS launching, but PrPro is still not functioning, drop by the PrPro Forum, and someone can help you there.

  • Why is video size different to original when exporting from Premiere Pro CS6 to Encore?

    Hi there
    My source files in Premiere Pro are 1920 x 1080.
    When I export the sequence to Encore to burn to a DVD the size in the burned DVD changes to 720 x 576
    In Encore project area I have these two entries
    The encoding settings for the above two entries are
    this (for the first entry above)...
    and this (for the second entry above)...
    It does not seem to be possible to change the encoding to 1920 x 1080 for the first enry and as such the video is being burned as 720x576.
    How can I fix this? What am I doing wrong?

    DVD is 720x576 you cannot change that.
    If you want 1920x1080 which is HD you need to make a BluRay.
    You can however make an AVCHD disk which is HD on DVD.
    About 20 minutes will fit on a DVD and will only (but not all) BluRay players.

Maybe you are looking for