jeffl Posted September 4, 2010 Share Posted September 4, 2010 I'm building a new Windows 7 show PC. After I moved my sequence folder now none of my windows commands show in the sequence. I have verified the cmdmap.lcm file exists, keys are same and sequences and cmdmap.lcm file are in the sequences folder. I'm puzzled.The other crazy part is I then added a command to a sequence and noticed it stayed in the sequence but my cmdmap file does not get updated. Where could it be saving this information?I will admit I changed the AudioPath, ClipboardPath, NonAudioPath,UserDataPath and VisulizationsPath after installing because I didn't like the path it was in.I am running 2.8.10. Link to comment Share on other sites More sharing options...
ItsMeBobO Posted September 4, 2010 Share Posted September 4, 2010 Run the verifier and it may help you figure this out.You can see your LOR folders using REGEDIT hereHKEY_CURRENT_USERSoftwareLight-O-Ramacmdmap.lcm is stored in "NonAudioPath" folder. Link to comment Share on other sites More sharing options...
jeffl Posted September 4, 2010 Author Share Posted September 4, 2010 Yep. I ran the verify already. I'll do it again. I may need to re-install if I can't get it. Link to comment Share on other sites More sharing options...
jeffl Posted September 4, 2010 Author Share Posted September 4, 2010 I found the problem. After seeing that I could save commands, and they would stay. I noticed the cmdmap.lcm file was not getting updated.I did the same thing and noticed that a file called SequencesCmdMap.lcm in the Light-o-rama folder was being updated.I think I found a change that may need to be updated in the help file. Link to comment Share on other sites More sharing options...
bob Posted September 7, 2010 Share Posted September 7, 2010 Wait a minute, you're saying that when you change a sequence's shell command, a file called "SequencesCmdMap.lcm" gets updated?And cmdmap.lcm does not? Link to comment Share on other sites More sharing options...
jeffl Posted September 7, 2010 Author Share Posted September 7, 2010 Correct. The file is called SequencesCmdMap.lcm and it's in the Light-o-rama folder instead of Sequences. After I copied my cmdmap.lcm file in this location with SequencesCmdMap.lcm file name all my commands show up in my Sequence files. I haven't tested to see if they actually run however. Link to comment Share on other sites More sharing options...
bob Posted September 7, 2010 Share Posted September 7, 2010 That's very strange.Could you please send me (bob@lightorama.com) a copy of the output of the LOR Diagnostic utility? You can run that from the "Light-O-Rama" folder in your computer's Start menu. Thanks. Link to comment Share on other sites More sharing options...
jeffl Posted September 7, 2010 Author Share Posted September 7, 2010 I'll do that when I get home from work. It just saves to a text file correct? I do know it's about 7K lines. Link to comment Share on other sites More sharing options...
bob Posted September 7, 2010 Share Posted September 7, 2010 It is textual, yes. Link to comment Share on other sites More sharing options...
jeffl Posted September 7, 2010 Author Share Posted September 7, 2010 I sent the files. I also tested a new sequence on a new machine and it works as expected in the cmdmap.lcm file. Link to comment Share on other sites More sharing options...
jeffl Posted September 7, 2010 Author Share Posted September 7, 2010 As I could not sleep tonight it came to me what the problem could be. I missed the "" at the end of the NonAudioPath when I changed the registry values.I had this:C:ShowFilesLight-O-RamaSequencesIt should be this:C:ShowFilesLight-O-RamaSequencesMy guess is the code is taking NonAudioPath + 'cmdmap.lcm' as the filename and in my case coming up with Sequencescmdmap.lcm.I believe in the end, "I" am the problem. Back in my windows coding days we checked for the trailing "" on directory names. It might be useful when you have users/hackers like me.Sorry for the wild goose chase. Link to comment Share on other sites More sharing options...
bob Posted September 8, 2010 Share Posted September 8, 2010 Thanks. This will be fixed in the next release. Link to comment Share on other sites More sharing options...
Recommended Posts