Posts by dango123

For me, the million dollar question is how this enhancement will work with the (now) legacy products - I'm guessing the new MK2 machines have full backward compatibility with all legacy profiles, but will the legacy toasters/racks/stages be able to play profiles made with the new tech (with processing limitations on the number of effects etc. based on the old architecture)?

Interesting that the OS13 updated recently posted is for all machines, Legacy AND MK2 - so perhaps the old machines will play the new profiles, and just be limited as per my earlier comment... Fingers crossed on that one... Given that I have a Toaster AND Player, I would hate to learn that they would no longer remain fully compatible with each other as future updates are rolled out.

Quote from tunetown

- For the display issue: I can recreate that, totally makes sense. I'll fix it with the next update.

- Normally the first defined page should be the default....which i just confirmed in the emulator. Perhaps you have page 2 defined before page 1?

- Multiple Displays: Have to think about that. Would make sense, but as always, labels are a RAM issue. However, this could work by having a display callback which would listen to a pager. However, this would mean 1) that we would perhaps get circular imports and 2) that this has to be added in a way that we can still have the tuner splash callback....not soooo easy.

Thanks!

Re: my point about what page comes up at start up, this is the start state on my controller as soon as I powered up:

You can see it’s not one of my programmed page designs, the white lights at top are new and the middle display looks a.little different as well.

When I press/select page 1, it looks correct.



Certainly not a big deal, but it doesn’t seem to be starting at page 1 in my model. You can see the actual code in the latest zip I just shared.

Thx again!

Dango

Quote from dango123

Just a quick share of my latest layout - comprised of 3 independent pages for Rig Mgmt, Effects, and Looper control. tunetown I will post a zip of my files later today when I am in front of my mac again Also - you can see in these screenshots the minor issue I mentioned earlier re: the missing ribbon that would have the page titles on it within the display - would be really cool if that could be added back into the Select Page function (but certainly not a big deal at all if that's not possible).

Display More

FYI - here's a zip of my latest files for posting - thanks! This latest version (for me at least) is a nice step forward, I like the more detailed control over rig selection, and the standalone view of effects and looper - interested to see what others have to say about this.

Thanks!
Dango

Dango123v2.zip

Just a quick share of my latest layout - comprised of 3 independent pages for Rig Mgmt, Effects, and Looper control. tunetown I will post a zip of my files later today when I am in front of my mac again Also - you can see in these screenshots the minor issue I mentioned earlier re: the missing ribbon that would have the page titles on it within the display - would be really cool if that could be added back into the Select Page function (but certainly not a big deal at all if that's not possible).

Quote from seve

dango123 I managed to fix it and it works but every now and then this error comes out: see image! Thanks again

Hi - earlier in this thread, tunetown noted that the onboard memory in the Midi Captain units is quite small, around 200K if memory serves (pun intended) - I had the problem you are noting earlier on, but I guess my scripts got a bit more efficient as I developed them and I haven't had a problem in the last few weeks - but your unit has more buttons, and thus more options for creative/heavier script development (and thus the potential to max out memory). I imagine this is something that you need to address thru trial and error.

Quote from seve

tunetown dango123 Hi! Could someone help me! With the MC10 I would like to have all 8 effect slots as shown in the image but I can't insert the performance number above the rig name. Thanks to everyone for the great work

Sure - take a look at the Dango123 example (it’s for Mini 6 but will/should work for the MC10), I believe the display.py file has minor adjustments to display both the rig ID and name (but there may be some diffs in the input file as well, I’m not in front of my computer at the moment unfortunately).

I also asked the same question earlier in this thread ;). But my example should give you what you need (I think…).

tunetown - Hi - just touching base as I continue to play around with the emulator and make adjustments to my latest controller configurations (love the drag and drop abilities BTW!) - I noticed some things that i wanted to mention:

1) when I used the Select Page function instead of the Rotate Pager, I lost the ability to update some of the descriptive text in the Display - for example, I used to display "E F F E C T S" in a colored ribbon towards the bottom of the screen, but now I don't have that option - you CAN still do it if you use the rotating page option, but I couldn't figure out how to do this when using Select Page - could I be missing something? If this is unclear, you can take a look at the Dango123 example, and you'll see the colored ribbon - this disappears when using Select Page.

2) when I used the Select Page function, on startup the controller seems to start at page 2, not page 1 - is there any way to control the initial page?

And finally, one additional question about the display controller - would it be possible to have multiple display options (e.g.. one view that is optimized for rig mgmt, maybe to display more of the target profile names, vs. a second view that is optimized for effects and looper display)? Certainly not a big deal, but could be good to have in tailoring the overall UI in specific instances.

As always - THANKS for putting this all together, it's really an invaluable add-on to the Profiler (not sure how people get on without it actually ).

Dango

Quote from JCW308

This is not.a Kemper issue. It's not about reliability. This is a training issue and that's a good thing. I would suggest all of what everyone else said and add using access point mode only may help, even when home. Also, try turning off cell data before connecting to the Player.

Thanks for the comments, and you certainly may be right... but at the very least I would humbly suggest that Kemper has a User Experience issue in this area, since I'm not the only person that has reported this type of problem (and I've also noted that others have had to experiment and come up with their own workarounds to make the onboard wifi perform as intended). Note that I've gotten this feature to work at home, and then watched it fail on the gig - 3 times. I may need additional training as you recommend, but that's a pretty finicky area of functionality

Also - limiting use to the onboard access point is not the greatest solution as it means I have to deactivate my home wifi on my phone since i can't use both hubs simultaneously.

I appreciate everyone's advice on this and will keep at it (and let you how it goes)!

Quote from timo

You can switch between Access Point Mode and Home Network Mode by holding [BANK] and tapping on [WIFI/BT]. Let your phone know both networks. The name/password is printed on the label on the backside of your Profiler Player.

I'll give this a shot and let you know how it works out - thanks

Quote from Wheresthedug

It sounds as though the Player is connecting to your phone ofer your home network but isn’t connecting via local access mode. This happened to me at first. I finally solved it by going into my phone settings and using “forget network” to clear the phone and then reconnecting. It appears the the issue was something on the phone itself.

Thanks - I've done it both ways at home - I can turn off my local network, and when I press the bluetooth button AT HOME I can see the Player wifi hub come up on my phone and connect - all good in that scenario.

But outside my home, I don't ever see the Player wifi hub appear - and the buttons on the Player itself don't seem to lock into the color that indicates the Player wifi hub is active. Very odd. While it very well could be my phone, I'd be surprised, since I can't see a wifi hub becoming active within the Player.

I have a Player that has consistently not connected as expected with my iPhone on my last 3 gigs - it works fine at home and I can even get it to start the internal wifi server. Outside my house however, it has never worked properly and I've had to struggle without any deeper editing capabilities on major gigs.

I've tried pushing the bluetooth/wifi button for 1 second - does not work. I've tried pushing the button for 8 seconds and the button flashes colors...and does not work. I've tried holding the button for 15 seconds, and, you've guessed it, IT DOES NOT WORK. Adding insult to injury, when I go home, it works immediately.

I'd be happy to learn out that I'm just doing something wrong... does anyone have some advice that could help me through this issue?

Thanks!
Dango

Quote from tunetown

dango123 it is not convenient to add pagers themselves to pages. you are thinking too complex: your requirement just needs ONE pager which will do exactly what you want: Rotate through pages. Just see the paging examples….you could have two or more pagers but this is another thing….when unclear, send me your files and ill show you

And: Yes you can directly talk with the controller when connected to the pc via USB! Just connect and then load the emulator, it will automatically load the config from it. Use the Save button at the top to flash your new version to it directly

Very cool - I went back and expanded my original layout - now i have 3 pages (rigs / effects / looper) as well as page toggling capabilities via the top row buttons (long pushes of button 1 for rigs, 2 for effects, 3 for looper) which IMO is more intuitive than my first effort - I'm giving this a real-world workout at a gig tonight, if it holds up I'll share this latest update for posting on the GitHub project (if that works for you of course!).

Interesting about the direct connect of the controller to the emulator - unfortunately that's not working for me at the moment. I'm on a macbook pro, running the emulator in Safari 16.6 - the emulator itself works totally fine but doesn't see the active controller on my machine - are there certain browser settings that need to be configured to make this work? Thanks again!!!!

Also - thought this might be interesting to some of the more adventurous forum members - I still find the looper a bit laggy on start, but as mentioned previously, clicking the designated start button has a built in delay because the switch has to travel nearly 1/4" before it engages - I opened up the mini-6 and worked out a modification to make a quicker connection - I found a small collar (5mm inner diameter) and tightened it on the shaft to shorten the switch travel - definitely an improvement, although this looper is still more finicky on start/stop than others I've worked with in the past - still, I found this helpful and thought others might want to know about it.

tunetown - got to experiment with the emulator - very very cool stuff!

I also tried out the select page logic and ran into a problem (at least via the emulator) - on a given button, I tried to add select page logic on different pages (so on page 1, the button directs to page 2, on page 2 it directs to page 1...) - when I added this logic to a single button, it only worked on one of the pages, the other one was non-responsive when pressing the button.

As an example, I took the Dango123 example for the Mini 6 and just added the aforementioned logic on button 3 - and as mentioned it only worked for page 1, not page 2

Hopefully this makes sense, but if not I'm happy to provide more info, so just let me know.

Also - is it possible to collect the emulator directly to a controller connected to my machine via usb? I was only able to use it when accessing the examples on GitHub.

Thanks again!
Dango

Quote from tunetown

Erikcb i also thought about some kind of "simple mode" which should be the default for the emulator, and "expert mode" for opening up all possibilities....perhaps you have an idea what to hide or show in these? I also think it is too overwhelming at first, but am too deep into the project to really see what is the thing that is too overwhelming, if you know what i mean

ps.: Updates coming up next week: Full paging support in the emulator, input help for colors etc.

Funny, I was just looking at your open items list in GitHub and saw that the page access updates were planned for the next release/sprint - REALLY looking forward to that, thanks so much for getting it in!!! FYI, I'm an IT consultant myself, love your agile approach to dev here

Now that I've had more real-world experience with the button actions, I find that having the effects on/off (short presses) and bank/rig changes (via long presses) on the same page is not an optimal "live performance" arrangement - both of these control types (effects and rig related changes) feel better as single/immediate pushes, and the extra long pushes becomes a little frustrating - I'm looking forward to breaking rig mgmt and effect mgmt out onto separate pages that can be directly toggled to (in addition to the looper page). Lets GO!

Thanks again for creating such a valuable offering to this community, I think alot of people will benefit (and frankly Kemper should be heaping praise upon you, as the Player without an effective midi controller is seriously hobbled as a live tool IMO).

Quote from tsachou

Still Not the sound i have ! the new updated sounds clearer than the last beta , but different than the official release .

Interesting, keep us posted as to how things work out. As mentioned, my A/B analysis was very close.

Quote from slateboy

if i understand correctly the player and the stage detect the pickup/guitar impedance and respond accordingly where as the rack and toaster do not.

Therefore, there will be tonal differences depending on the type of guitar even using the same presets/rigs

If i have this wrong please correct me, anyone.

Interesting, i thought the only difference between the Stage and Toaster/Rack was the form factor. I had not heard anything about differences related to pickup impedance functionality. I had read about something along those lines related to kemper fuzz box effects but not that it was applied in any other instances. Can anyone else here clarify?

Hi - I had previously reported audio issues in the 12.1.0 release, where there were significant differences between my Toaster on the latest Production version and the Player on Beta 12.1.0

Just a heads up that 12.1.1 seems to have resolved this problem, at least on my Player - the audio is now in line with what I'm hearing on my Toaster (I'd say ~98% the same - I do detect very subtle differences between the units, but I'm wondering if that could be due to issues such as component tolerances, etc.). Bottom line, I'm sticking with the Beta at this point

Just thought I'd share, as I know others reported the same issues I was experiencing. Thanks Kemper Support!

Best,
Dango

Quote from tunetown

Cool i just find it a bit problematic to have looper functions in the "hold" positions, because those normally require timing accuracy myself i use paging for that, see this example.... dango123 has created an example using this on the Mini 6

p.s.: I think it's super cool that i can now link to examples directly :D:D

Another thing to call out on my example - while you cannot switch the tuner on/off directly on the MIDI Captain in my latest version, the functionality is still active if you turn the tuner on from the kemper player buttons. So you get the note display and needle tuner in addition to what’s displayed directly on player. I thought that was a pretty cool (and unplanned/unexpected) bonus

I must say that the Mini 6 has turned out to be the perfect size companion to the Player IMO. While I originally wanted the 10 buttons on the STD version I also wanted to keep things small, and the reality is (at least for me) I rarely switch the post amp delay/verb effects mid song. I was glad to save to space and weight (although I realize that’s not everyone’s goal here).

One last thought for looper fans. I detected a slight delay in initiating loops when using Midi Captain, and after opening the unit up, I think there is a mechanical reason for this issue - the slack in the pedal buttons is about 5mm, so the “pressing action” on the button is not immediate / the button has to travel a bit before it actuates. I’m looking into a potential mechanical solution to this and will let you know what I come up with ;).

The separate page for looper functions is super convenient BTW if you haven’t tried it!

Best,

Dango

tunetown - Hi, I realized I needed to tweak the readme file describing the button layout in my latest update - any chance you can add this revised file to my example? THANKS!!!

Best,
Dango

ReadMe.txt

tunetown - also wondering, for long button holds, is there a way to optionally repeat the assigned function (e.g., if I do a long hold to switch banks and keep the button pushed for another half second, the pedal could cycle from bank 1, then to 2, then to 3, without having to do additional long pushes. Just a thought

Button combinations (e.g., pushing 1 and A simultaneously toavailable trigger the tuner, etc.) would also be a cool way to work with a limited set of buttons, if that functionality is not already availble.

Thanks!

Dango