Ron I wanted to take a minute to say this. Thank you, even if you don't have a million likes per video. They are awesome to see and help me even get a glimpse or what is possible or new with xlights. Your talents and kindness is very refreshing to see
Alias at submodel is not for models and groups (that has been there), but rather at the actual submodel level in the model itself. Edit SubModels, click on Actions button and then Add/Edit Aliases.
That would have been great to know. Maybe there should be screenshots with all releases, man. There are so many choices and so many changes taking place. How do we keep up? I hope in a future release having the functionality at the submodel level within the layout screen will be possible.
@@xTremeSequences I like that idea .. right click on the submodel on the expanded model list. (I realize the readme/changes is pretty brief and cryptic).
As others said, Had to enable setting, save layout, restart Xlights to enable dropdown, Desktop Specs Intel I7-8700 @ 3.20ghz NVIDIA GeForce RTX 2060 (6bg) 16gb Ram XLATW Greatest Showman Sequence (My Longest to Render) OFF - No Hardware Video Decoding 159 DIRECTX11 48 FFmpeg Auto 123 FFmpeg Cuda 122 FFmpeg QSV 160 FFmpeg Vulkan 160 DirectX11 for the win, 3 Times Quicker Massive different!!
@@alexb4734 I know, I do have some coding skills, and I'm actually really good at doing UI layouts etc. I just doubt I would have the time to do it the justice it needs.
Not that drop-down. The one next to checkmark. We found tonight that you have to save layout and restart xlights after the checkmark to enable the drop-down.
Key purpose for the script was to go an add a new prop to all of your sequences. Could also be used to reorder the models and such. In the vid - thanks Ron.
@@xTremeSequences Every one in the list. (DirectX11, FFmpeg Auto, FFmpeg CUDA, FFmpeg QSV and FFmpeg Vulkan They were all within a few seconds on Render time. No real usage shown for the GPU in Task Manager. Latest update installed for the T1000.
@@JonB256 Did you have images and videos in the sequence. The codecs, from what I have been told, only work on videos and images. I would also save the sequence first before rendering with each.
@@xTremeSequences So I picked a sequence with a long video displayed on a large (48panel) P5 panel. While I didn't see any HUGE difference in render times, using either FFmpeg Auto or FFmpeg CUDA, there was great use shown of the GPU resources. Up to 80% for FFmpeg Auto and over 93% for FFmpeg CUDA. It even made my GPU fan come on for the first time in ages. But, the time reduction was only 15%. The QSV and Vulkan choices didn't use my GPU to any real extent.
Ron I wanted to take a minute to say this.
Thank you, even if you don't have a million likes per video. They are awesome to see and help me even get a glimpse or what is possible or new with xlights. Your talents and kindness is very refreshing to see
Thank you so much for the kind remarks.
Alias at submodel is not for models and groups (that has been there), but rather at the actual submodel level in the model itself. Edit SubModels, click on Actions button and then Add/Edit Aliases.
That would have been great to know. Maybe there should be screenshots with all releases, man. There are so many choices and so many changes taking place. How do we keep up? I hope in a future release having the functionality at the submodel level within the layout screen will be possible.
@@xTremeSequences I like that idea .. right click on the submodel on the expanded model list. (I realize the readme/changes is pretty brief and cryptic).
One of these days, I will get it 100% right. LOL @darylerwin
Thanks for another great video Ron!!! Appreciate the info.
Thanks, Dan!
As others said, Had to enable setting, save layout, restart Xlights to enable dropdown,
Desktop Specs
Intel I7-8700 @ 3.20ghz
NVIDIA GeForce RTX 2060 (6bg)
16gb Ram
XLATW Greatest Showman Sequence (My Longest to Render)
OFF - No Hardware Video Decoding
159
DIRECTX11
48
FFmpeg Auto
123
FFmpeg Cuda
122
FFmpeg QSV
160
FFmpeg Vulkan
160
DirectX11 for the win, 3 Times Quicker Massive different!!
User interface could still do with a massive amount of improvement to make it more logical during use.
Opensource, so please feel free to jump in and contribute
@@alexb4734 I know, I do have some coding skills, and I'm actually really good at doing UI layouts etc. I just doubt I would have the time to do it the justice it needs.
Ron--on my windows laptop, I don't see any "FF" codecs in the dropdown. There are auto, HL264, HL265, & MPEG-4 in the windows dropdown. XL2024.08.
You would see these choices in xLights Preferences.
Not that drop-down. The one next to checkmark. We found tonight that you have to save layout and restart xlights after the checkmark to enable the drop-down.
Yikes. I had to reboot my laptop to install the update. I can see where this might confuse some. @@darylerwin
How do I find the developers' videos? Not sure where to even start looking. Thanks Ron.
Search for xLights Gems in RUclips.
Key purpose for the script was to go an add a new prop to all of your sequences. Could also be used to reorder the models and such. In the vid - thanks Ron.
@@darylerwinYeh, this is some nice work and I want to give it it's own video. I would have gone down a rabbit hole of no return.
896 CUDA cores on an Nvidia T1000 card and it made Zero difference
Yeh, that's no bueno. Which codecs did you try?
@@xTremeSequences Every one in the list. (DirectX11, FFmpeg Auto, FFmpeg CUDA, FFmpeg QSV and FFmpeg Vulkan
They were all within a few seconds on Render time. No real usage shown for the GPU in Task Manager. Latest update installed for the T1000.
@@JonB256 Did you have images and videos in the sequence. The codecs, from what I have been told, only work on videos and images. I would also save the sequence first before rendering with each.
@@xTremeSequences So I picked a sequence with a long video displayed on a large (48panel) P5 panel. While I didn't see any HUGE difference in render times, using either FFmpeg Auto or FFmpeg CUDA, there was great use shown of the GPU resources. Up to 80% for FFmpeg Auto and over 93% for FFmpeg CUDA. It even made my GPU fan come on for the first time in ages. But, the time reduction was only 15%. The QSV and Vulkan choices didn't use my GPU to any real extent.
@@JonB256 It appears there will be mixed results in Windows world for this. I'm not surprised. Thanks for testing it out.