Neuros Technology Forums

That's great news, as ASF is fairly useless as far as editing goes. Hopefully the audio and video will be in sync soon for AVI,

Another two semi-major problems are: no sound when the unit is turned off (why doesn't this just pass through like video) bug #714 and when recording there are transparent vertical lines or bands going down the screen (it's a CRT television) I believe this is bug #659

Bug 714 is important because people are not going to want to wait for the OSD to boot everytime they want sound if the OSD happens to be off or in the middle of resetting itself.

One last thing while I remember tonight, the recorder interface as of 3.20_18 is horrible because it makes no sense. There is a bar in the center that does something (it's not labeled) is it a time display of some sort? There is also the bar in the lower left.. I assume is storage remaining but why does it show the OSD storage when I'm recording to CF or SD? Why does my SD card show up as MMC and why do I need to tell it whether I am recording to SD or MMC when only one type can fit in that slot at a time.  It might be better to say 'why are there more choices than there are slots'? Why not combine them?

One option is SD/MMC/MS another is CF, another is USB, and maybe a future network one. If SD/MMC/MS is selected then record to whichever one of those is mounted by the OSD.

In reply to my post about menus...

I was finally able to upgrade the firmware using the emergency upgrade method (as the XIM menu method did not work due to "package error"). After the upgrade to 3.20_18 the menus seem to be fixed.

To date I have still not been able to make a single recording with the OSD. The screen goes black and doesn't stop being black until I stop the recording.  the file ends up being about 1024+ bytes and  if I press play all I get is more black screen. (recording from composite, 5 min recording time.)

As a side note, I was never able to update the firmware using any of my cards while using the XIM menu. Using the emergency update was the only was for me to upgrade the firmware.

After the upgrade my 2.2 GB CF microdrive worked once for about ten seconds then promptly stopped working again..

I have a 2 GB CF microdrive... In 3 out of 3 tests so far it has failed every time.

A short post regarding OSD menus:

I don't know about everyone else, but to me the OSD menu navigation is counter-intuitive (even though it is labeled).

For example, when changing the recording settings...

Usually on most electronic devices with 'navigatable' menus a person would press down to go down the menu (on the screen). Instead the OSD is set up to change the currently selected menu option settings when up or down is pressed (and this is labeled as such). In order to change the currently selected menu option a person must press the left or right arrow.

The reason this is counter-intuitive (at least for me) is because it is the exact opposite on other devices. On other devices a person uses the left or right arrows to change the settings of the currently selected menu option and they use the up and down arrows to change the selected menu item on the screen (as they are listed vertically).

It probably took me anywhere from 30-60 seconds to figure this out after pressing a whole bunch of different buttons, believe me that's an eternity.
I do not know if anyone will understand what I am talking about, maybe someone can put it in better words or make a flash demo. Basically in my opinion  "up and down should go up and down (on the screen), left and right should change the setting."

I know how it works as of now and I am constantly messing up while navigating (even though it has arrows).

Does anyone else have any opinions on this?

If there is a possiblility of the hardware needing to be reset on the production model then it would be beneficial to add a very small reset button which could be pressed without opening the OSD housing.

I am creating this thread to document my first impressions of the unfinished OSD. I am trying to be overly critical in order to see improvements made. The things I mention in this and following posts may or may not already be in bugzilla.

This post will primarily focus on the physical aspects:

The first thing I noticed when opening the box was the remote control batteries... Toshiba "Super Heavy Duty!" Now I know that a remote control is a low drain device, but Zinc-Carbon batteries scream "cheap". Alkaline batteries would be nice. Gold Peak (Hong Kong), Duracell, Energizer, the manufacturer doesn't matter so much. The OSD remote will be getting far more button presses than your standard remote.

Secondly, I found out very quickly that the power adapter plug that fits into the OSD gets dislodged pretty easily. It doesn't come all the way out, but it is enough to shut the OSD off. Curiously enough I can't cause it to happen by applying a minor force, yet it happens every other time I pick up the OSD possibly due to the weight of the power cable.

The remote is easy enough to program, but an end user in the final production model shouldn't have to do this.

USB support is going to be one of the key features that many OSD users will absolutely need above all else.

More later...

Do you have the latest version of NSM?

-Jeff

You can see it in windows explorer, yes, but can you access it in explorer?

-Jeff

If you can reproduce it by all means put it in bugzilla so that it can be fixed in later versions of NSM.

I'm currently drooling over the new hitachi 400GB drives.. I've almost got my WD 250GB filled up even though I thought it couldn't happen. It's probably not even a year old. If only I had money. []

-Jeff

Well, I'm not sure how it could have happened without being there. NSM used to check local copies which wouldn't have existed. I'm not sure how the latest version checks into this. Are you using the latest version?

Of course the primary plan for redundancy is to never let an electronic device such as an mp3 player, PDA, etc contain your only copy.

Make sure you are using the latest version earlier versions had many problems that could be related.

After searching for orphans which option did you choose?

-Jeff

Well, it depends how exactly it happened in the first place. First don't allow the Neuros copy to be your only copy as with any electronic device. Second, did you hit rebuild Neuros by mistake.

Also, If NSM removed them from your Neuros are they in the NSM recycle bin? I'm assuming you are using the very latest versions of NSM and Neuros Firmware to avoid dataloss and errors in general.

-Jeff

You can email support about the upgrade question (sending it in) since your drive assuming you are using the latest firmware should work if moved from USB 1.1 to USB 2.0 without any problems.

-Jeff

Those quotes are basically what I said myself...

In your earlier post you were mixing up the bundle and the HD unit

Neuros Bundle = 128MB Neuros (and everything included with it.) Plus a hard drive backpack and a car adapter.

Neuros HD unit = 64MB Neuros face with HD backpack in one box

So if you were to buy a bundle you get three items in the box. A Neuros box containing a 128MB Neuros exactly the same as if you bought it by itself, you get another box or envelope containing the HD backpack, and also a car adapter.

This means that a bundle is simply a 128MB plus car adapter and any HD backpack of your choice. I hope that clears it up.

As for 256MB... when the Neuros gets back in stock it will probably still be 128MB at least for a while.

-Jeff

Maybe Waylander, the possibility has been mentioned on the forums.

rramsey, the bundle and the 128MB version have always had 128MB. The "brains" as you say in the HD version (not bundle) has 64MB.  Buying a 128MB Neuros, a car adapter, and a 20GB backpack has always been equivalent to a bundle (maybe not always in price though).

-Jeff