Se connecter
Se connecter
Mot de passe oublié ?
ou
Créer un compte
ou
Se connecter avec Facebook
Notifications
< Retour vers TC Electronic
Agrandir
TC Electronic
TC Electronic
(1343 avis produit)
Produits 347 347
Actu 402 402
Articles 50 50
Tutoriels Tutos 30 30
Avis 1 343 1,3k
Petites annonces Annonces 138 138
Forums 2 606 2,6k

Sujet Powercore, c'était donc pas tout à fait la fin ?

  • 4 réponses
  • 2 participants
  • 879 vues
  • 2 followers
Sujet de la discussion Powercore, c'était donc pas tout à fait la fin ?
On aurait donc une release candidate d'un drivers 4.3.3 qui circule...

extrait du forum tc electronic (http://forum.tcelectronic.com/topic/10504/powercore-433-rc/):

"PowerCore 4.3.3 RC for OSX, Windows 64bit, Windows 32bit
fixed a memory leak in the PowerCore device OS in conjunction with using licensed plug-ins across several PowerCore devices.

added security checks in the PowerCore/OS

Master X5/X3: Labels corrected: Compressor Attack, Limiter (Softclip) Amount, Limiter Attack

MD3, BrickwallLimiter Version 1.2.5 now included: metering fixed

Dynamic EQ Version 1.2.4 now included: latency reporting fixed

fixed various issues in the PowerCore Control Panel related to device arrival and reset

fixed issue in PowerCore device OS leading to "communication error"



OSX

fixed "complete() while DMA active" KP when instantiating a lot of licensed plug-ins across several PowerCore devices.

added various driver security checks

Dynamic EQ.vst/component bundle: missing 1131.bmp added

fixes related to PowerCore reset and bringing up all DSPs on PowerCore X8/6000

fixed plug-in auval crashes under Logic 9.1.5

fixed MacBook Pro PowerCore/FireWire device removal

PowerCore Control Panel 4.3.3 is now included with lot of bug fixes and device arrival/removal fixes.

changes to the sleep/wake behavior for firewire devices



Windows

complete driver rewrite (all driver fixes and improvements of the OSX version are included)

Windows: kernel event logging added

PowerCore driver package not separately listed in the Windows list of installed items anymore. (This could stuck there since Windows does not always remove the associated driver package when removing the complete software package.)

driver signing fixed (timestamp was missing)

MD3,BWL,MasterX3/X5 dependencies to Microsoft redistributable runtime libs removed. (This fixes issues under XP where the plug-in would not load if the MS RT isn't installed.)

fixed Character presets.

PowerCore plug-in messages are shown in the Windows event viewer (replacement for the PowerCore Messenger that existed in PowerCore versions prior to 4.)



Some hints to make a succesful installation:
Supported OS versions are OSX 10.6 and Windows Vista/7 (with 32bit and 64bit Intel kernel), OSX 10.5 and Windows XP-SP3 (with 32bit kernel)

Please ensure that you have recently updated your system (otherwise certificates needed to check if the driver is correctly signed could be outdated leading to "device cannot start").

All PowerCore Firewire versions are supported, PCIe and PCI MkII are supported, The system will work with the Classic PowerCore PCI as well, but we will not be able to provide support anymore. Please use the forum in cases you will need help with the Classic PowerCore."

(Pourquoi jouer tant de notes alors qu'il suffit de jouer les plus belles ? MD)

2
Je viens voir par ici ce qu'il se passe. ;-)

 

 

 

3

la suite sera donc là : https://fr.audiofanzine.com/carte-son-dsp/tc-electronic/Powercore-6000/forums/t.469970,le-nouveau-driver-4-3-3-devrait-regler-pas-mal-de-bugs.html

 

(Pourquoi jouer tant de notes alors qu'il suffit de jouer les plus belles ? MD)

[ Dernière édition du message le 22/09/2011 à 18:40:13 ]

4
A mon avis je vais avoir pas mal de lignes à écrire. Je viens d'essayer et c'est pas ça du tout. Suite sur l'autre thread...

 

 

 

5
Le driver 4.4. RC II est sur les rails... Il n'y aura plus de nouveaux plugs au niveau de cette plateforme (powercore) mais le driver a été réécrit intégralement et le support reste en place. Les plugs en natif, c'est visiblement pas à l'ordre du jour...