new (4.1): external editors (midi/script)

[amiga909]

first: thanks, a very nice option

script editor:
tried with notepad++ and it works like a charm.
(now indicating in the trace window on which code line the interpreter stops, nice!!)


midi editor:
tried with domino:
http://homepage.ntlworld.com/eidenk/Tem ... nglish.zip (worth to check out!)
domino screenshot: http://stashbox.org/47705/Domino.jpg
but: domino refuses to draw any notes??

Q1: any help/comments for a good midi editor?
will try energy, temper, matryx (though they work non-standalone too)

Q2: not totally sure if the externalisation really is optimal but its nice to have of course
hope at least zoom will come one day (otherwise the finer quantizations make no sense because u cannot see em, IMHO)

[woodslanding]

do you have instructions for setting up the script editor? Or are they in the help file? I use notepad++ as well....

well, I've been too busy to install the beta, but now I have a chance--and a very good reason!

[senso]

After small tests it seems that http://www.widisoft.com/ works fine but cost 20$

setting the editor is very simple: just click and choose...

[bsork]

do you have instructions for setting up the script editor? Or are they in the help file? I use notepad++ as well....

well, I've been too busy to install the beta, but now I have a chance--and a very good reason!

Just click on the field and navigate to the EXE file. It should work even if you don't see a path and the program location isn't in your $PATH variable.

BTW, I'm using a 10-12 year old Windows version of Unix' VI text editor called Lemmy without any problems whatsoever. I've always wondered whether it's named after the Motörhead guy...

[Vincent]

do you have instructions for setting up the script editor?

I have the same question with NPP. It seems it's a wrong one. I'll try it.
What language to choose? Pascal?

rgds

[senso]

yes Pascal

[Vincent]

Thanks.

[woodslanding]

Okay, let me clarify my question--

More precisely: how do I compile? Things are opening great in NPP, but I select RUN and navigate to 'usine.exe', and nothing happens.

Is this not the right way?

[bsork]

If the script is loaded in a patch, just save the file from the editor, and the script should be compiled in Usine (almost) immediately. It's handy to have the trace window open to see what line numbers have errors etc.

[woodslanding]

oh, okay. That seems easy enough--but I would NEVER have thought of it!!

thanks!
-eric

[woodslanding]

well, it worked once, but I can't get it to work again. And I can't figure out a way to select 'no external editor'.

Is this possible?

well, back to v4 for now....

-e

[woodslanding]

ho ho, it's working now. NICE!

[woodslanding]

Hey, are the numbers in the console display supposed to be line numbers?? I'm getting numbers way past the last line in my file.

Is there an easy way to pinpoint the actual location of an error?

thanks,
-e

[bsork]

The line numbers are only shown for compilation errors as far as I can remember.

[woodslanding]

okay, I stopped using this feature a while back, and now I'm trying to get it to work again. I've re-read this a few times, but what ever made me say 'ho,ho, it's working' before is something I'm not doing now.

I wrote my draft in notepad, saved it to the usine library, opened it up in usine, double-clicked it, and it creates a temp file in notepad++. But saving the file does nothing. I can't get it to compile. I assume this is still working in V5??

help?

thanks,
-eric

[woodslanding]

oh, never mind. I just wasn't looking in the right place for the output....

[woodslanding]

Once again--it worked one time, and can't get it to happen again.....