RecORDER 2.1.1

[PixlPixi]

Hello,


Good to hear you found the issue - normally you should run OBS as an administrator (to avoid issues with the process permissions and such), so I just coded it this way and assumed most people would run it this way, my bad.
About this unicode character - sadly is not supported even in normal windows files (see below), so I cannot really counteract it, although I agree it looks better than YY-MM-DD or any other format, but I can only assume it has a special meaning inside of Windows or any OS at this point.
View attachment 107414

Also, worth noting and it's kind of my own fault - I experimented a lot with the script between the versions, so it caused some discrepancies and bugs, but right now I'm working on releasing a script version that should work, I should be done soon, because the tests are looking good.

I also hadn't been checking this forum much as of late, but I'm glad to see that my feature request was implemented. I can't wait to try it out now so thank you for all your hard work on this script.

As for the unicode issue I knew that the regular : symbol couldn't be used by windows file system for naming files, but I found a special character that looks almost identical and did work for a time when using this script and it broke at some point either from an update or some other setting I had changed. It was called a modifier letter colon and it's character map code was U+A789 and it looks like a smaller version of the standard : only it is supported by windows for file names. If it's too big of a hassle to fix then I understand, you've already done enough work making this script in the first place and I greatly appreciate that.

 

[oxypatic]

I also hadn't been checking this forum much as of late, but I'm glad to see that my feature request was implemented. I can't wait to try it out now so thank you for all your hard work on this script.

As for the unicode issue I knew that the regular : symbol couldn't be used by windows file system for naming files, but I found a special character that looks almost identical and did work for a time when using this script and it broke at some point either from an update or some other setting I had changed. It was called a modifier letter colon and it's character map code was U+A789 and it looks like a smaller version of the standard : only it is supported by windows for file names. If it's too big of a hassle to fix then I understand, you've already done enough work making this script in the first place and I greatly appreciate that.

Hope it will work for you.

As for the character - maybe it can work in the newest version of the script, because I changed the function to move from `os.rename` to `shutil.move` but afaik they are using the same methods, so might not work at all.
I cannot really change for the system works, as my script operates on higher level than the OBS itself, maybe it is using a special way of creating files, which I don't know about.
I will try to take another go at the issue, but I think it might not work.

 

[PixlPixi]

Hope it will work for you.

As for the character - maybe it can work in the newest version of the script, because I changed the function to move from `os.rename` to `shutil.move` but afaik they are using the same methods, so might not work at all.
I cannot really change for the system works, as my script operates on higher level than the OBS itself, maybe it is using a special way of creating files, which I don't know about.
I will try to take another go at the issue, but I think it might not work.

Well as mentioned you've already done more than enough work getting this script to work so I really don't want to be demanding. If the issue is resolved then great, but if not I have a work around. I'll test it out real quick and see how it works. It used to work prior to me updating OBS so for all I know the issue is on their end.

UPDATE: It works again! Just tested and the screenshot was moved correctly and given the proper name. I love this script!

 

[oxypatic]

oxypatic updated RecORDER with a new update entry:

1.6 - Gotta optimize them all!

Hi all!


It was a long time since I posted any updates on my script, since I feel like this is the way I like it for now.
Different things happened in my life and I had new experiences as well, which make me have better overall sight on my script, so I might try doing some work in the background about re-writing parts of code that make me cringe from the implementation.


But of course there still might be bugs to fix or features that you would like to see, so feel free to let me know about...

Read the rest of this update entry...

 

[oxypatic]

oxypatic updated RecORDER with a new update entry:

Thank you for 3,000 downloads!

Hello everybody!

Just recently my script has hit 3,000 downloads, so I wanted to share some warm words as well as my thanks for using it!

View attachment 112555

I know my script might not be the best quality, but my first and most important thought behind it was to make it as universal as possible. There are probably different scripts that work better than mine, but I'm still happy that so many of you decided to give my script a go!

If you have any ideas or you need some...

Read the rest of this update entry...

 

[oxypatic]

oxypatic updated RecORDER with a new update entry:

2.0 - Reworked and unborked!

Hey hey people, oxy here!​

I am still alive, despise the (almost) year silence (I hope my script was treating you right).

There was a lot of thing happening in my life and I was all over the place.
I grew as a programmer (as a person too) and learned lots of stuff to improve my future code.
Then I finally got to do some working on the RecORDER.

I'm going to be frank with you - I used the AI available in Visual Studio Code to help...

Read the rest of this update entry...

 

[oxypatic]

oxypatic updated RecORDER with a new update entry:

2.1 - We made the boo boo better :)

Hello everybody, oxy here!​

Another surprise this year!
I got inspired by some muse (or bard too happy to cast bardic inspiration) to do more changes to the script, improve it and hopefully made it even nicer to use.
Got rid of old, unused things, focused to make things simpler so the usage of script is more straight-forward, allowed some customization for the user and added option to check if there was an update to the script.

Anyway, I hope that as always, you...

Read the rest of this update entry...

 

[PixlPixi]

Hadn't updated in a while and decided to since I saw this was getting some updates. I'm getting an error when I enable the replay feature, but other than that everything is working fine. The videos and screenshots get organized properly.

This is the error I'm getting.

[RecORDERv2-1.py] Traceback (most recent call last):
[RecORDERv2-1.py] File "C:\Program Files/obs-studio/data/obs-plugins/frontend-tools/scripts\RecORDERv2-1.py", line 590, in global_event_handler
[RecORDERv2-1.py] handler()
[RecORDERv2-1.py] TypeError: 'tuple' object is not callable

Not sure if I'm doing something wrong. I've added every source name to the file for every scene that I typically use.

 

[PixlPixi]

Hadn't updated in a while and decided to since I saw this was getting some updates. I'm getting an error when I enable the replay feature, but other than that everything is working fine. The videos and screenshots get organized properly.

This is the error I'm getting.

[RecORDERv2-1.py] Traceback (most recent call last):
[RecORDERv2-1.py] File "C:\Program Files/obs-studio/data/obs-plugins/frontend-tools/scripts\RecORDERv2-1.py", line 590, in global_event_handler
[RecORDERv2-1.py] handler()
[RecORDERv2-1.py] TypeError: 'tuple' object is not callable

Not sure if I'm doing something wrong. I've added every source name to the file for every scene that I typically use.

I'll add that I'm really excited for this update as I think it makes it possible for me to capture and sort the recordings of multiple sources finally. I had an issue before where Minecraft Bedrock edition could capture perfectly fine when OBS was specifically looking for that game, but failed to capture properly when using "Capture any fullscreen application". The problem is I would have to change that setting each time in order for RecORDER to recognize and sort these captures since using a secondary source that points specifically to this one game didn't work before.

 

[oxypatic]

I just saw the issue with the code that causes that, let me do a quick fix and upload that on site.
As for your problems, I am not sure if I understood that right, but it seems to be the problem with OBS itself, if Game Capture does not work, it might be good to use the Window Capture instead.

 

[PixlPixi]

I just saw the issue with the code that causes that, let me do a quick fix and upload that on site.
As for your problems, I am not sure if I understood that right, but it seems to be the problem with OBS itself, if Game Capture does not work, it might be good to use the Window Capture instead.

If you're referring to the reply I left, basically OBS can recognize the game if I tell the source to capture the specific program. I could have a different source capture the game and everything will look fine, but if it wasn't using the same source it wouldn't get sorted because RecORDER previously asked me to specify which source I wanted to record. If I'm understanding this new version correctly that should mean that it now allows for the sorting of multiple different sources so long as they're specified in the script.

 

[oxypatic]

I think I understand your issue.
Generally, you do not want multiple sources that can hook into the windows in the same scene (that can cause issues, but I understand it's easy to use).
The way I used it before I went for "one hooking source (like Window Capture) - one scene" approach was that I hid the other source from the list using an eye icon.

 

[oxypatic]

As for recording different sources at the same time, it should be possible, but make sure that inside of script, the main one (the one that you want to use as a organization point) is first between "[]" characters.

 

[oxypatic]

I want to let my users select which source should be used as a organization point, but only recently I got time to actually program, so hopefully I get some more time and put this feature in 2.2 version of the script :D

 

[oxypatic]

oxypatic updated RecORDER with a new update entry:

2.1.1 - Hotfix: 'tuple' object is not callable

Hello everyone, oxy here!​

I did a oopsie in the code that made the Replay Buffer method included incorrectly into the dictionary of events.
Here's a quick fix for this situation, because I have to move my bottom to do some shopping.

Have fun recording!

Read the rest of this update entry...

 

[PixlPixi]

I think I understand your issue.
Generally, you do not want multiple sources that can hook into the windows in the same scene (that can cause issues, but I understand it's easy to use).
The way I used it before I went for "one hooking source (like Window Capture) - one scene" approach was that I hid the other source from the list using an eye icon.

Well I just gave it a test when playing Minecraft and it worked perfectly. This is the best update I could've asked for. I've also done the same thing you mentioned with having different scenes to record different programs, but the issue is that the name needs to match and the source in order for it to hook properly and making any changes to that source will change it for the other scenes which use the same source. I've tried everything i can to make this easier when recording but sometimes i forget to change the source back to record fullscreen games and the plugin i have to auto-enable the replay when it detects a game doesn't work because I'm not playing the same game that I told OBS to search for.

This update really is fantastic. Thank you so much for the work you've put into this.

 

[oxypatic]

A little teaser of what I will be working on