No products in the cart.
Any ideas on why?
Happened recently, has been working fine ever since I reinstalled after a drive failure.
The other kits loads just fine (Pop/Rock, Coctail, Vintage Rock)
Tried updating it with the latest version from your page (which I am fairly certain I did after first installing) – made no difference.
Should I reinstall Nashville?
Wossname - using an: Amd Phenom XIII 2.8/4Gb DDR2/3x500SATA/Windows 7-64
Hi,
please fill in your system specifications in your profile and/or signature.
BR,
John
John Rammelt - Toontrack
Technical Advisor
As they haven’t changed I can’t quite see why, but here they are:
-AMD Phenom II X3, 2.8ghz
-4Gb DDR2 memory
-500Gb SATA for OS & Misc
-500GB SATA for Apps & Data
-ATI Radeon HD4870X2 gfx
-Running Windows XP SP3
-M-Audio USB Micro soundcard.
Wossname - using an: Amd Phenom XIII 2.8/4Gb DDR2/3x500SATA/Windows 7-64
Is this happening in Toontrack Solo as well as your sequencer?
A reinstall of Nashville wouldn’t be a time consuming effort and it would be my first choice of things to do. Also, check for updates to the Nashville EZX.
Dave Modisette www.gatortraks.com www.plasticsamerica.com http://www.gatortraks.com/forum
Just to add to Dave: Perform an uninstall of Nashville, perform a disk check, defragment (optional) and reinstall
Intel i7 5820K - ASRock X99 Extreme4/3.1 - NVidia GTX660 - 64Gb Vengeance DDR4-2133 RAM - RME Fireface 400 - 64-1024 - 48KHz - Fractal Audio Axe Fx III - Windows 10 Pro 64-bits - Cubase 10 Pro - http://www.harrymaes.com
Ok,
-moved off the EZX_Nashville to temp (in case there were corrupt files in there, the reinstall would not happen to reside on the same blocks)
-Checked disk for errors (there were none)
-Defragmented
-Uninstalled
-Reinstalled
-Stopped loading at 71mb
-Ran the Nashville updater
-Stopped loading at 72mb.
Same behaviour in Ableton Live as in Toontrack Solo.
This is very annoying, as I’m mixing down ~30 tracks right now for a gig on saturday, many of which uses Nashville.
Wossname - using an: Amd Phenom XIII 2.8/4Gb DDR2/3x500SATA/Windows 7-64
I’ve tried copying the EZX_Nashville folder off to another location to see if Windows complained about broken files. All good.
The folder itself is:
Size: 957MB (1 004 495 212 bytes) big.
Size on disk: 976 (1 024 315 392 bytes)
Contains 9668 Files, 11 Folders
Wossname - using an: Amd Phenom XIII 2.8/4Gb DDR2/3x500SATA/Windows 7-64
Which host are you using?
Could you try downloading another host (like Reaper) and see if it loads in there?
It might be memory related (maxed), do you use the /3G switch?
If the files are not broken something else must have changed between the working and the current situation.
Intel i7 5820K - ASRock X99 Extreme4/3.1 - NVidia GTX660 - 64Gb Vengeance DDR4-2133 RAM - RME Fireface 400 - 64-1024 - 48KHz - Fractal Audio Axe Fx III - Windows 10 Pro 64-bits - Cubase 10 Pro - http://www.harrymaes.com
Just wondering if it could be some sort of bit depth conversion issue. Could you try it in your host at a 16 bit bit depth and see if that solves it? Also, does the problem manifest using different kit pieces? IOW, change the snare and see if that helps. Also if you haven’t tried it, resist the temptation to trigger the kit pieces while the kit is loading and see if that changes anything.
Dave Modisette www.gatortraks.com www.plasticsamerica.com http://www.gatortraks.com/forum
Have you tried going through the default kit that loads up, setting all the drum types to “none” and then back to something else and see if they load normal…. not that this is the way you want to work… but it may reset something in Nashville….
Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)
Using Pro Tools M-Powered, Ableton Live, Reaper, Tracktion, Toontrack Solo. it ain’t the host 🙂
Wossname - using an: Amd Phenom XIII 2.8/4Gb DDR2/3x500SATA/Windows 7-64
ORIGINAL: bradch00
Have you tried going through the default kit that loads up, setting all the drum types to “none” and then back to something else and see if they load normal…. not that this is the way you want to work… but it may reset something in Nashville….
I’ll do that, and also look into bit-conversion type problems.
Thanks,
Wossname - using an: Amd Phenom XIII 2.8/4Gb DDR2/3x500SATA/Windows 7-64
Bit depth is highly unlikely to cause any problems.
Any Anti-Virus program at the same time?
Which version number is reported for the Nashville EZX in the Help menu?
BR,
John
John Rammelt - Toontrack
Technical Advisor
ORIGINAL: John
Bit depth is highly unlikely to cause any problems.
Any Anti-Virus program at the same time?
Which version number is reported for the Nashville EZX in the Help menu?
Nashville 1.1.3 it says.
Changing bit depth (to 16) and bitrate (to 48) didn’t help.
No antivirus installed on my studio computer, but I occasionally run MCAfee Security Scan.
Wossname - using an: Amd Phenom XIII 2.8/4Gb DDR2/3x500SATA/Windows 7-64
ORIGINAL: Dave Modisette
Just wondering if it could be some sort of bit depth conversion issue. Could you try it in your host at a 16 bit bit depth and see if that solves it? Also, does the problem manifest using different kit pieces? IOW, change the snare and see if that helps. Also if you haven’t tried it, resist the temptation to trigger the kit pieces while the kit is loading and see if that changes anything.
Tried that, didn’t help.
Thanks for the tip anyways 🙂
in summary: Nashville loads, up to ca 72mb. Ie: All kit pieces EXCEPT toms! (and possibly less layers on the others, but atleast they make a sound)
Wossname - using an: Amd Phenom XIII 2.8/4Gb DDR2/3x500SATA/Windows 7-64
No products in the cart.