July 26, 2017, 09:43:56 am
News:
Pages: 1 ... 8 9 [10]
 91 
 on: December 01, 2012, 11:15:23 pm 
Started by gtibay04 - Last post by gtibay04
Hi guys, new user here. I got an OSD from my father, apparently he had it in storage after he couldn't get it to work. I'm a little more savvy with tech stuff so he passed it off to me. I plugged it in, everything started up great, but my remote is completely dead and I can't control the OSD. From what I've searched so far, there is so far no way to bypass the remote and control the OSD directly, and no remote replacements. If I'm incorrect and a solution has been made, please direct me to it.

The remote is completely dead, I've tried with several different battery sets that I have tested and confirmed are good, but it will not operate. The LED indicator light on it doesn't so much as flicker.

Any help is greatly appreciated, I am very eager to see this system for myself.

Thanks everyone!

 92 
 on: November 17, 2012, 09:29:23 am 
Started by pfft2001 - Last post by pfft2001
So, my first question is: How can I turn off this weekly check?  (I've been living with it for years now - and have found it annoying  - but after today's adventure, it is more than annoying).  I'm pretty sure I've seen a setting in the menus somewhere to turn it off - but I couldn't find it just now.  So, if someone could inform me where it is,  that'd be nice.

Main menu -> Settings -> Firmware upgrade -> set "Frequency" to "Off".

(Another old thread necro-ing.  It even warned me that I should start a new thread instead)

Anyway, a few (semi-) interesting points about the firmware upgrade functionality:

1) It is Main menu -> Tools -> Firmware upgrade (i.e., Tools, not Settings)
2) There can be a mismatch between what it says onscreen and what is in the scheduler.sql database.  I found that on both of my machines, there was an entry in the SQL database even though the onscreen said "Off".  But, when I clicked "OK" on the onscreen, the record in the SQL database was removed.  The point being that you may have to do that - to ensure that the two views are "in sync".  Incidentally, changing the onscreen to something other than "Off" - and OK'ing out - causes the SQL database record to be re-created.  Setting it back to "Off" causes it once again to be removed.
3) Curiously, on one of the machines, even though the onscreen said "Off", it was still periodically going out and looking for updates (in, it seems, all the wrong places [*]).  I was getting an error message that it could not contact the updates server and that I should check my network settings.  I'm guessing that that server is no longer running.

[*] A reference to an old US country music song - a reference probably lost on non-US readers.

P.S.  Anyway, now both scheduler.sql databases are empty - so, presumably, no more looking for updates (in all the wrong places) will be occurring...

 93 
 on: November 08, 2012, 05:02:11 am 
Started by pfft2001 - Last post by pfft2001
Update:

According to http://pinoutsguide.com/DigitalCameras/tvout_rca_pinout.shtml, the pinout used on the OSD is the standard for camcorders.

And, it looks like you can buy them here: http://www.techcables.com/3-ft-3-5mm-4-pole-mini-av-to-3-rca-camcorder-a-v-cable-p-44.html for $3.  Yey!

 94 
 on: November 07, 2012, 07:59:15 am 
Started by pfft2001 - Last post by pfft2001
Update.  According to: http://forums.neurostechnology.com/index.php?topic=11340.msg57151#msg57151, it is:

tip: left audio
next: video
next: ground
next: right audio

which seems pretty weird to me.  FWIW, the layout of the similar connector on a certain SBC (single board computer) (that I happen to own) is:

tip: left audio
next: right audio
next: video
next: ground

which seems to make more sense.

 95 
 on: November 07, 2012, 07:41:11 am 
Started by pfft2001 - Last post by pfft2001
I seem to remember that they are some kind of a standard, and the wiring schematic should be on the wiki somewhere...?

I don't think they're iPod A/V, but something similar...?

(Waking up an old thread...)

Could you point me to the pinout (i.e., the "wiki somewhere" to which you refer)?

I don't know what to search for, alas...

 96 
 on: October 18, 2012, 07:11:18 pm 
Started by ChadV - Last post by ChadV
This topic has been moved to Other Linux Installed.

http://forums.neurostechnology.com/index.php?topic=11967.0

 97 
 on: October 18, 2012, 09:43:09 am 
Started by OldSmoke - Last post by OldSmoke
based on peppermint 3 everything preloaded ready to run hulu-fire,minitube,tv-maxe,and much more
for people with the Link it is  the ultimate os can do as livedvd-liveusb
made as a ram loader so make sure to have loads of ram if not order the regular livedvd or liveusb
I have a video on Youtube which will be updated this weekend but the old one will suffice for the moment.
search EvoLinuxTV on youtube and ebay for Neuros owners i will sell for 29.00 +shipping.
there is nothing like this out there can also be installed to the hard drive any questions please email me at sukitoto@gmail.com.
Thx OldSmoke
this is not intended for Linux people only as it all works upon boot nothing to configure programs are preinstalled.
this also will work on desktops,laptops and netbooks

 98 
 on: September 29, 2012, 09:48:36 pm 
Started by pfft2001 - Last post by ChadV
Quote
3,098,123,456
it makes sense to be able to say that it (the file) is "just over" 3 Gb.  (Even though that statement is, technically, untrue...)

I handle that by saying "it's about 3gb", and I would work out the size in MiB/KiB/bytes if it came to actually mattering that much; 99% of the time the only comparisons I have are will this stuff fit on a DVD-R (<=4488MiB) or do I have enough space on this SD card for the next episode of Joshiraku?...

I have "ll" aliased to "ls -lh --color" on most of my systems.  No conversion necessary.  Smiley

 99 
 on: September 29, 2012, 06:03:52 pm 
Started by pfft2001 - Last post by heyrick
1) Regarding the 4 hour limit.  So, it has nothing to do with the FAT 4G file size limit?  That was just a coincidence.

See? The Asians have a dislike for the number 4 for a reason. Wink [see Tetraphobia (Wiki)]

Quote
It has to do with running out of memory (and the system crashing) when finalizing the file.  Note that because of the MP4 file structure, you have to pass the entire file through in order to finalize, so it makes sense that the larger the file, the more memory it will take to do it.

Which is what I was thinking with the I-frame index. Good God, how did such a shonky video format ever become a standard? Why can't the start of one chunk point to the previous and next? It'd only be 16 bytes for two 64 bit values (or could use 32 bit values if it's just an "offset to prev/next chunk" (instead of absolute position). This would also mean the files could be playable if incorrectly/not finalised.


Quote
I'm not using any file manager.  GUI file managers are for wimps.

Hahahaha! You're a dying breed, you know? I bet you love Unity about as much as I do.


Quote
3,098,123,456
it makes sense to be able to say that it (the file) is "just over" 3 Gb.  (Even though that statement is, technically, untrue...)

I handle that by saying "it's about 3gb", and I would work out the size in MiB/KiB/bytes if it came to actually mattering that much; 99% of the time the only comparisons I have are will this stuff fit on a DVD-R (<=4488MiB) or do I have enough space on this SD card for the next episode of Joshiraku?...

I only get annoyed when I look in the supermarket and see 500Gb harddiscs, and I know well that if I plugged it in, my computer would tell me something rather different; and worse, as I pointed out, it isn't as if harddiscs have any denary component, so using non-binary for the sizes is just a crappy thing to do...

Anyway. Hope you can rebuild (or maybe binary-hack) your nmsd to see how far you can push it. Let me know how you get on.

 100 
 on: September 28, 2012, 07:25:18 pm 
Started by pfft2001 - Last post by pfft2001
A couple of things:
1) Regarding the 4 hour limit.  So, it has nothing to do with the FAT 4G file size limit?  That was just a coincidence.  It has to do with running out of memory (and the system crashing) when finalizing the file.  Note that because of the MP4 file structure, you have to pass the entire file through in order to finalize, so it makes sense that the larger the file, the more memory it will take to do it.

2) Regarding the Gb vs. GiB thing.  I'm not using any file manager.  GUI file managers are for wimps.  I  just use variations of the 'dir' command ('dir' under CMD.EXE or the equivalent 'ls' command under Unix flavors) and that displays the sizes of files in bytes.  If I see a 10 digit number that starts with 2950, that says "just under 3 Gb to me".

I understand, and empathize with your little rant, but it is also true that if you see a file size like:

3,098,123,456

it makes sense to be able to say that it (the file) is "just over" 3 Gb.  (Even though that statement is, technically, untrue...)

Pages: 1 ... 8 9 [10]