So, what was the purpose of this email? On 4/4/10, WILLIAM GOODMAN <[email protected]> wrote: > On 4/4/10, [email protected] > <[email protected]> wrote: >> Send MacOSX-talk mailing list submissions to >> [email protected] >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://www.omnigroup.com/mailman/listinfo/macosx-talk >> or, via email, send a message with subject or body 'help' to >> [email protected] >> >> You can reach the person managing the list at >> [email protected] >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of MacOSX-talk digest..." >> >> >> Today's Topics: >> >> 1. Re: Selecting beginning of line (Macs R We) >> 2. Recording stopped because the maximum duration for the file >> has been reached (Kevin Callahan) >> 3. Re: Syncing Twitter Clients (Neil Laubenthal) >> 4. Re: Syncing Twitter Clients (LuKreme) >> 5. Re: Syncing Twitter Clients (Scot Hacker) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Sat, 3 Apr 2010 12:23:19 -0700 >> From: Macs R We <[email protected]> >> Subject: Re: Selecting beginning of line >> To: OSXtalk Talk <[email protected]> >> Message-ID: <[email protected]> >> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes >> >> >> On Apr 3, 2010, at 9:34 AM, Daniel Israel wrote: >> >>> This may have been covered before... In most of my OS X apps, when >>> I am working with large amounts of text, selecting the end or >>> beginning of a line often behave oddly. >>> >>> For example, in dreamweaver, if I want to select to the end of the >>> line and include the EOL, it often selects the first character >>> (often a tab) on the next line. Or, when I click on the very >>> beginning of a line (like when I want to paste something there) it >>> does the same. Is this a setting, or just a bug? (The Windows >>> version of Dreamweaver doesn't do this.... and it's not just >>> Dreamweaver, but many applications...) >>> >>> It's mainly kind of annoying more than anything, but just wondering >>> if anybody had found some sort of fix/workaround for this? >> >> Usually, this is due to minor mousing aberrations. If you twitch your >> mouse even slightly up or down when doing this kind of selection, you >> will often get more than you bargained for. Also, sweeping the mouse >> leftwards past the beginning of line or rightwards past end of line >> can lead to the same behavior. I have found that some applications >> seem to be touchier than others in this regard and I end up doing more >> shift-clicking than usual to re-establish the desired boundary. >> >>> (It's not as bad as infernal Microsoft Office select whole words >>> (and whitespace) when I'm trying to select only a small part of the >>> word) >> >> Yes, Microsoft seems to think this is some kind of feature. I >> discovered that one can defeat this behavior by holding down the >> option or command key (I forget which it is, because I don't use Word >> all that often) as you are selecting, causing the selection range to >> stop jumping and work just like it does in every other Mac application. >> >> -- >> Macs R We -- Personal Macintosh Service and Support >> in the Wickenburg and far Northwest Valley Areas. >> http://macsrwe.com >> >> >> >> ------------------------------ >> >> Message: 2 >> Date: Sat, 03 Apr 2010 15:43:27 -0700 >> From: Kevin Callahan <[email protected]> >> Subject: Recording stopped because the maximum duration for the file >> has been reached >> To: MacOSX-talk Talk <[email protected]> >> Message-ID: <[email protected]> >> Content-Type: text/plain; charset="us-ascii" >> >> I've searched The Google for the "Recording stopped because the maximum >> duration for the file has been reached" error I'm getting when trying to >> capture video into QTPro 7 on Snow Leopard since the 10.6.3 update. The >> error appears the second I start the capture. >> >> Looks like this problem showed up in 2004,2005,2007,2008 ... and now in >> 2010. >> >> I posted a bug to RADAR. >> >> Wondering if someone can suggest an application that will allow me to >> capture video over HDMI (and via my Black Magic Pro Intensity card - using >> Apple Pro Res codec) while pulling audio in via my Apogee firewire audio >> interface. >> >> Black Magic has a video capture app, but it appears I have to run my audio >> out of my Apogee and resample it via the Intensity Pro card, which is >> something I don't want to do. >> >> Thanks >> Kevin >> >>> >> On Apr 1, 2010, at 2:58 PM, Kevin Callahan wrote: >> >>> Maybe not a QT7Pro 7 bug, but it's put me in a serious bind. Maybe >>> BlackMagic Intensity Pro driver needs update? >>> >>> As of the 10.6.3 update, I can no longer capture video over HDMI (via >>> IntensityPro card) into QTPro on my DUAL QUAD. >>> >>> "Recording stopped because the maximum duration for the file has been >>> reached". >> >>> Until 10.6.3, my video input source to QT7Pro has been my Canon HV20 over >>> HDMI into my Black Magic Intensity Pro capture card (which does Apple 422 >>> compression). >>> >>> For audio, I set QT7Pro to my Apogee DUET (or MOTU 896HD) over firewire. >>> On my DUAL QUAD, the syncing has been so good I haven't had to resync >>> the >>> audio to video when sweetening in Logic Studio. >>> >>> As of 10.6.3, now when I start a new video capture and hit spacebar to >>> start recording, IMMEDIATELY, a sheet slides out telling me I've reached >>> the end of the file - checking the file in the Finder, I see it wrote an >>> 8.3 MB file and quit. It doesn't record anything, of course. I've >>> changed my capture directory from my RAID to my local drive and that >>> didn't help. >>> >>> Normally, I've been recording 20-40 GB files and both audio and video >>> have >>> been in perfect sync. >>> >>> It's hard to know if it's a QT issue - as I can record just fine using my >>> Logitech 5000 webcam. >>> Of course, it's not capturing HD through my BMIP card. It's just via >>> HDMI >>> and my Black Magic Intensity Pro card. >>> >>> I've contacted BlackMagic about it .. but I thought I'd post it here to >>> see if anyone else has found similar issues. >>> I'm also about to post a bug to RADAR. >>> >>> Thanks, >>> Kevin >>> >> >> >> The Red Fantasy : >> http://www.dobermaneditions.com//en/sheet-music-for-guitar/guitar-solo/p17554733.html >> The Fourth Stream: >> http://www.dobermaneditions.com//en/sheet-music-for-guitar/guitar-solo/p17554731.html >> Three River Moments: >> http://www.henry-lemoine.com/en/catalogue/rechercheFiche.html?cotage=27461 >> Accessorizer: >> http://www.kevincallahan.org/software/accessorizer.html >> Homepage: http://www.kevincallahan.org/ >> http://www.xeniamara.com >> >> >> >> >> >> >> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> /mailman/archive/macosx-talk/attachments/20100403/0d83ed4b/attachment-0001.html >> >> ------------------------------ >> >> Message: 3 >> Date: Sat, 3 Apr 2010 22:23:14 -0400 >> From: Neil Laubenthal <[email protected]> >> Subject: Re: Syncing Twitter Clients >> To: Jared Earle <[email protected]> >> Cc: MacOSX-talk Talk <[email protected]> >> Message-ID: <[email protected]> >> Content-Type: text/plain; charset=us-ascii >> >> Thanks . . .that was what I concluded as well. I'm surprised that with the >> mixed platforms we use these days that individual apps don't sync between >> say Twitteriffic for iPhone, iPad, and Mac. >> >> >> On Apr 3, 2010, at 12:37 PM, Jared Earle wrote: >> >>> >>> This is not something that Twitter manages; you need to somehow sync the >>> clients, and I'm not aware of a solution for this. >> >> ----------------------------------------------- >> There are only three kinds of stress; your basic nuclear stress, cooking >> stress, and A$$hole stress. The key to their relationship is Jello. >> >> neil >> >> >> >> >> >> ------------------------------ >> >> Message: 4 >> Date: Sun, 4 Apr 2010 09:45:38 -0600 >> From: LuKreme <[email protected]> >> Subject: Re: Syncing Twitter Clients >> To: [email protected] >> Message-ID: <[email protected]> >> Content-Type: text/plain; charset=us-ascii >> >> On 3-Apr-2010, at 10:14, Neil Laubenthal wrote: >>> >>> So . . .how does one synchronize your unread tweets between your MBP, >>> iPhone, and soon to arrive iPad? I haven't figured out a way . . .but >>> then >>> I'm not heavy duty twitter user so maybe I just missed it. >> >> Well, this exposes one of the 'faults' of twitter (I put faults in quotes >> because I don't think it is a fault). >> >> Twitter is a stream of data. It is not part of the design ethos that every >> tweet be read. >> >> -- >> By the way, I think you might be the prettiest girl I've ever seen outside >> the >> pages of a really filthy magazine >> >> >> >> ------------------------------ >> >> Message: 5 >> Date: Sun, 4 Apr 2010 09:09:03 -0700 >> From: Scot Hacker <[email protected]> >> Subject: Re: Syncing Twitter Clients >> To: MacOSX-Talk Talk <[email protected]> >> Message-ID: <[email protected]> >> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes >> >> >> On Apr 4, 2010, at 8:45 AM, LuKreme wrote: >> >>> Twitter is a stream of data. It is not part of the design ethos that >>> every tweet be read. >> >> Exactly. You choose to "sip, dip, or bathe" in the stream when you >> have a few free moments. Take a random sampling from the river when >> the mood strikes. It's not email, for goodness sake. I can't see any >> utility at all in being able to "sync" anything with Twitter. >> >> ./s >> >> >> >> >> >> >> ------------------------------ >> >> _______________________________________________ >> MacOSX-talk mailing list >> [email protected] >> http://www.omnigroup.com/mailman/listinfo/macosx-talk >> >> >> End of MacOSX-talk Digest, Vol 59, Issue 4 >> ****************************************** >> > _______________________________________________ > MacOSX-talk mailing list > [email protected] > http://www.omnigroup.com/mailman/listinfo/macosx-talk >
-- Best Regards, John Musbach _______________________________________________ MacOSX-talk mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-talk
