Closed theowocat closed 1 month ago
I guess (as you said) that this error happens because you didn't pass the mediaparam "video", so the main problem is the error catching.
a correction would be :
if len(ctx.message.attachments) < 1:
await ctx.reply("Please add a video.", ephemeral=True)
elif not(ctx.message.attachments[0].url.endswith(".mp4")):
await ctx.reply("Bad format, please send a mp4.", ephemeral=True)
...
else:
await process(ctx, processing.ffmpeg.mp4togif, [["VIDEO"]])
P.S : There is the same issue for almost every conversions.
EDIT: The issue is already solved.
The error in question here isn’t about the source media, it’s that somehow the gif conversion function just isn’t returning anything. By default, MediaForge scans the channel for media and errors prematurely if nothing is found https://github.com/HexCodeFFF/mediaforge/blob/8e2ee00270947f55355e9f9f23f08f2f02e475c8/src/core/process.py#L148-L153
MediaForge doesn’t actually support sending attachments via slash commands it requires you to send them in the channel first then run the command where it will scan for attachments
merged into #208
Describe the bug
/togif
with nothing replied to just raises an error with a traceback to report as an issue.Traceback
Expected Behavior
/togif
with no arguments sending a message like "❌No argument given".Steps To Reproduce
/togif
command without anything being replied toAnything Else
No response