-
Notifications
You must be signed in to change notification settings - Fork 103
preset nr missing in log. nr woul be helpful to debug missing graphics.. #85
Comments
does the image /tmp/win/pixelcontroller-distribution-2.1.0-RC2/data/pics/circle.jpg exist? |
no. the circle.jpg was request by an preset. i think, this filename comes from a default-preset an must be checked...but cant find out preset-nr. (by the way: this was not the reason for my stalled pixelmatrix. pixelcontroller is running perfectly 24/7 since months. i check it running and it is correctly sending data to my artnet client. i think the client stalls. because pixelcontroller outputs the data to an itead iboard 1.1, on which an art-net client-sketch is running. i think the board shows after a productive and errorfree year now sometimes temperatur problems... i will investigate that board) |
Seems like there is already a call to log this data: private synchronized void loadActivePreset(VisualState visualState) {
LOG.log(Level.INFO, "Load Preset ...");
visualState.setLoadingPresent(true);
// save current visual buffer
transitionManager = new TransitionManager(visualState);
// save current selections
int currentVisual = visualState.getCurrentVisual();
int currentOutput = visualState.getCurrentOutput();
List<String> presetToLoad = presetService.getActivePreset();
// load preset
long start = System.currentTimeMillis();
for (String s : presetToLoad) {
s = StringUtils.trim(s);
s = StringUtils.removeEnd(s, ";");
LOG.log(Level.FINEST, "LOAD PRESET: " + s);
this.processMsg(StringUtils.split(s, ' '), false, null);
}
} Line 770 in d1fda8a
|
i understand: you looked after this issue.... fantastic, but: |
The log level needs to be set to |
Ah. Edit
to:
|
hi, i have stalled pixelcontroller-images, which i wanted to debug.
i found warnings about missing graphics, but i cannot find the number of the preset in the log. only three dots [...]. is this by design? i would be helpful to see the preset-nr in the log to correct the preset-settings ...
my log:
The text was updated successfully, but these errors were encountered: