Comments

Log in with itch.io to leave a comment.

You. Are. AWESOME.

Hello! I am having an issue with the Mac ARM version of this plug in. 

I am getting this error output when booting up the test room as well as my own project. I cross develop on a Windows computer and a Mac Laptop. Everything works fine in the windows environment. I am using your latest version.


ERROR: Can't open dynamic library: /Users/kenziekatsu/Downloads/gde_gozen_test_room_v6.1.1/addons/gde_gozen/bin/macos_arm64/debug/libgozen.macos.template_debug.arm64.dylib. Error: dlopen(/Users/kenziekatsu/Downloads/gde_gozen_test_room_v6.1.1/addons/gde_gozen/bin/macos_arm64/debug/libgozen.macos.template_debug.arm64.dylib, 0x0002): tried: '/Users/kenziekatsu/Downloads/gde_gozen_test_room_v6.1.1/addons/gde_gozen/bin/macos_arm64/debug/libgozen.macos.template_debug.arm64.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/Users/kenziekatsu/Downloads/gde_gozen_test_room_v6.1.1/addons/gde_gozen/bin/macos_arm64/debug/libgozen.macos.template_debug.arm64.dylib' (no such file), '/Users/kenziekatsu/Downloads/gde_gozen_test_room_v6.1.1/addons/gde_gozen/bin/macos_arm64/debug/libgozen.macos.template_debug.arm64.dylib' (no such file).

  ERROR: Can't open GDExtension dynamic library: 'res://addons/gde_gozen/gozen.gdextension'.

  ERROR: res://addons/gde_gozen/video_playback.gd:37 - Parse Error: Could not find type "Video" in the current scope.

  ERROR: res://addons/gde_gozen/video_playback.gd:138 - Parse Error: Could not find type "Video" in the current scope.

  ERROR: res://addons/gde_gozen/video_playback.gd:146 - Parse Error: Could not find type "Video" in the current scope.

  ERROR: res://addons/gde_gozen/video_playback.gd:120 - Parse Error: Identifier "Video" not declared in the current scope.

  ERROR: res://addons/gde_gozen/video_playback.gd:390 - Parse Error: Identifier "Audio" not declared in the current scope.

  ERROR: res://addons/gde_gozen/video_playback.gd:405 - Parse Error: Identifier "Video" not declared in the current scope.

  ERROR: modules/gdscript/gdscript.cpp:3022 - Failed to load script "res://addons/gde_gozen/video_playback.gd" with error "Parse error".

  ERROR: Failed loading resource: res://addons/gde_gozen/icon.webp. Make sure resources have been imported by opening the project in the editor at least once.

I noticed that all of the files in the debug and release folder were in a sub folder titled "lib" This was not the path represented in the .gdextension file so I moved all of the files out of that directory into the release and debug directory respectively thinking this was the issue. It was not, libgozen.macos.template_debug.arm64.dylib just actually doesn't exist in the files. I just wanted to bring this to your attention.

Hi and thanks for reporting this issue!

Yeah, that’s why I have the note on the itch.io page saying MacOS should work, but not guaranteed. as I don’t have a Mac machine available to properly test things out. I’ll have a look and see if I can fix this issue and try to get an update out when it’s fixed (and if I can fix it).

At some point in the future I might be able to afford a Macbook so I can make certain that each release will work. ;)

But your comment helps a lot especially with libgozen.macos.template_debug.arm64.dylib not even existing, makes it a lot easier to troubleshoot this! ^^

Understandable. Let me know if and when you update it and I can test it to see if everything works!

Sorry for the wait! I think that I managed to fix the issue in version 6.1.2 ;)

I'm really looking forward to working Web support!
Can we get any timeline?

Sadly, due to limitations with FFmpeg, a web export won’t be possible. At this moment this isn’t going to happen anytime soon, but if I end up making my own video demuxer, this might become possible … however that would be a very big task and take several months if I were to even be able to do this.

If I could find another library which could help with video demuxing for the web, then it could be a matter of weeks, but it’ll still require quite a bit of work and will most likely come with other limitations.

Hey, I was considering purchasing this GDExtension of yours, since it includes the only working Godot video player node on the entire planet. I have a few questions though, if I may.

1. Is it possible to apply a playback speed multiplier to a video, for instance, if I wanted to play a video at 0.75 or 1.25 speed?

2. With the VideoPlayback node requiring an absolute video file path, is it possible at all to access video files inside the res:// directory when running a release build?

(+1)

Hey there, first question is an easy to answer one. For one of the next updates I’ll have video playback speed implemented, main troublesome point at the moment to implement is just audio but I may have found a fix for that one so it should be coming in the next weeks.

At this moment the video files should be in the folder of the executable for it to work, but apparently someone got it working with including the video files in the project itself so I’ll have to get back to you on that one.

Hello! I had been using the 2.0 version from Github for a while and it's been working great! I decided to give this newer version a try (and wanted to support the project).

I ran the sample room just to make sure everything was working for me, but pretty much all videos do not display correctly. They seem to load and begin playback (I can see some movement and hear audio) but the video itself is a bunch of random colored lines.

It's like that for about 90% of videos I'd say. I cannot figure out what is triggering it as it doesn't seem to depend on encoding (videos with same encoding some fail, others don't).

I'll hop on the Discord in a week or 2 to check in. Not a big deal as I will continue using the old version for now. Just thought you might want to look into it. I am running the Windows version on Godot 4.3, default everything.

Thanks for letting me know! Would be helpful to see some error logs to know more of what’s going wrong. I will check to see if I can replicate it, must probably have something to do with the compute shader which is being used so I guess it’s the format which is probably not yuv420p. I’ll make the necessary adjustments and hopefully this fixes it ^^” Sorry about that!