VideoReDo TVSuite 6 *still* giving me problems. . . . :-(

pyatrus

New member
I've gone back to version 5 a couple of times because of the problems with version 6. Every release of version 6 seems unstable, IMHO. :-(

I'm using: Version 6.62.4.827 - Release date: 2020-12-26 & have had similar disappointing results with 2 or 3 previous releases of version 6. Is it a memory issue? Did version 5 manage memory better? use less memory?

Currently, version 6 frequently "dies" in the "not responding" mode when I select "Save Video As" (a DVR'ed .ts file). No matter how long I wait, it doesn't recover.

Does VideoReDo TV Suite 6 "hate" Windows 10 Pro 64-bit or ??

Is it time for me to go back to version 5 again? (Since every release of version 6 behaves as tho it were beta-ware for me.)
 
Last edited:

Dan203

Senior Developer
Staff member
I've gone back to version 5 a couple of times because of the problems with version 6. Every release of version 6 seems unstable, IMHO. :-(

I'm using: Version 6.62.4.827 - Release date: 2020-12-26 & have had similar disappointing results with 2 or 3 previous releases of version 6. Is it a memory issue? Did version 5 manage memory better? use less memory?

Currently, version 6 frequently "dies" in the "not responding" mode when I select "Save Video As" (a DVR'ed .ts file). No matter how long I wait, it doesn't recover.

Does VideoReDo TV Suite 6 "hate" Windows 10 Pro 64-bit or ??

Is it time for me to go back to version 5 again? (Since every release of version 6 behaves as tho it were beta-ware for me.)
Does it die before it displays the save dialog? Or after you click save?
 

musicvid

Member
One thing you can try is updating your graphics drivers to the latest stable version.
If you have Nvidia, the Studio drivers are better suited to video rendering than the gaming version.
 

JS_VRD

New member
Hi

I agree with pyatrus and currently have a support ticket raised. I too have experienced the "not responding" issue when opening *.ts files as well as saved project *.Vprj files.

My main ticket concern however was when heavily editing a large *.ts file and scrubbing video quickly both in forward and reverse directions would cause the "not responding" issue to manifest itself. The only work around at the moment is to save the edits as *Vprj at each edit point until some solution becomes available. V6 beta 828 still exhibits the "not responding" issue when opening ts and/or vprj files.

I'm not sure exactly the point in time that VRD6 started to become unstable. For me V6 initially was fine however since there have been that many updates to windows 10,
I'm not sure if this is also contributing to the issue.

I also have the latest nVidia studio drivers installed but no luck thus far

Cheers
 

jmc

Active member
I've found it best for me NOT to edit TS files but to convert h264.TS to h264.MP4 with audio sync and QSF then do my editing.
My (OBS) TS files are generally spastic and twitchy. :)
 
Last edited:

Winnewup

Member
I don't have issues with the actual beta 828a and ts-files. I usually only use ts-files (720p, 1080i) recorded with satellite receiver (dreambox).
Maybe it has to do something with the recorded files and the details of the file format.

Regards
Frank
 

JS_VRD

New member
As I mentioned earlier V6 was fine for some time and I have been using ts files for many years even with V5 and not had issues. I personally don’t believe it’s the ts file but something else may be impacting on VRD.

Anecdotally I would have to guess that windows 10 (for me) may be a suspect here and perhaps VRD developers may need to look at how VRD manages resources under win10, but I’m just guessing

Cheers
 

bdg2

Member
I've found it best for me NOT to edit TS files but to convert h264.TS to h264.MP4 with audio sync and QSF then do my editing.
But what if you can't even get QSF to accept the .ts files?
I have many short H.264 .ts files from HD satellite channels and they will not open.
Open Video says "No PIDs specified when trying to open a transport stream." and QSF just says "Unable to open file.".
 

JS_VRD

New member
Hi JMC

If you are getting PID errors, then try changing parameter 5 under manual options (Number of times a PMT has to be read when opening a file) from 10 to 30
To access manual options hold down SHIFT key whilst selecting Tools/Options

I think running QSF is just adding to the work load of editing big files and a suitable solution should ideally be made by VRD developers in the long run
Cheers
 

jmc

Active member
-----------------------------Some info on PID problems from my VRD_Fixes.txt file----------------------------
There are 2 things to try:

1. Go to Tools>Options>Stream and increase the number of Mbytes to scan at file open. You can make this value really large, like 100 to 500 MBytes. The downside is that if it's large and an audio stream isn't found it will take a while to give you the warning.

2. If #1 doesn't work, try turning on the "Ignore transport stream maps" which is also on the Tools>Options>Stream page.
--------------------------------------------------------------------------------------------------------

jmc
 
Top Bottom