# Frame function improvement

**URL:** <https://forum.lightburnsoftware.com/t/frame-function-improvement/123474>\
**Category:** LightBurn Software Questions\
**Created:** [January 4, 2024, 3:15pm UTC](https://forum.lightburnsoftware.com/t/frame-function-improvement/123474 "2024-01-04T15:15:06Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![FasterIT](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/fasterit/32/74784_2.png) [@FasterIT](https://forum.lightburnsoftware.com/u/FasterIT)\
**Post date:** [January 4, 2024, 3:15pm UTC](https://forum.lightburnsoftware.com/t/frame-function-improvement/123474/1 "2024-01-04T15:15:06Z")

</div>

Hi @LightBurn,  
Happy New Year!

You said in [Is it possible to have the framing happen on a slight delay - #4 by LightBurn](https://forum.lightburnsoftware.com/t/is-it-possible-to-have-the-framing-happen-on-a-slight-delay/61250/4) that you have something cooking for the Frame function to run continuously. Can we have that soon™? For us the function as is means you need two people. One to push Shift+[Frame] and the other one to look at the devices 🙂

There are multiple past issues that indicate the same problem with this function falling short (and this is why we can’t use LightBurn 😭 ):

[How to get "shift+frame" driving 3 times a test frame instead of only 1 time?](https://forum.lightburnsoftware.com/t/how-to-get-shift-frame-driving-3-times-a-test-frame-instead-of-only-1-time/30060) ,  
…/t/frame-how-i-can-run-the-frame-more-than-one-time/12169  
etc.

Daniel/FIT

---

<div class="post-metadata">

**Author:** ![FasterIT](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/fasterit/32/74784_2.png) [@FasterIT](https://forum.lightburnsoftware.com/u/FasterIT)\
**Post date:** [January 4, 2024, 3:19pm UTC](https://forum.lightburnsoftware.com/t/frame-function-improvement/123474/2 "2024-01-04T15:19:35Z")

</div>

[Continuous frame · LightBurn](https://lightburn.fider.io/posts/844/continuous-frame) for the feature request link that is closest

---

<div class="post-metadata">

**Author:** ![cggorman](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/cggorman/32/75539_2.png) [@cggorman](https://forum.lightburnsoftware.com/u/cggorman)\
**Post date:** [January 4, 2024, 4:22pm UTC](https://forum.lightburnsoftware.com/t/frame-function-improvement/123474/3 "2024-01-04T16:22:44Z")

</div>

Implemented in ver 1.5

---

<div class="post-metadata">

**Author:** ![misken](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/misken/32/47593_2.png) [@misken](https://forum.lightburnsoftware.com/u/misken)\
**Post date:** [January 4, 2024, 4:36pm UTC](https://forum.lightburnsoftware.com/t/frame-function-improvement/123474/4 "2024-01-04T16:36:57Z")

</div>

While implemented in 1.5, I don’t know if it’s still of use for you:

> [@FasterIT](#):
>
> One to push Shift+[Frame] and the other one to look at the devices

If you enable “fire on when framing” in recent LB versions, you don’t need to press shift anymore. And since the framing function has a hotkey assigned (ALT+R usually), you can use any wireless keyboard or some add-on keypads to start the framing. Even mobile phones or tablets can function as hot key sender.

---

<div class="post-metadata">

**Author:** ![FasterIT](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/fasterit/32/74784_2.png) [@FasterIT](https://forum.lightburnsoftware.com/u/FasterIT)\
**Post date:** [January 4, 2024, 4:44pm UTC](https://forum.lightburnsoftware.com/t/frame-function-improvement/123474/5 "2024-01-04T16:44:46Z")

</div>

Not the continuous framing or any other useful N-repeat feature or so.

---

<div class="post-metadata">

**Author:** ![FasterIT](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/fasterit/32/74784_2.png) [@FasterIT](https://forum.lightburnsoftware.com/u/FasterIT)\
**Post date:** [January 4, 2024, 4:45pm UTC](https://forum.lightburnsoftware.com/t/frame-function-improvement/123474/6 "2024-01-04T16:45:23Z")

</div>

Thanks for the tip. This is a real crutch only but … that’s what is possible for now.  
I hope this request will make the developer(s) reconsider investing a bit of time in this function.

---

<div class="post-metadata">

**Author:** ![berainlb](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/b/85f322/32.png) [@berainlb](https://forum.lightburnsoftware.com/u/berainlb)\
**Post date:** [January 4, 2024, 5:38pm UTC](https://forum.lightburnsoftware.com/t/frame-function-improvement/123474/7 "2024-01-04T17:38:49Z")

</div>

As @cggorman has indicated the feature is slated for 1.5.

However, if this is a showstopper for you now you can readily remedy this for yourself with a workaround:

1. create a shape on workspace that fits the frame shape desired. If you want a rubberband frame LightBurn provides a feature that will create a rubberband shape in Arrange-\>Create rubber-band outline from selection
2. assign shape to a dedicated cut layer for framing. Set speed and power level appropriately for framing operation. Set multiple passes on the cut layer.
3. select only the frame shape to run, then start the job
4. once material is aligned, stop the job. If using GRBL, use pause then stop to prevent alarm condition.

---

<div class="post-metadata">

**Author:** ![FasterIT](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/fasterit/32/74784_2.png) [@FasterIT](https://forum.lightburnsoftware.com/u/FasterIT)\
**Post date:** [January 4, 2024, 8:20pm UTC](https://forum.lightburnsoftware.com/t/frame-function-improvement/123474/8 "2024-01-04T20:20:41Z")

</div>

Thank you @berainlb for the detailed work-around!

Is there a tentative schedule for the v1.5?

---

<div class="post-metadata">

**Author:** ![berainlb](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/b/85f322/32.png) [@berainlb](https://forum.lightburnsoftware.com/u/berainlb)\
**Post date:** [January 4, 2024, 8:29pm UTC](https://forum.lightburnsoftware.com/t/frame-function-improvement/123474/9 "2024-01-04T20:29:29Z")

</div>

I’ve not seen any indication of timeframe for 1.5 and frankly I don’t think I’ve ever seen LightBurn team commit to a date.

In general I’d advise against waiting on the promise of a brighter future for something that you’re counting on now.

Once a release is available in public beta then relatively safer to say the release is imminent and that you can count on it being released somewhat soon.

---

<div class="post-metadata">

**Author:** ![FasterIT](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/fasterit/32/74784_2.png) [@FasterIT](https://forum.lightburnsoftware.com/u/FasterIT)\
**Post date:** [January 4, 2024, 8:42pm UTC](https://forum.lightburnsoftware.com/t/frame-function-improvement/123474/10 "2024-01-04T20:42:18Z")

</div>

Thank you again @berainlb.  
May be hell will freeze over in 2024 and we can get a guesstimated timing from @LightBurn ? Pretty please?

---

<div class="post-metadata">

**Author:** ![FasterIT](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/fasterit/32/74784_2.png) [@FasterIT](https://forum.lightburnsoftware.com/u/FasterIT)\
**Post date:** [February 2, 2024, 6:33pm UTC](https://forum.lightburnsoftware.com/t/frame-function-improvement/123474/11 "2024-02-02T18:33:12Z")

</div>

The continuous framing is now an option in the 1.5 beta at [Public Beta - Google Drive](https://drive.google.com/drive/folders/1eOw5Ea2soarfXAcKJjq5bDgtstpXTfNX) (check Device settings)

---

<div class="post-metadata">

**Author:** ![system](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/system/32/64335_2.png) [@system](https://forum.lightburnsoftware.com/u/system)\
**Post date:** [March 3, 2024, 6:33pm UTC](https://forum.lightburnsoftware.com/t/frame-function-improvement/123474/12 "2024-03-03T18:33:20Z")

</div>

Closed on March 3, 2024, 6:33pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
