Synology DS1522+ Btrfs RAID5 Volume (operating system updated too latest) Connected to local network on-site with both computers all using static ip’s assigned from Comcast Business Class Router/Modem
MAC OS Ventura
Windows 10 (operating system updated too latest)
Current setup at local bar/nightclub
MAC Laptop/Windows machine/NAS all connected on same local network with static ip’s. Mac laptop is used as primary machine, windows is used as backup and for shift change on a 4-channel dual USB Pioneer mixer. Both Mac & PC are using same version of VDJ and signed-in as Pro license with same account. This setup works great aside from both machines recusing after reboots or cold starts and new VDJ sessions
1st issue: On both Mac and windows machines connected to local network NAS shared folder(s) are seen in VDJ, stream fine from local network, Add to Database & Recurse, however after shutting down cold both the MAC & PC and running a new session Recursing runs every time. I have set both*rememberRecurse* to (NO) and *autoSearchDB* also to (NO) with zero luck.
2nd issue I have is with windows drive mapping feature. After drive map is created and seen in VDJ as local drive, the drive disappears after reboot or cold start of machine in VDJ and file explorer. Should I create a mapped drive/folder on both MAC & PC with same drive letter so both machines can sync databases during a new session in VDJ?
MAC OS Ventura
Windows 10 (operating system updated too latest)
Current setup at local bar/nightclub
MAC Laptop/Windows machine/NAS all connected on same local network with static ip’s. Mac laptop is used as primary machine, windows is used as backup and for shift change on a 4-channel dual USB Pioneer mixer. Both Mac & PC are using same version of VDJ and signed-in as Pro license with same account. This setup works great aside from both machines recusing after reboots or cold starts and new VDJ sessions
1st issue: On both Mac and windows machines connected to local network NAS shared folder(s) are seen in VDJ, stream fine from local network, Add to Database & Recurse, however after shutting down cold both the MAC & PC and running a new session Recursing runs every time. I have set both*rememberRecurse* to (NO) and *autoSearchDB* also to (NO) with zero luck.
2nd issue I have is with windows drive mapping feature. After drive map is created and seen in VDJ as local drive, the drive disappears after reboot or cold start of machine in VDJ and file explorer. Should I create a mapped drive/folder on both MAC & PC with same drive letter so both machines can sync databases during a new session in VDJ?
Posted Sat 30 Dec 23 @ 3:57 pm
Bump>
Posted Tue 16 Jan 24 @ 3:39 pm
First you need to resolve the 2nd issue.
If you map a drive on Windows and then later the drive dissapears or fails to connect, then it's an issue that could be caused by several reasons and would have a big impact on VirtualDJ.
You see, VirtualDJ relies on OS (MAC OS or Windows) for file operations. If the OS can't see a drive or a network filepath, then VirtualDJ can't either.
The drive issue on Windows deserves a troubleshooting guide of it's own.
It could be due to the protocol used to create the connection, it could be due to security related settings, it could be due to computer's local GPO, or finally even a setting on the NAS itself.
So, as a first step I would Google around how to solve the problem for the mapped drive dissapearing.
Then I would go to troubleshoot the first issue. Obviously if you have rememberRecurse and autoSearchDb set to off, VirtualDJ should not recurse the network drive. And I don't think it does actually. However, VirtualDJ DOES remember the last folder you browsed. And when you start it and it visits a folder, even if autoSearchDb is set to OFF, it needs to read the tags of the files on that folder.
So, depending on the size of the file, the network connection e.t.c. it may seem like it's recursing when it's not ?
Your problem description doesn't make sense (to us). So you need to describe better what's happening so that we can understand and help.
However, there's no real gain to do so unless you fix the "2nd" (drive dissapearing) issue first.
PS: Windows have drive letters, but MAC OS does not. So it's impossible to set them both to "use the drive with the same letter"
If you map a drive on Windows and then later the drive dissapears or fails to connect, then it's an issue that could be caused by several reasons and would have a big impact on VirtualDJ.
You see, VirtualDJ relies on OS (MAC OS or Windows) for file operations. If the OS can't see a drive or a network filepath, then VirtualDJ can't either.
The drive issue on Windows deserves a troubleshooting guide of it's own.
It could be due to the protocol used to create the connection, it could be due to security related settings, it could be due to computer's local GPO, or finally even a setting on the NAS itself.
So, as a first step I would Google around how to solve the problem for the mapped drive dissapearing.
Then I would go to troubleshoot the first issue. Obviously if you have rememberRecurse and autoSearchDb set to off, VirtualDJ should not recurse the network drive. And I don't think it does actually. However, VirtualDJ DOES remember the last folder you browsed. And when you start it and it visits a folder, even if autoSearchDb is set to OFF, it needs to read the tags of the files on that folder.
So, depending on the size of the file, the network connection e.t.c. it may seem like it's recursing when it's not ?
Your problem description doesn't make sense (to us). So you need to describe better what's happening so that we can understand and help.
However, there's no real gain to do so unless you fix the "2nd" (drive dissapearing) issue first.
PS: Windows have drive letters, but MAC OS does not. So it's impossible to set them both to "use the drive with the same letter"
Posted Wed 17 Jan 24 @ 7:33 am
On your Windows machine try adding this to a batch file that runs on startup:
This is what I use & it just works (for me)
It will ping the NAS & will display the error if it doesn't respond.
If it does it maps the network drive.
nb. The drive is disconnected when you log off
ping -n 1 -w 100 [IP address of NAS] | find "TTL=" >nul
if %errorlevel%==0 goto 1
echo "NAS offline"
exit
:1
if not exist [Network drive letter] (net use [Path on NAS including drive letter] /p:No)
exit
This is what I use & it just works (for me)
It will ping the NAS & will display the error if it doesn't respond.
If it does it maps the network drive.
nb. The drive is disconnected when you log off
Posted Wed 17 Jan 24 @ 12:27 pm