RecORDER

RecORDER 1.5.1

PixlPixi

New Member
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

New Member
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

New Member
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!
 
Top