Open erikliles opened 5 months ago
Could you please send me a Flame archive to have a look?Sent from my iPhoneOn 15 May 2024, at 18:03, erikliles @.***> wrote: I tried running a 50% Timewarp on a clip with Mix selected. TWML render a clip with a frame hold on each frame. 1-1, 2-2, 3-3, etc. I then converted the Timewarp to Motion, pre-rendered the clip, then ran TWML using "flownet4". This was better, but it randomly added double frames too. It also did not start at frame 1. As mu frame counter burn-in showed. It started at frame 2. It went from 2, 2.5, 2, 2.5, 3, 3.5, 4, 4.5 ,5 ,6, 6, 6.5, 7, 8, 8, etc. I used both models, "flownet4-lite" was worse, almost every frame was doubled. macOS 13.6.4 (22G513) Flame 2024.2.1 original frame rate of the clip is 23.976
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
Here is the archive.
https://drive.google.com/drive/folders/1Ijm-bHYmQW9nPfIOqU-0YbGNiIQAYo3t?usp=sharing
On May 15, 2024, at 13:10, Andriy Toloshny @.***> wrote:
Could you please send me a Flame archive to have a look?Sent from my iPhoneOn 15 May 2024, at 18:03, erikliles @.***> wrote: I tried running a 50% Timewarp on a clip with Mix selected. TWML render a clip with a frame hold on each frame. 1-1, 2-2, 3-3, etc. I then converted the Timewarp to Motion, pre-rendered the clip, then ran TWML using "flownet4". This was better, but it randomly added double frames too. It also did not start at frame 1. As mu frame counter burn-in showed. It started at frame 2. It went from 2, 2.5, 2, 2.5, 3, 3.5, 4, 4.5 ,5 ,6, 6, 6.5, 7, 8, 8, etc. I used both models, "flownet4-lite" was worse, almost every frame was doubled. macOS 13.6.4 (22G513) Flame 2024.2.1 original frame rate of the clip is 23.976
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***> — Reply to this email directly, view it on GitHub https://github.com/talosh/flameTimewarpML/issues/94#issuecomment-2113278967, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACA3B4BGTLCKDEOMOSTGNUDZCOXLTAVCNFSM6AAAAABHYR7PHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJTGI3TQOJWG4. You are receiving this because you authored the thread.
There is a v0.4.5 dev 003 in the releases would you mind to test it on Apple Silicon Mac?
Will do.
On Jun 16, 2024, at 12:39, Andriy Toloshny @.***> wrote:
There is a v0.4.5 dev 003 in the releases would you mind to test it on Apple Silicon Mac?
— Reply to this email directly, view it on GitHub https://github.com/talosh/flameTimewarpML/issues/94#issuecomment-2171804183, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACA3B4FAVWYNQVHOZZTYV6TZHXLU7AVCNFSM6AAAAABJMZ3IP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZRHAYDIMJYGM. You are receiving this because you authored the thread.
Hi, We have noticed the same problem here. Running Flame 2025.0.1 with macOS 14.5 on a Mac Studio 14,14. Same behavior in flameTimewarpML v0.4.5 dev 001 and v0.4.5 dev 003.
I tried running a 50% Timewarp on a clip with Mix selected. TWML render a clip with a frame hold on each frame. 1-1, 2-2, 3-3, etc. I then converted the Timewarp to Motion, pre-rendered the clip, then ran TWML using "flownet4". This was better, but it randomly added double frames too. It also did not start at frame 1. As mu frame counter burn-in showed. It started at frame 2. It went from 2, 2.5, 2, 2.5, 3, 3.5, 4, 4.5 ,5 ,6, 6, 6.5, 7, 8, 8, etc.
I used both models, "flownet4-lite" was worse, almost every frame was doubled.
macOS 13.6.4 (22G513) Flame 2024.2.1 original frame rate of the clip is 23.976