ProRes and Non-TV-standard resolution

Hi, I've tried to use the ProRes HQ codec for two different frame-sizes
1: 1366x702 (for a kiosk solution)
2: 680x384 ( for a FLV kiosk solution)
Trying to make a sequence in FCP for these sizes, gives me, on output, a black vertical line about 10 pixels wide at the left side of the picture... and some places on that line, it is green og transparent, but only at 1 to 2 pixels high...
Is it so that the ProRes can only handle TV standards?

I have exactly the same problem. However, I really like using the ProRes since it plays smoothly at high resolutions (1366 x 768 in my case, it's the native resolution of many tft tvs). File size is not an issue for me, I need the smooth playback. I had some small success by generating Image Sequences and then using Quicktime Pro to convert these to ProRes - the problem does not seem to exist then. Also, when saving ProRes from Motion (same resolution of course) I don't get the black bar either - it's just from Final Cut Pro.
I'm really disappointed by Apple - the put this application suite out with many bugs and don't seem to be fixing anything (Motion has so many bugs it's unbelievable).
I'll report back when I know more about the image sequence method.

Similar Messages

  • Compressing non-TV standard resolutions

    How can I compress movies that don't confirm to normal SD/HD resolutions?
    Seems like compressor wants to limit my frame size.

    Okay, this is what I get. No option other than broadcast TV resolutions.
    Message was edited by: Navarro Parker -

  • 17" high-resolution display vs. standard resolution

    Hi,
    I'm looking to buy a refurbished MacBook Pro 17" and I'm trying to decide between the 17" high-resolution display and the 17" standard resolution display.
    The laptop will be connected to a Studio Display 90% of the time and I'll use the laptop display as a second monitor. Battery life isn't a big concern. I like that a 7200rpm drive comes with the high-resolution display.
    I'll be using the computer mostly for text and HTML editing, e-mail, web-based reading, and a small amount of simple photo editing, such as resizing and cropping. I'm replacing a Powerbook G4 17" 1Ghz.
    I saw the high-resolution display and I thought the text looked small. It was very sharp and readable, but still small. Unfortunately, stepping down to the next resolution isn't as sharp and clear as the native resolution.
    I'm wondering if I will get tired of the small text. Not all applications work well and look as good when bumping up the text sizes. And zooming is kind of a kludge.
    Maybe the high-resolution display is better for photo and video editing?
    The $200 difference isn't that big of a deal to me, especially since the computer is $2000+.
    I'm trying to decide if I should go with the high-resolution display, and I'd appreciate your thoughts if you've had to make a similar decision. Do you find the text large enough? If you like your high-resolution display, what do you use your computer for primarily?
    Please let me know if you've read any helpful reviews or comments about the high-resolution screen (other than recent 90-day posts in this forum, which I've already read). Thanks to hiking4ever for your helpful post in the other recent thread.
    Thanks!
    -- Ed

    I have the high resolution display, and I just set the fonts bigger for the applications I use in that application's preferences. Foe example, you can go to Safari>Preferences>Advanced and check the Universal Access box. That will allow you to set the fonts at any size up to 24 pt. I set them at 18 pt., and every Safari Application will open in that size. Same for Mail. That way you don't have to change the resolution. I primarily do Safari and Mail and documents now, although I got the high resolution display for photo editing. But I really do like it, and am glad I got it.
    Hope this helps!

  • Standard and Non-standard exports and queries issue

    Hi,
    We have created a few STANDARD books with standard exports in them. The standard exports use standard queries.
    The ISSUE is that in the Verifications/Filters tab, where we have put in a lot of queries - ONLY the STANDARD queries show up. We would like to have all the queries show up. I am the adminsitrator and still only the standard ones show up.
    I am worried that if I "Save As" the export as a non-standard export, it does not allow me to uncheck the standard tick column and save it but I have to manually change the name of the export. Can we change this in anyway?
    Is there a system preference where I can allow all the queries to show up in the verifications/filter tab at least for the admnistrators if not for all? Thanks
    - Ad

    Thanks for your input but DRM does seem to be behaving what you said or may be I am still missing something here.
    I created a standard query.
    I have a standard export.
    Now, in the verification/filter tab of my Standard export, I am able to see my standard queries.
    But,
    I am unable to see the Non-Standard Queries.
    HOWEVER,
    If I have a Non-Standard export --> I am able to ALL the queries. This makes it a lot more flexible in doing things.
    My question is the WHY are my standard exports not able to reach the non-standard queries. What I wanted to do a twist in my export for analysis purposes for a particular use. If non-standard exports have access to Standard and Non-Standard queries --> it just makes more sense to always use a non-standard export and create non-standard queries.

  • Need std and non-std baud rates on PXI-8420 (16 channel RS232)

    I found a similar request on the knowledge base, and the resolution was possibly NI would make a card on a case-by-case basis.
    I need the forementioned PXI card to support std and non-std baud rates (i.e. not a simple xtal change, and the software sets up for 57.6 Kbaud, and it is really 62.5 Kbaud) that is easily configured in LabVIEW/VISA.
    The rates I need are as follows:
    All std rates (i.e. 1200,2400,4800,9600,...)
    10.4K (possible with std ports, but unsure about NI hardware and VISA).
    62.5K
    Thanks.
    62.5K

    The golden rule in serial (UART) communication, is that if two communicating partners are within +-2% of each other, they'll happily communicate error-free. Since you often only know one side of the equation, the window narrows to +-1%.
    Next, take a look at how baud rates are calculated. On most NI-Serial hardware, there is a 7.3728 MHz oscillator that is divided by 16 (to create the what I'll call the 'base' frequency), and then divided again by a divisor latch. A divisor latch value of 1 yields 460800, 2 = 230400, 3 = 153600, etc. This is where the 'standard' baud rates come from.
    However, on some OS's, we divide the clock source again by 4 before it hits the divisor latch. This means 1 = 115200, 2 = 57600, etc. While this does creat
    e a set of 'standard' baud rates, it also limits the number of possible baud rates. This is something that will be fixed in the future.
    Now hopefully the following table will make sense. In systems that have a base of 460800, we support baud rates that are within +-1% of the following (baudrates marked with * are supported in 115200 base systems):
    110-9216*, 9404, 9600*, 9804, 10017, 10240, 10472*, 10716, 10971, 11239, 11520*, 11815, 12126, 12454, 12800*, 13165, 13552, 13963, 14400*, 14864, 15360, 15889, 16457*, 17066, 17723, 18432, 19200*, 20034, 20945, 21942, 23040*, 24252, 25600, 27105, 28800*, 30720, 32914, 35446, 38400*, 41890, 46080, 51200, 57600*, 65828, 76800, 92160, 115200*, 153600, 230400, 460800.
    10.4k is supported in both systems at the baud rate 10472.
    If you're running at 62.5k when set to 57.6k, then you're likely using a 8 Mhz Oscillator. In this case, you have a base of 500000, and with a divisor latch value of 48 you'll be running at 10416. This cor
    responds to a 'normal' baud rate setting of 9600. So if you set your modified card to 9600, you should get 10.416k.

  • Problem with T400 and external monitor (1920x1200 resolution)

    Hi there
    My laptop:
    ThinkPad T400 2767-C99* (graphics is: ATI Mobility Radeon HD 3470 256MB / X4500MHD (Switchable Graphics)), OS is WinXP
    I just installed the newest video driver from the lenovo page (which also installs "ATI catalyst")
    Externale Monitor:
    I just bought a Samsung SyncMaster 2443FW, 24" TFT monitor with maximum resolution 1920x1200
    Problem:
    Monitor works great with my newer T400s and my old Acer laptop. However, with my T400 (described above), I can't make the monitor use the 1920x1200 resolution. However, all the other resolutions look ugly so I need it to work with 1920x120
    - If i change the resolution by rightclicking on the Windows XP desktop (and then properties=>settings) and set the screen resolution there to 1920x1200, then my monitor only used a lower resoltion (1440x900) and I get a scrolling effect as I move my pointer across the screen
    - if I use ATI catalyst software to set the resolution, I can only chose smaller resolutions (it does no go up to 1920x1200)
    Questions
    Is that a hardware (maybe the graphic card does not support 1920x1200) or a software problem (maybe some problem with the driver) or just a matter of setting?
    What can I do?
    Help would be very much appreaciated!
    *Original description: Based 2767-2JG: T9550(2.66GHz), 4GB RAM, 250GB 5400rpm HD, 14.1in 1440x900 LCD, 256MB ATI Radeon 3470HD, CDRW/DVDRW, Intel 802.11agn wireless, Bluetooth, Modem, 1GB Ether, UltraNav, Sec Chip, FPR, Camera, 9c Li-Ion, DOS License
    Solved!
    Go to Solution.

    bfrey wrote:
    Thank you for your answer.
    I have already installed the newsest drivers from Lenovo. I don't really see why I should install a non-official driver. I am convinced that it must work somehow with the official driver.
    Kind regards
    there are plenty of instances where the official driver have glitches... just look around the forum to find instances of which.... while official drivers maybe better in most instances, there are always the odd case where it doesn't work as well as it should. If they perfectly out of box, then there would never need to be multiple revisions and updates. 
    Regards,
    Jin Li
    May this year, be the year of 'DO'!
    I am a volunteer, and not a paid staff of Lenovo or Microsoft

  • Report for Excisable and Non Excisable vendor

    Hello
    Is there any Std report is there....it can give us the list of Excisable and Non excisable Vendors based on the Perticular Purchase Orgnisation.
    Regards
    sapman man

    Hi
    I do not think in SAP this kind of report is available.
    what you can do , if your vendor master has different  accounting group for Excisable and Non excisable vendor then you can check in standard table of vendor master like LFA1  and LFM1 or create Z report or Query.
    Awaiting your feedback.
    Kishor Rudani

  • Difference between Valuated and Non valuated Sale order stock

    Hi All,
    Can anybody tell me the difference between the above said subject with the steps involved in each scenario.
    That is valuated sale order stock and Non valuated sale order stock in Product cost by Sale Order.
    With Journal entries at each step and whether any WIP or variances at Production order level and sale order level and all the financial entries related to them
    Thanks in Advance,
    Ravi Kumar

    Hi Shail,
    Thans for your inputs,
    But I wanted to know it in more detail. In what scenarios they are used with financial entries in both the cases.
    I will give you my scenario. It goes like this,
    My client is in pipe coating business, who receives pipes from customers and does only coating work(which is considered as service) and despatches it to the customer. this process is carried on the basis of work order(Sale order).
    Now Production order is created and work is done on that with reference to Sale order for that particular customer.
    So the pipe which my client receives should be non valuated stock as it will not be a raw material to them and the cost incurred on it is booked on production order like chemicals as raw material consumption, activity cost etc.
    now in this scenario just tell me how and at which stage FI entries get generated at Production order and Sale order level, and also at wat level Standard cost estimate should be created i,e at production order level or sale order level(sale order cost estimate).
    Will there be any entries at goods isssue and GR against production order. If no then how the COGM account will get hit.
    Please tell me this scenario in both cases Valuated sale order stock and Non valuated sale order stock with financial entries in Sale order costing.
    Thanks & Regards,
    Ravi Kumar

  • Idoc  b/w sap(r/3) and non sap system .

    hi gurus,
    how i pass an outbound idoc  b/w sap(r/3) and non sap system .
    which  function module we will use in this scenerio for inbound and outbound idoc both
    please guide me  with an example .

    Hi Pawan,
    Non SAP system should have RFC adapter in order to receive and send Idocs from/to SAP.
    If this is not your case, you should us a Integrator Middelware with RFC and standard adapters like SAP Exchange Infrastructure.
    If for example, your non SAP system is able to process data from flat files you can build next interface: SAP send Idocs to middleware that receive them using RFC adapter, middelware maps Idocs into flat file and send it to a one of non SAP system folder using FTP adapter. Non sap system triggers the flat file into its applications.
    Reward points if useful.
    Roger

  • Edit to tape confusing drop frame and non drop frame

    This is a re-creation of a dead thread I found from June 6, 2006. This is the exact problem this other user was having.
    OS 10.4.7
    FCP 5.0.4
    Dual G5 2.5
    4.5 GB RAM
    KONALH
    Trying to edit to a Sony DVW-A500 (Digibeta) in Drop Frame mode.
    Read Below for deets.
    Problem: When working with a drop-frame sequence, and editing to tape, the program is edited to the tape with an offset of 3 seconds and 18 frames at the end of one hour.
    Reproducible: Yes.
    Steps to Reproduce:
    1. Create a drop-frame sequence.
    2. Edit the sequence in step 1.
    3. Perform an edit to tape with the sequence edited in step 2.
    What should happen: The sequence should be edited to tape at the time it occurs in the timeline.
    What does happen: The sequence is edited to the tape 3 seconds and 18 frames after it should be!
    Other observations: 3 seconds and 18 frames is exactly how much time is not in an hour of drop-frame time when compared to non-drop frame time. If you drop two (2) frames in every minute that does not end in zero, the math works out to 2*54=108 dropped frames in an hour. For the sake of simple mathematics, lets say there are 30 frames in a second. So 108/30= 3 with a remainder of 18, or 3 seconds and 18 frames.
    It's as if FCP is getting confused about drop and non-drop timecode when the sequence is drop-frame. If anyone can offer any insights, confirmation, or resolutions for what I am seeing, it would be appreciated.
    Thanks for reading!

    So is the timeline a drop frame timeline, starting at 1:00:00:00?
    And then is the DBeta tape prestriped (at least enough to do an assemble edit) to start the program at 01:00:00:00?
    In other words, is the FCP timeline timecode matching the Dbeta tape timecode in a 1:1 relationship before you attempt to Edit to Tape?
    Thinking further: FCP can't really confuse the two timecodes, it's dependent on the operator to tell it what to do. When it outputs it's not outputing timecode or looking even really looking for timecode. It's looking for your IN point in the Edit to Tape tool.
    Message was edited by: loyed256

  • TS3694 my phone has switched off for the second time this week, however when connecting to itunes the restore process wont complete. the error is 2006 however i have tried a number of USB cords, and none seem to be working.

    my phone has switched off for the second time this week, however when connecting to itunes the restore process wont complete. the error is 2006 however i have tried a number of USB cords, and none seem to be working.
    I am in the noerthern [parts of australia and accessing an apple store is not possiable for another month. this is my only soucrce or telecommunication. please help

    This is what it says about error 2006
    Error 2000-2009 (2001, 2002, 2005, 2006, 2009, and so on)
    If you experience this issue on a Mac, disconnect third-party devices, hubs, spare cables, displays, reset the SMC, and then try to restore. If you are using a Windows computer, remove all USB devices and spare cables other than your keyboard, mouse, and the device, restart the computer, and try to restore. If that does not resolve the issue, try the USB issue-resolution steps and articles listed for Error 1604 above. If the issue persists, it may be related to conflicting security software. If the errors persist on another computer and known-good USB cable, the device may need service.

  • How can the symbol and non-English diacritical marking, etc accessed with combinations of letters and functional keys prior to Snow Leopard be achieved in Snow Leopard?

    How can the symbol and non-English diacritical marking/punctuation pallet, available in pre-Snow Leopard OSes with various combinations of letter or number keys and functional keys, be accessed in Snow Leopard?  Those pre-Snow Leopard versions worked on the fly as one was making text in any pedestrian application and its native font (Mail, Text Edit, for example).  One didn't need to dig around in font libraries, change font preferences, etc.

    > One didn't need to dig around in font libraries, change font
    > preferences, etc.
    It hasn't worked like that since the Early Chalcolithic (ie, System 7 or thereabouts).
    You've already got plenty of answers. Briefly (and grossly oversimplified),
    - Mac OS X conforms to a standard known as Unicode; in its current incarnation, it defines over 100k characters.
    - A keypress is translated into a character according to the current keyboard layout.
    - The graphic representation of a character (ie, glyph), is provided by the current font.
    - If a font lacks a glyph for the requested character, either another font will be automatically chosen (Mac OS X text engine), or some form of feedback (empty box, question mark, etc) will be used.
    - To inspect the actual key codes, use a utility such as Key Codes.
    - To inspect the current keyboard layout, invoke Keyboard Viewer.
    - To inspect the full complement of glyphs of a font, invoke Character Viewer (also accessed with the Special Characters command).
    (Remember that both these utilities are resizable and zoomable -- you can enlarge them to a comfortable viewing size, then zoom out to see more of the screen for your original task.)
    - For a more detailed look, use a utility such as UnicodeChecker.
    - The default keyboard layout depends on your Mac OS X localisation.
    (Keep in mind that there's no need to stick with the default layout; choose whichever one makes sense to you, given your language, habits, and proclivities. Mac OS X comes bundled with quite a few, including some obviously designed for the huddled masses of refugees from the Dark Side, who, in their wretched ignorance, have the unmitigated gall of labelling our native ways "really uncomfortable". Oh well, this, too, shall pass.
    If none of the supplied keyboard layouts fits your needs -- if, for instance, you write your emails in Etruscan -- go out on the 'net, you'll find quite a few. Or write your own with Ukulele, it's not really all that difficult.)
    - Use Keyboard Viewer to familiarise yourself with the current layout and to enter the odd character; but, to be proficient, you should learn your layout to the point that KV is no longer needed.
    - Use Character Viewer to enter the odd character not available in the current keyboard layout.
    Neither Keyboard Viewer nor Character Viewer are effective tools for more extensive needs, eg, for writing and editing bilingual or multilingual texts. In such a case, you should enable the respective keyboard layouts and switch between them with a keyboard shortcut.
    A few interesting layouts bundled with Mac OS X have already been mentioned. Let me add three.
    - Dvorak: several layouts based on the Dvorak keyboard. It is claimed that the latter is more productive and lessens RSI risk.
    - US Extended: based on QWERTY, it offers a more extensive set of diacritics (eg, caron, breve) via dead keys.
    - Unicode Hex Input: also based QWERTY, it allows input by Unicode codepoint (in hexadecimal), so it's the most extensive layout of all; eg, to enter the character "Parenthesized Number Twelve" (U+247F), hold down Option, type "247f", release Option.

  • SAPScript: how tu adjust heigh and width of standard text (logo)?

    Hi!
    how to adjust heigh and width of standard text (logo)?
    I do not want to edit the logo, because it is used elsewhere, so I need to adjust heigh and width when using it in a form.
    For now stadard text comes over the window. Here is how I use it:
    INCLUDE ZHEX-LOGO OBJECT TEXT ID ST
    Will reward,
    Mindaugas

    Hi Mindaugas,
    While uploading using RSTXLDMC. You have to maintain your size of the logo.
    Go through below mentioned document.
    Upload TIFF files to SAPscript texts
    Description
    The report RSTXLDMC allows a TIFF graphics file to be uploaded from the file system of the R/3 GUI to a standard text in the R/3 word processor SAPscript. (TIFF is a registered trademark of the Aldus Corporation.)
    When uploading, the TIFF graphic is converted either into a black and white raster image (parameter type=BMON ) or as a color raster image with a maximum of 256 colors (parameter type=BCOL).
    The black and white raster images ( BMON) can be printed using the following printer types:
    PCL-5 printer
    PostScript printer
    Kyocera PRESCRIBE printer
    Device type SAPWIN (with SAPlpd 32-bit as of Version 2.41 for Windows NT or Windows 95)
    The color raster images (BCOL) can be printed using the following printer types:
    PCL-5 printer with color capability (e.g. HP Color LaserJet). Color graphics are not printed properly on monochrome PCL-5 printers (e.g. HP LaserJet 5), because the printer cannot set the color palette as required and does not perform any gray-level conversion.
    PostScript printer (color graphics are automatically converted to gray levels on black and white printers using PostScript) Device type SAPWIN (with SAPlpd 32-bit as of Version 2.41 for Windows NT or Windows 95) During TIFF graphic import, the basic set " Baseline TIFF 6.0 " of the TIFF specification 6.0 is supported.
    To maintain compatibility with earlier versions of the report RSTXLDMC, it is also possible to convert the TIFF graphic directly into a black and white raster image for a particular printer type when uploading. These are the three printer types PCL-5 (parameter type=PCL ), PostScript (parameter type=POST) and Kyocera PRESCRIBE (parameter type=PRES ). A raster image uploaded in this manner can only be printed using the appropriate printer type.
    Besides TIFF raster graphics, direct printer commands in the respective printer language (PCL-5, PostScript or Prescribe) can also be contained in the file which is to be uploaded (printer macros). They are then transferred to the standard text unmodified.
    The graphics are output by inserting the standard text into the document which is to be printed, directly or using an INCLUDE command. The printer commands, which for example draw a company logo on the page, are only output if the print request is processed by the printer driver corresponding to the macro type, otherwise they are ignored. Example: A macro of type PCL is contained in a print request. If the request is output to a printer with type HPLJIIID (to which the driver HPL2 is assigned), the macro data is sent to the printer. If the request is printed on a printer of type POSTSCPT (to which the driver POST is assigned), the output of the macro data is suppressed.
    In the standard text, the printer commands are inserted between the HEX ... ENDHEX command lines in hex notation. Various report parameters allow the graphic or printer macro to be placed on the page or at the current text position. Note: When the /:HEX command line which precedes the macro appears in the text, a line break is generally made before the graphic is output. The output of the macro therefore begins in the next text line at the left window border of the current page window, as long as a shift to the right is not specified (see below).
    If your own printer macros are uploaded and not TIFF files, you must ensure yourself that the normal (text) output of the driver is not impaired when the printer commands are inserted in the output from the uploaded file. The printer drivers pass the data contained in the file to the printer unmodified, therefore without control over the individual actions this triggers on the printer. For example, syntax errors should not be generated by the PostScript commands (type POST), or form feeds should not be contained in the file (unless this was intended) for PCL-5 (type PCL).
    Restrictions:
    In general, the output of graphics generated via RSTXLDMC from R/3 is not suitable for mass printing (that is, unless you are using the "Graphic resident on printer" feature): the R/3 spooler has to hold significantly more data in its output files. If the graphics occur several times in a spool request, the data also reoccurs. Apart from this, the network is more heavily loaded in sending the increased volume of data to the printer and the printer output is slowed significantly (varies according to printer model) if raster graphics are output as well as the text.
    If your graphics reside on your printer during a printing job, the degree of 'correctness' with which they are printed depends on the amount of memory available in your printer. R/3 print drivers are unable to determine whether the amount of memory available is enough! If one of the graphics that you have marked as resident is not displayed, try reloading the graphic and switching off the parameter "Graphic resident on printer".
    When printing black and white graphics on PCL-5 printers, image data is compressed in order to greatly reduce the file size.
    The output of graphics and macros on PCL-5 printers, PostScript printers and device type SAPWIN (type BMON, BCOL, PCL, POST) is adapted to the page orientation used, that is if landscape is used instead of portrait, the graphic is also turned when output. This is not the case for the PRESCRIBE printers (type BMON, PRES)! With these printers, the graphic is not automatically turned when landscape is used, but appears on the page in the identical position as for portrait. You are therefore recommended not to output raster images when printing in landscape on PRESCRIBE printers.
    PRESCRIBE printers do not support the resolutions 200 and 600 dots per inch when printing raster images.
    Not all PCL-5 compatible printers support the resolutions 200 and 600 dots per inch when printing raster images.
    TIFF graphics with compression type 2 ("CCITT Group 3 1-Dimensional Modified Huffman run length encoding ") can currently not be imported although this is a component of the Baseline TIFF 6.0 specification for monochrome images.
    Color TIFF graphics with full color representation (ie. a lot more than 256 colors) are automatically converted into 256 gray levels when uploading with type BCOL.
    When TIFF graphics are converted to black and white raster images (type BMON, PCL, POST, PRES) there is no default simulation of gray levels or colors of the original image on the printer (for example, by using different tones of gray). Each pixel of the original image is converted to a white or black pixel on the printer according to its intensity value.
    The parameter "Number of TIFF gray levels" does, however, allow a simulation of gray/colour tones of the original image through levels of gray on the printer, when using type PCL, POST or PRES. This parameter is ignored for type BMON.
    The conversion of TIFF graphics can be so time-consuming that it is recommendable to execute the report RSTXLDMC in batch processing. Note: in batch, the file is always read from the file system of the application server (ie. not from the file system of the GUI).
    The length of an individual text in the text file is limited. When importing TIFF graphics with very large dimensions, especially if more than 2 gray levels are used, a termination can therefore occur when saving the standard text ("EXPORT_TOO_MUCH_DATA"). This restriction can only be avoided by reducing the TIFF graphics. Note: The display of a raster image in Postscript or PRESCRIBE format needs from two to three times as much space as displaying in PCL-5.
    When processing very large TIFF images on PostScript printers, a print termination can occur with PS error message "limitcheck". In this case the internal memory of the printer is insufficient to scale the required raster image. This implementation limit cannot be influenced by changing the report parameters when importing.
    Requirement
    The file which is to be uploaded can contain the following formats/ commands:
    Baseline TIFF 6.0 raster image files. The image information of the TIFF file is converted into black and white/color raster images when uploading. Note: As the TIFF format allows a variety of variants, only a basic set of TIFF 6.0 formats is supported here described in the TIFF 6.0 specification as Baseline TIFF 6.0.
    PCL : PCL-5, Hewlett Packard Printer Control Language 5 for HP LaserJet 3, 4, 5 series and compatible printers. The data is output by the printer driver HPL2 only.
    PRES: Kyocera PRESCRIBE for Kyocera laser printers. The data is output by the printer driver PRES only.
    POST: Adobe PostScript or EPS format (encapsulated PostScript ) for PostScript printers. The data is output by the printer driver POST only. In the upload, one of the end-of-file markers (CTRL-D, hex $04) which may be contained in the PostScript file is not transferred.
    For PostScript files which contain a bounding box entry (for example, all EPS files) the macro/graphic can be scaled to a size specified by the user. In this case, a small lead text and trailer are generated by the report for the macro data and inserted in the standard text.
    Parameters of RSTXLDMC
    File name
    Path and file name of the file to be uploaded in the file system of the R/3 frontend (dialog processing) or in the file system of the application server (batch processing)
    Type
    Way which the data contained in the file is to be converted. Possible values are BMON, BCOL, PCL, POST and PRES. With parameter values BMON and BCOL, a TIFF 6.0 file is expected. This is converted into either a black and white raster image (BMON) or a color raster image (BCOL). These raster images are printer-independent and can be printed using various printer types (see above).
    With parameter values PCL, POST and PRES, either a TIFF 6.0 file or a file with printer commands in the appropriate printer langauge is expected. If the file is a TIFF file, it is converted into a black and white raster image for the printer type specified in the parameter. The presence of a TIFF file is recognized automatically. If the file is not a TIFF file, the file contents are regarded as the printer macro of the respective type. Data loaded with type PCL, POST or PRES can only be printed on the respective printer type.
    Resolution for TIFF raster images
    Resolution which should be used when importing a TIFF raster image, in dots per inch (dpi). If an allowed value is entered here, this overrides the resolution information in the TIFF file. The allowed values are:
    75 dpi
    100 dpi
    150 dpi
    200 dpi (not for type PRES, for PCL only HP LaserJet 4,5 series)
    300 dpi
    600 dpi (not for type PRES, for PCL only HP LaserJet 4,5 series)
    Changing the resolution affects the size of the graphic on the printer. If a resolution of 300 dpi is stated in the TIFF file and this parameter is set to 75 dpi, the graphic is four times as big when printed as at the outset.
    Note: Kyocera PRESCRIBE printers do not support 200 and 600 dpi resolutions.
    Note: Not all PCL-5 printers support resolutions 200 and 600 dpi, for example HP LaserJet 3 series does not, but LaserJet 4 and 5 series do.
    Graphic Resident on Printer
    Normally, graphics that occur more than once in a printing job (a company logo that appears on each page, for example) are sent to the printer repeatedly each time they are needed. In order to avoid this kind of redundancy, you can select this checkbox on the selection screen. The R/3 print driver then stores the graphic in the printer's memory and the printer retrieves the 'resident' graphic memory every time that re-occurs in your job.
    Caution: Whether or not the printer correctly reproduces the graphic depends on the amount of memory available in the printer during the printing job! You should avoid using this feature with color graphics since they take up a lot more memory than monochrome graphics.
    This parameter can only be used with types "BMON" and "BCOL".
    Absolute positioning
    Determines whether the macro/graphic is positioned absolutely or is to be output at the current text position. If this checkbox is selected, the graphic is positioned absolutely (parameters "X-position" and "Y-position" are used), if this checkbox is not selected, the graphic is positioned at the current text position (parameters "Reserved height" and "Shift to right" are used)
    Absolute X-position
    Horizontal position (space from left border) of the macro/graphic, if absolute positioning is required. This is the parameter XPOS of the HEX command.
    Absolute Y-position
    Vertical position (space from upper border) of the macro/graphic, if absolute positioning is required. This is the parameter YPOS of the HEX command.
    Reserve height automatically
    If this checkbox is selected, the system automatically inserts the actual height of the graphic during printing into the subsequent "Reserved height" parameter.
    Reserved height
    If positioned at the current text position, this parameter specifies the horizontal spacing to be reserved for the macro/graphic, which must not be printed with text from the paragraph. This is the parameter HEIGHT of the HEX command.
    Shift to right
    If positioned at the current text position, this parameter specifies the space between the left border of the macro/graphic and the left border of the page window. If this value is increased, the macro/graphic is shifted to the right. This is the parameter LEFT of the HEX command.
    Unit of measurement for positioning
    The unit of measurement in which the position values (X,Y, height, shift) are specified. Possible values are CM (centimeters), MM (millimeters), IN (inches), PT (typographic point = 1/72 inch), TW (1/20 point = 1/1440 inch)
    Text title
    Comment used for the attribute "Title" of the standard text generated as well as as a comment line in the text itself
    Line width
    Number of columns to be used in the standard text when generating the HEX...ENDHEX command lines. The default value is 132
    Text name
    Name of the standard text to be generated. If an * character occurs in the name, it is replaced by the value of the parameter "Printer type". For example, if the entry is ZHEX-IMAGE1-* and the printer type = PCL, the text name ZHEX-IMAGE1-PCL is generated. The default value for the name is ZHEX-MACRO-<printer type>, but the standard text can be named as required (take into account customer reserve). Standard texts are client-dependent!
    Note: The name of a standard text can be up to 32 characters long !
    Text ID
    ID of the standard text to be generated. The default value is ST (general standard texts)
    Text language
    Language key of the standard text to be generated. The default value is the logon language
    PostScript scaling
    Flag which determines how the macros/graphics of type POST are handled. If set to 'X', the report expects a PostScript comment line in the file
    %%BoundingBox llx lly urx ury (e.g. %%BoundingBox -1.5 0 21.4 14.1)
    as present, for example, in all EPS files, in which the dimensions and the position of the macro/graphic are specified (if a bounding box comment is not included, 0 0 1 1 is assumed as the default value). This information is then used by the report to insert PostScript commands which scale the macro/graphic to the size specified in the parameters "Width" and "Height" (listed below).
    If the flag is set to ' ' (blank), the PostScript file is transferred to the standard text without any additions (any transformations to the coordinate system used by the printer driver must already be contained in the file).
    The flag must be set to 'X' for the import of TIFF files for type POST.
    Width according to PS scaling
    Required width of the macro/graphic if the flag PostScript scaling is set. Can remain at zero for the import of TIFF files, the size is then determined by the resolution of the graphic.
    Height according to PS scaling
    Required height of the macro/graphic if the flag PostScript scaling is set. Can remain at zero for the import of TIFF files, the size is then determined by the resolution of the graphic.
    If you want to scale the PostScript graphic with these parameters, one of the two values, width or height, can be specified with zero. The graphic is then scaled so that the width-to-height ratio remains unchanged and the original graphic is not distorted.
    Unit of measurement for PS scaling
    Unit of measurement in which the parameters "Width" and "Height" are specified. Possible values are CM (centimeters), MM (millimeters), IN (inches), PT (typographic point = 1/72 inch), TW (1/20 point = 1/1440 inch)
    Number of TIFF gray levels
    Number of gray tones which are to be used on the printer for displaying the original image. Note: This parameter is only evaluated when using types PCL, POST or PRES!
    Possible values are 2,4,9. With the default value 2, each pixel of the original image is converted either to a white or a black pixel on the printer. With the value 4, each pixel of the original image is converted on the printer with 4 pixels, which simulate 4 different gray levels. With the value 9, each pixel of the original image is converted on the printer with 9 pixels which simulate 9 different gray levels.
    Note: With values 4 or 9 the resolution of the image is doubled or tripled. The restrictions on the possible resolutions (see previous parameter) then apply for the resulting resolution.
    Output
    Individual steps of the upload procedure are logged in the report list generated and, if necessary, errors reported. The uploading of TIFF graphics, in particular, is cancelled if there is a variant which is not supported. A message to this effect is then issued. If execution is successful, the report generates a standard text with the key specified in the parameters. If the standard text already exists, a window appears with a warning before the text is overwritten.
    Regards,
    Ameer Baba.

  • R9 290X gaming 8G - standard resolution on HDMI output

    Hi,
    Could anyone help me with the problem - I just installed new card 8G 290X and from hdmi output I'm getting standard resolution signal. In the standard controlling program it says its 32 bit true color 1080p signal, on -for example - youtube in settings is 1080p as well but its not - the videos and even desktop picture is of way poorer quality. Before, I had radeon 5870 and it was fine till last minute, so its not tv or cable or videos that Im checking ( ). It says the driver is updated. What else can it be? Codecs?

    Does this happen when from DVI or DP? Any picture? Or driver settings?

  • Internal table with Dynamic and Non dynamic fileds

    Hi Experts,
    How to get the internal table with Dynamic and Non-Dynamic Fields.
    Could u please help me.
    Thanks,
    Varun

    Hi,
       Execute the below sample code or analyze it there is appropriate description provided.
    *& Report  ZTEST_PRM_DYN_ALV
    REPORT  ZTEST_PRM_DYN_ALV.
    type-pools: slis.
    field-symbols: <dyn_table> type standard table,
    <dyn_wa>.
    data: alv_fldcat type slis_t_fieldcat_alv,
    it_fldcat type lvc_t_fcat.
    selection-screen begin of block b1 with frame title text-001.
    parameters: p_flds(5) type c.
    selection-screen end of block b1.
    start-of-selection.
    *build the dynamic internal table
    perform build_dyn_itab.
    *write 5 records to the alv grid
    do 5 times.
    perform build_report.
    enddo.
    *call the alv grid.
    perform call_alv.
    *Build_dyn_itab
    form build_dyn_itab.
    data: new_table type ref to data,
    new_line type ref to data,
    wa_it_fldcat type lvc_s_fcat.
    *Create fields .
    clear wa_it_fldcat.
    wa_it_fldcat-fieldname = 'name1'.
    wa_it_fldcat-datatype = 'mara-matnr'.
    wa_it_fldcat-intlen = 5.
    append wa_it_fldcat to it_fldcat .
    *clear wa_it_fldcat.
    wa_it_fldcat-fieldname = sy-index.
    wa_it_fldcat-datatype = 'CHAR'.
    wa_it_fldcat-intlen = 5.
    append wa_it_fldcat to it_fldcat .
    do p_flds times.
    clear wa_it_fldcat.
    wa_it_fldcat-fieldname = sy-index.
    wa_it_fldcat-datatype = 'CHAR'.
    wa_it_fldcat-intlen = 6.
    append wa_it_fldcat to it_fldcat .
    enddo.
    *Create dynamic internal table and assign to FS
    call method cl_alv_table_create=>create_dynamic_table
    exporting
    it_fieldcatalog = it_fldcat
    importing
    ep_table = new_table.
    assign new_table->* to <dyn_table>.
    *Create dynamic work area and assign to FS
    create data new_line like line of <dyn_table>.
    assign new_line->* to <dyn_wa>.
    endform.
    *Form build_report
    form build_report.
    data: fieldname(20) type c.
    data: fieldvalue(5) type c.
    data: index(3) type c.
    field-symbols: <fs1>.
    do p_flds times.
    index = sy-index.
    *Set up fieldvalue
    concatenate 'FLD' index into
    fieldvalue.
    condense fieldvalue no-gaps.
    assign component index of structure <dyn_wa> to <fs1>.
    <fs1> = fieldvalue.
    enddo.
    *Append to the dynamic internal table
    append <dyn_wa> to <dyn_table>.
    endform.
    *CALL_ALV
    form call_alv.
    data: wa_cat like line of alv_fldcat.
    *clear wa_cat.
    wa_cat-fieldname = 'matnr'.
    wa_cat-seltext_s = sy-index.
    wa_cat-outputlen = '10'.
    append wa_cat to alv_fldcat.
    do p_flds times.
    clear wa_cat.
    wa_cat-fieldname = sy-index.
    wa_cat-seltext_s = sy-index.
    wa_cat-outputlen = '6'.
    append wa_cat to alv_fldcat.
    enddo.
    *Call ABAP List Viewer (ALV)
    call function 'REUSE_ALV_GRID_DISPLAY'
    exporting
    it_fieldcat = alv_fldcat
    tables
    t_outtab = <dyn_table>.
    endform.
    Hope this will help, reward if found usefull.
    Cheers,
    Ram.

Maybe you are looking for