Error having a too long path (+260 characters).

XXHighEnd - The Ultra HighEnd Audio Player

November 24, 2024, 12:55:06 pm

Welcome, Guest. Please login or register.
Did you miss your activation email?

News: August 6, 2017 : Phasure Webshop open ! Go to the Shop

Home

Help

XXHighEnd > Ultimate Audio Playback > XXHighEnd Support > Error having a too long path (+260 characters).

Pages: [1]

« previous next »

	Author	Topic: Error having a too long path (+260 characters). (Read 7745 times)
0 Members and 4 Guests are viewing this topic.

BertD

Audio Enthusiast

Offline

Posts: 422

Only the Best!

Error having a too long path (+260 characters).

« on: February 20, 2015, 07:22:04 pm »

This stalls the extraction of making Galleries and the whole selection has to be done all over again. Somehow it does not recognise previous extracted directories making things even more time consuming. unhappy


	Logged

Februari 1st: RDC controlled i7-4785T (set to 800Mhz - fully passive design without any moving parts), 16GB RAM / XXHighEnd 2.04c on 2GB RAMDisk (IMDisk) / Windows 10 Pro 10586.0 X64 on internal 250GB SSD / Music on external NAS / Playback Drive 10GB RAMDisk (IMDisk) / SFS 0.10 / Barbone Industrial Intona > Phasure NOS1a 75B (BNC Out) async USB DAC, Driver v1.0.4b (4ms) > Blaxius BNC interlink > BD-Design BD30-SPR amplifiers > BD-Design Custom Made Sigma loudspeakers.

XX settings basically similar to PeterSt's

PeterSt

Administrator
High Grade Audiophile

Offline

Posts: 16854

Re: Error having a too long path (+260 characters).

« Reply #1 on: February 20, 2015, 07:33:16 pm »

Bert,

I think that you know what the problem is : too long files. And yes, a bit too bad if you now run this for the first time.

Hint : Make your Galleries Names as short as possible. But obvious of course.

I can put this on the ToDo for the next version, so the messages about it end up in the log files only (then for you to check). But this will not be ready "tomorrow".
Btw, I had thought that such processes would end up with log entries only, but apparently not.

Well, sorry

...
Peter


	Logged

For the Stealth III LPS PC :
W10-14393.0 - July 17, 2021 (2.11)
XXHighEnd Mach III Stealth LPS PC -> Xeon Scalable 14/28 core with Hyperthreading On (set to 14/28 cores in BIOS and set to 10/20 cores via Boot Menu) @~660MHz, 48GB, Windows 10 Pro 64 bit build 14393.0 from RAM, music on LAN / Engine#4 Adaptive Mode / Q1/-/3/4/5 = 14/-/0/0/*1*/ Q1Factor = *4* / Dev.Buffer = 4096 / ClockRes = *10ms* / Memory = Straight Contiguous / Include Garbage Collect / SFS = *10.13* (max 10.13) / not Invert / Phase Alignment Off / Playerprio = Low / ThreadPrio = Realtime / Scheme = Core 3-5 / Not Switch Processors during Playback = Off/ Playback Drive none (see OS from RAM) / UnAttended (Just Start) / Always Copy to XX Drive (see OS from RAM) / Stop Desktop, Remaining, WASAPI and W10 services / Use Remote Desktop / Keep LAN - Not Persist / WallPaper On / OSD Off (!) / Running Time Off / Minimize OS / XTweaks : Balanced Load = *62* / Nervous Rate = *1* / Cool when Idle = n.a / Provide Stable Power = 1 / Utilize Cores always = 1 / Time Performance Index = Optimal / Time Stability = Stable / Custom Filtering *Low* (16x) / Always Clear Proxy before Playback = On -> USB3 from MoBo -> Lush^3
A: W-Y-R-G, B: *W-G* USB 1m00 -> Phisolator 24/768 Phasure NOS1a/G3 75B (BNC Out) async USB DAC, Driver v1.0.4b (16ms) -> B'ASS Current Amplifier -> Blaxius*^2.5* A:B-G, B:B-G Interlink -> Orelo MKII Active Open Baffle Horn Speakers. ET^2 Ethernet from Mach III to Music Server PC (RDC Control).
Removed Switching Supplies from everywhere (also from the PC).

For a general PC :
W10-10586.0 - May 2016 (2.05+)
*XXHighEnd PC -> I7 3930k with Hyperthreading On (12 cores)* @~500MHz, 16GB, Windows 10 Pro 64 bit build 10586.0 from RAM, music on LAN / Engine#4 Adaptive Mode / Q1/-/3/4/5 = 14/-/1/1/1 / Q1Factor = 1 / Dev.Buffer = 4096 / ClockRes = 1ms / Memory = Straight Contiguous / Include Garbage Collect / SFS = 0.10 (max 60) / not Invert / Phase Alignment Off / Playerprio = Low / ThreadPrio = Realtime / Scheme = Core 3-5 / Not Switch Processors during Playback = Off/ Playback Drive none (see OS from RAM) / UnAttended (Just Start) / Always Copy to XX Drive (see OS from RAM) / All Services Off / Keep LAN - Not Persist / WallPaper On / OSD On / Running Time Off / Minimize OS / XTweaks : Balanced Load = *43* / Nervous Rate = 1 / Cool when Idle = 1 / Provide Stable Power = 1 / Utilize Cores always = 1 / Time Performance Index = *Optimal* / Time Stability = *Stable* / Custom Filter *Low* 705600 / -> USB3 *from MoBo* -> Clairixa USB 15cm -> Intona Isolator -> Clairixa USB 1m80 -> 24/768 Phasure NOS1a 75B (BNC Out) async USB DAC, Driver v1.0.4b (4ms) -> Blaxius BNC interlink *-> B'ASS Current Amplifier /w Level4 -> Blaxius Interlink* -> Orelo MKII Active Open Baffle Horn Speakers.
Removed Switching Supplies from everywhere.

Global Moderator

BertD

Audio Enthusiast

Offline

Posts: 422

Only the Best!

Re: Error having a too long path (+260 characters).

« Reply #2 on: February 20, 2015, 07:52:11 pm »

Quote from: PeterSt on February 20, 2015, 07:33:16 pm

I can put this on the ToDo for the next version, so the messages about it end up in the log files only (then for you to check). But this will not be ready "tomorrow".

If not for me (my Galleries will be done by then!) then for somebody else in the future. yes


	Logged

PeterSt

Administrator
High Grade Audiophile

Offline

Posts: 16854

Re: Error having a too long path (+260 characters).

« Reply #3 on: February 20, 2015, 07:53:18 pm »

PS: Why do I recall that all errors from this end up in the Log File only ? most probably because I did this all already several months ago. But I will check it.

PPS: Hint-2 : Skip the Classical for now. Wink