I sent a support request email about adding both, so we'll see what happens. If you want it I suggest you do the same.

I've also asked several times (through several different media sites) about full vs limited rgb, but no reply :/

I've been messing around with the AVS some more today and I think I've dialed in my favorite settings for 1.3b5. Here they are:

Pixel Aspect: 2 Left from Default, or the 2nd from the left. I did a lot of comparison between this and the Super Nt. 1 left from default is still wider than 4:3 for 16:9, but 2 left from default is basically halfway between 4:3 for 16:9 and 8:7, so it strikes a good balance. Would still prefer 16:9 for 4:3 and 8:7 option, but this works for now.
Vertical Border: Default. It's fine where it is, but your preferences may differ.
Scanlines: 2. I think this is enough to give a nice scanline appearance, but not too much that it would really start throwing the gamma off. I think 1 is a good option too, but I wanted mine just a tad darker. I think anything over 2 is too much, but YMMV.
Left side hide, extra sprites on
Exp Volume Default
Palette: YUV v3. This one kinda surprised me too, but as I kept going back and forth I noticed that, especially with scanlines, Unsaturated looked a bit washed out for my taste. If I weren't using scanlines, I'd probably go for Unsaturated, but the added vibrancy of YUV v3 helps a lot when they're on.

Interesting. I don't do scanlines, so I think that's why I like Unsat v6. I haven't checked the other settings since upgrading to 1.30b5.

Yeah, for me it was a toss up with scanlines off, but at 2 strength Unsaturated just starts to look really washed out. It was the main reason I thought the RGB might output limited RGB, because everything looked even more washed out in Full.

It should be full. 

Thank you for the clarification!

Nice! Glad to see some confirmation on the RGB output. I knew something seemed off.

I know it's a very small issue, but is there any possible way to fix it to communicate with the tv correctly? That way people can set their TV's to automatically detect the RGB value. I have my consoles connected to an HDMI box and two of them only output in Limited mode only. All of the consoles work with auto detect except the AVS.

Got a reply from retrousb support. They said they would look into adding support for Smooth and Wavebeam.

Tell them to keep unsaturated.  

Sweet

Anyone else notice that on 1.30b5 if you enter game genie codes, start a game, and then return to the menu, codes 2 through 4 have their last letters changed?

I mentioned this issue earlier in this thread and even reported it to retrousb support more than once. Last year and again this year. No response from anyone here or from retrousb. This bug has been around at least since 1.20x but there seems to be no interest in addressing it. I have seen the issue with power-pack and regular carts.
 

1.30b6 is up. Game Genie issue is fixed.

1.30b6 is edging closer to perfection. I'll probably do an update video on the AVS in late summer. Keep up the good work!

Still has an audio issue, though.

Alright, I'm back in action. I can confirm/second that there's some new audio clicking in 1.3b6. It's not as bad as earlier 1.3 betas, but it's definitely there. If anyone's asking me, 1.3b5 should probably be considered official 1.3, as I've yet to find any problems with it other than the game genie issue (which doesn't affect me, since I don't use it).

I would agree.

Though complete GG functionality is a nice feature.  

Did you report the audio to [email protected]?
 

Just did.

Thanks!   I reported it about two weeks ago, but they hinted that Bunnyboy might be away for spring break. I think he's back this week, though.

I don't know if it needs thirded or not, but I finally got around to testing/playing with my launch AVS after installing the updated 72-pin connector a couple of weeks back and can confirm that after updating to 1.3b6, there's definitely a lot of random crackling/popping going on audio-wise. If I had to guess, I'd say it might be related to some sort of memory access? The reason I think this is that while it was kind of random during gameplay (real cartridges or Everdrive ROMs), it was constantly noticeable and had a bit of a pattern to it anytime I was working within the OS/menus of my Everdrive. It reminded me a lot of noise you can/could get from RF interference with powered speakers and cell phone traffic and, in the distant past, old MFM/RLL hard disk accessing. I'll have to load a copy of 1.3b5 and see if it goes away.

Just got an email saying they're aware of the audio issues  

Same here.

I'm in no big rush as the 1.30b5 only has the Game Genie issue, but it would be nice to have it done.

I just checked and found out I got the same message as well as the suggestion that I go to b5 as the only difference between the two is the Game Genie fix. I've just about never used a Game Genie during my entire life, so that's not exactly a problem for me, lol.

I made sure to thank the support person and also bug them about new palettes and more accurately pixel aspect options. Hopefully we'll see that in the next month or two  

Just adding palettes, right? No dumping of the ones already there.