if you have any questions about using Trax, or issues you find, please post there in this topic.
this is for use with both SSP and XMX versions of Trax, as they are basically the same.
(though please indicate which you are using)
Getting a black screen on XMX
Hi I followed the instructions in the zip file but I just get a black screen. I put the contents of the XMX plugins on the sd and the contents of the traxhost_xmx zip file onto the sd and renamed the SYNTHOR to SYNTHOR.ORIG and the install.sh to SYNTHOR
has anyone run into this and figured it out?
did you let it reboot, and wait a while?
are you using Mac or Windows?
one likely issue that could cause this is if, when you rename the files you end up with a file extension.
its v. important that install.sh is exactly SYNTHOR on the disk, and similarly SYNTHOR → SYNTHOR.ORIG. otherwise it will not work.
(and yeah, a black screen would be normal as its just not running anything)
can you show me a listing of the contents of the sd card after this has run.
I should be able to see what stage it got to from this.
I tested it 3 or 4 times before releasing, and followed along my instructions… so it should work 
I renamed the file exactly and I did it in windows. I’m remounting the synthor image file now in linux. I’m going to try and do it again. maybe i made a mistake. also i’ll do what you said and wait a while. Thanks for writing me TB
I wanted to say I got it to work. Thanks, I must of done something before.
1 Like
cool glad you got it to work !
it was likely the file renaming, thats the only thing that can really go wrong.
(esp. as on some OSs, it can start adding hidden file extensions)
as for ‘waiting a while’… its really only the time it takes the xmx to do a restart and then start synthor again. do I guess sub 30 seconds? (though might feel longer)
anyways, no matter, its good to know someone else has got it working and I hadn’t missed a step, or taken something for granted
enjoy
[SSP]
Is there any special procedure other than copying the plugins when using the plugins from [tbplugins ssp beta including trax]?
I copied the plugins folder to SD and tried the TRAX and Dual plugins, but when I press the Processor menu it reboots.
Other your plug-ins also reboot when I press the Processor menu.
no, identical to every other release Ive made… just copy into plugins.
odd, they (obviously) all work here… and I put the same copy that I released onto my SSP.
are you getting this with every TB plugin?
is this the latest version of SYNTHOR?
the only thing I can think of is perhaps our versions of SYNTHOR are different
given it only happens when you try to pull up the UI, its seems the module is loaded and running,
(you could test this by patching up PLTS and checking that audio is coming thru, if you dont bring up UI)
so makes me think, something do with when it tries to retrieve the UI.
but doesn’t explain why it runs fine with version of SYNTHOR.
hmmm…
The version of SYNTHOR is 13072202, so I believe it is the latest.
When I connect PLTS, I get sound, but when I go into the Processor menu, it reboots.
I have not tried all plugins, but all TB plugins I tried caused the reboot.
My plugins and older TB plugins work fine.
hmm, Im going to need to somehow get a copy of that version of SYNTHOR…
preferably without downloading the entire SDCARD image 
there must be a difference somehow in the build I have vs you…
but given the development I do, its hard to be certain, of which version of SYNTHOR is sitting on my SSP at present.
even then, still very odd, as Ive not made any changes to synthor for these plugins, so even if it was a different build, that should not really affect anything.
OK, I think Im going to have to ‘pull’ (remove) the SSP beta release.
indeed here it will crash with the released SYNTHOR, but not my build of synthor.
it seems the ‘old’ synthor thinks there is an invalid memory deallocate, but there is no way I can tell where/why - and because my build of synthor does not have the same issue, I cannot add code/debug to find out why it think this is the case.
also, ofc, its notable that SYNTHOR running on the XMX, using same code, similarly does not have an issue.
perhaps this points to a fix that was put into the synthor code after the release, which is now in my synthor ssp build, and also the xmx version!?
a lot has changed since my last plugin releases.
but the primary issue is, I cannot go backwards to test where/when the issue has started.
basically, the old version of JUCE I used for my release is no longer support using the build tools I have available (on Mac). so Im unable to even build the old versions now.
I tried a test build of the new plugins under Linux, and that fails in the same way, so its not a Mac build tools issue.
in fact, Ive tried numerous other builds and they all fail in the same way.
so Im at a bit of a loss…
its impractical for me to start undoing 1000s of changes to determine which particular one the old synthor build is objecting too… and I cannot build a debug version of synthor (that will fail) to determine where it has an issue
so… Im at a bit of an impasse for now…
1 Like
ok, Ive determined the cause… but I have no solution.
the released synthor has an issue using the newer version of JUCE within plugins.
I’ve no idea why…
It’s nothing to do with that changes Ive made to my plugins.
nor my build environment changes.
Ive verified this in two different ways:
a) rnbo.example.ssp
this has not been updated to my latest framework, so the code dates back to my last release.
if I only update this to latest juce (needed to compile), then this also fails.
b) ssp-sdk examples
qvca, does not use my framework at all, but uses juce
again, update to juce 8.0.4, it fails
api/test, which does not use juce.
works fine, thus proving my build environment is fine.
so… I now know it something to do with the released synthor loading plugins that use a latter version of juce.
I cannot debug synthor , since my build of synthor appears to work fine.
I cannot revert back to an older version of juce, as these are not compatible with macOS for building.
so yeah, I know what has introduced the issue - but cannot see a way forward.
the only thing we can do is beg @bert to come up with a new SYNTHOR version - and fix a few bugs or imperfections on the way
ok, Ive put up a new build, kind of a workaround - details coming
3 Likes