Rockbox Technical Forums
Support and General Use => Hardware => Topic started by: Davide-NYC on July 13, 2006, 01:33:47 AM
-
I just purchased two of the JOYSTICK remotes for my iHP-140 (H140)
(http://www.misticriver.net/photos/albums/userpics/20561/Remote%20front.JPG)
Will this remote work well with Rockbox on my H140? If not is there a dev that needs me to lend them one temporarily. (I need it back once the code is finished)
Please let me know...
Davide-NYC.
PS: I don't have them yet but they should be on their way from South Korea to NYC.
-
Yes, they are supposed to work on the H1xx series as well.
-
Although I suspect the buttons will not necessarily do what you imagine they will do!
This is because the button mappings for the remote are all based on the standard h1xx remote which doesn't have a joystick.
There needs to be some code that differentiates between remotes at runtime.
There is a patch HERE (http://www.rockbox.org/tracker/task/4860#comment8657) that may do the trick if it is an H3xx remote....(I've never seen one so don't know)
-
When I tried that wierd set-up (when I had an H300 remote on an H100) the remote worked quite well if you exclude some buttons that Mmmm said.
If you learn those misconfigured buttons you could navigate quite easily with it.
-
Well, my remotes are not here yet, so this may be premature, but I purchased two for a reason.
I am willing to send a joystick + LCD remote to a dev (Mmmmm?) that is willing to do the coding/testing to get it to work perfectly with the H1xx AND then send the thing back to me when they are done.
Sound interesting?
Davide-NYC
-
Hmmm that sounds tempting... how much did it cost you? maybe I could buy it off you to relieve the pressure a bit? ;) (unless you need the spare for something else of course)
-
Could you (or anyone else with the h300 lcd/nonlcd remotes) tell me what the buttons on the top and bottom are labelled?
On the LCD version they must be source, bitrate, on/play, record, mode and stop i assume, as these are defined in the code but not on the front of the remote, but where exactly are these buttons? are they rockers or push in types or what?
On the non-lcd type there must just be vol up/down somewhere (no stop button ???.... it's as bad as an Ipoo!).
Does anyone know?
-
Although I suspect the buttons will not necessarily do what you imagine they will do!
This is because the button mappings for the remote are all based on the standard h1xx remote which doesn't have a joystick.
There needs to be some code that differentiates between remotes at runtime.
There is a patch HERE (http://www.rockbox.org/tracker/task/4860#comment8657) that may do the trick if it is an H3xx remote....(I've never seen one so don't know)
That remote is for the H300-series.
-
Could you (or anyone else with the h300 lcd/nonlcd remotes) tell me what the buttons on the top and bottom are labelled?
On the LCD version they must be source, bitrate, on/play, record, mode and stop i assume, as these are defined in the code but not on the front of the remote, but where exactly are these buttons? are they rockers or push in types or what?
On the non-lcd type there must just be vol up/down somewhere (no stop button ???.... it's as bad as an Ipoo!).
Does anyone know?
On that H300 LCD joystick remote, there's three jog-levers and the joystick (as well as the hold switch). There's probably more controls on it than the H100-series remote, which has just four jog levers and a Stop & Play button.
-
On that H300 LCD joystick remote, there's three jog-levers and the joystick (as well as the hold switch). There's probably more controls on it than the H100-series remote, which has just four jog levers and a Stop & Play button.
Are you sure? I can only see 2 on the pic and there aren't enough buttons defined in the code for 3!
Both the H1xx remote and the H3xx remote have 11 buttons defined which would tally with 3 jogs and 2 buttons (H1xx) or 2 jogs and 5 buttons (H3xx) (as there are 3 buttons per jog - unless you can't push in the H3xx ones).
I really want to know how they are labelled...do you push the top jog in to play, or push the bottom jog left etc..
-
Tons and tons of pics HERE --> http://www.misticriver.net/photos/thumbnails.php?album=364 (http://www.misticriver.net/photos/thumbnails.php?album=364)
I just got the two I ordered in the mail! They are perfect and they sort of work with my H-140.
I know that these are meant for the H3xx series, but the socket is the same and both the remotes and the base units are so similar I'm sure it won't take that much to get it all working the way it should in Rockbox.
Mmmm, PM me if you want to work something out.
:-)
-
On that H300 LCD joystick remote, there's three jog-levers and the joystick (as well as the hold switch). There's probably more controls on it than the H100-series remote, which has just four jog levers and a Stop & Play button.
Are you sure? I can only see 2 on the pic and there aren't enough buttons defined in the code for 3!
Both the H1xx remote and the H3xx remote have 11 buttons defined which would tally with 3 jogs and 2 buttons (H1xx) or 2 jogs and 5 buttons (H3xx) (as there are 3 buttons per jog - unless you can't push in the H3xx ones).
I really want to know how they are labelled...do you push the top jog in to play, or push the bottom jog left etc..
OOPS MY MISTAKE! I have an LCD joystick remote from the iMP-900 MP3/WMA CD player and it's identical except for the words below the screen. There's ONE lever on the top and ONE on the bottom. The 'Reduce Ticking' option would be handy with this remote, as I've noticed ticking on it before on my iMP-900 with my Boostaroo amp.
My iMP-550 MP3/WMA CD player works fine with both remotes, and the button mappings are identical (you wouldn't be able to tell which CD player you were using except for a few updated firmware features & the Snakebyte game on the iMP-550) on both units.
-
Tons and tons of pics HERE --> http://www.misticriver.net/photos/thumbnails.php?album=364 (http://www.misticriver.net/photos/thumbnails.php?album=364)
I just got the two I ordered in the mail! They are perfect and they sort of work with my H-140.
I know that these are meant for the H3xx series, but the socket is the same and both the remotes and the base units are so similar I'm sure it won't take that much to get it all working the way it should in Rockbox.
Mmmm, PM me if you want to work something out.
:-)
Ta for the pics...hmmm interesting..the top jog is push for play, the bottom push for stop, that's ok...
But the top left is labelled -10 and right +10 ??? what is that supposed to mean? The bottom left is a/b right is mode, whereas these are usually the same button! confusing eh?
Davide-NYC, could you do me a favour? With this remote plugged in, go to mode->info->debug->view I/O ports
now on the remote press left/ right on the jogs and tell me what numbers come up for ADC_REMOTE. From this, I'll know what buttons they are.
Also, I may have a patch/build for you to try out soon, If it works I probably won't need a remote off you, if it doesn't I will! (although I quite fancy having one anyway!) :D
-
Ok, here's a build for you to try out
H3remotemods.zip (http://homepage.ntlworld.com/martin.scarratt/Rockbox/H3remotemods.zip)
All normal screens should work now with all 3 remotes..give them a go. It messes my H100 remote keys up nicely so that's good (when I enable it for the patch that is). Check for any weirdness (like the wrong lcd lighting up and other possible weirdnesses).
Also give me those ADC_REMOTE numbers I asked for in my previous post so I can tell you what the rocker switches are supposed to do.
Hope it works... plugins probably don't, I'm still looking at it ;)
-
OK, one of my remotes is slightly "off" from the other. Is that normal? Should I return one?
Here are the number:
Remote 1 (the more stable one)
Top Jogwheel
-10 (left) = B8
+10 (right) = 9F
press = 80
Bottom Jogwheel
a-b (left) = 50
mode (right) = 68
press = 38
Joystick
Up = D1
Down = 01
Left = EA
Right = 18
Press = NO CHANGE
Remote 2 (the less stable one)
Top Jogwheel
-10 (left) = B8
+10 (right) = 9F
press = 80
Bottom Jogwheel
a-b (left) = 50
mode (right) = 66/67 (vaccilating between the two numbers)
press = 37
Joystick
Up = D1/D2 (vaccilating between the two numbers)
Down = 01
Left = EA/EB (vaccilating between the two numbers)
Right = 18
Press = NO CHANGE
Does this mean the one of my remotes is bunk? Please let me know these cost me quite a bit (for a DAP remote).
Davide-NYC
-
WOW!!!
Your patch seems to work perfectly on both of my remotes.
Sweet.
The -10/+10 jogwheel function just jumps up or down ten items in a list.
On a different note, what is going on with the main LCD contrast!?!?! I have to lower it from 37 to 27 in order to read anything! Is that as easy as changing the default startup value? Different issue I guess...
I'll play with the remote for the rest of the day and let you know how it goes.
Anyone else with this combination (H-1xx and Joystick Remote) do some testing!!!
I'll report back here in a couple of days.
Thanks so much!!!
Davide-NYC.
-
Hang on hang on, don't go yet....I've put a new build in now...should work better (depending on when you downloaded it! :D
Everything should work now...plugins and all!
By the way, don't worry if the remotes give slightly different ADC_REMOTE no.s as there is a range that is valid, so it should be ok.
the top and bottom rockers should be
top right -> bitrate
top left -> source
bottom right -> record
bottom left -> mode
About the dark screen, this is a separate issue, I thought Linus had fixed it..try resetting your settings, that may do it!
Keep giving feedback and i'll commit it if you don't find any weirdnesses.. have fun ;)
The link again: H3remotemods.zip (http://homepage.ntlworld.com/martin.scarratt/Rockbox/H3remotemods.zip)
-
Ah.. the dark screen thing was because I hadnt updated my build! ::)
Now it should be better!:)
-
OK from the Filetree :
- Joystick functions are correct.
- Top Jogwheel is (-10, Play/Pause, +10)
- Bottom Jogwheel is (A-B, Stop, nothing)
From the Menu screen (Mode) :
- Joystick functions are correct.
- Top Jogwheel is (-10, nothing, +10)
- Bottom Jogwheel is (A-B, up a level/cancel/out to filetree, nothing)
From the WPS :
- Joystick is correct (up/down = volume, left/right = seek/track skip)
- Top Jogwheel is (prev directory, play/pause, next directory)
- Bottom Jogwheel is (A-B, STOP, nothing)
From WRS (while recording screen) :
- Joystick is (up/down = NOTHING, left/right = select next item)
- Top Jogwheel is (nothing, rec/pause, nothing)
- Bottom Jogwheel is (nothing {while recording}/mode otherwise, STOP, filesplit)
So the up/down on the main unit == left/right on the remote. This needs fixing.
So the left/right on the main unit == -10/+10 on the remote. This needs fixing.
Observation : The Joystick remote mirrors the main units buttons PLUS has the -10/+10 buttons which can be used for whatever purpose. The next directory/previous directory functionality is really nice in the WPS. I find that using the top jogwheel is slightly easier than using the remote joystick, so while in the WRS making {up/down == select} and a {-10/+10 == level adjustment} could be sweet ergonomically.
Opinion : Unless someone sees a reason to not do the following I suggest that remote joystick left/right and top jogwheel -10/+10 be redundant butons for level adjust while in the WRS. What say y'all? I can't think of what else to do with -10/+10 in WRS.
Plugin observations:
No JPG viewing on remote (who cares)
No TXT viewing on remote (who cares)
Audio observations :
The ticking is back in full effect! (insert worst profanity you know)
The whole point of this excercise was to have good navigability during stealth recording (or am I alone on this one?) this ticking business is a real PITA. I remember there being a setting to reduce or remove the ticking problem but I can't seem to find it. Is it in this build?
Display observation :
On the remote I get a cool HD activity icon, but on the main unit I don't.
Presumably the red LED is supposed to serve this purpose but they are not in sync. (?)
Can I enable an HD activity icon on the main unit LCD? (ignore if not possible)
Hope this helps., Davide-NYC
-
Here's a JPG I just made showing the 1:1 button mappings plus the -10/+10 buttons which should equal the source/bitrate buttons on the plain LCD remote.
[attachment deleted by admin, too old]
-
From WRS (while recording screen) :
- Joystick is (up/down = NOTHING, left/right = select next item)
- Top Jogwheel is (nothing, rec/pause, nothing)
- Bottom Jogwheel is (nothing {while recording}/mode otherwise, STOP, filesplit)
So the up/down on the main unit == left/right on the remote. This needs fixing.
So the left/right on the main unit == -10/+10 on the remote. This needs fixing.
Ahh..Cheers david, That's an easy fix (the recording screen checks buttons in a slightly different way to everything else) All I have to do is run my new function in peakmeter.c and that should sort it...I'll do that later when I'm back with my DEV environment.
The bitrate/source thing is also easily done... :)
I'll post a new build for you to try later.. ;)
-
Oh and I think you'll find the ticking fix in the remote LCD settings (right at the bottom)
-
Alrighty then.... try this build now: H3remotemods.zip (http://homepage.ntlworld.com/martin.scarratt/Rockbox/H3remotemods.zip)
Hopefully that whips this one...:)
-
I do belive we have a winner!
WRS functions are all correct and the redundant level controls to boot!
Well done Mmmm. Thanks again.
If you want one of these amazing remotes this guy has them:
http://feedback.ebay.com/ws/eBayISAPI.dll?ViewFeedback&userid=95prober
They ship from South Korea and are brand new.
He has them, just ask him.
Davide-NYC
-
I think I've found a bug. It's difficult to say without being able to test. It hit me just before I snoozed off last night!
I bet the virtual keyboard doesn't work properly... can you test it?
Go to mode->manage settings->write .cfg file
press mode on the remote to flip the page and then try to enter a character.
I bet the wrong one pops up....Am I right?
Anyway, I wouldn't like to report a bug without a fix ;), so Here's the (hopefully) fixed build in the usual place: H3remotemods.zip (http://homepage.ntlworld.com/martin.scarratt/Rockbox/H3remotemods.zip)
-
Hmmm well, I'm not going to commit this as there is a HUGE button reworking in process at the moment so I'll probably have to start from scratch after that is committed anyway.
Ahh well, so until then, here is the patch so that you can all update your builds etc...
[attachment deleted by admin, too old]
-
I hadn't thought of that at all.
I tried renaming a file with the last biuld and in fact it didn't work properly.
When I tried with your updated build it seemed to work perfectly!
(although I didn't attempt to type every character)
Thanks again for the build and the patch.
Are there any other tests I should perform?
-
Are there any other tests I should perform?
Just try everything you can think of...press all the buttons, go into all the menus try the plugins...you can never do too much testing! ;)
-
Minor bug to report:
The 300remotekeys patch breaks the UISimulator on MAKE.
Here's the error:
LD rockboxui.exe
/home/Administrator/rockbox-devel/sim_20060801/apps/recorder/peakmeter.o: In function `peak_meter_draw_get_btn':
/home/Administrator/rockbox-devel/apps/recorder/peakmeter.c:1186: undefined reference to `_remote_key_remap'
collect2: ld returned 1 exit status
make[1]: *** [/home/Administrator/rockbox-devel/sim_20060801/rockboxui.exe] Error 1
make: *** [all] Error 2
No idea what this means but I thought I'd report it.
:-)
-
He most probably forgot to either not call the function or supply a stub function for sim builds
-
Would there be a way to make this an option in the menu?
General Settings-->System-->Remote Type
- LCD (Default)
- Blind
- Joystick
I'm not sure the 'blind' option is necessary. If the non-LCD remote is a subset of the LCD remote then I'd assume there would be no change programmatically. (Maybe I'm wrong)
Question:
Could this be implemented and committed then I could start bugging other people about fixing their plugins to check remote type and remap buttons accordingly, or better yet I would attempt it myself as long as someone was willing to check my work. (I still suck at programming)
Correct?
;D
-
The preferred system is to have the remote type detected automatically.
-
OK. That is (of course) better.
As it stands now an H120 Rockbox build is not H300-Joystick-Remote "aware". How can we make it so that it is?
Would this be a CVS commitable patch since the remotes are autodetected?
I consider this core functionality, but maybe others don't.
-
The remote doesn't work at all, or just doesn't have proper buttons yet? The word aware is very vague.
-
Hang on hang on....what's going on? Why would you want to manually select which remote you are using?
Doesn't my patch do the job??
I am aware that it breaks the simulator but that is easy to fix. You also wont be able to switch off the remote LCD which is also easy to fix. The plugins should work with this patch (the keys if not the screen) but only on the H300 remotes so that is a bit of a bonus!
EDIT: actually some plugins may not work...it depends on how they check the buttons, if they use button_get() they wont work and will all need to be slightly changed to remote_key_remap(button_get()).
I haven't committed it because I am waiting for the new button code to get committed first (as adding this now would just complicate things for the people working on the button code) and then ill look at it again and commit something.
Or have I just totally misunderstood everything you've said? ;)
-
I might be a little over excited about my new remote. :P
I had completely forgotten that the underlying button code was being re-written.
Sorry. :'(
OK,
DLed CVS, applied REP patch, applied 300rem patch, compiled. Breaks the sim (of course) but seems to build fine normal. Will recording a show tonight (if I can get in with my iriver) and report back.
-
I've fixed the sim building and the LCD off button...press -10 to switch off the LCD.
Davide, If you could tell me exactly which plugins don't work with the H300 buttons, (not the LCD, just the buttons, the LCD is a whole new kettle of piranhas :D) I can get them working too.
I should be getting my new remote soon (can't wait) so I thought I may as well get this patch going properly (and the button code revision seems to be taking longer than I thought ::))
[attachment deleted by admin, too old]
-
Oops...now thats not going to compile is it? ::)
Here's a better one!
[attachment deleted by admin, too old]
-
Fresh CVS DL, your patch and during MAKE SIM got this:
LD rockboxui.exe
/home/Administrator/build/sim/apps/recorder/recording.o: In function `recording_
screen':
/home/Administrator/build/apps/recorder/recording.c:501: undefined reference to
`_remote_type'
collect2: ld returned 1 exit status
make[1]: *** [/home/Administrator/build/sim/rockboxui.exe] Error 1
make: *** [all] Error 2
I was using the SDL (default) option. I don't know if this means anything.
Also I'm using CYGWIN on WinXPSP2.
Maybe your source is old? I dunno.
-
Fresh CVS DL, your patch and during MAKE SIM got this:
LD rockboxui.exe
/home/Administrator/build/sim/apps/recorder/recording.o: In function `recording_
screen':
/home/Administrator/build/apps/recorder/recording.c:501: undefined reference to
`_remote_type'
collect2: ld returned 1 exit status
make[1]: *** [/home/Administrator/build/sim/rockboxui.exe] Error 1
make: *** [all] Error 2
I was using the SDL (default) option. I don't know if this means anything.
Also I'm using CYGWIN on WinXPSP2.
Maybe your source is old? I dunno.
Hmm weird...does it work with a normal build? have you got the REP installed too? because I dont think that builds for sim!
If you only have this patch installed, try deleting everything in your sim folder and then trying again. If it still doesn't work you'll have to wait till i'm back home in a week or so until I can fix it.
I'm using a build with it at the moment (I got my new remote just in time to go on holiday with it) so it should work in a normal build.
-
I use a fresh CVS DL with only the remote patch.
It does work with a NORMAL build. I was just reporting the broken SIM build.
When I do patch testing I do one patch at a time so that I can see what causes what problem.
So I actually do three (now two since disktidy has been commited!) separate builds.
If all single patch builds work then I go ahead and try another patch on top.
I also generally attempt a SIM build before a NORMAL build. So that would be six compiles (now reduced to four) before I even start combining patches.
I wish I was a better programmer, I'd set up a batch process and walk away.
As it is now I just multi-task as best I can.
Let me know if you need me to test something specific.
IN CASE ANYONE IS LOOKING FOR ONE OF THESE REMOTES:
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=180015706977 (http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=180015706977)
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=270016077241 (http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=270016077241)