XMPlay Portable 3.6 Dev Test 1

I know the feeling about beta applications here, but I wanted to discuss the manner in which XMPlay is upgraded.

As people use the program and find issues and/or request features, the author puts out a new version of the .exe file. I won't post the link to that newest version since I don't need my wrist slapped. Suffice to say that anyone can look for the right "stuff" and download it themselves.

While I'm all for sticking with the "official release" version, it currently lacks several features that many people want, such as album art. You can install either of the two album art add-ons, and nothing will work, since the feature was implemented AFTER the last official release. Same goes for some of the library/history features.

And you are right about the skins. There are some nice ones. Unfortunately, the official XMPlay link you gave provides only a few of the skins. The official XMPlay support site has a different selection of skins. Further, there are some nice skins that are buried as posts in the XMPlay support forum.

And the last thing for this post is that some skins are "compiled", but others are available as a group of source files. The compiled ones are a lot smaller, but the source files can be manipulated (with a text editor or a graphics program) to tweak the skin or use as a start for your own skin.

Oh... someone asked today about having an online radio program available as a portable application. XMPlay does that, and it even records the stream, too.

Edit: I see Neutron was already on top of this.

I was recently discussing portability on the XMPlay forum, and mentioned your note about library drive-letter portability.

They pointed me to the library format, which may help?

; Copyright: Gringoloco023
; License: BSD  (NSIS license)
; define added by John T. Haller of PortableApps.com
Function RIF

  ClearErrors  ; want to be a newborn

  Exch $0      ; REPLACEMENT
  Exch
  Exch $1      ; SEARCH_TEXT
  Exch 2
  Exch $2      ; SOURCE_FILE

  Push $6     
  Push $7   
  Push $R0     
  Push $R1
  Push $R2
  Push $R3  
  Push $R4  
  Push $R5    

${registry::StrToHex} $0 $0
${registry::StrToHex} $1 $1
IfFileExists $2 +1 RIF_Error
  FileOpen $R0 $2 r                 ;open file to read
  GetTempFileName $R2               ;get temp file name
  FileOpen $R1 $R2 w                ;open temp file to write
                RIF_Loop:
                StrCpy $R4 ""
                StrLen $7 $0                      ;Set lenght of search text
                StrCpy $6 $0 2 0                                      ;get first character of search text
			RIF_ReadLoop:
				FileReadByte $R0 $R5                   ;read byte
                                IfErrors RIF_End                       ;no more bytes
				IntFmt $R3 "%02X" $R5
				StrCmp $6 $R3 RIF_Found                ;found first byte
				FileWriteByte $R1 $R5                  ;write non important byte
			Goto RIF_ReadLoop

			RIF_FoundLoop:
                                StrCpy $6 $0 2 -$7                     ;get next byte of search text
			        FileReadByte $R0 $R5                   ;read next byte
                                IntFmt $R3 "%02X" $R5
			RIF_Found:
			        StrCmp $6 $R3 0 RIF_Write              ;found next character / not found, write saved bytes
				StrCpy $R4 "$R4$R3"                    ;combine found characters into string
                                IntOp $7 $7 - 2                        ;decrease counter
				IntCmp $7 0 "" "" RIF_FoundLoop        ;counter zero, last byte
				StrCpy $R4 $1                          ;write replacement bytes

		        RIF_Write:
				StrLen $7 $R4                          ;lenght of bytes, as counter
				RIF_WriteLoop:
				        StrCpy $R3 $R4 2 -$7           ;get first/next byte
				        intfmt $R3 "%d" "0x$R3"
				        FileWriteByte $R1 $R3          ;write byte
				        IntOp $7 $7 - 2                ;decrease counter
                                        IntCmp $7 0 "" "" RIF_WriteLoop    ;counter zero, last byte
                                IfErrors RIF_End                           ;no more bytes
                                StrCmp $R4 $1 RIF_Loop
                                        StrCpy $R4 ""
                                        StrLen $7 $0                      ;Set lenght of search text
                                        StrCpy $6 $0 2 0                  ;get first character of search text
				        IntFmt $R3 "%02X" $R5
				        StrCmp $6 $R3 RIF_Found                ;found first byte
				        FileWriteByte $R1 $R5                  ;write non important byte
			         Goto RIF_ReadLoop

  RIF_End:
    FileClose $R1                   ;close writen file
    FileClose $R0                   ;close read file
    Delete "$2.old"                 ;delete old file, if still exists after last replace
    Rename "$2" "$2.old"            ;rename original file
    Rename "$R2" "$2"               ;move/rename replaced file
  ClearErrors
Goto RIF_Out

RIF_Error:
    SetErrors

RIF_Out:
  Pop $R5
  Pop $R4
  Pop $R3
  Pop $R2
  Pop $R1
  Pop $R0
  Pop $6
  Pop $7
  Pop $2
  Pop $0
  Pop $1

FunctionEnd

!macro _ReplaceInFile SOURCE_FILE SEARCH_TEXT REPLACEMENT
  Push "${SOURCE_FILE}"
  Push "${SEARCH_TEXT}"
  Push "${REPLACEMENT}"
  Call RIF
!macroend

!define ReplaceInFile '!insertmacro "_ReplaceInFile"'

Done testing changing the driveletter and back again, after checked the file with WinMerge !
Also done a quick test on the push and pop's, all the variables stay ok.

The following is a zip file containing the exe,nsi & nsh files.
Just unpack them into the XMPlayerPortable folder, and use XMplayerPortableFix.exe to start XMPlayer, you will see the Library will be updated !

XMPlayerPortableFix

Ps.:I've tested it with Cyrillic, just the XMPlayer tab bar seems to not show the Cyrillic well, but that is probably related to something else.
And I've found a bug, when updating it but the $OLDDRIVE is empty, it seems to mess things up. It definitely needs more testing !

Well, the discussion of "beta or not" has been concluded.

Version 3.5 was just officially released.

I developed a new plugin, to use instead of ReplaceInFileWithUnicode.nsh !

It's based on the same code as the normal TextReplace plugin, so it shouldn't have (m)any bugs. As well it is a much faster solution, than the macro XMPlayPortable is using now!

My self I have tested it on several files including 'xmplay.library' and UTF16LE files.

So you would do me a favor if you could include it in XMPlay Portable for additional testing !

https://portableapps.com/node/21840

Thanx

this is just a random comment about XMplay and a "feature" with skins. I have no idea if this issue has been fixed and it was part of XMPlay itself, nothing to do with the portable version so perhaps it's not even relevant here. However, I recall that paths to skins were saved as absolute and so consquently XMPlay would revert to the default skin if you used it from different locations with different drive letters etc.

Is this an issue here? I'm assuming not, since the launcher probably handles all that business. I supposed I should give XMplayPortable a test really shouldn't I, since it is my preferred MP3 player.

Looking forward to this one hitting the shelves.

Any problems with 'NewTextReplace' so far ?

I would appreciate it if you would update to the latest 'NewTextReplace Beta 4'.

Sorry for all the updates, and changes in the usage, but this version is basically the final major update.

It's configured so all you have to do is, include NewTextReplace.nsh, and it works in combination with ReplaceInFileWithTextReplace.nsh
Do away with 'UTF16.nsh'

This is all, cause I finaly code all of it in C, and could do away with the additional NSIS macros.

I am eager to utilize the portable path problem with XM Play. I downloaded the installer. It throws an error saying it cannot download XMPlay 3.6

I downloaded 3.6 manually, and placed in existing portable apps directory for 3.5, and 3.6 works, but I am fairly certain the install does not reflect the new version portable apps (it is running 3.6 XMPlay).

Any ideas?

Thanks.