Jan M

Before exporting to the RaspPi target there could be a version match between the target version and the RNBO package implemented and give a warning if there's a mismatch.

Currently it just says: there's a newer version go the target available.

Here's a concrete situation where it would have help me:

I was working on a location without internet and tried to export an updated version of my RNBO patch. The compilation failed because of the version mismatch and I couldn't continue to work, and had to find a place where I could connect the RasPi to the internet.

Another possibility would be to rollback the target when compilation fails - which is probably much more complex to implement. Just a warning that compilation might fail would be sufficient I think.

And thanks again for this wonderful tool! It doesn't happen to me often that just days after encountering something new it already has a permanent place in my workflow!!!!

In case someone from C74 reads this: 

Before exporting to the RaspPi target there could be a version match between the target version and the RNBO package implemented and give a warning if there's a mismatch. 

I was working on a location without internet and tried to export an updated version of my RNBO patch. The compilation failed because of the version mismatch and I couldn't continue to work, and had to find a place where I could connect the RasPi to the internet. 

In case someone from C74 reads this: 

Before exporting to the RaspPi target there could be a version match between the target version and ... 

suggestion-to-improve-rnboraspberry-pi-workflow-cycling74-team

This is a great idea, maybe a popup after you click the export button if there is a mismatch, basically says "there is a mismatch, the build might fail, are you sure you want to continue?" or something like that?

There are cases where the build could succeed, so being able to force it makes sense. Right now RNBO moves too fast to properly adhere to SemVer but I hope that happens eventually.

Either way, I'll add a feature request ticket for this, also, rolling back.. I believe I have a more general approach in the works.

Hey JAN,

This is a great idea, maybe a popup after you click the export button if there is a mismatch, basically says "there is a mismatch, the build might fail, are you sure you want to continue?" or something like that?
There are cases where the build could succeed, so being able to force it makes sense. Right now RNBO moves too fast to properly adhere to SemVer but I hope that happens eventually.

Either way, I'll add a feature request ticket for this, also, rolling back.. I believe I have a more general approach in the works.


Glad you like the idea, Alex! As many of us are artists and we might try to do some last minute changes onsite, that would helps to avoid critical situations.

Glad you like the idea, Alex! As many of us are artists and we might try to do some last minute changes onsite, that would helps to avoid critical situations.
Thanks for ticketing it.

Suggestion to improve RNBO/Raspberry Pi workflow (@Cycling74 Team)