Ableton Forum

I wasn't thinking of a preview as in, actual usage, but more of a 'predrawn representation'of each mode.

So it steals the Push, it doesn't function as Push, but you get to see a snapshot of different modes. The. A person would scroll through the color options for each parameter. At any time, a person could create a txt that gives the info.

I'm not asking anyone to make it. I'm just wondering how realistic it sounds as a future possibility. And if it seems like a good method for users to make their own color combinations.

In other news, your device sounds like even more fun. Pad paint! I'll try it after I eat something.

I see exactly what you mean, but it looks to me that M4L isn't the way to go for such a feature. I can't exclude it, but I would be surprised if we could access the color variables through M4L. If we can't access the colors one would have to define the pad layout for each Push mode in M4L, which is doable, but imo no fun at all.

As far as I can see python would be the much better road to take for this task. And I guess it's realistic to assume we will see some (even official) development in this direction one day (the colors are defined in a file called SkinDefault.py, why would you call a file like this if you're not planing to add cumstom skins one day?).

I downloaded the file "Push Script Mods v1.1.1" from here http://beatwise.proboards.com/thread/1281 and copied over the unzipped folder in to my Midi Remote Scripts folder however now when I load up Ableton, Push doesn't start up at all and even after moving the Push Scripts Mods folder back out of the Midi Remote Scripts folder, it's still not working Can anyone advise what I'm doing wrong? I only picked my Push up last night and now it's not working at all now unless I go in to a Beta version of Live.

Any help appreciated.

Anyone able to assist? I've managed to get Push working again, for some reason it had removed 'Push' as a control surface in the drop down within preferences so it's back working now I've selected it.

I would still like to know what I'm doing wrong with regards to the Push Scripts Mods v.1.1.1 folder to allow me to use the Seapush skin?

Many thanks in advance.

stevoEOS wrote:... and copied over the unzipped folder in to my Midi Remote Scripts folder

Maybe this: don't copy the folder, but only the *.py files within the folder. The *.py files have to end up in the same folder where the *.pyc files are, namely: ...\MIDI Remote Scripts\Push

Thanks a lot for the response, will try that tonight when I get home from work and report back.

Cheers

hey folks, sorry for disappearing without warning. i've been in total seclusion in the woods for 2.5 months (no human contact, no internet, no electricity) to write and meditate. and in the whirlwind of preparing for this trip i got negligent about the seapush mod.

before i left i was trying to get seapush to work with the live 9.1 beta, but the script mod basically made the melodic step sequencer mode unusable for reasons i didn't know enough about to debug.

my push is still in a storage unit in NYC and i won't be returning there till april, so i can't test myself, but do i understand correctly from this thread that someone else figured out how to fix the DefaultSkin.py mod so that it doesn't ruin the note sequencer interface? i'd love to know how this was done.

once i get back to my push in april i'll fix my github page. for now i'll just add a warning...

Unless I missed something, it looks like it works fine. Just tested it, getting the new colors in the sequencer and everything appears to function as you'd expect.

Hi does anyone have a copy of the original scripts as I saved mine when I installed the sea push colour scheme then updated to latest remote scripts from here but I wanted to revert to the original scheme but when installed the old scripts push is no longer working , it just says please start live and when I start live nothing happens.

Anybody know what file contains an individual preset for a VSTi control mapping? Just curious about the possibility of hacking the bank names in a VSTi control mapping.

-

TomViolenz wrote:

Airyck wrote:Anybody know what file contains an individual preset for a VSTi control mapping? Just curious about the possibility of hacking the bank names in a VSTi control mapping.

I have not the slightest idea. But it should be with the rack presets I would assume. I doubt that these files are in an easily accesible language like Phyton though. And even if you get to edit the file, it's not certain that there is a ready made template for bank names. It could be made in a generic fashion. Like: Up to 8 paramers, return Bank(x); up to 16; return Bank(x) and Bank(x+1) and so on. Which means you would have to program a way to actually give your banks meaningfull names. I would leave that to Ableton to be honest

I see, thanks for the insight. Just thought I'd see if it was possible but the more I thought about it the more I thought it would probably require writing some code rather than editing whats there. It seems you've confirmed that as a very likely possibility.

After the 9.1.1 Update it doesn't work anymore Any ideas?

Bimmlu wrote:After the 9.1.1 Update it doesn't work anymore Any ideas?

Could you be more specific as to what "it" is?

drez wrote:

Bimmlu wrote:After the 9.1.1 Update it doesn't work anymore Any ideas?

Could you be more specific as to what "it" is?

The Seapush Mod for Push.