Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TAStudio ArgumentOutOfRangeException at read-only movie end #13

Closed
GoogleCodeExporter opened this issue Jun 22, 2015 · 2 comments
Closed

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Open a movie in read-only mode. For testing purposes, I used 
http://tasvideos.org/1715M.html .
2. Open TAStudio.
3. Wait until end of input.

What is the expected output? What do you see instead?
At end of input, an ArgumentOutOfRangeException is thrown; see 
http://bayimg.com/mAndLAAdg . After closing the exception dialog, Bizhawk 
crashes.

What version of the product are you using? On what operating system?
r1957, Win7 x64

Please provide any additional information below.


Original issue reported on code.google.com by stop.squark on 19 Mar 2012 at 2:33

@GoogleCodeExporter
Copy link
Author

Fixed. TAStudio does substring operations on the movie mnemonic strings to set 
the controller pads. When the movie ends, the mnemonic strings are empty, and 
doing substring operations on an empty string is probably going to cause some 
out of range issues. I just added a condition to prevent this from happening 
and it seems to work.

Note: In your screenshot, your frame numbers are shown in full. For whatever 
reason, 5 digit numbers are displayed as 10..., 11..., etc. on my computer. I 
think this might have to do with my operating system and not any recent changes 
to TAStudio. Let me know if you don't have this issue on the latest revision.

Original comment by brandman...@gmail.com on 27 Mar 2012 at 7:53

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

Verified fixed in r2098; thanks. The problem with the TAStudio 5-digit frame 
count being displayed as XX... is because the frame column in the table is too 
narrow, in the screenshot I already worked around this problem by increasing 
the column size by dragging in the table header. I'll file a new issue for this.

Original comment by stop.squark on 30 Mar 2012 at 10:52

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant