InContext Editing Too Slow

Hi Folks,
Love the concept of InContext editing but I don't think it actually works!
I am only working on a simply HTML page with one other user. It takes forever to do anything.
clicking the edit page button: 23 seconds
clicking the done button: 56 seconds
Clicking the publish button: 25 seconds then clicked ok and it took another 47 seconds.
This is the 3rd client I have tried this product on. Each time we have found it a great solution until we try to actually work with it. It's just way too slow so we stop using it.
I tried the Adobe demo pagehttp://incontextediting.adobe.com/demo/includes/ice/ide.html#page=news.html. It's supper fast no issues at all.
Is there some trick to setting it up that I don't know about?
I spent an hour in total this morning with tech support. 25 minutes on hold, then I spent more time actually going through license numbers then talking about my problem. They just told me that Adobe does not support InContext Editing. I was told to go to the support portal and put in a ticket. I went there, the support portal doesn't list InContext Editing in the list of support issues. What gives?
Thanks for any help you can provide
Sylvia

Hi Tom,
Here is the page http://webviewdesigns.com/haiti_earthquake_relief/includes/ice/ide.html#page=haiti_news_ja ckie.html
I'm using Safari (MAC PRO) and my client is using Firefox (Windows XP)
I've had the same issue before with client's on other browsers and desktops, servers configs.
The page is a news page for a Haiti relief site mini site. It's is inside my work site which is pretty big, could that be an issue?
I've attached it for you to look at.
Thanks
Sylvia

Similar Messages

Bumblebee performance is too slow

Hi everyone,
This is my second post in this forum and it has been only 2 days that I met Arch. Before, I was using Ubuntu for 3 years, but due to low performance in my PC, unfortunately, I decided to say good bye which was hard to say.
Now, I am trying to have the same setup as my previous laptop and Bumblebee was one of them. I followed the instructions here: https://wiki.archlinux.org/index.php/Bumblebee.
It seems that bumblebee is installed and working, however, the FPS is too slow:
$ optirun glxspheres64 -info
Polygons in scene: 62464
Visual ID of window: 0x20
Context is Direct
OpenGL Renderer: GeForce GT 520MX/PCIe/SSE2
0.023848 frames/sec - 0.021114 Mpixels/sec
Without optirun I get:
$ glxspheres64 -info
Polygons in scene: 62464
Visual ID of window: 0x20
Context is Direct
OpenGL Renderer: Mesa DRI Intel(R) Sandybridge Mobile
0.033237 frames/sec - 0.029426 Mpixels/sec
0.029968 frames/sec - 0.026533 Mpixels/sec
This is impossible as I was getting very good results before.
I am wondering if I did something wrong, or missed anything.
Just for information, system specs:
Intel i7 2670QM 2.2 GHZ
4 GB RAM
1 GB GeForce GT 520MX
512 MB Intel Graphics
I played 0ad with and without optirun and the performance was good in both of them, but not sure if it switches the video cards itself.
I also have bbswitch installed.
Any help would be appreciated. Thank you.
Last edited by wakeup12 (2014-09-27 14:29:19)

Hello,
Can you please explain in a little more detail the scenario you testing? Are you comparing a SQL Database in Europe against a SQL Database in India? Or a SQL Database with a local, on-premise SQL Server installation?
In case of the first scenario, the roundtrip latency for the connection to the datacenter might play a role.
If you are comparing to a local installation, please note that you might be running against completely different hardware specifications and without network delay, resulting in very different results.
In both cases you can use the below blog post to assess the resource utilization of the SQL Database during the operation:
http://azure.microsoft.com/blog/2014/09/11/azure-sql-database-introduces-new-near-real-time-performance-metrics/
If the DB utilizes up to 100% you might have to consider to upgrade to a higher performance level to achieve the throughput you are looking for.
Thanks,
Jan

Why am I getting this error message, "Disk is too slow. (Prepare) (-10001)"

Hello all! I've been using GarageBand for a while now and I've accumulated quite a few files. Along with all of my movies and iTunes library, my internal hard drive filled up rapidly and I didn't catch it. I received a warning message on my screen one day saying that my hard drive was nearly full and I only had a few MB available. I'm using a 150 GB Solid State Hard Disk on my 2009 MacBook Pro (2.6 GHz Intel Cre 2 Duo, 4 GB of RAM). I remembered reading a while back that it's better to use an external hard drive for pretty much everything when using Garageband, so I bought one. I now have a seagate 500 GB, 5400 rpm external (USB 2.0) and I moved ALL of my movies and music over to it. I freed up around 60 GB of space on my internal hard drive in doing so.
So now that I've given you a little background, let me explain the issue I'm having. Before I noticed that my hard drive was full, I started receiving this error message:
Disk is too slow. (Prepare)
(-10001)
Upon receiving this message, I was unable to do pretty much anything in GarageBand. I couldn't listen to tracks, export to iTunes, or do anything! All I'm using GarageBand for is editing. My band and I do all our recording (and mixing) offsite at a separate studio and i just deliver a 2 track stereo signal (L/R) to my MacBook. From there, I just cut the individual tracks from a block of 30-45 minutes of recording because we just record our entire studio session and mix everything there. I pretty much never have more than two tracks and a few effects going at the same time.
After I realized that my disk was nearly full, I consulted my brother-in-law. He's head of the IT Deartpment at a major hospital here in West L.A. and he told me that I may have created a problem with the cache by filling up my internal hard drive and that I may still have issues with performance even after I free up space. He then told me that I may need to reboot my MacBook a few time to "free up the cache" (or something close to that, sorry guys I'm not that tech-savvy). It seems he may have been right, as I'm still experiencing the same issue. I rebooted around 10 times overall to no avail. I'm still using my internal hard drive to store the files that I'm working on (temporarily) because USB 2.0 is way too slow for my liking, when using GarageBand.
I've read quite a few articles on this offering solutions such as:
1. Do a complete Uninstall and Reinstall of GarageBand
2. Clone my hard drive to my external, format it, and reinstall everything back on it
3. Get a hard drive that supports Firewire 800 (The HDD I bought is USB 2.0, but it has two USB cables to increase speed, but I only have 1 port and I tried a powered USB Hub, but this HDD won't work with it for some reason).
4. Use different editing software.
5. Take it to Apple!
Will any of these things fix my problem? Are some better than others? Before I do anything, I wanted to ask this question on the furum to see if anybody had an easier (or cheaper!) solution. Any suggestions, tips, or advice would be much appreciated, as my band is starting to get on my case about finishing our CD! Thanks...

Have a look into the Preferences folder (YourUserFolder/Libraries/Preferences/) and trash all Logic preferences.
You'll have to setup the program again.
cheers
rob

Internet connection too slow, is there a way to speed up the itouch?

So I can connect to Facetime, but all I see is a picture of a person and then the Itouch freezes and shuts down. I think it is because my internet connection is too slow, because it only doesn't work in my apartment (it works at places with quicker connections).
The question is, is there currently a fix to this problem (I can't be the only one who has it)? It all works, just freezes after connecting and showing the picture of the person I'm talking to then disconnects. Is there a way to make this work?
I'm at college and the only reason I got the 4g from my parents is 'cause they wanted me to help my little bro with homework back home... but if Facetime doesn't work at college then I should sell mine and go with a cheaper, earlier generation. Thanks!
Message was edited by: ClassyCoug

By what type of security I mean, WEP (not preferred), WPA, WPAs. I would go to the support page for you router on the manufacturer's sit to see if an update to the firmware is available. You also have to enter the setup for the router to determine the installed version of the firmware. Not infrequently a firmware update fixes problems since that is one purpose of the updates.

No Reason For Disk Too Slow Error, any ideas?

Ok,
So I've used Garageband for years from iLife 06 and up and I've never had an issue with any Garageband until now. Here's the deal, I still get the disk too slow error, and there is no explanation. Below is my computer config:
COMP I'M USING:
Macbook Pro 13 inch
OS X Mavericks
Intel Core 2 Duo (1st unibody)
4 GB of RAM MAX
BRAND NEW Hybrid 7200 RPM Drive Installed 500GB total, 300 GB FREE
NO Other programs are open.
I use Garageband for recording songs but mostly now for recording podcasts. So the track I am using is normally 1 hour in duration. I can't seem to skip around, from minute 1 to minute 54 and edit at my whim without beach ball and timeing out getting the disk to slow error I never had this issue before, I either get the disk to slow error when trying to navigate large gaps of time in the podcast as I said earlier or even during RECORDING a podcast it'll simply say disk to slow, stop recording and occassionally say there are too many tracks in use, when I only record using 1 track of audio.
How can this be possible? Even my old G4 allowed me to jump all over the timeline with no issues. It seems there is some kind of flaw in the software. And yes, I just restored OSX Mavericks to my brand new Hybrid Hard drive, so there's no explanation as there are no disk errors or permissions errors of any kind.
I'd rather not hookup an external drive to record too as that seems silly when I've never had too before. If this "modern" computer can't do something that my old G4 ibook can do, don't you think we're going in the wrong direction with this program?
I've heard of so many people having this issue, and I thought upgrading my OS and getting a new HD would help but it hasn't. I'm at wits end with this issue.
Any advice would be helpful, thank you.

There are a few other reports of problems with 10.6.7
Some audio device(s) inputs have ceased working, a few disk to slow messages...etc. I don't see the wisdom of upgrading a working DAW system if that's it main function. OSX has to support a lot of different hardware now, many, many Intel motherboard and/or processor revisions... it's not going to be as smooth sailing as it used to be.
pancenter-
Here's a search over the past 90 days.
http://discussions.apple.com/search.jspa?threadID=&q=Disktoslow&objID=c231&dateRange=last90days&userID=&numResults=15&rankBy=10001

Disk too slow error when using M-Audio Oxygen 49 keyboard

I bought the M-Audio Oxygen 49 keyboard. And when I plug it into my MacBook Pro to do some playing, the project will record for maybe a minute but then I get a 'disk too slow' error and the recording stops. This happens every single time, no matter if there's 30 tracks or 1 track on the recording. I know that it is the keyboard causing the error because I am currently working on a 59 track piece that has effects on almost every track and my setup doesn't even blink. (well it'll pinwheel for a second when I hit record sometimes, but the CPU and disk meters don't ever get near red-line levels).
What on earth is causing this stupid keyboard to cause this problem, and how do I fix it? It's clearly the keyboard. When I unplug it and record a live track on a project that just gave me the 'disk too slow' error, everything works just fine!
Grr...
Any help is appreciated, thanks!
Edit: I have the MBP plugged via firewire into an Echo Audiofire and then into a WD hard dtive (at 7200 RPM). The keyboard is USB into the MBP.
Message was edited by: Zombie Flanders
Message was edited by: Zombie Flanders

hi
i spoke with Apple pro application support staff who confirmed that the Tascam 1884 patch for 10.4.10 is the cause of the problem. The apple boot drive can reliably record 1 channel of audio under normal circumstances. Apple staff described the situation as "unfortunate" and recommended to wait for Tascam to release 10.4.10 compatible drivers.
For anyone interested in the technical background, the Tascam 10.4.10 patch DOWNGRADES the audioFW component (messing with kernel headers etc.). This compromises the OS's ability to correctly communicate with FW devices.
I had tried recording to a firewire 800 drive, but all FW IO is affected by the 10.4.10 Tascam patch: Logic simply didn't record anything to disk when I tried this, and the machine became unresponseive. I do not recommend anyone attempt recording to a FW drive with the Tascam drivers installed.
I have recorded circa 400 hours of single channel 96K 24bit audio to my internal Macbook Pro boot drive using the same software/configuration under 10.4.9 without a single glitch. I do recognise that when requiring heavy disk IO it is not advisable to record to the boot drive. However, 1 channel of audio can be reliably recorded if the system is well maintained.
Thanks to all for your comments and suggestions.

How do I fix the problem 'disk is too slow' and what does it mean anyway?

I'm transferring casete tapes to the Mac via the input line. I've transferrred nearly 100 with no prouble, but sudddenly today two things have gone wrong (see separate question for the other one). This one is that suddenly the error message 'Disk is too slow' comes up. also the track (the top one, not the bottom edit section one) is bright red instead ofthe usual dark purple.
What's gone wrong and how do I fixit?

Sorry about the lack of terms: lazy of me I admit. Having read up Garageband Help, I think I've got the answers. Yes, by the top part I mean the track in the timeline. The bottom part is the same track showing up in what is headed the 'Audio Region' The bright red is the colour the track is in the timeline during recording, and it stays like that until after stopping recording I click somewhere in the timeline section (not necessarily on the track itself) at which time it just goes the normal kind of dull greyish colour an unselected region does.
Thanks for telling me how to see the HD info. Its 250GB, of which I've used about 23GB. The first computer I worked on as a programmer back in 1962 had a 400KB drum (the first disks didn't arrive until 1963) as its random access backing store - and yes, that is a K. The machine also came with 12KB of RAM and 4 tape decks, was the size of a hotel kitchen, and cost about $200,000. You young people don't know how lucky you are

Disk is too slow (Record)(-10004) error..so sick of this.

Hello all,
I can no longer record more than three tracks in logic without getting the error message "Disk is too slow (Record)(-10004)". When this happens, recording is stopped.
At first I suspected my drive was faulty, maybe slowing down. So being in the middle of a session that took me 2 hours to set up, I called for a break and rushed off and bought an external Seagate 7200rpm firewire 800 drive. I installed it and set it as the recording path for the project. There was no change, the same error occured.
I then switched the target drive to another internal one I use for Time Machine - same problem occured.
It seems to me that this problem has nothing to do with my drives. I am at a loss to explain it. I have looked for hours online for a solution but while many have experienced this there seem to be few answers out there.
Unless I find a solution this will be my last project with Logic. I tried and tried for the last 5 years to use this program but things like this keep happening. It's glitchy with UAD cards, Duende, RME interfaces, Midi controllers, Hard Drives, RAM and external clocks. I've had problems with them all over the years. I will most likely switch to Cubase which I feel is inferior for editing and loops, but at least it seems to be stable.
If anyone has any insight I'll try and fix it, but I just can't keep shelling out money for a program that just doesn't work.

I am experiencing a similar problem & have been receiving the same messages, even while recording as little as one track and playback has become an issue as well. However, THIS WAS NOT ALWAYS THE CASE. I have heard of people with this same problem, where they receive this message out of nowhere after logic has been working perfectly for them.
I also would like to note that I am running all settings in logic for optimized recording and playback (audio & buffer settings etc etc etc)
THIS IS NOT A HARDWARE ISSUE, at least in my situation as I am running a fast internal HD & have ample memory. Please reach out if you feel like you have a pragmatic solution to this issue.
This may be a possible lead on the fix... I remember reading this post from a user "soundsgood" in 2008 who was having a similar issue..I don't understand completely his solution, but if someone could enlighten me, I feel that this might be the solution to our issue
+"Okay - forgive me 'cause I'm a newbie on this forum and if somebody else has already figgered this out, I'm sorry.... I've been having the same problem all of the sudden after many years of crash-free and error-free recording. I've read everything. I've pulled my hair out. I've done dozens of clean installs. I've repaired permissions so many times I can do it blindfolded. And sitting here tonight, it dawned on me.... there are TWO places Logic is sucking data from: wherever you've got your SONG files stashed, of course.... but it ALSO NEEDS TO ACCESS THE STARTUP DRIVE (or wherever else you might have your Apple Loops installed). I was watching my drives being accessed during a playback of a fairly complicated tune (most tracks were frozen of course), and both of the afore-mentioned drives were going berserck with accesses. We're all focusing on our dedicated audio drives, but forgetting about our boot drives (where Logic usually resides along with most or all of our loops). I carbon copy cloned my boot / operating system (including Logic) to a different (in my case, an external firewire) drive and the problem disappeared. Could've been because the cloning process de-fragged all the loops & stuff, or maybe my OS just likes snatching its sample/loop info from an external drive. Worked for me... so far....... let me know if it works for others....."+

GARAGE BAND disk is too slow. (prepare) (-10001)

Hi, Im trying to edit some mp3 files in separated tracks in GB on my NEW Macbook Air 2013 with 4gb ram and 128 flash drive, this files are between 170mb and 221 MB, so this message comes on: disk is too slow. (prepare) (-10001) garageband... what can i do? The files are MP3. What could be the problem? the 4gb of RAM? the 128gb ssd? Thanks!

How much free disk space do you have? Keep at least 10 GB disk space free for the operating system as working space, better more.
Try to lock all tracks that you are currently not using, while you are editing.
Close all other applications and reboot, before starting to work.
If the problem persists, you may have a problem with incompatible audio drivers. Then I'd test from a different user account, to check, if there is a general problem.
Regards
Léonie

Is Version Cue CS4 TOO SLOW TO USE??????

Is it just me or is the new CS4 versioncue workflow extremely slow?
After installing Version Cue CS4 on the same server that was running CS3 and trying to open an existing InDesign project (book with dozens of linked images), I realized that using VersionCue CS4 is so painfully slow compared to CS3 that it's unusable.
It seems that VC CS4 does not create local copies on the hard drive and instead, all traffic is sent over the relatively slow Ethernet connections. While this does help with synchronizing confusions, it makes working on the projects way too slow.
VC CS4 is running with 768MB on my server, so I don't think that is the problem.
Will someone respond to this post and let me know if (a) I'm probably doing something wrong and everything will be OK, or (b) if I can install CS4 and still use VC CS3 on the server?
thanks in advance!

Thanks for the response.. It seems a bit hit or miss on opening up my projects.
For example, if I click on a PDF file in Bridge, it takes upwards of a minute to launch Acrobat 9 and display the first page. If I open Acrobat 9 first, and then click on the PDF, it opens almost instantly.
Also, we have a job with a Microsoft PPT slideshow. When editing the slide show and saving back to the Version Cue 4 server (pressing save in the PowerPoint program), it takes upwards of a minute.
This is with 768MB allocated to the stand-alone server, and 1GB assigned to the Adobe Drive CS4 cache on the client computer.
Does anyone know how to get VC CS4 or Adobe Drive to operate faster?

Oi vay! a mac thats too slow to use DVDs, quicktime, imovi,

OI VAY!!I believe I was sold a mac, by a mac expert nonetheless, that is far too slow and lacking in memory to watch videos in any form, dvd, file, with quicktime, etc.
And it seems too old for the updates available.
its a iBook G4
version 10.4.11
processor: 800 mhz (slow!)
memory: 640 mhz (low!)
Can anyone pls confirm or tell me otherwise please!?
thank u all or any replies most appreciated!
m in berlin

The computer should be able to play DVDs, if it has the correct Combo optical drive,
(and not a CD-RW basic drive) and the RAM can be increased to 1.12GB by adding
a chip under the keyboard in the upgrade slot there.
All in that series should have been able to play DVD media and record/play CD media.
You can find more specifications about portable Mac and others by getting the
Mactracker download from http://mactracker.ca and note the iBook (G4) info.
According to this ^ database (free download) the RAM max is over 1024MB.
Early iBook G4 tech specs: http://support.apple.com/kb/SP89
The software updates for Tiger 10.4.11 should appear when you run Software Update
from the menu which appears when you click on the Blue Apple in left side menubar.
You could also get the items which appear in there, direct as stand-alone installers
from Apple Support downloads online (good for later re-installs, if necessary, if saved.)
Not sure what the problem really is, in regard to the computer. There is a DVD Player
which should launch automatically on insertion of DVD media; in System Preferences
you can choose how media discs are handled in the appropriate Preference panel.
Note, you may have to buy an iLife version suitable for the computer you have, and
due to technical differences in the older 800MHz iBook G4 vs some latest models,
the iLife 09 may have specifications unsupported in the hardware of that computer.
iLife 06 is better suited for older G4 Macs, and that is a retail installer disc. You may
be able to get one in the second-hand market. Tiger 10.4 retail disc itself does not
contain an iLife version, as that was a separate disc. Computers that shipped with
Tiger 10.4.x included extra software and they had an iLife version, plus AppleWorks.
You can see a DVD without iLife installed, DVD Player should be in Applications folder.
iLife '09 Support: http://www.apple.com/support/ilife/
So, perhaps the alleged expert may have omitted something or the other in discussion
of the computer; ideally, the best iBook G4 would be the last edition 1.33/1.42GHz 12/14".
Hopefully this helps a bit.
Good luck & happy computing!
edited.

Application response too slow- How to resolve (webLogic)

Hi All, Can you please let me know what are all the main areas that i need to concentrate in the weblogic application server if i get the complaint from the clients saying "application performance is too slow".
Edited by: user11361691 on Apr 21, 2010 12:18 AM

you need to check the following:
1: Check the server log files to find any errors at the time when the Client is complaining about the server performance.
2: You can enable the GC logs in the server log and can check whether the there is any issues with the memory usage of the server. From the GC logs you can that whether the time has been taken to to the GC and hence you can try allocating higher memory or you can try changing the GC algorithm according to the analysis.
For details refer the following link:
http://download.oracle.com/docs/cd/E13222_01/wls/docs100/perform/topten.html
http://download.oracle.com/docs/cd/E13222_01/wls/docs100/perform/JVMTuning.html
3: Finally you can collect the thread dumps snap shots and can see whether there are any stuck threads or deadlock situation in the server at the time of slow performance.

[SOLVED] mplayer says that the system is too slow?

I've noticed that mplayer has been complaining that my system is too slow to play videos lately.
mplayer CLI output:
AVI file format detected.
[aviheader] Video stream found, -vid 0
[aviheader] Audio stream found, -aid 1
VIDEO: [XVID] 640x352 12bpp 25.000 fps 1537.8 kbps (187.7 kbyte/s)
Clip info:
Software: Nandub v1.0rc2
==========================================================================
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
Selected video codec: [ffodivx] vfm: ffmpeg (FFmpeg MPEG-4)
==========================================================================
==========================================================================
Opening audio decoder: [mp3lib] MPEG layer-2, layer-3
AUDIO: 48000 Hz, 2 ch, s16le, 128.0 kbit/8.33% (ratio: 16000->192000)
Selected audio codec: [mp3] afm: mp3lib (mp3lib MPEG layer-2, layer-3)
==========================================================================
AO: [oss] 48000Hz 2ch s16le (2 bytes per sample)
Starting playback...
VDec: vo config request - 640 x 352 (preferred colorspace: Planar YV12)
Could not find matching colorspace - retrying with -vf scale...
Opening video filter: [scale]
VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is 1.82:1 - prescaling to correct movie aspect.
[swscaler @ 0x89d5f50]SwScaler: using unscaled yuv420p -> bgr24 special converter
VO: [gl2] 640x352 => 640x352 BGR 24-bit
[gl2] You have OpenGL >= 1.2 capable drivers, GOOD (16bpp and BGR is ok!)
[gl2] antialiasing off
[gl2] bilinear linear
A: 866.0 V: 866.0 A-V: 0.012 ct: 0.099 21651/21651 2% 3% 0.2% 4 0
A: 868.6 V: 867.9 A-V: 0.763 ct: 0.099 21698/21698 2% 3% 0.2% 50 0
**** Your system is too SLOW to play this! ****
Possible reasons, problems, workarounds:
- Most common: broken/buggy _audio_ driver
- Try -ao sdl or use the OSS emulation of ALSA.
- Experiment with different values for -autosync, 30 is a good start.
- Slow video output
- Try a different -vo driver (-vo help for a list) or try -framedrop!
- Slow CPU
- Don't try to play a big DVD/DivX on a slow CPU! Try some of the lavdopts,
e.g. -vfm ffmpeg -lavdopts lowres=1:fast:skiploopfilter=all.
- Broken file
- Try various combinations of -nobps -ni -forceidx -mc 0.
- Slow media (NFS/SMB mounts, DVD, VCD etc)
- Try -cache 8192.
- Are you using -cache to play a non-interleaved AVI file?
- Try -nocache.
Read DOCS/HTML/en/video.html for tuning/speedup tips.
If none of this helps you, read DOCS/HTML/en/bugreports.html.
mediainfo output:
Format : AVI
Format/Info : Audio Video Interleave
File size : 698 MiB
Duration : 58mn 0s
Overall bit rate : 1 684 Kbps
Writing application : Nandub v1.0rc2
Writing library : Nandub build 1852/release
Video
Format : MPEG-4 Visual
Format profile : Streaming Video@L1
Format settings, BVOP : Yes
Format settings, QPel : No
Format settings, GMC : No warppoints
Format settings, Matrix : Default
Muxing mode : Packed bitstream
Codec ID : XVID
Codec ID/Hint : XviD
Duration : 58mn 0s
Bit rate : 1 538 Kbps
Width : 640 pixels
Height : 352 pixels
Display aspect ratio : 16/9
Frame rate : 25.000 fps
Resolution : 24 bits
Colorimetry : 4:2:0
Scan type : Progressive
Bits/(Pixel*Frame) : 0.273
Stream size : 638 MiB (91%)
Writing library : XviD 1.1.2 (UTC 2006-11-01)
Audio
Format : MPEG Audio
Format version : Version 1
Format profile : Layer 3
Codec ID : 55
Codec ID/Hint : MP3
Duration : 58mn 0s
Bit rate mode : Variable
Bit rate : 133 Kbps
Nominal bit rate : 128 Kbps
Channel(s) : 2 channels
Sampling rate : 48.0 KHz
Resolution : 16 bits
Stream size : 55.1 MiB (8%)
Alignment : Aligned on interleaves
Interleave, duration : 24 ms (0.60 video frame)
Interleave, preload duration : 477 ms
Writing library : LAME3.90.
Encoding settings : ABR
~/.mplayer/config contents:
vo=gl2
monitoraspect=16:9
Any ideas?
EDIT: Well, it looks like adding "ao=alsa" to ~/.mplayer/config did it. I guess that it uses OSS by default, which is apparently too slow.
EDIT 2: If anyone else can offer any mplayer performance tips, I'd still appreciate them.
Last edited by mrbug (2008-10-24 00:42:05)

Perhaps. Also, in that error message, do as it says and play around with combinations of those.
Possible reasons, problems, workarounds:
- Most common: broken/buggy _audio_ driver
- Try -ao sdl or use the OSS emulation of ALSA.
- Experiment with different values for -autosync, 30 is a good start.
- Slow video output
- Try a different -vo driver (-vo help for a list) or try -framedrop!
- Slow CPU
- Don't try to play a big DVD/DivX on a slow CPU! Try some of the lavdopts,
e.g. -vfm ffmpeg -lavdopts lowres=1:fast:skiploopfilter=all.
- Broken file
- Try various combinations of -nobps -ni -forceidx -mc 0.
- Slow media (NFS/SMB mounts, DVD, VCD etc)
- Try -cache 8192.
- Are you using -cache to play a non-interleaved AVI file?
- Try -nocache.
Read DOCS/HTML/en/video.html for tuning/speedup tips.
(Taken directly from your post )

InContext Editing not showing "edit page" button

I made a site for someone using dreamweaver and defined areas as editable regions.
I've used InContext Editing before and found it really easy with no problems until now. When I log in from my computers (varrying between 3 different browsers and 2 different operating systems), it works just fine.
At the top I see exactly this:
There are two rows at the top, and I can click "edit page" and it works perfectly.
When the person I made it for logs in, he see the top row... like this:
Clicking "Edit Site" seems to do nothing for him (well, me neither, but I can just hit edit page)...
I can't check what's going on with his computer because I don't live where he lives, but I had him make sure he had the most recent version of flash, and he does.
Does anyone know of any common problem with this? Does he have too old of a browser? Is he disabling something on his browser that's blocking the second row?
I've googled this pretty thoroughly and can't fine anyone that has had the same problem

Assuming here that you have set up ICE regions on that page...
And that he "accepted" your invitation to do ICE.
Z

Aperture - Too slow to be really efficient?

I have been thinking about whether Aperture might be a way to go for me as far as working with my photographs. The ads etc. seemed like it offered some great features and I don't like the Nikon software that has come with my cameras. iPhoto is OK for my family snapshots, but I want more capabilities for my more serious stuff.
So I when i got an email mentioning the 30 day trial I figured that was a great opportunity to check it out. I was hoping I'd be pleased enough over that 30 days that spending the $300 dollars to buy it would be justified despite the fact that I have Photoshop CS2 and a few other way to organize my photos. Thus far $300 seemed way too steep simply to duplicate capabilities I already have and doesn't come close to offering the capabilities of a full blown image editing app like PS.
So my question is this. Is this thing really supposed to be as slow as it is? The app is running so slow on my Mac G5 dual 2.5 with Radeon 9600 with 2gb of Apple installed RAM that I can't see suffering through using it long enough to even see if it does some of the things I hope it does. I certainly couldn't see using it rountinely as an app for PRODUCTIVITY. There's nothing productive about an app that takes a good 5 seconds merely to remove a master from the library. Even clicking on an image to look at it takes way too long as the preview refines it's resolution.
I did a quick search on this issue and saw lots of stuff out there. I have waded through some of it and some of it is enlightening and some just adds to the confusion. Apparently there may be an issue when running dual monitors. Am I understanding that correctly? Seems to me that most Pros and heavy duty amateurs run 2 monitors (and for good reason - most of the apps these days need to screens to display all the neccessary palattes etc.) So if 2 displays hurt performance, I can't see how this is an app that is going to work for me. I certainly don't want to go reconfiguring my Mac simply to go through the latest batch of pics. It also seems to me that a large library could also be an issue - while I don't have huge numbers of images, I do have a couple of thousand that I keep active on my machine (and a ton more on backup DVD).
So anyway, I'd like to hear from people with a similar setup to mine . . . from your experience is trying to use this app on such a system (which is by no means a slow and incapable Mac at all - I push heavy pixels doing HD work in After Effects and Final Cut all day long and never feel like the apps are too slow to even use)? I am not going to run out and buy a new system simply to run Aperture since. Even if all the bells and whistles are what they seem, they aren't enough to justify it. I also don't want to waste any time using this trial version and learning it's ins and outs if going In know the app won't run efficiently enough.
So am I crazy? Is this thing really as slow as it seems? Are there really as many speed issues as a search of the forum reveals? Is there something I am missing?

So am I crazy?
I have no such evidence.
Well, give it time.
In my personal experience, for all practical purposes
it's unusable on my configuration. A Mac user since
1986, I purchased my Mac Pro configured specifically
for Aperture, including an upgraded video card. The
outcome has been underwhelming.
As I can't buy a faster computer, I can only assume
Aperture is suited to hardware yet to be released.
Aperture is the lowest point in my experience as a
Mac user.
I am actually hearing that sentiment more than I would like to as I ask around. Too bad. On the surface it looks quite good. I findit odd that the company that has taken on such great things as it has in the video world can't make this a more efficient piece of software. Perhaps they see much bigger money in the volume that comes from focusing on phones with video and computers for your TV and thus don't really care about an app like Aperature which would really just appeal to dedicated photographers at it's current pricing and probably doesn't rpresent enough revenue - even amongst photogs with cash to burn.
I'm evaluating Aperture (which I have purchased at
full retail price) alongside the beta of another
professional photo app which is yet to be released.
The jury is still out, but growing restless.
Yeah, I have played with the Beta from one of the "Others". It was interesting. It was a while ago and that version didn't seem as potentially "robust" as aperture did. But I think it may be time to go back and take another look.

InContext Editing Too Slow

Similar Messages

Maybe you are looking for