Requests

[sirius]

Some further requests.

1. Would it be possible to include in the three dot menu for tracks the option to access the 'Effects' option in the main app menu? This would allow direct access to the 'Tempo' adjustment, without having to click back through the albums to the main app menu each time a track is played This would greatly help the adjustment of the tempo for dance music for those learning dances.

2. Also some means of returning the Tempo setting to 100% without having to fiddle about with the slider bar e.g. when it is disabled it automatically returns to 100%.

3. Also, could the 'Comment' variable be made available for the same views as 'Genre', especially the 'Song/Album Details' view? The 'Comment' variable is useful for including basic dance description.

[GoneMAD]

1) No plans on doing that. You can use the drawer to access the effects UI quickly
2) When disabled it will no longer apply any tempo changes (so would go back to 100%)
3) Comment is not indexed in the database, so its only available in views that access the tags of the file (like now playing)

[MotleyGord]

Nov 7, 2022 10:41:31 GMT -5 GoneMAD said:

3) Comment is not indexed in the database, so its only available in views that access the tags of the file (like now playing)

This is a good thing to not include the comment field, as often the comments field can have a large amount of information. This would very likely clog up the database and negatively impact the scan times.

[sirius]

Thanks for your reply and these are my comments (with apologies for the delay).

1) OK but it's not as convenient, especially for non-techies, as being able to access just the Tempo effect from the three dot menu, as can be done to change the volume. Ideally it should be as simple as turning a knob as is usually the case with hardware such as CD players.

2) When the Tempo effect is disabled the player indeed reverts to 100% but not the effect which remains on its last set setting.

3) For display purposes the Comment field could be restricted to the first n characters.

[GoneMAD]

Feb 16, 2023 13:31:56 GMT -5 sirius said:

Thanks for your reply and these are my comments (with apologies for the delay).

1) OK but it's not as convenient, especially for non-techies, as being able to access just the Tempo effect from the three dot menu, as can be done to change the volume. Ideally it should be as simple as turning a knob as is usually the case with hardware such as CD players.

2) When the Tempo effect is disabled the player indeed reverts to 100% but not the effect which remains on its last set setting.

3) For display purposes the Comment field could be restricted to the first n characters.

2) what do you mean? When tempo is disabled playback is at 100%. That is your desired behavior and that is what toggling the tempo setting does

3) Display purposes are not the issue nor what motley was talking about

[sirius]

2) I meant that when the Tempo effect is disabled the playback reverts to 100% but the Tempo effect control still shows the last setting (if it was not 100%) and does not revert to 100%. NB it would be worth taking look at the Audipo app which has quite a user friendly interface for changing the tempo.

3) Sorry, I had understood Motley's comment to mean that the Comments field could have a large amount of information which could clog up the database and would impact scan times, which seems reasonable. My suggestion may have been poorly expressed but it was meant to say that if only the first n characters of a Comment were processed then the clogging problem might be prevented, so that the Comments field could be included in the same views as for the Genre field.

[GoneMAD]

Feb 18, 2023 16:05:14 GMT -5 sirius said:

2) I meant that when the Tempo effect is disabled the playback reverts to 100% but the Tempo effect control still shows the last setting (if it was not 100%) and does not revert to 100%. NB it would be worth taking look at the Audipo app which has quite a user friendly interface for changing the tempo.

3) Sorry, I had understood Motley's comment to mean that the Comments field could have a large amount of information which could clog up the database and would impact scan times, which seems reasonable. My suggestion may have been poorly expressed but it was meant to say that if only the first n characters of a Comment were processed then the clogging problem might be prevented, so that the Comments field could be included in the same views as for the Genre field.

its not supposed to return to 100%. The UI gets disabled and the seek bar gets disabled clearly indicating the effect is not being applied. Every effect works this way. Its intentional and how most user interfaces are designed. If it would return to showing 100% then you would have no idea what tempo is going to be applied when reactivating the effect

there are no plans on reading the comments field into the database. Your proposed solution would only open up more questions when a user has a comment longer than whatever character limit is set and wonders why the whole comment field isn't usable.