Having entered Start At/Loop Start/Loop End/Fade In/Fade Out values on sub-cues and then saving and closing as usual, when I go back to the edit screen they have all disappeared. Sometimes the [Reset] button is available and when I click, the values all come back again. Sometimes they've gone for good.
Has this been reported? Anyone else having the problem? Or is someone out to get me?
9.4.1 sub-cue problems (Fixed in 9.4.2)
-
- Site Admin
- Posts: 3629
- Joined: Sun Jul 24, 2005 8:58 am
- Location: Brisbane, Queensland, Australia. TZ:GMT+10
- Contact:
Hi Mike - Thanks for your prompt response (as usual).
Like you, I've had trouble reproducing this in a controlled way but it has happened again by accident this morning while doing some proper work.
I can think of nothing I did out of the ordinary but here are the current symptoms.
I have set up and saved a sub-cue (the first in a group of two) with a fade out type of Log. I later found it had reverted to the default of Linear. When I redisplayed the Edit screen, the [Reset] button was highlighted, I clicked it and the fade out type changed back to Log. If I subsequently sign out of SCS altogether and then restart, it has gone back to Linear, the [Reset] button is highlighted and we start all over again.
I've had a look at the .scs file itself (while SCS was closed) which seems to be correct:
<Filename>$(Cue)\RRGarden.wav</Filename>
<FadeOutTime>8000</FadeOutTime>
<FadeOutType>log</FadeOutType>
How can it be that when the .scs file says Log, it opens as Linear with the [Reset] button highlighted even though no change has been made?
I hope there are some clues in all that. I can send you the whole .scs file if it helps.
Like you, I've had trouble reproducing this in a controlled way but it has happened again by accident this morning while doing some proper work.
I can think of nothing I did out of the ordinary but here are the current symptoms.
I have set up and saved a sub-cue (the first in a group of two) with a fade out type of Log. I later found it had reverted to the default of Linear. When I redisplayed the Edit screen, the [Reset] button was highlighted, I clicked it and the fade out type changed back to Log. If I subsequently sign out of SCS altogether and then restart, it has gone back to Linear, the [Reset] button is highlighted and we start all over again.
I've had a look at the .scs file itself (while SCS was closed) which seems to be correct:
<Filename>$(Cue)\RRGarden.wav</Filename>
<FadeOutTime>8000</FadeOutTime>
<FadeOutType>log</FadeOutType>
How can it be that when the .scs file says Log, it opens as Linear with the [Reset] button highlighted even though no change has been made?
I hope there are some clues in all that. I can send you the whole .scs file if it helps.
Update
Found a circumvention that seems to work.
Opening any other SCS file and then re-opening the problem one clears the error.
I still think it needs to be fixed because if loading a show in a hurry you may not notice the problem. A log fade reverting to linear may not be a disaster but a looped sound file reverting to non-looped could be embarrassing.
Hope this helps.
Found a circumvention that seems to work.
Opening any other SCS file and then re-opening the problem one clears the error.
I still think it needs to be fixed because if loading a show in a hurry you may not notice the problem. A log fade reverting to linear may not be a disaster but a looped sound file reverting to non-looped could be embarrassing.
Hope this helps.
-
- Site Admin
- Posts: 3629
- Joined: Sun Jul 24, 2005 8:58 am
- Location: Brisbane, Queensland, Australia. TZ:GMT+10
- Contact:
OK, I've found the cause of the Log fades changing to Linear. This occurs only on the first audio file sub-cue displayed in the Editor during an SCS session. So if the first audio file sub-cue you display has linear fade-in and fade-outs and then you go to a sub-cue with log fade-in or fade-out then you don't get the error. You only get the error if log fades are used in the first sub-cue displayed.
I've emailed you details of a fixed version to download.
The loop start and loop end times being cleared may be due to the length of time it takes to display the graph. In that fixed version I've also changed the order in which information is displayed so that the loop start and end times, etc, are displayed before the graph is generated.
I've emailed you details of a fixed version to download.
The loop start and loop end times being cleared may be due to the length of time it takes to display the graph. In that fixed version I've also changed the order in which information is displayed so that the loop start and end times, etc, are displayed before the graph is generated.
-
- Site Admin
- Posts: 3629
- Joined: Sun Jul 24, 2005 8:58 am
- Location: Brisbane, Queensland, Australia. TZ:GMT+10
- Contact:
The problems raised here will be fixed in 9.4.2. The current list of changes for 9.4.2 is as follows:
- Minor change to the way the end of a MIDI file is detected during playback.
- Fixed an error associated with displaying the graph in the editor where the same audio file is used in multiple cues.
- Fixed an error associated with 'before end' auto-start cues where the controlling cue has both a loop and a fade-out time.
- Fixed an error in the editor that would set the fade type to 'Linear' for the first audio file sub-cue displayed, even if the saved fade type was 'Log'.
- Fixed an error that could cause an audio file sub-cue containing a loop to lose timing properties if the fade-in or fade-out time is greater than the file length (which is valid for a sub-cue containing a loop).