MPEG-2 conversion issues

Hi all-
I normally post over at the FCP discussion page, but for my most recent question someone suggested posting over here, since I'm having problems with the combo of FCP and DVD Studio Pro. Can anyone over here point me in the right direction, even for an old discussion page? (FYI I'm running on 10.3.9, so I'm not on Tiger yet. And I have Quicktime 6.5, not 7).
Here's the original post:
I have FCP HD (4.5) and DVD Studio Pro 2. Both are licensed academic versions.
I have repeatedly noticed problems trying to export my timelines as MPEG-2s, to prepare them for DVD usage.
When exporting with "Compressor," I tend to have a high failure rate - generally, only about 1 out of every 4 exports actually succeed. This has been the case both before and after a recent reinstall of my OS and FCP and DVDSP (for other unrelated reasons). In addition, obviously compressor doesn't give you the kind of control over compression, such as CBR vs. VBR, one pass vs. two pass, max and average bit rate settings, etc.
I also noticed that in my DVD Studio Pro Manual, it claims that I should be able to export an MPEG-2 through "Export > through QuickTime Conversion" if I have both FCP and DVD Studio Pro installed. However, when I get to the QuickTime Conversion options in FCP, "MPEG-2" is NOT listed among my possibilities.
According to the DVD Studio Pro manual, I should be able to set my Encoding parameters in DVDSP's "Preferences" panel, and then have those encoding options carry over into FCP. But the MPEG-2 option isn't even present in FCP.
Is there some crucial step that I'm missing or unaware of?

It does sound more problematic than it ought to be.
First off, the QT conversion export option from the FCP time line should be in place - have you tried to re-install QT lately?
Compressor uses the same 'engine' to encode the footage to MPEG2 as QT will, but in fact does give you more control over the process, since you have access to various filters and settings which in QT you just don't - nor, for that matter, are they within DVDSP.
However, if this isn't working then it doesn't matter how many features you have... One thing to keep in mind is that Compressor 1 was/is not a reliable encoder anyway - the files it creates are fraught with problems like 'spikes' in the bit rate which will prevent the DVD from being built. You may want to consider an alternative encoder as an extra tool. I (and many others here) use BitVice and MegaPEG.X regularly on a Mac, or Canopus Procoder or Cinemacraft on a PC. These do cost (of course) and this makes it even more infuriating when Compressor doesn't do the job it is designed for.
This kind of issue is frustrating because it is hard to nail it down - I seem to remember that some folk reported the order in which the apps were installed makes a big difference - have you recently tried to re-install all of these apps?
Finally, the later version of Compressor is far better (IMO) than the first, but to get it you'll need to upgrade to a later version of DVDSP (v4). You don't need to upgrade the OS or QT in order to run it, I don't think. At some level I believe you will need to do some uninstalling and re-installing in order to fix this issue.

Similar Messages

Conversion issue in encoding in PI

Hi,
I am having a problem in conversion issue for encoding. Let's have a detailed look into the scenario first.
Scenario: SNC->PI (through Proxy)->MQ (through Receiver JMS adapter)->SeeBeyond (It's a middleware system).
Here from SNC, data are coming into PI as in UTF-8 encoding, whereas all the systems shown in the above flow are of ISO 8859_1 format. Hence UTF-8 needs to be converted into ISO 8859_1. PI does this conversion in Receiver JMS adapter. CCSID has been set to 00819 which is for ISO 8859_1 encoding. But the beginning of the xml, it remains still UTF-8, like below:-
<?xml version="1.0" encoding="utf-8" ?>
Whereas the content of the xml has already been converted into ISO 8859_1 by Receiver JMS adapter. Now let's see the problem now.
Problem: After the data been passed in SeeBeyond, the mapping fails in SeeBeyond, since SeeBeyond tries to look at the XML tag from the beginning and it found it's in UTF-8 as per he tag above. Then it tries to map it in UTF-8 format whereas the content is in ISO 8859_1, so mapping fails in SeeBeyond. Please note, here allthe systems except SeeBeyond are just bypassing the data, no mapping been introduced in anywhere in the systems except SeeBeyond.
Workaround: Is there any other chance where we can change the tag header from UTF-8 to ISO 8859_1 in Receiver JMS adapter itself in PI like this:-
<?xml version="1.0" encoding="iso 8859_1" ?>
This might resolve our problem I think. Any suggestions would be appreciated.
Thanks and Regards
Soumya

Hi Stefan,
Thanks for your reply. I have gone through the link you have specified. Ya, that's the other way to resolve that issue in that case. But here we have asked the receiver system (SeeBeyond) to change the encoding part in their mapping. Because changing the coding part in SeeBeyond is less time consuming than adding a new Bean in JMS adapter. Our problem got resolved by changing the mapping in Receiver end. Thanks anyway for your valuable reply.
Thanks
Soumya

Umlaut Conversion issue in Sender communication channel SAP PI

Hi Gurus,
We are facing issue while conversion.
umlaut Conversion issue in Sender communication channel that is reason channel not able to pic the file from the path.
Sender CC error:
Value of incoming field is too large. Segment:'IMD', Field:'7008', MaxLength:'35', value:'Plssvvkbecher LÃ¼bzer 0,4 (1280Stk p' DESCRIPTION: The length of the field value is too big !
Actually field contains 35 Chars only the value is : 'Plssvvkbecher Lübzer 0,4 (1280Stk p'
We tried with “ISO-8859-1” if the field value is less than 35 characters it is able to converting.
Please help me out from this issue.
Thank you.
Regards,
Jittu.

Hi Jittu,
Have you tried using the codepageconversion bean in the modules under the sender? It would be like:
AF_Modules/TextCodepageConversionBean with a parameter of Conversion.charset and a value of utf-8.
Regards,
Ryan Crosby

Language conversion issue in PI7.1

Hi,
My sceanrio is file to Idoc. Am facing language conversion issues.
For example one of the field in the source file is having the value "Différence sur net". And in the IDOC field the value is appearing as "DiffÃ©rence sur net".
With the same data I have done file to file scenario with and without content conversion and the output is coming correctly as "Différence sur net".
I have enabled Unicode check box in RFC destination also in XI server. But still its coming "DiffÃ©rence sur net" . Please advice how can I get the target field value same as that of the source field vale.
Can anyone help me to sort out this issue?
Thanks.
Dinesh

Hi,
In Channel try with using the File type: text and encoding : UTF-8.
I think this will solve your issue.
Thank you,
Siva

Currency conversion issue in SPM. We are getting incorrect results with SPM conversion function from one of the document currency to USD.

Currently we are using SPM 2.0 version and we have been facing currency conversion issues.
Please help me in following aspects.
1) Where actually currency conversion happens in SPM. Is it the global program which does the conversion or other way.
2) We have conversion issue for one of the currency where conversion function is giving incorrect results when converting from one of the document currency to USD. here The respective document currency is considering the 1:1 ratio with Dollar which is actually incorrect.
3) We have verified in both BI side(currency tables) and even ECC side.
Please help me in understanding this issue and let me know if you need more information on this.
Its an production issue and appreciated your immediate inputs.
Thanks
Kiran

Hi Arun,
The following information may be helpful to you.The SSA_HELPER_PROGRAM has options regarding currency settings.
EXCH_RATE_TYPE: This flag governs the exchange rate type which will be used for currency conversion in data management. For example if RSXAADMIN contains an entry EXCH_RATE_TYPE = „ZSPM‟ then the conversion type used for currency conversion is ZSPM. The default value for the exchange rate type is „M‟. More details can be found in the note 1278988.
CURRENCYCONVERSION: By default data management converts all the measures in transaction currency to reporting currency and copies over to the corresponding measure in reporting currency. If the measure in reporting currency is already available in source it might be desirable to disable the currency conversion. To disable the conversion you can make an entry CURRENCYCONVERSION = „ „ in the table RSXAADMIN. This can also be achieved by running the program SSA_HELPER_PROGRAM with the option DEACTIVATE_CURRENCYCONVERSION. The conversion can be reactivated by running the same program with option ACTIVATE_CURRENCYCONVERSION.
UNITCONVERSION: Similar to above. To deactivate unit conversion you can use the program with option and DEACTIVATE_UNITCONVERSION and to reactivate ACTIVATE_UNITCONVERSION. By default both the conversions are switched on
EXTERNAL_CURRENCIES: Normally most of the international currencies are stored with two decimal places however certain currencies do have 0 and 1 decimal place too. For example JPY has 0 decimal places. SAP internal format stores even these currencies with 2 decimal places and at the time of display it changes the value to right decimal places. In case a file from external source is loaded to SPM it might have the format with 0 decimal places in the file. To convert it to SAP standard format post processing needs to be done on this value. If that is the case you can set the flat EXTERNAL_CURRENCIES = „X‟ in the table which will enable the post processing for these values. This flag can also be set and reset using the helper program using the option TURNON_EXT_CURRENCY_FORMAT and TURNOFF_EXT_CURRENCY_FORMAT.
Kind Regards,
John Harris
Senior Support Engineer, SAP Active Global Support

How To Avoid MPEG-2 Conversion "Motion Streaking"

I've noticed a problem artifact I'm having when converting an existing QuickTime MPEG-2 clip to .mov, or .avi.
In the original MPEG-2 the motion, in say children playing hop scotch with eachother where their motion (or moving) legs, have a nice smooth transition in the motions.
However, when making a .mov conversion in QuickTime Pro, the motion in her "sweeping leg" now has horizontal lines in it. There isn't the "soft normal motion blur" of their legs, as in the original MPEG-2.
What is the "technical term" for this video artifact, and how can it be prevented, or what settings are best to use to avoid it.?
I would appreciate any input for either QuickTime conversions, or info on how to correct this ... possibly using Squeeze 4.1 (of which I also have installed on my Mac).
-David

"interlacing" .... that's what I thought it was.
However, using Sorenson Squeeze 4.1 does not solve the issue of
the interlacing from motion. The original MPEG-2 QuickTime has no
interlacing issues, the action is smooth and "artifact" clear.
It's just when I attempt to make a .mov or copy MPEG-2 (where I've slightly cropped the video using Sorenson Squeeze 4), that I always
get the interlacing in the copies.
In Squeeze 4 my settings are:
• CD Quicktime
• Remove Interlacing - Set to Auto
• Data Rate: 768+
• Frame Rate: 1:1
• Sorenson Video 3 Pro
• Sorenson 2 Pass VBR
and yet I still get the interlacing showing as small motion lines off someone's legs or arms in motion.
Any further suggestions?

Quicktime Conversion Issues!

I am using my new MacBook Pro 2.33 to edit a 2 minute piece that I want to upload to the web. Ive used Quicktime conversion in the past to upload several other videos to my website. For some reason, everytime I try to export my finished project to Quicktime Conversion, it says: FILE ERROR: UNKNOWN FILE!
What is this all about? How can it be an unknown file? The project is still sitting on the timeline! Just out of curiousity I selected Send to Compressor and it sent it with no problem. I also tried Export> Quicktime Movie and that worked with no problem but I am havng issues with Quicktime Conversions.
Any suggestions?

Which format were you choosing? If it was the MPEG-2 option, chances are you're running QT 7 and no longer have the MPEG-2 Export Component installed on your system.
If that's the case, use Compressor for MPEG-2 and AC3 encoding ... that's what Apple is trying to force us to do by dropping the MPEG-2 support in QT Pro.
-DH

MPEG Video Import Issues (Not Trial)

Hi Everyone,
I am fairly new to PP CS3. Up until recently I have been using basic Video Editing tools. I have decided since I like video editing so much, that I am going to try and go into it full force. So I bought my friends copy of CS3 Master suite off of him (because his company bought him two licenses and he only needs one so I got it cheap) and away I go.
So, with that in mind. Please be patient if I sound like noob because I am. I am a system admin, but when it comes to this stuff, I know very little compared to most of you I am sure.
Right now I am just doing something really basic to get my feet wet. I have imported a bunch of Kids shows I recorded using my Media Center PC and want to make a compilation of just the musical scenes for my little girl. I have done this type of stuff with Pinnacle in the past but I seem to running into a weird issue.
The video's are a standard MPEG 2 DVD compliant format. The capture card I use is a Hauppauge PVR 150 so it does the hardware encoding on the board.
If I watch these files on my TV or in Media Player Classic/WMP/VLC they all look fine. The minute I view them in PP CS3 they get this weird distortion. It looks like digital artifacts from say a bad digital cable stream, except it is all colorful and such. Dare I say the "Technicolor rainbow" :)
I thought at first that maybe it was just because the preview is a lower quality. So I did a small amount of editing and exported the video. After watching the exported video, the weird distortion IS there. So I am not sure what to do about this. I did see one post on the forums that suggested simply changing the file extension to AVI might help. I did this and odly enough, it did fix the video issue, but then the sound was completely out of synch.
I have looked around the forums and seem some references to MPEG file issues but none seem to describe the issue I am having and most seemed related to trial versions of the software not having the MPEG codec licensed. That would not be my situation.
Just as a last note. I know that MPEG files are highly compressed and are usually and especially in the case of DVD's the final product not meant for further editing. However, in this case I am just cutting sections out so I didn't think there would be an issue. Also, as I mentioned above, I have done this without issue on Pinnacle.
If anyone has any suggestions. I would appreciate it.
Thanks again.

Kyle,
It sounds like it could be a CODEC issue. I'd start by getting a bit of freeware, G-Spot, http://www.headbands.com/gspot/ and installing it. Run your MPEG-2 in G-Spot and see what it says about it. Your capture card could be doing the compression in a CODEC that PP does not work nicely with, or that it does not/can not access on your system. G-Spot will give you the CODEC used/required. Also, it will render the file with just a few mouse clicks and you can view it, with audio, in G-Spots viewer. How does it look there, just like in WMP?
I assume that you are doing all of the work on the same computer, right? If so, any CODEC available to WMP (and G-Spot) *should* be accessible to PP.
Actually doing a "conversion" to AVI would be better than just chaning the extension of the file. The Premiere-pedia has a full set of FAQs on file conversions. Eddie Lotter, the "gate-keeper" of the pedia offers this link:
http://premierepro.wikia.com/wiki/FAQ%3aHow_do_I_import_%E2%80%9Cxyz%E2%80%9D_format_files %3F
Hope that the forum does not truncate the URL.
As for sync issues, if the Audio & Video are out of sync by a constant amount, you can alt-click on the Audio and adjust it, until the sync comes in. You will want to Zoom the Timeline and also turn off the "Snap" feature, when you begin adjusting the sync. Find a point that is pretty obvious, like a sound that has a distinct visual associated with it. Dialog can be used, if the visual is shot tight enough to see the actor's lips. Do this BEFORE you do any cutting of the Clip. Once you have matched the sync, then you can cut and all should stay the same. However you should not have to do this, if your file is something that PP can play with. PP likes DV-AVI footage, that one shoots with a DV tape camera best, but should work with what you have, to a lesser degree.
Doing VHS captures to PP on my system (Turtle Beach A-D card) yields an 8 frame sync issue, that I have never cleared up. However, with the above syncing technique, it edits fine. These captures are done AVI uncompressed, but the sync problem exists with all of the possible formats from the TB card. Some day, I need to address this problem, rather than just do the workaround.
As for the exact distortion, that you describe, I have not seen that, but maybe others have and can tell you that I'm full-of-it, but give you a fix. Hey, that's all that's important, right? Believe them.
You might want to go up a level in the hierarchy of this forum (to get ALL versions of Premiere) and do a search for "MPEG + distortion," and similar, to see if someone else has had this problem. The Premiere-pedia is another good source of info too, though its "search" is not as good. I often find that Google does a better job, searching the P-pedia. Premiere-pedia:
http://premierepro.wikia.com/wiki/Main_Page
Good luck,
Hunt

Conversion Issues

I am upgrading software. I used to use MS Office Pro 2003--> now 2007. In converting documents from 2007 into Acrobat Pro 8.x, I was having a problem with the page numbers not getting converted properly. For example, I use Page x of y at bottom of docs and the conversion was giving Page x of x.
SO, I figured it could be time to upgrade to 9.0 pro. I am currently using the trial version. Well, I no longer have the problem above but I have another bigger problem. The conversion is changing the fonts of most text that is centered. I could live with that some of the time, however, certain documents must retain the specific font I use. This is pretty much a deal breaker if I cannot fix this.
Any thoughts?
Many thanks and Happy Halloween.

Ok, I figured out the CAUSE of the issue. If a font is regular and not bolded in the font box, it converts correctly when bolded by the "B". However, if it is bolded through the bold box, it converts to another font. SO, is it word or adobe that is the culprit?? Therefore, what is the SOLUTION?

Currency conversion issue while creating PO from Shopping cart

Hello Experts,
I'm facing an issue in SRM during Limit purchase order creation from Limit shopping cart.
Scenario:
Shopping cart was created on 1st of June and Approved on 20th June & Po was created on the same day. But the currency conversion is no ware matching and couldn't able to trace out the same. I have tried several times to replicate the issue it never done in test environments.
But the PO is creating with refer to Vendor currency. For example if SC was created in USD and vendor order currency in EUR then PO is created in EUR.
the relevant notes were already updated in the system and it is working fine when the SC is created and approved on the same day.
Please give me some idea how to fix this issue.
Is there any way to make SC currency is priority than Vendor Order Currency while creating PO?
Regards
Pratap J

Hello,
Read information available in KBA 1862453.
It mentions this issue.
Regards,
Ricardo

Crystal Data Conversion Issue (Error converting data type varchar to datetime)

Hi,
I can run stored procedure without error in SQL Server using my personal credentials as well as database credentials.
I can also run Crystal Report after connecting to Stored procedure without error on my desktop using my personal credentials as well as database credentials.
But when I upload the crystal report in BOBJDEV and when I run using database credentials report fails saying that "Error in File ~tmp1d1480b8e70fd90.rpt: Unable to connect: incorrect log on parameters. Details: [Database Vendor Code: 18456 ]" but I can run the crystal report successfully on BOBJDEV using my personal credentials.
I googled (Data Conversion Error Message) about this issue & lot of people asked to do "Verify Database" in Crystal Report. So I did that, but when I do it I am getting a error message like this:
Error converting data type varchar to datetime.
Where do you think the error might be occurring? Did anyone faced this kind of issue before? If so, how to resolve it?
(FYI, I am using Crystal Reports 2008, & for stored procedure I have used SSMS 2012 )
Please help me with this issue.
Thanks & Regards.
Naveen.

hello Naveen,
since the report works fine in the cr designer / desktop, we need to figure out where you should post this question.
by bobjdev do you mean businessobjects enterprise or crystal reports server? if so please post this question to the bi platform space.
-jamie

PSE 8 upgrade album conversion issue

I upgraded my system to Windows 7 and since I was going to have to reload everything anyway, I upgraded to PSE 8 at the same time.
Before the upgrade I saved my catalog files to my external drive and then moved them back to the C:\Program Files\Adobe folder I put it there because I didn't see a catalog folder under the Elements Organizer folder
Anyway, I then converted my catalog - renamed it "My Catalog 7.0" to differentiate
The conversion says it was good and upon inspection all meta tags and albums seem okay. The issue is that it didn't bring in the images from May 2009 onward. I know those were in the catalog in 7.0 and had tags on them.
Any sggestions on how to get those images (with their metadata) into PSE 8.0?
Susan

Thanks John
You were right, I pulled the wrong file to convert (the one I used to convert 6 to 7)
Thankfully I had a back up and was able to restore my correct 7 catalog. All is good now.

Non English characters conversion issue in LSMW BAPI Inbound IDOCs

Hi Experts,
We have some fields in customer master LSMW data load program which can
contain non-English characters. We are facing issues in LSMW BAPI
method with non-English characters Conversion. LMSW steps read and
conversion are showing the non-English characters properly with out any
issue. While creating inbound IDOCs most of the non-English characters
replaced with '#' and its causing issues in creating customer master data in
system. In our scenario customer data with non-English characters in
the first name, last name and address details. Any specific setting
needs to be done from our side? Please suggest me to resolve this issue.
Thanks
Rajesh Yadla

If your language is a unicode tehn you need to change the options like IN SAP you need to change it to unicode in the initial screen Customize local layout(ALT F12) options 118 --> Encoding ....

Currency Conversion Issue

HI experts,
i have an issue with my currency report,
where user want see the sales volume data converting from CAD to US $.
when i checked the query the conversion type is Avg rate M source to CAD and the Target currency is CAD only.
but when he execute the report he want to see the volume data in USD $.
and when i execute the report i can see below error.
Could not find any data to display. This might be due to the current selection of variable or filter values.
can some please help me out this issue.
thanks
Raj

Hi venu
thanks for the post,
there's no selection criteria being used by the user, has web link, once he click on link, he directly checking the report.
so there's no section screen available.
and there's no variable created for the currency conversion type .
here my requirement is to display currency in USD $ from CAD $.
target currency maintained as CAD in RSCUR tcode.
how would i do this,
and again the same report is being used by CAD user also, so view shouldn't be change for the both users.
what im thinking is
is there any possibility to create variable on currency to select the required currency dynamically by user in selection screen
please let us know possible solutions like without changing the view for CAD users
please let me know for more info
regards
raj

Unicode MDMP conversion issue with document management table.

Hi,
We are in a process of doing a unicode conversion for our ECC 6.0 MDMP non-unicode system. We have completed the scans and we found close to 14 million words not assigned to the codepages.
Then we checked at the table level which table has the highest number of words. There is one custom table ZQMDOCS which is used to store documents (MS-word) documents those are test procedures for our labs.
If we see the MS-word document in non-unicode we are able to get to the document and just did some dummy assignment and completed the import and on our unicode system if we try to open the document it is opening in a readable format.
So the issue is the data what is being stored in the document is in english but the formating which is done is read as a special character in a unicode system and in SAP it stores raw data.
Please suggest ways to resolve this issue or any possible workarounds for this. This is a very critical table ( 43,000 documents & close to 14 million words not assign to the code page)
Thanks
Junaid.

Hi Venkat,
Thanks a lot for your immediate response.
The InfoObject 0DOC_TYPE was without conversion exit by default. but when data coming from R/3 it is converting and sending to BW So that's why i am planning to use conversion exit "AUART" in the info Object.
I checked data in R/3 using RSA3 it is showing sales document type as "OR" and for the same transaction data when i checked in PSA it is showing as "TA".
Could you please let me know if there any other options.
Thanks in advance,
Dara.

MPEG-2 conversion issues

Similar Messages

Maybe you are looking for