Hmm I'm running in 32 bit mode. so hopefully the say command will work for me this semester. It'd better. Maybe try running your os in 32 but mode by holding the numbers 3 and 2 both at power up. I really don't know if this will work, but it could not hurt to try. right?
Tc all and be blessed. On Jul 24, 2013, at 5:21 PM, Esther <[email protected]> wrote: > Hello Gena, Sarah, and Others, > > The default output file format for the "say" command is AIFF, which is the > Mac equivalent of WAVE, and using lower case still will not work. An AIFF > file is the default audio format you get on a Mac when you import an audio CD > with no compression. It may be the fact that by default we're running 64-bit > operating systems on the newer Intel Macs that impacts how some system > utilities that used to work in earlier versions of Mac OS X now operate. > (This might explain why the man page descriptions of the "say" command are > not necessarily accurate in this instance -- by default, earlier operating > systems ran under a 32-bit architecture.) > > As for the error code, it shows up as an invalid property value under the > Apple Developer documents for Audio Unit Component Services.. > kAudioUnitErr_InvalidPropertyValue > > This URL will probably wrap, but here's the source, and 10851 is listed under > the Result Codes. Also, this documents core audio codes under iOS. Apple is > in the process of merging functionality of OS X with iOS. > <http://developer.apple.com/library/ios/#documentation/AudioUnit/Reference/AUComponentServicesReference/Reference/reference.html> > > One of the reasons that mp3 and wave formats might not now be legitimate > products of the "say" command, is that since Tiger (OS X 10.3, the first to > support VoiceOver) Apple started to completely overhaul their Core Audio > format. Many audio files actually have the structure of video files with > just the audio components. They also wanted the audio formats to be written > to new standards that were not limited by the older file format definitions. > MP3 file standards were established a long time ago, and nobody thought that > you'd want to listen to single files that were longer than 13 hours (e.g. > audiobooks). The system sound files all have .caf extensions (standing for > "core audio file"), and the time counters don't turn over at 2 billion > samples (basically, the maximum number that can be represented with a 32 bit > unsigned integer as a header keyword), so you could listen to audio content > with hundreds of hours (in theory) in a single file. > > This is all part of future-proofing the media standards. I don't think the > error code is permissions related. You could always try using old voices > like fred. He does sound a bit like a duck quacking when you speed him up, > but remains pretty intelligible at fairly high speaking rates. > > Most list users will probably prefer to create audio files of text using the > service menu option "Add to iTunes as a spoken track". For Gena, since she is > comfortable with the Terminal command line, using the "say" command is a > reasonable choice, and has some advantages: > 1. She's transferring the file to an Audio CD, so the default AIFF format of > the "say" command makes sense. Using the service menu option would create an > AAC file in her iTunes library, which is smaller if she wants to store and > listen to it on her computer, but which would take additional processing by > her system to compress the file, and is not necessary, since when she writes > the file out as an Audio CD she'd have to expand it again, anyway. > 2. If she uses the Terminal command line she can create the file as a > background process. Again, this uses less of her system's resources, and > will minimize instances of "busy" messages. > 3. She can set the speaking rate as an argument in her command. If she were > using the service menu option to create a spoken track in iTunes she would > have to edit the file to insert an embedded command to set the speaking rate > at the start of the file. (It would have the format of two left brackets, > followed by the word "rate", followed by a space, followed by a number like > "300" -- written without the quotation marks -- followed by two right > brackets.) > > Embedded speech commands let you do things like alter pitch or volume, change > speaking rates, speak acronyms letter by letter, or speak phone numbers digit > by digit, and a whole lot more. You can test them out with the "say" command > in Terminal by embedding them into phrases enclosed within quotation marks. > Some of them, like speaking rate, can alternatively be set as a "switch" in > the command (e.g., in Sarah's example, this would be the "- r 250"). > > Here are a few examples: > Here's the command to get Fred instead of Alex, speaking fast at slightly > boosted volume, with the "say" command. Open up Terminal, paste the string > in, and press "return" to hear the results: > say -v Fred "[[rate 400; volm +0.2]]Am I speaking too fast?" > Here's the say command for using a phone number, pronounced number by number, > with no change in speaking rate: > say "Please call me at [[nmbr LTRL]] 5551990 [[nmbr NORM]]." > > Read more about these from the Apple Developer documents at: > <http://developer.apple.com/documentation/UserExperience/Conceptual/SpeechSynthesisProgrammingGuide/index.html> > Embedded commands are described in the section titled "Techniques for > Customizing Synthesized Speech" > "Use Embedded Speech Commands to Fine-Tune > Spoken Output". > > HTH. Cheers, > > Esther > > On 23 Jul 2013, at 19:58, Sarah k Alawami wrote: > >> If i read that right you got m4a to work whereas I did notk but I normally >> start with .aiff as that's what I do work with and you can burn those to cd. >> Well let us know what you find with the error. and good luck. >> On Jul 23, 2013, at 8:24 PM, Georgina Joyce <[email protected]> wrote: >> >>> Hello, >>> >>> Well, it is an interesting one. Yes, if I had plunged straight in. It would >>> have worked. But as I like to start with the most simplest form then >>> expand. I crashed into this bug. I can't get the --file-format=WAVVE to >>> work but m4af does. That's interesting too. The inconsistency of the upper >>> case and lower case of the format options. I'll have to check to see if >>> wave will work if I enter it lower case. Usually man pages are accurate >>> regarding such issues. >>> >>> It all adds to the learning experience. So it looks like I'll be now >>> exploring how to write the file to a compact disk as an audio disk. To make >>> it easy on myself. I'll put all the documents in one file. Lucky for him, >>> there's only about 3 pages of text in total. >>> >>> BTW: I understand that there is an Apple support document that expands >>> error codes. So I might spend a little time in seeking the meaning of error >>> 10851. It's beginning to should like it's a typical Unix problem of >>> something not being given the correct privileges or permissions. >>> >>> Thanks to everyone who contributed. >>> >>> Gena >>> >>> Please Note: >>> Please use email address below for all future correspondence: >>> >>> [email protected] >>> >>> Georgina Joyce >>> Applied Psychologist >>> Training and Coaching. >>> Because individuals of groups matter! >>> >>> >>> On 23 Jul 2013, at 18:35, Esther <[email protected]> wrote: >>> >>>> Hi Sarah, >>>> >>>> I've seen queries to the Apple Discussion forums, reporting that error >>>> message comes up even if you don't designate an output file for the say >>>> command -- even if your command is: >>>> say hello >>>> with no output file arguments. It seems to be a bug in the latest update >>>> of Mountain Lion, and shows up when you use downloaded or updated voices >>>> as the default voice or for the voice argument. In some cases when you >>>> switch to another account the command works. But I think that in many of >>>> those cases the reason may be that these are test accounts, where they >>>> only have the standard voices available, or have not updated them. >>>> >>>> Cheers, >>>> >>>> Esther >>>> >>>> On 23 Jul 2013, at 07:20, Sarah k Alawami wrote: >>>> >>>>> I see that error when I try and do wave or mp3 or m4a files so try the >>>>> aiff files as I don't think Im getting the error with those. I have not >>>>> tried anything in 10.8.4 yet how ever as the fall semester has not >>>>> started. lol! >>>>> >>>>> Tc all and be blessed. >>>>> On Jul 23, 2013, at 10:00 AM, Esther <[email protected]> wrote: >>>>> >>>>>> Hi Gena, >>>>>> >>>>>> Sarah's answer should do what you want. You can do a short test file, >>>>>> and Quick Look it (with the space bar). Just out of curiosity, are you >>>>>> getting that error message only with voices that you downloaded and >>>>>> updated? Because I think that's a bug that has been reported in 10.8.4 >>>>>> (not just with the "say" command). Try using a different voice. I >>>>>> don't have any problems with the say command. I think that if you had >>>>>> tried your test in earlier versions of the OS, you wouldn't have gotten >>>>>> that error message. >>>>>> >>>>>> HTH. Cheers, >>>>>> >>>>>> Esther >>>>>> >>>>>> On 23 Jul 2013, at 06:31, Sarah k Alawami wrote: >>>>>> >>>>>>> Try this. Convert your file to text and then save it on your desk top. >>>>>>> Now copy the file to the clip board. >>>>>>> >>>>>>> 1. launch terminal >>>>>>> >>>>>>> 2 enter >>>>>>> >>>>>>> say -f (paste in file name here) --progress -voice tom -r 250 -o >>>>>>> filename.aiff >>>>>>> >>>>>>> You can change the voice but I personally use tom but you can use >>>>>>> samantha as well or any of the other voices that are on your mac. >>>>>>> On Jul 23, 2013, at 8:59 AM, Georgina Joyce <[email protected]> wrote: >>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> Yes, coming from a linux background I need to get some information >>>>>>>> over to a blind friend who doesn't like or use computers. Therefore, >>>>>>>> simply passing a text file through say should give me an audio version >>>>>>>> of the text. Which can be then burnt to disk and he can play it. >>>>>>>> >>>>>>>> But I'm getting the error: >>>>>>>> >>>>>>>> MTBEAudioUnitSoundOutput::PropagateProperty Error -10851 >>>>>>>> MTBEAudioUnitSoundOutput::PropagateProperty Error -10851 >>>>>>>> >>>>>>>> Hence my question. Should have mentioned using 2013 13" MacBook Pro >>>>>>>> running ML. >>>>>>>> >>>>>>>> Gena >>>>>>>> >>>>>>>> Please Note: >>>>>>>> Please use email address below for all future correspondence: >>>>>>>> >>>>>>>> [email protected] >>>>>>>> >>>>>>>> Georgina Joyce >>>>>>>> Applied Psychologist >>>>>>>> Training and Coaching. >>>>>>>> Because individuals of groups matter! >>>>>>>> >>>>>>>> >>>>>>>> On 22 Jul 2013, at 22:09, Esther <[email protected]> wrote: >>>>>>>> >>>>>>>>> Hi All, >>>>>>>>> >>>>>>>>> I could be wrong about this, but I think that Gena is asking about >>>>>>>>> using the say command in the Terminal environment, since she's coming >>>>>>>>> from a linux background with command line use. Gena, welcome to the >>>>>>>>> mac-access list >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> >>>>>>>>> Esther >>>>>>>>> >>>>>>>>> On 22 Jul 2013, at 11:00, Sarah k Alawami wrote: >>>>>>>>> >>>>>>>>>> Oh that say command. Um? Sorry. I guess lunch is getting to me. I >>>>>>>>>> thought you guys meant vo a for the say all command. Excuse me >>>>>>>>>> while I go and melt lol! >>>>>>>>>> >>>>>>>>>> I love the terminal say command and use it to convert text files to >>>>>>>>>> speech for university or my own pleasure. Mainly for university for >>>>>>>>>> now. lol! >>>>>>>>>> >>>>>>>>>> Tc. >>>>>>>>>> On Jul 22, 2013, at 1:46 PM, Esther <[email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> Hello Gena, >>>>>>>>>>> >>>>>>>>>>> Since I know you have a background in command line usage, I'll just >>>>>>>>>>> mention that you can use the say command in combination with >>>>>>>>>>> switches for voice selection and also include any embedded commands >>>>>>>>>>> for speech rate, volume, etc. (all of these four-letter embedded >>>>>>>>>>> commands that are enclosed within two left brackets at the start, >>>>>>>>>>> and two right brackets at the end, and separated by semi-colons), >>>>>>>>>>> within quotation marks. >>>>>>>>>>> >>>>>>>>>>> You can search the Mail Archive for this list (link given as the >>>>>>>>>>> public archive at the bottom of each post) for threads like "adding >>>>>>>>>>> spoken tracks to iTunes", and "Text to Speech parameters" for >>>>>>>>>>> details. Sarah like to send the output of the say command to a >>>>>>>>>>> file from the command line, in preference to using the services >>>>>>>>>>> option of "Add to iTunes as a spoken track", so she can run this >>>>>>>>>>> separately in background. >>>>>>>>>>> >>>>>>>>>>> HTH. Cheers, >>>>>>>>>>> >>>>>>>>>>> Esther >>>>>>>>>>> >>>>>>>>>>> On 22 Jul 2013, at 10:33, Anne Robertson wrote: >>>>>>>>>>> >>>>>>>>>>>> Hello Gena, >>>>>>>>>>>> >>>>>>>>>>>> Yes, I've used the Say command with VoiceOver. I have it set to >>>>>>>>>>>> Cmd-F9 and I just tested it with your message. >>>>>>>>>>>> >>>>>>>>>>>> Cheers, >>>>>>>>>>>> >>>>>>>>>>>> Anne >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On 22 Jul 2013, at 22:19, Georgina Joyce <[email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hello All, >>>>>>>>>>>>> >>>>>>>>>>>>> I wondered if anyone had successfully used the say command while >>>>>>>>>>>>> using VoiceOver? >>>>>>>>>>>>> >>>>>>>>>>>>> Thanks. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Gena >>>>>>>>>>>>> >>>>>>>>>>>>> Please Note: >>>>>>>>>>>>> Please use email address below for all future correspondence: >>>>>>>>>>>>> >>>>>>>>>>>>> [email protected] >>>>>>>>>>>>> >>>>>>>>>>>>> Georgina Joyce >>>>>>>>>>>>> Applied Psychologist >>>>>>>>>>>>> Training and Coaching. >>>>>>>>>>>>> Because individuals of groups matter! >>>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>> > > <--- Mac Access At Mac Access Dot Net ---> > > To reply to this post, please address your message to > [email protected] > > You can find an archive of all messages posted to the Mac-Access forum at > either the list's own dedicated web archive: > <http://mail.tft-bbs.co.uk/pipermail/mac-access/index.html> > or at the public Mail Archive: > <http://www.mail-archive.com/[email protected]/>. > Subscribe to the list's RSS feed from: > <http://www.mail-archive.com/[email protected]/maillist.xml> > > As the Mac Access Dot Net administrators, we do our very best to ensure that > the Mac-Access E-Mal list remains malware, spyware, Trojan, virus and > worm-free. However, this should in no way replace your own security > strategy. We assume neither liability nor responsibility should something > unpredictable happen. > > Please remember to update your membership preferences periodically by > visiting the list website at: > <http://mail.tft-bbs.co.uk/mailman/listinfo/mac-access/options/> > <--- Mac Access At Mac Access Dot Net ---> To reply to this post, please address your message to [email protected] You can find an archive of all messages posted to the Mac-Access forum at either the list's own dedicated web archive: <http://mail.tft-bbs.co.uk/pipermail/mac-access/index.html> or at the public Mail Archive: <http://www.mail-archive.com/[email protected]/>. Subscribe to the list's RSS feed from: <http://www.mail-archive.com/[email protected]/maillist.xml> As the Mac Access Dot Net administrators, we do our very best to ensure that the Mac-Access E-Mal list remains malware, spyware, Trojan, virus and worm-free. However, this should in no way replace your own security strategy. We assume neither liability nor responsibility should something unpredictable happen. Please remember to update your membership preferences periodically by visiting the list website at: <http://mail.tft-bbs.co.uk/mailman/listinfo/mac-access/options/>
