1
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1] 2
2
Enhancement Requests / Re: Import a Sequence to a Timestamp Other than 0:00
« on: February 28, 2022, 07:23:39 PM »
I agree about presets. They are great for copying effects within a particular model track. This request would provide a method for more complex patterns.
Hopefully this feature enhancement is viewed favorably that it could be included in a future build. The Import feature already does most of the heavy lifting, connecting the right models together, then adding the necessary additional layers, if needed.
One immediate use case could be a library of firework effects, which are really a chain several different effects. Users could build a sequence from a variety of shared effect-chains.
Hopefully this feature enhancement is viewed favorably that it could be included in a future build. The Import feature already does most of the heavy lifting, connecting the right models together, then adding the necessary additional layers, if needed.
One immediate use case could be a library of firework effects, which are really a chain several different effects. Users could build a sequence from a variety of shared effect-chains.
3
Enhancement Requests / Import a Sequence to a Timestamp Other than 0:00
« on: February 27, 2022, 09:10:37 PM »
Could the Import feature be enhanced to allow the important into a sequence and have the import add it at a timestamp other then 0:00?
If a user has a chain of effects that span models or model groups, using the preset feature becomes challenging. Presets appear to assume model group orders are the same, and the correct number of layers for a model are already defined.
In the video link example I'd like to decompose a number of firework effect chains into small sequences, then reload them in different orders across a new sequence.
Here is video of the feature request: https://youtu.be/loTvil2RMvA
Thanks.
If a user has a chain of effects that span models or model groups, using the preset feature becomes challenging. Presets appear to assume model group orders are the same, and the correct number of layers for a model are already defined.
In the video link example I'd like to decompose a number of firework effect chains into small sequences, then reload them in different orders across a new sequence.
Here is video of the feature request: https://youtu.be/loTvil2RMvA
Thanks.
4
Enhancement Requests / Add Scale Values in the UI for Poly-line Models
« on: February 27, 2022, 07:08:48 PM »
The request is to add a Scale X, Scale Y, and Scale Z to the UI for Poly-line models. Many of the other model types have this feature, but currently not the Poly-line model.
This sample video demonstrates: https://youtu.be/X30v2vH0w8I
This sample video demonstrates: https://youtu.be/X30v2vH0w8I
5
Bugs in xLights/Nutcracker / Preview Cache Does Not Clean-up After a Change of Layout
« on: February 27, 2022, 12:43:32 PM »
Within an xLights session, if you bounce between layouts the preview cache does not cleanup. It grows to include previews of old and the newest layouts. After bouncing a couple times the Preview list can grow to become large, and with duplicate values.
A short video demonstrating this issue is shared here: https://youtu.be/C9ZdEsKEIC0
I believe the desired result is for the preview to only show the relevant groups of the currently loaded layout?
Thanks.
A short video demonstrating this issue is shared here: https://youtu.be/C9ZdEsKEIC0
I believe the desired result is for the preview to only show the relevant groups of the currently loaded layout?
Thanks.
6
Bugs in xLights/Nutcracker / Re: obj file appears as blank
« on: April 04, 2021, 06:43:30 AM »
Thanks for the suggestions, this is a scale issue. Looks like this file needs to be scaled a lot to see it.
7
Bugs in xLights/Nutcracker / obj file appears as blank
« on: April 03, 2021, 11:50:50 PM »
When loading the attached obj file and supporting materials it appears as blank in xlights 2021.09. The same file viewed in meshmixer or online 3d viewer shows the file successfully? Files and screenshots attached.
8
Xlights Setup / Re: Faces and States layout properties for a servo do not match the timing track opt
« on: April 03, 2021, 12:18:06 AM »
Hi Gil,
Thanks for the reply. The lyric track works well if the servo drives a mouth. If the servo effect could support the standard state track, that would enable other servo applications nicely. I've shared here a couple prototype examples (the paper snowman head will be replaced with am 18" sphere with singing face):
1) video prototyping the lyric track. The challenge here is having to translate servo positions based on phenomes and would be error prone. It also does not allow for value curves.
2) video prototyping effect presets. A generic timing track was used to plan the head movements then effect presets were used. The challenge here is that if one of the effects were to be improved at a later date then one would need to hunt down and update each effect instance.
It would be great if the servo effect could support generic timing track comments like the state effect. Also shared in this post is a screenshot of a grayed out timing track field from within the value curve dialog box from the servo effect. Might this be a possibility? It is grayed out and I'm not sure if or how it might be used.
Thanks,
--Charlie
Thanks for the reply. The lyric track works well if the servo drives a mouth. If the servo effect could support the standard state track, that would enable other servo applications nicely. I've shared here a couple prototype examples (the paper snowman head will be replaced with am 18" sphere with singing face):
1) video prototyping the lyric track. The challenge here is having to translate servo positions based on phenomes and would be error prone. It also does not allow for value curves.
2) video prototyping effect presets. A generic timing track was used to plan the head movements then effect presets were used. The challenge here is that if one of the effects were to be improved at a later date then one would need to hunt down and update each effect instance.
It would be great if the servo effect could support generic timing track comments like the state effect. Also shared in this post is a screenshot of a grayed out timing track field from within the value curve dialog box from the servo effect. Might this be a possibility? It is grayed out and I'm not sure if or how it might be used.
Thanks,
--Charlie
9
Xlights Setup / Faces and States layout properties for a servo do not match the timing track opt
« on: March 30, 2021, 11:37:46 PM »
I have a servo defined and struggling to link it to a timing track. I've built a snowman head which would pivot on a vertical post where the servo would control the head position.
On the layout tab, the States property is configurable. The Faces property is not configurable. On the Sequencer tab it is not possible to link the servo to a standard timing track. However, it is possible to link to a lyric timing track? This appears to conflict? Or how can one configure this properly?
My ideal goal would be to define 5 servo positions, as example at position {20, 40, 60, 80, 100} then name each position {far-left, left, center, right, far right} then within a sequence define a single servo track and using the defined position names to determine the servo position. I'd like to avoid having to add many servo effects on the timeline, especially since each servo effect has to be clicked on to see its value. With several moving snowman heads it would be easier to generally program
Is there a best practice way do this?
Thanks
--charlie
On the layout tab, the States property is configurable. The Faces property is not configurable. On the Sequencer tab it is not possible to link the servo to a standard timing track. However, it is possible to link to a lyric timing track? This appears to conflict? Or how can one configure this properly?
My ideal goal would be to define 5 servo positions, as example at position {20, 40, 60, 80, 100} then name each position {far-left, left, center, right, far right} then within a sequence define a single servo track and using the defined position names to determine the servo position. I'd like to avoid having to add many servo effects on the timeline, especially since each servo effect has to be clicked on to see its value. With several moving snowman heads it would be easier to generally program
Is there a best practice way do this?
Thanks
--charlie
10
Bugs in xLights/Nutcracker / Issue with polyline objects and group inheritance spanning previews
« on: September 28, 2020, 02:10:12 PM »
Polyline submodels in preview 'A' do not appear in preview 'B' when the polyline submodel is member of a group assigned to preview 'B'
Agree this is a complicated scenario but it is a way I've found to geographically organize models and controllers into smaller sections for planning purposes.
Other model types work fine including single lines and custom models. I've 2 polyline models in all of my display and they are the two not working.
Included is a simplified example from my display.
The submodels at issue are contained in the OL-GarR and OL-GarL polylines. The desire is for them to show up in the Xlights preview inherited from OL-GarL and OL-GarR membership in the respective House Outlines Horiz and House Outline Vert groups.
Agree this is a complicated scenario but it is a way I've found to geographically organize models and controllers into smaller sections for planning purposes.
Other model types work fine including single lines and custom models. I've 2 polyline models in all of my display and they are the two not working.
Included is a simplified example from my display.
The submodels at issue are contained in the OL-GarR and OL-GarL polylines. The desire is for them to show up in the Xlights preview inherited from OL-GarL and OL-GarR membership in the respective House Outlines Horiz and House Outline Vert groups.
11
Bugs in xLights/Nutcracker / Re: Export sphere custom model loses nodes
« on: January 21, 2020, 04:51:55 PM »
It appears to be exporting in 3D. When the model is imported into XLights the custom model is spread across 17 tabs. Including a screenshot showing this. Also including the model export when it is exported as a native xlight model vs the custom model attachment in the original post.
12
Bugs in xLights/Nutcracker / Export sphere custom model loses nodes
« on: January 21, 2020, 06:30:59 AM »
Exporting a sphere to a custom model loses nodes. On a 72 node sphere across 8 strings, 8 nodes are dropped.
Steps to recreate:
1) Create a sphere. In my case, 8 strings of 9 nodes. The issue was found on 2019.68 and also recreated on 2020.3
2) Export sphere as custom model. Inspect the export file and node numbers will be missing.
3) Alternatively import the model into a layout. There are missing numbers across the 17 layers the sphere is laid out against.
Steps to recreate:
1) Create a sphere. In my case, 8 strings of 9 nodes. The issue was found on 2019.68 and also recreated on 2020.3
2) Export sphere as custom model. Inspect the export file and node numbers will be missing.
3) Alternatively import the model into a layout. There are missing numbers across the 17 layers the sphere is laid out against.
13
Nutcracker Effects / Fading Problems when masking layers exist
« on: December 27, 2019, 11:53:49 PM »
Hi, I'm not sure if this is a bug, or just not supported, but when a fade transition in or out is configured on an effect set to "2 is Unmask", the fade transition is not honored. On render, the effect with "2 is Unmask" is all on or all off.
Attached is a sample. It includes the effect layering I'm trying to accomplish, the red Entire Display effect should fade into the color of the tree, then out. Fade is no honored. The sample also shows a similar scenario within the prop with the green on effect.
Is there a way to enable fading in these examples?
Thanks,
--Charlie
Attached is a sample. It includes the effect layering I'm trying to accomplish, the red Entire Display effect should fade into the color of the tree, then out. Fade is no honored. The sample also shows a similar scenario within the prop with the green on effect.
Is there a way to enable fading in these examples?
Thanks,
--Charlie
14
General Software / Re: Add Phonemes?
« on: February 15, 2019, 01:07:48 AM »
Thanks for the guidance thus far. I've determined a way to effectively add a new phoneme without swapping an existing one. It is a little more involved, but sharing here in case others have same need.
Add additional "phonemes" as submodels in the state field. If you need a special phoneme, change the effect from faces to A/B and set the value to the proper sub-model. This way...a MBP for "Merry Christmas" can start with a wide MBP expression, while a MBP for a "Boom Boom Boom" can start with a narrow or puckered looking MBP expression.
Add additional "phonemes" as submodels in the state field. If you need a special phoneme, change the effect from faces to A/B and set the value to the proper sub-model. This way...a MBP for "Merry Christmas" can start with a wide MBP expression, while a MBP for a "Boom Boom Boom" can start with a narrow or puckered looking MBP expression.
15
General Software / Re: Add Phonemes?
« on: February 14, 2019, 09:12:53 AM »
Is it possible to configure a new custom face outline?
The word breakdown feature works great, but in my use case I'd prefer to swap the standard breakdown phoneme image for mbp with a smaller, flattish line. Even the rest phoneme is a little too wide when a phrase is "boom boom boom" it looks like the face is trying to smile between the words.
Thanks,
The word breakdown feature works great, but in my use case I'd prefer to swap the standard breakdown phoneme image for mbp with a smaller, flattish line. Even the rest phoneme is a little too wide when a phrase is "boom boom boom" it looks like the face is trying to smile between the words.
Thanks,
Pages: [1] 2