PFL-Player active Playlist
Re: PFL-Player active Playlist
Yes, I'm aware of that. Currently I'm sort of in a deadlock: I need a soundcard, but it has to be PCIe since my mainboard isn't sporting any PCI-slots.... So it's either plague or pestilence: M-Audio (who I'd prefere) does not offer affordable PCIe-Cards and I am not toooo convinced about Creative/Asus-cards. Auzentech is basically not availible in Germany and I shy away from the ESI Maya44 XTe, which really tempts me for its features but seems to be diva'esque in terms of win7-64...
Any ideas?
Any ideas?
Re: PFL-Player active Playlist
The assignment of sound devices is already 'locked' within ProppFrexx.
However, the issue is a bit more complex and can not directly be resolved during the time ProppFrexx is running.
The issue arise from a new sound driver being installed in the background (e.g. by an automatic OS update).
A simple restart of ProppFrexx resp. a reboot of the machine (depending on the driver installation) might have already resolved the issue.
The problem is due to the following scenario:
ProppFrexx is running while the new driver is being installed - as such ProppFrexx is using the 'old' driver, which is being invalidated by the new driver installation in the background.
The OS can not release that 'old' driver while it is being currently used, so it had to install the new driver side by side.
A restart/reboot at this time would enable the OS to release the 'old' driver and enable the new one. ProppFrexx could now use that new driver.
In some case however, the new driver is providing a new ID and name and as such ProppFrexx couldn't resolve its assignment (since ProppFrexx could only identify the device assignment by checking its name and driver id - which typically should not change for the same device - but as said, saidly some devices do change that with a new driver installation).
So it all depends (if ProppFrexx could re-identify the device) on how the device driver is implemented.
However, the issue is a bit more complex and can not directly be resolved during the time ProppFrexx is running.
The issue arise from a new sound driver being installed in the background (e.g. by an automatic OS update).
A simple restart of ProppFrexx resp. a reboot of the machine (depending on the driver installation) might have already resolved the issue.
The problem is due to the following scenario:
ProppFrexx is running while the new driver is being installed - as such ProppFrexx is using the 'old' driver, which is being invalidated by the new driver installation in the background.
The OS can not release that 'old' driver while it is being currently used, so it had to install the new driver side by side.
A restart/reboot at this time would enable the OS to release the 'old' driver and enable the new one. ProppFrexx could now use that new driver.
In some case however, the new driver is providing a new ID and name and as such ProppFrexx couldn't resolve its assignment (since ProppFrexx could only identify the device assignment by checking its name and driver id - which typically should not change for the same device - but as said, saidly some devices do change that with a new driver installation).
So it all depends (if ProppFrexx could re-identify the device) on how the device driver is implemented.
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
Re: PFL-Player active Playlist
As said, if a new driver 'decides' to rename the device or its internal ID or change the Windows sound device ordering - ProppFrexx can not 'link' this new device with any previously used device (since there is no way anymore to identify the same physical device as it was identified before).
So this is unfortunately not under my control - ProppFrexx can simply try its best to find the correct device (previously assigned), but at some point this is not possible anymore.
Basically due to the fact, that device drivers are not perfectly implemented or do not behave as they preferrably should.
Also note, this definitly MUST happen (it depends on the driver and installation mode).
E.g. it was happening for one user with a specific internal RealTek soundcard.
What soundcard was effected in your case?
So this is unfortunately not under my control - ProppFrexx can simply try its best to find the correct device (previously assigned), but at some point this is not possible anymore.
Basically due to the fact, that device drivers are not perfectly implemented or do not behave as they preferrably should.
Also note, this definitly MUST happen (it depends on the driver and installation mode).
E.g. it was happening for one user with a specific internal RealTek soundcard.
What soundcard was effected in your case?
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
Re: PFL-Player active Playlist
Great, that it is working for you - and it is also working again fine for adger.
His issue is now to select a decent soundcard fitting his budget
His issue is now to select a decent soundcard fitting his budget
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution