I am making a stack for reading audio clips, setting extracts of them and then saving the extracts as audio files.
This is done by piping the audio sound output to QuickTime 7 with SoundFlower under AppleScript control.
I am doing this with a Japanese AppleScript expert because I don`t know how.
When I send him the stack I have made with my commercial version LiveCode 6.5 he gets:
"There was a problem opening that stack: stack is corrupted ~ check for backup file"
He has the commercial version of LiveCode.
What`s going on, and what`s to be done?
OK on my computer, "corrupted" on his ???
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
-
- VIP Livecode Opensource Backer
- Posts: 5
- Joined: Sun Apr 14, 2013 4:33 am
- Contact:
Re: OK on my computer, "corrupted" on his ???
Hi Simon,
this can happen if your japanese partner uses a Livecode version below 5.5. The stack format changed. You could save your stack as and at the bottom is an option menu and you choose legacy LiveCode stack 2.7. That will save in the old format but looses any specific stuff that is LC 5.5 or beyond. The part that is covered by "older" LC versions is saved.
You miight also want to zip the file, just to make shure.
Kind regards
Bernd
this can happen if your japanese partner uses a Livecode version below 5.5. The stack format changed. You could save your stack as and at the bottom is an option menu and you choose legacy LiveCode stack 2.7. That will save in the old format but looses any specific stuff that is LC 5.5 or beyond. The part that is covered by "older" LC versions is saved.
You miight also want to zip the file, just to make shure.
Kind regards
Bernd
-
- VIP Livecode Opensource Backer
- Posts: 5
- Joined: Sun Apr 14, 2013 4:33 am
- Contact:
Re: OK on my computer, "corrupted" on his ???
Thanks for the feedback Bernd, actually he had a recent version of LiveCode.
I finally got the the bottom of this, the problem was caused by the language settings on my Japanese collaborator`s machine.
He wrote:
"I succeeded to open your LiveCode stack. LiveCode seems not to be able to open stacks under Japanese language environment any more... I changed "Language & Region" settings in System Preferences.app."
That`s worth knowing...
I finally got the the bottom of this, the problem was caused by the language settings on my Japanese collaborator`s machine.
He wrote:
"I succeeded to open your LiveCode stack. LiveCode seems not to be able to open stacks under Japanese language environment any more... I changed "Language & Region" settings in System Preferences.app."
That`s worth knowing...
Re: OK on my computer, "corrupted" on his ???
Hi Simon,
thanks for the feedback.
Good to know and you might want to bug-report it to
http://quality.runrev.com/
(registration required)
I would never have guessed it.
Kind regards
Bernd
thanks for the feedback.
Good to know and you might want to bug-report it to
http://quality.runrev.com/
(registration required)
I would never have guessed it.
Kind regards
Bernd
Re: OK on my computer, "corrupted" on his ???
..........
Last edited by [-hh] on Wed Aug 13, 2014 1:58 pm, edited 1 time in total.
shiftLock happens
-
- VIP Livecode Opensource Backer
- Posts: 5
- Joined: Sun Apr 14, 2013 4:33 am
- Contact:
Re: OK on my computer, "corrupted" on his ???
Some answers to your questions:
1. The stack has a plain non-Unicode name, its focus is just on running AppleScript scripts for the time being
2. The stack does not use Unicode 16 internally
3. I don`t know
4. I don`t know
The stack will include Unicode stuff at a later stage.
1. The stack has a plain non-Unicode name, its focus is just on running AppleScript scripts for the time being
2. The stack does not use Unicode 16 internally
3. I don`t know
4. I don`t know
The stack will include Unicode stuff at a later stage.