Problems importing LIFT file (audio and images)
Lisa
I'm sorry if these questions have been addressed elsewhere. I haven't been able to locate answers searching through the list.
In addition to creating a dictionary app using DAB (which I referenced in an earlier post), I'm trying to make a transition from Lexique Pro to FLEx. We have been using Lexique Pro for many years now and our Talking Dictionary (available online and distributed on DVD as well) has over 1000 entries and over 5000 audio files. (Many entries have multiple audio files associated with them from different speakers representing different dialects.)
We have run into problems using the LIFT files exported from Lexique Pro in FLEx, and I'm hoping someone in this discussion group can help us troubleshoot them. I describe the problems below.
- We are able to export a LIFT file from Lexique Pro 3.6, but when I try to import that file into FLEx, I get an error message:
- When I was trying to troubleshoot the sound issue in DAB, Richard Margetts identified a problem with the export from Lexique Pro. DAB will only recognize audio entered as an alternate writing system in FLEx, not files entered in the audio field in Lexique Pro. To fix this problem, he suggested I search and replace code relating to audio files in the LIFT file itself. I changed the syntax in all lines referencing audio files to read:
<form lang="shh-audio"><text>filename.wav</text></form>
This did not completely solve my DAB problem. However, when I tried to import this edited LIFT file into FLEx, I was able to complete the import without any error messages. The resulting entries in the FLEx database have a field for the audio writing system, but they only have a record button (the circle) and don't reference the actual audio files. The names of the audio files are instead listed in the text of the entry:
I've read in the help file how to link an empty field to an existing .wav file, but it would be too time consuming to do this for each individual file. Is there a way to make this connection during the import of the LIFT file? Since our product is a Talking Dictionary, the sound files are vital. At this point, would it be better to stick with Lexique Pro than to switch over to FLEx?
- It looks like I'm also losing the images associated with the entries in Lexique Pro during the FLEx import. This is less of a concern than the audio files are, but I'm wondering if there is a way to preserve this information anyway.
Lisa
Beth-docs Bryson
On Oct 26, 2016, at 1:52 PM, Lisa <li...@metaserve.org> wrote:
I'm sorry if these questions have been addressed elsewhere. I haven't been able to locate answers searching through the list.In addition to creating a dictionary app using DAB (which I referenced in an earlier post), I'm trying to make a transition from Lexique Pro to FLEx. We have been using Lexique Pro for many years now and our Talking Dictionary (available online and distributed on DVD as well) has over 1000 entries and over 5000 audio files. (Many entries have multiple audio files associated with them from different speakers representing different dialects.)
We have run into problems using the LIFT files exported from Lexique Pro in FLEx, and I'm hoping someone in this discussion group can help us troubleshoot them. I describe the problems below.
- We are able to export a LIFT file from Lexique Pro 3.6, but when I try to import that file into FLEx, I get an error message:
<Auto Generated Inline Image 1.png>
- When I was trying to troubleshoot the sound issue in DAB, Richard Margetts identified a problem with the export from Lexique Pro. DAB will only recognize audio entered as an alternate writing system in FLEx, not files entered in the audio field in Lexique Pro. To fix this problem, he suggested I search and replace code relating to audio files in the LIFT file itself. I changed the syntax in all lines referencing audio files to read:
<form lang="shh-audio"><text>filename.wav</text></form>
This did not completely solve my DAB problem. However, when I tried to import this edited LIFT file into FLEx, I was able to complete the import without any error messages. The resulting entries in the FLEx database have a field for the audio writing system, but they only have a record button (the circle) and don't reference the actual audio files. The names of the audio files are instead listed in the text of the entry:
<Auto Generated Inline Image 2.png>
I've read in the help file how to link an empty field to an existing .wav file, but it would be too time consuming to do this for each individual file. Is there a way to make this connection during the import of the LIFT file? Since our product is a Talking Dictionary, the sound files are vital. At this point, would it be better to stick with Lexique Pro than to switch over to FLEx?
- It looks like I'm also losing the images associated with the entries in Lexique Pro during the FLEx import. This is less of a concern than the audio files are, but I'm wondering if there is a way to preserve this information anyway.
Lisa
--
You are subscribed to the publicly accessible group "FLEx list".
Only members can post but anyone can view messages on the website.
---
You received this message because you are subscribed to the Google Groups "FLEx list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flex-list+...@googlegroups.com.
To post to this group, send email to flex...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/flex-list/8b732a41-6168-43ff-b898-d52d767abb7b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
<Auto Generated Inline Image 1.png><Auto Generated Inline Image 2.png>
Mark Penny
BTW - I had similar issues earlier with trying to use LIFT files exported from LexiquePro in DAB. Not everything came across into DAB, so eventually I went to the FLEx database and exported that as LIFT and DAB was much happier - and so was I! Hopefully someone else can help you import your data into FLEx in a way that everything stays connected and nothing gets lost.
Regards
Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/flex-list/DB2F2DFB-CC7C-445B-9F14-FC24C9DD77E8%40sil.org.
For more options, visit https://groups.google.com/d/optout.
-- Perhaps one secret to a long life is just to have a late mid-life crisis. But for sure, the only secret to eternal life is an encounter with grace!
Lisa Johnson
Beth, thanks for forwarding the message to the right people. Hopefully they can help me work through these issues.
Mark, thanks for the suggestions. I tried the import to DAB 1.0, but that caused even bigger problems. The resulting app had no dictionary entries at all. Clearly there is something strange going on with this LIFT file. I’m glad to know that exporting from FLEx was more successful for you. It sounds like that’s probably my best bet as well. Fingers crossed!
Lisa
From: flex...@googlegroups.com [mailto:flex...@googlegroups.com]
On Behalf Of Mark Penny
Sent: Wednesday, October 26, 2016 7:44 PM
To: flex...@googlegroups.com
Cc: Flex Errors <Flex_...@sil.org>
Subject: Re: [FLEx] Problems importing LIFT file (audio and images)
Lisa, I'm not sure if this affects you or now, but I was recently made aware that there is a regression in DAB 1.2 - so that sound files are not working in Apps built with that version. My (temporary) fix was
to go back to DAB 1.0 and now the sound files work. [The developer knows about this, and I'm sure it will be fixed pretty soon.]
BTW - I had similar issues earlier with trying to use LIFT files exported from LexiquePro in DAB. Not everything came across into DAB, so eventually I went to the FLEx database and exported that as LIFT and DAB was much happier - and so was I! Hopefully someone
else can help you import your data into FLEx in a way that everything stays connected and nothing gets lost.
Regards
Mark
On 27-Oct-16 11:06 AM, Beth-docs Bryson wrote:
Lisa, I’m copying this to FLEx_...@sil.org. With problems like this, you are more likely to get better help from the developers and the FLEx Help Team than from users, since some of this has to do with changes that are needed in FLEx, or with modifications to database files.
If FLEx_...@sil.org doesn’t have specific advice that can help you, hopefully one of our technical support people can work on some workarounds with you.
And thank you for trying this out. If we can get this working well for you, it ought to serve others in the future.
-Beth
On Oct 26, 2016, at 1:52 PM, Lisa <li...@metaserve.org> wrote:
I'm sorry if these questions have been addressed elsewhere. I haven't been able to locate answers searching through the list.
In addition to creating a dictionary app using DAB (which I referenced in an earlier post), I'm trying to make a transition from Lexique Pro to FLEx. We have been using Lexique Pro for many years now and our Talking Dictionary (available online and distributed on DVD as well) has over 1000 entries and over 5000 audio files. (Many entries have multiple audio files associated with them from different speakers representing different dialects.)
We have run into problems using the LIFT files exported from Lexique Pro in FLEx, and I'm hoping someone in this discussion group can help us troubleshoot them. I describe the problems below.
1. We are able to export a LIFT file from Lexique Pro 3.6, but when I try to import that file into FLEx, I get an error message:
<Auto Generated Inline Image 1.png>
2. When I was trying to troubleshoot the sound issue in DAB, Richard Margetts identified a problem with the export from Lexique Pro. DAB will only recognize audio entered as an alternate writing system in FLEx, not files entered in the audio field in Lexique Pro. To fix this problem, he suggested I search and replace code relating to audio files in the LIFT file itself. I changed the syntax in all lines referencing audio files to read:
<form lang="shh-audio"><text>filename.wav</text></form>
This did not completely solve my DAB problem. However, when I tried to import this edited LIFT file into FLEx, I was able to complete the import without any error messages. The resulting entries in the FLEx database have a field for the audio writing system, but they only have a record button (the circle) and don't reference the actual audio files. The names of the audio files are instead listed in the text of the entry:
<Auto Generated Inline Image 2.png>
I've read in the help file how to link an empty field to an existing .wav file, but it would be too time consuming to do this for each individual file. Is there a way to make this connection during the import of the LIFT file? Since our product is a Talking Dictionary, the sound files are vital. At this point, would it be better to stick with Lexique Pro than to switch over to FLEx?
3. It looks like I'm also losing the images associated with the entries in Lexique Pro during the FLEx import. This is less of a concern than the audio files are, but I'm wondering if there is a way to preserve this information anyway.
Lisa
To view this discussion on the web visit https://groups.google.com/d/msgid/flex-list/58115BD0.3000109%40sil.org.