Export mpeg2 problems with DVDSP 4 serial

When i'm exporting in FCP5 from QT Conversion using mpeg2,
Final Cut Pro asks for DVDSP4 to be serialized,
I have tried deleting the system ID's and also reinstalling the apps and it still asks for serials.
I know i can use compresser but don't understand why this is not working.
+ In compresser i have approx 10 options to compress in DVD and i think the old 10 options aswell to compress in MPEG2.
why are they still there?

I had the same problem after having to do an erase and install of the OS the Sunday. If you have an earlier version of DVDSP follow the steps in this link:
http://discussions.apple.com/thread.jspa?messageID=1049698&#1049698
Make sure to read all the posts, including the one about re-entering the serial number for Studio Pro 3.
I tried it successfully this morning.

Similar Messages

  • I have problem with delay in serial port

    I have problem with serial port. I have connected two computers by serial port and I need to create program in Labview for transfer strings using start bits and stop bits. My problem is that my program is working quite well ...when I press start bit it starts to concatenate strings and if i press stop bits it stops...this is the purpose of this program...but problem is that it working only with delay...and need that this program dont need delay, because it can only concatenating data depends on delay from start bit....I wana solved problem with delay...I dont want using delay process in my program, but allways when I try to delete this delay it stop works correct
    here is my program

    Ok this should be simple - if I understand you correctly.
    You have the VISA session initialized with read termination character enabled.  So reading the number of bytes at port is NOT the correct way to read from the port.  Set the read number of bytes to something large (say 4096) and the read will return as soon as a termination character is received (or timeout).
    You'll need to make sure the sending device is configured to send termination character on writes (you can set that with a VISA property node)  and that you are sending the correct termination character.  The default is 0x0A (newline).
    Jeff

  • CS3 - Import and Export Quality Problems with Canon S90 .mov files

    Hi Folks,
    I have spent several hours searching with no results in the forums, and I am a beginner with Premiere, so I apologize for any annoying questions I may post.
    Here is the problem I am having.  The very first step!  Go figure.
    I have videos taken with a Canon S90 point and and shoot camera, in .mov format, 640x480, 30 frames per second.
    When I play these videos in Quick Time or Windows Media Player they look great.  Very sharp and smooth video.
    When I import these videos into Premiere Pro CS3 - and don't do anything to them besides play them in either the source window or or Program window, the quality is much lower.  They are not sharp, and have an unusual texture, almost like there is a tiny bit of water on the lens distorting the view as it moves.
    I imported the video under the DV-NTSC Standard 48kHZ preset.  I have the most updated Quick Time.
    I also attempted to improve the view settings to their maximum with no results.  I also exported the video to see if it was just the viewing, but the exported video is even worse.  Very low quality and not sharp.
    Thanks for any suggestions on the correct settings to import these videos without loosing quality.

    Well, I have read and understand the Codec aspect a bit.  I have discovered that my
    files are avc1 H.264 Codec.  Doing more research it appears that CS3 Premiere Pro has some trouble editing H.264 files.
    So from what I gather so far, it looks like my best bet would be to convert the file into another format that is easier to edit by Premiere.
    Is that correct?
    If so, I am still unsure what to convert it to.
    What is the program that is best to use to convert with?
    Thanks again for your help.

  • Problems with access to serial port using reentrant code

    Hi,
    I have a VI that send commands and receive answers from an instrument using
    de serial port.
    This VI runs perfectly when used alone.
    However I'm trying run two instances of that VI simultaneously using
    reentrant code and I'm facing some problems.
    Sometimes everything is OK but sometimes, in the process of writing to
    serial port the following error happen:
    Error code 36.
    Invalid refnum device.
    What is this?
    Does someone know how to prevent this?
    Thanks in advance for any help.

    "Paro, Paula [CMPS:2721:EXCH]" wrote:
    >
    > Hi,
    >
    > I have a VI that send commands and receive answers from an instrument using
    > de serial port.
    > This VI runs perfectly when used alone.
    > However I'm trying run two instances of that VI simultaneously using
    > reentrant code and I'm facing some problems.
    > Sometimes everything is OK but sometimes, in the process of writing to
    > serial port the following error happen:
    > Error code 36.
    > Invalid refnum device.
    >
    > What is this?
    > Does someone know how to prevent this?
    >
    > Thanks in advance for any help.
    You can't use reentrant vi's vith serial vi calls without supervising of
    driver.
    Use VISA instead and you have to control the VISA session opening and
    closing. Another word is that the only one serial port sess
    ion should be
    opened at a time.
    Reentrant vi's for serial port without checking serial port session is a
    mistake of program algorithm. Change it in any convenient way.
    Sergey Krasnishov
    Automated Control Systems
    National Instruments Alliance Member
    Moscow, Russia
    [email protected]
    http://acs.levsha.ru

  • Problem with PGI for serialized materials

    Hello
    We have created a delivery out of a stock transport order.
    The materials are picked and we have specified which serial number were picked (the material has a serial number profile).
    When performing the post goods issue for the delivery, the following error message occurs:
    "Stock data of serial number 12345678 not suitable for movement
    Serial number 12345678 cannot be used here"
    I check the status of the related equipment via IE03 and the status is EDEL ESTO.
    Could someone please help out on what is causing this error message to occur and how we can proceed with the PGI?
    BR,
    OT

    Please check whether the following notes helps you
    Note 684326 - IO231 during goods receipt
    Note 316342 - IO231 during goods receipt for stock transport order
    Note 712985 - IO201, IO231 and IO305 occur for a delivery goods movement
    G. Lakshmipathi

  • I have a problem with Lightroom 4 serial number

    Hi,
    With my leica M9 coming a ligtroom 4 with a number for download.
    After one year i upgraded my ligtroom 4 at to lightroom 5 directly , well, now i want install lightroom 5 in my new MAC and after installation says me that i have to  write  two serial numbers, one number is the lighroom 4 original and the number of lightroom 5 update, I only have to the lighroom 5 and i don't found the lightroom 4 in my adobe profile.
    How can i know what is my number serial of the first Ligtroom 4?
    Sorry for my english, is bad.
    Thanks-
    Best Regards.

    you'll need both serial numbers to install the lr 5 upgrade.
    if you purchased and downloaded lr 4 from adobe or registered with adobe, you may be able to find your lr 4 serial number under the account used to make that purchase/registration (not necessarily your current adobe id), Adobe ID
    and adobe support may be able to help you, contact adobe support by clicking here and, when available, click 'still need help', https://helpx.adobe.com/contact.html

  • Problems with Aperture DVD serial number

    I have Aperture 2 and 3 serial numbers on my files and the Aperture 3 box that I bought from Apple shows only stickers for two equal serial numbers labeled Aperture Upgrade V3.0. The installation rejects those as being for an upgrade and requests the original. The previous ones I had on file do not work either. I am actually in the process of reinstalling the OS and cannot install Aperture due to this problem. I do not remember how I handled this problem for the initial installation, which was not easy but finally worked. 

    See Troubleshooting Professional Application Serial Numbers and if that doesn't help see Pro Application Replacement Serial Numbers

  • Problem with activation of serial number

    I try to acitvate my serial number for Adobe Creative suite 6 design Standard (student edition), but I receive a error message which says that it can't be activate. Please Help!!

    Bonjour Karine. quel est le message d'erreur exact que vous avez reçu? avez-vous contacté le service clientèle?

  • Problems with Lightroom 5 serial number

    Desperation setting in. Have been round and round this site, followed all the helpful advice but still receive message that my serial number is invalid. However I bought and paid for the software yesterday and received confirmation emails and serial number and I have a version of Lightroom 5 downloaded and working on my laptop. So why is it a trial only when Adobe has taken my money?
    And there was me thinking it was quite a straightforward process - perhaps I should stick to Photoshop CS5.!!!!

    Hi Derrick2014.
    The order for Adobe Lightroom 5 has been completed and the serial number should be in your account.
    See - http://helpx.adobe.com/x-productkb/global/find-serial-number.html#adobeproductdownload
    You may also contact support at http://adobe.ly/yxj0t6
    ^Ani

  • HT4381 I have a problem with the right serial number? It will not take it!

      I have the appletv s/n right!  But it will not work and I am asked again and again and it will not take it. It is the right number exactly! I also am not sure how to get Netflix after this hurdle is over.

    There are some third-party instruments that will not show up in MAX, but you can still communicate with them through the GPIB card. When you say that the PC used to work just fine, I am not sure if you meant that it worked with these specific instruments. If not, then it may be that these instruments will not be detected in MAX.
    If these instruments have been successfully detected before, then it is very possible that it is a driver issue. I could email you a program that may help you with the uninstall and reinstall process. If you are interested in this program, please post your email address so that I can send it to you.
    John M.

  • Aperture 2.1.3 Export Problems with Cropped Photos

    I ran into an odd problem after updating to 2.1.3. I was trying to upload to a Picasa album via "aperture-picasa-plugin", which I had used before without problems. The resulting export had problems with two photos I had cropped from landscape to portrait size. The resulting exports had the entire uncropped/original content "squeezed" into a photo matching the cropped size, so the exported pics were squished making everything look tall and skinny. (I found it especially odd that stuff I had cropped out was back in, but the size was cropped.)
    I assumed it was a problem with the plugin, so I exported to a file straight from Aperture and had the same problem. I had other crops that worked OK, but they appear to all be landscape to landscape with no change in aspect ratio.
    Is anyone else having this problem?

    YES!
    I have seen this show up as well. I'm also using Aperture 2.1.3. I too thought it was the fault of the picasa plugin... but when I, like you, started doing my exports directly to files I noticed that they still had the same problem.
    The horizontal 16x9 seems to be particularly vulnerable... And, yes, it almost looks as if the (pre-crop) master has been "squished" into the aspect ratio of the (post-crop) version. It is very strange, very annoying, and very intermittent. Although, I found that if I quit aperture, restart then re-export... I have better luck.
    Boy, am I relieved to find somebody else who is having this problem. For a while there I thought I was going nuts.
    -C.

  • Premiere Pro CS4 - Problems with mpeg2 export file

    Hello!
    I shoud get export a one videofile (mpeg2 D-10, 4:2:2) with 4 audio channels (two stereo track). Audio must be .wav and PCM. The end result shoud be on channel 1 and 2, which has music, effects and narration. Channels 3 and 4, everything else, but without narration. (tv company wants to change narration language).
    The problem is that Premiere Pro cs4 connects two separate stereo tracks  to one stereo track when I export mpeg2 file. Another problem is that Premiere Pro does not accept PCM audio if  I have any multiplexing setting selected. If I select none multiplexing, audio is seperate from the video file.
    I have now about 150 test clips with different settings, nothing works...So, please help me! What shoud I do? Is this possible with Premiere Pro CS4 and Adobe Media Encoder? If so, how it can be done?

    I don't believe the end result is possible with Premiere Pro alone. You'll have to export out am .m2v file, and two separate .wav files.  Then look to other tools to mux them together.

  • Isolating problems with MPEG2 VBR "best"

    There have long been discussions here around problems with the quality of MPEG2 compression with Compressor v2.x, usually difficult to quantify or "solved" with "It doesn't work, use something else" such as a different product, Compressor v1 or a Quicktime MPEG2 export component. Maybe I'm an optimist, but I have to believe that someone who owns the code behind the Compressor product really does care to improve the quality of the compression, and is just waiting for a decent test case to figure-out what everyone is complaining about.
    That in mind, I would like to propose that the most visible problems I've seen can be isolated to something to do with what is done when switching from "VBR" compression to "VBR best" compression, either in 1-pass or 2-pass mode. I would be curious if others who have had similar quality complaints could also check if they are using "VBR best" compression, such as the various default presets for "DVD: MPEG2 best quality..." which use "2-pass VBR best". In short, it seems as though one can get rid of the most serious artifacting problems by taking a "best quality" preset and changing the quality from "2-pass VBR best" to simply "2-pass VBR" (and similarly for 1-pass).
    My own example: I've taken a short clip (less than 30 seconds) from the start of a recent home movie and published it along with some results on my iDisk's Public folder (Finder > Go > iDisk...): member name "dickermn" [sic], with no password. There you will find the folder CompressorTest, containing...
    -> 2006winter - a self-contained QT movie with the DV source material.
    -> dualG4 - a folder with the results of Compressor's MPEG2 compression with various settings, as run on a dual-1GHz G4 system.
    -> coreDuo - a folder with the results of the same settings as above, but with Compressor run from a coreDuo mini.
    -> *.png - two pairs of window-capture shots showing the same frames as compressed with "VBR" and "VBR best" settings.
    Background: after having various odd and intermittent problems with MPEG2 compression results, I've used the recent upgrades to start with a clean slate: on the G4 system I ran Software Update, then removed all the components of DVD Studio Pro 4, Compressor and Qmaster, along with all preferences, application support files, frameworks, receipts, etc, as recommended in these web pages to remove these programs, then did a full install of my unversal upgrade to Final Cut Studio, and re-ran Software Update. This got me up to the current ProApps updates and Compressor v2.3.
    Using only Compressor's default presets, selecting "DVD: Best Quality 150 minutes - 4:3" (2-pass VBR best, 3.7Mbps average rate), gives results with very visible artifacting. Using this same preset but changing the quality to "2-pass VBR" appears to clear up the most visible problems. Similarly, selecting "DVD: Fastest Encode 150 minutes - 4:3" (1-pass VBR) gives good results, but changing the preset's quality to "1-pass VBR best") produces visible artifacting.
    For the purposes of testing, I also installed just Compressor on my coreDuo mini - a clean install - then ran Software Update to bring this to Compressor v2.3. Running the same tests as above on the Intel-based machine produced similar artifacting problems when selecting "best quality", but in different places in the media than on the G4. Using the same quality settings as above, but moving the average bitrate down to 3.0Mbps has similar behavior, but the artifacts are just more pronounced, and using a default preset with higher bitrate (5Mbps average, not included here) the artifacts are still quite visible, but less pronounced. From the 3Mbps results on the G4, the still frames captured show good examples of the problems at hand, though the artifacts are much more visible with the video in motion. These are the examples described below.
    The clip shows some still titles against a still, horizontal-blurred background. At the end of the titles, the blurred background "un-blurs" and the motion starts: a horizontal pan, a wipe transition, and a downward pan. The subject is all falling snow, trees, our back deck, my son and me. The footage was taken with a consumer-grade Sony handheld camcorder.
    The problems first noticable in the video appear as a blockiness to the images, particularly notable against the floor of snow where the image shifts visibly to different intensities of gray/white as the camera moves. More severe are blocks which don't move correctly with the camera, at first visible as a jerkiness to the opening background as it un-blurs, but more pronounced in the trees and decking during the downward pan at the end.
    At about 14s is a good still of the blocking artifacts, seen here in the 1-pass VBR still frame. Note the large blocks in the snow in the "best" encoding, which are small enough to be lost in the noise for the "not-best" encoding. These shimmer between the different shades of gray as the camera moves.
    At the last half of the clip, as the camera pans down, parts of the trees appear to jump independently of their branches. This is very clearly visible around the straight-lines of the railing in the lower part of the frame as the clip ends. The still is from about 23s into the clip, and you can see a block of the railing in the lower right which has clearly jumped-above the rest of the railing. Interestingly enough, this is the correct placement for those pixels in the next frame (as the camera continues to pan downward). In each of these "jumpy" cases, it would appear as though blocks of pixels show-up one frame early, and their surrounding blocks catch-up in the next frame (while these hold still). Again, when using the same settings without "best" quality, the jumping does not occur.
    Note that with each pair of still (png) images you can group-select the pair and double-click to open them both in Preview, which allows you to toggle back-and-forth easily between the "best" and "not-best" versions. Comparing the two, you can easily spot several blocks in the frame which shift relative to their surroundings.
    While I am aware that MPEG2 at low bitrates is a complicated thing (though I will leave open for debate how low 3-4Mbps is in today's world), and consumer-grade video has lots of noise which the encoder has to dance-around, I do believe it is fair to assume that the "best" settings should give visibly better results than their faster "non-best" counterparts, all else being equal - at the very least, the results should not be visibly worse. It is worth noting that the "best" VBR settings do appear (subjectively) to give better contrast or color-depth, so clearly something right is going-on - I just have to believe that there is something going awry in the whole process which creates artifacts negating the other benefits, but which, with any luck, could easily be fixed.
    Please post with your comments, experiences or similar issues... or exactly what is the proper way to get this information to someone who could fix it?
    dual 1GHz G4 + coreDuo mini   Mac OS X (10.4.8)   Compressor v2.3 / Final Cut Studio (univseral)

    Well, I've found one more piece to this puzzle: hardware graphics accelerators.
    In short, I tried this same test running Compressor on my G4 PowerBook (with Radion Mobility 9700) and got better results. The terrible blockiness and pixelation problems seem - dare I say it - gone from the MPEG2 video. In this regard, the video compressed as both the default "2-pass VBR best" and the same preset adjusted to use "1-pass VBR best" both looked cleaner than any of the VBR "not best" encodings produced on this machine, or either of the others.
    Unfortunately, we're not completely out of the woods: the problems evidenced later in the clip - blocks which appear displaced in space/time for one frame - are still there, though they have moved to different locations in the frame.
    This gets me to thinking: my PowerBook is just barely past current muster in terms of hardware-accelerated graphics (enough to run Motion, for example), whereas my other two machines are not (NVidia GForce4Ti & mini's Intel graphics). So this starts to get to the root of "If these presets don't work, why does Apple label them best - or distribute them at all?" I'm going to hazard a guess that there are various pieces to the codecs which can take either a software-only path or a hardware-accelerated path, and the bugs seen here exist only in the software (non-accelerated) path. Anyone testing on the latest top-notch hardware with a fancy-shmancy graphics card wouldn't go down that path and see any problems. And the problems are subtle enough that they'd even slip by the occasional testing of the slower path.
    So now I'm out to find a more-current-than-my-PB graphics card to run the test, to see if I can get rid of the other problem. Updating to Compressor v2.3 got rid of most of the problems, and if buying new hardware is all it takes to fix MPEG2 compression, I might just spring for it - and hey, I'd get to run Motion, too.
    So anyone out there with a whiz-bang graphics card care to run these tests and compare/contrast with what I've got here? I might know someone with a new MacBookPro, which I hear has a pretty current graphics chip in it...

  • Im having problem with the dvd quality, I'm using compressor to convert the video fils from apple prores to mpeg2 .It doesn't matter how long my video is even if its just 5 minutes  I'm getting cut edges in the video , does anyone have any idea ?

    Im having a problem with the dvd quality, I'm using compressor to convert the video fils from apple prores to mpeg2 .It doesn't matter how long my video is even if its just 5 minutes  I'm getting cut edges/lines  in the video specialy if i have titles it comes up really bad , I took the same video to a friend of mine who have PC and he uses Encore , did the encoding there and it was just fine no problems! BTW I tried using doferent setings in compressor from CBR and VBR I even pushed up the setings to 8 or 9 BR and still no luck !
    does anyone have any idea ?
    Thanks in advence ...

    Let's focus attention on just the Sony. (What model and what resolution are you shooting?)
    For now, I'll assume you're shooting 1080i.
    Take a representaive clip  into a new sequence. Add a title.
    In your sequence, make sure field dominance is set to Upper.
    Set render settings to Pro Res 422.
    After rendering, export QT self contained.
    Import into Compressor (I'm now referring to v3.5).
    Select the 90 minute Best quality DVD preset.
    Open frame controls and turn on (click the gear icon). Set Resize filter to Best.
    Submit burn and check quality on TV.
    Good luck.

  • Problem with interlacing when exporting with Media Encoder CS 5.5

    It seems that when exporting a Video with interlacing in Premiere 5.5 with Media Encoder 5.5, the exported video is still interlaced although it is rendered with progressive settings. When rendering with the same settings through Premiere 5.5 without Media Encoder 5.5 (Button "Export") it is correct and progressive.
    I tried this with H264 and MPEG2. Anyone experiencing this problem too?
    Thanx!

    Were the field interpretted correctly in the first place?  Even if you think they are, try reversing them.  I've just been through hell doing something similar with a mishmash of client material from around the world.
    In some instances I switched field order (In the File>Modify) although it didn't seem logical.  In others, I used AE CS5.5 to added the Reduce Interlace Flicker filter.

Maybe you are looking for