I’m getting a consistent crash every time I try to play a clip in batch with a timewarp on, just a simple 50% mix, no ML. This is happening in 2027 and 2027.1. It starts to play, but as soon as it hits frame 2 flame quits.
This is only in batch and not on the timeline, but is really screwing me up.
We upgraded from 2025 and this never happened in that version.
I’m on Rocky Linux 2027.1 and have no such issues.
In batch Tim?
yes
As a work-around, you can animate the slip on a mux node old skool to get something simple like 50% with no mix. I’m curious if it does it using the timing mode rather than percentage
Good point, I’ll give it a go
Yep, that crashed it too.
Use a mux node and in the slip channel put the expression frame*-.5
I was only using mix to find the right speed to run it at, before doing a ML respeed
You can still use the mux. The expression is frame*-(1-DesiredSpeed). For instance, if you wantted 2/3 speed, or 66.6667% the expression would be frame*-(1-.6667). You can replace the percentage with a dummy axis or variable so that you can easily dial in your speed. frame*-(1-dummychannel)
In fact, if you want it to be really elegant, you can add a timewarp node, but don’t plug any video into it. In the mux slip add the expression frame*-(1-(TimewarpNodeName.Speed / 100)). This way the timewarp speed will be duplicated on the mux slip. Notice the space on either side of the /. Until version 2027.2, this is important. In 2027.2 and up I am told you won’t need the spaces.
Maybe it’s that one clip?
Just in case there’s some funky metadata, I’d try something like taking the source clip and exporting it to your filesystem and reimporting it. At least that would rule in/out the clip itself.
I tried it on a clip of generated colour noise, same crash
I’d open a support case. Obviously something wrong with your setup.
Have done already