Restore default work area bar

Hi folks, how do I restore the default work area bar in PE10 so that the work area corresponds with the full length of all clips in the timeline? I accidentally shortened the work area, have searched help and googled but have not been able to restore the default. Regards, Phil

Bill,
I could not agree more. Once, that knurled "box" was actually a BOX, and easy to spot. In the continued "streamlining" of the GUI, I feel that the designers are making too much, too difficult to see. I am becoming less, and less inclined to like the GUI. Maybe I am just used to having everything clearly deliniated, right in front of me (streamlined, or not), and now I have to really hunt all over, to do what I am used to doing. Maybe for a brand new user, with Steve's book at hand, it is more intuitive, but as a Premiere user for many years, I am often lost, and have to search. I also feel that many operations are not in logical locations - I am still a bit miffed that the output functions were moved from the Export menu, to Share, which is now Publish+Share.
Years ago, Kai Krause left the Adobe Photoshop team, and formed his own company. His first product was Kai's Power Tools, which was a very useful set of Filters, that were not then included in Photoshop. Everyone rushed to add that as a plug-in, and I found it very useful. He followed Power Tools with Convolver, with even more Filters. However, his team designed a totally new interface. Almost every pixel in that interface did something. There were few noticable "buttons," and one had to randomly click all over the interface, then things would happen to the image. However, as one never knew WHAT was chosen, it was totally impossible to repeat, say with some attribute change. Critics praised that innovative interface, but commercial users shunned it, like a very bad plague. If they found a combo of pixel pushes, that did something they liked, but wanted to repeat that, with a change, or two, or make a simple adjustment to suit a client, it was impossible. One had to start over, begin clicking on, or click-dragging on random pixels, hoping to get back to something close to what they had. Because nearly every pixel was active, who knew what they had done previously? The GUI won many design awards, but it failed in the marketplace, which was about 99% commercial back in those days. It also haunted Kai Krause, when he released more traditional plug-ins, as most users still remembered Convolver. It was more of a video game, based on an Imported image, than a useful tool.
The software reviewers seem to love the more streamlined GUI's, but then they only use the program, perhaps once, or twice, to write their articles. They get caught up in the "look," and miss having to actually use the program.
Hunt

Similar Messages

How do you reset the Work Area Bar to auto adjust?

This is something that's been a thorn in my side for a while. Maybe I'm just being OCD about it... but I've been wondering if there is a way, once you reposition the I / O points of the Work Area Bar (WAB) you can get Pr to go back to auto adjusting it to the end of your clip.
You can double-click it to get it to expand to the full length of the sequence, if you remember to do that... Sometimes I'm in a rush, or I have 10 sequences and I miss the fact that my WAB is not all the way to the end. I select and batch drag them all to Media Encoder and *POW*... I've forgotten to stretch the Out to end on one sequence ... and I have to re-render. A pain, yes, something I should have double checked, but at 2am these things can get missed.
So, can you get the Work Area Bar to auto adjust again?
If yes, it's probably something ridiculously obvious – but I'll take it!
Thanks
Stephen

I would have an issue with auto or a default for a number of reasons.
Not least this one...
I now place dummy clip ( black video) a distance off the end of my sequence to prevent the End of Sequence Marker displaying at the end of my edited material. I dont want that included in an export.
Here is another...
As I get to lock down and I am sending previews to clients...I insert Black Video head and tail of the edit so that the preview does not start jarringly on first frame video. I have I and Os marked so that I can simply export "Program at length (without black head and tail) when I come to master.
and...
Often I have edit versions (TVCs) on the same time line ( sequence) and I need to adjust WAB or I/Os to export them separately.
Automating stuff to eliminate our dumb moments doesnt help much because it just opens the chance of another dumb moment driven by expectation and forgetfulness. .
Mental checklist is the only way IMHO.

WAB - Work Area Bar - What's That?

We get a lot of questions on the WAB (the Work Area Bar) in all versions of Premiere. Many of those questions come when someone has accidentally reset the WAB, and cannot find out why parts of their Timeline are not Rendering, or maybe Exporting. Though there are some subtle differences between versions, it basically works the same way.
It can be used for several functions:
It can limit the area of a Timeline, that is Rendered
It can limit the area of a Timeline, that is Exported, with most Export/Share formats
It can act as a ruler to tell you how long, say 4 Clips, plus two partial Clips will be - useful for things like adding music to just part of the Timeline
It has some dynamic features, and Stan Arthur covers many of them in his TUTORIAL on using the WAB. His example is done in PrPro CS 5/5.5, but the functions are almost identical in earlier versions of PrPro and also PrE.
As Stan did not cover using the WAB as a "ruler" I have added an image showing how to access that function - just hover the cursor over the little box in the middle of the WAB and read the info shown. I find this particularly useful, when I need to know exactly what Duration I need for a particular part of the Timeline, when doing a SmartSound music piece.
Hope that this helps answer the questions on the WAB.
Hunt

Because the GUI has changed a bit in PrE 11, here is a view of the WAB "brackets," and then the setting to Share only the WAB in the Share settings:
Hunt

Work Area Bar to Clip ?

PPro CS3 advertises the same facility which worked in previous versions for ALT-clicking the work area bar to set the work area to contiguous clips from the CTI.
ALT-click doesn't do this on my system, though, even after resetting Preferences. Sets the work area to cover the whole sequence even when there are significant gaps.
I've tried all other likely modifiers without success. Have I missed a trick, is my system an exception, or is this a bug?
PPro CS3.1.1(374), XP SP2, Core 2 Duo 2.8, 2Gb RAM, NVidia 8800GTX, all drivers etc up to date.

I tried in both CS3 and 2.0 and neither version does anything when I Alt+click on the work area bar. Targeting different tracks and making clip selections made no difference. I would recommend you file a bug report.
Cheers
Eddie
Forum FAQ
Premiere Pro Wiki
- Over 300 frequently answered questions
- Over 100 free tutorials
- Maintained by editors like
you

CS4: How do I get the Work Area Bar unstuck?

I have the Work Area Bar stuck on the right side of the work area with the Start & End both at 12:38:28. I can't seem to drag the Start indicator to take it to the beginning position on the left.
How do I get the Work Area Bar unstuck?

Stan,
Thanks the double-click worked!

Work area bar has a mind of it's own!

Using premiere pro cs4. when i adjust the work area bar to the in and out points i want it changes everytime i zoom in and out of the timeline, it also sometimes follows the red input indicator??? Its driving me crazy! Also i am sending out vision from my timeline down to TV networks, not live but sometimes the vision goes to air 10 minutes after sending.... I am having trouble keepiong the timeline running smotth even after i have rendered everything in the work area bar? Any tips on how to get this running smooth or is it a lack of ram issue? (i have 4GB at the moment)
thanks in advance
paul

If you are still under warranty, take the computer to an Apple store or an AASP. Whichever is more convenient for you.

HELP!!! Work area bar / export issue in Premiere CS4

I have a project that is several hours in length. There is a small part, about 5 minutes worth, that I need to export. I have set the work area bar for just that area. However, no matter what I do, it exports my entire sequence. How can I get this to ONLY export the work area? Anyone else had this issue?

>Does this mean that the prior feature [...] has been discontinued by Adobe in CS4?
That statement makes it clear you did not read this entire thread. Click the
Show All Messages link to see the entire thread.
Let us know what you try and what the result is.
Cheers
Eddie
PremiereProPedia (
RSS feed)
- Over 300 frequently answered questions
- Over 250 free tutorials
- Maintained by editors like
you
Forum FAQ

Work area bar in/out -point setzen,P Elements 12

wie kann ich den work area bar in/out -point setzen, alt+[ / ] (alt+5/6) funktioniert nicht, arbeite mit einem IMac

berend1
Thank you for posting your question and good job finding the solution yourself.
Apparently you are a Premiere Elements 12 Mac user who wanted to set the gray tabs of the WorkArea Bar to span a specific area of your Timeline and the shortcut Alt + [ and Alt + ] were not working for you.
Your solution was to go to Edit Menu/Keyboard Customization/Windows and the Timeline category and change
Set Work Area Bar In Point from Alt+[ to 5
and
Set Work Area Bar Out Point from Alt+] to 6
That worked for you. Good job.
Thank you.
ATR

I cant make the restore defaults work in fire fox

I lost google as my default search engine and when I try to restore default search engines the box is grayed out. All I have is an option for Firefox Add-ons. I am running xp3

Do the following:
Upgrade to Firefox 16.0.1: [[Update Firefox to the latest version]]
Then
Install [https://addons.mozilla.org/en-US/firefox/addon/searchreset/ This]. Your Search Engine should now be Reset to Google

Internal table & Work area

Hi Experts,
I am a novice to ABAP. Can anyone tell me whats the difference b/w internal table and work area. In writing function modules how these will be utilized and in what way.
Regards
ss

HI,
Internal tables are a standard data type object which exists only during the runtime of the program. They are used to perform table calculations on subsets of database tables and for re-organising the contents of database tables according to users need.
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb35de358411d1829f0000e829fbfe/content.htm
Difference between Work Area and Header Line
While adding or retrieving records to / from internal table we have to keep the record temporarily.
The area where this record is kept is called as work area for the internal table. The area must have the same structure as that of internal table. An internal table consists of a body and an optional header line.
Header line is a implicit work area for the internal table. It depends on how the internal table is declared that the itab will have the header line or not.
e.g.
data: begin of itab occurs 10,
           ab type c,
           cd type i,
        end of itab. " this table will have the header line.
data: wa_itab like itab. " explicit work area for itab
data: itab1 like itab occurs 10. " table is without header line.
The header line is a field string with the same structure as a row of the body, but it can only hold a single row.
It is a buffer used to hold each record before it is added or each record as it is retrieved from the internal table. It is the default work area for the internal table
1) The difference between
whih header line and with out heater line of internal table.
ex:-
a) Data : itab like mara occurs 0 with header line.
b) Data: itab like mara occurs 0.
-While adding or retrieving records to / from internal table we have to keep the record temporarily.
-The area where this record is kept is called as work area for the internal table.
-The area must have the same structure as that of internal table. An internal table consists of a body and an optional header line.
-Header line is a implicit work area for the internal table. It depends on how the internal table is declared that the itab will have the header line or not.
a) Data : itab like mara occurs 0 with header line.
table is with header line
b) Data: itab like mara occurs 0.
table is without header line
2)work area / field string and internal table
which one is prefarable for good performance any why ?
-The header line is a field string with the same structure as a row of the body, but it can only hold a single row , whereas internal table can have more than one record.
In short u can define a workarea of an internal table which means that area must have the same structure as that of internal table and can have one record only.
Example code:
data: begin of itab occurs 10,
ab type c,
cd type i,
end of itab. " this table will have the header line.
data: wa_itab like itab. " explicit work area for itab
data: itab1 like itab occurs 10. " table is without header line.
http://www.allsaplinks.com/faq_abap_internaltables.html
Do reward if it helps,
Regards,
Laxmi

Basic query regarding work-area and select query

hi
dear sdn members,
thanks too all for solving all my query's up till now
i am stuck in a problem need help
1) why basically work-area has been used ? the sole purpose
2) different types of select query ? only coding examples
note: no links pls
regards,
virus

hi,
Work Area
Description for a data object that is particularly useful when working with internal tables or database tables as a source for changing operations or a target for reading operations.
WORKAREA is a structure that can hold only one record at a time. It is a collection of fields. We use workarea as we cannot directly read from a table. In order to interact with a table we need workarea. When a Select Statement is executed on a table then the first record is read and put into the header of the table and from there put into the header or the workarea(of the same structure as that of the table)of the internal table and then transferred top the body of the internal table or directly displayed from the workarea.
Each row in a table is a record and each column is a field.
While adding or retrieving records to / from internal table we have to keep the record temporarily.
The area where this record is kept is called as work area for the internal table. The area must have the same structure as that of internal table. An internal table consists of a body and an optional header line.
Header line is a implicit work area for the internal table. It depends on how the internal table is declared that the itab will have the header line or not.
.g.
data: begin of itab occurs 10,
ab type c,
cd type i,
end of itab. " this table will have the header line.
data: wa_itab like itab. " explicit work area for itab
data: itab1 like itab occurs 10. " table is without header line.
The header line is a field string with the same structure as a row of the body, but it can only hold a single row.
It is a buffer used to hold each record before it is added or each record as it is retrieved from the internal table. It is the default work area for the internal table.
With header line
SELECT.
Put the curson on that word and press F1 . You can see the whole documentation for select statements.
select statements :
SELECT result
FROM source
INTO|APPENDING target
[[FOR ALL ENTRIES IN itab] WHERE sql_cond]
Effect
SELECT is an Open-SQL-statement for reading data from one or several database tables into data objects.
The select statement reads a result set (whose structure is determined in result ) from the database tables specified in source, and assigns the data from the result set to the data objects specified in target. You can restrict the result set using the WHERE addition. The addition GROUP BY compresses several database rows into a single row of the result set. The addition HAVING restricts the compressed rows. The addition ORDER BY sorts the result set.
The data objects specified in target must match the result set result. This means that the result set is either assigned to the data objects in one step, or by row, or by packets of rows. In the second and third case, the SELECT statement opens a loop, which which must be closed using ENDSELECT. For every loop pass, the SELECT-statement assigns a row or a packet of rows to the data objects specified in target. If the last row was assigned or if the result set is empty, then SELECT branches to ENDSELECT . A database cursor is opened implicitly to process a SELECT-loop, and is closed again when the loop is ended. You can end the loop using the statements from section leave loops.
Up to the INTO resp. APPENDING addition, the entries in the SELECTstatement define which data should be read by the database in which form. This requirement is translated in the database interface for the database system´s programming interface and is then passed to the database system. The data are read in packets by the database and are transported to the application server by the database server. On the application server, the data are transferred to the ABAP program´s data objects in accordance with the data specified in the INTO and APPENDING additions.
System Fields
The SELECT statement sets the values of the system fields sy-subrc and sy-dbcnt.
sy-subrc Relevance
0 The SELECT statement sets sy-subrc to 0 for every pass by value to an ABAP data object. The ENDSELECT statement sets sy-subrc to 0 if at least one row was transferred in the SELECT loop.
4 The SELECT statement sets sy-subrc to 4 if the result set is empty, that is, if no data was found in the database.
8 The SELECT statement sets sy-subrc to 8 if the FOR UPDATE addition is used in result, without the primary key being specified fully after WHERE.
After every value that is transferred to an ABAP data object, the SELECT statement sets sy-dbcnt to the number of rows that were transferred. If the result set is empty, sy-dbcnt is set to 0.
Notes
Outside classes, you do not need to specify the target area with INTO or APPENDING if a single database table or a single view is specified statically after FROM, and a table work area dbtab was declared with the TABLES statement for the corresponding database table or view. In this case, the system supplements the SELECT-statement implicitly with the addition INTO dbtab.
Although the WHERE-condition is optional, you should always specify it for performance reasons, and the result set should not be restricted on the application server.
SELECT-loops can be nested. For performance reasons, you should check whether a join or a sub-query would be more effective.
Within a SELECT-loop you cannot execute any statements that lead to a database commit and consequently cause the corresponding database cursor to close.
SELECT - result
Syntax
... lines columns ... .
Effect
The data in result defines whether the resulting set consists of multiple rows (table-like structure) or a single row ( flat structure). It specifies the columns to be read and defines their names in the resulting set. Note that column names from the database table can be changed. For single columns, aggregate expressions can be used to specify aggregates. Identical rows in the resulting set can be excluded, and individual rows can be protected from parallel changes by another program.
The data in result consists of data for the rows lines and for the columns columns.
SELECT - lines
Syntax
... { SINGLE }
| { { } } ... .
Alternatives:
1. ... SINGLE
2. ... { }
Effect
The data in lines specifies that the resulting set has either multiple lines or a single line.
Alternative 1
... SINGLE
Effect
If SINGLE is specified, the resulting set has a single line. If the remaining additions to the SELECT command select more than one line from the database, the first line that is found is entered into the resulting set. The data objects specified after INTO may not be internal tables, and the APPENDING addition may not be used.
An exclusive lock can be set for this line using the FOR UPDATE addition when a single line is being read with SINGLE. The SELECT command is used in this case only if all primary key fields in logical expressions linked by AND are checked to make sure they are the same in the WHERE condition. Otherwise, the resulting set is empty and sy-subrc is set to 8. If the lock causes a deadlock, an exception occurs. If the FOR UPDATE addition is used, the SELECT command circumvents SAP buffering.
Note
When SINGLE is being specified, the lines to be read should be clearly specified in the WHERE condition, for the sake of efficiency. When the data is read from a database table, the system does this by specifying comparison values for the primary key.
Alternative 2
Effect
If SINGLE is not specified and if columns does not contain only aggregate expressions, the resulting set has multiple lines. All database lines that are selected by the remaining additions of the SELECT command are included in the resulting list. If the ORDER BY addition is not used, the order of the lines in the resulting list is not defined and, if the same SELECT command is executed multiple times, the order may be different each time. A data object specified after INTO can be an internal table and the APPENDING addition can be used. If no internal table is specified after INTO or APPENDING, the SELECT command triggers a loop that has to be closed using ENDSELECT.
If multiple lines are read without SINGLE, the DISTINCT addition can be used to exclude duplicate lines from the resulting list. If DISTINCT is used, the SELECT command circumvents SAP buffering. DISTINCT cannot be used in the following situations:
If a column specified in columns has the type STRING, RAWSTRING, LCHAR or LRAW
If the system tries to access pool or cluster tables and single columns are specified in columns.
Note
When specifying DISTINCT, note that you have to carry out sort operations in the database system for this.
SELECT - columns
Syntax
| { {col1|aggregate( col1 )}
{col2|aggregate( col2 )} ... }
| (column_syntax) ... .
Alternatives:
1. ... *
2. ... {col1|aggregate( col1 )}
{col2|aggregate( col2 )} ...
3. ... (column_syntax)
Effect
The input in columns determines which columns are used to build the resulting set.
Alternative 1
Effect
If * is specified, the resulting set is built based on all columns in the database tables or views specified after FROM, in the order given there. The columns in the resulting set take on the name and data type from the database tables or views. Only one data object can be specified after INTO.
Note
If multiple database tables are specified after FROM, you cannot prevent multiple columns from getting the same name when you specify *.
Alternative 2
... {col1|aggregate( col1 )}
{col2|aggregate( col2 )} ...
Effect
A list of column labels col1 col2 ... is specified in order to build the resulting list from individual columns. An individual column can be specified directly or as an argument of an aggregate function aggregate. The order in which the column labels are specified is up to you and defines the order of the columns in the resulting list. Only if a column of the type LCHAR or LRAW is listed does the corresponding length field also have to be specified directly before it. An individual column can be specified multiple times.
The addition AS can be used to define an alternative column name a1 a2 ... with a maximum of fourteen digits in the resulting set for every column label col1 col2 .... The system uses the alternative column name in the additions INTO|APPENDING CORRESPONDING FIELDS and ORDER BY. .
Column labels
The following column labels are possible:
If only a single database table or a single view is specified after FROM, the column labels in the database table - that is, the names of the components comp1 comp2... - can be specified directly for col1 col2 ... in the structure of the ABAP Dictionary.
If the name of the component occurs in multiple database tables of the FROM addition, but the desired database table or the view dbtab is only specified once after FROM, the names dbtab~comp1 dbtab~comp2 ... have to be specified for col1 col2 .... comp1 comp2 ... are the names of the components in the structure of the ABAP Dictionary.
If the desired database table or view occurs multiple times after FROM, the names tabalias~comp1 tabalias~comp2 ... have to be specified for col1 col2 .... tabalias is the alternative table name of the database table or view defined after FROM, and comp1 comp2 ... are the names of the components in the structure of the ABAP Dictionary.
The data type of a single column in the resulting list is the datatype of the corresponding component in the ABAP Dictionary. The corresponding data object after INTO or APPENDING has to be selected accordingly.
Note
If multiple database tables are specified after FROM, you can use alternative names when specifying single columns to avoid having multiple columns with the same name.
Example
Read specific columns of a single row.
DATA wa TYPE spfli.
SELECT SINGLE carrid connid cityfrom cityto
INTO CORRESPONDING FIELDS OF wa
FROM spfli
WHERE carrid EQ 'LH' AND connid EQ '0400'.
IF sy-subrc EQ 0.
WRITE: / wa-carrid, wa-connid, wa-cityfrom, wa-cityto.
ENDIF.
Alternative 3
... (column_syntax)
Effect
Instead of static data, a data object column_syntax in brackets can be specified, which, when the command is executed, either contains the syntax shown with the static data, or is initial. The data object column_syntax can be a character-type data object or an internal table with a character-type data type. The syntax in column_syntax, like in the ABAP editor, is not case-sensitive. When specifying an internal table, you can distribute the syntax over multiple rows.
If column_syntax is initial when the command is executed, columns is implicitly set to * and all columns are read.
If columns are specificied dynamically without the SINGLE addition, the resulting set is always regarded as having multiple rows.
Notes
Before Release 6.10, you could only specify an internal table with a flat character-type row type for column_syntax with a maximum of 72 characters. Also, before Release 6.10, if you used the DISTINCT addition for dynamic access to pool tables or cluster tables, this was ignored, but since release 6.10, this causes a known exception.
If column_syntax is an internal table with header line, the table body and not the header line is evaluated.
Example
Read out how many flights go to and from a city. The SELECT command is implemented only once in a sub-program. The column data, including aggregate function and the data after GROUP BY, is dynamic. Instead of adding the column data to an internal l_columns table, you could just as easily concatenate it in a character-type l_columns field.
PERFORM my_select USING `CITYFROM`.
ULINE.
PERFORM my_select USING `CITYTO`.
FORM my_select USING l_group TYPE string.
DATA: l_columns TYPE TABLE OF string,
l_container TYPE string,
l_count TYPE i.
APPEND l_group TO l_columns.
APPEND `count( * )` TO l_columns.
SELECT (l_columns)
FROM spfli
INTO (l_container, l_count)
GROUP BY (l_group).
WRITE: / l_count, l_container.
ENDSELECT.
ENDFORM.
SELECT - aggregate
Syntax
... { MAX( col )
| MIN( col )
| AVG( col )
| SUM( col )
| COUNT( DISTINCT col )
| COUNT( * )
| count(*) } ... .
Effect
As many of the specified column labels as you like can be listed in the SELECT command as arguments of the above aggregate expression. In aggregate expressions, a single value is calculated from the values of multiple rows in a column as follows (note that the addition DISTINCT excludes double values from the calculation):
MAX( col ) Determines the maximum value of the value in the column col in the resulting set or in the current group.
MIN( col ) Determines the minimum value of the content of the column col in the resulting set or in the current group.
AVG( col ) Determines the average value of the content of the column col in the resulting set or in the current group. The data type of the column has to be numerical.
SUM( col ) Determines the sum of the content of the column col in the resulting set or in the current group. The data type of the column has to be numerical.
COUNT( DISTINCT col ) Determines the number of different values in the column col in the resulting set or in the current group.
COUNT( * ) (or count(*)) Determines the number of rows in the resulting set or in the current group. No column label is specified in this case.
If you are using aggregate expressions, all column labels that are not listed as an argument of an aggregate function are listed after the addition GROUP BY. The aggregate functions evaluate the content of the groups defined by GROUP BY in the database system and transfer the result to the combined rows of the resulting set.
The data type of aggregate expressions with the function MAX, MIN or SUM is the data type of the corresponding column in the ABAP Dictionary. Aggregate expressions with the function AVG have the data type FLTP, and those with COUNT have the data type INT4. The corresponding data object after INTO or APPENDING has to be selected accordingly.
Note the following points when using aggregate expressions:
If the addition FOR ALL ENTRIES is used in front of WHERE, or if cluster or pool tables are listed after FROM, no other aggregate expressions apart from COUNT( * ) can be used.
Columns of the type STRING or RAWSTRING cannot be used with aggregate functions.
When aggregate expressions are used, the SELECT command makes it unnecessary to use SAP buffering.
Null values are not included in the calculation for the aggregate functions. The result is a null value only if all the rows in the column in question contain the null value.
If only aggregate expressions are used after SELECT, the results set has one row and the addition GROUP BY is not necessary. If a non-table type target area is specified after INTO, the command ENDSELECT cannot be used together with the addition SINGLE. If the aggregate expression count( * ) is not being used, an internal table can be specified after INTO, and the first row of this table is filled.
If aggregate functions are used without GROUP BY being specified at the same time, the resulting set also contains a row if no data is found in the database. If count( * ) is used, the column in question contains the value 0. The columns in the other aggregate functions contain initial values. This row is assigned to the data object specified after INTO, and unless count( * ) is being used exclusively, sy-subrc is set to 0 and sy-dbcnt is set to 1. If count( *) is used exclusively, the addition INTO can be omitted and if no data can be found in the database, sy-subrc is set to 4 and sy-dbcnt is set to 0.
if helpful reward points

PPCS3 won't export only the work area to media encoder

I can't figure out why Premiere Pro CS3 is no longer exporting the work area to the media encoder. I CAN successfully export the work area to Encore but even when I select WORK AREA under the RANGE option in EXPORT SETTINGS the media encoder still shows only the entire sequence.
Same results on any sequence or project I've tried.
Any suggestions?

Are you sure you're not confusing the sequence In and Out Points with the Work Area Bar? I've seen people make that mistake before. The Work Area Bar is what controls the "Work Area" export.
If it's not that then you have a real mystery on your hands. :o
Cheers
Eddie
PremiereProPedia
RSS feed)
- Over 350 frequently answered questions
- Over 300 free tutorials
- Maintained by editors like
you
Forum FAQ

PPRO 2014: ALT+[/] won't set working area start/end

ALT+[/] won't work in PPRO 2014. WIndows 7 x64, Russian. Previous PPRO on the same machine and this very installation of Windows responds to ALT+] command and sets the working area just fine, from both Russian and English language keyboard choice.
NOTE: PPRO2014 windows>adobe premiere pro help menu takes me to the adobe keyboard shortcuts that lists this as a valid keyboard shortcut for Adobe PPRO 2014.
Can anyone let me know if there are new shortcuts or something is wrong with my PPRO 2014 installation (files missing)?
Thanks!

Thank you, work area bar is an old habit of mine
[Email flotsam removed.]

Exporting work area in cc 2014 doesnt export actual entire work area

Can't understand what the issue is here. It only exports about 80% of the clip.

Hello,
There's a few things you can try.
1. Make sure the Work Area Bar is extended to the entire length of your sequence. See image below
2. From the Export Settings dialog, change the Source Range to 'Entire Sequence'. See image below.
Best,
Peter Garaway
Adobe
Premiere Pro

Hitting enter key or choosing "render work area" no rendering occurs

I recently migratated all my pictures and projects from one computer to another, new one.
Working with PE12.
I'm trying to render a project that I have created, but when I hit the enter key, or even select "Render Work Area" from the Timeline menu, instead of rendering, it plays back the project.
Anyone knows what is going on?! please?

ATR,
I'm very glad you jumped back in. So, thank you.
I've done everything you have suggested, and I'm getting the same issue. However, there is one observation that could help you further narrow it down.
I'm going to respond to all your suggestions, point-by-point below in order to help you - help me- the best I can
1. I am assuming that you are working in the Expert workspace of Premiere Elements 12. If so, the go to the Quick workspace and try each of the following [ Correct]
a. Hit the Render button above the Filmstrip there [done]
b. Go to Timeline Menu/click on Render Work Area [done]
c. Press Enter key of the computer main keyboard [done]
Did the rendering dialog come up at any time? [YES, (and this has been happening all along), when I try to render, in any of the 3 ways above, I do see a window pop up for a millisecond and then it disappears. I hightly suspect that it is the "render" window that is attempting to open, but just goes away for some reason.
When you went back to the Expert workspace, was there now a green line instead of an orange line over the TImeline content spanned by the gray tabs of the Work Area Bar? [no, still orange coolor]
2. Make a copy of the problem project (File Menu/Save A Copy and renaming it). Open the copy and determine if you can render the Expert workspace Timeline content of that of the Quick workspace Filmstrip.
3. Have you cleared out the preview files in the Adobe Premiere Elements Previews FIle Folder for this problem project? [YES, manually went inside the Adobe Premiere E Previews File and deleted everything] Double check on that. How much free space is there at the location where you have this Adobe Premiere Elements Previews Files Folder? [Plenty of space is left ~ 230GB] Next, go to Edit Menu/Preferences/Media and its Media Cache Datebase and hit the Clean button there to get rid of conformed video files. [Hit the clean button, twice]
4. Next, delete the Premiere Elements 12's settings file named Adobe Premiere Elements Prefs. The route to it in Windows 7, 8, or 8.1 64 bit is
Local Disk C
Users
Owner
AppData
Roaming
Adobe
Premiere Elements
12.0
and in the 12.0 Folder is the Adobe Premiere Elements Prefs file that you delete. If that does not work, delete the whole 12.0 Folder in which the Adobe Premiere Elements Prefs file exists. Be sure to be working with Folder Option Show Hidden Files, Folders, and Drives active so that you can see the path cited. [Wend all the way inside the 12.0 folder, but did not see any file called Adobe Premiere Elements Prefs, so deleted the whole 12.0 folder instead as you suggested]
Just starting my day. We will be watching for further developments. I will be thinking about this some more.
Thanks.
ATR
Add On...Leaving the whys behind can lead to more of the same. So, unless you are in a time crunch to get this project out, let us not give up just yet [ I am not in any rush to get this out, and I not giving up if you aren't . I can tell you like to solve puzzles and I thank you for it.]

Restore default work area bar

Similar Messages

Maybe you are looking for