Hi Greg,

first of all: complements on posting the technical details! (most do not even mention the OS or version).

Sorry to hear you're running into issue.

So a few reason an access violation may occur.

Obviously this could be a bug but there could be other reasons - which I'd like to find out so I can write code around the issue and notify the user.

Are you using anything like video detection (enabled ffprobe in preferences) or metadata updating (also in preferences)?
Sometimes "corrupt" video files make ffprobe crash or produce corrupt info (I'd need to see the file to test it myself and see what goes sideways there). You can check the settings and disable ffprobe and metadata updating. Since it happens while adding files, you'll only have to disable ffprobe.

Next could be a problem in the autodetect mechanism - disabled it (bottom right of the main window) and try again.

Then there is the potential problem of special characters in the filename. Maybe you can lis a filename that fails.

Now we are on the topic of filenames: sometimes networkshares are not very stable, even though this is rare. You could try a local file.
Note that access rights could be an issue as well.

I'd probably start with making an empty test file. I did do a little write up on that here. But long story short: right click in Explorer, select “New” and choose “Text Document“. After that rename it to for example "testfile.mp4" (video extension) and see if you get an Access Violation when dropping hat on RMTV. If that causes the Access Violation then I'd temporary move the data directory. This can be:

c:\Users\<username>\AppData\Local\Rename My TV Series

or a "data" directory in the application directory, as you mentioned.

You already mentioned the data directory so just a FYI:
When RMTV is not installed in the default C:\Program Files or whatever Windows designated to be the application directory.
You can find the defaul path like so in CMD/DOS:

echo "%ProgramFiles%"

In your case it should say "E:\Program Files". If not then a "data" directory should be found in the application directory like in your case.
Any chance you can test what happens when using the usual path? (C:\Program Files)
Just so I can narrow it down to my code handling this.

I guess these are a few steps to get started with.
Let me know your findings and thank you for reporting and testing!

@hans Hi Hans,  Thanks for the fast reply!  I disabled ffprobe and it works.  So then I went ahead and re-enabled ffprobe and it still works.  Something must have been stuck.  If I can provide any further info to help you fix the issue going forward let me know.  I will also update this with any additional issues I run into.  You just earned yourself a cup of coffee.  😊 

Thanks,

Greg

Thanks Greg!

Cup-a-Joe is always very much appreciated. 😉 

Let me know if you run into this again (or find new issues). I'd be happy to help.

Thank you as well 😊