-- SOLD --

Thanks

It's fantastic to see this project continuing Calvi, many thanks for all your work keeping it going. nullpointer created something pretty amazing with Web Scheduler, and its good to see it still setting the standard.


EDIT:

EDIT2: Have removed the issue point that was in the above post, my error, it seems to behave as expected, at least from a network browser adding items. Not sure what happened there.
Many thanks for the hard work remain.

Thanks for the extra info.

The STB and the PVR scan and auto tune themselves. It's under their control. The Tiny Twin (and other similar PC tuners) are controlled by whatever software you happen to be using to tune them. If parameters aren't correct, they may not tune.

Perhaps download a free copy of TSReader Lite and put in the frequencies shown above. See if you get a 'lock', and if the program comes through without errors.
You'll probably need to use the 'Generic DVB-T BDA' driver (or similar wording).

That would at least show that the tuner is able to tune to TVS.

At 6 kms from the transmitter, you may have too strong a signal. Or maybe many strong unwanted signals, such as ABC CH2 analogue and FM radio. Without putting a meter on the antenna distribution system, it's difficult to really know what's going on.

If TVS in Melbourne is transmitted the same way as it is in Sydney, it will be using a very robust modulation method. This should pretty well guarantee you receive it OK, in particular if you are getting SBS (on a nearby frequency) correctly.

You are receiving from the main transmitter site, aren't you? The frequencies are as below.



This note came from here.
I think C31 in Melbourne is running with an offset.
557.625 MHz.

Main Broadcast Site
HSV VHF 6 Hor 177.5 MHz HSV-7 Tower Eyre Road MT DANDENONG
GTV VHF 8 Hor 191.625 MHz ATV-10 Tower Ornata Road MT DANDENONG
ATV VHF 11 Hor 219.5 MHz ATV-10 Tower Ornata Road MT DANDENONG
ABV VHF 12 Hor 226.5 MHz NTL (ABC-2) Tower Eyre Road MT DANDENONG
SBS UHF 29 Hor 536.625 MHz NTL (ABC-2) Tower Eyre Road MT DANDENONG
TVS (C31) UHF 32 Hor 557.625 MHz (2 week test, then permanent on Friday 11 June 2010)
3D trial UHF CH 35 Hor 578.5 MHz

Have a look at DV Scheduler.
It uses VLC to work with streams across a network. One of the 'capture types' is TS, the full stream.

Paul,
Suggest you take MC out of the mix. Try recording and/or viewing with a third party application, like DV Scheduler (record/view), TV Scheduler, DNTV Live!
Even run TSReader Lite and see if you get any errors.

If it fails consistently with those other apps, then maybe it's a card issue.

There's a post over in the Australian Media Center forum here that has a link to Source Forge.

Gabs, DV Scheduler would be a good app to try that with.

Probably not.

Many digital receivers will 'produce' this error message when the signal presented to them is either too low, or too high.

Great. Glad you've got it working.

But the meta data is the trick on this one. Having the show details added to the dvr-ms files at time of capture.

It's not just simply playing the recorded files back, it's being able to view the meta data of the show, like you can in MC.

If you try TSReader Lite (free) you can read all that info.

You 'tune' it to the frequency you want, and look through the information it displays about the transmission stream.

Maybe try a similar program to JTVLAN called DV Scheduler.
Also a program called TSReader Lite.

They will allow you to see if it is a problem specific to JTVLAN.

I think C31 in Melbourne is running with an offset.
557.625 MHz.

Main Broadcast Site
HSV VHF 6 Hor 177.5 MHz HSV-7 Tower Eyre Road MT DANDENONG
GTV VHF 8 Hor 191.625 MHz ATV-10 Tower Ornata Road MT DANDENONG
ATV VHF 11 Hor 219.5 MHz ATV-10 Tower Ornata Road MT DANDENONG
ABV VHF 12 Hor 226.5 MHz NTL (ABC-2) Tower Eyre Road MT DANDENONG
SBS UHF 29 Hor 536.625 MHz NTL (ABC-2) Tower Eyre Road MT DANDENONG
TVS (C31) UHF 32 Hor 557.625 MHz (2 week test, then permanent on Friday 11 June 2010)
3D trial UHF CH 35 Hor 578.5 MHz

536625 kHz

Me too! I prefer vertical.
I suppose it's what you're used to in a way.
As noted elsewhere, I schedule programs from a web browser window. Running at 1600 x 1200 or higher, it's a great way to do it. And vertical works really well.
If you were trying to do that on your TV, then a different matter, no doubt.



It has been suggested in various posts.

As a long shot, have you tried reducing the ample memory you have in your new server? Down to say 1GB, or maybe 2GB?
What did your old server have?

It's not unheard of for very large amounts of memory to cause strange problems.
Maybe worth a quick try.

Have you tried different USB ports on the motherboard?
Tried a separate powered USB hub?

You should see both tuners on a device appear/dissappear when you plug/unlpug them, while checking in DNTV Live.


You need to work out if it is a device problem, or a motherboard problem.
And of course that the drivers are loading correctly, which they should just do when plugging the USB device in.

I'm not sure this is fully correct, Bear can correct if something is misunderstood.


I seem to recall up to Web Scheduler v4 was open source.
Web Scheduler v5 was the next version, paid for ( "closed source'?). This later became TV Scheduler Pro, open source again.

DNTV Scheduler Pro (and later on v2) was developed from the Web Scheduler v4 level, before it went 'closed source'.

As a matter of interest, how does the note below for release 5.39 impact de-interlacing using VLC? Does this just applywhen you 'view' using DV Scheduler.

Is it different in the situation when you 'stream' the output, and then open a session of VLC to monitor that stream?

In the first example I suppose some parameters get passed to VLC by the code, in the second you have more direct control of VLC.

You may find there is a difference between recording two HD channels, and viewing two HD channels.

I regularly record up to five or six SD channels with an older P4 XP2 SP2 machine. I'm using two external USB2 hubs, into two motherboard USB sockets.
However I'm sure if I tried to watch two HD channels I might see some issues.

So it may still be throughput related in some way.
Recording may well be different to viewing.

Just to test some functionality of having the two tuners work, also try DV Scheduler.

It branched off the Web Scheduler development path some time ago as well, but offers TV viewing as well as recording.
Handy for testing. Although you'll only view with one tuner of course. But you can see both being identified by the system.

Maybe try running some different software that provides similar functionality, and see if the problem goes away.


You'll find DV Scheduler on this forum, or just Google for the web site.
It uses VLC as well, and is also based around Web Scheduler.
Works very well. Combines recording as well as viewing.

Hi bear, thanks for the response.

I think all problems most likely related to overlay VMR7 VRM9 type issues.
A second window would always start, but just be 'black'. I didn't have the sound running, I must admit, perhaps I would have heard the two audio sources if it had been on.

I can check some specifics if it would help you, please let me know.



One thing I really wanted to see was how the program handled multiple recordings across different channels, with different tuners. And how it handled pre and post padding on overlapping programs on the same channel.

Web Scheduler Pro v5 (TV Scheduler) sets up some 'stream producer' and 'stream capture' tasks in memory, streaming to a hard disk capture file as required.
This seems to handle this sometimes complicated situation very well.

Once I had it running, I saw Parent/Child tasks being used by DNTV Scheduler Pro 2.
As far as I remember, this was used around the Web Scheduler v4 product time frame.

I changed the audio renderer to DNTV version, and the overlay to VRM9.

I can now display two channels in the two windows, great.
The second window really is a second version of DNTV Live!, isn't it? You exit both windows by choosing to exit the app each time, rather than exiting the PIP by a choice to just close PIP.

I'll retry DNTV Scheduler Pro.

EDIT:
DNTV Scheduler Pro works with two tuners now.