Recent Posts

11

Repertoire Help / Re: Saving Text Size

« Last post by avdb on September 29, 2023, 04:03:59 AM »

I can confirm your observation Jerry. I also had a few songs that suddenly displayed partial HTML commands. After deleting and re-saving the displaying of lyrics seem to have gone back to normal

12

Repertoire Help / Re: Saving Text Size

« Last post by JerryK on September 28, 2023, 01:32:13 PM »

I can confirm this behavior after last update.  Previously saved text sizes were reset. But in addition to that, I also noticed some weird behavior in lyrics in standard txt format that were previously entered via typing in webbrowser and worked perfectly fine. Now suddenly and for some unexplainable reason HTML commands appear without an understandable reason. After retyping the texts were fine again, though some of the colorization of text do not seem to work anymore either.
Resetting certain words in standard color in the webbrowser is not followed by IOS app

I've seen just a small amount of partial html code in the lyrics, not whole phrases.  I edited it out and was happily not a problem for me.  I supposed I was the cause in the first place but perhaps not.

13

Repertoire Help / Re: IRig Blueboard

« Last post by JerryK on September 27, 2023, 03:39:26 PM »

I tried not using their app but it was unreliable.
Use the app.
Don't ask me the details of the trouble, it was several years ago.

However, I can tell you I use just the 4 buttons, in CC mode (control change).
They are assigned to Midi channel 16 and controller numbers 80, 81, 82, 83. 
In BH, App Control, I chose Midi input port: Blueboard, channel 16, button style Latch.
Key repeat timers 0.2 and 0.5

Down in the Actions section (Choose ALL actions or many are hidden - my choices of button layout - in order of those choices in BH):
  Next Song - General Button 4 (cc83) - Next song
  Scroll doc up - "  "  1 (cc80) - Scroll up AND previous song when it gets to the top
  Scroll doc down - " "  3 (cc82) - Scroll down a bit
  Reselect cur song - " "  2 (cc81) - Start song

Some nice Dymo labels on the buttons and it has worked ever since.
I did get inside and cut the circuit board tracks feeding the 4 button LEDs, mostly because they go on and off with alternate presses of that button, which was annoying, but it seemed to me that I would save some battery life too.

You have to run the Blueboard app every time, to choose the Bluetooth device to talk to - the iPad for me.  It's easy.

14

Repertoire Help / Re: IRig Blueboard

« Last post by arlo on September 26, 2023, 10:36:01 PM »

Did you try the instructions on this page?

http://forum.arlomedia.com/index.php/topic,484.0.html

At what step did you get stuck?

15

Repertoire Help / IRig Blueboard

« Last post by bdbarr on September 26, 2023, 08:17:16 PM »

Im haviong a real hard time getting my iRig Blueboard to talk to the Bandhelper app. Im a novice at this and not familier with Midi and all I want to do is use the Blueboard to move from one sog to another in the setlist on Bandhelper. Any insight would be appreciated.

16

Repertoire Help / Re: Sending pinned midi on song end

« Last post by Ahiru on September 26, 2023, 06:21:14 AM »

If you want to accomplish the OP's objective but avoid the use of pinned MIDI, consider using an approach where the end of the previous song triggers First Song Selection for the next song, but the automation for that next song does not start until Second Song Selection (e.g. by tap or switch).

Then the first attached MIDI in each song (which would be sent on that First Song Selection as a result of ending the previous song) can include all sorts of 'utility' commands appropriate for both ending the previous song (turn off harmonizer, turn off reverb, set lights for talking, turn off song recording, etc.) and getting ready for the next song (e.g., setting initial instrument presets).  Since a BH MIDI preset can contain a list of other MIDI Presets (which can contain other presets, and so on), you can define one globally useful 'end of song' preset, which you include in the first attached preset for each song along with whatever other presets that song needs for unique 'getting ready' settings.

(I'm not a fan of positional references to pinned MIDI, since I use them more as globally available 'emergency' buttons on all layouts, so it feels like forcing one data structure into two rather different use cases.)

17

Repertoire Help / Re: Saving Text Size

« Last post by arlo on September 25, 2023, 09:34:58 AM »

For the new problem mentioned by avdb, please submit a help ticket.

For the original problem, please try force-quitting and restarting the app. That would address a bug where your local settings were not immediately updated when installing the latest app update.

18

Repertoire Help / Re: Sending pinned midi on song end

« Last post by arlo on September 25, 2023, 09:29:15 AM »

I would think that the previous layout MIDI was perfect, as it ensured that a particular midi-command (like FX-OFF, light reset etc) were ALWAYS sent at song end (in my particular workflow).

Unless you changed layouts or devices and forgot to attach the same MIDI presets in the same order to the new layout ... then it wouldn't work. That was a disadvantage of the previous approach.

Does change in workflow mean that besides being nondeterministic, I would now have to go thru each of the songs in my repertoire and verify that the correct midi preset is added to each song and actually is on the 1st position?

I think you're conflating attaching a MIDI preset, which works on a song-by-song basis, with pinning a MIDI preset, which makes a preset available from all songs without having to attach it to all songs. Attached MIDI presets work the same way they did before, and pinned MIDI presets take the place of layout MIDI presets.

19

Repertoire Help / Re: Sending pinned midi on song end

« Last post by avdb on September 25, 2023, 06:19:51 AM »

this seems a rather unexpected change to the previous Layout MIDI function that I had to figure out during a live performance....

And I concur with Jerry that this workflow may lead to non-deterministic behavior, which in my opinion is not correct for this particular function. I would think that the previous layout MIDI was perfect, as it ensured that a particular midi-command (like FX-OFF, light reset etc) were ALWAYS sent at song end (in my particular workflow). This regardless if the midi was pinned to a song or not, regardless of its placement in the midi preset list of that song. That was an ensuring factor.
If I understand the concept of pinned MIDI now correctly (but I had no way to really verify as the change-log pages of the website seems to be down?) is that now the only option is to send a pinned midi (#1?). Does change in workflow mean that besides being nondeterministic, I would now have to go thru each of the songs in my repertoire and verify that the correct midi preset is added to each song and actually is on the 1st position?

And even if this is the case, again, imho, this should be a deterministic workflow, regardless of what midis are pinned to a song or not.

But may be I am missing something here?

20

Repertoire Help / Re: Saving Text Size

« Last post by avdb on September 25, 2023, 05:50:13 AM »

I can confirm this behavior after last update.  Previously saved text sizes were reset. But in addition to that, I also noticed some weird behavior in lyrics in standard txt format that were previously entered via typing in webbrowser and worked perfectly fine. Now suddenly and for some unexplainable reason HTML commands appear without an understandable reason. After retyping the texts were fine again, though some of the colorization of text do not seem to work anymore either.
Resetting certain words in standard color in the webbrowser is not followed by IOS app