Luxea 6 Free not saving more than 7 sec

[Regor250]

Trying to run Luxea 6 Free app and I can't save more than 7 sec of video screen recording. Anyone else encountered such issue? To my understanding the Free version isn't limited in recording time.

[Greyfox]

Trying to run Luxea 6 Free app and I can't save more than 7 sec of video screen recording. Anyone else encountered such issue? To my understanding the Free version isn't limited in recording time.

If you are referring to Luxea Video Recorder, then I often record sessions way more than that (some around an hour), but I don't have the free version., ..
Do you by chance have the record duration option set in tools\Options\General Settings.

[Regor250]

I tried setting Record Duration to 1hr, didn't work. Tried changing the output folder, didn't work. Tried unchecking Hardware Acceleration, didn't work. 7sec is a pretty tidy time, always consistent so I doubt it's a buffering issue otherwise it would vary from recording to recording. Win11 Xbox video screen capture (Win-Alt-R) works fine, so is the Nvidia Game Capture. James is on the case, we'll see if we can pin that one down.

[Greyfox]

I tried setting Record Duration to 1hr, didn't work. Tried changing the output folder, didn't work. Tried unchecking Hardware Acceleration, didn't work. 7sec is a pretty tidy time, always consistent so I doubt it's a buffering issue otherwise it would vary from recording to recording. Win11 Xbox video screen capture (Win-Alt-R) works fine, so is the Nvidia Game Capture. James is on the case, we'll see if we can pin that one down.

The other application that works well for me for recording on screen video is OBS Studio.
Will be interesting to see what Support comes up with. I did use the earlier free version some time ago for a trial and aside from the logo I can't remember any other restrictions. I subsequently purchased V6 and that doesn't have any time restrictions here on Windows 10 Pro. .

[Regor250]

I installed the app on my old Windows 10 platform just to see, and 7 seconds is the max length recorded. Two completely different systems, one on Win10 the other on Win11, the only thing in common is my account. This rules out just about any local configuration issue and may have something to do with the ACDSee account or something I thought. Then I tried different accounts and no account and it made no difference. I am at a loss on that one and the only option not tested is with an activation code, which of course I don't have.

[Greyfox]

I installed the app on my old Windows 10 platform just to see, and 7 seconds is the max length recorded. Two completely different systems, one on Win10 the other on Win11, the only thing in common is my account. This rules out just about any local configuration issue and may have something to do with the ACDSee account or something I thought. Then I tried different accounts and no account and it made no difference. I am at a loss on that one and the only option not tested is with an activation code, which of course I don't have.

By default the F9 key Starts, Pauses and Resumes recording, and the F10 key terminates and saves the record session.
I wonder whether either of those keys is being affected by something else on your PC's.
In the recorder Tools\Options\ Hotkey\Hotkey settings you can modify the hotkeys - might be worth doing that to see whether it fixes the problem.

[Regor250]

James has given me a temporary key, and that worked fine after activation. After reinstalling/repair the app and NOT re-registering/activating it, it still works fine. So the issue happens only on a first clean install. Something set during activation and unaffected by a reinstall is making it work. The activation on my Win11 box did not make it work on my other non-activated but registered Win10 box, so the issue is local and not linked to the activation on the server side, in which case it would have fixed it on my other platform. Awaiting for James to get back to me. Technically my issue is resolved, the app now works as it should, but the source of the bug remains to be identified.

[James W-]

Hi Rogor250,

I am glad to know that workaround does work for you on one machine. However, I have not been able to reproduce the issue even after a complete reinstallation of all ACDSe programs and then running Recorder under a brand-new user account. I think the same workaround shall be possible to make the difference on your other machine. Another method is to perform a complete reinstallation of Luxea on that machine. I will reply to your email to follow up.

Hope this helps. If the issue still remains, I suggest setting up a remote diagnosis meeting to find out more.



Regards
James

[Regor250]

The problem had nothing to do with the key. After much headaches, even an OS fresh install eliminating all but one possibility I discovered that the problem is that Luxea does not work without speaker and mic connected, aka headset for me ! That's right, no headset, no Luxea screen recording, who would have thought !

[Greyfox]

The problem had nothing to do with the key. After much headaches, even an OS fresh install eliminating all but one possibility I discovered that the problem is that Luxea does not work without speaker and mic connected, aka headset for me ! That's right, no headset, no Luxea screen recording, who would have thought !

Confirmed !
it does that here too. Being on a desktop, I had to physically unplug not only the headset from the front panel, but also the speaker audio from the rear panel, at which stage the task bar icon shows the audio with a red cross.


Strange that it records for 7 seconds (+12 frames in my case) rather than not at all, and perhaps also that the recorder still shows the green tick against System Audio.

Good to have that identified for when someone else runs into the problem.

[Regor250]

I was just about giving up on that one, when after updating the app on my current system it stopped working correctly. So now I had two completely different systems, both with the same issue and only one thing in common, the headset unplugged! No one with a laptop would experience it, and a vast majority of desktops have speakers, so no wonder it was never picked up. At least now the development team is aware. They can either fix it, or add a warning, or hopefully not... ignore it.

[S.hussain]

Hi Regor,

Thanks for reporting the issue. We were able to reproduce the issue. A ticket has been logged to address the issue.

Sincerely,

Shakil H.
ACD Systems