Se connecter
Se connecter
Mot de passe oublié ?
ou
Créer un compte
ou
Se connecter avec Facebook
Notifications
< Retour vers Native Instruments Maschine
Agrandir
Native Instruments Maschine
SérieNative Instruments Maschine

Produits 91 91
Actu 142 142
Articles 16 16
Tutoriels Tutos 17 17
Avis 165 165
Petites annonces Annonces 217 217
Forums 1 421 1,4k

Sujet Export à 192 kHz NOK

  • 7 réponses
  • 3 participants
  • 183 vues
  • 2 followers
Sujet de la discussion Export à 192 kHz NOK
HELP !

J'exporte mes titres à 192 kHz : RAS.
Seul un de mes titres pose problème : lorsque je l'exporte à 192 kHz, le fichier audio est là, mais est vide, sans son, juste qqs craquements. En revanche, qd je l'exporte à 96 kHz, ou moins, le résultat est OK.
Et surtout, après l'export à 192 kHz de ce seul titre, windows craque continuellement !!!!!! Jusqu'au reboot suivant !

J'ai effectué un scan LatencyMon avant / après.
Avant : pas de problème. Les conclusions sont : "votre PC est OK pour du traitement audio en temps réel"
Après.... C'est moins joli (voir rapport complet dans les commentaires) Je constate notamment ce fichu driver wdf01000.sys, à la latence somme toute acceptable (0,5 ms) mais appelé 585000 fois pendant les 10 minutes de l'export. Soit presque 6 minutes !!!

D'autre part, dans ce cas, mon gestionnaire de tâches m'annonce "interruption système", et mon CPU est temporairement à 100%.

(Win10, i7-8750H @ 2.20GHz, 16Go)

Au secours Obiwan Kenobi !
2
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 0:10:19 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: MSI
OS version: Windows 10, 10.0, version 2004, build: 19041 (x64)
Hardware: GP63 Leopard 8RD, Micro-Star International Co., Ltd.
CPU: GenuineIntel Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
Logical processors: 12
Processor groups: 1
RAM: 16230 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 2208 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.


_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 44335,0
Average measured interrupt to process latency (µs): 5,654166

Highest measured interrupt to DPC latency (µs): 44323,30
Average measured interrupt to DPC latency (µs): 2,446017


_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 139,942935
Driver with highest ISR routine execution time: ACPI.sys - Pilote ACPI pour NT, Microsoft Corporation

Highest reported total ISR routine time (%): 0,006857
Driver with highest ISR total time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation

Total time spent in ISRs (%) 0,007602

ISR count (execution time <250 µs): 589917
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 0
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µs): 0
ISR count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 740,619565
Driver with highest DPC routine execution time: ACPI.sys - Pilote ACPI pour NT, Microsoft Corporation

Highest reported total DPC routine time (%): 0,194791
Driver with highest DPC total execution time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation

Total time spent in DPCs (%) 0,217598

DPC count (execution time <250 µs): 946803
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 201
DPC count (execution time 1000-2000 µs): 0
DPC count (execution time 2000-4000 µs): 0
DPC count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count: chrome.exe

Total number of hard pagefaults 10133
Hard pagefault count of hardest hit process: 1872
Number of processes hit: 80


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 27,509757
CPU 0 ISR highest execution time (µs): 139,942935
CPU 0 ISR total execution time (s): 0,564494
CPU 0 ISR count: 589893
CPU 0 DPC highest execution time (µs): 740,619565
CPU 0 DPC total execution time (s): 15,818834
CPU 0 DPC count: 885660
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 2,990558
CPU 1 ISR highest execution time (µs): 31,340580
CPU 1 ISR total execution time (s): 0,000386
CPU 1 ISR count: 20
CPU 1 DPC highest execution time (µs): 453,576087
CPU 1 DPC total execution time (s): 0,127044
CPU 1 DPC count: 8715
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 3,286453
CPU 2 ISR highest execution time (µs): 29,026268
CPU 2 ISR total execution time (s): 0,000078
CPU 2 ISR count: 4
CPU 2 DPC highest execution time (µs): 232,680254
CPU 2 DPC total execution time (s): 0,057774
CPU 2 DPC count: 14711
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 2,302269
CPU 3 ISR highest execution time (µs): 0,0
CPU 3 ISR total execution time (s): 0,0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 207,776268
CPU 3 DPC total execution time (s): 0,010098
CPU 3 DPC count: 2383
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 2,659184
CPU 4 ISR highest execution time (µs): 0,0
CPU 4 ISR total execution time (s): 0,0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 148,137681
CPU 4 DPC total execution time (s): 0,024861
CPU 4 DPC count: 6902
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 2,286057
CPU 5 ISR highest execution time (µs): 0,0
CPU 5 ISR total execution time (s): 0,0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 187,101449
CPU 5 DPC total execution time (s): 0,008826
CPU 5 DPC count: 1957
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 2,499545
CPU 6 ISR highest execution time (µs): 0,0
CPU 6 ISR total execution time (s): 0,0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 190,372283
CPU 6 DPC total execution time (s): 0,022711
CPU 6 DPC count: 4849
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 2,267984
CPU 7 ISR highest execution time (µs): 0,0
CPU 7 ISR total execution time (s): 0,0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 196,618659
CPU 7 DPC total execution time (s): 0,008283
CPU 7 DPC count: 1733
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 2,475293
CPU 8 ISR highest execution time (µs): 0,0
CPU 8 ISR total execution time (s): 0,0
CPU 8 ISR count: 0
CPU 8 DPC highest execution time (µs): 187,405797
CPU 8 DPC total execution time (s): 0,028267
CPU 8 DPC count: 6513
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 2,191870
CPU 9 ISR highest execution time (µs): 0,0
CPU 9 ISR total execution time (s): 0,0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 185,077899
CPU 9 DPC total execution time (s): 0,012549
CPU 9 DPC count: 2764
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 2,604167
CPU 10 ISR highest execution time (µs): 0,0
CPU 10 ISR total execution time (s): 0,0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 219,630435
CPU 10 DPC total execution time (s): 0,033844
CPU 10 DPC count: 7409
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 2,223523
CPU 11 ISR highest execution time (µs): 0,0
CPU 11 ISR total execution time (s): 0,0
CPU 11 ISR count: 0
CPU 11 DPC highest execution time (µs): 215,817029
CPU 11 DPC total execution time (s): 0,019070
CPU 11 DPC count: 3408
_________________________________________________________________________________________________________
3
Autre constat : sur la totalité des titres exportés à 192 kHz, le rendu des basses est différent, elles sont beaucoup plus présentes. Trop !
Je repasse à 96 kHz : basses OK. Incroyable, non ?

Dernière info avant de clore le sujet : la vitesse de modulation des effets de modulation (genre chorus, trémolo...) des instruments gérés par Kontakt (ben... tous les sons samplés, en fait) varie en fonction de la fréquence d'export.... (ex: à 96 Khz, le chorus intégré de Scarbee MM Bass est 2 fois plus rapide qu'à 48 kHz) Incroyable, non ?
J'avais ouvert un ticket auprès de NI lorsque j'ai découvert cela : "utilisez kontakt 6" me disaient-ils à l’époque. "c'est bien ce que je fais" leur répondis-je...
Ticket resté sans suite.

On me dit enfin, sur un autre forum, qu'exporter à une si haute fréquence est inutile... Soit... J'avoue que mon oreille de 48 ans ne fait pas de différence. J'imagine pourtant que si la fonction existe, c'est qu'elle a une utilité !

Bref. Devant tant d'arguments, je repasse définitivement à 96 kHz
4
Quand tu fait ton export fait le en wav 32bits

"Tu peux vendre un million de disques et avoir l'impression que c'est un échec. Ou tu peux ne rien vendre du tout et te sentir très heureux", Vangelis. 

MY Music Link                            .

[ Dernière édition du message le 29/12/2020 à 09:31:18 ]

5
Tu as investi dans un portable, et le look est parfait pour l'utilisation conjointe avec maschine...
seulement il ne sert à rien de vouloir faire la course, même avec toute une écurie de pur sang, s'ils ne savent pas courir.
Il te reste à lâcher quelques billets supplémentaires pour acquérir une vraie carte son, car realtek c'est très bien pour vendre un pc, et suffisant pour les gamers, mais pour des exports audio convenable c'est un autre niveau de jeu.
ça se passe par là : https://fr.audiofanzine.com/interface-audionumerique-usb/
il y en a pour tout le monde, mais fais toi ton idée en lisant les avis... :bravo:
6
Citation :
il ne sert à rien de vouloir faire la course, même avec toute une écurie de pur sang, s'ils ne savent pas courir.


:mdr:

"Tu peux vendre un million de disques et avoir l'impression que c'est un échec. Ou tu peux ne rien vendre du tout et te sentir très heureux", Vangelis. 

MY Music Link                            .

7
Citation de Nelyo74 :
Quand tu fait ton export fait le en wav 32bits

OK, je vais essayer

Citation de Pafinix :
Il te reste à lâcher quelques billets supplémentaires pour acquérir une vraie carte son, car realtek c'est très bien pour vendre un pc, et suffisant pour les gamers, mais pour des exports audio convenable c'est un autre niveau de jeu.

J'en ai une : presonus Studio 2|6. Peut-être non visible lors du scan car considérée comme externe ?
8
12 CPU logiques : seul le premier semble tourner à plein régime :

CPU 0 Interrupt cycle time (s): 27,509757
CPU 0 ISR highest execution time (µs): 139,942935
CPU 0 ISR total execution time (s): 0,564494
CPU 0 ISR count: 589893
CPU 0 DPC highest execution time (µs): 740,619565
CPU 0 DPC total execution time (s): 15,818834
CPU 0 DPC count: 885660

Tous les autres :
CPU x Interrupt cycle time (s): 2,990558
CPU x ISR highest execution time (µs): 31,340580
CPU x ISR total execution time (s): 0,000386
CPU x ISR count: 20
CPU x DPC highest execution time (µs): 453,576087
CPU x DPC total execution time (s): 0,127044
CPU x DPC count: 8715