[Q] Refreshing/Timing problem 21:9-monitor

Hi fellas!
I'm using a Macbook Pro 15" non-retina (Windwith GT-650Mtogether with my AOC q2963pm 21:9 monitor through HDMI. What I have encountered is what I think is a timing-problem. I cannot find the settings which works perfect.
Either, the screen looks a bit grainy at the max resolution of 2560x1080 with the games working (this with Atomatic timing in NVIDIA settings),
or I have a crispy display, but the games ends with a flimmering and black screen after I quit or Alt+Tab out of a fullscreen-game which causes the NVIDIA-driver to stop responding and restarting (using CVT Reduced Blank).
I had to create a custom resolution in order to use the full 2560x1080 resolution instead of just 1920x1080. I tried to manually create something that should meet the requirements, but with no luck. Either, the display goes black, or I get the same problems as listed above.
Here are the specs of the screen:
Resolution: 2560x1080 @ 60Hz
Scanning Frequency: H: 30-99 KHz / V: 50-76 Hz
Pixel Frequency: 185.58 MHz
Does someone know which settings I should use? The only thing I can think of to fix this is buying a Displayport-cable as "no one" ohters is experiencing this issue. Will this easy solution fix it?

Try the Thunderbolt connection.
<http://store.apple.com/us/product/MD861ZM/A/apple-thunderbolt-cable-20-m>

Similar Messages

Timed 3-state script monitor can't auto resolve the alert

My environment is 2007 R2. I usually create timed 2-state script monitor which works fine. However yesterday I created a timed 3-state script monitor. I did check the option "Automatically resolve the alert when the monitor returns to healthy state".
Then I put it in our DEV to test. The monitor trigger the alert properly. However when the critical situation is gone, the alert didn't resolve itself. Since my script also output the result into event log, so I am pretty sure the "Healthy" state
was returned.
Then I did a test, I created a timed 2-state script monitor. This monitor uses almost exactly the same script as the 3-state one. The only modification is 3-state script will output status as "Critical", "Warning" and "Healthy".
In 2-state script, I just simply changed the "Warning" one to "Critical". Then I put it in the test. When critical situation is detected, both 3-state and 2-state monitor trigger the alert properly. However after the situation changed back
to healthy, only alert generated by 2-state monitor resolved and marked itself as "closed" while the alert generated by 3-state monitor still shown as "New".
I am wondering whether this a bug? Does anyone get the similar issue?

Hi,
As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as "Answered". Either the previous steps should
be helpful for many similar scenarios and will be marked as answer, or this post will be marked as answer in order to close the thread. Feel free to re-open the thread if you have additional information about this specific case or to open a new thread for
a new case. In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.
Thanks,
Yan Li
Regards, Yan Li

Aperture Slideshow Slide timing problem

We are having a problem with Aperture on an iMac. We have several preset slide shows that we use frequently in our office, and just recently, the slide show began to have a weird bug. When the slide show is stopped manually with the space bar, then started again with the space bar, it will play about 6 slides at a much faster rate than our settings. Then it goes back to normal. If we try to compensate for that by going back a few slides, then Aperture plays up to 25 slides at a faster speed, then goes back to the time we put in the preset. This occurs in multiple projects.
We are playing the slides with music, showing the photos for a fixed time, not looping the slides how, crossfade is checked. It does this with a project of 100 images or with a short slide show of 12 images. We have restarted Aperture and the Mac. We are using the latest version of Aperture. I tried making a new preset and it still happened.
This is a really embarrassing problem to have when presenting to our clients. Any ideas? I am seriously considering re-installing the program. Is there a way to repair" the installation so that we don't have to reinstall?
We are running an iMac with OS 10.4.11, 2.33Ghz, 2MB Ram.
Thanks,
Carol E.

Update...
I had tried copying my Aperture library directly to my iMac, as stated above, which did not work. Then, I copied the library to another LaCie HD that I got from Mac Mall, and that worked fine. It turns out that both of these are formatted for the MacOS, but they aren't journaled, so FAT32 is not the problem (journaling maybe or some other issue, but not FAT32).
So last night, I went to the Apple Store with my iMac and two external hard drives in tow.
So I'm in the Apple store with the a Creative guy, who is a very experienced Aperture user and photographer. We operate my iMac attached to my "Aperture Library external drive". The slide show misbehaves as expected. It does the same with the small temporary library I had made, too, on the iMac. So we hook that same HD to one of the STORE Mac Book Pro computers.... and LO and BEHOLD.... *+that computer also had the same issue as mine+*
I said "HA! I broke your computer!" So he reboots the store's Mac Book Pro, which has Deep Freeze on it, and it goes back to the same state it was in before we were using it. He runs a slide show again, same problem with the timing after pausing a slide show.
The conclusion is: The problem with the slide show is an update to Aperture and/or the video card for the iMac and Mac Book Pro, because those two computers use the same video card. Or perhaps some other OS update that affects both of those computers and whatever hardware they have in common. The guy helping me suspects the video card or something related. I went and tried the Mac Pro in the store, and it does not have this issue (same as my Mac Pro at the office). However the Mac Pro did exhibit some strange slide show behavior, as a horizontal (refresh rate problem?) line that travels up the screen during the slide show.
I couldn't say if all the newer iMacs or Mac Book Pro's in the store have this problem. He used one of the laptops that they have at the creative bar for doing classes to test things. But it is possible if you go to an Apple store and use Aperture on their iMac or Mac Book Pro computers, you will see the same thing (pause the slide show and it screws up the timing).
As to the file problem... I don't think there is a problem with the files anymore, since it copied just fine to another external hard drive. I think the problem is with the iMac. I can access the library and I can vault it to another external, and I can copy the library to another external using finder. I just can't get it back on the iMac. I may fiddle with moving the files around some more and see what happens, but I may just have to live with the fact that the library won't move back to the iMac internal drive. We plan to get another Mac Pro in a few months, so perhaps this won't even matter.
Anyway thanks for the help on this issue. Hopefully Apple is listening, or at least listening to an Aperture user that has also found this problem. I will probably post on some more forums, and maybe someone with some influence will check out the problem.
Carol E.

The problem is to monitor two experimental parameters

The problem is to monitor two experimental parameters (pressure and temperature) using USB -6008. These parameters are converted to voltage by proper sensors.
I use the following sequence of commans:
DAQmxBaseCreateTask("T",&taskHandle);
DAQmxBaseCreateAIVoltageChan(taskHandle,"Dev1/ai0","",DAQmx_Val_Diff,-10,10,DAQmx_Val_Volts,NULL);
DAQmxBaseCreateAIVoltageChan(taskHandle,"Dev1/ai1","",DAQmx_Val_Diff,-1,1,DAQmx_Val_Volts,NULL);
DAQmxBaseStartTask(taskHandle);
Then I read the results every 200 msec. To do this I put into the Timer event handler next code:
{ DAQmxBaseReadAnalogF64(taskHandle,1,timeout,0,data,2,&pointsRead,NULL);
data[0] I convert to pressure;
data[1] I convert to temperature;
The program works, but I am not satisfied because of noise. The origin of the noise is electric interference of power network. I know that the best way to reduce electrical interference is to integrate a signal over period of the power network (20 msec in Russia). All high sensitivity digital voltmeters do this integration. The idea is to make, for example, 40 measurements with SampleRate=2000 , ( 0.5 msec * 40 = 20 msec) instead of single measurement. Then calculate the sum of pressure readouts and the sum of temperature readouts. This procedure should be repeated every 200 msec using the Timer event handler.
Therefore I added before DAQmxBaseStartTask(taskHandle);
DAQmxBaseCfgSampClkTiming (taskHandle, source, sampleRate, DAQmx_Val_Rising, DAQmx_Val_FiniteSamps, 40);
and modified Timer event handler:
{ DAQmxBaseReadAnalogF64(taskHandle,40,timeout,0,data,80,&pointsRead,NULL);
data[0] … data[39] I convert to pressure;
data[40] … data[79] I convert to temperature;
Testing of the program showed: the program can make only one cycle of measurement. All times I call the DAQmxBaseReadAnalogF64 the results were the same. It looks like USB-6008 make one cycle of measurement (probably at DAQmxBaseStartTask) and puts the results to the buffer. And the DAQmxBaseReadAnalogF64 just read the buffer but can not initiate new measurements.
How the program can initiate new cycle of measurements? Could anybody to help me?

Dear Micaela,
Thank you for advice. I will change driver to the DAQmx . But it will take time to download 460 M.
Therefore I continued with the old driver.
I changed DAQmxBaseCfgSampClkTiming to DAQmx_Val_ContSamps and immediately faced with another problem. The device began to acquire data continuously, and when I call DAQmxBaseReadAnalogF64 in the timer handler, I got the date that does not correspond to the current time. The data corresponds to the experimental parameters which were 5 minutes ago. I was very surprised until I realized that this huge delay exits!
To fix this problem I tried to add DAQmxBaseStartTask and DAQmxBaseStopTask to the timer handler.
     DAQmxBaseStartTask(taskHandle);
     DAQmxBaseReadAnalogF64(taskHandle,40,timeout,0,data,80,&pointsRead,NULL);
     DAQmxBaseStopTask(taskHandle);
    data[0] … data[39] I convert to pressure;
     data[40] … data[79] I convert to temperature;
The program did not work. Even did not respond to any action.

Problem with two monitors while using Photoshop, windows move from 2nd screen to 1st screen.

Problem with two monitors while using Photoshop, windows move from 2nd screen to 1st screen.
I saved a new workspace and it did not help.
No problem before I went to Maverick.

I found the fix, go to System Preferences and open Mission Control and uncheck the box to keep monitors as they were (When switching to an application...........)

I have a Power MAC G5 dual 2ghz that has a peculiar problem. The monitor will not report until the machine is stopped and started 5 or 6 times. Once booted it will restart without problem if done so from the apple menu. Swapped out all hardware

My Power MAC G5 has a peculiar problem. The monitor fails to report until the machine is started and shut down 5 or 6 times. Once it has booted it can be restarted without incident from the Apple menu. I have swapped out all of the hardware. Monitor, Memmory,Video Card and reset the PRAM. After resetting the PRAM it booted on the first attempt and I thought it was solved. But the next day it was back to starting and stopping until the Monitor came on. Does anyone have a suggestion? Thanks

It could be a bad PRAM battery corrupting your PRAM. Typically when I have monitor issues on startup it is a bad PRAM battery.
Texas Mac Man's PRAM, battery, PMU tutorial - https://sites.google.com/site/macpram/mac-pram-nvram-cuda-pmu-battery-tutorial
Apple's PRAM reset directions - http://docs.info.apple.com/article.html?artnum=2238
If you have a digital multimeter you can check the condition of your present battery. It should read at least 3.2V if it is the 3.6V half-AA battery type. A new battery provides 3.67 Volts DC. A bad battery provides under 3.2 Volts DC. Ideally this should be measured while the battery is under load; added recommendation from Hans777:
>I have recently found out that an exhausted battery will still indicate >3.6 V with a high internal resistance VM.
>
>Checking incircuit: powercord disconnected press PMU reset button for >about 5 sec before measuring.
>
>Checking outside: load the battery with a 1500 Ohm resistor when measuring.
Alternatively, test the battery while it is still in the computer.
If the battery is more than 5 years old, especially if you totally disconnect the computer from the power regularly, or have left it unplugged for several months at one time, it is likely the battery is dead.
Sometimes you have to do a more intensive reset of hardware management:
[Resetting Cuda/PMU on Power Mac G5, Power Mac G4, Power Macintosh G3|http://support.apple.com/kb/HT1939]
[How to reset the SMU on a Power Mac G5 (Late 2004) or Power Mac G5 (Late 2005)|http://support.apple.com/kb/HT1436]
[iMac G5: How to Reset the SMU|http://support.apple.com/kb/HT1767]

Premiere Pro CS4 - Problem with the monitor program.

Hi. I'm not able solving problems with the monitor using PremiereProCS4. When I drag a photo (also only one photo) in the timeline and play it in the monitor program, vision in the monitor program doesn't run:black monitor or a little part of the photo appear... sometimes distort colours. Asus P5QPRO, Intel 9550 and Sparkle Nvidia GeForce 9800 GTX+ 1024 DDR3; last gpu driver and directX are installed. Different configuration of stratch disks were tested. Where am I wrong?

Dear Bill,
thanks for your answer and your article. I tried with your NTSC 4:3 720x480 PAR 0.9 and, "magically", no more problem!!! I used the script pocedure in Photoshop CS4 to resize my images. Now, before starting my workflow and hoping not to overuse your patience, I would like to indicate you my equipment and my target: I use a Canon Eos 7D (generally for still images, 90% are vertical, and just some videos) and I use Premiere Pro CS4 to burn a dvd (normal, 4.7 Gb or double side, more than 8 Gb) with a 16.9 lcd tv (I'm Italian); my camera save as .jpg and .raw (but why use heavy .raw files if I've to redute to 720x480?!??).
So, according to your "everyone wants the highest quality that they can obtain when doing theri videos..." and "your video project may vary, so you will need to plug in the dimensions for YOUR video project in that case", I've a question: which is the best for me?
And then:
1 - Premiere Pro CS4 havn't a batch or a script procedure for still image like PS (only for videos)!?!
2 - Premiere does'nt allow you to import images like 4.181 Kb (a too large dimension file error appears)!
3 - In the timeline of Premiere, after you dragged images, you can select them and right click to perform "resize to frame size": it seems to run good without problem, but what appen to the photo? Which is it's pixel?
4 - In the general preferences of Premiere you can to optimize rendering for "memory" or not: which is the best for you?
5 - I attached file with a screen of something strange in Premiere: dragging an image (the first of the project) in the timeline, the timeline appears distort (you can see the part in the yellow square): then, when I render the project and play in the monitor program, it becames normal.
Thanks!

Insert and then show the result and refresh page problem

hi all,
I collect the form value and put them into db, and then display this student 's inform out from db including the one we just submit, first I do it on this way
insertpayment(UserId, FeeType, DuteDate, OfficerReason, OtherReason, CompleteDate,
                        InterviewDate, ApprovalDate,PaymentYear);
               studentRecords= getFound(UserId);
                 userSession.setAttribute("studentRecords", studentRecords);
                 RequestDispatcher disp;
               // disp = getServletContext().getRequestDispatcher("/WEB-INF/jsp/   studentRecords= getFound(UserId);");
                 disp = getServletContext().getRequestDispatcher("/showPayment");
                disp.forward(req, res); then whenever I refresh my showRecords.jsp" I call the insert function. THAT IS HORRIABLE.
I try to move the studentRecords= getFound(UserId); to my showPayment servlet and then forward the result to showRecords.jsp, but I alwarys get error
PWC4011: Unable to set request character encoding to UTF-8 from context /report, because request parameters have already been read, or ServletRequest.getReader() has already been called
How should I handle this kind of problem??

Karan, thank you for the link, i read a few articles, I only get the sample part part use res.sendRedirect("/myfolder/showPayment"); in my insert servlet and use forward to display the page
userSession.setAttribute("studentRecords", studentRecords);
              RequestDispatcher disp;
              disp = getServletContext().getRequestDispatcher("/WEB-INF/jsp/secure/admin/showRecords.jsp");
               disp.forward(req, res);
this solute the refresh page problem, but bring the new problem I can't use the following way to disable the back button. not the perter solution
maybe I did not understand PRC more advice!!
response.setHeader("Cache-Control","no-cache"); //Forces caches to obtain a new copy of the page from the origin server
response.setHeader("Cache-Control","no-store"); //Directs caches not to store the page under any circumstance
response.setDateHeader("Expires", 0); //Causes the proxy cache to see the page as "stale"
response.setHeader("Pragma","no-cache"); //HTTP 1.0 backward compatibility

Data Services Admin Console "Read Timed Out" via Job Monitor Log Tab.

Hi All,
I am getting the "Read Timed Out" via Job Monitor Log Tab issue, when large ETL jobs are being executed.
Is there a resolution for this issue.
Thank you
Kind regards
Hai.

Hi Manoj,
I have checked the UNIX server and the admin.xml is not located in advised location.
The only two file that are in the advised location are:
- ContentTypes.xml
- PythonAPI.xml
I have another install of data service (default installation) on a windows environment, and I checked the advised location and the file is there.
Is it possible to copy the windows admin.xml to the Unix server.
Thanks
Kind regards
Hai.

Can anyone help me with Labview/GPIB timing problems?

I am trying to use a very simple VI (downloaded from the NI site) to control a Newport 1830C optical power meter.
I have been spending most of my time trying to use the VI issue a command to read the current displayed power. When I run the VI normally, I get no response from the meter, and the VI simply terminates without any error message. (The "remote" indicator does light on the meter, though, so it seems to be receieving the command.)
However, when I run the VI in the "highlight exectution" mode, everything seems to work just fine, and I receive a correct reading from the meter! Needles to say, this makes it really hard to debug the problem.
My guess is that I have some kind of timing problem, and t
he "highlight execution" feature fixes it by introducing delays. Is this correct? If so, how can I achieve the same thing by putting in delays by hand?
thanks, Whitney White

Whitney,
I agree that this is very likely to be a timing issue. VIs run much slower in highlight execution mode, therefore your instrument may need more time to prepare the data you have requested. Try wiring a delay inline prior to the GPIB reads and/or writes, or try using Service Requests (SRQs) to give the instrument enough time to generate the data it needs to send back to the computer.
Another possibility is that your instrument may not be IEEE 488 compliant. Some older instruments indicate that they are ready to receive data before they really are. Try changing the GPIB bus timing to the slowest setting (in the GPIB Configuration Utility). This only affects the time that the GPIB controller waits before valid data is on the bus and the DAV line i
s asserted (a step in the GPIB handshaking that occurs each time a byte of information is sent to the device) so this may not be effective.
Lastly, you may wish to try the instrument driver for your instrument. There is a contributed driver at this location: LabVIEW Traditional Instrument Driver: Newport Optical Power Meter 1830C. A 'contributed driver' means that someone outside of National Instruments wrote the driver and then submitted it for posting. This driver also contains a good example of adding a time out.
Regards,
Heather S.
Applications Engineer
National Instruments

Is someone with iMac 2010 users have problems with the monitor. I mean horizontal stripes and dark screen ?

Is someone with iMac 2010 users have problems with the monitor. I mean horizontal stripes and dark screen ?

Mine's a late '09, but there have been display issues with iMacs.
Contact Apple Service, iMac Service or Apple's Express Lane. Do note that if you have AppleCare's protection plan and you're within 50 miles (80 KM) of an Apple repair station, you're eligible for onsite repair since yours is a desktop machine.

I hit the wrong monitor refresh rate and now lost monitor picture. How can I get back to the right refresh rate with no pic to view?

I hit the wrong monitor refresh rate and now lost monitor picture. How can I get back to the right refresh rate with no pic to view?

Try this:
Mac OS X 10.6 Help: If you changed your display’s resolution and now it doesn’t display a picture

My new macbook air and new thunderbolt monitor will not work together. the keyboard will not engage and the monitor screen keeps going black. is it a problem with the monitor, connection, laptop?

my new macbook air and new thunderbolt monitor will not work together. the keyboard will not engage and the monitor screen keeps going black. is it a problem with the monitor, connection, laptop?

A new Mac comes with 90 days of free tech support from AppleCare.
AppleCare: 1-800-275-2273
Call AppleCare. They will help you.
Best.

Timing problems with AU Ivory Piano + ESB and Logic 7.2

I have problems with Ivory and Logic 7.2:
The Ivory (AU version 1.50) plays well in tempo, but when I want to bounce (export track as audio file) the Ivory plays totally out of tempo.
Even when I touch the record button on audio tracks or when I want to record my mix on 2 audiotracks, the Ivory plays out of tempo.
Even freezing the Ivory track gives the same problem.
Then I need to go back to my last saved version.
The same actions with Emagic, Native Instruments and Spectrasonics AU plugins, and everything works fine.
I throwed away already the Ivory prefs, no positive results.
My Ivory sample files are on a separate 400 GB internal disk, and my Audio I'm recording on a external Glyph disk.
I think I have this problem since I've upgraded from Logic 7.1.1 to 7.2 but I'm not sure. I didn't worked long with Logic 7.1.1.
I don't work in Protools, but I use the DAE and Direct TDM (no Core Audio)
It happens in the most simple application: no DAE or AU plug-ins, only one Ivory AU plug-in.
This is my configuration:
Ivory AU (Audio object-Direct TDM-Instr) output ESB 1-2 -> input ESB1 2 (Audio Object-DAE) -> Output 1-2 of my digidesign interfaces
Ivory becomes totally unusable for me this way. Is someone having the same problems?
Suggestions?
Wim Claes
Setup
Logic 7.2
Protools 7.1cs4
192, 2x96i, 1x 96 interface
G5 dual 2,7 Mac OS X (10.4.3) 4 GB RAM

I tried already a lot of things, but it is very clear:
1. Instantiating Ivory as AU- Ivory plays in tempo
2. Record enable an audio track in the arrange window - Ivory plays out of tempo
This happens with the default song of logic, no other plugins or AU-instruments are instanciated.
I can not find a way to convert my Ivory-midi to audio without the timing problems;
Bouncing, freezing, record to audio, export as audio file: all those things result in timing problems.
I tried this all with emagic plugins (ES2...) and Native Instruments plugins and then I don't have the tempo problem

Potential problem with my monitor, please help.

Hello
I recently upgraded my OSX to Mavericks and I've been having problems with my monitor, I've attached a screenshot of what is happening because I didn't know how to explain it and I'm unsure if its the OSX upgrade causing the issue or not, however I'm really worried about my monitor on my macbook pro.
The model I have is the 15" mid 2010 2.4Ghz Intel core i5 with 4GB RAM.

Still having this issue with my macbook pro monitor... There was no updates available and I followed every other possible solution, sometimes my monotor looks perfect like there was never any problem and other times my entire screen is just covered with this stuff you've seen in the above image.
I really have no idea what the exact issue is and how to solve it.
This macbook was given to me for university by the government as I have a form of dyslexia and because I've just finished my degree the insurance has ended... is there anyway I can still buy applecare insurance for my machine?! I got this MBP in 2010 so I've had it for three years now.
I'm just worried that one day I'll turn on my machine and the monitor won't work whatsoever.. and I thought apple was suppossed to be good and last a long time.
Hope somebody can help me further.
Thanks.

[Q] Refreshing/Timing problem 21:9-monitor

Similar Messages

Maybe you are looking for