Jump to content

Album Art on 2014 Intelilink


Recommended Posts

Posted

Ok, so I have my music library loaded on a sd card and everything plays fine. I did a direct copy of my Windows 7 music directory which was being handled by Windows Media Player. Files are in .mp3 format. I noticed that the album art files were in each directory but had hidden and system attributes. I undid the attributes now the files are visible .jpg's. The .jpg's sizes are small. All the ones I checked were well under 500x500.

 

So okay, how do I get the album art to show when the music is playing vs. sd card graphic?

 

Posted

For me, sizing to 500x500 or below made mine appear.

I saw someone one here had issues b/c there were two img files attached to mp3, one at 500 and the other above. Check if your files have more than one.

 

If they don't, maybe try using a different software to view the mp3 tags (in WinAmp for example, you can see all 3 types of tags. Maybe there's something there that should be? Dunno?)

Posted

That's why I mentioned the 500x500 because of your post. Looking in the directory, it appears Windows actually places four art .jpg files. All of these files are under the 500x500. Maybe I don't need them all? They are all of the same album picture.

 

All are titled:

 

AlbumArt_{xxxxxx}_Large.jpg

AlbumArt_{xxxxxx}_Small.jpg

AlbumArtSmall.jpg

Folder.jpg

Posted

Just went through the whole thing and deleted all the extra .jpgs except the main one which appears to be the "folder.jpg" that appears in every subdirectory. Put it back in the truck and I still see the same thing, no album art. Grrrr..... Wonder if there is a way to have the truck rescan the sd card?

Posted

Just went through the whole thing and deleted all the extra .jpgs except the main one which appears to be the "folder.jpg" that appears in every subdirectory. Put it back in the truck and I still see the same thing, no album art. Grrrr..... Wonder if there is a way to have the truck rescan the sd card?

 

Are they separate jpg files in the same windows folders as the mp3's? or are they actually embedded in the mp3's tag and aren't visible when looking at files in windows folders?

Posted

They are all separate files. Each is labeled "folder.jpg" and each one is located under the album folder right next to the song files. They are all visible.

Posted

They are all separate files. Each is labeled "folder.jpg" and each one is located under the album folder right next to the song files. They are all visible.

Yeah, those aren't embedded. You shouldn't have any files on SD other than the mp3 files and playlist files if you created any.

 

I'm not that familiar with WinMedPlayer... if you open mp3s in iTunes, right click song, & choose Get Info, the Artwork tab lets you add/embed images to the mp3. If more than one song has the same artwork, you can select multiple before right-clicking & change them all at once. I know in WinAmp (simply free music player) you can also do the same.

Archived

This topic is now archived and is closed to further replies.

  • Latest Articles

  • Posts

    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...