Digital FX 2.0 Transparent Released

**jarred** · 01-10-2007, 01:55 PM

Originally Posted by DeadlyAP1

John, one thing I noticed on the BlueDevil skin and now on the digital series, is that when you go to the "music" function, you are taken straight to the browser. Is this done for a reason? Personaly, I would rather go straight to the "player" skin instead of having to hit the button at the bottom of the browser skin to get there. Once my play;ist is loaded, I generaly don't need the browser skin unless I want to change. Maybe it's just me.

I didn't like it that way either, so I edited the music button in the menu skin file to go directly to the player.

**DeadlyAP1** · 01-10-2007, 02:40 PM

Originally Posted by jarred

I didn't like it that way either, so I edited the music button in the menu skin file to go directly to the player.

I will probably do the same, but figured I would mention it incase John wanted to consider changing it for future releases.

**JohnWPB** · 01-10-2007, 03:06 PM

The problem with manually changing the name of the skin to load is the "Audio" commands is an internal command used to load music, and the default "Audio_Player.skin". Changing the button to call a different skin, and not using the "Audio" command circumvents certain Road runner check sums.

For instance, if you are listening to Satellite radio, and return to the main menu, the playback continues. This allows you to go to GPS, the calculator ect, and still listen to the Satellite radio. Pressing the button with the "Audio" command, tells Road Runner you are going to go into MP3's, and to stop the satellite radio playback. Loading another skin manually with the button on the first menu, "Load;Audio_Full_Player.skin" will allow BOTH audio sources to be playing at the same time, as RR doesn't "know" that you are going to another audio screen.

To set it up properly the skins them selves need to be renamed, and then changing all 4 (including the Audio GPS screen) of the buttons on the bottom of the audio screens to call the correct skins when pressed.

**DeadlyAP1** · 01-10-2007, 03:07 PM

Ah, forget that!

I will leave it alone for now and hope you get enough demand to change it.

**DeadlyAP1** · 01-10-2007, 03:10 PM

Also, and this is probably a problem outside of your skin, but I have had an issue with XM. If I am listening to MP3 when I shut car off (standby), when it resumes, I can hear the XM over the MP3 and need to go into the XM skin and then go back to the MP3 to stop the XM sound. If I am listening to XM when I shut down, there is no MP3 when I resume.

I researched it some, and I have my mic setting muted on the volume control before I start RR. I also have the mic in set as the line to mute in RR config. Any suggestions?

**zap** · 01-10-2007, 03:39 PM

Originally Posted by JohnWPB

Added

(NICE logo by the way!)

New version will be posted probably later tomorrow afternoon. Still working on one last issue.

Thanks John for adding the Z71 logo it looks mighty fine with DFX.

-Zap

**jarred** · 01-10-2007, 04:48 PM

Originally Posted by JohnWPB

The problem with manually changing the name of the skin to load is the "Audio" commands is an internal command used to load music, and the default "Audio_Player.skin". Changing the button to call a different skin, and not using the "Audio" command circumvents certain Road runner check sums.

For instance, if you are listening to Satellite radio, and return to the main menu, the playback continues. This allows you to go to GPS, the calculator ect, and still listen to the Satellite radio. Pressing the button with the "Audio" command, tells Road Runner you are going to go into MP3's, and to stop the satellite radio playback. Loading another skin manually with the button on the first menu, "Load;Audio_Full_Player.skin" will allow BOTH audio sources to be playing at the same time, as RR doesn't "know" that you are going to another audio screen.

To set it up properly the skins them selves need to be renamed, and then changing all 4 (including the Audio GPS screen) of the buttons on the bottom of the audio screens to call the correct skins when pressed.

Thanks for the information, I'm still learning!

**JohnWPB** · 01-10-2007, 06:34 PM

Originally Posted by DeadlyAP1

Also, and this is probably a problem outside of your skin, but I have had an issue with XM. If I am listening to MP3 when I shut car off (standby), when it resumes, I can hear the XM over the MP3 and need to go into the XM skin and then go back to the MP3 to stop the XM sound. If I am listening to XM when I shut down, there is no MP3 when I resume.

I researched it some, and I have my mic setting muted on the volume control before I start RR. I also have the mic in set as the line to mute in RR config. Any suggestions?

That does sound like a specific machine issue. I have not see this here before, and am honestly not sure what could cause that to happen.

**KyACRASH** · 01-10-2007, 08:11 PM

I'm still having a problem with the date. My computer date is set fine, but when I open roadrunner digitalfx displays a date in the future (today it was october 1) and when i close roadrunner the computer date has been changed. I've tried using the same version of roadrunner but with different skins and this doesn't happen. Any suggestions???

**JohnWPB** · 01-10-2007, 08:44 PM

Originally Posted by KyACRASH

I'm still having a problem with the date. My computer date is set fine, but when I open roadrunner digitalfx displays a date in the future (today it was october 1) and when i close roadrunner the computer date has been changed. I've tried using the same version of roadrunner but with different skins and this doesn't happen. Any suggestions???

Hmm I'll have to get back to you November 12th.

That is strange, but I THINK I noticed something similar while using iGuidance in the car today. The ETA was 3:40am (It was only a 15 minute drive in the middle of the afternoon). I was thinking the CMOS battery has died, and brushed it off. I will look into it a bit more here and see what I can figure out if anything. Has anyone else noticed strange dates/times on their systems that conflicts with what the OS says?