V.6.2.5 (397) Not able to link to mp3

[W R Gibson (VintageGibson)]

Loaded in a couple of sets of lyrics, prepared in OpenSong Editor, and their corresponding mp3 files, but latest version won't let me link them.

The onscreen Link short cut allows me to find the required mp3 and this shows on the Song Features page in Edit. on this page if I set the field to Audio  file link this does not 'stick' when saved.

A long press on the onscreen Pad shortcut normally allows me to select Audio file link, but when I select this the app crashes.

Tried to revert to a previous version by downloading V.6.2.4 apk but could not install due to;

"App not installed as package appears to be invalid"

I believe this worked for me previously when I needed to revert to V.5.6.0 after checking out the V.6 beta.

I have a temporary work around to link the mp3s using an older tablet, not connected to internet and running V.6.1.4, then copy the song files across, but this is a bit tedious.

regards

William Gibson

[Gareth Evans]

Hi William,

Thanks for that information.  I've been able to replicate the crash and have a fix in place for the next release.

As to the other issues:

The onscreen Link short cut allows me to find the required mp3 and this shows on the Song Features page in Edit. on this page if I set the field to Audio  file link this does not 'stick' when saved.

I've done some investigating and found some bugs.  It does actually stick/save (you can check the xml song file), but it saves the wrong value for the <pad_file>...</pad_file> part of the xml file.  It should contain 'link', but it is currently saving "Audio file link'.  This means the pad logic doesn't understand what it is (as it looks for 'link') and defaults to the auto pad.  'Auto' will be shown from the pad popup window and the Edit songs page as a result.

A long press on the onscreen Pad shortcut normally allows me to select Audio file link, but when I select this the app crashes.

Crash fixed - this was due to the window trying to update the text when it didn't have permission (a coding error on my behalf!).  In getting this working, I discovered that clicking on the 'choose file' (if it didn't crash) also created a blank additional song named songname (1), songname (2), etc. each time you clicked on it with a filesize of 0b.  Some users have reported these blank files and I've never been able to trace how or where they were created.  They didn't do any harm, but irritated me.  I think I now know the reason!

Tried to revert to a previous version by downloading V.6.2.4 apk but could not install due to;
"App not installed as package appears to be invalid"

Actually, most of these bugs could have existed for a while (probably back to the original v6), other than the crash - that was actually introduced in v6.2.4 I think.  The 6.2.4.apk file shouldn't be invalid as it is the same file that I upload to the Google Play Store.  You have to uninstall your current version first before attempting an install.  Also, you may have updated security permissions on Android since you last tried this.  To allow you to download and run an apk file, you need to give 'special access permission' to the app used when downloading/running so that it is able to install from unknown sources.  Likely this is Google Chrome, but may be Google Drive or whatever your default browser is.  To do this, you go to Android settings >.Apps > Special access.  You can read more about this on the following website:

https://developer.android.com/training/permissions/requesting-special#:~:text=To%20grant%20a%20special%20permission,%3E%20Apps%20%3E%20Special%20app%20access.

Without these special access permissions or if you already have another version installed, you may see this error message.

As a temporary workaround to get audio link files working, you can set the file to use in the Link settings page (Settings > Song actions > Link > Audio File link.  (or use your page button shortcut).  Select the file by clicking on the 'Link' option.  Test the file using the play/stop button if you wish.  Click on 'Save', but don't bother clicking on the Pad option here (as it doesn't work properly as described above).  Next edit the song by going to Setting > Song actions > Edit (or double tap the song window in performance mode as the default double tap gesture).  Go to the 'Song features' tab and change the Pad from 'Auto' to 'Audio file link', then click on 'Save'.  This one does save the correct value to the song file.

I will release v6.2.6  this week (probably tomorrow or Wednesday) with these and other bug fixes, so you may want to wait until then.

Best wishes and thanks,

Gareth

--
When responding to a post on the forum using your email, please make sure to click on the 'Reply all' button so that your response is also sent to the forum for other people to see the full conversation.
---
You received this message because you are subscribed to the Google Groups "OpenSongApp" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opensongapp...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/opensongapp/9f89b437-a088-4807-963e-c89b01fb16d2n%40googlegroups.com.

[Ian Wanden]

Hi Gareth

I will be very keen to see if this fixes my issue with mp3 pad files as well, this started with the first version of v6. The level of change you managed taking us from v5 to 6 has been amazing, there's always a few things to bolt back on with a big software change.   

As always thanks

Ian :V{D>

[Ian Wanden]

Sadly still no improvement on the Tab 8. I have access to the mps pads on the tab 4 but only by locking it to 5.6.0. 

On the Tab 8  now running 6.2.6 each time I try to run one of the mp3 files as a pad it reports "there is a problem with the custom auto pad set for this song". This is even though I have set the song to "audio file link".                                                                                                                                                                                                                                                                                                                                                                                                                                 

[Gareth Evans]

Hi Ian,

Can I clarify what you are trying to do?  Pads can be one of a few options

• Auto (based on the song key) using my built in pads/MIDI files
• Auto (based on the song key) using custom pad files you have - usually you will have at least 12 files, one for each key (you may also have minor key pads too, meaning 24 files).
• Link audio files (specific to individual songs).  
• Off

I think you are using the second option?  If so, the pad should be set to 'Auto' and the song should have a key specified.  When you load the song, the app will use the pad file that matches this key.  If you haven't specified a custom pad, it will use my MIDI files, if you have specified a custom pad for that key (NOT an audio link file), the custom pad file for that key will be used.

You set the file for the custom pad using Settings > Song actions > Pad > Custom

The audio link file is different and must be set for every song individually.

Can I also check that the custom pad files are stored somewhere inside the OpenSong folder such as OpenSong/Pads or OpenSong/Media?  This ensures the app has permission to use them (really important on newer versions of Android).

Gareth

To view this discussion on the web, visit https://groups.google.com/d/msgid/opensongapp/aab07815-eb87-400c-aa97-f54a7eb85372n%40googlegroups.com.

[Ian Wanden]

Hi Gareth 

Yes I have been in via settings -> Song Actions -> Pad -> Custom and set the following.

With that loaded in the settings I got the error code "there is a problem with the custom auto pad set for this song" when using start pad from the page buttons. While this was in the background changing to Auto or changing to a specific Pad file via page button selection didn't change anything.

Tonight I have deleted all the custom list shown above. I don't seem to be able to delete the audio file link in the same way as the as the custom list where I was simply able to select the item and back step in my files several times and it would bring me back to a cleared entry. Pushing the start here again brings up the error message "there is a problem with the custom auto pad set for this song"

   

Changing from Audio file link to Auto does indeed bring up your old midi.

Changing to off stops everything and gives me predictable message as I was curious enough to use the start button tha "Pads are switched off for this song"

Interestingly changing back from either Auto or Off still displays the same file  and path.

Ian :V{D>

[Gareth Evans]

I wonder if it is because you have them in a sub folder inside of Pads.  I'll investigate

To view this discussion on the web, visit https://groups.google.com/d/msgid/opensongapp/61969914-bb85-4f82-b46b-4c2c44437ec4n%40googlegroups.com.

[Gareth Evans]

Hi Ian,

Got it - they always say a picture is worth a thousand words!  Your screenshots of the file locations ../OpenSong/Pads/WT-Pads-8-Wondrous-Pads/PADNAME.mp3 was key to spotting the issue(s) there are 2!  Screenshots and videos really do help with debugging issues!

Firstly my code did not consider custom pads being in a subfolder inside the OpenSong/Pads/ folder, so that part was throwing an error as the file didn't exist where the app was looking.

Secondly, because you had the name "Pads/" at the end of the subfolder, "WT-Pads-8-Wondrous-Pads/", the app was removing this from it's search, so it was actually looking in the OpenSong/Pads/ folder for a filename "WT-Pads-8-Wondrous-PADNAME.mp3" which also didn't exist.  An error that would have shown up if I'd simply coded for subfolders (I saw this as I set my test device up to use a pad with the same name and subfolder as you).

These bugs would exist for custom pads, audio link files and Background images if they were in subfolders as the code is part of the logic that converts 'localised' ../OpenSong/ file links into actual file links that Android understands with the full file path.

I've got a fix in place for the next update and hopefully that will get you working again properly!

Gareth

[Ian Wanden]

That makes a lot of sense. 

As always thanks Gareth, I will end up with both tablets back to the same version. 

[Ian Wanden]

LOL interestingly I spotted todays Facebook memory from 9 years ago explaining that i'd been using a wonderful app for a couple of years called OpenSong. Its been an amazing journey and I and many others are grateful to your work. Some people are evangelists, some are teachers, you have enabled many many worship leaders world wide to enhance what they do. Some people are reached through preaching, some initially are reached by the spirit through a song, please never underestimate what effect you have had on many churches and fellowships throughout the world. 

Ian :v{D>