SuperStarResponse.lid used by other process

[Brad Stucky]

Can anyone tell me why I'm getting this error when trying to enter a SuperStar sequence into a motion effects row.

"The process cannot access the file 'C:\Users\Brad\Documents\Light-O-Rama\LORInternal\SuperStarResponse.lid' because it is being used by another process."

I've been having this problem occasionally since about version 5.5.0. or maybe earlier, and I thought it had to do with having 2 copies of Superstar open, one within the sequence editor and one outside.  Up till now, I always seemed to be able to fix the situation, but now it seems to be happening when only accessing SuperStar within the Sequence editor.

I open the Sequence Editor.  Go to 96 x 42 vertical matrix.  select entire motion effect row, Insert Superstar sequence.  I open an older SuperStar sequence for a 64 x 42 vertical matrix.  I resize for 96 x 42 matrix, save to a new file, close and when data is trying to insert into the sequence, that is when I get this error.  Could this be a license issue?   96 x 42 is 4032 pixels and my SuperStar License is for 4000.  I do have several sequences that have accepted this slight over-license situation.

I deleted the created SS file associated for the 96 x 42 matrix motion effects row,  opened SuperStar again for that motion effects row, entered one smooth effect, and exited.  I still get the same error.

I've verified that I can go into other sequences and do the same thing and the SuperStar file will save and be entered, so it seems to be associated with at least this one particular song sequence.

 

[k6ccc]

I think I follow what you are trying to do.  That is similar to what I spent A LOT of time doing this year.  I had previous S4 SuperStar sequences that I was converting to "Insert SuperStar Effects" in S5.  Sounds like you are doing the same thing.  My conversion process was a bit different.  Rather than your step by step, my process was to open one copy of SuperStar directly (outside of the S5 Sequencer), and open my S4 sequence there.  Then in the S5 Sequencer, select whatever time interval and Motion Effects Row, and select "Insert SuperStar Effects" - which of course opens a second instance of SuperStar.  Then I copied the desired effects from the stand-alone instance of SuperStar and pasted them into the Sequencer initiated instance of SuperStar.  Then adjust anything as needed (which in my case was almost every effect because I was going from a 24 to a 26 string Pixel Tree - among other changes).  Then exit the Sequencer initiated instance of SuperStar.  Worked every time.

46 minutes ago, Brad Stucky said:

Could this be a license issue?   96 x 42 is 4032 pixels and my SuperStar License is for 4000.  I do have several sequences that have accepted this slight over-license situation.

I don't think so.  If that was the case, you would have gotten an error in SuperStar.  Also note that several of the SuperStar license levels will allow a slightly larger number of channels.  I don't know if that is one of those levels (that is the same one I have.

 

[Brad Stucky]

You got it Jim.   That is exactly what I was doing last year and it seemed to work fine except for the orientation problem I was having in converting data from a horizontal matrix to a new vertical matrix added for this year.   Brian added the change orientation item in the Tools earlier in the year to accommodate that and now it's much easier to orientate and scale effects from one prop to another.

I do seem to remember something about a little tolerance in the licensing for SuperStar.

 

As for the SuperStarResponse.lid error,  I just tried again, and this time I didn't save before exiting SuperStar.  The save prompt came up like usual just before it would display the error, but this time there was no error and the data was inserted.  What in the world?   I double-clicked on the motion effect row again, opening Superstar,  made a slight edit change, save the file and then exited.  Now I'm back to that error again.   I went back in again, made a small edit, and exited without saving first, and following the automatic save window, the error is now back.  It appears I can no longer make changes to that Superstar sequence.    Hmmmmmm!!!!!!

 

Edited October 22, 2020 by Brad Stucky

[BrianBruderer]

It is not a license issue. For what it is worth, for the 16CCR license and above it actually allows one more CCR than the license level.

As for the "The process cannot access the file" error you are getting, I'm not sure why it is happening. It is behaving as if superstar didn't let go of the file after passing it to the sequencer. 

[Brad Stucky]

1 hour ago, BrianBruderer said:

It is not a license issue. For what it is worth, for the 16CCR license and above it actually allows one more CCR than the license level.

As for the "The process cannot access the file" error you are getting, I'm not sure why it is happening. It is behaving as if superstar didn't let go of the file after passing it to the sequencer. 

Thanks, Brian.  I've seen this error several times but could never find a pattern to it.   Somehow I just managed to get the file saved.   Similar to what you described,  I likened it to 2 runners, each trying to make the finish line before the other does but most of the time the "ERROR" lost and the "DATA" came through.  It seems to be selective about it's "races", though.  This particular file size is about 1.5 meg, but it is one of the few that has NO images.     I'll keep plugging at it to see if there is a pattern.

[BrianBruderer]

Hmmm. One theory is that because of the large file size it takes time for the file to get written out and the file doesn't close before things are passed to the Sequencer. I save the file and then close down superstar but maybe the operating system saves the file in a separate thread. I will look to see if there is a way in the program to wait until the file has finished saving.

 

[Brad Stucky]

12 hours ago, BrianBruderer said:

Hmmm. One theory is that because of the large file size it takes time for the file to get written out and the file doesn't close before things are passed to the Sequencer. I save the file and then close down superstar but maybe the operating system saves the file in a separate thread. I will look to see if there is a way in the program to wait until the file has finished saving.

 

I thought of another possibility.  I have a Western Digital MyCloud drive that backs/syncs up My Documents from this computer.  I regularly get a notification from the WD software that says it can't sync up LORSequencer-trace.txt and will try again later.  Could that be the issue when trying to sync up the .sup file?  I will turn it off and see what happens.

[BrianBruderer]

That is a definite possibility. After turning off that feature let me know if the problem goes away.

[Brad Stucky]

5 minutes ago, BrianBruderer said:

That is a definite possibility. After turning off that feature let me know if the problem goes away.

Sure will.   So far this morning, the error hasn't shown up and I've worked on several sequences.  I'll be working on it most of the day and then report back.

[Brad Stucky]

8 hours ago, BrianBruderer said:

That is a definite possibility. After turning off that feature let me know if the problem goes away.

At the end of the day now and the error never showed up again.    I will still save before exiting, though, and when I'm done for the day, I'll just restart the WD sync software and wait for it to finish syncing before shutting down for the day.

          Thank you, Brian.

[BrianBruderer]

Sounds good.