Program Bug ...

[misteralexander]

Hello All --

I think I've come across a bug in the program. I have purchased a license and this was the first time I've ever seen go wrong ...

I tried to put in a remote FTP location (a QNAP NAS on my local network) as the save location in the MakeMKV Preferences.

MakeMKV doesn't seem to handle this well, sometimes saying that location doesn't exist, offering to create it under the install directory and other times completely locking the program. When the latter happens, anywhere I click I get a Windows tone alerting me that what i'm doing is not allowed. The only way to resolve this is to kill the process in Task Manager.

I'm not sure the proper place to submit bug reports. I looked on GitHub, but didn't see anything obvious, so I thought i'd ask here.

The format I'm using for the remote is: ftp://user:pass@host:port/PATH

Thanks!

[Woodstock]

To my knowledge, MakeMKV does not do FTP. It works on mappable network shares only.

When data is written, it needs to go back and modify the MKV file once it has reached the end to update the header information. That would not work with an FTP-based network.

If you have not enabled SMB sharing on your QNAP, your only option would be to save the file locally, then FTP it to the QNAP.

[misteralexander]

To my knowledge, MakeMKV does not do FTP. It works on mappable network shares only.
When data is written, it needs to go back and modify the MKV file once it has reached the end to update the header information. That would not work with an FTP-based network.
If you have not enabled SMB sharing on your QNAP, your only option would be to save the file locally, then FTP it to the QNAP.

Yes, I ended up just saving locally, and then uploading. I don't do NFS on the qnap, as I don't like the direct access to the server Windows grants itself.

Thanks!

[Woodstock]

NFS and SMB are different protocols. I don't do NFS either...