I guess this is because of the 1.12 update we did. We changed the way the eSampler deals with clips longer than 2 minutes. Before 1.12 the eSampler wouldn’t allow you to load a video longer than 2 minutes and crop the video automatically (cut the rest off). Upon request we changed that. Now you can load videos longer than two minutes, but the eSampler will discard the audio to avoid RAM issues. So now you can use videos of any length in the eSampler, but without audio. The eSampler will not show the waveform anymore in that case, but the lines. The lines are there for reference when you are editing the startpoint, because you still need to do that in the display eventhough there is nothing to display (no audio).
I guess that when you made the set you were using videos that were automatically cropped and now (since version 1.12) are loaded full length and the sound is discarded.
Quick fix (probably): drag the file name in the display (see pic below) into an empty clipslot on an audio track in Session View with the eClips plug-in loaded. Set the end point at exactly 2 minutes. Drag the clip back into the eSampler (overwriting the file you dragged into the clipslot). Now the eSampler will not discard the sound. The start point and other settings should still be intact, so you should have your original chop back. You’ll have to do that for each sample. Annoying for you, sorry about that. But if you used the same source video multiple times you can just drag the same clip (that you just manually cropped) into those eSamplers. On Monday I check with the team if we can improve this in the upcoming update (should be very soon).
About: “The video actually plays if I hit the pad but the “slices” are now in the wrong place.”:
Since the Start point is stored relative to the file length, the original start point setting will have a different effect on the full length video. When the videos are 2 minutes (using the procedure above) the start point should be the same as the original.
Does all of this make sense? We want EboSuite to be backwards compatible as much as possible when we release an update, but apparently we didnt take your case into account. Sorry about that!