| VidHD Question [message #380437] |
Thu, 31 January 2019 20:29  |
Steven Hirsch
Messages: 798
Registered: October 2012
Karma: 0
|
Senior Member |
|
|
I just received my VidHD card and am trying to drive an LCD computer monitor
through an HDMI-to-DVI adapter cable. Unfortunately this is not working. Can
anyone (John, if you're here) shed light on why this won't cooperate? The
monitor just goes into standby with a floating "No Video Signal" message.
|
|
|
|
| Re: VidHD Question [message #380441 is a reply to message #380437] |
Thu, 31 January 2019 22:18  |
|
|
Originally posted by: thom
On Thursday, January 31, 2019 at 8:29:15 PM UTC-5, Steven Hirsch wrote:
> I just received my VidHD card and am trying to drive an LCD computer monitor
> through an HDMI-to-DVI adapter cable. Unfortunately this is not working. Can
> anyone (John, if you're here) shed light on why this won't cooperate? The
> monitor just goes into standby with a floating "No Video Signal" message.
I installed mine yesterday in my IIe to compare with the A2Heven VGA Scaler.. As of right now, I'm sort of leaning toward calling it "beautiful, but temperamental".
My IIe is running through a LCD TV (VGA port, component and 2 HDMI) and I installed the card in the preferred (and otherwise empty) Slot 3.
From a cold boot with the VidHD going to HDMI, I see the firmware bootup of the card, then the screen will go black. I can jump into the control panel (Ctrl-6), but 9 times out of 10, it's unresponsive. If I give it the three finger salute (Ctrl+OApple+Reset), it'll boot as it should, control panel is fine, etc...
If I switch over to the VGA Scaler, everything runs as expected; but (again 9 times out of 10), if I switch over to the VidHD, it'll sit black/unresponsive control panel until I reset.
I'm going to install it into my IIgs (where I expect to live) this weekend to see if it behaves similarly. I consider there's a lot going on in my IIe (Fastchip, Uthernet, Ramworks, Soundblaster, CFFA3k), so there's a bit to consider re: compatibility. The IIgs is less busy (just a Microdrive Turbo and an Uthernet II) so it'll be easier to properly troubleshoot if I see the same behavior.
One other thing, while I'm thinking about it... I've also noticed that changes made in the control panel are finicky. The only change that seems to stick between resets is border colours. Text and background colours revert to default if I soft reset and everything resets with a hard reset (oh, and control panel interaction passes through to the system...).
I'll dig out an HDMI to DVI adapter this weekend and give it a shot on a monitor and report back. In the meantime, try invoking the control panel and see if it wakes the monitor up...
(For the record... I'm not trying to come off as negative about the card; as I mentioned near the beginning, the output is truly beautiful... it just feels little rough/quirky at the moment).
thom
|
|
|
|
| Re: VidHD Question [message #380448 is a reply to message #380441] |
Fri, 01 February 2019 07:23 |
Steven Hirsch
Messages: 798
Registered: October 2012
Karma: 0
|
Senior Member |
|
|
On 1/31/19 10:18 PM, thom wrote:
> On Thursday, January 31, 2019 at 8:29:15 PM UTC-5, Steven Hirsch wrote:
>> I just received my VidHD card and am trying to drive an LCD computer
>> monitor through an HDMI-to-DVI adapter cable. Unfortunately this is not
>> working. Can anyone (John, if you're here) shed light on why this won't
>> cooperate? The monitor just goes into standby with a floating "No Video
>> Signal" message.
> If I switch over to the VGA Scaler, everything runs as expected; but (again
> 9 times out of 10), if I switch over to the VidHD, it'll sit
> black/unresponsive control panel until I reset.
Interesting. In the interim, I also tried an HDMI-to-DisplayPort adapter and
am seeing the same intermittent behavior. If I hold my mouth just right, it
gives a nice display after startup. But, this only works about 1 in 5 times
and I get nothing for the other 4. As you may have guessed, I don't have a
single monitor with built-in HDMI ports (out of about a dozen here).
> (For the record... I'm not trying to come off as negative about the card;
> as I mentioned near the beginning, the output is truly beautiful... it just
> feels little rough/quirky at the moment).
I have confidence that John will work this all out. When I'm able to get a
display it does look great!
|
|
|
|
| Re: VidHD Question [message #380454 is a reply to message #380441] |
Fri, 01 February 2019 08:12 |
|
|
Originally posted by: cb meeks
On Thursday, January 31, 2019 at 10:18:49 PM UTC-5, thom wrote:
> I consider there's a lot going on in my IIe (Fastchip, Uthernet, Ramworks, Soundblaster, CFFA3k),
You have a Soundblaster in your IIe? Can you tell me more about this?
|
|
|
|
| Re: VidHD Question [message #380459 is a reply to message #380454] |
Fri, 01 February 2019 10:00 |
|
|
Originally posted by: thom
On Friday, February 1, 2019 at 8:12:52 AM UTC-5, cb meeks wrote:
> On Thursday, January 31, 2019 at 10:18:49 PM UTC-5, thom wrote:
>> I consider there's a lot going on in my IIe (Fastchip, Uthernet, Ramworks, Soundblaster, CFFA3k),
>
> You have a Soundblaster in your IIe? Can you tell me more about this?
No, but I can tell you all about emailing late at night and thinking about two entirely different retro builds (I've added a MT-32 to an old PC and getting some conflicts with the Soundblaster...). :)
Mockingboard, not Soundblaster.
|
|
|
|
| Re: VidHD Question [message #380461 is a reply to message #380459] |
Fri, 01 February 2019 10:45 |
|
|
Originally posted by: jbrooks
Hi guys.
It looks like the linux HDMI driver has trouble reliably identifying the resolution of certain displays due to a timeout on the HDID query (I think). I'm currently working on a linux driver patch which will ignore the HDID query and just force 1920x1080 resolution.
If your display doesn't turn on within a second or two of the Apple II being powered on, or if your display reports 1024x768 resolution instead of 1920x1080, those are both symptoms of this linux HDMI driver issue.
I'll need help testing the fix as the problem seems sensitive to the specific system setup. Applying firmware upgrades will require a PC/Mac with an SD card writer, the Etcher program (or equivalent), and a whopping 128MB or greater microSD card with SD adapter.
-JB
|
|
|
|
| Re: VidHD Question [message #380462 is a reply to message #380461] |
Fri, 01 February 2019 11:20 |
|
|
Originally posted by: thom
On Friday, February 1, 2019 at 10:45:58 AM UTC-5, jbr...@blueshiftinc.com wrote:
> Hi guys.
>
> It looks like the linux HDMI driver has trouble reliably identifying the resolution of certain displays due to a timeout on the HDID query (I think).. I'm currently working on a linux driver patch which will ignore the HDID query and just force 1920x1080 resolution.
>
> If your display doesn't turn on within a second or two of the Apple II being powered on, or if your display reports 1024x768 resolution instead of 1920x1080, those are both symptoms of this linux HDMI driver issue.
>
> I'll need help testing the fix as the problem seems sensitive to the specific system setup. Applying firmware upgrades will require a PC/Mac with an SD card writer, the Etcher program (or equivalent), and a whopping 128MB or greater microSD card with SD adapter.
>
> -JB
You're a rockstar, JB. I'd be happy to offer up my card to test on. Can bounce between a IIgs and a IIe and various displays if that'll help as well..
thom
|
|
|
|
| Re: VidHD Question [message #380466 is a reply to message #380461] |
Fri, 01 February 2019 13:09 |
Steven Hirsch
Messages: 798
Registered: October 2012
Karma: 0
|
Senior Member |
|
|
On 2/1/19 10:45 AM, jbrooks@blueshiftinc.com wrote:
> Hi guys.
>
> It looks like the linux HDMI driver has trouble reliably identifying the
> resolution of certain displays due to a timeout on the HDID query (I
> think). I'm currently working on a linux driver patch which will ignore the
> HDID query and just force 1920x1080 resolution.
>
> If your display doesn't turn on within a second or two of the Apple II
> being powered on, or if your display reports 1024x768 resolution instead of
> 1920x1080, those are both symptoms of this linux HDMI driver issue.
I thought it might be some sort of handshaking issue. Will locking the
resolution result in a suboptimal aspect ratio on older 6:9 (square) displays?
If so, this would seem to be a good candidate for control panel adjustment.
> I'll need help testing the fix as the problem seems sensitive to the
> specific system setup. Applying firmware upgrades will require a PC/Mac
> with an SD card writer, the Etcher program (or equivalent), and a whopping
> 128MB or greater microSD card with SD adapter.
I'll be glad to test anything you come up with. Thanks, John!
|
|
|
|
| Re: VidHD Question [message #380469 is a reply to message #380459] |
Fri, 01 February 2019 13:39 |
|
|
Originally posted by: cb meeks
On Friday, February 1, 2019 at 10:00:42 AM UTC-5, thom wrote:
> On Friday, February 1, 2019 at 8:12:52 AM UTC-5, cb meeks wrote:
>> On Thursday, January 31, 2019 at 10:18:49 PM UTC-5, thom wrote:
>>> I consider there's a lot going on in my IIe (Fastchip, Uthernet, Ramworks, Soundblaster, CFFA3k),
>>
>> You have a Soundblaster in your IIe? Can you tell me more about this?
>
> No, but I can tell you all about emailing late at night and thinking about two entirely different retro builds (I've added a MT-32 to an old PC and getting some conflicts with the Soundblaster...). :)
>
> Mockingboard, not Soundblaster.
LOL. I understand. But the idea of a SoundBlaster in an Apple IIe does "sound" pleasing....
|
|
|
|
| Re: VidHD Question [message #380484 is a reply to message #380461] |
Fri, 01 February 2019 16:28 |
christopher.shepherd2
Messages: 13
Registered: December 2012
Karma: 0
|
Junior Member |
|
|
I have replicated a no-video situation (ROM 01 IIgs + old Dell 2405FPW monitor + HDMI/DVI adapter) and am capable of testing updates according to the specified requirements.
Le vendredi 1 février 2019 10:45:58 UTC-5, jbr...@blueshiftinc.com a écrit :
> Hi guys.
>
> It looks like the linux HDMI driver has trouble reliably identifying the resolution of certain displays due to a timeout on the HDID query (I think).. I'm currently working on a linux driver patch which will ignore the HDID query and just force 1920x1080 resolution.
>
> If your display doesn't turn on within a second or two of the Apple II being powered on, or if your display reports 1024x768 resolution instead of 1920x1080, those are both symptoms of this linux HDMI driver issue.
>
> I'll need help testing the fix as the problem seems sensitive to the specific system setup. Applying firmware upgrades will require a PC/Mac with an SD card writer, the Etcher program (or equivalent), and a whopping 128MB or greater microSD card with SD adapter.
>
> -JB
|
|
|
|
| Re: VidHD Question [message #380491 is a reply to message #380484] |
Fri, 01 February 2019 18:12 |
|
|
Originally posted by: Michael Mann
I am having trouble with the VidHD. I tried connecting a II+ and a IIe both to an older revision Dell U2410 and a new U2410. The symptoms are a blank screen, no input found, or the VidHD menu coming and going, toggling back and forth every ~5 seconds, with random lines of horizontal "static" on the screen. On the newer unit, the display would occasionally settle down after 5-10 minutes, but wouldn't survive a reboot. I hope it's something that can be fixed with an update: I bought a few VidHDs and my hopes were very high for the definitive Apple II* video solution.
|
|
|
|
| Re: VidHD Question [message #380492 is a reply to message #380461] |
Fri, 01 February 2019 18:14 |
Steven Hirsch
Messages: 798
Registered: October 2012
Karma: 0
|
Senior Member |
|
|
On 2/1/19 10:45 AM, jbrooks@blueshiftinc.com wrote:
> Hi guys.
>
> It looks like the linux HDMI driver has trouble reliably identifying the
> resolution of certain displays due to a timeout on the HDID query (I
> think). I'm currently working on a linux driver patch which will ignore the
> HDID query and just force 1920x1080 resolution.
>
> If your display doesn't turn on within a second or two of the Apple II
> being powered on, or if your display reports 1024x768 resolution instead of
> 1920x1080, those are both symptoms of this linux HDMI driver issue.
Hi, John.
I'm having much better luck with a cheap little 'Benfei' HDMI-to-VGA adapter
from Amazon. On a 1920 x 1280 Samsung LCD monitor it gives an instant, rock
solid display from my IIe. This adapter is USB powered. I wasn't sure if you
supplied enough power on the VidHD's connector to run an active adapter directly.
I'm having issues with square aspect monitors (e.g. 1600x1200 or 1280x1024).
They do give me a display, but shifted too far to the right to be usable. The
monitors do not have enough horizontal adjustment range to compensate. You
may want to give some thought to supporting traditional aspect-ratio monitors,
either though a mode selection or even an alternate firmware load.
|
|
|
|
| Re: VidHD Question [message #380493 is a reply to message #380491] |
Fri, 01 February 2019 18:39 |
|
|
Originally posted by: jbrooks
On Friday, February 1, 2019 at 3:12:24 PM UTC-8, Michael Mann wrote:
> I am having trouble with the VidHD. I tried connecting a II+ and a IIe both to an older revision Dell U2410 and a new U2410. The symptoms are a blank screen, no input found, or the VidHD menu coming and going, toggling back and forth every ~5 seconds, with random lines of horizontal "static" on the screen. On the newer unit, the display would occasionally settle down after 5-10 minutes, but wouldn't survive a reboot. I hope it's something that can be fixed with an update: I bought a few VidHDs and my hopes were very high for the definitive Apple II* video solution.
Hi Michael.
I have older 2405 Dell monitors which experience difficulty syncing to the 1920x1200 signal generated by VidHD's H5 chip. The Dell monitors often take a minute or two to sync. This appears unique to Dell 1200p displays and has not happened with any 1080p HDTVs.
That being said, I have not seen this 'slow sync' problem with other inputs plugged into the Dell, so my guess is that there is a mismatch between the HDMI timing values used by the H5 linux driver for 1200p and what the Dell monitor likes.
If possible, can you do a test of hooking VidHD to a 1080p TV and see if the problems are specific to the Dell monitor?
I'm in the process of reviewing the linux HDMI driver code as it seems finicky with certain displays. I expect to release a firmware update with improvements and hope that either the open-source community will improve the linux driver independently, or that I can fix the configurations commonly used with VidHD.
-JB
|
|
|
|
| Re: VidHD Question [message #380546 is a reply to message #380493] |
Sun, 03 February 2019 11:33 |
retrogear
Messages: 245
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
while we're on the subject of VidHD bug reports, I tried to run the Microdrive setup utility booted from floppy on my ROM 01 GS with a RM MicroDrive/Turbo in slot 7 and VidHD in slot 3. When I set Microdrive partitions then tried to save I got a crash to the monitor. I tried several times then removed the VidHD and was able to save partitions. Not sure if this was a fluke or not. I wasn't about to recreate the problem once I got it working. Otherwise, GS/OS from the MDT works great with the VidHD.
Larry G
|
|
|
|
| Re: VidHD Question [message #380556 is a reply to message #380437] |
Sun, 03 February 2019 13:57 |
|
|
Originally posted by: jbrooks
Here is a quick update on the VidHD issues reported by users:
1) Some 1200p Dell Monitors have trouble syncing to VidHD. The most often reported model is the Dell 2405 and 2410. The 2415 has been reported to work fine. A few 1080p displays are intermittently mis-detected as 1024x768 and require power-cycling the Apple II to correctly ID the display as 1080p
Looking at the linux HDMI driver, I suspect that the Dell issue is that when a monitor reports it's detailed video timings, the linux driver picks the closest match to an internal table of resolutions, and then sets the timing values to that table entry's settings. Some monitors want only their exact timing values and get confused/cranky with the linux settings.
2) A few users (3 so far) have reported odd Apple II hangs or error messages with VidHD installed. These symptoms appear to be due to a weak power supply with many cards installed and goes away when cards are removed.
3) Both the Microdrive Turbo and the Floppy Emu can freeze when VidHD starts up and reads video memory w/DMA . A workaround for this is to hold ctrl-reset for about 6 seconds at power on so VidHD's startup DMA happens before the disk boots. Another option for the MDT is to disable DMA using it's setup utility. I plan to add a 'boot delay' option in a future VidHD firmware update to automate this fix.
-JB
|
|
|
|
| Re: VidHD Question [message #380573 is a reply to message #380556] |
Sun, 03 February 2019 15:51 |
Steven Hirsch
Messages: 798
Registered: October 2012
Karma: 0
|
Senior Member |
|
|
On 2/3/19 1:57 PM, jbrooks@blueshiftinc.com wrote:
>
> Here is a quick update on the VidHD issues reported by users:
>
> 1) Some 1200p Dell Monitors have trouble syncing to VidHD. The most often
> reported model is the Dell 2405 and 2410. The 2415 has been reported to
> work fine. A few 1080p displays are intermittently mis-detected as 1024x768
> and require power-cycling the Apple II to correctly ID the display as
> 1080p
>
> Looking at the linux HDMI driver, I suspect that the Dell issue is that
> when a monitor reports it's detailed video timings, the linux driver picks
> the closest match to an internal table of resolutions, and then sets the
> timing values to that table entry's settings. Some monitors want only their
> exact timing values and get confused/cranky with the linux settings.
Thanks, John. Would this account for the "shifted" display I see on 4:3 monitors?
|
|
|
|
| Re: VidHD Question [message #380584 is a reply to message #380573] |
Sun, 03 February 2019 17:32 |
|
|
Originally posted by: jbrooks
On Sunday, February 3, 2019 at 12:52:00 PM UTC-8, Steven Hirsch wrote:
> On 2/3/19 1:57 PM, jbrooks wrote:
>>
>> Here is a quick update on the VidHD issues reported by users:
>>
>> 1) Some 1200p Dell Monitors have trouble syncing to VidHD. The most often
>> reported model is the Dell 2405 and 2410. The 2415 has been reported to
>> work fine. A few 1080p displays are intermittently mis-detected as 1024x768
>> and require power-cycling the Apple II to correctly ID the display as
>> 1080p
>>
>> Looking at the linux HDMI driver, I suspect that the Dell issue is that
>> when a monitor reports it's detailed video timings, the linux driver picks
>> the closest match to an internal table of resolutions, and then sets the
>> timing values to that table entry's settings. Some monitors want only their
>> exact timing values and get confused/cranky with the linux settings.
>
> Thanks, John. Would this account for the "shifted" display I see on 4:3 monitors?
Probably. I think the driver's HDTV timing values were designed for 16:9 displays.
It's likely that your HDMI->VGA adapter is more flexible at syncing to the VidHD video timing than the digital HDMI/DVI decoder in your monitor.
What brand is your monitor? Is it a Dell?
-JB
|
|
|
|
| Re: VidHD Question [message #380598 is a reply to message #380437] |
Sun, 03 February 2019 20:52 |
Steven Nelson
Messages: 91
Registered: January 2013
Karma: 0
|
Member |
|
|
On Thursday, January 31, 2019 at 7:29:15 PM UTC-6, Steven Hirsch wrote:
> I just received my VidHD card and am trying to drive an LCD computer monitor
> through an HDMI-to-DVI adapter cable. Unfortunately this is not working. Can
> anyone (John, if you're here) shed light on why this won't cooperate? The
> monitor just goes into standby with a floating "No Video Signal" message.
I installed my VidHD in a Rom01 IIGS (actually a IIe/GS conversiob aka an Eggs). I moved ZipGS8/64 from slot 3 to slot 2, installed VidHD and hooked Apple HD cinema display via HDMI/DVI adapter cable. Powered up and viola - a better than expected display. Only problem is display is off center of monitor - a little right and down. Cosmetic but I hope eventually some software adjustment can be made to allow positioning.
I am very impressed and satisfied. Congrats to a great product.
--Steven
|
|
|
|
| Re: VidHD Question [message #380627 is a reply to message #380584] |
Mon, 04 February 2019 07:26 |
Steven Hirsch
Messages: 798
Registered: October 2012
Karma: 0
|
Senior Member |
|
|
On 2/3/19 5:32 PM, jbrooks@blueshiftinc.com wrote:
> On Sunday, February 3, 2019 at 12:52:00 PM UTC-8, Steven Hirsch wrote:
>> Thanks, John. Would this account for the "shifted" display I see on 4:3
>> monitors?
> Probably. I think the driver's HDTV timing values were designed for 16:9
> displays.
>
> It's likely that your HDMI->VGA adapter is more flexible at syncing to the
> VidHD video timing than the digital HDMI/DVI decoder in your monitor.
>
> What brand is your monitor? Is it a Dell?
Almost all my monitors are Dell branded. Maybe I'm just speaking for my own
needs, but getting proper operation on 4:3 displays seems rather important.
|
|
|
|
| Re: VidHD Question [message #380644 is a reply to message #380493] |
Mon, 04 February 2019 11:54 |
scott
Messages: 4237
Registered: February 2012
Karma: 0
|
Senior Member |
|
|
In article <2f018319-95af-4fbb-b1bc-270a0f4b58df@googlegroups.com>,
<jbrooks@blueshiftinc.com> wrote:
> I'm in the process of reviewing the linux HDMI driver code as it seems
> finicky with certain displays. I expect to release a firmware update
> with improvements and hope that either the open-source community will
> improve the linux driver independently, or that I can fix the
> configurations commonly used with VidHD.
Mine arrived Friday; I did some quick tests with a ROM 01 IIGS I had sitting
around (no peripherals beyond an Apple 1-MB RAM expansion, and I just hit
Ctrl-Reset and did some Hi-Res and Lo-Res tests from BASIC...might've gotten
some SHR tests by running the self-test).
The first test was with a 32" TV with a native 1360x768 resolution. The
right and bottom edges were cut off, as you can see in this sliding-apple
error screen:
https://home.alfter.us/s/BkrHQ4fPHjt3A38
I then tested with the 28" 4K monitor I use with my primary desktop
computer. It briefly tried to sync up before going into sleep mode. (FWIW,
it's always been slow to switch modes...don't know if that might have
something to do with it.)
I was able to get good results with a smaller (maybe 20" or so) TV I'd
picked up at Goodwill a while back. This one also works with an
RGB-to-component adapter I had built a while back, so it may be a bit more
tolerant of iffy signals.
I'm at work right now, or I would've tried to name makes and models.
_/_
/ v \ Scott Alfter (remove the obvious to send mail)
(IIGS( https://alfter.us/ Top-posting!
\_^_/ >What's the most annoying thing on Usenet?
|
|
|
|
|
|
| Re: VidHD Question [message #380667 is a reply to message #380437] |
Mon, 04 February 2019 20:21 |
|
|
Originally posted by: Katherine Rohl
My card exhibits the same symptoms and in addition the Control+6 in BASIC does nothing. I have a ROM03 GS and I'm using a new-ish Dell 4K monitor at my desk. I removed the MicroDrive IDE adapter and RAM expansion in case it was stressing the power supply but no luck.
|
|
|
|
| Re: VidHD Question [message #380670 is a reply to message #380667] |
Mon, 04 February 2019 22:53 |
retrogear
Messages: 245
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
On Monday, February 4, 2019 at 7:21:17 PM UTC-6, Katherine Rohl wrote:
> My card exhibits the same symptoms and in addition the Control+6 in BASIC does nothing. I have a ROM03 GS and I'm using a new-ish Dell 4K monitor at my desk. I removed the MicroDrive IDE adapter and RAM expansion in case it was stressing the power supply but no luck.
1080p = 1080 lines = VidHD compatible
4K = 2160 lines so I would assume not compatible
Larry G
|
|
|
|
| Re: VidHD Question [message #380676 is a reply to message #380670] |
Tue, 05 February 2019 01:39 |
|
|
Originally posted by: Anthony Adverse
On Tuesday, February 5, 2019 at 2:53:27 PM UTC+11, retrogear wrote:
> On Monday, February 4, 2019 at 7:21:17 PM UTC-6, Katherine Rohl wrote:
>> My card exhibits the same symptoms and in addition the Control+6 in BASIC does nothing. I have a ROM03 GS and I'm using a new-ish Dell 4K monitor at my desk. I removed the MicroDrive IDE adapter and RAM expansion in case it was stressing the power supply but no luck.
>
> 1080p = 1080 lines = VidHD compatible
> 4K = 2160 lines so I would assume not compatible
>
> Larry G
Oddly at the moment I'd expect 4k to scale upwards quite happily, there's got to be "bugger all" 4k equipment but plenty of 1080p. But you might be right there.
A
|
|
|
|
| Re: VidHD Question [message #380686 is a reply to message #380676] |
Tue, 05 February 2019 06:34 |
retrogear
Messages: 245
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
On Tuesday, February 5, 2019 at 12:39:18 AM UTC-6, Anthony Adverse wrote:
> On Tuesday, February 5, 2019 at 2:53:27 PM UTC+11, retrogear wrote:
>> On Monday, February 4, 2019 at 7:21:17 PM UTC-6, Katherine Rohl wrote:
>>> My card exhibits the same symptoms and in addition the Control+6 in BASIC does nothing. I have a ROM03 GS and I'm using a new-ish Dell 4K monitor at my desk. I removed the MicroDrive IDE adapter and RAM expansion in case it was stressing the power supply but no luck.
>>
>> 1080p = 1080 lines = VidHD compatible
>> 4K = 2160 lines so I would assume not compatible
>>
>> Larry G
>
> Oddly at the moment I'd expect 4k to scale upwards quite happily, there's got to be "bugger all" 4k equipment but plenty of 1080p. But you might be right there.
>
> A
On the other hand, I would think a 4K display can show 1080p simply by mirroring two consecutive horizontal and vertical pixels but it has to "detect"
when to do the conversion and maybe the VidHD signal doesn't trigger it.
Larry G
|
|
|
|
| Re: VidHD Question [message #380704 is a reply to message #380670] |
Tue, 05 February 2019 11:47 |
scott
Messages: 4237
Registered: February 2012
Karma: 0
|
Senior Member |
|
|
In article <4cbf6d97-c6e1-4348-aba4-de2c1ebcd252@googlegroups.com>,
retrogear <larrygr510@gmail.com> wrote:
> On Monday, February 4, 2019 at 7:21:17 PM UTC-6, Katherine Rohl wrote:
>> My card exhibits the same symptoms and in addition the Control+6 in
> BASIC does nothing. I have a ROM03 GS and I'm using a new-ish Dell 4K
> monitor at my desk. I removed the MicroDrive IDE adapter and RAM
> expansion in case it was stressing the power supply but no luck.
>
> 1080p = 1080 lines = VidHD compatible
> 4K = 2160 lines so I would assume not compatible
Most monitors will adapt to lower resolutions. There's not a 4K monitor on
the market that won't display a 1080p signal if that's you feed it, just as
a 1080p monitor will handle 720p (common for broadcast TV from the likes of
ABC or Fox) or 480p from a DVD.
_/_
/ v \ Scott Alfter (remove the obvious to send mail)
(IIGS( https://alfter.us/ Top-posting!
\_^_/ >What's the most annoying thing on Usenet?
|
|
|
|
| Re: VidHD Question [message #380738 is a reply to message #380556] |
Tue, 05 February 2019 21:08 |
|
|
Originally posted by: jbrooks
On Sunday, February 3, 2019 at 10:57:17 AM UTC-8, jbr...@blueshiftinc.com wrote:
> Here is a quick update on the VidHD issues reported by users:
>
> 1) Some 1200p Dell Monitors have trouble syncing to VidHD. The most often reported model is the Dell 2405 and 2410. The 2415 has been reported to work fine. A few 1080p displays are intermittently mis-detected as 1024x768 and require power-cycling the Apple II to correctly ID the display as 1080p
>
> Looking at the linux HDMI driver, I suspect that the Dell issue is that when a monitor reports it's detailed video timings, the linux driver picks the closest match to an internal table of resolutions, and then sets the timing values to that table entry's settings. Some monitors want only their exact timing values and get confused/cranky with the linux settings.
>
> 2) A few users (3 so far) have reported odd Apple II hangs or error messages with VidHD installed. These symptoms appear to be due to a weak power supply with many cards installed and goes away when cards are removed.
>
> 3) Both the Microdrive Turbo and the Floppy Emu can freeze when VidHD starts up and reads video memory w/DMA . A workaround for this is to hold ctrl-reset for about 6 seconds at power on so VidHD's startup DMA happens before the disk boots. Another option for the MDT is to disable DMA using it's setup utility. I plan to add a 'boot delay' option in a future VidHD firmware update to automate this fix.
>
> -JB
Update:
The new HDMI driver in Linux 4.20 greatly improves compatibility with Dell monitors. The problems with my Dell 2405 not syncing properly to VidHD appear fixed. I'm not sure how many Dell Monitors will now work correctly with VidHD, but it looks promising.
-JB
|
|
|
|
| Re: VidHD Question [message #380864 is a reply to message #380738] |
Fri, 08 February 2019 16:24 |
|
|
Originally posted by: jbrooks
I have a beta version of the VidHD firmware which uses the new linux 4.20 HDMI drivers.
If anyone is having trouble with their display not syncing and would like to help test the new firmware, please send me a PM.
-JB
|
|
|
|
| Re: VidHD Question [message #381501 is a reply to message #380441] |
Fri, 01 March 2019 06:42 |
roughana
Messages: 219
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
On Friday, February 1, 2019 at 2:18:49 PM UTC+11, thom wrote:
> I installed mine yesterday in my IIe to compare with the A2Heven VGA Scaler. As of right now, I'm sort of leaning toward calling it "beautiful, but temperamental".
> From a cold boot with the VidHD going to HDMI, I see the firmware bootup of the card, then the screen will go black.
> I consider there's a lot going on in my IIe (Fastchip, Uthernet, Ramworks, Soundblaster, CFFA3k), so there's a bit to consider re: compatibility.
The problem is the Fastchip //e usage of DMA. The VidHD manual mentions this now and how to work with it. Unfortunately, they don't work 100% well together. Transwarp //e has the same symptom.
Regards,
Andrew
|
|
|
|
| Re: VidHD Question [message #381611 is a reply to message #381501] |
Tue, 05 March 2019 18:16 |
|
|
Originally posted by: Brian Patrie
On 01/03/2019 05.42, andrew.roughan@writeme.com wrote:
> On Friday, February 1, 2019 at 2:18:49 PM UTC+11, thom wrote:
>> I installed mine yesterday in my IIe to compare with the A2Heven VGA Scaler. As of right now, I'm sort of leaning toward calling it "beautiful, but temperamental".
>
>> From a cold boot with the VidHD going to HDMI, I see the firmware bootup of the card, then the screen will go black.
>
>> I consider there's a lot going on in my IIe (Fastchip, Uthernet, Ramworks, Soundblaster, CFFA3k), so there's a bit to consider re: compatibility.
>
> The problem is the Fastchip //e usage of DMA. The VidHD manual mentions this now and how to work with it. Unfortunately, they don't work 100% well together. Transwarp //e has the same symptom.
>
> Regards,
> Andrew
Need to combine them into one card.
/me hides!
|
|
|
|
| Re: VidHD Question [message #382546 is a reply to message #380556] |
Thu, 28 March 2019 21:40 |
|
|
Originally posted by: cashbackideas
On Sunday, February 3, 2019 at 12:57:17 PM UTC-6, jbr...@blueshiftinc.com wrote:
> 3) Both the Microdrive Turbo and the Floppy Emu can freeze when VidHD starts up and reads video memory w/DMA . A workaround for this is to hold ctrl-reset for about 6 seconds at power on so VidHD's startup DMA happens before the disk boots. Another option for the MDT is to disable DMA using it's setup utility. I plan to add a 'boot delay' option in a future VidHD firmware update to automate this fix.
>
> -JB
John - the 6 second ctrl-reset hold worked like a champ for me. My ROM 3 boots from an MDT and I also have an Apple High-Speed SCSI card. Both now with DMA turned on and behaving themselves nicely. Looking forward to the boot delay option.
-Jim
|
|
|
|
Members
Search
Help
Register
Login
Home
