reorganized file system

this one works – and provides verbosity at the asterisk CLE

a slight modification in the call to tts_callback adding the ‘o’ option will locate the output file where it is wanted

the connection between app_jack and PD both input and output appears to work and the quality is fine – the python script to send midi data to PD has stopped working from the command line at the moment – banging the readsf below will play the file through the handset and the handset audio come into PD – ignore the midi trigger

much to my amazement this code worked – connecting an asterisk I/O channel to Pd I/O channels

My new solution to exercising more control over the playback of audio to the different kiosk channels is to pass playback of the cereproc rendered file over to PD and then route it through app_jack to the handset rather than rendering it directly through Asterisk playback – the first few lines of code are: once the jack channel is available then pd can play the wav file created by cereproc

Alistair’s mere presence caused a break-though – here is the dialplan exten => 300,1,Answer() ;exten => 300,2,MusicOnHold() exten => 300,n,JACK() exten => 300,n,Set(JACK_HOOK(manipulate)=on) ;END OF EXTENSIONS.CONF —————————————————

Today I discovered the perils of a disorganised file system. The tts_callback routine in the cereproc python examples folder has undergone a certain amount of hacking by me. It is creating a file ‘cue1.txt’ that contains timing data gleaned from the xml file relating to marker files. I believed it was modifying a file in my home directory – it wasn’t it was modifying a file in the root directory.

managed to get Asterisk to call tts_callback and cereproc chris to speak – here is the dialplan code

None of these worked I checked that the jack module had been installed – change to astrisk src directory and make menuselect -it was installed correctly