BUG: Engine Lightning not recognizing Autoscripted Tracks with Engine OS 4.2.0

Hello everyone,

this one took a while to pin it down, but now i managed to get the reproduction steps done:

When you have autoscripted tracks and everything is correctly synced to an SD Card, the autoscript is not working for many, but for some tracks. So i searched further, rescripted all tracks and had the same issue.

After days of testing i found the following behavior in my Prime 4+ Unit:

Test #1

  1. Boot up
  2. Load 2 Tracks
  3. Start Engine Lightning
  4. Scripts are recognized and working for the previus loaded tracks

Test #2

  1. Boot up
  2. Start Engine Lightning
  3. Load the same Tracks as in Test 1
  4. Scripts are NOT recognized and auto loops are used

Test #3

  1. Boot up
  2. Load first track of Test #1
  3. Start Engine Lightning
  4. Load Second Track of Test #1
  5. Result: First Tracks autoscript is working, second one not

So iam pretty sure that there is a bug in the track loading functionality in Engine OS 4.2.1

EDIT: Engine OS: 4.2.0 Engine Desktop: 4.2.1 Soundswitch: 2.9.1.0 Control One: Firmware 1.18

Greetings,

André

I have the same issue. Just so you dont feel alone :slightly_smiling_face:

Same problem here!

@Glandragor @Engell @DjEric hope you are all doing well.

I just had a look at this issue following the test steps you provided and was unable to reproduce this issue.

I just want to double-check that you do not have the “Override Scripted Tracks” option enabled? This can be enabled on the Autoloops page or in the Engine Lighting preferences.

I have ensured that this is not enabled on my machine and have then tried the method provided restarting the device and loading scripted tracks which all playback correctly for me.

If this can be reproduced easily a short video of this would be great.

Hi Liam,

the Option ist disabled. And i have the Same issue with reproducable steps on a Prime 4+ and in an older Prime 4 Unit.

What i could find Out in the Meantime is, that a soundswitch Project from an older soundswitch Version seems to Work Just fine.

Maybe some Export issue in the 2.9er Versions?

Greetings,

Andre

Ok and a little information how are you exporting your SoundSwitch Project to your USB Drive? Are you using the Engine DJ Method?

If you take the source drive you use with your device and you connect this to your computer running SoundSwitch you can open the SoundSwitch Project that is located on this drive as well as the audio file can you verify this is correctly scripted?

Same problem here, just prepared for a gig and see all new auto scripts not working :frowning: Looks to me like any new scripted track (since 4.2.0/2.9 update?) is not recognized anymore. Older ones work for me. Tried exporting via engine and soundswitch and both ways it doesn’t work.

I also loaded the project from the export medium and checked that the scripted track is there in soundswitch software.

Ok, can you please provide a little more info about the exact version of both SoundSwitch and Engine you are using.

Can you also confirm whether you are using a MacOS or Windows machine?

I have confirmed all versions are working correctly on my devices so if you can provide me with as much info as possible I can get closer to your environments to confirm.

Sure. Hope we can tackle this. I’m on pretty new versions: MacOS Sequoia 15.3, Engine Dj Desktop: 4.2.1, Prime 4+ with Engine OS 4.2.0, SoundSwitch Software: 2.9.1.0-63c8b278.

I’m using Soundswitch since 2.5 years and autoscripted songs roughly from last year until November (I can actually check more precisely) seem to work. Note that I used PrimeGo until then. Currently I assume that songs autoscripted after upgrade from SoundSwitch 2.8.x to 2.9 are not detected anymore as autoscripted.

You can DM me directly if you need more information. I think I could also take a video or provide more details.

Ok perfect my environment is identical to this.

I just want to verify a few things first.

Have you tried opening the SoundSwitch Project that is located on your external drive and confirmed if the files are scripted when opening these in Edit Mode?

When in Engine Lighting you have confirmed that the “Override Scripted Tracks” preference is not enabled.

Lastly how are you verifying that a scripted track is not playing back can you see an Autoloop playing on the autoloop page?

A video would be great if possible.

When in Engine Lighting you have confirmed that the “Override Scripted Tracks” preference is not enabled.

Correct, it is disabled.

Lastly how are you verifying that a scripted track is not playing back can you see an Autoloop playing on the autoloop page?

Yes, I see an Autoloop playing instead. And vice versa, when one of the working, older, autoscripted track is playing I don’t see an auto loop running. Yesterday I had also my lights connected and could see it visually.

Have you tried opening the SoundSwitch Project that is located on your external drive and confirmed if the files are scripted when opening these in Edit Mode?

Here I am a bit confused: I opened the exported project on SD-card. Now in SoundSwitch Edit Mode in the browser tree I have 2 entries under “Engine DJ”: “Collection” and “My SD Card”. Is “Collection” now still my local collection on the harddisk? Under “Collection” I see all scripted tracks as expected, the ones that work and also the ones that don’t work. On “My SD Card” there’s completely no scripted track. However I definitely played yesterday from this SD-card with scripts working for the older tracks.

Ok yes you want to open the Project located on the SD Card. Now if you are looking at the “SS” icon and this is not present in Edit Mode this could be a result of opening different projects and to resolve this navigate to the “Options” menu and hit the “Rebuild TrackMap” option that will now re-scan the library for the script tracks and present the icon again.

I see, ok. After rebuild TrackMap indeed the icon appears at the older songs on the SD card. But not at the newer autoscripted ones. They are autoscripted in the “Engine DJ” collection on harddisk but not on SD card.

I guess this may at least mean Engine OS on the player didn’t do something wrong… But why the new autoscripts weren’t exported? I just double checked the export option in Engine Desktop SW. “Export via Sync Manager” is active. And just to be 110% sure I exported once again via Sync Manager, but the new songs keep to be unscripted.

Ok so this confirms that your new Autoscripts have not been exported. Can you confirm that in the Engine DJ Desktop preferences you have the correct SoundSwitch Project selected to export?

Yes, correct project is selected. And the newly autoscripted, but not working tracks, are also marked with a dot in the SoundSwitch-column in Engine Desktops Track Browser.

Ok can you please provide me a video of this issue you will need to show that the track is scripted in SoundSwitch. The more info or screenshots you can provide the better.

Ok, I’ve send you a video link via message. Let me know if its understandable.