#268

I’m looking forward to get a Crow as soon as possible, but there’s a thing I can’t really figure out from what I found on the documentation: is it possible to create Max scripts and run them in standalone mode such as the LUA ones? I understand you have to format Max messages with a LUA syntax inside the tell_crow:" " paradigm, but I don’t get if by following such procedure I’d manage to load scripts that would run automatically when switching up the module without connecting it to the computer.

I apologize in advance if this has already been answered, I tried to read throughout each Crow-related thread but couldn’t find a clear answer. This is quite a crucial point for me as I create lots of processes in Max and would love to finally have a proper bridge between that and my modular system :slight_smile:

#269

not presently. to run a Max script, Max (or its runtime) needs to be running on the device. currently you can use Max to load a Lua script to crow, and you can use crow to communicate between a Max patch running on your computer and Eurorack, but crow cannot natively run a Max patch.

you could easily integrate crow into your Max patches, however! but a computer running Max is still a current requirement.

1 Like
#270

Thank you for your reply, I have now a clearer picture about how to integrate it into my setup!

Edit: not sure about this part though: is there a way to load a complete Lua script onto Crow by using Max?

#271

Yeah - you can use the following technique

tell_crow ^^startscript
tell_crow “<lua line 1>”
tell_crow “<lua line 2>”
.
.
.
tell_crow ^^endscript

If you want to load a file from disk via max, you will have to read the file into max and then pass the individual lines to crow using the same strategy as above.

You can also do multiline instead of line by line as well.

2 Likes
#272

Looks great, thanks a lot for the hint! :slight_smile:

#273

Not sure if this is the right place for this question, but will crow fit in a 4ms pod x?

1 Like
#274

it should! those are 51mm, yeah? crow is 41mm. I didn’t realize 4ms put out those deeper models, thanks for the tip. hope this helps!

#275

i got crow a couple weeks ago, but i’m just now trying it out for the first time!

first seems like a very intuitive, easy-to-use script, but it’s not working for me. no matter what voltage source i plug into input 1 to clock the sequencer, i can’t seem to get a regular response from the v/o and envelope outputs. several different voltage sources into input 1 (a steady EOR gate from maths, the LFO output from the same channel of maths, ansible TRs, CVs, and JF LFOs) don’t seem to get crow going. what am i doing wrong??

#276

Which firmware version are you on/did you upgrade the firmware to the current version?

1 Like
#277

it’s been a little bit but I think I had an issue too and when I updated crow it began working. sorry that’s all I have to offer for a tip

1 Like
#278

of course! i’m sure that’s it. thanks :pray:

1 Like
#279

I’m waiting for BPCMusic to send me some boards, but is there any progress on TXi integration? What needs to happen?

#280

If/when you have a TXi it would be great if you could help test the coming TXi support https://github.com/monome/crow/releases/tag/v1.0.2b0

2 Likes
#281

As noted, once I get the boards from BPC to build one, I will very ready for it!

#282

Just curious what the ballpark timeline is on adding 16n functionality to Crow is looking like? Thanks as always for the ongoing development!

#283

Is it, or will it, be possible for a Norns script to send/receive CV to/from crow in addition to ii? Like at the same time?

#284

@iiii I have this already written, just need to post a beta firmware with it so someone can test (I don’t have one) - Will get it into the next beta (~1-2 weeks away).

@TanSaturn This is already possible if I’m understanding your question correctly. You can send & receive CV at the same time as sending & receiving ii. If you have a more specific question I’ll try and answer.

2 Likes
#285

That is the answer I was looking for. Thank you!

#286

There were some early issues with sending Crow too much at once that I believe have been addressed. Recently I think I read somewhere here (can’t find it now) that Crow is now fine with receiving up to 16 lines at once. Can it be confirmed that as long as I keep it under 16 lines of code, other size considerations (within reason, I suppose) are not a factor? That is, I can send long-ass lines of code, as long as it’s no more that 16 lines at a time, or is it more complicated than that?

#287

Your functions can have as many lines as you like. The limit for sending code to crow is 8k characters!

The 16 number is just the ii command buffersize. If people start seeing dropped ii commands, please post the script and I’ll see if I can help get it working.