I posted it here. I posted it to my wordpress site, where I it gets a few hits a month. Try Honda,

http://automobiles.honda.com/handsfreelink/

Click on the connectivity button.

At the time I did this, the above was not available.

Sorry for the necro-thread. But is this the current thinking on best practices for making USB media with a high level of compatibility (esp for cars)?
FAT32 storage format
ID3V2 tags in ASCII only
VBR (high bitrates are ok)
no "bit reservoir"
yes strictly enforce ISO

Other parameters:
no files larger than XX MB?
No more than YY folders at a given level?
No more than ZZ directory tree levels?
No more than NN files per directory?

I will post back later when I have more info; however, the current working theory is that its not CBR versus VBR. I have a stick with VBR that works. Best guess its something in the tags, like no id3v1 tags, no utf-16 or utf-8 characters that are not ascii. Its a bitch when you possible combinations that include:

FAT or FAT32 or NTSF
VBR or CBR
iso or no iso
bit or no bit
id3v1 + id3v2
Ascii or utf-8 or utf-16

I just made a stick that was
FAT, VBR, ISO, no bit, ID3V2 only, and ascii that worked

Often the radio is made by a different brand (like Bose, Sony, Blaupunkt, etc.) As the issue is with the radio you may be able to get the answer you need through the maker, Honda may be able to at least provide info on the maker if you can't find it yourself (either on unit or through internet search).

Basically using the preset Compatible: CBR 128 kbps - Average Quality should work on pretty much everything that supports MP3.

See
I have tried Honda in a number of ways. My dealer, on Twitter, through the Honda owners support telephone line, which after bumping it up to the next level of support, basically said the information on what they support is unavailable. %^%^.

in first post.

I went to my dealer, sent them this link which has some more detail:
[url]http://www.crvownersclub.com/forums/13-dear-honda-feedback-forum/17417-usb-playback.html[/url]

Still nothing.

I'm not aware there are any rip setting limitations for MTP, if there are you should consult with the maker of the radio or Honda.

What settings do I use to synch/convert to a USB device so that it sort of kinds follows the MTP specification?

See
The sticks that I have problems with are formatted FAT32 and:

No security features. They play fine on my ubuntu laptop

[quote="GMGJ"]I do not think that if it says unsupported that you can make the assertion that its a problem with the device itself, unless you know exactly why the car is saying unsupported? Do you know that? [/quote]
What I mean is, it's more likely a problem with the formatting of the drive, or some security feature built into the stick, than the audio files causing that message.

I do not think that if it says unsupported that you can make the assertion that its a problem with the device itself, unless you know exactly why the car is saying unsupported? Do you know that?

I have tried created a number of different usb sticks, in different formats, most of which say unsupported, one of which briefly gave me a folder list then reverted to unsupported and one which plays fine (high quality VBR FAT32). What is unsupported?

The sticks that I have problems with are formatted FAT32 and:
2 sticks were created using Media Monkey and Windows Media Player in VBR
1 stick in CBR (most compatible)
1 stick in CBR with ISO compliance and no Bit reservoir used.
1 stick in wma format
These sticks work fine on at least 2 Windows 7 computers and a 2010 version of Linux Ubuntu laptop using multiple media players. According to Honda's specs, ( MP3/WMA) these should play fine.

I have a slightly more detailed post with more info pertaining to the lack of information here:
[url]http://www.crvownersclub.com/forums/13-dear-honda-feedback-forum/17417-usb-playback.html[/url]

What exactly is the problem? I don't know even after reading the thread whether the car cannot recognize the stick at all or what.

If the car says the stick is unsupported, then it's an issue with the device itself, it has nothing to do with the tracks on the device.

I am having problems creating a stick for my Honda CRV
see [url]http://www.mediamonkey.com/forum/viewtopic.php?f=12&t=68291&p=350033#p350033[/url]

When you synch with a device like an MP3 player or a phone,

is it common for these devices to require:
======
What would be a MM rip convert advanced option :
check -strict ISO Compliance
do not check -bit reservoir

These options are for the LAME mp3 encoder
for strict ISO compliance, see: http://webhelp.x-treem.net/WebHelp/Popu ... ce-ISO.htm
bit resevoir, see: http://wiki.hydrogenaudio.org/index.php ... _reservoir
=====
And for Tags

Options
Use only ID3V2 tags
ID3V2 tags in Ascii only

Thanks for the info. I have tried Honda in a number of ways. My dealer, on Twitter, through the Honda owners support telephone line, which after bumping it up to the next level of support, basically said the information on what they support is unavailable. %^%^. Options that fail:

anything not using advanced options (These options are for the LAME) mp3 encoder
check -strict ISO Compliance
do not check -bit reservoir

for strict ISO compliance, see: http://webhelp.x-treem.net/WebHelp/Popup_Topics/Encoder_Decoder/LAME_Switch_Reference/strictly-enforce-ISO.htm
bit resevoir, see: http://wiki.hydrogenaudio.org/index.php?title=Bit_reservoir
=====
Options
Use only ID3V2 tags
ID3V2 tags in Ascii only
====
FAT (not FAT32 or NTFS) formatted disks seem to work best

You can convert, but not strip ID3v2 tags out during conversion.

However you can select the files after sync (with or without auto-conversion) and use Tools > Advanced Tag Management. This will allow you to remove ID3 tags altogether or just ID3v2 tags. You may want to test using CB3 MP3 as Auto-Conversion format as the unit may trip up on VBR files. Lastly you may want to contact the manufacturer about any known limitations on the device or consult forums discussing the device.

I do not think I have a MM problem. I think the Honda CRV can't handle something in the MP3 files. My best guess is its 1) either ID3V1 or ID3V2 or 2) UTF-16.
I want to keep my library like it is. I have no problems with it. What I do want to do is convert on the fly or if that's not possible, run a script on the output to make the mp3 files readable. The system I use for converting is Windows 7 64 bit with 8GB memory and an I3 processor. It works fine for converting.