Looking good!
Opening from glaxnimate.exe:
6 successful launches in a row,
0 fail.
Opening from Shotcut:
Just successful launches from there also.
Can you do please do a test if you still have the old settings.ini file? Restore it, get it to launch successfully, take it out of the maximized window state, quit, and see if it now launches successfully a few times.
After restoring the files from the recycle bin, it took 3 tries to launch in successfully.
I took it out of the maximized state, quit, and then got 6 or 7 successful launches.
Out of curiosity, I maximized the window again and quit.
3 successful launches, then a series of 5 or 6 failed ones.
I minimized again, quit, then 10 successful launches.
I can confirm the ARM64 build of this Beta release run on PineBook Pro with latest Manjaro.
The App launch and can seemingly perform all editing work as expected, with known drawbacks and limitation.
Hardware accelerated encoding is not available due to the platform side thing, which is to be expected according to this Wiki: Mainline Hardware Encoding - PINE64
Unfortunately, my existing project created in other laptop seems to be too big due to the 4K H265/BT2020/50MBps clips. Loading them into the Shotcut quickly overrun the limit of 4GB RAM of PineBook Pro. Hence the exporting and encoding part were not tested. I will try to shoot some 1080P clips this weekend to test later.
I guess this app would be perfectly usable on RPi 4 8G or other recent SBC with high RAM configuration.
Still, very glad to see and kudos to Shotcut moving ahead in ARM64 Linux landscape!
For that, you need to stick with a SD video mode or make use of proxies and preview scaling at 360p. Also, we found a serious memory bug in the beta, and you should probably wait for the next beta.
This Glaxnimate startup crash is fixed for the next version (or daily build as of 23.04.13).
Windows 10
Shotcut v23.04.14
GPU Effects OFF
Speed: Forward & Reverse filter: Shotcut crashes while attempting to convert a clip to edit friendly.
I tried with many clips from different origins (all MP4s though).
Shotcut crashed while trying to convert each clip to edit friendly from the Speed: Forward & Reverse filter.
No crashes when trying to convert a clip from the Properties panel though.
Speed: Forward and Speed: Forward & Reverse filters:
On normal filters, when you click on the Reset to Default button, Shotcut will reset to default the value of the selected keyframe, OR, if there is no keyframe, it will add a new one, set to the default value.
But on the Speed: Forward and Speed: Forward & Reverse filters, clicking on the Reset to Default button will delete all the other keyframes.
For some reason, your video does not play for me.
I was not able to reproduce a crash using the same version, but on Windows 11.
- Open a file
- Attempt to add Speed: Forward & Reverse filter
- Go through the convert dialog
- Observe that the conversion kicks off and completes
Does it also crash when you trigger it through the time remapping filter?
On time filters, the button resets all the keyframes to be the default state from when you create a new filter. This is the same behavior as Time Remap. I think this is more intuitive because a single keyframe doesnāt really have a ādefaultā state since its time/position is affected by all the keyframes in front of it. But I am open minded about this if some people find it unintuitive.
Thank you for testing the speed filters, by the way.
I kind of understand your rationale, but in my case at a certain point in time I wanted to return to normal, clicked undo/reset to do so, and was surprised to lose all of my speed changes.
I re-uploaded the video. I hope it works now.
Ah! Yes it does
Maybe not unintuitive, but unexpected? This is the same button used by all the other filters, so I guess people will expect it to behave the same.
Maybe add a warning after clicking?
This will remove all keyframes. Do you want to continue?
ā” Donāt show this message again
Or use a different button?
I like the functionality of the new copy filters dialogue but I just had to copy paste a single filter 10+ times and it got very annoying very fast. Would you maybe consider a āDonāt show again for this sessionā checkbox? Or an option in the menu somewhere.
2 Likes
Good feedback. The filter sets have been moved to a new button for the release and the paste action has gone back to normal.
2 Likes
A few more stuff as Iāve been using mainly the beta last few days:
- thereās something wrong with the ordering of recent projects in the latest version. I donāt really understand if thereās a logic behind but the latest project I saved is not always at the top (or bottom), it sometimes is second, or somewhere in first 10, or just doesnāt appear at all. Especially if the app crashes it is very likely that the project is not in the list anymore.
This might be somehow broken by having this latest version as the standalone one and the older (stable) version installed normally. Or by GPU effects enabled? does it hide some projects intentionally?
-
This only happened once and I havenāt been able to reproduce it but after a crash I reopened last project and Shotcut asked me if I want to use the autosave, I clicked yes but it complained that it is from an invalid version: 23.04.30. Not sure how it got to that .30, Iāll keep an eye on it if it happens again.
-
There seems to be some memory usage issues in new beta version compared to the older one and while for both it seems to go up by about 300MB for every new clip in the timeline (for this particular project, not sure if itās related to video type), the beta seems to never release or stop eating extra RAM.
Iāve launched the same old project (made in the 22.12.21 version) in 2 Shotcut versions (22.12.21 + beta) side by side and here is task manager while both of them are playing it (GPU effects off):
Side note: the beta plays back way smoother even the 4k footage in the timeline so I am extremely happy if the extra RAM is the cause, but not at 95+% ram, caching stuff until 80-90% used ram would be completely fine for me.
OK. I changed it to create or modify a keyframe to be speed 1.0x
1 Like
Thanks for updating the video. I still can not recreate it trying the same steps in your video and with multiple files.
Can anyone else reproduce that crash?
Does it happen with all files, or only some?
What if you try to save in a different location?
In my original report, I only tested with MP4 files.
Now I tried with FLV, AVI and MKV files. Shotcut still crashes.
I also tried with a VMW file, but Shotcut didnāt ask to convert it.
I tried to save on different locations, including the Desktop and My Documents. Still crashes.
Note: Rebooting my computer didnāt fix the problem.
This is a known issue that is fixed for the next version.