The Following 4 Users Say Thank You to Copernicus For This Useful Post: | ||
|
2012-09-07
, 02:35
|
|
Posts: 198 |
Thanked: 219 times |
Joined on May 2012
@ Louth / Ireland
|
#662
|
The Following User Says Thank You to Garrett_PL For This Useful Post: | ||
|
2012-09-07
, 03:05
|
|
Posts: 1,986 |
Thanked: 7,698 times |
Joined on Dec 2010
@ Dayton, Ohio
|
#663
|
For me, as well as for Sixwheeledbeast, FFW in searching for right panel freazing after around ten to twelve devices.
And I alsow think that SCAN, PAUSE, sounds like great idea and more user friendly thing.
TRIAX have only one device now, why?
Can I help somehow in searching for the documentation, details about device...to make it work on that particural one that I'd mentioned earlier?
The Following 2 Users Say Thank You to Copernicus For This Useful Post: | ||
|
2012-09-07
, 12:29
|
Posts: 112 |
Thanked: 30 times |
Joined on Jun 2012
@ Jeddah,Saudi Arabia
|
#664
|
The Following User Says Thank You to unexpected For This Useful Post: | ||
|
2012-09-07
, 12:43
|
|
Posts: 1,986 |
Thanked: 7,698 times |
Joined on Dec 2010
@ Dayton, Ohio
|
#665
|
The Following 3 Users Say Thank You to Copernicus For This Useful Post: | ||
|
2012-09-07
, 13:26
|
|
Posts: 198 |
Thanked: 219 times |
Joined on May 2012
@ Louth / Ireland
|
#666
|
Hmm. I definitely need to do some more work here. Is it any ten to twelve devices? (In particular, does it freeze after hitting a Pioneer device? I'm having a little trouble with their protocol.) Also, after the fast forward freezes, does the step forward/backward still work, or does it also freeze? Thanks!
Actually, I really shouldn't have put any Triax device names into Pierogi. I've built this app entirely on lists of numbers that I found somewhere on the internet: I have no actual Triax devices to test these lists of numbers against. So, I don't really feel justified in labeling a keyset as being able to control a device until someone with the actual device tells me that it works.
In any case, Triax does have three keysets in Pierogi right now...
For some reason I really don't understand, almost no manufacturer ever publishes their IR codes. (I say "almost" because I once did find an LG TV manual with a brief, but useful description of them.) The way that pretty much everybody gets IR codes these days is to put their device's remote control in front of an IR receiver hooked up to a PC, and push each button on the thing one by one.
If you've got the equipment and the skill to read IR codes, that'd be the quickest way to add support for the Triax into Pierogi (or, for that matter, QtIrreco, or a wide range of other universal remotes). Eventually, though, somebody will probably do it, because universal remotes are just too useful.
It really makes no sense to me that manufacturers try to hide this data.
The Following 2 Users Say Thank You to Garrett_PL For This Useful Post: | ||
|
2012-09-07
, 13:56
|
|
Posts: 1,986 |
Thanked: 7,698 times |
Joined on Dec 2010
@ Dayton, Ohio
|
#667
|
It freazes for a moment on "Deutsche Telekom TV Receiver Keyset 1", after a sec. I still can pres the buttons, and they are working (scrolling devices list) but FFW is naw like "Next" button, without possibility FFW.
Afterwards when I switch to Main panel (Universal Devices), trying to use (tested and working) JVC TV Keyset 1, it is not working what so ever (probably no other does).
After app restart, I'm getting errors with random letters like "yyyyy^yyyyy*yyyyyyy^" and "Done" button on right side.
Second test, I was able to FFW thru Deutsche Telecom.... but when I was gooing back (fast rewind as well) it stoped at that device (Deutsche ....) and everything happend again (buttons, not working). But this time,i t was allright after first restart.
Honestly, I do have only one, not working at all. The Strong device, when pressing buttons for testing is messing around my Triax reciver, but it's hardly usable.
The Following 4 Users Say Thank You to Copernicus For This Useful Post: | ||
|
2012-09-07
, 21:05
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#668
|
And what's worse is that TVBgone doesn't even know anything about the IR commands it spits out. I've looked at the data in the TVBgone widget, and I have no idea how they manage to update it, as it is just a list of raw numbers. Even if you knew that the 45th entry in the list was the one you wanted, there's no way to tell just where the 45th entry came from...
Well, I'm trying to tie everything in to the "Select Keyset" window now. So, if you select a keyset in the "Select Keyset" window, that should be the keyset that the search panel starts with. Similarly, each move in the search panel changes the current keyset on the Select Keyset window.
Basically, I want to allow you to start at the beginning, at the end, or in the middle; wherever you want. There's really no difference in this task whether you move forward or backwards. Moreover, if you overshoot by a bunch, it's nice to be able to move back quickly...
Hmm, actually, I wanted to try things out this way, because I always thought the scan & restart system was a real pain in the rear end. I've always hated having to sit and stare at the TV, waiting to pounce on the pause button as quickly as I can once something happens. This way feels a lot more relaxed to me; you just let up on the button whenever you want to stop.
But yeah, I can put it together the other way too; I no longer have a limit on the number of panels in Pierogi.
The Following 2 Users Say Thank You to Estel For This Useful Post: | ||
|
2012-09-07
, 21:15
|
|
Posts: 198 |
Thanked: 219 times |
Joined on May 2012
@ Louth / Ireland
|
#669
|
Drat. I really need to do some more testing, then... Here's one thing you might try (if you're willing) -- I'm storing persistent data for Pierogi in the standard Qt manner, in a file in your home directory called ".config/pietrzak.org/Pierogi.conf". It may be that that file has been corrupted in some manner; you could, say, move it to "Pierogi.conf.backup" to force Pierogi to start fresh with a new config file, and see if the errors continue. (The config file is almost readable, if you're interested in seeing what Pierogi is trying to store. )
Yeah, my error handling mechanism is really bad right now. Yet another piece of Pierogi that needs a lot more work...
Oh! Hey! Let me know which if the Strong keysets are working -- both Strong and Triax are using the classic NEC protocols, so if Strong keys are doing something on the Triax machine, that means that both devices are using the same NEC "device number". All I would need to do, I think, is graft the device number Strong is using onto the command list Triax is using, and we might be able to come up with a usable keyset!
The Following 3 Users Say Thank You to Garrett_PL For This Useful Post: | ||
|
2012-09-07
, 21:19
|
Posts: 2,290 |
Thanked: 4,134 times |
Joined on Apr 2010
@ UK
|
#670
|
I agree with you here - for me, current layout is more convenient, so it probably depends on personal taste.
I hope You won't take it as unnecessary feature demand, but I would *love* small button, or panel, or whatever, that would have one single purpose - to cycle, as fast as possible, through all SHUTDOWN, STANDBY, POWER DOWN, etc codes, from all manufacturers, as available on Pierogi at given time.
I've currently got it set to switch keysets every 0.05 seconds, but as some protocols require more time than that to encode a single command, it won't always move forward that quickly.
The Following 2 Users Say Thank You to sixwheeledbeast For This Useful Post: | ||
But yeah, I can put it together the other way too; I no longer have a limit on the number of panels in Pierogi.