Most of my speech output are simple text so I am using type: "PlainText" for my responses.
Is there a way to read out individual letters without resorting to SSML?
I tried "'I' 'D'" for Id but it didn't work.
Try these (they sound good to me in alexa en voices). Tested in https://developer.amazon.com/alexa/console/ask/test//en_US/: "Voice and tone".
ay,
bee,
see,
dee,
ee,
eff,
gee,
aitch,
aye,
jay,
kay,
el,
em,
en,
oh,
pee,
queue,
are,
ess,
tee,
ewe,
vee,
double u,
ex,
why,
zee
Related
I'm home sick and trying to view a worksheet my teacher posted to Canvas. The file is listed on Canvas as a .ks-ipc file, here's a link to it in Google Drive: https://drive.google.com/drive/folders/110hWYFenrT5Ymz5twMsEroS3zVCLi7jN?usp=sharing
The file seemed to contain a bunch of random characters, which I think may or may not be raw bytes according to my limited internet research? Here is what it said:
æ#z gÊ/ Èc| ZI> ♥ ☻ ýµ
☺▼Ïxœí]ol∟G§Ÿ=Û‰c'qâ$ý♥$]%¡
R←Çi„H♦¨ÆiÁRm§±)♣ ¢õÝÆY¸?fw/‰)↕◄¨B¨jÂ↨ª"!ñ…OHù‚„„ø H >ô‼â_)T¨)►J¨PZ’▬³swïnï2gßì¼Ý ›'|Þ }3û{¿7³óöÍ®A◘1→ÛÖÆßW☼‼2¼P]ò↔¿hï˜ ZüÄä±#‼ôïý“Ç>♦%†▬éá ³–ï:↨Íù§Ûµ|§Röàø–9«d?f-ÙÅAú«¹û¤å7vÓ_°{ô”í:•BíÀ¦úo846U(8TµU¬↔®µñ/Á ÍOØ®↨ì‡ö_§zfÊùbµ×ªìÜY«►vnkì¬WÖT°³±»UióÐöÆ¡Fµµý# º¯Ñj>n—♥eùÇ∟ÏÿÂ^º·~lm-h+™ž_¢•†‚ 2NfOÛVa¾\\ dù§w Q|sã/½ÄaÏ·\®Z2B¶↓)8® ¯ ýð‚SZ):gW☼›æ§\Ç·ÍýÕrÁ>ë”íÂ~ólÅ5í‹+®íÑöz¦ÎòM˵Íf™ÃPÑŽÒ™òŠ•·↨]Ë):ååË# ÷¬œñ|wºêù•ÒÉfÝÍFÞµrfé“ž}ÇñP“G♂¶—w §zà¾♠e aÓ*↨LJ7ת ◘pnýbÕöè♫ ÛU“°ñÌÕðÜJf▼¹¸òxã„Á ÐØX½ð–£ÿO}lúä#&Àe♠È\èÄë„iÖ ▬”Î◄òÜÜ☼J/ÏÞؕЃ♀…\f0d«]ùs§'oÏxs•²=vñœíÙkk´u„¼▲∟ß]´<¶RpÎ:v RqÑ)Õ
’{¬b±raúNMF¨Ðx©¦%_s¸♣ßò«^¸1F
’Q2← }n~éó =(·ŠÁv4Øèo;Ø~§lÔþW‚í3
Ÿ♫♫æ6(7▲•Õ’
ÎÙ▲l♂ÁÁ4΃KþNpùðÿ¡”t¼‼œ/ªã]†♫#´ÕÝÄuÊþ”7U].Ùeß.Ôý#è°àþ_L—É«c◘Ád„¡ƒ♥î°<↨ríúéC—zñ–ñF³DͲ† é ☻¤↑ž$è♣††<iÈATð☻Œ♫îôÇ‚,y " ƒh/h]»¨Ž[Ú♂2♠9ˆö☻<“è± k ƒh/¨K.}“ô›↨H 9HØ♂♠Hwi§←¸♦Ñ7ZuôèÛ3‼;~²úʕ׌6홈¾õÖQD · Ey↓±‰Ä‼*ãU↕—y;&•Œà<T°†‘¨pŒ¨¬~1Æî;ת’ÕY#™¢V↨¼T•¬Î→%¶µºà¥ªdõ„oÐ3|©*Y 0t(juÁK♣é´z71Ú~ÑmS¨¢ÑSne©h—▬WWl(C“$¶Î”V*nPñ£n¥´{¦∟Ì‹è∟é”kçb¾Z¬6skvͻβS¶Š'ùÒ*è¹ÛàÜéFäí ŸÖÊß™95ÝLI¡ç¼▬œs/œ³û¾S^ö▲¸Sùªã¯▲ì¸ân¨ ♫TÛ↑h›¯5ÜûšÑ*C'l{ɺ →h¶Õy2Œ<™]$Œe(O¦7‼ \Z↨]8¨ º•▬☻§²\s¶Zô ñõé¼yÁñÏ™5àó¶ÇDøÕ}]►^/‼‰☻↨=▬rß ¿üÓ¥7VŸ☻rƒd ▬↕)‼i”ô▬→aõô´,ÏhÑ↓w€(—,³Ï”îo¨ÝãD…¶#Ûˆ—♫,↔[↑:b¼Oês¸#Òf▼♠¶↑&aåGHÈ>Eà☻I›}↑PH g–ú> à☻Q }↑↔B▼±O☻¸#ÒfŸ,CIFîû¶ ♂„?ÆÖJ9↑$"Óì▼▲▼Üóé•Þ↑¤½æ♀L³{sP‘yuŽaÝ$æÕ↑Ì$œmÏHN#TH1àÀÐÁZC!aÿª◘\ i³☼#☼ ♥NÁ\¦¤Ø§◘\ i³ •#Ÿ♠œÃ♀↔↕²O◄¸#4ûê’‘‘W◄¸#ÒfŸ,CIFا◘\ ü©üPAü¹+½>Œ ?åN¶Ú±å¯|Ýh•◄Í_ ƒýœaÑC♫ËzfÚ ‡♣¢9 ¼§‘!ÔŽ0‼Ó·▼ì‚ézY+¶ªèá´Ñ+OþáÖôæIp↔ ♀„ÓbÍZ GÆh↓è×1Æ♣^↔C◘:0²V♠►Ú ±ò‡¥ƒc¬íÕì°E1;F#¶c•"♠ý V¬SÁ¸¹▬ñÆ·◄ ý{LOaxuì#Ðñ2µü6¹► 6½R¦•I»WÅxuü>¦¼¶^↔»◄®♣cŒ>Äh‡„½‚6½t¦•I»Wø3☻¶²Pã♠‚Ž♥♀³Ú+hÓKgz ´{♣Y♠Œ1„vPC‚☺£ßé¥ë§L♦“Pãß’ÜFbL.3Ò+hÓKgz►‘÷¢ÑÇ©ÑŸª|õéñ↔7þµû↨F›öL<UÁMRƒ↓Òˆ…˲üˆŠ♀í►LYHâé↓Fv•♠Tq=µ’å±R„Ε
Æm↨l$%8è÷”dˆéofèˆévGCŽ☻9HÚ^€‘€ù^♦81tdÄ♂4äÒy☺F§‚☺ç#ú&IÊ♂4äÒyÁ←’ÜdJ’¤¼#C. ↨♀Ï↑Qv L’¥;"E • {AŽt↨£í↨Ýâ_ËÑ=)=¹Õ← ûàêY«7V V↓ÑÕ←►„í¯µ♣∟ë5X†Ù½♠ìT Ó»ïøX¶yhªXü ‼Õ ”º º©ËŠ ¯ŒÔ◄Œþlổo>ÿ·Ñg¯æ:¬” g♂±®Øˆò©▬Z&êˆ÷Ž$1aŒG#↑í ü“xe‡ÈkuÖ8áÁ¢X♫☺RŒ←"‚ ♥ãQ♫¯↔zÕ D±Î‡ Ð;§áIHë‘©%×D…ãg◘V◄AÇ▼ŘÃ3‼Óp5%möaäæÀI÷e€}ŠÀ♣’6ûdq挰O◄¸#4ûêò€↑œýÆ>A¸#Òf▼ƃ§Œ°4Ë$↕²O◄¸#ø£çõä]→£+5¢•Ø&_↓¼ýf~mŸÑ¦=‼☺¶øß0Ì;7íœ‼G
…¼È☻#b↨×û\"x◘•´Ÿ´b¬↑¸Ž▬Œv∟►3♂O?¯!G ∟D♣/ Eǽb&É’↨È¢C►r►§¼#–Ž© ¼#◄ÈAÒö‚}Ú$I{ †:/À€S◄“$å♣→rÔ↑↕ ▼E !½ôío\ûç³·Þ͵iW(†Ôk¶•H¬‰7Ö↕Ž5↓ r$B½♥œõÆ•ªÂJ™áð‚¸ÌÂ{iXfÁ€¶#♦HÄÌ↕–´?6± q)¼:r◘:î↕ƒ”gˆÕp5%möa¬▼$◘:î◄ƒ3)ö)☻↨HÚìÛ) œï◄ƒ3)ö)☻↨HÚìÃ↑J0àÌHߧ◘\ *°o↑AÇëÉ¥Öh¸š↕õ½x4,BçýÑÃ"/þæûŸýåóç›♠☺Q&,"2¯æ} #”♣o"^€1ÿæM▼êu♫Ïá♣Y‰ ↓◘:X&‹ÐaPI{Șý¤H²^R á ¥◘\ i³☼á%€3)ö)☻↨HÚìÃHËfÝ;òêØ#♠gRìS♦.►§Ø' 3g‰}↕À♣¢ÙW↨Ö·x4ûâ‚♂D$TAçâÑC§sϼÿ[c3 ï2Ú´ëPEMèߨ) ÐN↕¡^Y>«‹‘F Ù{ØEÌ‚Ñé#Šñ WÁ¯↔óôó→r¶ÈA´↨à™D0ƪ½ qÈA´↨Ô♣ãy›àK´úÍ♂$€∟D♣/ÀXj. I²ä♣Š#♫¢½ .↕♀Ïýæ♣↕#♫Òé♣ݤu¬§C¢ Q£Ç f♠☼~ôò“W,ƒ´×Üw1¤pü•6↕ ◄↑/‘ňÿ↑◘íéàw↕p‼„ËÄ0Y\ï♫ŽÐ™PI{qí›◘♀¾▼☺RÖw2xu°↕Âb→V5ä( ƒ¤í♣ÿ‘Ä$↑ SF¼#C. ↨ÜD0ÉÁ˜àÄ0«„^ !—Î♂0²]÷Ç♦'¯Žÿ&↨hÐ £#♫¢‚↨ü)¦ç¹Ú♂T‡∟„?Ü♠§ÄÿÙÃõ¾í▬ÿ‡☼ Žë
ÿ♠m ▼>|Êh•‼ýða¿~¤¯‡O▼®gš
}¸M↔T▼삪yaÂœ*.ÛKA♂òfPÞö˜XÏNtÁ:·Î•◄)„Ñ£ìwø{c§þ¹↨è¾pä2♥QöX?ˆÈêãy‼(Ñdƒ´rp1¢¯q·}£ ;Xªl„¶F↑𨤠%?#ÄïCX)Û"6↕Å—ç▲Nc'çê
ŒÙÙ8‚Ž[↓ä¥ŠØ ¤ÍK♀Ÿß‚ £_ûKÙ°♥I›—↑÷8↑؆mœ§^ªˆ↔HÚ¼$◘¸Ä¥CB☻↨ˆÈ{´i³¢Ïíwñ›K?zßÓ☼↓↔5g`nŸì·Ø içÃ↔M¯3{‘„SƒðÑt„´, (BŽ♣Z↕ Ǹm
gær7¾W
U♣Çigž‡?BÀí→"V¾Í¸)í¹b–Â◄Ö•♀ô¨PäJÆX§‹\ Ó&½^ Kaø+◄ ´ÙB◄&óÜ&h–↕¢Yš♠KAÒîk…nCDlS³8û,Nª¯Õ,Õ,Õ}¾cèg▬+ß×j–ÀR►Ý×F©Xm▬_gA#%‹u_«Y?KAÒîk…È$b{!÷éyº§YLåZHa&ûZÍRÍRܾ6Gº‹Ñö‹nñ/ á_☺ ̲™ðÖ¹ µlæ²Ñ*'ºlF/ðˆ°˜f=ƒ½Ú o¡š÷笒½.K·7
a»¶ÉÁ£‡?x¶Ž
/Xçk↓∟; LN∟9>qô!óÈñ‼G œ86Ù´âBÊa'↔>e-Û♂Ηì\hçh#¡Àck°#‹ÿJ←►¸G làÈnÀ0ïáàœ«Á±_•œy)×:}lªì]◘ÚxÚ>o[E»►®o$¨ºR¬–Ê▲ñÿ>_Ä|
I first tried opening the .ks-ipc file, and my computer asked what program to try opening it in, so I selected Word. It gave me all the random characters splayed out across a few pages, which was unhelpful. I then looked up what a .ks-ipc file was to see if there were any programs that could open it, but I found absolutely nothing about the existence of that file type. As far as Google is concerned, it doesn't exist. So I thought, okay, maybe it's just a weird ipc file, whatever an ipc file is, because Google does seem to know what an ipc file is. I try opening it in an ipc file converter that allows you to open and view them online. It tells me there's no readable text because it's a binary file and spits out the same random characters Word did. Did some googling and came to the conclusion that the random characters might be raw bytes, so I tried putting them into a raw bytes to string (text?) converter, but I got a few errors and it wouldn't work. The first error was there's an uneven amount of hex characters, the second was that there was an invalid UTF-8, whatever that means. I have no idea what any of this means, and I'm hoping somebody here can help me figure out what's going on. Is there any way to figure out what this says, or did my instructor just screw up?
I wrote some text search with use Google App Engine search.
In SDK I tested such query on atom field:
u'tag:"wartości"'
In production I run the same query but it not works on same data.
How can I do unicode query on atom field?
Is it possible to use unicode in Google App Engine search?
We are aware of this issue and plan to fix ASAP. The fix that we're currently planning will require that the atom field value include exactly the same accent characters in order to match. Matches will continue to be case-insensitive. We expect that at least initially, values that use combining diacritical marks will be treated as different values than those using precomposed characters. We may revisit that decision depending on feedback, but it's the most straightforward fix on our end.
For more on the precomposed characters vs. combining diacritical marks, see this Wikipedia article:
http://en.wikipedia.org/wiki/Precomposed_character
Chris
It looks that I need translate AtomField values into new string and I need to translate queries too. This workaround will allow only Polish unicode search. I do not know tonkenization rules so I use 'q', 'x' to expand alphabet since not used in Polish.
# coding=utf-8
translate = {
u'ą': u'aq',
u'Ą': u'Aq',
u'ć': u'cq',
u'Ć': u'Cq',
u'ę': u'eq',
u'Ę': u'Eq',
u'ł': u'lq',
u'Ł': u'Lq',
u'ń': u'nq',
u'Ń': u'Nq',
u'ó': u'oq',
u'Ó': u'Oq',
u'ś': u'sq',
u'Ś': u'Sq',
u'ż': u'zx',
u'Ż': u'Zx',
u'ź': u'zq',
u'Ź': u'Zq',
}
import re
reTranslate = re.compile(u'(%s)' % u'|'.join(translate))
print reTranslate.pattern
test = u"""\
Właściwie prowadzona komunikacja wewnętrzna w firmie,\
zwłaszcza dużej czy posiadającej rozproszoną sieć oddziałów,\
może przynieść oszczędność czasu, a co za tym idzie, również pieniędzy."""
print reTranslate.sub(lambda match: translate[match.group(0)], test)
I Am currently working on a project where I want to have the SpeechSynthesizer speak a text. I also want a textblock to display the words as they are spoken. This is so you can read along if you don't understand the Speech Synthesizer.
So basically the problem is that i cant find a efficient way to append every letter to a text within a textbox right when its spoken by the Speech Synthesizer. So it looks like the Speech Synthesizer is typing along with what he is saying.
Example
If I would do this:
SpeechSynthesizer x = new SpeechSynthesizer();
x.SpeakAsync("Hello there");
I want the textbox text to write along as the words are spoken by the x (SpeechSynthesizer ). Something like this:
http://youtu.be/hx6JL7PsLrg?t=1m56s
As Eric mentioned, you have to use the SpeechSynthesizer.SpeakProgress event:
For Example:
var ss = new SpeechSynthesizer();
ss.SpeakProgress += (sender, args) => txtBox.Text += args.Text;
ss.Speak("Hello this is " + true);
This is kind of hacky (and isn't guaranteed to do letter-by-letter), but you could use the PhonemeReached event as a hint to display the next letter (and stop at word breaks) and then use the SpeakProgress event to generate the remaining letters in the word. If you're using SSML, you'll need to skip over markup, of course.
I am using Maya to do some procedural work, and I have a lot of textures that I need to load into Maya, and they all have transparencies (alpha channels). I would very much like to be able to automate this process. Using PyMEL, I can create my textures and hook them up to a shader, but the alpha doesn't set properly by default. There is an attribute in the psdFileTex node called "Alpha to Use", and it must be set to "Transparency" in order for my alpha channel to work. My question is this - how do I use PyMEL scripting to set the "Alpha to Use" attribute properly?
Here is the code I am using to set up my textures:
import pymel.core as pm
pm.shadingNode('lambert', asShader=True, name='myShader1')
pm.sets(renderable=True, noSurfaceShader=True, empty=True, name='myShader1SG')
pm.connectAttr('myShader1.outColor', 'myShader1SG.surfaceShader', f=True)
pm.shadingNode('psdFileTex', asTexture=True, name='myShader1PSD')
pm.connectAttr('myShader1PSD.outColor', 'myShader1.color')
pm.connectAttr('myShader1PSD.outTransparency', 'myShader1.transparency')
pm.setAttr('myShader1ColorPSD.fileTextureName', '<pathway>/myShader1_texture.psd', type='string')
If anyone can help me, I would really appreciate it.
Thanks
With any node, you can use listAttr() to get the available editable attributes. Run listAttr('myShaderPSD'), note in it's output, there will be two attributes called 'alpha' and 'alphaList'. Alpha, will return you the current selected alpha channel. AlphaList will return you however many alpha channels you have in your psd.
Example
pm.PyNode('myShader1PSD').alphaList.get()
# Result: [u'Alpha 1', u'Alpha 2'] #
If you know you'll only ever be using just the one alpha, or the first alpha channel, you can simply do this.
psdShader = pm.PyNode('myShader1PSD')
alphaList = psdShader.alphaList.get()
if (len(alphaList) > 0):
psdShader.alpha.set(alphaList[0])
else:
// No alpha channel
pass
Remember that lists start iterating from 0, so our first alpha channel will be located at position 0.
Additionally and unrelated, while you're still using derivative commands of the maya.core converted for Pymel, there's still some commands you can use to help make your code read nicer.
pm.setAttr('myShader1ColorPSD.fileTextureName', '<pathway>/myShader1_texture.psd', type='string')
We can convert this to pymel like so:
pm.PyNode('myShader1ColorPSD').fileTextureName.set('<pathway>/myShader1_texture.psd')
And:
pm.connectAttr('myShader1PSD.outColor', 'myShader1.color')
Can be converted to:
pm.connect('myShader1PSD.outColor', 'myShader1.color')
While they may only be small changes, it reads just the little bit nicer, and it's native PyMel.
Anyway, I hope I have helped you!
I have a "Microsoft wedge mobile keyboard". It changes the Function key to play, mute, search, share, etc... I cannot find any driver or programs for this keyboard.
Can I change it back to normal function key instead?
http://www.autohotkey.com/
With this script, work for me!
Media_Play_Pause::F1
Volume_Mute::F2
Volume_Down::F3
Volume_Up::F4
<+#F21::F5
<!<#F21::F6
<^<#F21::F7
<#F21::F8
PrintScreen::F9
Home::F10
End::F11
PgUp::F12
F1::Media_Play_Pause
F2::Volume_Mute
F3::Volume_Down
F4::Volume_Up
F5::<+#F21
F6::<!<#F21
F7::<^<#F21
F8::<#F21
F9::PrintScreen
F10::Home
F11::End
F12::PgUp
Reply from MVP, they said it is hardware function, which means it cannot be changed. It is not for a programmer to use it. :(