Rockbox Utility rbutlQt: Error generating voice files "Path to encoder is wrong"

[dmoriarty]

I am using the Accessibility Tab in the rbutilQt utility 1.0.3 and when I select "Create Talk Files" after selecting the drive of the player, it generates the error "Path to encoder is wrong".  There is no way to change the path to the encoder.  It says thet the encoder is "lame(default)" but you can't change it.  Also since the speex codec is now being used for voice files, this option may not work?

I am using the Windows version running on Windows XP Profesional SP2.

I was also unable to get autodetect to work at all.  Pressing the autodetect button did nothing.  There was no warning about it at all.  I was able to select the player manually.  The install has worked and even managed to keep my settings (screen colours and font sizes) after an upgrade!

Thank yuu very much for your attention.

Declan Moriarty.

[Llorean]

I'm not certain, but I don't believe support for rbspeexenc has been added yet.

[Domonoky]

To set the path to the lame encoder in rbutil, you have to use the configuration dialog. There is an option to change the path to your encoder. ( The Configuration dialog has Tabs. (not very accessible for the blinds at moment))

But unfortunatly i didnt found any time lately, to include the rbspeex encoder into rbutil. So the generated talk files wont work with a recent build of rockbox).

About the Autodetection: which player do you have ?

[dmoriarty]

Thank you very much for this.  I found the configuration option after I had posted it.  I was able to run the utitility successfully.  However as you mentioned in your post the .talk clips don't speak in the latest build.  I have since run the voicebox script ant all is well.

I have an iAUDIO X5.

I removed the rockbox-info.txt file and tried to autodetect.  It seemed to work correctly the second time?  Although I don't know if this is because it had detected the player before.  I am pretty sure that I didn't have any other USB devices installed at the time of the first autodetection but I can't now be sure.  It might be a good idea to remove/switch off all other USB devices before one tries autodetection?