Latest several betas showing double date in recordings

[Ronstang 293]

I think this is something new but I didn't try to record a movie in a long time previous to .24 but the date in parentheses in the folder and filenames are now in there twice.  Strange but kind of funny.  There is a picture below.

At first I thought my wife had spiked my drink.

[Luke 42077]

Hi, I don't think there's any change here. I think this is just caused by the guide data having the year at the end of the name which up until now has not been typical.

So the recording process needs to be updated to check for this and not double it up if it's already there.

[Ronstang 293]

Not really understanding what you mean Luke.

8 minutes ago, Luke said:

I think this is just caused by the guide data having the year at the end of the name which up until now has not been typical.

Look at this picture below and pay attention to the last column which is date created, my emby recordings have ALWAYS had the date at the end of the file in parenthesis.

[Ronstang 293]

Oh, by the way Luke, the very same guide data in my stable 4.8 server has the date only once.

[Ronstang 293]

Thanks again Luke, it's fixed, great job!  I appreciate it.

You're not going to believe this one.  I was going to post an issue that I found baffling.  Running parallel servers recording the same content I found an issue with the beta.  I edit with VRD6 and streaming content usually does not show errors but almost every recording in the bet server showed small errors where 3-12 audio or video frames needed to be removed to maintain sync.  But the same recording in the the same time slot on the stable server showed no such errors.

Well after editing an entire day of movies there seem to be no errors in the beta now.  Very strange, it appears you fixed something by accident. 

[Ronstang 293]

Crap, I spoke a little too soon.  The double dates are gone in the folder names but not the filenames, they still have a double date.

[Ronstang 293]

Thanks again Luke!!   It is fixed now as of last night's new beta release. 

[Ronstang 293]

The errors are back in the recordings, and this is streaming.  I am parallel recoding with the stable server and the exact same program for the same channel at the same time slot recorded with it are fine.  I am not even sure how this is possible.  Do you have any idea what could be causing this?  It's kind of important because I don't want to use the stable server because the navigation error will NEVER be fixed in that.

[Luke 42077]

Hi, what errors are back?

[Ronstang 293]

Every recording I make then goes into Video Redo TV Suite 6 to edit out the non program parts.  For movies this is just the lead in an lead out but for TV shows it is all the commercials.  Upon saving the edits VRD6 performs a quickstream fix and if it finds any errors it corrects them but that does not mean the results are not marred in some way.

This is streaming, not cable TV.  I used to have all kinds of errors with cable TV recordings but expect non with streaming.  This is really only an issue with moves from TCM but when I edit and save a movie that was recorded with the beta server I get some minor errors like up to 10 audio resync frames removed and sometimes video resync frames. This is to keep the audio and video in sync upon saving the edit.

Now the exact same movie recorded at the same exact time on the same exact channel using the stable 4.8.x server has ZERO errors upon saving the edit using the exact same cut points.  So something is happening in the beta server when recording that is not happening with the stable.

When you corrected the double dates in the folders only the errors ceased but once you corrected them in the filenames too in the latest beta they came back.  Now this is not on every movie recorded but the lion's share, but it is annoying having to edit to find errors only to load up the other recording to then have no errors.  It's a waste of time.  I would just use the stable server but that still has the navigation problem and you told me that would never be corrected.

These two servers record to totally different drives BTW.

Edited September 11, 2025 by Ronstang

[Luke 42077]

All that happened was the file name changed.

[Ronstang 293]

5 hours ago, Luke said:

All that happened was the file name changed.

I'm not accusing you of anything Luke, you have been really great about this so I am not complaining but relaying information to you is all.  I am not making this up.  I am going to start up my old idle server that is complete with a fresh install of Windows 11 and the beta emby server already installed.  I will update it and then add the new streaming TV guide data and make a second parallel recording of TCM to see what happens.

[Ronstang 293]

I'm trying another experiment first Luke.  I created a different recording repository on a different drive to see if this SSD is too old and maybe having errors.

Edited September 12, 2025 by Ronstang

[Ronstang 293]

No difference there Luke, I will get the second server going later if I have time.  Just in case for another point of test is there a way I can step back to the beta that fixed the double dates in the folder but not the file itself?  That seems to be the only version I didn't get errors in my recordings on the beta.

[Ronstang 293]

Got the second machine back online and installed Channels and added it to emby and recorded the same movies as on my normal machine last night.  I am running the stable emby and the beta on my normal machine and only the beta on the second machine.  The beta servers are both portable installs where the stable is an actual install.  My main machine is Windows 11 and the second is Windows 10.

Upon editing the same movies this morning on both machines recorded using the beta servers I get interesting results.  My main machine's beta server records movies will small errors that are detected by VRD6 but the same exact movies recorded on the second machine do not show the same errors.  So the problem is NOT the beta server but something else.

Could the problem be running 2 servers on the same machine?  Could it be as simply as just reinstalling the beta on the main machine?  I will have to try this when I have time.  I am now stumped, any ideas Luke?

[Ronstang 293]

Not sure what is going on but the latest beta seems to have corrected this issue.  I'll keep my fingers crossed.