I am using FireCore 1.7 Media Player connected to an SMB share.
After upgrading to 1.7 I have noticed that when playback of a MKV finishes control returns to the top level menu of the share is displayed.
e.g. If I have the following directory structure and file
A to I\Hawaii 5-0\Season 2\mkv\Hawaii.Five-0.2010.S02E02.First.mkv
When playback of Hawaii.Five-0.2010.S02E02.First.mkv finishes a black screen with ‘Loading…’ appears, then the menu at A’ to I’ is displayed .
Confirmed, after every video you are being thrown to the root of the share…
But, when you use longer way to access share (My files → Share…), the it stays in the current folder after the playback…
I like these quick links in the top menu, so the bug is really annoying…
Just tried accessing via My Files and can confirm that it stays in the current folder after playback.
Makes the quick links almost useless, so high annoyance factor on this bug.
Hmmm - we’ll look into it.
I started investigating further last night, and tried playing things from another favorite link and didn’t see the problem.
So I went back to the original episodes where I saw the problem and found I could not reproduce it now. I tried several episodes and each behaved correctly at the end of playback, i.e. I was not returned to the root menu.
I wonder if this could be an problem with corrupted Metadata. I noticed that none of the episodes displayed a description even though descriptions exist in TVDB and the filenames of the episodes seem to be marked up correctly with the Season and Episode numbers.
I also wondered if it was running out memory at the end of playback as it tried to reload the directory information, however I did not see any Low Memory warnings any time I was seeing the problem.
It is simple… 
When you rename Favorite quick link, you will get back to root… When you keep original name, everything is ok:)
Edit: sometimes true, sometimes not, still cannot figure it exactly… 
One more victim over here. I confirm that same behavior. It’s really annoying. I’m using an AFP connection.
Just started having the same problem with 1.7 as well.
Problem still occurring. Is thre any update please.
This should be fixed in the 2.0 update that was released today.
Seems to have sorted it, thanks very much James. Just upgraded so will do more testing over the weekend.