@gagax123 Hey bud, not sure what happened. I recently tried to open OFS but recevied the following error:
I get the same error when using an older version of OFS. Any idea on what may be causing this?
Delete config.json and restart OFS and it should work. You will need to re-configure OFS, but it should start again.
You can always make a copy of the file and then edit the original. It could be invalid characters in the recent files paths stored in the file that are the culprits. Also, if you made a copy and delete the original you can compare restart OFS and close it again and compare the new settings with the old and see if there are something strange in the old one. Opening a ticket in the project @ github with your config file attached could also be an option so that gagax123 can debug it.
I tried deleting the config.json but it reset everything like none of the windows are in the correct position. Is there a way to reset them to their correct positions?
I don’t know, if there is a way to reset the position of the windows.
But you can just drag them and let them snap, to where you want them to be.
Hey, I was wondering if you would be willing to add a new scripting mode or make an adjustment to Alternating Mode. I predominantly script on a laptop which so I’ve been thinking of ways to speed up the scripting process particularly in places where actions are repetitive so i’m just going back and forth from 0-100,0-90, then back to 0-100.
As it stands I use my right hand to navigate so moving forward/backwards, jump to next point and I have the position mapped to keys that i can use with my left hand.
Z-100, X - 90, C - 80, V - 70.
When a motion goes up down, I slow myself down because i now have to use my right hand to the keypad select the corresponding bottom number, <50. I can use alternating mode which helps but there are some rules that I don’t quite understand. So for example, if i key 90, then want to key 0 with the 100 key it actually goes to 100 and not 0.
So my suggestion is if there could be a mode that simply does inverse. So if i press 100, then the next key will have to be sub 50, so in this case if Z is 100, then if I press Z again it gives me 0. If I press X - 90, then if i Press Z it would give me 0, or if I press C, it would give me 20. If i double pressed it would take me back to the number above 50.
I hope you kind of get what i’m saying and hopefully it wouldn’t be something too difficult to implement. Not sure how helpful it would be to others but if others use a laptop to script i think it would speed up back and forth movements considerably.
Type %appdata% in the windows menu search bar and delete OFS folder that’s there. It will reset all windows and your settings. Just make a backup before doing that.
I showed it in the 2nd part of my video tutorial, it’s should be somewhere near the beginning:
1 Like
Yea I knew that but for some reason, I can’t get the controls & Time to snap into the correct bottom positions. They key getting tabbed together which isn’t what I want.
That’s why i thought if there was a way to just reset them all to their original posiiton it would be helpful
Yes, that worked. Thank you, that was nice & easy
small release
Deleting “imgui.ini” resets everything.
I tried having a reset in the UI but that broke more than it helped.
Technically the imgui docking & the multi-viewport stuff that I’m using are all beta features of imgui.
So right now deleting “imgui.ini” is the way to reset the layout.
Deleting the whole folder obviously resets everything aswell
Also
Alternating mode now alternates every key press instead of looking at previous actions
I think this was all you wanted.
.
2 Likes
Yes!!! Thank you for implementing this so quickly excited to give this a try
I usually make manual copies of the files before I make any bigger change or continue my work.
This one is actually slightly baffling to me. Now if I make a mistake in alternating mode and delete some points to try it again, I have to remember the last input I made instead of just looking at the previous point. Maybe we could just have a toggle for this?
What do you mean by make a mistake??
And that shouldn’t be how it works. If you delete a section and input the next point, in that instance it will alternate from the previous point so if your points were
100-0-100-10-100-0-100-10, and you deleted the points and went back to
100-0-100-10 - __
the next point you input would go back above 50.
I actually like the new alternating mode. Its much faster when it comes to repetitive movements but I’m not sure what your scripting exactly.
I think the new implementation is way better.
Sure a point might end up not where you wanted it initially but the fix is just hitting the same button again and after that you’re in sync again.
I’m adding a label indicating if the next point is inverted or not and for fixed range it’s going to display if the next point is going to be at the defined minimum or maximum.
Also if you make the mistake for multiple points you can select them and “Select”->“Invert” to fix the whole thing. No need to delete and redo anything.
Would it help if “undo” would also undo the alternating mode “state”?
It would be the first thing “undo” would undo which isn’t a script modification 
1 Like
I agree. It usually take me appx 6 min to script 1 min of on screen action. I’m still getting used to it but i’m down to 4.30. In a 45 min scene, 20-25 min of which is repetitive action I’ve saved so much time. so i"m happy about that.
This is actually a good addition, though once you’re in a groove you kind of get where you are.
I personally don’t use it, so i’m fine either way.
That’s definitely true, but this actually reduces speed when you’re trying to script the video live while it’s playing. Take for example if I’m scripting a video while it’s playing, if I go DOWN-UP-DOWN-UP and that last up is just slightly off, I’ll pause and quickly delete it, skip back a few points and start playing again. But when I get to the point I’m correcting, it’ll go DOWN-UP-DOWN-DOWN, (the last point being down instead of up) because it’s doing the opposite of what it did before, not alternating with the last event. Then multiply that a couple billion times over the course of a script and it’s a huge time sink.
any ideas why this application doesn’t accept inputs from a stream deck? its able to perform combinations of hotkey presses like macros so i thought it would be good to program key presses that produce certain patterns. but the program just doesnt seem to accept any sort of input.
Not sure what im doing wrong but any script I make when brought into scriptplayer for testing after I save is playing back at a faster rate then the video. Any