Premiere choppy playback after update

Greetings,
I'm having a rather bizarre issue which has just came about recently.
I've been running PPro CC successfully for six months without issue. After the most recent update to 7.2.2 I'm having choppy playback both in the source and program monitors. I'm editing mostly AVCHD from a Panasonic HMC80 camera. The choppy playback occurs regardless of resolution or frame rate. I even tried a standard DV file and that too is playing back not smooth. Changing the playback resolution to 1/2, 1/4 etc.. makes no difference.  Changing from Mercury software to hardware makes no difference. I tried creating a new project as well as clearing cache files, previews, etc.. and still have the problem. As a last effort, I re-installed my OS, and re-installed Creative Cloud and Premiere. The issue is still present. My hardware cannot be the issue as I've been editing successfully before. Nothing has changed except for the Premiere update. I've read elsewhere that others are experiencing the same issue. Any thoughts?
Windows 7 Home
Premiere Pro CC 7.2.2
i7 [email protected]
8GB RAM
NVIDIA GT 425M

Im having the same problem. Didnt show up until after the 7.2 update.
Major lag on one specific spot in the timeline, and muting all tracks makes no difference on the lag.
I cleaned my project file, caches, downgraded playback resolution, tried the mercury playback function. Nothing. Now the choppiness seems to bleed into the rest of the project until it is all so slow and unplayable. I'm having a harder time finishing this project as time goes on.
almost same specs
windows 7 home
Premiere CC Pro 7.2.2
Intel i7 2670QM
Nvidia gt 630m 1gb vram
8gb ram

Similar Messages

  • Premiere pro CC drop playback after update 7.2.1

    Why premiere pro cc drop playback after update 7.2.1? I have a MacBook Pro late 2011 with ATI Radeon HD6770m 1GB. Premiere pro cc 7.1.0 run normal, ok, without crashing and drop-freeze frame, but after update 7.2.1 i have all this problems.

    Just came on here to post about the buzzing transitions, glad to see it's been fixed already!
    Another thing though I don't see mentioned, since moving to 7.2 I find audio playblack is out of sync while editing, and in some clips significantly more noticeably than others. This only happens during playback, if I pause and scrub manually, the audio is perfectly in sync. This actually messed up a  project for a client. I thought the audio off the camera was  out of sync in one segment so I bumped it a few frames before exporting. Didn't check it after of course and sent him the file, then got a reply back that it was out of sync in that spot. Check the exported video and sure enough, he was right. Check it again in project but it looks in sync. So I bump the audio back in the timeline so that it LOOKS out of sync again during playback, but the new exported video is perfectly in sync!
    Editing a TV show now with hundreds of clips and it's maddening with some looking fine, some looking a little off, and some looking completely off and having to manually scrub to check and be sure along the way.
    Hopefully this is also fixed in this update..will see tomorrow.

  • Choppy playback after upgrading hardware

    I've recently upgraded from a phenom 965 and 7gb 1333 gb ram, to an i5-2500k with 16gb 1600mhz. Otherwise everything is the same, i just reinstalled windows and premiere pro after the upgrade. After the upgrade this error, or annoyance, occured. Here's all the specifics:
    -Premiere pro CS5.5.2 v/latest updates
    -Windows 7 pro (fresh install v/important updates)
    -h.264 in mp4-container
    -no error messages
    -very choppy playback after "jogging". When theres a lot of movement, the picture becomes very "stuttery" and "pixelated" in that area.
    -no extra codecs or similar is installed.
    - hardware:
       -nvidia gtx 560 v/latest drivers
      -i5 2500k @ 4,6Ghz
      -16Gb 1600mhz xmp ram
      -7200rpm 500gb source hdd
      -5200rpm 120gb scratch disk
      -Agility 120gb ssd OS and programs
    I have tried using 1/4 playback, using ssd as scratch disk, installing and uninstalling extra codecs but none of it made any difference. The cpu or ram never exceeds 50% capacity when the problems occur. 

    But wouldnt the cpu reach 100% capacity before it starts being the bottleneck?
    Only if all the other components supply data fast enough that the CPU can run flat out. If the CPU has to wait for other components to catch up, CPU load will be less than 100%.
    If you race alone on a track and there are no other contestants (components) in the race, you can go flat out at 100% of the speed, but if the track is filled with many other contestants (components) from a local old-age house, your speed will drop significantly.

  • Premiere crashes constantly after update to CUDA Driver Version: 7.0.35

    I have had troubles with the dreaded garbled screen bug, it occurs after working with premiere for more than an hour or working with 4K material or large graphic files.
    But since updating to CUDA Driver Version: 7.0.35 premiere crashes immediately after starting the same project that worked  the previous day. Only switching to open CL stops premiere from crashing.
    Please advise!
    yosemite 10.10.2 (14C1514)
    Identifier:            com.adobe.AdobePremierePro
    Version:               8.2.0 (8.2.0)
    Code Type:             X86-64 (Native)
    Parent Process:        ??? [1]
    Responsible:           Adobe Premiere Pro CC 2014 [544]
    NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB
    MacBookPro9,1, BootROM MBP91.00D3.B08, 4 processors, Intel Core i7, 2.6 GHz, 8 GB, SMC 2.1f175

    I moved from Version 5.. to  7.0.36 and the crashes started.  Also strange pixelating on some screens.  Is there a way to go backwards on the drivers or do I use Open CL until CUDA or Adobe or Apple comes up with a fix?

  • Choppy scrolling after updating to iOS 4? (Device: iPhone 3GS)

    Is anyone else experiencing a little slugginess in scrolling speed after updating to iOS 4 on the 3GS? The worst choppiness happens at the homescreen when scrolling through pages; the pages seem to "stick" a little bit occasionally, like they're running through a sticky surface.

    Even this is a minor issue it's really annoying and makes the phone feel very flimsy, cheap and slow. I hope Apple will do something about it in the next update.

  • Choppy playback after burning data dvd in toast

    Hi Ive just finished burning a copy of various short clips which I exported as a quicktime files from FCP onto my desktop then saved them as quicktime mov. through QT player which was successful enough.I then burned a copy of this QT movie in toast as a data dvd compatible for Mac & PC viewing.When I played the dvd in QT 7.4.5 the playback was choppy but the sound was fine. I then played the same disc on my G5 desktop running panther and QT 7.4.1 and it was absolutely fine.Is this process rather a roundabout way of doing things ? and what could be causing this choppy playback on my laptop?

    Data DVD's and regular movie DVD are not read in the same way. A regular movie that is being read by your DVD player app is being stream too...and the player is set up to read from a DVD that way.
    On the other hand a data DVD the data is just setting there...The DVD player can't send the video to Quicktime fast enough to play smoothly. That's why you need to copy the data DVD to the hard drive.
    It would be if you had a 1gig image on a DVD and tried to edit it with Photoshop from the DVD. Photoshop would constantly bog down trying to read from the DVD while editing the image. Same if you had video files on a DVD tried and to it them from a editing app. The editing app not getting the data fast enough making editing very slow. Sometimes the program that's trying to read the from the DVD will freeze or crash. Best to copy the data from the DVD to the hard drive.

  • Help with video playback after updating to 3.1

    Hi there, after updating to 3.1 on my 2nd gen iPod Touch, I restored it and loaded some videos I converted. On playing those files, the video would play normally until at a random point the video frame would freeze, while the audio continues to play. If I quit the video app and go back to the video, it would play again normally for maybe 1 minute and then the video frame would freeze again, while audio still continues.
    These video files were working perfectly before I updated to 3.0, so I doubt that there is a problem with the files. Could someone suggest what I should do in this situation? Should I revert the firmware back to what it was before updating to 3.0?
    Thanks in advance for your help!

    I have the same issue, except that if I let it go on for a few secomds the video eventually catches up. I am also watching converted videos, and mine are in mp4 format. I haven't tried m4v yet but this is still a bug that Apple should fix.

  • Itunes choppy audio playback after update of software...no help in site!!!!

    I have updated my itunes in the past month and am getting ready to abandon itunes all together (though I have loved it up until now!) All of my audio plays back so choppy you can not make out one word of any song. I purchase quite a bit of music and it is now useless! I have gone onto the web and spent hours searching for help only to discover there are lots of people out there with the same problem and apple seems to be doing nothing. I found another couple post on the forums with no reponse. I did find after some research on google that you should adjust the sample/bit rate on quicktime and it should help, this is not true. PLEASE PLEASE PLEASE could someone from itunes/apple team give me a solution for my purchased songs?
    Dell Xps 410   Windows XP Pro  

    We apparently have a major problem with "Paid for" merchandise that is NOT being supported by itunes/Apple
    My hope here is that this site IS being moderated by some apple techs, but I am not seeing much. If you dig into the archives of this message board you will see a few of us out there that have been trying to get this resolved for a while and there are NO replies to their messages. Also I would like to state that apple makes it nearly impossible to find a good e-mail address that would go to anybody for help. We need to try and keep this topic on top of the message board to get it looked at by the right person. I don't understand the computer being under resourced though, I am running a dual processor and have 2 gig of ram.... my audio never plays correctly now regardless of itunes being opened alone of with any other applications. I NEED TO HAVE MY PAID FOR MUSIC BACK!
    sorry-- had to get that off my chest.
    Thanks for your support
    G
    Dell Xps 410   Windows XP Pro  

  • Premiere CC Sluggish after update 7.2.0

    My Premiere Pro CC is running extermely sluggish after the 7.2.0 update.  Playback is very slow and unresponsive.   I tried to trash my perference and that did not resolve the issue.  I created a new project and imported the media again and still very sluggish. 
    Has anyone else experienced this or have any suggestions. 
    My Mac Pro is:
    Version 10.8.5
    2.4 Quad-Core Xeon
    24GB RAM
    SSD startup and SSD project drive.

    Ok, I think I might have a solution as I changed a new project settings and started getting the lagging/performance issue. Then got rid of it by swapping the project settings back.
    I have been using RGB curves for the last 3 months on my laptop (specs above) and have had no issues with RGB Curves in Premiere 7.2.1 - I just checked my settings and I am using GPU acceleration via CUDA on my laptop. 
    Both my systems are running Mac OSX 10.9.2
    I then put RGB curves on the same clip in the same version of premiere on my Mac Pro Tower (Specs above) with GPU acceleration via open cl turned on and it immediately lagged and slowed my whole system.
    Next I turned off the OPEN CL option and chose Mercury engine playback software only and the issue immediately dissapeared meaning I can playback in full resolution and grade like we should be able to do.
    I would be very interested to see if this solution works for anyone else who is having this problem.
    Thanks
    Piers

  • Problems with Premiere Elements 8 after updating to Nvidia driver 195.81 or later?

    Hello PRE8 users,
    If you have an Nvidia-based graphics chipset, and you've updated to Nvidia driver version 195.81 or later and you're still experiencing frequent crashes and freezes in Premiere Elements 8, then we'd like to hear from you in this thread. As mentioned in the announcement at the top of this forum, we believe most of these issues are caused by a problem with an Nvidia driver that was released after PRE8 was developed, and that the issues should be resolved by updating to Nvidia driver version 195.81 or later. Notes from the announcement I mentioned above are copied below for your reference.
    Best regards,
    Chad
    For Nvidia users, there is a driver update that will fix both of the following issues:
    Premiere Elements 8 does not restart after closing on Windows
    Frequent and inexplicable crashes with Premiere Elements 8
    To resolve these issues, you should update your GPU (graphics card) driver to version 195.81 or higher, by following the steps below.
    1.      Identify which GPU driver you have by right clicking on the Desktop > Properties > Settings and in the Display field it will be displayed.
    2.      Go to http://www.nvidia.com/Download/index.aspx?lang=en-us and download driver for your GPU card. Its size varies from 80 to 120MB depending upon the GPU card model.
    3.      After the download is complete, run the driver install Installation. This should take less than 2 minutes.
    There are no known issues that the latest driver update will cause.
    This is an announcement. There is a separate discussion topic located here.
    ***If the update steps shown above do not upgrade your system to version 195.81 or higher, then you may need to download the driver directly. Use the link below only if the steps above do not update your driver to 195.81 or higher. The download page for Vista and Windows 7 is located here:
    http://www.nvidia.com/object/win7_winvista_32bit_195.81_beta.html
    http://www.nvidia.com/object/win7_winvista_64bit_195.81_beta.html

    Processor
    AMD Athlon(tm) II X4 620 Processor
    7.1
    4.9
      Determined by lowest subscore
    Memory (RAM)
    4.00 GB
    7.1
    Graphics
    NVIDIA GeForce 9500 GT
    4.9
    Gaming graphics
    2431 MB Total available graphics memory
    6.3
    Primary hard disk
    231GB Free (466GB Total)
    5.9
    Up here I copied and posted my PC's spec's.  Since upgrading to the new driver, my problems increased.  I seem to experience more crashes than before.  Happens randomly and I can not see a pattern.   (I have noticed dragging clips from one area to another on the time line is no-no)
    JPR

  • Premiere CC crashes after update (Lion to Mavericks)

    Hey guys,
    So I installed Mavericks on my OSX and now my Premiere CC does not work. When I open it, it immediately crashes and says Adobe Premiere PRo CC Quit Unexpecedly. This is after I installed the new Mavericks OSX on my system. I tried reinstalling, updating to the latest version, and it's still crashing. PLEASE HELP!
    This is the report that it gives me:
    Process:    
    Adobe Premiere Pro CC [1664]
    Path:       
    /Applications/Adobe Premiere Pro CC/Adobe Premiere Pro CC.app/Contents/MacOS/Adobe Premiere Pro CC
    Identifier: 
    com.adobe.AdobePremierePro
    Version:    
    7.2.2 (7.2.2)
    Code Type:  
    X86-64 (Native)
    Parent Process:  launchd [154]
    Responsible:
    Adobe Premiere Pro CC [1664]
    User ID:    
    501
    Date/Time:  
    2014-04-08 22:31:25.571 -0400
    OS Version: 
    Mac OS X 10.9.2 (13C64)
    Report Version:  11
    Anonymous UUID:  5168CCD0-7CD0-647A-98FF-924DC21C90A4
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
    VM Regions Near 0:
    -->
    __TEXT            
    0000000100000000-0000000100003000 [   12K] r-x/rwx SM=COW  /Applications/Adobe Premiere Pro CC/Adobe Premiere Pro CC.app/Contents/MacOS/Adobe Premiere Pro CC
    Application Specific Information:
    /Library/Frameworks/CUDA.framework/Versions/A/CUDA
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   com.apple.CoreFoundation 
    0x00007fff848cac5f CFStringGetLength + 15
    1   com.apple.CoreFoundation 
    0x00007fff848dde58 CFStringCompare + 24
    2   CUDA                     
    0x0000000111ce8fff GetNVDADriverModelString + 287
    3   CUDA                     
    0x0000000111cec823 cuda_driver_initializer + 99
    4   dyld                     
    0x00007fff67eccc2e ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 268
    5   dyld                     
    0x00007fff67eccdba ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 40
    6   dyld                     
    0x00007fff67ec9a62 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) + 308
    7   dyld                     
    0x00007fff67ec99eb ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) + 189
    8   dyld                     
    0x00007fff67ec98f6 ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) + 54
    9   dyld                     
    0x00007fff67ebfb0e dyld::runInitializers(ImageLoader*) + 89
    10  dyld                     
    0x00007fff67ec67cf dlopen + 538
    11  libdyld.dylib            
    0x00007fff8b40b7ee dlopen + 59
    12  com.adobe.GPUFoundation.framework
    0x000000010914f378 cuInit + 40
    13  com.adobe.GPUFoundation.framework
    0x0000000109102a8d GF::Initialize(bool, void*, void*) + 333
    14  com.adobe.DisplaySurface.framework
    0x0000000110bd0906 DS::ExecuteGPUSnifferAsync() + 22
    15  com.adobe.Mezzanine.framework
    0x0000000105dea830 MZ::(anonymous namespace)::FullInitializer::FullInitializer(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, bool, bool, bool) + 192
    16  com.adobe.Mezzanine.framework
    0x0000000105de9d64 MZ::Initializer::Initializer(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, bool, bool, bool) + 84
    17  com.adobe.Frontend.framework 
    0x00000001000a7d77 FE::Initializer::PrivateImpl::PrivateImpl(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 1479
    18  com.adobe.Frontend.framework 
    0x00000001000a6f88 FE::Initializer::Initializer(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 40
    19  com.adobe.Frontend.framework 
    0x00000001000c808d FE::AppMain(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int, void*) + 237
    20  com.adobe.Frontend.framework 
    0x00000001000cf285 FE::Run(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int) + 581
    21  com.adobe.AdobePremierePro
    0x00000001000018bc main + 524
    22  com.adobe.AdobePremierePro
    0x00000001000016a4 start + 52
    =================================
    Edited by moderator to trim crash report down to the essentials

    1st, please do not post full crash reports... if an Adobe "staff" engineer asks for a report, you would send a Private Message
    2nd, Read http://forums.adobe.com/message/6109315#6109315 for a possible Mavericks fix
    3rd, if #2 doesn't help, do the below
    Go to http://forums.adobe.com/community/premiere and, in the area just under Ask a Question, type in
    maverick
    or
    mavericks
    or
    10.9
    You may now read previous discussions on this subject... be sure to click the See More Results at the bottom of the initial, short list if the initial list does not answer your question

  • Choppy playback after upgrading to iTunes 11

    I am still on OSX 10.6.8 so I can still use Front Row on my laptop. I just recently upgraded to iTunes 11 and now playback of video will become choppy and sometimes stalls and the sound will also become choppy and unsynchronized with the video. This occurs when playing video on iTunes or Front Row. Has anyone else experienced this and if so, have you come up with a solution?? Thanks in advance.

    I was also having this issue on my iMac running OSX 10.6.8 after upgrading to iTunes 11.  Clearing my user Library Cache seems to have solved the issue.
    In case you're not sure how to do that, open a finder window, hit Cmd-Shift-G to go to a folder, then enter "~/Library/Caches". Select all the contents of the Caches folder, and hit Cmd-Delete. You will be prompted to enter your password in order to delete these files.  Restart your machine and empty the bin when you log back in.

  • Choppy Playback after 7.2 Upgrade

    I also upgraded my Final Cut Studio to 2.0
    Now when I open up DVCPROHD files in Quicktime, the playback is terribly choppy (and vertical resolution is jaggy) at all window sizes. If I open it up in Final Cut, it plays back fine as usual and the resolution is great.
    I had no issues before this upgrade. What's the deal?

    I've experienced something similar.
    I was watching an HD music video in 720p and it looked fine; played smoothly and had a crisp picture.
    But after installing Quicktime 7.2, the same video now plays choppy when put in fullscreen, and the video looks a little jagged. However, if I watch the same video in Front Row, it plays perfectly and looks great.

  • 10.2 No Playback After Update - solved

    HI
    just in case anyone else gets this ... Had me stumped for a bit .
    updated to Yosemite from Mavericks so I could use FCP 10.2. Among other things I also updated my Audio interface driver ( Apogee One ) and tested it it. Worked fine.
    Updated FCP X along with ProVideo updates.
    it launched fine and worked in all respects except it would play anything .! Hitting play gave a 3 sec. Beach ball then the app sat there . Nothing!nActivity Monitor showed FCP X using 100% CPU.
    Messed around a lot ... permissions, prefs all that ... To no effect.
    FInally I uninstalled and reinstalled the Apogee audio drivers  and all came good.
    maybe this might help  if you are having a similar issue,
    best

    Download and reinstall OS X Yosemite 10.10.2 Combo Update if you upgraded an existing Yosemite system. Otherwise, do this:
    Reinstalling OS X Without Erasing the Drive
    Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
    Reinstalling OS X Without Erasing the Drive
    Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
    When the recovery menu appears select Disk Utility and press the Continue button. After Disk Utility loads select the Macintosh HD entry from the the left side list.  Click on the First Aid tab, then click on the Repair Disk button. If Disk Utility reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit Disk Utility and return to the main menu.
    Reinstall OS X: Select Reinstall OS X and click on the Continue button.
    Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
    Also see:
    Reinstall OS X Without Erasing the Drive
    Choose the version you have installed now:
    OS X Yosemite- Reinstall OS X
         Note: You will need an active Internet connection. I suggest using Ethernet
                     if possible because it is three times faster than wireless.

  • No sound in multimedia playback after update (xine,vlc,mplayer)

    Hi!
    For some days now I don't have sound anymore in amarok and vlc. Since the sound works on e.g. youtube I don't know how to find the root of the problem and of course not the solution. In amarok my sound card doesn't show up any more. I'm using ALSA. "aplay /usr/share/sounds/alsa/Front_Center.wav" doesn't give any output. (I don't know if it matters.)
    I already spent time in searching (googling) by myself without success. Can anyone give me a hint?
    Thanks in advance,
    Maximalminimalist
    Last edited by Maximalminimalist (2010-12-14 20:05:41)

    Ultraman wrote:What vitals did you check? What DE/WM are you running? KDE by any chance?
    I'm using i3. (tiling WM)
    Ultraman wrote:Did you check the mixer? Anything muted there? Probably not, but worth a check.
    Alsamixer should be fine. (Sound works on youtube anyway.)
    Ultraman wrote:Have you blacklisted the snd-pcm-oss module to prevent some app using OSS instead of ALSA and claiming the soundcard that way? (rc.conf -> MODULES=(!snd-pcm-oss) )
    No, I even had it in the modules but the "!" makes no difference.
    Ultraman wrote:If you are running KDE: Have you checked Phonon's settings? Does it recognize any backend (e.g. Xine, Gstreamer)? What about sound hardware?
    I'm not using KDE but amarok recognises xine.
    Ultraman wrote:Tried starting VLC and Amarok from a terminal and looked at the output they send to it? Perhaps any error messages among them?
    When I start VLC from terminal I get this:
    vlc Weird\ Al\ Yankovic\ -\ White\ And\ Nerdy\ \[HQ\].avi
    VLC media player 1.1.5 The Luggage (revision exported)
    Blocked: call to unsetenv("DBUS_ACTIVATION_ADDRESS")
    Blocked: call to unsetenv("DBUS_ACTIVATION_BUS_TYPE")
    Blocked: call to setlocale(6, "")
    Blocked: call to sigaction(17, 0x7fec095fbac0, 0x7fec095fbb60)
    Blocked: call to setlocale(6, "")
    frame skip 8
    frame skip 8
    When I tell vlc to use alsa. (Which wasn't necessary before.) I get this as a "pop-up error":
    Potential ALSA version problem:
    VLC failed to initialize your sound output device (if any).
    Please update alsa-lib to version 1.0.23-2-g8d80d5f or higher to try to fix this issue.
    But pacman tells me:
    pacman -Qs alsa-lib
    local/alsa-lib 1.0.23-2
    An alternative implementation of Linux sound support
    local/lib32-alsa-lib 1.0.23-4
    An alternative implementation of Linux sound support (32 bit)
    EDIT: I just tried KDE. (I have it installed but don't use it.) Everything is weird. I can't press anything right with the mouse because everything is mirror inverted and some zones are covered with a weird mix of pixels...fact is KDE doesn't work fine on my computer right now.
    Last edited by Maximalminimalist (2010-12-12 04:01:53)

Maybe you are looking for