Thread: update issue

small problem with update...it locks up..i get a "object reference not set to an instance of an object" LSP 'loading hardware' no response

help

BTW: how do you re-install LSP? Where do you get the installer?

I just load it from the home screen, where it says free trial. Try closing the program before you update as well. I hope this works for you. George

I had to do a clean install. Uninstall, delete the graphxpros file and reinstall. Just remember to back up all sequences, music, and your xml files located in the sequencer folder in graphxpros. I have a LSPbackup folder I keep in my documents so when I do an update, I just copy and replace them back over.


animal

Just make sure not to copy the old lightshow.exe into the new directory like I did. doh!

Originally Posted by animal

I had to do a clean install. Uninstall, delete the graphxpros file and reinstall. Just remember to back up all sequences, music, and your xml files located in the sequencer folder in graphxpros. I have a LSPbackup folder I keep in my documents so when I do an update, I just copy and replace them back over.


animal

Hi Animal,

What do you mean by documents? xml files, config files?

You need to be carefull if doing that with config files especially as new items get added and old items can get deleted to/from that file. The latest example I can think of is the copy paste options now have 2 entries in the LightShowProSequencer.exe.config that were not there in prior releases. This might not be a major issue but others could be.

I keep a folder in my documents file labled LSP Controller backup Files. This is where I keep a copy of my Hardware layout xml, transition layout xml, user objects and patterns, etc etc. You can put it on your desktop if you want. I just put it there because my documents folder is diverted to a second hard drive and not the primary. Just something i do so I don't lose my documents in case of a primary failer. Saved me more than once. When I do a clean install, I can replace my configurations back to the sequence folder in graphxpros.

animal

Originally Posted by animal

I keep a folder in my documents file labled LSP Controller backup Files. This is where I keep a copy of my Hardware layout xml, transition layout xml, user objects and patterns, etc etc. You can put it on your desktop if you want. I just put it there because my documents folder is diverted to a second hard drive and not the primary. Just something i do so I don't lose my documents in case of a primary failer. Saved me more than once. When I do a clean install, I can replace my configurations back to the sequence folder in graphxpros.

animal

I agree completely and I do the same thing, I'm just suggesting you need to be careful with the config file, the hardwarelayout.xml, and the userhardware.xml. These files, at least, could be changed in the release and restoring over them could lose changes that were incorporated in the release.

So with every new release, we should not be copying our old usertransitions.xml and userhardware.xml to the new graphxpros directory?
For transitions especially, it's time consuming to reload all my custom avi transitions that I have created. They have to have the exact same name or else when you regenerate transitions on old sequences, it can not find the correct transition avi.
If this is the case, there needs to be an update utility that will pull the custom saved data from the old files into the new.
Controllers aren't too bad since you can export them all at once but if you have them organized into groups, that may not be fun either.

Originally Posted by n8huntsman

So with every new release, we should not be copying our old usertransitions.xml and userhardware.xml to the new graphxpros directory?
For transitions especially, it's time consuming to reload all my custom avi transitions that I have created. They have to have the exact same name or else when you regenerate transitions on old sequences, it can not find the correct transition avi.
If this is the case, there needs to be an update utility that will pull the custom saved data from the old files into the new.
Controllers aren't too bad since you can export them all at once but if you have them organized into groups, that may not be fun either.

Nope, not saying that.

I think that is fine with user transitions, user patterns, and user blends

For user hardware what I would suggest is an export from the library and then keep the exported file as it only contains controllers that were created by the user and then do an import after a clean install. Lets say that LSP adds a new controller to the Library and it is included in the release. By restoring the old hardware file, this controller would not be available to you.

If the user hardware and the hardware layout are not in sync according to the software, the LSP get it in sync by deleting inappropriate entries so you could lose controllers. This usually only happens if a user attempts to modify the files outside of the software.

For user objects, I would also suggest exporting(sharing) them and saving the exported file. If a new object like a "Ghost", "Pumpkin" or "Bat" is released by LSP and you restore your old ueser object file you would not have availability of the new object(s).

DJ or anyone else, please correct me if I am mistaken on my above descriptions or if they need further clarification.

Makes sense Mike. Never thought of it that way. I'll have to reinstall. I have exported my controllers. Thanks for the correction.


animal