Red ligne in the timeline

When i am creating a text and sliding it in to the timeline the line on top of it gets red and then impossible to see it in the canvas????????

this is because the video you are working with does not match the sequence settings. Hit command-R or go to sequence->render (choose one of the render selections) to render out the clip. Then you will be able to view it in the canvas. If you would rather only render it at the end, hit RT settings, unlimited RT. This will play through at the fastest speed possible (though frames might be dropped).
I highly recommend keeping it simple and simply hitting command-R.

Similar Messages

Red Line in the timeline by the time code

Hello Again,
Suddenly, a red line appeared in the timeline by the time code? what does it mean? How can I delete it? Thanks again.

Thank you for your feedback.
Yes, I' familiar about the un rendered red lines. The line I'm talking about is right inside the "ruler" as if the digits (minutes/seconds) are crossed out. This line also showing up at the canvass window. I think this came out when i'm doing some keyframing.
Thanks again.

How can I follow the red line in the timeline?

Bit of a basic question, but when i play through a song i want it to follow with the red line, but it keeps going off the screen and it never follows it
how do i put it back on?

thanks

Greetings, I am working in Final Cut Pro 7. In the timeline some clips show as offline. I tried going to sequence and reconnecting to media but it does not work. I can still see the video in the timeline and work with it. It just has the red box.

Greetings, I am working in Final Cut Pro 7. In the timeline some clips show as offline. I tried going to sequence and reconnecting to media but it does not work. I can still see the video in the timeline and work with it. It just has the red box. Thanks! Olga

If the clips are not actually missing, you could try to refresh the timeline by using cmd-0 and then going to the timeline options tab. Then select name only where it says "thumbnail display". Press ok to accept the change, then repeat the process to add thumbnails back to your timeline.

Red vs green line above graphic in the timeline

I recently needed to trash my FCP preferences and now whenever I add a graphic to the timeline, I get a red line above it indicating that the graphic needs to be rendered before I can view it. Before trashing the preferences, I use to get a green line above the graphics which would allow me to at least see the graphic over the video without rendering it.
Any idea how I can get back to the green line?
thanks.

You may want to increase the amount of RAM dedicated to the "stills cache". The setting can be found in the FCP system preferences>Memory.
If you have 4 GB or more in the machine, bump this up above the 10% or so that is the default setting.
x

Can only see first and last frame of clip in the timeline HELP PLEASE

Hi, my first time and I did look for an answer, but can't find one. I have premiere elements 4 and I am trying out ver. 9. In ver. 4 the clips in the timelin shows all the frames, but in ver. 9 it only shows the first and last frame of the clips. Is there any way to make all the frames show. By "all the frames", I mean the clips fill with frames.I liked to see all the frames in the timeline, it is easier for me to select and trim the bits out.
My specs are Core 2 Duo 6750, Nvidia 8600GTS, 4G Ram, Vista Home Premium. 3 HDD 3TB.
Thank you for answering
Werner

As for the GUI, PrE had one more like PrPro (the early versions), up through PrE 3. With PrE 4, they streamlined the GUI (and some of the operation), and went with the "dark look." PrPro went in that direction starting with CS3, and now, the two programs' GUI looks more alike - darker. Personally, I like PrPro 2.0's brighter GUI. Now, one can alter the brightness, but the contrast can work against doing much of that - give me the lighter GUI....
The look of PrE 4 thru PrE 9 is very similar, though things have moved about some. Still the look is similar. Same for PrPro CS 3 through CS 5.5.
As for the trial, things have changed in PrPro, as of CS 5.5. Once, the PrPro trial was very crippled, but had no watermark. No more. No crippling, and still no watermark. The trial for PrE is far less crippled, but does have the watermark. We do not know what changes might be coming with the trial of PrE10. We will just have to wait and see. One great option that Adobe offers is the 30-day, money-back guarantee. If you buy Premiere (either flavor), and use it for 29 days, but do not like it, then you return it for your money back. This is the full-paid version (both flavors) with nothing crippled, and no watermark. Not that many companies make such an offer. Basically, on can use the trial for 30 days, to see some of the powers of the program, and then buy it, and try it fully for another 29 days. If not completely satisfied, they get their money back - essentially a 59 day trial.
Were I doing AVCHD, I would definitely look at buying PrE 9, and giving it a 29 day shakedown. The only caveat is that AVCHD requires a lot of computer "horsepower," and not all computers (especially if more than a year, or so old) are up to that task. I find it amazing that a consumer format, like AVCHD, requires more computer power to process, than most professional formats, until one gets up to, say RED 2K/4K. However, that is the nature of the H.264 CODEC, and by that, I mean all H.264, not just the AVCHD version.
Good luck and happy editing,
Hunt

Slide order in the timeline

I have been shown how to do a very specific task in Flash Pro CS5. I have five slides in my timeline, with buttons that include links to product pages on our website. These five slides comprise a movie, with each slide being displayed for a few seconds and it repeatedly cycles through the five slides in a banner at the top of our home page.
In addition there is a navigation bar below my slide images with a play and pause option, plus the five slide numbers so the viewer can navigate from slide to slide manually.
I have been asked to change the order of the slides so that slide #5 now becomes slide #1 and slide #1 becomes slide #2, and so on. I can easily switch the images and links so that the slides are in a different order in my file, but now the navigation bar below does not work. In the Actions panel, the #1 button in the navigation bar still appears to be linked to slide 1, which now has the new images, yet the nav bar does not respond to clicks anymore.
How was my nav bar disabled when I switched the images and links around between the slides? and how can I correct this?
(Keep in mind, I know NOTHING else about Flash except how to replace the images and change the button links in each slide, which I do monthly, as this is the top banner on our website.)

Thanks so much for your reply, Rob.
The slides are on the timeline and each one is displayed as the playback head moves from one frame to another. I do this in my file by dragging the red rectangle with the red line extending from below it across the timeline, which is on a layer that the original author named MC Content. However, when I go to the layer called Scene 1 where the navigation bar is, the red rectangle at top will not move when I try to drag it.
I don't know what the action script does except to link my button to a page on our website. The code looks like this for slide 1.
slide1_1_btn.addEventListener(MouseEvent.CLICK, myButtonFunction5_1);
function myButtonFunction5_1(event: MouseEvent) {
var request:URLRequest = new URLRequest("http://www.tobaccofreecatalog.org/ProductDetails.aspx?id=2&itemno=J660");
navigateToURL(request,"_self");
I don't know if the slides use actionscript to show and hide each one.
Now that I look at it, maybe all I need to do is change myButtonFunction5_1 to myButtonFunction1_1 on the above code?
I don't know how to answer your last question. The individual images for each slide are jpegs I created in InDesign, but I don't know how they are referenced or what that means.
Colleen

Hi, I've just downloaded the latest release 10.1.1 and now I do not see any more correctly my clips either in the canvas and in the timeline. Playing clips, they now appears with garbled images, completely unstables: I can not editing in these conditions!

Hi, I've just downloaded the latest release 10.1.1 and now I do not see any more correctly my clips either in the canvas and in the timeline. Playing clips, they now appears with garbled images, completely unstables: I can not editing in these conditions!
Anyone can help me?
Thank you, Claudio

Hi Russ, Thank you for your reply!
System Spec:
2x2.26 Ghz QUAD-CORE
12 GB RAM 1066 MHz DDR3
I've stored the library in HARD DISK which is installed inside my computer (1 TB capacity) and different from my hard disk in which I've installed all my applications (600 GB capacity).
I've installed FCP since 2001, bought FCP X in 2012: never had a problem. Yesterday I was editing my video of my last vacations (in California!) and I have updated FCP X, downloading FCP X 10.1.1: then the problem!
Strange is the fact that I've just tried to export a short project, I can see the final product quite well.
What is impossible is playing the clips within Final Cut: they are jumpimg, moving, presenting some frame in green or red ...
Everything all right in iMovie.
I've just checked the RAM: 9GB out of 12 GB is busy, could this be the problem?
Motion is very slow: for 20 sec of project, it takes minutes to play. And once again, if you finalize the projet and export it in Quicktime, you can see it correctly.
I do hope you may suggest something, I'm getting crazy!
Thank you in adavance
Claudio

Is it Possible to Preview Sound While Scrubbing the Timeline Using Hotkeys?

If I have a sound in my timeline, I can scrub through the timeline by dragging the red box and it will preview the sound that plays on every frame. However, I have hotkeys set to scrub through my timeline (, & .), and when I use them, the sound does not in fact preview. Is there a way to set up my hotkeys so the sound will in fact preview?

Hello,
I don't believe there is a way to view images in the files
panel.
However, there's a quick way to see them if you're using
Windows.
Select your image folder in the Files Panel.
Right click and choose "Explore".
It opens a window where you can see all the images in that
folder.
It's much faster than scrolling through the assets, clicking
the file names
and reading the paths to know where they are.
This is very handy whether you have image folders in
different directories
(for organization and cleaner img src paths in the pages
within the
directory) or if you just dump them all in a folder in the
root.
On my wishlist: Hover over the image name in the files panel
and a small
box, like a tool tip, displays the image.
Maybe someday.
Take care,
Tim
"dexter manika" <[email protected]> wrote in
message
news:go4to8$k1m$[email protected]..
> sorry in advance for what probably is a dumb question
with a simple
> solution.
>
> i realize i can view images in the assets panel-- but is
it possible to
> view
> image files while in the files panel instead?
>
> i have a lot of images organized within folders in the
files panel-- so
> it's
> easier there to locate and visulalize an image-- than
scrolling down the
> long
> list in the assets panel.
>
> thanks.
>

My clips have a yellow line on the timeline sequence. Does this affect my video quality output if I don't render?

I use Adobe CS 6 to edit and I use Sony NX 3 to record. Every time I import my clips. It has a yellow line on the timeline sequence, even when I make new clip from the sequence.. My question is, does this affect my video quality output if i did not render the yellow line out? Please someone help me

Please see this link for more info about red and yellow bars - http://blogs.adobe.com/premierepro/2011/02/red-yellow-and-green-render-bars.html
If you shoot 1080p, you will likely have better results going to DVD than if you start with 1080i. It's hard enough downscaling with decent quality, then if you add in interlacing issues...
When exporting from Premiere to create a DVD, choose "MPEG-2 DVD" as the format, and then choose a preset such as "NTSC Widescreen Progressive".
There is a checkbox at bottom of export window for "Max Render Quality" - use that for best downscaling results.
Use 2-Pass VBR encoding. Use a bitrate calculator to determine best bitrate for length of movie, or quick option is 560/minutes = bitrate. But don't exceed 8.0 on shorter movies. I typically round down a little for safety margin, such as 560/120 = 4.6, encode at 4.5 and no worries.
The export will result in TWO files, .m2v video and .wav audio, import both into Encore for authoring. Encore will convert the .wav to Dolby AC3, reducing file size. Video should NOT get transcoded. And as others said, don't expect HD quality when viewing a DVD...definitely not HD video any longer. But do be sure to use an upscaling player, this makes all the difference. If you run a yellow composite cable from DVD to TV, it will look horrible. Use HDMI with upscaling DVD/Blu-ray player for improved result.
Good luck
Jeff Pulera
Safe Harbor Computers

How do I restore my video/audio in the Timeline of my project?

The whole timeline has windows that are red that say Media Offline. Where did my video/audio go??
Where do I find it? How do I restore it into the timeline I was working on with the project. When I open the project I also get a question that wants to know where is a specific file pertaining to this project.

Or, was it on a DVD, that you Imported directly, and now that DVD is not in the drive/burner?
When media is listed as Off-line, just as Steve mentions, the link between the Project file (.PREL) has been broken. This can happen, when one Moves files, Renames files, or those files are, for some other reason, not where the program last saw them. This ARTICLE will give you a bit more background on the .PREL files, plus some tips on Save/Save_As, etc.
Usually, one gets warning messages, and PrE will help you locate your files. It does a good job of this. Did you get any messages, when you Opened this Project? Did you Move, or Rename any media files?
Good luck,
Hunt

Just wondering whether rendering is required for unedited AVI on the Timeline?

I just bought Premiere Elements 11.0. I was currently using Premiere Elements 3.02. In 3.02 When importing a standard AVI File to the timeline, only transitions and Titles needed rendering before exporting to DvD. However, I noticed when doing the same project in 11.0, There is no Red Lines above the titles or Transitions for it to be rendered. When I cliked on Render Project, it seemed it was rendering the entire AVI file and it took a very long time. Is this Normal for 11.0? or is there a Patch I need?

orlandoVideography
Just to add a little bit more to the story of "rendering the Premiere Elements Timeline content".
Given that rendering the Timeline content is for previewing purposes (to get the best possible preview of your Timeline content when it plays back in the Edit Mode monitor. You can do that in 3 ways in Premiere Elements 11
a. Pressing the Enter Key of the computer main keyboard
b. Expert workspace, Timeline Menu at top of workspace/Render Work Area
or
c. The Render tab to the right above the Timeline
You do not have to do this type of rendering for the program to allow you to move forward in the program. But, it is your window of opportunity to catch a problem sooner than later.
But, there are 3 indicators used by the program to tell you whether or not it feels that you have the best possible preview.
a. orange line (red line used in versions earlier than 11) OVER the Timeline content is program indicator for rendering recommendation
b. no colored line OVER the Timeline content and green line OVER the Timeline content are program indicators for "you have the best possible preview".
c. waving your mouse cursor over the Render button above the Expert workspace Timeline results in a pop up recommending rendering if the program decides you are not getting the best possible preview.
The no colored line comes into this when you import a file for the first time to the Timeline and it is a native format. But once you edit this file, orange line with all its implications - render. After this render, that file will then only use the orange/green indicators and not the no colored line for it.
As always, rendering is most appropriate for transitions, effects, titles, and non native formats.
Remember to keep watch for pile ups of the preview files on the hard drive....if you have a SD project, the previews (for photos or video) are DV.AVI 720 x 480 @ 29.97 interlaced frames per second and, for HD project (for photos and video), they are MPEG2.mpeg. 960 x 540 @ 29.97 interlaced frames per second, Upper Field First accompanied by some other files such as .xmp.
And, the program does help out...if you want to render and the program decides you have the best possible preview, then all you will get from trying to initiate Timeline rendering is playback of the Timeline with no rendering.
Then there is the old story of saving/closing a project with a rendered Timeline only to reopen the project and find an orange/red line over the content. Does not happen too often lately, but it can be a puzzlement. More on that other time if necessary.
ATR
ATR

Send to Speedgrade dpx workflow only converts about half of the timeline

I am using RED footage (and some QT stock) and sending this footage from Premiere CC to Speedgrade using dpx files.
(I can't use EDL because of multiple resizes/reframes throughout the project, so please don't consider that as an option)
I have split the 100 minute project into 5 20-minute reels, each with its own Premiere sequence.
When I send a sequence, the Speedgrade file is created as well as the folder structure for the dpx's. This all seems perfect.
The problem is that Premiere does not fill all of the dpx folders. It leaves about half of them empty and skips to other folders.
This seems random and I cannot see any pattern as to what would cause this. The error is repeatable in that each export of a given sequence yields the same empty folders.
The Premiere sequences play just fine in Premiere.
Premier gives no errors when exporting. It appears to finish successfully, but just skips certain areas.
In Premiere I've tried batch disabling/enabling clips as well as duplicating sequences and cutting/pasting the clips into the duplicate sequence.
Any help would be apprecited - the lack of options is frustrating.

Hello Epasc, I am also a newbie to speedgrade, and honestly I am still trying to see if it is actually 100% usable for my needs. (very simple ones..)
anyway what is happening to you happened also to me in a little different way, the clips that were missing where at the end of the timeline and not in the middle.
We then found out that it was a problem with the Hard Disk not having enough GB available for all the dpx files that Speedgrade needed to create to complete the task. ( for a 9 minutes shortmovie shot on 5dm2 it created a 60gb folder with the DPX inside it , so if you're working with R3D material, it must be way more than that )
if your hard disk has already a lot of GB available, then this is not your case.
check it out. if it is already full ( I am talking about the Hard Disk containing the DPX and SG project folder ) that may be the problem
Cheers from Italy

When I drop anything into the timeline I have to render it to view it.

I am working with 2 sequences in one project. In one sequence I can drop images, video clips, text onto the timeline and I can view it, showing a green line. No problem. I switch to the other sequence and every time I do anything to the timeline I have a red line and have to render each and ever clip to review the work I just did. I don't understand why the two are different. Any suggestions? Thanx

#28 Having to render every clip in the timeline
Shane's Stock Answer #28: When I put a clip in the timline, I have to render it before it will play. Why?
Your clip settings MUST match your timeline settings. If you have DV/NTSC material, you need a DV/NTSC timeline. The frame rate, audio rate and dimensions (4:3, 16:9) all need to match exactly. In Final Cut Pro 6, this is easy, because when you drop a clip into the timeline, it asks if you want to set up the timeline to match the settings of the first clip you drag into it. Click YES and you are ready to go.
However, in FCP 5.1 and earlier, it is a bit trickier.
The most important thing you need to do is properly set up your project from the start, and the best way to do this is to choose a setting from the Easy Setups, located under the Final Cut Pro menu.
Once you do this, you’ll need to create a new sequence. This is because the sequence that is already in your new project is setup for the typical default setting of DV/NTSC, or for the settings of your last project, which might not match what you are currently working with. So delete SEQUENCE 1 and create a new sequence:
This new sequence will contain the settings you chose in the Easy Setup menu, and should match the format you captured.
Shane

NMP random crashes when modifying the timeline.

FCPx is crashing/exiting when modifying the timeline. Happens randomly few times an hour - sometimes more. I updated all apps except going to YOSEMITE and it still crashes.
I`ll paste a log report below for what its worth.
Is there any apple staff that look at logs or is it just community aid?
Thanks anyone who can advise!
Process: Final Cut Pro [274]
Path:
/Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier:
com.apple.FinalCut
Version:
10.1.3 (251130)
Build Info:
ProEditor-25113000038000000~1
App Item ID:
424389933
App External ID: 668174963
Code Type:
X86-64 (Native)
Parent Process:
launchd [140]
Responsible:
Final Cut Pro [274]
User ID:
501
Date/Time:
2014-10-28 22:19:51.027 -0400
OS Version:
Mac OS X 10.9.5 (13F34)
Report Version: 11
Anonymous UUID:
BBE9B781-E2B2-6063-20AA-75CAA4074303
Crashed Thread:
0 Dispatch queue:
com.apple.main-thread
Exception Type:
EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Application Specific Information:
objc_msgSend() selector name: respondsToSelector:
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0
libobjc.A.dylib                 0x00007fff892e5097 objc_msgSend + 23
1
com.apple.proapps.MIO           0x000000010c9eef71 -[MIOOutputCore outputDroppedFrames:] + 97
2
com.apple.proapps.MIO           0x000000010c9cdf25 -[MIOOutputDevice
setCMIODroppedFrames:] + 213
3
com.apple.proapps.MIO           0x000000010c9cc8f9
outputBufferUnderrunCountListenerProc(unsigned int, unsigned int,
CMIOObjectPropertyAddress const*, void*) + 89
4
com.apple.CoreMediaIO.FCPX.Lion 0x00000001102552b3
CMIO::DAL::PropertyListener_Call_Helper(int, void*, void*, unsigned int,
unsigned int, CMIOObjectPropertyAddress const*) + 123
5
com.apple.CoreMediaIO.FCPX.Lion 0x00000001102550b5
CMIO::DAL::PropertyListener::Call(unsigned int, unsigned int,
CMIOObjectPropertyAddress const*) + 601
6
com.apple.CoreMediaIO.FCPX.Lion 0x000000011025086b
CMIO::DAL::Object::PropertiesChanged(unsigned int, CMIOObjectPropertyAddress
const*) + 501
7
com.apple.CoreMediaIO.FCPX.Lion 0x0000000110256efc
CMIO::DAL::System::CMIOObjectPropertiesChanged(CMIOHardwarePlugInInterface**,
unsigned int, unsigned int, CMIOObjectPropertyAddress const*) + 236
8
com.apple.cmio.DAL.AJA          0x0000000139c4ca6b
CMIO::DP::Object::PropertiesChanged(unsigned int, CMIOObjectPropertyAddress
const*) const + 93
9
com.apple.cmio.DAL.AJA          0x0000000139c59825
CMIO::DP::Property::OutputBuffers::BumpUnderrunCount(bool) + 65
10
com.apple.cmio.DAL.AJA          0x0000000139c5f2c8
CMIO::DP::AJA::Stream::UpdatePropertyState(CMIO::PropertyAddress const&,
bool) + 1056
11
com.apple.cmio.DAL.AJA          0x0000000139c5b226
CMIO::DP::AJA::Device::UpdatePropertyStates() + 752
12
com.apple.cmio.DAL.AJA          0x0000000139c59b13
CMIO::DP::AJA::Device::Event(__CFMachPort*, mach_msg_header_t*, long,
CMIO::DP::AJA::Device&) + 81
13
com.apple.CoreFoundation        0x00007fff8b0c89c4 __CFMachPortPerform + 388
14
com.apple.CoreFoundation        0x00007fff8b0c8829
__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 41
15
com.apple.CoreFoundation        0x00007fff8b0c879e __CFRunLoopDoSource1 + 478
16 com.apple.CoreFoundation        0x00007fff8b0b97d6
__CFRunLoopRun + 1830
17
com.apple.CoreFoundation        0x00007fff8b0b8e75 CFRunLoopRunSpecific + 309
18
com.apple.HIToolbox             0x00007fff92ebda0d RunCurrentEventLoopInMode +
226
19
com.apple.HIToolbox             0x00007fff92ebd685 ReceiveNextEventCommon +
173
20
com.apple.HIToolbox             0x00007fff92ebd5bc
_BlockUntilNextEventMatchingListInModeWithFilter + 65
21
com.apple.AppKit                0x00007fff8bea424e _DPSNextEvent + 1434
22
com.apple.AppKit                0x00007fff8bea389b -[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
23
com.apple.TLKEventDispatcher    0x000000010e808668 -[TLKEventDispatcher
_startTrackingLoop] + 399
24
com.apple.TLKEventDispatcher    0x000000010e8097a6 -[TLKEventDispatcher
_evaluateEventDescription:withEventContext:] + 492
25
com.apple.TLKEventDispatcher    0x000000010e8091b0 -[TLKEventDispatcher
dispatchEvent:] + 335
26
com.apple.TLKEventDispatcher    0x000000010e806c76 -[TLKEventDispatcher
mouseDown:] + 156
27
com.apple.AppKit                0x00007fff8c0a4aea forwardMethod + 122
28
com.apple.AppKit                0x00007fff8c0a8a58 -[NSWindow sendEvent:] +
11296
29
com.apple.prokit                0x000000010ac119a4 -[NSProWindow sendEvent:] +
236
30
com.apple.AppKit                0x00007fff8c0475d4 -[NSApplication sendEvent:]
+ 2021
31
com.apple.prokit                0x000000010abefd29 -[NSProApplication
sendEvent:] + 129
32
com.apple.Flexo                 0x000000010b1c1404 -[FFApplication sendEvent:]
+ 548
33
com.apple.AppKit                0x00007fff8be979f9 -[NSApplication run] + 646
34
com.apple.prokit                0x000000010abf05d5 NSProApplicationMain + 333
35
com.apple.FinalCut              0x000000010a8a508b main + 1355
36
libdyld.dylib                   0x00007fff89cf15fd start + 1
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0
libsystem_kernel.dylib          0x00007fff91d77662 kevent64 + 10
1
libdispatch.dylib               0x00007fff91d9b421 _dispatch_mgr_invoke + 239
2
libdispatch.dylib               0x00007fff91d9b136 _dispatch_mgr_thread + 52
Thread 2:: com.apple.ProGL.object-deletion
0
libsystem_kernel.dylib          0x00007fff91d76716 __psynch_cvwait + 10
1
libsystem_pthread.dylib         0x00007fff93e20c3b
_pthread_cond_wait + 727
2
com.apple.progl.framework       0x000000010cefa490 (anonymous
namespace)::threadFunc(void*) + 71
3
com.apple.procore.framework     0x000000010aa1f03f PCThread::startup(void*) +
29
4
libsystem_pthread.dylib         0x00007fff93e1e899 _pthread_body + 138
5
libsystem_pthread.dylib         0x00007fff93e1e72a _pthread_start + 137
6
libsystem_pthread.dylib         0x00007fff93e22fc9 thread_start + 13
Thread 3:: MIO Mounting Thread
0   libsystem_kernel.dylib          0x00007fff91d76716
__psynch_cvwait + 10
1
libsystem_pthread.dylib         0x00007fff93e20c77 _pthread_cond_wait + 787
2
com.apple.Foundation            0x00007fff8d702fc0 -[NSCondition
waitUntilDate:] + 344
3   com.apple.Foundation            0x00007fff8d6f9e68
-[NSConditionLock lockWhenCondition:beforeDate:] + 232
4
com.apple.proapps.MIO           0x000000010c9d2dcd -[PluginLockPair scanPaths]
+ 189
5
com.apple.Foundation            0x00007fff8d731dfb __NSThread__main__ + 1318
6
libsystem_pthread.dylib         0x00007fff93e1e899 _pthread_body + 138
7
libsystem_pthread.dylib         0x00007fff93e1e72a _pthread_start + 137
8
libsystem_pthread.dylib         0x00007fff93e22fc9 thread_start + 13
Thread 4:: MIO Mounting Thread
0
libsystem_kernel.dylib          0x00007fff91d76716 __psynch_cvwait + 10
1
libsystem_pthread.dylib         0x00007fff93e20c77 _pthread_cond_wait + 787
2
com.apple.Foundation            0x00007fff8d702fc0 -[NSCondition
waitUntilDate:] + 344
3   com.apple.Foundation            0x00007fff8d6f9e68
-[NSConditionLock lockWhenCondition:beforeDate:] + 232
4
com.apple.proapps.MIO           0x000000010c9d2dcd -[PluginLockPair scanPaths]
+ 189
5
com.apple.Foundation            0x00007fff8d731dfb __NSThread__main__ + 1318
6
libsystem_pthread.dylib         0x00007fff93e1e899 _pthread_body + 138
7
libsystem_pthread.dylib         0x00007fff93e1e72a _pthread_start + 137
8
libsystem_pthread.dylib         0x00007fff93e22fc9 thread_start + 13
Thread 5:: MIO Mounting Thread
0
libsystem_kernel.dylib          0x00007fff91d76716 __psynch_cvwait + 10
1
libsystem_pthread.dylib         0x00007fff93e20c77 _pthread_cond_wait + 787
2
com.apple.Foundation            0x00007fff8d702fc0 -[NSCondition
waitUntilDate:] + 344
3
com.apple.Foundation            0x00007fff8d6f9e68 -[NSConditionLock
lockWhenCondition:beforeDate:] + 232
4
com.apple.proapps.MIO           0x000000010c9d2dcd -[PluginLockPair scanPaths]
+ 189
5
com.apple.Foundation            0x00007fff8d731dfb __NSThread__main__ + 1318
6
libsystem_pthread.dylib         0x00007fff93e1e899 _pthread_body + 138
7
libsystem_pthread.dylib         0x00007fff93e1e72a _pthread_start + 137
8
libsystem_pthread.dylib         0x00007fff93e22fc9 thread_start + 13
Thread 6:: MIO Mounting Thread
0
libsystem_kernel.dylib          0x00007fff91d76716 __psynch_cvwait + 10
1
libsystem_pthread.dylib         0x00007fff93e20c77 _pthread_cond_wait + 787
2
com.apple.Foundation            0x00007fff8d702fc0 -[NSCondition
waitUntilDate:] + 344
3
com.apple.Foundation            0x00007fff8d6f9e68 -[NSConditionLock
lockWhenCondition:beforeDate:] + 232
4
com.apple.proapps.MIO           0x000000010c9d2dcd -[PluginLockPair scanPaths]
+ 189
5
com.apple.Foundation            0x00007fff8d731dfb __NSThread__main__ + 1318
6
libsystem_pthread.dylib         0x00007fff93e1e899 _pthread_body + 138
7
libsystem_pthread.dylib         0x00007fff93e1e72a _pthread_start + 137
8
libsystem_pthread.dylib         0x00007fff93e22fc9 thread_start + 13
Thread 7:: MIO Mounting Thread
0
libsystem_kernel.dylib          0x00007fff91d76716 __psynch_cvwait + 10
1
libsystem_pthread.dylib         0x00007fff93e20c77 _pthread_cond_wait + 787
2
com.apple.Foundation            0x00007fff8d702fc0 -[NSCondition waitUntilDate:]
+ 344
3
com.apple.Foundation            0x00007fff8d6f9e68 -[NSConditionLock
lockWhenCondition:beforeDate:] + 232
4
com.apple.proapps.MIO           0x000000010c9d2dcd -[PluginLockPair scanPaths]
+ 189
5
com.apple.Foundation            0x00007fff8d731dfb __NSThread__main__ + 1318
6
libsystem_pthread.dylib         0x00007fff93e1e899 _pthread_body + 138
7
libsystem_pthread.dylib         0x00007fff93e1e72a _pthread_start + 137
8
libsystem_pthread.dylib         0x00007fff93e22fc9 thread_start + 13
Thread 8:: com.apple.dvdplayback-DDPTask
0
libsystem_kernel.dylib          0x00007fff91d72a56 semaphore_wait_trap + 10
1
com.apple.AVCHDPlugin           0x0000000132ebf787
semaphore_wait(viona_semaphore_t*) + 39
2
com.apple.AVCHDPlugin           0x0000000132ecafba
WinPortServer::ProcessMessages() + 90
3
com.apple.AVCHDPlugin           0x0000000132e7b3d8 0x132e19000 + 402392
4
com.apple.AVCHDPlugin           0x0000000132ebfd52
ST20Thread::Run(PThreadRunParams*) + 34
5
libsystem_pthread.dylib         0x00007fff93e1e899 _pthread_body + 138
Thread 9:: com.apple.helium-texture-finish
0
libsystem_kernel.dylib          0x00007fff91d76716 __psynch_cvwait + 10
1
libsystem_pthread.dylib         0x00007fff93e20c3b _pthread_cond_wait + 727
2
com.apple.Helium.HeliumRender   0x000000010e8f0497
textureFinishThread(void*) + 183
3
libsystem_pthread.dylib         0x00007fff93e1e899 _pthread_body + 138
4
libsystem_pthread.dylib         0x00007fff93e1e72a _pthread_start + 137
5
libsystem_pthread.dylib         0x00007fff93e22fc9 thread_start + 13
Thread 10:: com.apple.helium.rq.gpu-ru0.vs0
0
libsystem_kernel.dylib          0x00007fff91d76716 __psynch_cvwait + 10
1
libsystem_pthread.dylib         0x00007fff93e20c3b _pthread_cond_wait + 727
2
com.apple.Helium.HeliumRender   0x000000010e96362e
HGSynchronizable::Wait() + 46
3
com.apple.Helium.HeliumRender   0x000000010e86b1b2
HGRenderQueue::GetRenderJob(HGRenderExecUnit*, HGRenderJob**) + 498
4
com.apple.Helium.HeliumRender   0x000000010e859857
HGRenderExecUnit::RunLoop() + 183
5
com.apple.Helium.HeliumRender   0x000000010e859794
StartRenderExecUnitFunc(void*) + 20
6
libsystem_pthread.dylib         0x00007fff93e1e899 _pthread_body + 138
7
libsystem_pthread.dylib         0x00007fff93e1e72a _pthread_start + 137
8   libsystem_pthread.dylib         0x00007fff93e22fc9
thread_start + 13
Thread 11:: com.apple.helium.rq.gpu-ru1.vs0
0
libsystem_kernel.dylib          0x00007fff91d76716 __psynch_cvwait + 10
1
libsystem_pthread.dylib         0x00007fff93e20c3b _pthread_cond_wait + 727
2
com.apple.Helium.HeliumRender   0x000000010e96362e
HGSynchronizable::Wait() + 46
3
com.apple.Helium.HeliumRender   0x000000010e86b1b2
HGRenderQueue::GetRenderJob(HGRenderExecUnit*, HGRenderJob**) + 498
4
com.apple.Helium.HeliumRender   0x000000010e859857
HGRenderExecUnit::RunLoop() + 183
5
com.apple.Helium.HeliumRender   0x000000010e859794
StartRenderExecUnitFunc(void*) + 20
6
libsystem_pthread.dylib         0x00007fff93e1e899 _pthread_body + 138
7
libsystem_pthread.dylib         0x00007fff93e1e72a _pthread_start + 137
8
libsystem_pthread.dylib         0x00007fff93e22fc9 thread_start + 13
Thread 12:: com.apple.helium.rq.gpu-cu2.vs0
0
libsystem_kernel.dylib          0x00007fff91d76716 __psynch_cvwait + 10
1
libsystem_pthread.dylib         0x00007fff93e20c3b _pthread_cond_wait + 727
2
com.apple.Helium.HeliumRender   0x000000010e96362e
HGSynchronizable::Wait() + 46
3
com.apple.Helium.HeliumRender   0x000000010e86b1b2
HGRenderQueue::GetRenderJob(HGRenderExecUnit*, HGRenderJob**) + 498
4
com.apple.Helium.HeliumRender   0x000000010e859857
HGRenderExecUnit::RunLoop() + 183
5
com.apple.Helium.HeliumRender   0x000000010e859794
StartRenderExecUnitFunc(void*) + 20
6   libsystem_pthread.dylib         0x00007fff93e1e899
_pthread_body + 138
7
libsystem_pthread.dylib         0x00007fff93e1e72a _pthread_start + 137
8
libsystem_pthread.dylib         0x00007fff93e22fc9 thread_start + 13
Thread 13:: com.apple.helium.rq.pbo-rbu0.vs0
0   libsystem_kernel.dylib          0x00007fff91d76716
__psynch_cvwait + 10
1
libsystem_pthread.dylib         0x00007fff93e20c3b _pthread_cond_wait + 727
2
com.apple.Helium.HeliumRender   0x000000010e96362e
HGSynchronizable::Wait() + 46
3
com.apple.Helium.HeliumRender   0x000000010e86dab7
HGRenderQueue::GetPBOReadbackJob(HGPBOReadbackExecUnit*, HGPBOReadbackJob**) +
87
4
com.apple.Helium.HeliumRender   0x000000010e857f3f
StartPBOExecUnitFunc(void*) + 143
5
libsystem_pthread.dylib         0x00007fff93e1e899 _pthread_body + 138
6
libsystem_pthread.dylib         0x00007fff93e1e72a _pthread_start + 137
7
libsystem_pthread.dylib         0x00007fff93e22fc9 thread_start + 13
Thread 14:: com.apple.helium.rq.pbo-rbu1.vs0
0
libsystem_kernel.dylib          0x00007fff91d76716 __psynch_cvwait + 10
1
libsystem_pthread.dylib         0x00007fff93e20c3b _pthread_cond_wait + 727
2
com.apple.Helium.HeliumRender   0x000000010e96362e
HGSynchronizable::Wait() + 46
3   com.apple.Helium.HeliumRender
0x000000010e86dab7
HGRenderQueue::GetPBOReadbackJob(HGPBOReadbackExecUnit*, HGPBOReadbackJob**) +
87
4
com.apple.Helium.HeliumRender   0x000000010e857f3f
StartPBOExecUnitFunc(void*) + 143
5
libsystem_pthread.dylib         0x00007fff93e1e899 _pthread_body + 138
6
libsystem_pthread.dylib         0x00007fff93e1e72a _pthread_start + 137
7
libsystem_pthread.dylib         0x00007fff93e22fc9 thread_start + 13
Thread 15:: com.apple.helium.rq.pbo-rbu2.vs0
0
libsystem_kernel.dylib          0x00007fff91d76716 __psynch_cvwait + 10
1
libsystem_pthread.dylib         0x00007fff93e20c3b _pthread_cond_wait + 727
2
com.apple.Helium.HeliumRender   0x000000010e96362e
HGSynchronizable::Wait() + 46
3
com.apple.Helium.HeliumRender   0x000000010e86dab7
HGRenderQueue::GetPBOReadbackJob(HGPBOReadbackExecUnit*, HGPBOReadbackJob**) +
87
4
com.apple.Helium.HeliumRender   0x000000010e857f3f
StartPBOExecUnitFunc(void*) + 143
5
libsystem_pthread.dylib         0x00007fff93e1e899 _pthread_body + 138
6   libsystem_pthread.dylib         0x00007fff93e1e72a
_pthread_start + 137
7
libsystem_pthread.dylib         0x00007fff93e22fc9 thread_start + 13
Thread 16:: com.apple.helium-texture-finish
0
libsystem_kernel.dylib          0x00007fff91d76716 __psynch_cvwait + 10
1   libsystem_pthread.dylib         0x00007fff93e20c3b
_pthread_cond_wait + 727
2
com.apple.Helium.HeliumRender   0x000000010e8f0497
textureFinishThread(void*) + 183
3
libsystem_pthread.dylib         0x00007fff93e1e899 _pthread_body + 138
4
libsystem_pthread.dylib         0x00007fff93e1e72a _pthread_start + 137
5
libsystem_pthread.dylib         0x00007fff93e22fc9 thread_start + 13
Thread 17:: com.apple.helium.rq.gpu-ru3.vs1
0
libsystem_kernel.dylib          0x00007fff91d76716 __psynch_cvwait + 10
1
libsystem_pthread.dylib         0x00007fff93e20c3b _pthread_cond_wait + 727
2
com.apple.Helium.HeliumRender   0x000000010e96362e
HGSynchronizable::Wait() + 46
3
com.apple.Helium.HeliumRender   0x000000010e86b1b2
HGRenderQueue::GetRenderJob(HGRenderExecUnit*, HGRenderJob**) + 498
4
com.apple.Helium.HeliumRender   0x000000010e859857
HGRenderExecUnit::RunLoop() + 183
5
com.apple.Helium.HeliumRender   0x000000010e859794
StartRenderExecUnitFunc(void*) + 20
6
libsystem_pthread.dylib         0x00007fff93e1e899 _pthread_body + 138
7
libsystem_pthread.dylib         0x00007fff93e1e72a _pthread_start + 137
8
libsystem_pthread.dylib         0x00007fff93e22fc9 thread_start + 13
Thread 18:: com.apple.helium.rq.gpu-ru4.vs1
0
libsystem_kernel.dylib          0x00007fff91d76716 __psynch_cvwait + 10
1
libsystem_pthread.dylib         0x00007fff93e20c3b _pthread_cond_wait + 727
2
com.apple.Helium.HeliumRender   0x000000010e96362e
HGSynchronizable::Wait() + 46
3
com.apple.Helium.HeliumRender   0x000000010e86b1b2
HGRenderQueue::GetRenderJob(HGRenderExecUnit*, HGRenderJob**) + 498
4
com.apple.Helium.HeliumRender   0x000000010e859857
HGRenderExecUnit::RunLoop() + 183
5
com.apple.Helium.HeliumRender   0x000000010e859794
StartRenderExecUnitFunc(void*) + 20
6   libsystem_pthread.dylib         0x00007fff93e1e899
_pthread_body + 138
7
libsystem_pthread.dylib         0x00007fff93e1e72a _pthread_start + 137
8
libsystem_pthread.dylib         0x00007fff93e22fc9 thread_start + 13
Thread 19:: com.apple.helium.rq.gpu-cu5.vs1
0   libsystem_kernel.dylib          0x00007fff91d76716
__psynch_cvwait + 10
1
libsystem_pthread.dylib         0x00007fff93e20c3b _pthread_cond_wait + 727
2
com.apple.Helium.HeliumRender   0x000000010e96362e
HGSynchronizable::Wait() + 46
3
com.apple.Helium.HeliumRender   0x000000010e86b1b2
HGRenderQueue::GetRenderJob(HGRenderExecUnit*, HGRenderJob**) + 498
4
com.apple.Helium.HeliumRender   0x000000010e859857
HGRenderExecUnit::RunLoop() + 183
5
com.apple.Helium.HeliumRender   0x000000010e859794
StartRenderExecUnitFunc(void*) + 20
6
libsystem_pthread.dylib         0x00007fff93e1e899 _pthread_body + 138
7
libsystem_pthread.dylib         0x00007fff93e1e72a _pthread_start + 137
8   libsystem_pthread.dylib         0x00007fff93e22fc9
thread_start + 13
Thread 20:: com.apple.helium.rq.pbo-rbu3.vs1
0
libsystem_kernel.dylib          0x00007fff91d76716 __psynch_cvwait + 10
1
libsystem_pthread.dylib         0x00007fff93e20c3b _pthread_cond_wait + 727
2
com.apple.Helium.HeliumRender   0x000000010e96362e
HGSynchronizable::Wait() + 46
3
com.apple.Helium.HeliumRender   0x000000010e86dab7
HGRenderQueue::GetPBOReadbackJob(HGPBOReadbackExecUnit*, HGPBOReadbackJob**) +
87
4
com.apple.Helium.HeliumRender   0x000000010e857f3f
StartPBOExecUnitFunc(void*) + 143
5
libsystem_pthread.dylib         0x00007fff93e1e899 _pthread_body + 138
6
libsystem_pthread.dylib         0x00007fff93e1e72a _pthread_start + 137
7
libsystem_pthread.dylib         0x00007fff93e22fc9 thread_start + 13
Thread 21:: com.apple.helium.rq.pbo-rbu4.vs1
0
libsystem_kernel.dylib          0x00007fff91d76716 __psynch_cvwait + 10
1
libsystem_pthread.dylib         0x00007fff93e20c3b _pthread_cond_wait + 727
2
com.apple.Helium.HeliumRender   0x000000010e96362e
HGSynchronizable::Wait() + 46
3
com.apple.Helium.HeliumRender   0x000000010e86dab7
HGRenderQueue::GetPBOReadbackJob(HGPBOReadbackExecUnit*, HGPBOReadbackJob**) +
87
4
com.apple.Helium.HeliumRender   0x000000010e857f3f
StartPBOExecUnitFunc(void*) + 143
5
libsystem_pthread.dylib         0x00007fff93e1e899 _pthread_body + 138
6
libsystem_pthread.dylib         0x00007fff93e1e72a _pthread_start + 137
7
libsystem_pthread.dylib         0x00007fff93e22fc9 thread_start + 13
Thread 22:: com.apple.helium.rq.pbo-rbu5.vs1
0
libsystem_kernel.dylib          0x00007fff91d76716 __psynch_cvwait + 10
1
libsystem_pthread.dylib         0x00007fff93e20c3b _pthread_cond_wait + 727
2
com.apple.Helium.HeliumRender   0x000000010e96362e
HGSynchronizable::Wait() + 46
3
com.apple.Helium.HeliumRender   0x000000010e86dab7
HGRenderQueue::GetPBOReadbackJob(HGPBOReadbackExecUnit*, HGPBOReadbackJob**) +
87
4
com.apple.Helium.HeliumRender   0x000000010e857f3f
StartPBOExecUnitFunc(void*) + 143
5
libsystem_pthread.dylib         0x00007fff93e1e899 _pthread_body + 138
6
libsystem_pthread.dylib         0x00007fff93e1e72a _pthread_start + 137
7
libsystem_pthread.dylib         0x00007fff93e22fc9 thread_start + 13
Thread 23:: com.apple.coremedia.scheduledfileio
0
libsystem_kernel.dylib          0x00007fff91d76716 __psynch_cvwait + 10
1
libsystem_pthread.dylib         0x00007fff93e20c3b _pthread_cond_wait + 727
2
com.apple.CoreMedia.ProAppsSupport    0x000000010ab7fc37
WaitOnCondition + 11
3
com.apple.CoreMedia.ProAppsSupport    0x000000010ab7fa4b
FigSemaphoreWaitRelative + 133
4
com.apple.CoreMedia.ProAppsSupport    0x000000010ab7ad0e
FigScheduledFileIOThread + 141
5
com.apple.CoreMedia.ProAppsSupport    0x000000010ab8058b
figThreadMain + 382
6
libsystem_pthread.dylib         0x00007fff93e1e899 _pthread_body + 138
7
libsystem_pthread.dylib         0x00007fff93e1e72a _pthread_start + 137
8
libsystem_pthread.dylib         0x00007fff93e22fc9 thread_start + 13
Thread 24:: CVDisplayLink

So a guy goes into his doctors office and tells his doctor "Ya gotta
help me doc...it hurts when I run my head into the door like
this...OW!". Then the doctor says:
"DON'T DO THAT ANY MORE!!!"
(I promise to keep my day job...oops what job...and not go into
comedy..)
Why don't you convert all the old 16 bit code into 32 bit code and
create one application where the various parts all know about each
other? I don't think that there's any way to coordinate an old 16 bit
LV and a new 32 bit LV application so that they don't step on each
other driverwise like they appear to be doing. I don't think that the
two LabVIEW's even know that the other exists!
Alternatively, get a second computer to run the 16 bit code on and
make the two apps communicate with
each other using TCP/IP or serial.
Doug De Clue
[email protected]
cincidude wrote in message news:<[email protected]>...
> I am using 2 versions of Labview at the same time, one is version 4
> which has a camera and a weigh-in-motion scale attached to it. The
> second is either Labview version 4, 16-bit or Labview 3.0.1, 16-bit,
> i'm not sure. The sixteen bit has a data acquisition system attached
> to it. Its an optim electronics system and the 16-bit Labview drivers
> for the optim were provided by Optim electronics and so I am stuck
> with using the same system. When I use both these systems in tandem,
> the system crashes frequently, but both systems run fine
> independently. It usually just freezes up or says "Illegal operation
> performed. Contact program vendor". Its a windows error with a red
> cross.

Red ligne in the timeline

Similar Messages

Maybe you are looking for