First file, a 1080i30 TS, does not play
Posted: Wed Oct 11, 2017 6:25 am
Hi Subjunk! You might remember me from 3 years ago when I was interacting heavily with you on (I think) the doom9 forum, subforum Avisynth, and your very long thread about Interframe. Every fall (and following), I've been heavily using Interframe. But this season, I need to refrain from writing Avisynth scripts as much as possible. I am racing to hunt down and find solutinos that I thought would be forthcoming but keep running into disappointments. I was bemoaning that I might have to resort to scripts after all, and was reviewing your Interframe web page, where it mentioned THIS (UMS). I never heard of it! Looks like you've done a fabulous job with it from what I can tell.
So I said, "I'll bite". I've installed, and the very first file I wish to play out to my Chromecast Ultra, fails to play. For a couple minutes I see a grey line on a black screen crawling left to right at bottom of TV screen, but nothing of the video plays.
I was startled to not see a menu item to open a video file, but did find it after selecting my Chromecast Ultra. The only two potentially anomalies I can think of are:
1. It's a highbitrate file of a video that is 1080i30, that is, interlaced. H.264, with aac audio. I am really hoping I can get this catagory of file to play and cast.
2. When it asked me to let it install Avisynth 2.6MT, I skipped it for this reason. A few days ago, while researching SVP Pro as a viable solution, it comes out that they use Avisynth+. I was running a script "from the past" and "setmtmode" was an error. Posting on their board revealed that they use Avisynth+. If I didn't want to convert my logic to the new method of multithreading, he said to take my old Avisynth dll and store it where the Virtualdub executable is. I did so, and was able to run my old script again. So.... what's the deal with you having (and requiring me to have) 2.6MT vs SVP's requirement that I have Avisynth+? And was it this issue that prevented my video from playing??
I feel this is pretty basic, but do I still need to collect and send the log as per normal "problem reporting"? I was hoping it was something more simple that wouldn't require that. It's rather discouraging to get a "big new toy", then it not work right out of the box.
So I said, "I'll bite". I've installed, and the very first file I wish to play out to my Chromecast Ultra, fails to play. For a couple minutes I see a grey line on a black screen crawling left to right at bottom of TV screen, but nothing of the video plays.
I was startled to not see a menu item to open a video file, but did find it after selecting my Chromecast Ultra. The only two potentially anomalies I can think of are:
1. It's a highbitrate file of a video that is 1080i30, that is, interlaced. H.264, with aac audio. I am really hoping I can get this catagory of file to play and cast.
2. When it asked me to let it install Avisynth 2.6MT, I skipped it for this reason. A few days ago, while researching SVP Pro as a viable solution, it comes out that they use Avisynth+. I was running a script "from the past" and "setmtmode" was an error. Posting on their board revealed that they use Avisynth+. If I didn't want to convert my logic to the new method of multithreading, he said to take my old Avisynth dll and store it where the Virtualdub executable is. I did so, and was able to run my old script again. So.... what's the deal with you having (and requiring me to have) 2.6MT vs SVP's requirement that I have Avisynth+? And was it this issue that prevented my video from playing??
I feel this is pretty basic, but do I still need to collect and send the log as per normal "problem reporting"? I was hoping it was something more simple that wouldn't require that. It's rather discouraging to get a "big new toy", then it not work right out of the box.