Open Beta Version 3.1.0

peter

Beejaywh Thanks, I appreciate it.

DickyDutch Damn, that's the code that fixed the keyboard staying open when editing start and stop times. I might need to remove it or think about something else.

What exactly does not work with the history? The change was that a song will be added to the history tab if you play at least 50%. And that works for me. If less than 50% has been played, it is not added to the history tab.

EDIT: A quick workaround to open lyrics editor is to do a long touch on that field. But I will come up with a fix.

Beejaywh

Just checked the history again, as Peter says as long as >50% played even if starting part way into the song it works on both my machines.

Beejaywh

Sorry Peter,

We’re close but not quite there on the midi stop start for what I’m after (sorry, I know I’m a pain)

how I have been operating is by putting lines at the top of the lyrics file like this:

[midi: PC1@2, CC28.120@2, CC114.127@2]
[midi@00:00.01: CC114.0@2]
[00:23.68]Wake
From your sleep

This has the effect that when the previous song finishes the new song will load the top, none timestamped line and send the code out. This switches my reverb off and my lighting to a set pattern etc. The second line switches them on and flashing etc.

If I had no midi commands in a song the play button will now send any assigned commands in the settings play field thus taking care of my current second line but there is nothing to send the first line commands at the natural end of a song. Thus there is no way for a default set of strings for all songs without editing the lyrics of each

although I have not tested it yet, I’m presuming the song start commands would not be sent if auto play was used.

in effect what I’m saying is that to make it work properly it should be the song coming to a start or stop either at the beginning/end of a song or anywhere between (via any method) rather than the action of the press button itself.

hope that makes sense to you

and you thought you were going to have a nice relaxed Saturday with your feet up lol

regards Brian

peter

DickyDutch Might be a rounding issue, or do you maybe trim your songs? I guess the current code does not account trimmed starts or endings, I will take a look.

Beejaywh Currently the commands are for pressing the start stop button. So they are only triggered when you actually touch that button.

So if I understand correctly you would like to have global midi commands for start of playback and end of playback, right? But what is start and end of playback? Is it for each song, or if you have autoplay start will only fire at the beginning of the first track and end at the end of the last track with autoplay? And how about crossfades? If you crossfade, the start of a song is triggered before the end of the previous song!

I'm not sure this can be accounted for with global midi settings. With timecoded midi you can omit the song end commands when you know that another song will follow with autoplay (and possibly crossfade). On other songs, you can send reverb off right before the end.

Having a global song start playback and end playback midi command could lead to some nasty unwanted situations.

DickyDutch

For me the history seems to work @ 50% on some songs but not others. I’ll do more testing to see if I can provide more details. I confirm that a long touch on the playlists, lyrics and key words editing files works as a temp work around.

DickyDutch

Have just taken three songs at random - the longest 4.22 mins, the shortest 2.54 mins, the other 4.06 mins. I’ve just played them as normal from start to finish uninterrupted and they all show in the history as being played. I’ve cleared the history and played them each again but stopping them manually just after their midway point. None of them show in the history. I’ve done this in both the advanced queue on and off modes with no difference. The test was done on my iPad 6th gen running the very latest official ios. Regards Richard.

Beejaywh

peter hi Peter,

can I suggest I come back to this at a later time as I don’t want to hold up the 3.1 release. The changes already made are more important to get into the field.

Again, thanks for the efforts

peter

New beta build 4706

Small bugfix release for last update.

Changes

Fixed song details dialog to allow lyrics editor, keyword view and playlist view to be opened again
Fixed history add trigger to use the trimmed song length

TimN-MK

peter OK I have the lyric editing back!
When I use the iOS multitasking and float StageTraxx over AUM, I can indeed see the song name scrolling back-and-forth. However when in full screen mode I would also need this as well in the Queue/Playlist screen so we pick the correct version for the Queue etc.

peter

Beejaywh Agreed, let's discuss this in a separate thread in detail.

DickyDutch Hm, that's really strange, I absolutely can not reproduce this problem. I tried all button stop modes with or without fade and also double tap to stop and it always works as expected. So what is different on your devices?

DickyDutch

Hi Peter have just loaded build 4706 and still have problem with the history. I’ve just played a song that is 2.54 mins long (with no trimming at either the start or end) and let it run to almost the end ( about a couple of seconds before) then pressed stop. It didn’t show in the history. I therefore seem to have an issue if I press the stop button.

peter

TimN-MK Oh, you mean in the list view on the left side? I'm afraid the scrolling of these entries would take up too much cpu. Maybe a setting to enable dynamic text sizes is really needed in this place. I will think about it.

peter

TimN-MK I tried it on one screen and reducing the font size for long titles is working ok if a minimum size is set. But I'm not sure you win that much more information that way. See this example:

A smaller font is not readable enough and with this font you gain maybe 8 additional characters.

Question: Any other opinions? Should the font size be constant or dynamic as in the above screenshot?

JDSMUSIC

I used latest beta last night without any major problems. One thing that seemed strange. With automatic scrolling enabled the lyrics pane would occassionally "jump" a line... hard to explain but whild doing smooth scroll scrolling as it normally does it would have a line jump about every 6 or seven lines. I was running on latest version of an iPad and doing a Hosted session where another iPad running ios 12.5.4 and an iPhone 6 running ios 12.54. Later today I will set them up and try it and video the screen with my newest iPhone.

peter

JDSMUSIC Did it jump on the host or on the clients? Jumping on the clients might happen if clocks run out of sync which most certainly happens if the playback speed is altered. The host sends his current timestamp every 5 seconds to the clients and if they run out of sync, lyrics might jump.

JDSMUSIC

JDSMUSIC If it matters... neither client was running the beta version....

JDSMUSIC

peter It was jumping on the host. Dont know about clients ... other side of stage... I will update the clients to the beta and check the clocks.

Thanks

peter

JDSMUSIC This will also happen with the beta version. I did not change anything in this regard. The problem is that due to network latency there will always be asnychronous clocks on the clients especially if you speed up or slow down your songs.

Only thing I could do is to decrease the time between the two sync messages to maybe 2.5 seconds. It might still jump, but less.

But you say it was jumping on the host. That has nothing to do with the network clients. I haven't seen that so far on my device. Can you reproduce it? If so, how?

peter

JDSMUSIC Could it be that the jumping occured only for songs with a long title that was scrolling?

JDSMUSIC

I don't know that I have any titles over one line.. Never saw it happen on current (not beta) version. As I said, I will try to reproduce later today....

« Previous Page Next Page »