Frankenciever AC3 troubles

  • WELCOME TO THE NEW SERVER!

    If you are seeing this you are on our new server WELCOME HOME!

    While the new server is online Scott is still working on the backend including the cachine. But the site is usable while the work is being completes!

    Thank you for your patience and again WELCOME HOME!

    CLICK THE X IN THE TOP RIGHT CORNER OF THE BOX TO DISMISS THIS MESSAGE
Status
Please reply by conversation.

rkrenicki

SatelliteGuys Pro
Original poster
Mar 11, 2005
976
0
Well... I completely rewired my entertainment system, so I have three hi-def sources (DCT6412, DSR500, and Dish811), with digital audio from all including my FTA recevier, the Frankenciever. (a rebuilt Pantec MS, a Pansat 2500a clone)

I have the PCM audio working fine for all the channels, but when I get to Imaginasian, I get nothing.. the reciever goes into UNLOCK.. do I have to change the APID for this channel, or should I just rescan it?
 
It rescans with an APID of 0000...

I guess I will try manually changing the pid.
 
Oddd.. I just scanned that TP.. and alot of the channels have no audio now.

Code:
Channel Name		VPID	APID	PCR
KLRA			0032	0033	0033
WNYI			0035	0034	0034
IMAGINE_ASIAN.TV	0036	0000	0036
KKTU			0041	0042	0041
MAS MUSICA		0043	0044	0043
KKFQ			0045	0046	0046
KXUN			0048	0049	0048
THE TUBE.TV		0050	0051	0050
KEYU			0039	0000	0040
KAMT			0052	0000	0047
WNGS			0053	0054	0054
KWWF			0055	0056	0056
KUOK			0058	0057	0057
INN_UTILITY		0060	0059	0059
KEGS			0064	0063	0063
KWFT			0061	0062	0062

So, now I have no audio on Imaginasian, KEYU, and KAMT.. there were others on other TPs but those are just on the 11720V TP
 
I figured as much, but are the APIDs correct on Lyngsat? I tried selecting VPID 36 and APID 37.. but no love...
 
I guess not.. the APID of 37, just gives me the familear pops.. that is when the reciever isnt in UNLOCK.. which it is wigging out on.. switching between UNLOCK and PCM 48kHz
 
On my coolsat I had to set the APID in the channel editing software to get audio on ImagineAsian. When doing so I also had to convert the APID on Lyngsat to hex.

37 became 0x0025

I couldn't set it from the reciever, had to do it in NDFEdit.

 
Seems like coolsat would have addressed this issue in there latest update. Or at least be able to explain why AC3 does not scan in correctly.
 
questic said:
Seems like coolsat would have addressed this issue in there latest update. Or at least be able to explain why AC3 does not scan in correctly.
Well, concidering AC3 didn't work at all before this update, I concider it a move in the right direction ;).

Shawn
 
Status
Please reply by conversation.

Users Who Are Viewing This Thread (Total: 0, Members: 0, Guests: 0)

Who Read This Thread (Total Members: 1)