Giter VIP home page Giter VIP logo

aegisub-motion's Introduction

Aegisub-Motion.moon

v1.0.0

The dream is real.

What do I need to use this?

  • Aegisub 3.2.x or any future release that doesn't break everything.
  • Motion tracking software, such as Blender or Mocha Pro.
  • Too much goddamn free time.

How do I install it?

The recommended method is to use DependencyControl. If you cannot use DependencyControl, however, release zips are provided. Note that the release zip versions will still use DependencyControl for automatic updating if it is available.

Installing with DependencyControl

Installation instructions for DependencyControl can be found here.

  • Save this copy of Aegisub-Motion.moon to your automation autoload directory. Make sure it is named a-mo.Aegisub-Motion.moon.
  • Either run Aegisub or reload all automation scripts. All modules should be automatically updated to their latest versions.

Installing from a release zip

Windows (Installed Aegisub)
  • Open %appdata%\Aegisub. You can do this by opening an explorer window and typing it in the breadcrumb.
  • In the folder you just opened, verify that there is an automation directory. If there is not, create it.
  • If you just created an automation directory, copy the autoload and include folders from this zip to the directory you just created.
  • If the autoload and include folders already exist, copy their contents in the zip into the those folders.
Windows (Portable Aegisub)
  • Find your Aegisub folder. In it should be an automation folder.
  • In the automation folder, copy the contents of the zip's autoload and include folders into the respective folders in your Aegisub/automation folder.
OS X
  • In a Finder window, press cmd+shift+g, and enter ~/Library/Application Support/Aegisub/ into the dropdown window.
  • In the folder you just opened, verify that there is an automation directory. If there is not, create it.
  • If you just created an automation directory, copy the autoload and include folders from this zip to the directory you just created.
  • If the autoload and include folders already exist, copy their contents in the zip into the those folders.
Linux
  • Copy the files into ~/.aegisub/automation. You may need to create these directories.

If you absolutely MUST install from git, I'll let you figure that one out yourself.

How do I use this?

I fully recommend finding something better to waste your time.

Help! I need somebody! Help! Not just anybody!

If you use IRC, I'm CoffeeFlux on freenode and rizon. Feel free to ask questions. Also, this repository has an issues page if you want to be formal about it.

aegisub-motion's People

Contributors

coffeeflux avatar conkererer avatar line0 avatar torque avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

aegisub-motion's Issues

Consecutives \t are not handled correctly

If I try to apply a motion tracking to something like

{\blur10\t(0,600,\blur7)\t(600,1000,0.5,\blur3)\t(1000,3000,0.65,\blur0.6)}

the result comes out wrong, because \t is always handled like is starting from the "static" value and not from the end of the previous \t.
This means that when motion tracked the type goes like:
blur10->blur7 | blur10->blur->3 | blur10->blur0.6

Trim Issues

Encoding error:
x264.exe : C:\Users\User\Downloads\Programs\x264.exe: unknown option -- s
At line:1 char:38

  • ... er\Videos"; & "C:\Users\User\Downloads\Programs\x264.exe" -ss 0 -an - ...
  •             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    • CategoryInfo : NotSpecified: (C:\Users\User\D...own option -- s:String) [], RemoteException
    • FullyQualifiedErrorId : NativeCommandError

If there is no log before this, your encoder is not a working executable or your encoding command is invalid.

Support multiple clips per line.

The \clip override tag can be used up to twice in a line without overwriting itself. There are two formats, one which is purely rectangular, and one which is described by the standard ASS vector shape format.

A single line can contain one of each kind, which is useful to allow, for example, gradients that are clipped behind a shape. In this case, the gradient effect is provided by the rectangular clips, and the actual shape clipping is provided by a vector clip.

In the case that both types of clips exist in a line and separate clip tracking data is provided, it is almost guaranteed that the rectangular clips should move with the line and the vector clip should move with the clip tracking data.

Aegisub-Motion Apply, Trim and Trim Each greyed out.

I am using Aegisub trunk build version r8700. I have installed Aegisub-Motion v1.0.0 beta 5 from here (https://github.com/TypesettingCartel/Aegisub-Motion/releases) by creating the "automation" folder in the location given by %appdata%\Aegisub and subsiqently copying the "autoload" and "include" folders respectivly. However, when I open Aegisub up, the Apply, Trim and Trim Each options are greyed out and can't be clicked from the menu.

The Config and Trim Settings can however...

Using this on Windows 7 x64 with an installed version (not portable) Aegisub.

Better support for transforms

  • Determine proper start/end times for \t(\effect)
  • Determine proper end time for \t(t_s,0,\effect)
  • Other valid cases that are not currently supported?

trim error

Encoding error:
x264_64_tMod-8bit-all.exe : mp4 [info]: audio muxing feature is disabled.
所在位置 行:1 字符: 2

  • & <<<< "E:\x264_64_tMod-8bit-all.exe" --crf 16 --tune fastdecode -i 250 --fps 23.976 --sar 1:1 --index "E:
    \mocha-TEMP/123.index" --seek 1227 --frames 85 -o "E:\mocha-TEMP/123[1227-1311].mp4" "F:\taikonglvke/123.avs"
    2>&1 | Out-File C:\Users\ADMINI1\AppData\Local\Temp\a-mo.encode.log -en UTF8; if($LASTEXITCODE -ne 0) {echo
    "If there is no log before this, your encoder is not a working executable or your encoding command is invali
    d." | ac -en utf8 C:\Users\ADMINI
    1\AppData\Local\Temp\a-mo.encode.log; exit 1}; exit 0
    • CategoryInfo : NotSpecified: (mp4 [info]: aud...re is disabled.:String) [], RemoteException
    • FullyQualifiedErrorId : NativeCommandError

avs [error]: Cannot load file 'D:/MarukoToolbox/tools/avs/plugins/LSMASHSource.DLL'.
(F:\taikonglvke/123.avs, line 1)
x264 [error]: could not open input file `F:\taikonglvke/123.avs'
mp4 [error]: failed to finish movie.

If there is no log before this, your encoder is not a working executable or your encoding command is invalid.

Remove tags that are the same as the line's value.

In particular, we insert \fscx, \fscy, \bord, \shad, \frz, and \org if they don't already exist. This means that on the reference frame (and possibly others), these should have the same value as the style, in which case, they can be removed from the line.

Ultra mega super optimization country, let's go.

Error when trimming

gives me this error whenever I try to trim anything

Lua reported a runtime error:
File "E:/sub\aegisub-3.2.1-portable-32\automation\autoload\Aegisub-Motion.moon", line 483
<anonymous function at lines 457-485>
File "E:/sub\aegisub-3.2.1-portable-32\automation\include\a-mo\TrimHandler.moon", line 128
performTrim
File "E:/sub\aegisub-3.2.1-portable-32\automation\include\a-mo\TrimHandler.moon", line 95
execFunc
attempt to index local 'logFile' (a nil value)execFunc

the command prompt does appear but complains about a wrong file path and then disappears
FYI: I'm running the latest aegisub 3.2.1(portable), Win8.1(non english OS)
I have heard that win8.1 doesn't like short paths? maybe that's the culprit?

Applying tracking data results into extra override tags

Yeah me again sorry,
every time I apply tracking data it creates an extra override tag right at the beginning of the line,
like this {=9} (The number here varies with the data applied)
which makes the whole subtitle rendering go crazy 😓

PS. My motion data is 720P where my script is 1080P

Stuff that you might find in handy

"Aegisub thinks your video is 0 frames long"

Ok, let me preface this by saying that I am very much a noob when it comes to all things typesetting so I'm not sure if it's a bug or if it's something I've done wrong. Probably the latter. In any case, when I try to trim any file on any line I get this error:

Screenshot 2020-06-19 09 42 34

System info:
Screenshot 2020-06-19 09 46 06

Log (I think):
Log.txt

Aegisub version:
Aegisub Version.txt

File and ASS file I import into Aegisub (Although, like I said it's ANY file I use):
Mega

Any help would be greatly appreciated. Please let me know if there's any more info I should provide. Thank you!

Request: Aegisub script to go to previous/next frame

A lot of the subtitling I do depend greatly on frame accuracy, the video preview in Aegisub doesn't feature going to next/previous frame, wish there was a tool that makes moving about in aegisub alot easier
-going to next/previous frame
-going to (+1/-1 sec, or 500msec)

Aegisub-Motion -> Apply Error

Whenever I try to apply tracking data I get this error. Any idea what this could mean?

<anonymous function at lines 422-561>
    File "C:/Users\Tyler\AppData\Roaming\Aegisub\automation\autoload\a-mo.Aegisub-Motion.moon", line 180
prepareConfig
    File "C:/Users\Tyler\AppData\Roaming\Aegisub\automation\include\a-mo\DataWrapper.moon", line 53
bestEffortParsingAttempt
    File "C:/Users\Tyler\AppData\Roaming\Aegisub\automation\include\a-mo\DataWrapper.moon", line 32
tryDataHandler
    File "C:/Users\Tyler\AppData\Roaming\Aegisub\automation\include\a-mo\DataHandler.moon", line 118
DataHandler
    File "C:/Users\Tyler\AppData\Roaming\Aegisub\automation\include\a-mo\DataHandler.moon", line 29
__init
    File "C:/Users\Tyler\AppData\Roaming\Aegisub\automation\include\a-mo\DataHandler.moon", line 41
parseRawDataString
attempt to perform arithmetic on field 'scriptResX' (a nil value)

Can't use Trim Anymore!

Encoding error:
Encoding Failed. Log has been printed to progress windows.

What happen to my A.motion? Last week i can use it, then this week i got this problem that nobody know how to solve it?
Unistall and Install Aegisub, Reopen Aegisub, Install A.mo again, all of that didn't work a bit.

Lua reported a runtime error

Hello, first of all, I have aegisub 3.2.2 at 32 bits, and aegisub motion v1.0.4, I erase all and install that versions, since the new update was released I have this problem.

Lua reported a runtime error: File "C:/Program Files (x86)\Aegisub\automation\autoload\a-mo.Aegisub-Motion.moon", line 536 File "C:/Program Files (x86)\Aegisub\automation\include\a-mo\MotionHandler.moon", line 112 applyMotion File "C:/Program Files (x86)\Aegisub\automation\include\a-mo\MotionHandler.moon", line 172 method File "", line -1 ? File "C:/Program Files (x86)\Aegisub\automation\include\a-mo\MotionHandler.moon", line 176 attempt to perform arithmetic on local 't1' (a nil value)

I'm new in this, so I need help....and I want to learn more. See ya.

x264 compatibility

I'm a noob so I'm sorry if I ask something that's not your job to fix. But for some reason, when I try to use the x264 encode binaries (releases starting from x264-r2356-a1d3d17), the encoder opens and closes, and does nothing. I think there's something wrong with the command line, because the command bat file is created and runs, but I don't get any video files in the folder. This version: x264-r2345

->that I got from here: http://www.digital-digest.com/software/download-997_0_282_file_x264.exe%2B%252832-bit%2529.html

does the thing, and the ones before it, too (although I only checked one previous version except this one). The official r2345 (from the official site) doesn't work either.
If you need more information, feel free to contact me.

And in the meantime, thanks for making this awesome tool.

Support shake shape data for clips.

shake_shape_data 4.0
motion_blur 0
shutter_timing 0
shutter_offset 0.0
num_shapes 1
shape_name Layer_9_0_mask
parent_name 
closed 1
visible 1
locked 0
tangents 1
edge_shape 1
num_vertices 4
num_key_times 216
key_time 0
center_x 401.59
center_y 496.908
color_r 1.0
color_g 1.0
color_b 1.0
color_a 1.0
vertex_data 513.456 465.194 474.776 505.553 511.736 418.649 513.456 465.194 474.776 505.553 511.736 418.649 509.882 359.38 511.117 414.547 437.711 433.326 509.882 359.38 511.117 414.547 437.711 433.326 289.724 552.887 403.902 463.659 292.842 595.444 289.724 552.887 403.902 463.659 292.842 595.444 306.424 634.436 297.03 600.712 443.967 531.568 306.424 634.436 297.03 600.712 443.967 531.568 
key_time 1
center_x 401.871
center_y 496.901
color_r 1.0
color_g 1.0
color_b 1.0
color_a 1.0
vertex_data 513.735 465.193 475.057 505.552 512.014 418.648 513.735 465.193 475.057 505.552 512.014 418.648 510.155 359.378 511.392 414.546 437.989 433.327 510.155 359.378 511.392 414.546 437.989 433.327 290.006 552.888 404.182 463.661 293.124 595.438 290.006 552.888 404.182 463.661 293.124 595.438 306.703 634.424 297.312 600.705 444.244 531.562 306.703 634.424 297.312 600.705 444.244 531.562 
key_time 2
center_x 402.134
center_y 496.902
color_r 1.0
color_g 1.0
color_b 1.0
color_a 1.0
vertex_data 513.993 465.2 475.321 505.558 512.269 418.655 513.993 465.2 475.321 505.558 512.269 418.655 510.399 359.385 511.64 414.552 438.245 433.332 510.399 359.385 511.64 414.552 438.245 433.332 290.275 552.883 404.435 463.657 293.396 595.434 290.275 552.883 404.435 463.657 293.396 595.434 306.98 634.42 297.587 600.701 444.504 531.558 306.98 634.42 297.587 600.701 444.504 531.558 
key_time 3
center_x 337.06
center_y 389.505
color_r 1.0
color_g 1.0
color_b 1.0
color_a 1.0
vertex_data 481.886 394.776 381.427 443.925 479.736 329.122 481.886 394.776 381.427 443.925 479.736 329.122 478.13 263.804 481.228 326.873 361.686 323.067 478.13 263.804 481.228 326.873 361.686 323.067 192.234 397.483 326.054 341.364 197.492 444.406 192.234 397.483 326.054 341.364 197.492 444.406 208.333 515.207 197.973 450.666 331.35 468.482 208.333 515.207 197.973 450.666 331.35 468.482 
key_time 4
center_x 337.056
center_y 389.512
color_r 1.0
color_g 1.0
color_b 1.0
color_a 1.0
vertex_data 481.873 394.784 381.418 443.93 479.724 329.131 481.873 394.784 381.418 443.93 479.724 329.131 478.119 263.815 481.218 326.882 361.68 323.077 478.119 263.815 481.218 326.882 361.68 323.077 192.239 397.499 326.054 341.382 197.497 444.417 192.239 397.499 326.054 341.382 197.497 444.417 208.332 515.209 197.975 450.676 331.345 468.489 208.332 515.209 197.975 450.676 331.345 468.489 
key_time 5
center_x 337.06
center_y 389.505
color_r 1.0
color_g 1.0
color_b 1.0
color_a 1.0
vertex_data 481.886 394.776 381.427 443.925 479.736 329.122 481.886 394.776 381.427 443.925 479.736 329.122 478.13 263.804 481.228 326.873 361.686 323.067 478.13 263.804 481.228 326.873 361.686 323.067 192.234 397.483 326.054 341.364 197.492 444.406 192.234 397.483 326.054 341.364 197.492 444.406 208.333 515.207 197.973 450.666 331.35 468.482 208.333 515.207 197.973 450.666 331.35 468.482 
key_time 6
center_x 318.488
center_y 344.685
color_r 1.0
color_g 1.0
color_b 1.0
color_a 1.0
vertex_data 463.534 373.797 332.705 416.325 464.878 303.034 463.534 373.797 332.705 416.325 464.878 303.034 461.974 235.497 464.157 304.892 320.985 283.501 461.974 235.497 464.157 304.892 320.985 283.501 173.442 321.379 319.032 284.152 177.091 396.142 173.442 321.379 319.032 284.152 177.091 396.142 179.328 453.873 175.138 360.982 321.636 421.535 179.328 453.873 175.138 360.982 321.636 421.535 
key_time 7
center_x 318.73
center_y 344.427
color_r 1.0
color_g 1.0
color_b 1.0
color_a 1.0
vertex_data 463.76 373.54 332.94 416.065 465.104 302.778 463.76 373.54 332.94 416.065 465.104 302.778 462.201 235.242 464.386 304.636 321.226 283.243 462.201 235.242 464.386 304.636 321.226 283.243 173.701 321.128 319.277 283.908 177.348 395.885 173.701 321.128 319.277 283.908 177.348 395.885 179.575 453.612 175.389 360.728 321.874 421.282 179.575 453.612 175.389 360.728 321.874 421.282 
key_time 8
center_x 318.97
center_y 344.203
color_r 1.0
color_g 1.0
color_b 1.0
color_a 1.0
vertex_data 464.016 373.315 333.186 415.843 465.36 302.552 464.016 373.315 333.186 415.843 465.36 302.552 462.455 235.015 464.639 304.41 321.466 283.019 462.455 235.015 464.639 304.41 321.466 283.019 173.924 320.897 319.513 283.67 177.573 395.659 173.924 320.897 319.513 283.67 177.573 395.659 179.809 453.391 175.62 360.5 322.118 421.053 179.809 453.391 175.62 360.5 322.118 421.053 
key_time 9
center_x 308.266
center_y 284.72
color_r 1.0
color_g 1.0
color_b 1.0
color_a 1.0
vertex_data 449.489 345.289 312.034 371.232 452.634 257.85 449.489 345.289 312.034 371.232 452.634 257.85 453.865 192.796 451.674 268.176 334.948 217.506 453.865 192.796 451.674 268.176 334.948 217.506 170.132 223.411 333.215 217.507 167.326 294.955 170.132 223.411 333.215 217.507 167.326 294.955 162.666 376.644 164.068 342.014 229.867 375.061 162.666 376.644 164.068 342.014 229.867 375.061 

Incorrect starting frame when using -ss #{startt}

I'm using the following expression to get a part of the video (24000/1001 fps)

"#{encbin}" -ss #{startt} -sn -an -i "#{inpath}\#{input}" -vframes #{lenf} -c:v libx264 -r 24000/1001 "#{prefix}/#{output}[#{startf}-#{endf}].mp4"

With the following values
#{encbin} = ffmpeg; #{startf} = 10655; #{endf} = 10720; #{lenf} = 65; #{startt} = 444.38

#{startt} is inaccurate. It is taken from the line of the starting frame instead of being calculated using the video's framerate. The actual time for the starting frame should be
10655 / (24000 / 10001) = 444.4022916667.

Would be nice if this could be fixed.

Trim Issue

Encoding error:
x264-r2901-7d0ff22.exe : x264 [error]: not compiled with MP4 output support
At line:1 char:38

  • ... er\Videos"; & "C:\Users\User\Downloads\Programs\x264-r2901-7d0ff22.ex ...
  •             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    • CategoryInfo : NotSpecified: (x264 [error]: n... output support:String) [], RemoteException
    • FullyQualifiedErrorId : NativeCommandError

If there is no log before this, your encoder is not a working executable or your encoding command is invalid.

[Please, Help Me. Thx]

Ctrl+A functionality addition

It would be a great time saver when replacing the data/file location in the input field, to be able to use Ctrl+A to select all the text instead of having to right-click > select all and then subsiquently delete it.

Exception with mal-formatted data

I initially temp-saved the data into a text editor, which replaced all tabs with spaces (which I only found out to be a problem later). I replaced most of the wrong spaces with tabs again using regualr expressions, but one was missing: the first line in the Rotation section. Don't ask me how that could happen.

While I would normally suggest to accept spaces as well, I guess relying on correctly formatted data is reasonable and simplifies the parsing since all separators are tab characters. Either way, it would probabaly be better if the error was caught.

The Traceback:

Lua reported a runtime error:
    File "C:/Users\Fichte\AppData\Roaming\Aegisub\automation\autoload\Aegisub-Motion.moon", line 476
<anonymous function at lines 350-489>
    File "C:/Users\Fichte\AppData\Roaming\Aegisub\automation\include\a-mo\MotionHandler.moon", line 89
applyMotion
    File "C:/Users\Fichte\AppData\Roaming\Aegisub\automation\include\a-mo\MotionHandler.moon", line 167
method
    File "C:/Users\Fichte\AppData\Roaming\Aegisub\automation\include\a-mo\DataHandler.moon", line 107
calculateCurrentState
attempt to perform arithmetic on a nil value

The Data: http://dpaste.com/0WMR05K (github auto-replaces tabs with spaces in comments)

"Theoretically it should be impossible to get this error"

Trying to trim another file resulted in the following error
Aegisub thinks your video 0 frames long. Theoretically it should be impossible to get this error.

aegisub_trim

Video details in Aegisub
aegisub_video_details

More video details from MediaInfo
aegisub_video.txt

So if it's theoretically impossible, is there even an explanation for it 🤔

Option to remove extradata info?

The extradata is great for keeping scripts clean while you work on them, but once you're happy with a sign, you're left with a bunch of invisible data bloating script sizes.

I don't suppose it's possible to add an option to remove that data?

trim's not working.

so i'm using trim for the first time (on Aegisub 9487-cibuilds-277d1e15c.).
and using the ffmpeg encoder, when i click on the trim option it shows the command prompt and goes like

Directory: E:\animes\[MTBB] Monogatari Series (BD 1080p)\01 - Bakemonogatari

Mode LastWriteTime Length Name


d----- 2/7/2024 12:54 PM encoded

and closes after without trimming or encoding the selected line. is there any solution for it? (haven't used x264 encoder yet)

FFMpeg custom command (mp4 output) don't work with mocha (black white frames)

the default command generates too low quality .jpg and gives problems if you do a 1 minute trim (since prefix doesn't work).

So I searched for a commando for ffmpeg and found 2:

"#{encbin}" -ss #{startt} -sn -an -i "#{inpath}\#{input}" -vframes #{lenf} -c:v libx264 -r 24000/1001 "#{prefix}/#{output}[#{startf}-#{endf}].mp4" from #45

"#{encbin}" -ss #{startt} -sn -an -i "#{inpath}/#{input}" -to #{endt} -copyts -map 0:v "#{prefix}/#{output}[#{startt}-#{endt}].mp4"

both do the trim ... Except that when opened on mocha the frames are all black or white.
If you open the file on mediainfo under duration (in general):
For the first command it is the duration of the source video file (ex, 1 hour instead of 2 seconds);
For the second command it is the duration in the -to parameter (ex, 44minutes and 21seconds instead of 2seconds);

First Command:
image
image

Second Command:
image
image

I don't understand how to fix

Lua error when applying

Hi,

Having just heard of your awesome tool I gave it a spin, but every time I select apply I run into this error:

Lua reported a runtime error:
File "/home/alucryd/.aegisub/automation/autoload/Aegisub-Motion.moon", line 347
<anonymous function at lines 324-449>
File "/home/alucryd/.aegisub/automation/include/a-mo/DataWrapper.moon", line 33
bestEffortParsingAttempt
attempt to index local 'input' (a nil value)

I tried v1.0.0-beta2 with aegisub 3.2.2 and its latest git on Arch Linux, both gave me the same error. After reading about issue #10 I also tried deleting ~/.aegisub/aegisub-motion.json but it didn't help. Any idea where it might be coming from?

Support for karaoke effects

At the moment, karaoke'd lines are not properly handled. The lines generated all have the same karaoke markers as the original line, effectively overriding the karaoke effect.

Ideally, they should be updated in a similar way to the \fade tag, with each marker being offset depending on the frame, to preserve the original karaoke effect.

Problem trimming the video

If I trim a line using x264, the output video is not what I chosen as start and as end in the subs.
This script trim a completely different part of the video.

Is there any way I can fix these Trim errors?

I couldn't find a solution anywhere on the net, hope someone can help.
The first error I get is when I put the subtitle file on the video. The second one is when I do it the other way round, i.e. put the video file on the subtitle.
image
image

Trim is outputting off-by-one frames

When using A-mo's Trim option, the frame numbers in the file title seem to be as requested, but the resulting image frames are one frame early.

As an example:

  • Line is timed to frames 100-120
  • A-mo output has correct filename [100-120]
  • A-mo output will have images from frames 99-119 instead

Lua error

I've been having this issue for quite a while now.
I installed my operation system anew, and installed a fresh Aegisub (the latest version, 3.2.0 64bit) and copied the script and the config file into the autoload folder. The script was working for a while (although I was only using it for trimming the videos) but I had to change the commands for x264 to make it work (no matter which version of x264 is used, it does not do anything). When I changed it today and click "Write local", the script started to give me error messages. Now, whenever I click any of the options (Apply/Trim/Config) I get this:

Lua reported a runtime error:
File "C:/Program Files\Aegisub Motion\automation\autoload\Aegisub-Motion.lua", line 1637
<anonymous function at lines 1633-1736>
File "C:/Program Files\Aegisub Motion\automation\autoload\Aegisub-Motion.lua", line 1564
readconf
attempt to index local 'val' (a nil value)

I tried reinstalling Aegisub and downloading+copying the script files again, but I still get this message. What did I do wrong?

Thanks for your help in advance.

Trim Error

I just installed Aegisub-Motion and added the x264 encoder in Trim Settings, yet when I attempt to trim the clip I need I keep getting this error message:

Encoding error:
x264_x64.exe : mp4 [info]: audio muxing feature is disabled.
At line:1 char:89

  • ... \Season 1"; & "D:\Aegisub\mcf\x264_x64.exe" --crf 16 --tune fastdecod ...
  •             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    • CategoryInfo : NotSpecified: (mp4 [info]: aud...re is disabled.:String) [], RemoteException
    • FullyQualifiedErrorId : NativeCommandError

ffms [error]: could not create indexer
lavf [error]: could not open input file
raw [error]: raw input requires a resolution.
x264 [error]: could not open input file `F:[Pog42] Bakuman Seasons 1-3 (BD 1080p HEVC x265 10bit FLAC)\Season 1/ep9
[983f5a98].mkv' via any method!
mp4 [error]: failed to finish movie.
If there is no log before this, your encoder is not a working executable or your encoding command is invalid.

Does anyone know a way to help solve this? Or am I simply missing something?

Been getting this error lately

After upgrading this error kept popping up

Lua reported a runtime error:
File "C:/Users\Mdai\AppData\Roaming\Aegisub\automation\autoload\Aegisub-Motion.lua", line 1722
<anonymous function at lines 1706-1775>
attempt to index a nil value

trim not recognizing crf option in ffmpeg

[Disclaimer: I see that there are several open issues related to trim right now. At first glance my issue appears unrelated to any of those, though I may be mistaken.]

When I try to trim a line using ffmpeg it fails with the following output:

Encoding error:
ffmpeg version n5.0 Copyright (c) 2000-2022 the FFmpeg developers
  built with gcc 11.2.0 (GCC)
  configuration: --prefix=/usr --disable-debug --disable-static --disable-stripping --enable-amf --enable-avisynth --enable-cuda-llvm --enable-lto --enable-fontconfig --enable-gmp --enable-gnutls --enable-gpl --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libdav1d --enable-libdrm --enable-libfreetype --enable-libfribidi --enable-libgsm --enable-libiec61883 --enable-libjack --enable-libmfx --enable-libmodplug --enable-libmp3lame --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-librav1e --enable-librsvg --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtheora --enable-libv4l2 --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxcb --enable-libxml2 --enable-libxvid --enable-libzimg --enable-nvdec --enable-nvenc --enable-shared --enable-version3
  libavutil      57. 17.100 / 57. 17.100
  libavcodec     59. 18.100 / 59. 18.100
  libavformat    59. 16.100 / 59. 16.100
  libavdevice    59.  4.100 / 59.  4.100
  libavfilter     8. 24.100 /  8. 24.100
  libswscale      6.  4.100 /  6.  4.100
  libswresample   4.  3.100 /  4.  3.100
  libpostproc    56.  3.100 / 56.  3.100
Unrecognized option '-crf'.
Error splitting the argument list: Option not found
If there is no log before this, your encoder is not a working executable or your encoding command is invalid.

I looked up the unrecognized option '-crf' part, which led me to this answer suggesting that the problem derives from ffmpeg not being compiled with the --enable-gpl and --enable-libx264 options, but as you can see in the above output, it does include those options, so I'm not sure what's going on here.

I am using the typesetting tools fork of Aegisub, commit 9266-master-f21d8a360 if the title bar is to be believed. I installed Aegisub-Motion through Dependency Control. Looks like it's at version 1.0.9.

Any help is appreciated.

Error after upgrade, before it was working...

Error Message


Script info:
Name: a-mo.Aegisub-Motion.moon
Description: Error initialising Lua script "a-mo.Aegisub-Motion.moon":

[string "C:/Users\Sawlyn\AppData\Roaming\Aegisub\autom..."]:61: Error: [DependencyControl] Error: one or more of the modules required by Aegisub-Motion could not be found on your system:
— a-mo.MotionHandler (v1.1.7)
—— Reason: fetch of module 'a-mo.MotionHandler' succeeded, couldn't be located by the module loader.
nil
Author:
Version:
Full path: C:\Users\Sawlyn\AppData\Roaming\Aegisub\automation\autoload\a-mo.Aegisub-Motion.moon
State: Falha ao abrir

Features provided by script:

[OK]


Line length not calculated from motion data (nil)

If I understand this correctly, Aegisub-motion does not calculate the number of lines the exported motion data takes up and reports it as being (nil):

apply motion error

Using r8700 build of Aegisub and v1.0.0 beta 5 of Aegisub-Motion.

Allow the user to choose the two anchor frames to use for linear interpolation.

In some cases, the first and last frames of an animation may not be the best frames to use to calculate the starting and ending position of a linear transform. There are a couple of complications that arise when considering implementing this:

  • There is no good place in the user interface to stick two more number edit fields that will be completely useless most of the time.
  • Should this allow applying linear motion to segments that are longer than the tracking data? This could potentially result in unintuitive behavior.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.