0.9.9 bugs

Bug reports
1

Various bugs I’ve encountered - I’m on Windows, Build 9. From what I recall there’s a repo for bug reports but I couldn’t find it :man_shrugging:

  • “Preview of output” window doesn’t seem to stay where it’s put after closing and re-opening the clip editor. I think this is a regression, I remember it staying where it was before?
  • I managed to create a clip in a ‘negative’ clip index (-7:0), I managed to add it to the timeline, where upon modifying its length in the timeline, Liberation crashed (logs below).
=== Crash Detected ===
Crash code: 0xc0000005
Address: 0x000000014138B660
Stack trace:
  [Unknown Function] [0x14138b660]
  [Unknown Function] [0x1413980fc]
  [Unknown Function] [0x141398597]
  [Unknown Function] [0x1413bbe41]
  [Unknown Function] [0x141408776]
  [Unknown Function] [0x141405a76]
  [Unknown Function] [0x1414113aa]
  [Unknown Function] [0x1413a53c5]
  [Unknown Function] [0x1412d8799]
  [Unknown Function] [0x1413ea93d]
  [Unknown Function] [0x1417f32a5]
  [Unknown Function] [0x14150599d]
  [Unknown Function] [0x1415ecbfa]
  CallWindowProcW [0x7ffc63f3e83a]
  CallWindowProcW [0x7ffc63f3e28f]
  wglSwapLayerBuffers [0x7ffbfcddbcf3]
  CallWindowProcW [0x7ffc63f3e83a]
  TranslateMessage [0x7ffc63f5ccb2]
  [Unknown Function] [0x1415ea78b]
  [Unknown Function] [0x14181b5f6]
  [Unknown Function] [0x14181b3a7]
  [Unknown Function] [0x1417e3584]
  [Unknown Function] [0x1413a1408]
  [Unknown Function] [0x14184781e]
  BaseThreadInitThunk [0x7ffc6243e8d7]
  RtlUserThreadStart [0x7ffc6447c5dc]
2

This is how I designed it, but yeah should probably rethink it. I’ve found it annoying at times.

Creating a clip with a negative index is absolutely fine and normal, and shouldn’t crash the timeline! I can’t recreate your issue here, let me know if it is reproducible every time and if so, send me your project file.

Thanks!

Seb

1 Like
3

Something appears to be up with the licensing levels in 0.9.9. We can’t seem to get more than two of the lasers to work:

image
image602×178 27 KB

The other two lasers are there, and we can see the software trying to send them data, but they appear red:

image
image270×112 3.18 KB

Is it possible that the software isn’t correctly reading my license? I have a Pro4 license and if only two lasers are working, could this be that it’s defaulting to the hobby level?

Thanks!

4

Hey Eric,

as mentioned in the other thread, the red square indicates a connection issue, not a licensing one - licensing only stops you being able to arm the lasers, the connections should all still be fine.

thanks for the feedback!

Seb

1 Like
5

A new project fixes the lasers not working, I just get to redefine my blackout zones each time. weee..

6

A post was split to a new topic: Preview timeline while working on it