MacGyverGear
Just to be sure about the clean project folder, I did the same procedure again.
Created a new Project folder. With the database added I can start SoundSwitch without any problem over and over again without closing.
Next step: Copiep the Venue file (Where all settings like: Midi, DMX, Static Settings, Positons, Attribute cues.. and so on are set). Re opening the project folder will result in closing down..
Next step: Cleared all midi settings for this venue. Close down the program manually and re opened it; and I finally I was able to just use SoundSwitch. Did the close down / re open procedure three times more and all went well again.
Pretty sure the midi settings where kind of messing up things here, but it's weird, excluding the database kind of solved things for my settings in this specific Venue file.
I now will try to do the same on the laptop I use for gigs, and adress the Streamdeck again. Perhaps there where some previous midi learn adresses specified, but those aren't accesable, and so SoundSwitch will close down. I've worked a lot with midi controllers and never got any problems with it. In my recent setup I've added a Numark DJ2GO which is an additonal controller for my touchscreen (like to have physical buttons). I always have to start Virtual DJ first. When starting SoundSwitch first, Virtual DJ can't acces the Numark DJ2GO. So perhaps it send out midi informations while I was learning my Streamdeck? Don't know..
Will now turn over to my gig laptop to continue the experiment.
Created a new Project folder. With the database added I can start SoundSwitch without any problem over and over again without closing.
Next step: Copiep the Venue file (Where all settings like: Midi, DMX, Static Settings, Positons, Attribute cues.. and so on are set). Re opening the project folder will result in closing down..
Next step: Cleared all midi settings for this venue. Close down the program manually and re opened it; and I finally I was able to just use SoundSwitch. Did the close down / re open procedure three times more and all went well again.
Pretty sure the midi settings where kind of messing up things here, but it's weird, excluding the database kind of solved things for my settings in this specific Venue file.
I now will try to do the same on the laptop I use for gigs, and adress the Streamdeck again. Perhaps there where some previous midi learn adresses specified, but those aren't accesable, and so SoundSwitch will close down. I've worked a lot with midi controllers and never got any problems with it. In my recent setup I've added a Numark DJ2GO which is an additonal controller for my touchscreen (like to have physical buttons). I always have to start Virtual DJ first. When starting SoundSwitch first, Virtual DJ can't acces the Numark DJ2GO. So perhaps it send out midi informations while I was learning my Streamdeck? Don't know..
Will now turn over to my gig laptop to continue the experiment.
geposted Fri 01 Nov 24 @ 10:55 am
MacGyverGear
Just did the same in my Gig laptop. Clear mid settings in SoundSwitch. Same problem when accessing the database. SoundSwitch just closes down.
And, where as my empty project folder with a copied venue in my clean install laptop without the virtual Midi Cable, Streamdeck app, and midi settings for the venue cleared seemed to run fine, now it is also closing down now. :-(
Back to the startingpoint.. I'm a bit lost.
I sent over my Virtual DJ database to SoundSwitch and could not find any issues with it.
I'm a bit lost.
The only knowledge I have now is that an empty venue (now DMX adresses for fixtures, posistions and stuff) will SoundSwitch acces the Database without closing down.
I also noticed, when the red spot is not lit (indicating SoundSwitch is reading the Database), and selecting performance mode, so just have a little patience, SoundSwitch will continue to work most of the time. But then those random crashes that bugged me the last gigs still are a problem.
And, where as my empty project folder with a copied venue in my clean install laptop without the virtual Midi Cable, Streamdeck app, and midi settings for the venue cleared seemed to run fine, now it is also closing down now. :-(
Back to the startingpoint.. I'm a bit lost.
I sent over my Virtual DJ database to SoundSwitch and could not find any issues with it.
I'm a bit lost.
The only knowledge I have now is that an empty venue (now DMX adresses for fixtures, posistions and stuff) will SoundSwitch acces the Database without closing down.
I also noticed, when the red spot is not lit (indicating SoundSwitch is reading the Database), and selecting performance mode, so just have a little patience, SoundSwitch will continue to work most of the time. But then those random crashes that bugged me the last gigs still are a problem.
geposted Fri 01 Nov 24 @ 11:48 am
DJ VinylTouch
Thank you for providing all of that info. So it does seem like the unexpected behavior is coming from the SoundSwitch side. MIDI controllers being accessible by a single client at a time is probably normal for the controllers you mentioned, and I guess you are using Virtual MIDI cable solution to overcome that.
I also would have looked to the Virtual MIDI setup first for the problems but you said you had issues even without it.
I personally always wait for the library to be loaded before doing anything in SoundSwitch, and I also go to Performance mode to test everything else out without issues (that's probably noy helpful to you though).
I think at this point it sounds like a SoundSwitch tech support problem. Maybe if possible you can provide them with a core dump when the issue occurs?
I also would have looked to the Virtual MIDI setup first for the problems but you said you had issues even without it.
I personally always wait for the library to be loaded before doing anything in SoundSwitch, and I also go to Performance mode to test everything else out without issues (that's probably noy helpful to you though).
I think at this point it sounds like a SoundSwitch tech support problem. Maybe if possible you can provide them with a core dump when the issue occurs?
geposted Fri 01 Nov 24 @ 12:26 pm
MacGyverGear
DJ VinylTouch wrote :
Thank you for providing all of that info. So it does seem like the unexpected behavior is coming from the SoundSwitch side. MIDI controllers being accessible by a single client at a time is probably normal for the controllers you mentioned, and I guess you are using Virtual MIDI cable solution to overcome that.
I also would have looked to the Virtual MIDI setup first for the problems but you said you had issues even without it.
I personally always wait for the library to be loaded before doing anything in SoundSwitch, and I also go to Performance mode to test everything else out without issues (that's probably noy helpful to you though).
I think at this point it sounds like a SoundSwitch tech support problem. Maybe if possible you can provide them with a core dump when the issue occurs?
I also would have looked to the Virtual MIDI setup first for the problems but you said you had issues even without it.
I personally always wait for the library to be loaded before doing anything in SoundSwitch, and I also go to Performance mode to test everything else out without issues (that's probably noy helpful to you though).
I think at this point it sounds like a SoundSwitch tech support problem. Maybe if possible you can provide them with a core dump when the issue occurs?
Thank you for the information. How do I capture a coredump?
I did not have any response from SoundSwitch, after I provided them the information, SoundSwitch continues working for at least an hour by not accessing the Database. They also asked if the problem persists when I switch the software setting to Serato, as it is not scanning the Virtual DJ database then I think.
Things work great as long as I won't be asking to much of my computer. Things like streaming or setting up an internet connection can close down SoundSwitch. It's just like, if there's too many tasks, the programm acts buggy in Windows. Even when there's lots of CPU overhead.
geposted Fri 01 Nov 24 @ 12:52 pm
MacGyverGear
I sent over my New created Project folder to SoundSwitch support. The one with the exchanged Venue that is causing the problems on any computer . Hopefully they'll come up with a solution on this.
geposted Fri 01 Nov 24 @ 4:02 pm
DJ VinylTouch
You could prob capture a coredump with a user space tool like userdump (I'm not really a Windows user). I think SoundSwitch devs would guide you much better than we can at this point though.
geposted Fri 01 Nov 24 @ 6:49 pm
MacGyverGear
oh.. thanks for the explanation. I will wait for what SoundSwitch will tell and provide them whatever they need. I really want to start using Soundswitch again if we can sort things out.
geposted Fri 01 Nov 24 @ 8:26 pm
DrivingCapEntertainment
Hi guys. I'm relatively new to SoundSwitch and just starting to set it up (bought the perpetual license for 50% off on Black Friday). I am using Virtual DJ 2024 and Soundswitch 2.9.1. I have been struggling to get SoundSwitch to see my files from Virtual DJ at all. Anyway, I know this thread is a month old, but hopefully we can provide some mutual help. Thanks for the useful info.
geposted 2 days ago @ 4:25 am
locoDog
@DrivingCapEntertainment I can't help with your problem, but a couple of months down the line, if you get into lamping individual tracks or want to call soundswitch without SS dedicated hardware, I made a thing that does it all inside vdj.
256 nameable commands, upto 1024 events [action cues] per track. os2l or midi.
256 nameable commands, upto 1024 events [action cues] per track. os2l or midi.
geposted 2 days ago @ 5:03 am
DJ VinylTouch
With respect to library visibility with SoundSwitch, I've always found it missed a lot of my filter folders in my collection (it might be that list has to be generated from the condition of the filter). However I found it read the entire collection and regular playlists (now just lists) ok. Also, maybe you can set browserShowLegacyM3UPlaylists to yes and disabling Hotplug for that list to see if that helps as well.
You might want to just drag all of the filea you want to script into a Virtual Folder and then open SoundSwitch and see if that works (that's the workflow I use).
You might want to just drag all of the filea you want to script into a Virtual Folder and then open SoundSwitch and see if that works (that's the workflow I use).
geposted yesterday @ 2:46 pm
DJ VinylTouch
An addition to this - if you are updating on MacOS from a fairly old version of VirtualDJ to a recent one, it may be that your older version was using an App folder location that has been deprecated (call this the old location = ~/Documents/VirtualDJ). VirtualDJ now uses ~/Application Support/VirtualDJ for that data (call this the new location). It think it does reference the old data location if it's found, but off the top of my head, I'm not sure what it does for new information (if it still writes to the old, or writes to the new and maintains looking at both - devs would know more here).
To ensure SoundSwitch isn't missing anything, you'll probably want to merge the contents of the old location into the new location, backup, then completely delete the old location, and point SoundSwitch to the new location.
To ensure SoundSwitch isn't missing anything, you'll probably want to merge the contents of the old location into the new location, backup, then completely delete the old location, and point SoundSwitch to the new location.
geposted yesterday @ 6:54 pm